[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1728244

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  ===SRU Justification===
  Hantick touchpad stops working after reboot.

  [Fix]
  Disable runtime power management for the touchpad.

  [Test]
  User confirmed it fixed the issue.
  Some users reported it doesn't work for them, I'll ask them to file new
  bugs for different touchpads.

  [Regression Potential]
  Low. Disable runtime power management doesn't affect devivce's
  funtionality. In general desktop usage the graphical session opens the
  touchpad HID device so the touchpad never get runtime suspended, so it
  won't hurt power in this case.

  ===Original Bug Report===
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, 
if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as 
bootloader (this is the only way to get linux booting on this laptop) 
everything works out of the box, but after a reboot or two the touchpad stops 
working. Both in Ubuntu and Windows 10. The only way to restore functionality 
is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and 
detach-reattach battery cable. This is mesg | grep i2c_hid:

  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1806682] Re: ACPI: Invalid passive threshold

[Bug Watch Updater]

** Changed in: linux
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806682

Title:
  ACPI: Invalid passive threshold

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  dmesg:
  [1.423794] ACPI: Invalid passive threshold

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2739 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2739 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 09:17:14 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806682/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1806682]

[caravena]

Created attachment 280155
$ sudo acpidump > acpidump.out

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806682

Title:
  ACPI: Invalid passive threshold

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  dmesg:
  [1.423794] ACPI: Invalid passive threshold

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2739 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2739 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 09:17:14 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806682/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1806682]

[rui.zhang]

please attach the acpidump output.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1806682

Title:
  ACPI: Invalid passive threshold

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  dmesg:
  [1.423794] ACPI: Invalid passive threshold

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2739 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2739 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 09:17:14 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1806682/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1722027] Re: Removing kernel packages leads to initrd regens, reboot-required

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-base (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1722027

Title:
  Removing kernel packages leads to initrd regens, reboot-required

Status in linux-base package in Ubuntu:
  Confirmed

Bug description:
  This concerns linux-base 4.0ubuntu1 in Ubuntu Xenial.

  Removing Linux kernel packages from the system leads to initrd
  generation and causes /var/run/reboot-required to appear. Neither of
  these side effects should occur if only kernel packages older than the
  running one are removed, a common operation in system maintenance.

  Below is a terminal session illustrating the problem. Note the update-
  initramfs lines indicating that an initrd is being (re)generated. The
  removal process paused for a few seconds at these lines, because
  generating an initrd is somewhat disk- and CPU-intensive. (Look
  closely at the versions of the initrd that are generated---the system
  is refreshing initrd files for the kernel versions that are being
  removed!)

   Terminal log begins 

  # ls /var/run/reboot-required
  ls: cannot access '/var/run/reboot-required': No such file or directory

  # apt-get --purge autoremove
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
linux-headers-4.4.0-83* linux-headers-4.4.0-83-generic*
linux-headers-4.4.0-87* linux-headers-4.4.0-87-generic*
linux-headers-4.4.0-89* linux-headers-4.4.0-89-generic*
linux-headers-4.4.0-91* linux-headers-4.4.0-91-generic*
linux-image-4.4.0-83-generic* linux-image-4.4.0-87-generic*
linux-image-4.4.0-89-generic* linux-image-4.4.0-91-generic*
linux-image-extra-4.4.0-83-generic* linux-image-extra-4.4.0-87-generic*
linux-image-extra-4.4.0-89-generic* linux-image-extra-4.4.0-91-generic*
  0 upgraded, 0 newly installed, 16 to remove and 0 not upgraded.
  After this operation, 1,188 MB disk space will be freed.
  Do you want to continue? [Y/n] 
  (Reading database ... 353048 files and directories currently installed.)
  Removing linux-headers-4.4.0-83-generic (4.4.0-83.106) ...
  Removing linux-headers-4.4.0-83 (4.4.0-83.106) ...
  Removing linux-headers-4.4.0-87-generic (4.4.0-87.110) ...
  Removing linux-headers-4.4.0-87 (4.4.0-87.110) ...
  Removing linux-headers-4.4.0-89-generic (4.4.0-89.112) ...
  Removing linux-headers-4.4.0-89 (4.4.0-89.112) ...
  Removing linux-headers-4.4.0-91-generic (4.4.0-91.114) ...
  Removing linux-headers-4.4.0-91 (4.4.0-91.114) ...
  Removing linux-image-extra-4.4.0-83-generic (4.4.0-83.106) ...
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-83-generic
  run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
  run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
  run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
  run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-4.4.0-96-generic
  Found initrd image: /boot/initrd.img-4.4.0-96-generic
  Found linux image: /boot/vmlinuz-4.4.0-93-generic
  Found initrd image: /boot/initrd.img-4.4.0-93-generic
  Found linux image: /boot/vmlinuz-4.4.0-92-generic
  Found initrd image: /boot/initrd.img-4.4.0-92-generic
  Found linux image: /boot/vmlinuz-4.4.0-91-generic
  Found initrd image: /boot/initrd.img-4.4.0-91-generic
  Found linux image: /boot/vmlinuz-4.4.0-89-generic
  Found initrd image: /boot/initrd.img-4.4.0-89-generic
  Found linux image: /boot/vmlinuz-4.4.0-87-generic
  Found initrd image: /boot/initrd.img-4.4.0-87-generic
  Found linux image: /boot/vmlinuz-4.4.0-83-generic
  Found initrd image: /boot/initrd.img-4.4.0-83-generic
  Found memtest86+ image: /boot/memtest86+.elf
  Found memtest86+ image: /boot/memtest86+.bin
  done
  Purging configuration files for linux-image-extra-4.4.0-83-generic 
(4.4.0-83.106) ...
  Removing linux-image-4.4.0-83-generic (4.4.0-83.106) ...
  Examining /etc/kernel/postrm.d .
  run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
  update-initramfs: Deleting /boot/initrd.img-4.4.0-83-generic
  run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-83-generic 

[Kernel-packages] [Bug 1705000] Re: ASUS G752VM: headphones and microphone not working (Ubuntu 16.04)

[IMarvinTPA]

I haven't tested the microphone or SPDIF capabilities.  But this is a
workable pinout for most uses.

[codec]
0x10ec0668 0x10431ced 0

[pincfg]
#Pin 12 is Internal Mic
0x12 0x90a60160
#Pin 14 is Internal "front" speakers
0x14 0x90170110
#Pin 15 is "Line Out" according to the manual, But Pin 15 won't let me pick 
that in HDA Jack Retask.
#Trying to use this as an output will have a constant tone too.
#Using this as an output breaks the front speakers working correctly with 
headphone detection.
0x15 0x40f000f0
#Pin 16 is the headphone jack.
0x16 0x0321403f
#Pin 18 is the external Microphone jack.
0x18 0x03a19020
#Pin 19 is nothing.
0x19 0x41f0
#Pin 1a is the internal subwoofer.  (Set the sound system to Stereo 2.1)
0x1a 0x90170151
#Pin 1b is nothing.
0x1b 0x41f0
#Pin 1d is nothing.
0x1d 0x40c6852d
#Pin 1e is the internal SPDIF out.
0x1e 0x014b1180
#Pin 1f is nothing.
0x1f 0x41f0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705000

Title:
  ASUS G752VM: headphones and microphone not working (Ubuntu 16.04)

Status in linux package in Ubuntu:
  Expired

Bug description:
  
  Hello I have an ASUS ROG-G752VM computer with Ubuntu 16.04 installed with and 
new kernel 4.12.0-041200-generic.

  I'm having problems when I plug in the headphones and microphone, they
  don't work.

  What I need to do?
  --- 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-01-24 (174 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.12.0-041200-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to xenial on 2017-01-25 (173 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705000/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1809864] Missing required logs.

[trusty ch]

Hi,

Thank you for reply. About running the command to send error report to you,
is there another way to export log and sent to you guys instead of sending
log via network. The server is located in a local network behide firewall
which block every outgoing package by security policy, opening outgoing IP
and port isn't possible now. Can you provide the way to export as file and
I can sent you a file back.

Regards,
Trusty

On Thu, Dec 27, 2018 at 1:35 PM Ubuntu Kernel Bot <
kernel-team-...@canonical.com> wrote:

> This bug is missing log files that will aid in diagnosing the problem.
> While running an Ubuntu kernel (not a mainline or third-party kernel)
> please enter the following command in a terminal window:
>
> apport-collect 1809864
>
> and then change the status of the bug to 'Confirmed'.
>
> If, due to the nature of the issue you have encountered, you are unable
> to run this command, please add a comment stating that fact and change
> the bug status to 'Confirmed'.
>
> This change has been made by an automated script, maintained by the
> Ubuntu Kernel Team.
>
> ** Changed in: linux (Ubuntu)
>Status: New => Incomplete
>
> ** Tags added: xenial
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1809864
>
> Title:
>   BUG: unable to handle kernel paging request at c08a5550
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   # symptom
>   OS hang, able to ping. Must do hard reboot.
>
>   # kernel info
>   Ubuntu 16.04.5 LTS
>   Kernel: Ubuntut 4.4.0-135.161-generic
>
>   # Kernel log
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.673329] BUG: unable to
> handle kernel paging request at c08a5550
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.673365] IP:
> [] __remove_mapping+0x8d/0x190
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.673394] PGD 1e0f067 PUD
> 1e11067 PMD 84e42a067 PTE 0
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.673420] Oops:  [#1] SMP
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.673436] Modules linked in:
> openafs(POE) binfmt_misc ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs
> skx_edac edac_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel
> kvm irqbypass ipmi_ssif joydev input_leds mei_me mei shpchp ioatdma dca
> ipmi_si 8250_fintek ipmi_msghandler acpi_power_meter acpi_pad mac_hid
> ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp
> libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid0
> multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor
> async_tx xor raid6_pq libcrc32c ses enclosure scsi_transport_sas raid1
> crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64
> lrw hid_generic gf128mul glue_helper ablk_helper cryptd ast i2c_algo_bit
> ttm drm_kms_helper i40e syscopyarea sysfillrect vxlan sysimgblt
> ip6_udp_tunnel fb_sys_fops udp_tunnel ptp megaraid_sas nvme usbhid drm
> pps_core ahci hid libahci wmi fjes [last unloaded: openafs]
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.673861] CPU: 5 PID: 187
> Comm: kswapd0 Tainted: PB  OE   4.4.0-135-generic #161-Ubuntu
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.673892] Hardware name:
> Supermicro SSG-6029P-E1CR12T/X11DPH-T, BIOS 2.1 06/15/2018
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.673919] task:
> 881054c85500 ti: 8808518c8000 task.ti: 8808518c8000
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.673945] RIP:
> 0010:[]  [] __remove_mapping+0x8d/0x190
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.673978] RSP:
> 0018:8808518cba40  EFLAGS: 00010002
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.673998] RAX:
> c08a5500 RBX: ea00191c1500 RCX: 0246
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.674022] RDX:
>  RSI:  RDI: 8807f9104d80
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.674047] RBP:
> 8808518cba78 R08:  R09: 8807f9104d68
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.674072] R10:
> 8808518cb9f8 R11:  R12: 8807f9104d80
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.674097] R13:
> 0001 R14: 88084e39d800 R15: 8807f9104d68
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.674122] FS:
> () GS:88085cb4() knlGS:
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.674150] CS:  0010 DS: 
> ES:  CR0: 80050033
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.674171] CR2:
> c08a5550 CR3: 000844156000 CR4: 00360670
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.674196] DR0:
>  DR1:  DR2: 
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.674221] DR3:
>  DR6: fffe0ff0 DR7: 0400
>   Dec 27 11:42:02 fileserver7 kernel: [8092783.674246] Stack:
>   Dec 27 11:42:02 fileserver7 

[Kernel-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[VanVan]

@sojusnik
It should be included for UX391UA, I committed it on 19 December 
https://github.com/torvalds/linux/commit/9cf6533e8060d3896b88ea14b27f620e6504b84b

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784485

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 811745] Re: Whole system freeze after safely remove external usb drive

[Saren Taşçıyan]

@politas Should we change the status to new?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/811745

Title:
  Whole system freeze after safely remove external usb drive

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Released

Bug description:
  OS: Ubuntu 10.04.2 LTS
  Kernel: 2.6.32-33 upgraded usnig official Ubuntu package
  description: Upgrading the kernel to 2.6.32-33 yesterday morning, and got no 
problem using my laptop until
  about 11pm, after I ejected my external usb drive, the whole system freeze, 
no response from keyboard, mouse, and even the system clock on the panel stop 
updating(it freeze at the time of ejecting usb drive). Falling back to kernel 
2.6.32.32 solve the problem so I assumed there are some issues in the lastest 
kernel. This bug is repeatable on my Asus M51va laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-32-generic-pae 2.6.32-32.62
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.32-32.62-genusername-pae 2.6.32.38+drm33.16
  Uname: Linux 2.6.32-32-generic-pae i686
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eric   1758 F pulseaudio
  CRDA: Error: [Errno 2] 沒有此一檔案或目錄
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfdef8000 irq 22'
     Mixer name : 'Realtek ALC663'
     Components : 'HDA:10ec0663,10431878,0011 
HDA:10573055,10431316,00100700'
     Controls  : 16
     Simple ctrls  : 9
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdfec000 irq 17'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,0010'
     Controls  : 4
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined penum
     Playback channels: Mono
     Mono: Playback [on]
  Date: Sun Jul 17 10:02:21 2011
  HibernationDevice: RESUME=UUID=6332cbb4-4548-4b11-8ec0-bd496fe6cd3e
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: ASUSTeK Computer Inc. M51Va
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-32-genusername-pae 
root=UUID=48ac84e3-5361-4c27-b339-7c2648d21ae4 ro quiet splash
  ProcEnviron:
   LANGUAGE=zh_TW:zh
   LANG=zh_TW.utf8
   SHELL=/bin/bash
  RelatedPackageVersions: linux-firmware 1.34.7
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: yes
  SourcePackage: linux
  dmi.bios.date: 07/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 206.000
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51Va
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr206.000:bd07/11/2008:svnASUSTeKComputerInc.:pnM51Va:pvr1.0:rvnASUSTeKComputerInc.:rnM51Va:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51Va
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/811745/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1685794] Re: Boot delayed for about 90 seconds until 'random: crng init done'

[Gustavo Carneiro]

Neither rng-tools nor haveged solves this problem for me.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1685794

Title:
  Boot delayed for about 90 seconds until 'random: crng init done'

Status in linux package in Ubuntu:
  Confirmed
Status in broadcom-sta package in Debian:
  New

Bug description:

  Shortened dmesg output, notice the unnaturally long delay before crng
  init finishes:

  [8.533630] Bluetooth: hci0: Intel Bluetooth firmware patch completed and 
activated
  [8.542239] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1b.0/sound/card1/input18
  [8.542313] input: HDA Intel PCH Line as 
/devices/pci:00/:00:1b.0/sound/card1/input19
  [8.542382] input: HDA Intel PCH Dock Line Out as 
/devices/pci:00/:00:1b.0/sound/card1/input20
  [8.542449] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card1/input21
  [8.544240] cdc_ether 2-6:2.0 usb0: register 'cdc_ether' at 
usb-:00:14.0-6, CDC Ethernet Device, 02:1e:10:1f:00:00
  [8.544271] usbcore: registered new interface driver cdc_ether
  [8.637660] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
  [8.654022] input: HP WMI hotkeys as /devices/virtual/input/input22
  [8.688226] cdc_ether 2-6:2.0 enp0s20u6c2: renamed from usb0
  [8.713288] iwlwifi :02:00.0 wlo1: renamed from wlan0
  [9.804308] input: ST LIS3LV02DL Accelerometer as 
/devices/platform/lis3lv02d/input/input23
  [   98.327857] random: crng init done
  [   98.330072] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   98.330073] Bluetooth: BNEP filters: protocol multicast
  [   98.330077] Bluetooth: BNEP socket layer initialized
  [   98.443281] kauditd_printk_skb: 90 callbacks suppressed
  [   98.492927] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
  [   98.681030] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
  [   98.685672] IPv6: ADDRCONF(NETDEV_UP): enp0s20u6c2: link is not ready
  [   98.685789] cdc_ether 2-6:2.0 enp0s20u6c2: kevent 12 may have been dropped
  [   98.688384] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
  [   98.690915] iwlwifi :02:00.0: L1 Enabled - LTR Enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 24 14:58:33 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-18 (5 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=9fb9fc1d-15a4-4e98-a2ae-bf572e0900d5 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: USH452L0B1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1809935] Re: Bugs

[Jose Abreu]

Apport-recogida 1809935
Apport-recogida: orden no encontrada


** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809935

Title:
  Bugs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, I have a problem with this

  
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. 
  Bus 001 Device 003: ID 04f2:b627 Chicony Electronics Co., Ltd 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Dont have driver fingerprint HP Pavilion x360. I need help. thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1809935] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1809935

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809935

Title:
  Bugs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi, I have a problem with this

  
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. 
  Bus 001 Device 003: ID 04f2:b627 Chicony Electronics Co., Ltd 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Dont have driver fingerprint HP Pavilion x360. I need help. thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1809935] [NEW] Bugs

[Jose Abreu]

Public bug reported:

Hi, I have a problem with this


Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. 
Bus 001 Device 003: ID 04f2:b627 Chicony Electronics Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Dont have driver fingerprint HP Pavilion x360. I need help. thanks.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809935

Title:
  Bugs

Status in linux package in Ubuntu:
  New

Bug description:
  Hi, I have a problem with this

  
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. 
  Bus 001 Device 003: ID 04f2:b627 Chicony Electronics Co., Ltd 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Dont have driver fingerprint HP Pavilion x360. I need help. thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809935/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Madani]

Hi. I'm experiencing problems that look very similar to the ones
described in this bug report (can't boot from USB, changes made in UEFI
won't save). This I noticed a couple days ago when trying to install a
new distro, that failed with "Installing for x86_64-efi platform. Could
not delete variable: interrupted system call. Grub-
install:error:efibootmgr failed to register the boot entry: block device
required"

I had Ubuntu 17.10 installed last year.

To make a long story short, I tried boot-repair and it failed, I tried
installing other distros and got the same message. I tried upgrading the
UEFI and it failed. It seems I can't even get a grub menu or prompt at
startup. My computer boots to the message "no boot device on HDD". I can
still boot however, if I pres F9 and manually choose "boot from EFI
file" and select the proper .efi file (I can boot into Lubuntu 18.10).

My computer is an HP Pavilion 14-n249nf

I initially asked about the problem at
https://askubuntu.com/questions/1104515.

1. how can I know for sure if this bug is the source of my problems ?
2. I followed the repair method described in the bug description. I can install 
kernel 4.15 without problems. But with no grub prompt at startup, how can I 
make sure to boot the right kernel that will fix my issues ?

thanks in advance for some answers

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734147

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Toshiba Satellite L70-A-13M
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     

[Kernel-packages] [Bug 1776266] Re: Touchpad and keyboard of MacBook unresponsive

[Ole]

Last update for people finding this via google: Changed the ribbon cable
from the touchpad to the motherboard. New cable has flaws as well,
force-click is not working. :-| But no unresponsiveness anymore. So
definitely a hardware issue.

Why on earth would Linux crap out while macOS works flawlessly with a
flaky ribbon cable? Mystery.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776266

Title:
  Touchpad and keyboard of MacBook unresponsive

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad and keyboard of my Macbook are unresponsive in Ubuntu
  18.04. External USB devices are fine. At first it happened
  sporadically at boot or kicking in during operation, now it's a
  somewhat permanent state. In grub I can still use the keyboard, on the
  login screen not anymore.

  dmesg snippet of the relevant lines:

  [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 
2018 (Ubuntu 4.15.0-22.24-generic 4.15.17)
  [ ... ]
  [1.644120] usb 1-5: new full-speed USB device number 3 using xhci_hcd
  [1.772223] usb 1-5: device descriptor read/64, error -71
  [2.008240] usb 1-5: device descriptor read/64, error -71
  [2.244154] usb 1-5: new full-speed USB device number 4 using xhci_hcd
  [2.372240] usb 1-5: device descriptor read/64, error -71
  [2.608239] usb 1-5: device descriptor read/64, error -71
  [2.716180] usb usb1-port5: attempt power cycle
  [3.368155] usb 1-5: new full-speed USB device number 5 using xhci_hcd
  [3.368385] usb 1-5: Device not responding to setup address.
  [3.576372] usb 1-5: Device not responding to setup address.
  [3.784150] usb 1-5: device not accepting address 5, error -71
  [3.912155] usb 1-5: new full-speed USB device number 6 using xhci_hcd
  [3.912397] usb 1-5: Device not responding to setup address.
  [4.120389] usb 1-5: Device not responding to setup address.
  [4.328154] usb 1-5: device not accepting address 6, error -71
  [4.328190] usb usb1-port5: unable to enumerate USB device

  Apparently touchpad and keyboard are connected internally via USB?

  This happens with the current Ubuntu generic kernel (4.15.0-22) as
  well as vanilla upstream kernel 4.17. In fact, it happened already
  with Ubuntu 16.04 and whatever the recent kernel there was.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ole2200 F pulseaudio
   /dev/snd/controlC0:  ole2200 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 11 19:25:07 2018
  InstallationDate: Installed on 2018-06-01 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 031: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
   Bus 001 Device 030: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28bf4396-f8c7-4936-9d45-d970c49ef1f3 ro 
resume=/dev/disk/by-uuid/28bf4396-f8c7-4936-9d45-d970c49ef1f3 
resume_offset=34816 quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0176.B00.1804091715
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0176.B00.1804091715:bd04/09/2018:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776266/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : 

[Kernel-packages] [Bug 946899] Re: 8086:2a02 [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung

[Chris Rainey]

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: linux (Ubuntu)
   Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/946899

Title:
  8086:2a02 [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
  elapsed... GPU hung

Status in Linux:
  Incomplete
Status in Linux Mint:
  Incomplete
Status in xf86-video-intel:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Fedora:
  Won't Fix

Bug description:
  Since upgrading to 12.04 beta, I've seen this happen twice. The
  symptoms are:

  - The screen freezes
  - The backlight turns off

  At that point I have to reboot to get my display back. In syslog, i
  see:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.612064] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
  Mar  4 23:09:18 perseus kernel: [ 3751.612076] [drm] capturing error event; 
look for more information in /debug/dri/0/i915_error_state
  Mar  4 23:09:18 perseus kernel: [ 3751.613658] [drm:i915_wait_request] 
*ERROR* i915_wait_request returns -11 (awaiting 114040 at 114004, next 114118)
  Mar  4 23:09:18 perseus kernel: [ 3751.637049] [drm:init_ring_common] *ERROR* 
render ring initialization failed ctl  head  tail  
start 

  followed by a lot of things like:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.700662] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:793 
intel_enable_pipe+0x14a/0x150 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.700667] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.700670] PLL state assertion failure 
(expected on, current off)

  Mar  4 23:09:18 perseus kernel: [ 3751.812158] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:930 
assert_pipe+0x75/0x80 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.812165] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.812170] pipe B assertion failure 
(expected on, current off)

  then:

  
  Mar  4 23:09:19 perseus kernel: [ 3753.044086] [drm:intel_lvds_enable] 
*ERROR* timed out waiting for panel to power on
  Mar  4 23:09:20 perseus kernel: [ 3753.671451] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.684603] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.704594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.724594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.744595] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.764606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.784607] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.804618] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.824606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-17-generic 3.2.0-17.27
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdz2458 F pulseaudio
   /dev/snd/controlC1:  mdz2458 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 49'
 Mixer name : 'Analog Devices AD1984'
 Components : 'HDA:11d41984,17aa20bb,00100400'
 Controls  : 31
 Simple ctrls  : 19
  Card1.Amixer.info:
   Card hw:1 'Q9000'/'Logitech, Inc. QuickCam Pro 9000 at usb-:00:1a.7-3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0990'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: 

[Kernel-packages] [Bug 946899] Re: 8086:2a02 [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung

[Chris Rainey]

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: linuxmint
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/946899

Title:
  8086:2a02 [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
  elapsed... GPU hung

Status in Linux:
  Incomplete
Status in Linux Mint:
  Incomplete
Status in xf86-video-intel:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Fedora:
  Won't Fix

Bug description:
  Since upgrading to 12.04 beta, I've seen this happen twice. The
  symptoms are:

  - The screen freezes
  - The backlight turns off

  At that point I have to reboot to get my display back. In syslog, i
  see:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.612064] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
  Mar  4 23:09:18 perseus kernel: [ 3751.612076] [drm] capturing error event; 
look for more information in /debug/dri/0/i915_error_state
  Mar  4 23:09:18 perseus kernel: [ 3751.613658] [drm:i915_wait_request] 
*ERROR* i915_wait_request returns -11 (awaiting 114040 at 114004, next 114118)
  Mar  4 23:09:18 perseus kernel: [ 3751.637049] [drm:init_ring_common] *ERROR* 
render ring initialization failed ctl  head  tail  
start 

  followed by a lot of things like:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.700662] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:793 
intel_enable_pipe+0x14a/0x150 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.700667] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.700670] PLL state assertion failure 
(expected on, current off)

  Mar  4 23:09:18 perseus kernel: [ 3751.812158] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:930 
assert_pipe+0x75/0x80 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.812165] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.812170] pipe B assertion failure 
(expected on, current off)

  then:

  
  Mar  4 23:09:19 perseus kernel: [ 3753.044086] [drm:intel_lvds_enable] 
*ERROR* timed out waiting for panel to power on
  Mar  4 23:09:20 perseus kernel: [ 3753.671451] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.684603] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.704594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.724594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.744595] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.764606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.784607] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.804618] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.824606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-17-generic 3.2.0-17.27
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdz2458 F pulseaudio
   /dev/snd/controlC1:  mdz2458 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 49'
 Mixer name : 'Analog Devices AD1984'
 Components : 'HDA:11d41984,17aa20bb,00100400'
 Controls  : 31
 Simple ctrls  : 19
  Card1.Amixer.info:
   Card hw:1 'Q9000'/'Logitech, Inc. QuickCam Pro 9000 at usb-:00:1a.7-3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0990'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume 

[Kernel-packages] [Bug 1528345] Re: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order

[bokateeka]

Try https://sourceforge.net/u/yannubuntu/

Dual Boot repair disk



https://sourceforge.net/projects/boot-repair-cd/files/

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1528345

Title:
  grub or kernel update broke Secure Boot by putting grubx64.efi instead
  of shimx64.efi in EFI boot order

Status in One Hundred Papercuts:
  Confirmed
Status in grub2 package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I've been running Ubuntu on a Lenovo ThinkPad X240.  I initially
  installed 14.10 when I got the machine in January.  I then upgraded to
  15.04, and on Monday evening (late December 14) I upgraded to 15.10.
  I rebooted once right after the update to make sure some postfix and
  opendkim configuration changes I made worked correctly after
  rebooting.

  Then between Monday evening and Friday evening (December 19) there
  were a bunch of system updates that I installed.  On Friday evening I
  decided to reboot to boot into the updated kernel.  (There were also
  grub updates in that interval.)

  When I rebooted, the laptop said:

  Secure Boot
  Image failed to verify with *ACCESS DENIED*
  Press any key to continue.

  See the image (posted by somebody else) of this error in
  http://askubuntu.com/questions/710146/how-to-fix-secure-boot-error-
  image-failed-to-verify-with-access-denied-on-st

  I had to disable secure boot to make the system boot.

  
  Based on the discussion in 
http://askubuntu.com/questions/710146/how-to-fix-secure-boot-error-image-failed-to-verify-with-access-denied-on-st
 it appears that the problem is that the updates caused it to try to boot 
directly to grub (File(\EFI‌​\ubuntu\grubx64.efi)) rather than via the shim 
(File(\EFI‌​\ubuntu\shimx64.efi)).  I don't know for sure what sequence of 
events caused that, nor did I verify for certain that it was booting via the 
shim before.  However, I know that this reboot on Friday was the first time I 
had a secure boot failure since installing Ubuntu on the laptop (and using only 
Ubuntu; no other OSes involved) in January.

  I'll attach a list of the system updates that were applied in the
  interval between the successful boot and the failed one from
  /var/log/dpkg.log .  Note that the log is in UTC but my description
  above ("evening", etc., is in UTC-8, so the evening of December 14 is
  actually around 07:00 UTC on December 15).  Note that this log
  contains a grub update, two kernel updates, and the removal of the
  first of those kernel updates via apt-get autoremove.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: grub-common 2.02~beta2-29ubuntu0.2
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec 21 15:39:21 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-25 (330 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: grub2
  UpgradeStatus: Upgraded to wily on 2015-12-15 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1528345/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[sojusnik]

@Santiago Londoño

Or you could have used UKUU: https://github.com/teejee2008/ukuu

Too bad that the 4.20 kernel doesn't contain the fix for the UX391UA :/

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784485

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1808886] Re: Microcode SW error detected. Restarting 0x0.

[jasd666]

Still actual for me

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1808886

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 0x0022 | umac major
  [ 3166.626199] iwlwifi :00:14.3: 0x | umac minor
  [ 3166.626204] iwlwifi :00:14.3: 

[Kernel-packages] [Bug 1809168] Re: FIPS and Ubuntu standard kernels prior to 4.11.0 won't boot; root device not found

[Nivedita Singhvi]

We now believe this to be the case.  The above is an issue
of new HW enablement. 

I believe this can be closed Will Not Fix.

For standard kernels, enablement available via the -hwe 
kernel upgrade.

For FIPS kernels, new HW enablement is not expected to be
backported/patched in existing 4.4.0-baseed releases.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809168

Title:
  FIPS and Ubuntu standard kernels prior to 4.11.0 won't boot; root
  device not found

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  [IMPACT]

  Booting of the Xenial-based FIPS kernel packages
  failed with disk not found errors on amd64.
  This was also observed on standard Ubuntu
  kernels prior to 4.11.0.

  FIPS
  --
  1. linux-image-4.4.0-1002-fips <-- FAIL
  2. linux-image-4.4.0-1006-fips <-- FAIL

  UBUNTU
  

  1. Bionic kernels all WORK

  2. Artful kernels:

     Ubuntu-4.11.0-1.6 <-- WORKS
     Ubuntu-4.10.0-26.30 <-- FAILS

  3. Xenial kernels:

     Ubuntu-hwe-4.11.0-12.17_16.04.1 <--- WORKS
     Ubuntu-hwe-4.10.0-43.47_16.04.1 <--- FAILS

     Ubuntu-lts-* <--- ALL FAIL
     Ubuntu-4.4.0-* <--- ALL FAIL

  We have narrowed down the window to be:

  4.11.0-1.6 (custom build) <--- WORKS
  4.10.0-43.47~16.04.1   <-- FAILS

  Also works:
  
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb

  Symptoms
  -
  System cannot find the root disk and drops into
  an initramfs shell:

  mdadm script local-block "CREATE group disk not found"
  "Gave up waiting for root device. Common problems:
   - Boot args (cat /proc/cmdline)
     - Check rootdelay=...
     - Check root= ...
   - Missing modules (cat /proc/modules; ls/dev)
  ALERT! UUID=... does not exist. Dropping to a shell!

  ...
  (initramfs)_

  There does not appear to be any workaround so far.
  The disks are encrypted SSDs.

  Attaching commit list between the last known
  failing Artful kernel and earliest known
  working kernel (adjacent tags) and other info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809168/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1758797] Re: [Ubuntu 18.04] USB Type-C test failed on GLK

[David Hereschler Shvo]

** Changed in: linux (Ubuntu)
 Assignee: Thadeu Lima de Souza Cascardo (cascardo) => David Hereschler 
Shvo (shvo123)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1758797

Title:
  [Ubuntu 18.04] USB Type-C test failed on GLK

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  USB Type-C ports would not be seen at ls /sys/class/typec/ some times, ie, 
driver probe would fail. The fix just changes a timeout setting, allowing the 
probe to succeed in those cases there is load on the system.

  [Test Case]
  During boot, with the system at load, the probe would fail some times. With 
the increased timeout for firmware responses, that doesn't happen after many 
reboots.

  [Regression Potential]
  This would only impact systems that have this specific ACPI node. As the 
probe runs on a work queue, this should not impact boot time.

  Description:

  Platform information:
  Label: GLK02SDP
  Processor: Silver N5000
  Bios: GELKRVPA.X64.0083.B30.1801162142
  OS: Ubuntu 18.04
  Kernel: 4.15.0-10-generic

  Details:
  Bios: system setup -> system component -> USB Type-C 

  root@GLK02:~# cat /boot/config-4.15.0-10-generic | grep -i ucsi
  CONFIG_TYPEC_UCSI=m
  CONFIG_UCSI_ACPI=m

  root@GLK02:~# ls /sys/class/typec/
  root@GLK02:~#

  USB Type-C ports could not be seen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1758797/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

[spi]

Forgot to mention: I only experinece this issue for the last few days.
Didn't have this issue before and I've been using deep sleep from the
beginning when I installed Ubuntu 18.04 myself. The only thing beside
Ubuntu package updates that occured some days ago is a BIOS update to
1.6.3 on the XPS 9370.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766825

Title:
  Bluetooth issues with Dell XPS 13 (9370)

Status in Dell Sputnik:
  Triaged
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New

Bug description:
  I have the following problem with my Bluetooth module on my new Dell
  XPS 13 (9370) with Ubuntu preinstalled.

  The bluetooth module gets disabled for some reason. The bluetooth
  devices (keyboard and mouse) just stop working in the middle of the
  work, the Bluetooth indicator goes away and the module is also gone in
  the rfkill list.

  To get it back working I need to reboot the machine, start the BIOS,
  disable the Bluetooth module and re-enable it or I have to turn the
  machine completely off and on again. After that, the bluetooth module
  is available again. That's pretty annoying.

  My syslog when this happens:

  Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB 
disconnect, device number 3
  Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 
22
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch 
Status.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root.
  Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 
21
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSource
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSink
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 
12120 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 
12133 (kill).
  Apr 11 12:25:46 visyu-albatross 

[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

[spi]

I am on Ubuntu 18.04 with kernel 4.18.0-13-generic and still have the
disappearing bluetooth issue. Reboot doesn't help, need to powercycle
the XPS 9370.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766825

Title:
  Bluetooth issues with Dell XPS 13 (9370)

Status in Dell Sputnik:
  Triaged
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  New

Bug description:
  I have the following problem with my Bluetooth module on my new Dell
  XPS 13 (9370) with Ubuntu preinstalled.

  The bluetooth module gets disabled for some reason. The bluetooth
  devices (keyboard and mouse) just stop working in the middle of the
  work, the Bluetooth indicator goes away and the module is also gone in
  the rfkill list.

  To get it back working I need to reboot the machine, start the BIOS,
  disable the Bluetooth module and re-enable it or I have to turn the
  machine completely off and on again. After that, the bluetooth module
  is available again. That's pretty annoying.

  My syslog when this happens:

  Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB 
disconnect, device number 3
  Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 
22
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch 
Status...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch 
Status.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root.
  Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 
21
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSource
  Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: 
sender=:1.80 path=/MediaEndpoint/A2DPSink
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root.
  Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 
12120 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session...
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets.
  Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 
12133 (kill).
  Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root.
  Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c11 of user root.
  Apr 11 12:25:46 

[Kernel-packages] [Bug 1809886] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809886

Title:
  f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes
  failed on X

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This patch exists in the Xenial tree.

  
  Test failed with:
  failed: degraded mount should have failed, but didn't

  
  Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43

  fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43

  Btrfs: skip submitting barrier for missing device

  I got an error on v3.13:
   BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO failure 
(errors while submitting device barriers.)

  how to reproduce:
> mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2
> wipefs -a /dev/sdf2
> mount -o degraded /dev/sdf1 /mnt
> btrfs balance start -f -sconvert=single -mconvert=single 
-dconvert=single /mnt

  The reason of the error is that barrier_all_devices() failed to submit
  barrier to the missing device.  However it is clear that we cannot do
  anything on missing device, and also it is not necessary to care chunks
  on the missing device.

  This patch stops sending/waiting barrier if device is missing.

  failed: degraded mount should have failed, but didn't

  FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-164-generic 3.13.0-164.214
  ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-164-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:11 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: [   29.063592] random: nonblocking pool is initialized
  Date: Thu Dec 27 10:11:58 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-164-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-164-generic N/A
   linux-backports-modules-3.13.0-164-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809886/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1809886] Re: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes failed on X

[Po-Hsu Lin]

BTW, this test failed on a KVM node, 2 bare-metal nodes amaura, daedalus.
But passed on node rizzo.

Re-testing on rizzo to see if this node can pass with it again.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809886

Title:
  f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes
  failed on X

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This patch exists in the Xenial tree.

  
  Test failed with:
  failed: degraded mount should have failed, but didn't

  
  Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43

  fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43

  Btrfs: skip submitting barrier for missing device

  I got an error on v3.13:
   BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO failure 
(errors while submitting device barriers.)

  how to reproduce:
> mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2
> wipefs -a /dev/sdf2
> mount -o degraded /dev/sdf1 /mnt
> btrfs balance start -f -sconvert=single -mconvert=single 
-dconvert=single /mnt

  The reason of the error is that barrier_all_devices() failed to submit
  barrier to the missing device.  However it is clear that we cannot do
  anything on missing device, and also it is not necessary to care chunks
  on the missing device.

  This patch stops sending/waiting barrier if device is missing.

  failed: degraded mount should have failed, but didn't

  FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-164-generic 3.13.0-164.214
  ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-164-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 10:11 seq
   crw-rw 1 root audio 116, 33 Dec 27 10:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg: [   29.063592] random: nonblocking pool is initialized
  Date: Thu Dec 27 10:11:58 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-164-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-164-generic N/A
   linux-backports-modules-3.13.0-164-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809886/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1809886] [NEW] f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes failed on X

[Po-Hsu Lin]

Public bug reported:

This patch exists in the Xenial tree.


Test failed with:
failed: degraded mount should have failed, but didn't


Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43

fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43

Btrfs: skip submitting barrier for missing device

I got an error on v3.13:
 BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO failure 
(errors while submitting device barriers.)

how to reproduce:
  > mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2
  > wipefs -a /dev/sdf2
  > mount -o degraded /dev/sdf1 /mnt
  > btrfs balance start -f -sconvert=single -mconvert=single 
-dconvert=single /mnt

The reason of the error is that barrier_all_devices() failed to submit
barrier to the missing device.  However it is clear that we cannot do
anything on missing device, and also it is not necessary to care chunks
on the missing device.

This patch stops sending/waiting barrier if device is missing.

failed: degraded mount should have failed, but didn't

FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-164-generic 3.13.0-164.214
ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
Uname: Linux 3.13.0-164-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Dec 27 10:11 seq
 crw-rw 1 root audio 116, 33 Dec 27 10:11 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg: [   29.063592] random: nonblocking pool is initialized
Date: Thu Dec 27 10:11:58 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
 
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-164-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-164-generic N/A
 linux-backports-modules-3.13.0-164-generic  N/A
 linux-firmware  1.127.24
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty uec-images

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809886

Title:
  f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes
  failed on X

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This patch exists in the Xenial tree.

  
  Test failed with:
  failed: degraded mount should have failed, but didn't

  
  Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43

  fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43

  Btrfs: skip submitting barrier for missing device

  I got an error on v3.13:
   BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO failure 
(errors while submitting device barriers.)

  how to reproduce:
> mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2
> wipefs -a /dev/sdf2
> mount -o degraded /dev/sdf1 /mnt
> btrfs balance start -f -sconvert=single -mconvert=single 
-dconvert=single /mnt

  The reason of the error is that barrier_all_devices() failed to submit
  barrier to the missing device.  However it is clear that we cannot do
  anything on missing device, and also it is not necessary to care chunks
  on the missing device.

  This patch stops sending/waiting barrier if device is missing.

  failed: degraded mount should have failed, but didn't

  FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-164-generic 3.13.0-164.214
  ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-164-generic x86_64
  AlsaDevices:
   total 0
   

[Kernel-packages] [Bug 1809879] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809879

Title:
  9f03740a956d7ac6a1b8f8c455da6fa5cae11c22 in ubuntu_btrfs_kernel_fixes
  hang with T

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Patch 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22 does not exist in
  Trusty kernel tree.

  When running this test, it will hang with Trusty and gets killed by
  the timeout setting (2h), this will cause the following test failed
  with /dev/loop0 mounted issue:

  Invoking test 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22
   
   fix 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22
   
   Btrfs: fix infinite path build loops in incremental send
   
   The send operation processes inodes by their ascending number, and 
assumes
   that any rename/move operation can be successfully performed (sent to the
   caller) once all previous inodes (those with a smaller inode number than 
the
   one we're currently processing) were processed.
   
   [  ]
   
   Even without this loop, the incremental send couldn't succeed, because 
it would attempt
   to send a rename/move operation for the lower inode before the highest 
inode number was
   renamed/move. This issue is easy to trigger with the following steps:
   
 $ mkfs.btrfs -f /dev/sdb3
 $ mount /dev/sdb3 /mnt/btrfs
 $ mkdir -p /mnt/btrfs/a/b/c/d
 $ mkdir /mnt/btrfs/a/b/c2
 $ btrfs subvol snapshot -r /mnt/btrfs /mnt/btrfs/snap1
 $ mv /mnt/btrfs/a/b/c/d /mnt/btrfs/a/b/c2/d2
 $ mv /mnt/btrfs/a/b/c /mnt/btrfs/a/b/c2/d2/cc
 $ btrfs subvol snapshot -r /mnt/btrfs /mnt/btrfs/snap2
 $ btrfs send -p /mnt/btrfs/snap1 /mnt/btrfs/snap2 > 
/tmp/incremental.send
   
   Create a readonly snapshot of 
'/tmp/mnt-9f03740a956d7ac6a1b8f8c455da6fa5cae11c22/btrfs' in 
'/tmp/mnt-9f03740a956d7ac6a1b8f8c455da6fa5cae11c22/btrfs/snap1'
   Create a readonly snapshot of 
'/tmp/mnt-9f03740a956d7ac6a1b8f8c455da6fa5cae11c22/btrfs' in 
'/tmp/mnt-9f03740a956d7ac6a1b8f8c455da6fa5cae11c22/btrfs/snap2'
   At subvol /tmp/mnt-9f03740a956d7ac6a1b8f8c455da6fa5cae11c22/btrfs/snap2
  Timer expired (7200 sec.), nuking pid 27517
ERROR

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-164-generic 3.13.0-164.214
  ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-164-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 27 08:26 seq
   crw-rw 1 root audio 116, 33 Dec 27 08:26 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Dec 27 09:21:07 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-164-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-164-generic N/A
   linux-backports-modules-3.13.0-164-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809879/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1809879] [NEW] 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22 in ubuntu_btrfs_kernel_fixes hang with T

[Po-Hsu Lin]

Public bug reported:

Patch 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22 does not exist in Trusty
kernel tree.

When running this test, it will hang with Trusty and gets killed by the
timeout setting (2h), this will cause the following test failed with
/dev/loop0 mounted issue:

Invoking test 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22
 
 fix 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22
 
 Btrfs: fix infinite path build loops in incremental send
 
 The send operation processes inodes by their ascending number, and assumes
 that any rename/move operation can be successfully performed (sent to the
 caller) once all previous inodes (those with a smaller inode number than 
the
 one we're currently processing) were processed.
 
 [  ]
 
 Even without this loop, the incremental send couldn't succeed, because it 
would attempt
 to send a rename/move operation for the lower inode before the highest 
inode number was
 renamed/move. This issue is easy to trigger with the following steps:
 
   $ mkfs.btrfs -f /dev/sdb3
   $ mount /dev/sdb3 /mnt/btrfs
   $ mkdir -p /mnt/btrfs/a/b/c/d
   $ mkdir /mnt/btrfs/a/b/c2
   $ btrfs subvol snapshot -r /mnt/btrfs /mnt/btrfs/snap1
   $ mv /mnt/btrfs/a/b/c/d /mnt/btrfs/a/b/c2/d2
   $ mv /mnt/btrfs/a/b/c /mnt/btrfs/a/b/c2/d2/cc
   $ btrfs subvol snapshot -r /mnt/btrfs /mnt/btrfs/snap2
   $ btrfs send -p /mnt/btrfs/snap1 /mnt/btrfs/snap2 > /tmp/incremental.send
 
 Create a readonly snapshot of 
'/tmp/mnt-9f03740a956d7ac6a1b8f8c455da6fa5cae11c22/btrfs' in 
'/tmp/mnt-9f03740a956d7ac6a1b8f8c455da6fa5cae11c22/btrfs/snap1'
 Create a readonly snapshot of 
'/tmp/mnt-9f03740a956d7ac6a1b8f8c455da6fa5cae11c22/btrfs' in 
'/tmp/mnt-9f03740a956d7ac6a1b8f8c455da6fa5cae11c22/btrfs/snap2'
 At subvol /tmp/mnt-9f03740a956d7ac6a1b8f8c455da6fa5cae11c22/btrfs/snap2
Timer expired (7200 sec.), nuking pid 27517
ERROR

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-164-generic 3.13.0-164.214
ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
Uname: Linux 3.13.0-164-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Dec 27 08:26 seq
 crw-rw 1 root audio 116, 33 Dec 27 08:26 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Dec 27 09:21:07 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
 
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-164-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-164-generic N/A
 linux-backports-modules-3.13.0-164-generic  N/A
 linux-firmware  1.127.24
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty uec-images

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809879

Title:
  9f03740a956d7ac6a1b8f8c455da6fa5cae11c22 in ubuntu_btrfs_kernel_fixes
  hang with T

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Patch 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22 does not exist in
  Trusty kernel tree.

  When running this test, it will hang with Trusty and gets killed by
  the timeout setting (2h), this will cause the following test failed
  with /dev/loop0 mounted issue:

  Invoking test 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22
   
   fix 9f03740a956d7ac6a1b8f8c455da6fa5cae11c22
   
   Btrfs: fix infinite path build loops in incremental send
   
   The send operation processes inodes by their ascending number, and 
assumes
   that any rename/move operation can be successfully performed (sent to the
   caller) once all 

[Kernel-packages] [Bug 1809872] Re: btrfs send / receive command with -f argument position in btrfs_kernel_fixes is causing failures on B

[Po-Hsu Lin]

In Btrfs v3.12 on Trusty, the --help shows the identical layout:

* btrfs send [-ve] [-p ] [-c ] [-f ] 
* btrfs receive [-ve] [-f ] 

So we should be able to fix this once for all.

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: ubuntu-kernel-tests
   Importance: Undecided => Medium

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809872

Title:
  btrfs send / receive command with -f argument position in
  btrfs_kernel_fixes is causing failures on B

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This issue is different from bug 1809869.

  Test failed with:
  ERROR: unable to resolve -f
  And:
  btrfs receive: too many arguments

  This patch does exist in Bionic kernel tree.

  
  Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  Btrfs: send, don't send rmdir for same target multiple times

  When doing an incremental send, if we delete a directory that has N > 1
  hardlinks for the same file and that file has the highest inode number
  inside the directory contents, an incremental send would send N times an
  rmdir operation against the directory. This made the btrfs receive command
  fail on the second rmdir instruction, as the target directory didn't exist
  anymore.

  btrfs-progs v4.15.1
  See http://btrfs.wiki.kernel.org for more information.

  Performing full device TRIM /dev/loop0 (1.00GiB) ...
  Label:  (null)
  UUID:   b9297d7d-f8b6-469e-b3c5-64ac1bf1e3d8
  Node size:  16384
  Sector size:4096
  Filesystem size:1.00GiB
  Block group profiles:
Data: single8.00MiB
Metadata: DUP  51.19MiB
System:   DUP   8.00MiB
  SSD detected:   no
  Incompat features:  extref, skinny-metadata
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  1 1.00GiB  /dev/loop0

  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
  ERROR: unable to resolve -f
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
  ERROR: unable to resolve -f
  btrfs-progs v4.15.1
  See http://btrfs.wiki.kernel.org for more information.

  Performing full device TRIM /dev/loop0 (1.00GiB) ...
  Label:  (null)
  UUID:   e6351943-c767-4339-b662-609e80dae55b
  Node size:  16384
  Sector size:4096
  Filesystem size:1.00GiB
  Block group profiles:
Data: single8.00MiB
Metadata: DUP  51.19MiB
System:   DUP   8.00MiB
  SSD detected:   no
  Incompat features:  extref, skinny-metadata
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  1 1.00GiB  /dev/loop0

  btrfs receive: too many arguments
  usage: btrfs receive [options] 
 btrfs receive --dump [options]

  Receive subvolumes from a stream

  Receives one or more subvolumes that were previously
  sent with btrfs send. The received subvolumes are stored
  into MOUNT.
  The receive will fail in case the receiving subvolume
  already exists. It will also fail in case a previously
  received subvolume has been changed after it was received.
  After receiving a subvolume, it is immediately set to
  read-only.

  -v   increase verbosity about performed actions
  -f FILE  read the stream from FILE instead of stdin
  -e   terminate after receiving an  marker in the 
stream.
   Without this option the receiver side terminates only in 
case
   of an error on end of file.
  -C|--chroot  confine the process to  using chroot
  -E|--max-errors NERR
   terminate as soon as NERR errors occur while
   stream processing commands from the stream.
   Default value is 1. A value of 0 means no limit.
  -m ROOTMOUNT the root mount point of the destination filesystem.
   If /proc is not accessible, use this to tell us where
   this file system is mounted.
  --dump   dump stream metadata, one line per operation,
   does not require the MOUNT parameter

  btrfs receive: too many arguments
  usage: btrfs receive [options] 
 btrfs receive --dump [options]

  Receive subvolumes from a stream

  Receives one or more subvolumes that were previously
  sent with btrfs send. The 

[Kernel-packages] [Bug 1809872] Re: btrfs send / receive command with -f argument position in btrfs_kernel_fixes is causing failures on B

[Po-Hsu Lin]

This issue is not related to the kernel,

for btrfs-progs v4.15.1 on Bionic, the btrfs send / receive command should be:
  * btrfs send [-ve] [-p ] [-c ] [-f ]  
[...]
  * btrfs receive [options] 

So the btrfs send in the script should be changed from:
btrfs send $MNT/snap1 -f $TMP/base.send
To:
btrfs send -f $TMP/base.send $MNT/snap1

For receive, it should be changed from:
btrfs receive $MNT -f $TMP/base.send
To:
btrfs receive -f $TMP/base.send $MNT


This change should be tested across distros, otherwise we need to use different 
command layout for different version of btrfstools.


** Summary changed:

- 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed on B
+ btrfs send / receive command with -f argument position in btrfs_kernel_fixes 
is causing failures on B

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809872

Title:
  btrfs send / receive command with -f argument position in
  btrfs_kernel_fixes is causing failures on B

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This issue is different from bug 1809869.

  Test failed with:
  ERROR: unable to resolve -f
  And:
  btrfs receive: too many arguments

  This patch does exist in Bionic kernel tree.

  
  Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  Btrfs: send, don't send rmdir for same target multiple times

  When doing an incremental send, if we delete a directory that has N > 1
  hardlinks for the same file and that file has the highest inode number
  inside the directory contents, an incremental send would send N times an
  rmdir operation against the directory. This made the btrfs receive command
  fail on the second rmdir instruction, as the target directory didn't exist
  anymore.

  btrfs-progs v4.15.1
  See http://btrfs.wiki.kernel.org for more information.

  Performing full device TRIM /dev/loop0 (1.00GiB) ...
  Label:  (null)
  UUID:   b9297d7d-f8b6-469e-b3c5-64ac1bf1e3d8
  Node size:  16384
  Sector size:4096
  Filesystem size:1.00GiB
  Block group profiles:
Data: single8.00MiB
Metadata: DUP  51.19MiB
System:   DUP   8.00MiB
  SSD detected:   no
  Incompat features:  extref, skinny-metadata
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  1 1.00GiB  /dev/loop0

  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
  ERROR: unable to resolve -f
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
  ERROR: unable to resolve -f
  btrfs-progs v4.15.1
  See http://btrfs.wiki.kernel.org for more information.

  Performing full device TRIM /dev/loop0 (1.00GiB) ...
  Label:  (null)
  UUID:   e6351943-c767-4339-b662-609e80dae55b
  Node size:  16384
  Sector size:4096
  Filesystem size:1.00GiB
  Block group profiles:
Data: single8.00MiB
Metadata: DUP  51.19MiB
System:   DUP   8.00MiB
  SSD detected:   no
  Incompat features:  extref, skinny-metadata
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  1 1.00GiB  /dev/loop0

  btrfs receive: too many arguments
  usage: btrfs receive [options] 
 btrfs receive --dump [options]

  Receive subvolumes from a stream

  Receives one or more subvolumes that were previously
  sent with btrfs send. The received subvolumes are stored
  into MOUNT.
  The receive will fail in case the receiving subvolume
  already exists. It will also fail in case a previously
  received subvolume has been changed after it was received.
  After receiving a subvolume, it is immediately set to
  read-only.

  -v   increase verbosity about performed actions
  -f FILE  read the stream from FILE instead of stdin
  -e   terminate after receiving an  marker in the 
stream.
   Without this option the receiver side terminates only in 
case
   of an error on end of file.
  -C|--chroot  confine the process to  using chroot
  -E|--max-errors NERR
   terminate as soon as NERR errors occur while
   stream processing commands from the stream.
   Default value is 1. A value of 0 means no limit.
  -m ROOTMOUNT the root mount point of the destination filesystem.
   If /proc is not 

[Kernel-packages] [Bug 1809870] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1809870

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809870

Title:
  2365dd3ca02bbb6d3412404482e1d85752549953 in ubuntu_btrfs_kernel_fixes
  failed on B

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Test failed on Bionic, and this patch does exist in Bionic kernel
  tree.

  
  Invoking test 2365dd3ca02bbb6d3412404482e1d85752549953

  fix 2365dd3ca02bbb6d3412404482e1d85752549953

  btrfs: undo sysfs when open_ctree() fails

  reproducer:
  mkfs.btrfs -f /dev/sdb &&mount /dev/sdb /btrfs &&btrfs dev add -f 
/dev/sdc /btrfs &&umount /btrfs &&wipefs -a /dev/sdc &&mount -o 
degraded /dev/sdb /btrfs
  //above mount fails so try with RO
  mount -o degraded,ro /dev/sdb /btrfs

  --
  sysfs: cannot create duplicate filename 
'/fs/btrfs/3f48c79e-5ed0-4e87-b189-86e749e503f4'
  ::

  Performing full device TRIM /dev/loop1 (512.00MiB) ...
  mount -o degraded /dev/loop0 
/tmp/mnt-2365dd3ca02bbb6d3412404482e1d85752549953 was expected to fail

  FAIL: 2365dd3ca02bbb6d3412404482e1d85752549953 (ret=1)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 20 18:17 seq
   crw-rw 1 root audio 116, 33 Dec 20 18:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Thu Dec 27 07:34:54 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809870/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1809872] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1809872

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809872

Title:
  29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed
  on B

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue is different from bug 1809869.

  Test failed with:
  ERROR: unable to resolve -f
  And:
  btrfs receive: too many arguments

  This patch does exist in Bionic kernel tree.

  
  Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  Btrfs: send, don't send rmdir for same target multiple times

  When doing an incremental send, if we delete a directory that has N > 1
  hardlinks for the same file and that file has the highest inode number
  inside the directory contents, an incremental send would send N times an
  rmdir operation against the directory. This made the btrfs receive command
  fail on the second rmdir instruction, as the target directory didn't exist
  anymore.

  btrfs-progs v4.15.1
  See http://btrfs.wiki.kernel.org for more information.

  Performing full device TRIM /dev/loop0 (1.00GiB) ...
  Label:  (null)
  UUID:   b9297d7d-f8b6-469e-b3c5-64ac1bf1e3d8
  Node size:  16384
  Sector size:4096
  Filesystem size:1.00GiB
  Block group profiles:
Data: single8.00MiB
Metadata: DUP  51.19MiB
System:   DUP   8.00MiB
  SSD detected:   no
  Incompat features:  extref, skinny-metadata
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  1 1.00GiB  /dev/loop0

  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
  ERROR: unable to resolve -f
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
  ERROR: unable to resolve -f
  btrfs-progs v4.15.1
  See http://btrfs.wiki.kernel.org for more information.

  Performing full device TRIM /dev/loop0 (1.00GiB) ...
  Label:  (null)
  UUID:   e6351943-c767-4339-b662-609e80dae55b
  Node size:  16384
  Sector size:4096
  Filesystem size:1.00GiB
  Block group profiles:
Data: single8.00MiB
Metadata: DUP  51.19MiB
System:   DUP   8.00MiB
  SSD detected:   no
  Incompat features:  extref, skinny-metadata
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  1 1.00GiB  /dev/loop0

  btrfs receive: too many arguments
  usage: btrfs receive [options] 
 btrfs receive --dump [options]

  Receive subvolumes from a stream

  Receives one or more subvolumes that were previously
  sent with btrfs send. The received subvolumes are stored
  into MOUNT.
  The receive will fail in case the receiving subvolume
  already exists. It will also fail in case a previously
  received subvolume has been changed after it was received.
  After receiving a subvolume, it is immediately set to
  read-only.

  -v   increase verbosity about performed actions
  -f FILE  read the stream from FILE instead of stdin
  -e   terminate after receiving an  marker in the 
stream.
   Without this option the receiver side terminates only in 
case
   of an error on end of file.
  -C|--chroot  confine the process to  using chroot
  -E|--max-errors NERR
   terminate as soon as NERR errors occur while
   stream processing commands from the stream.
   Default value is 1. A value of 0 means no limit.
  -m ROOTMOUNT the root mount point of the destination filesystem.
   If /proc is not accessible, use this to tell us where
   this file system is mounted.
  --dump   dump stream metadata, one line per operation,
   does not require the MOUNT parameter

  btrfs receive: too many arguments
  usage: btrfs receive [options] 
 btrfs 

[Kernel-packages] [Bug 1809872] Re: 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed on B

[Po-Hsu Lin]

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809872

Title:
  29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed
  on B

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue is different from bug 1809869.

  Test failed with:
  ERROR: unable to resolve -f
  And:
  btrfs receive: too many arguments

  This patch does exist in Bionic kernel tree.

  
  Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5

  Btrfs: send, don't send rmdir for same target multiple times

  When doing an incremental send, if we delete a directory that has N > 1
  hardlinks for the same file and that file has the highest inode number
  inside the directory contents, an incremental send would send N times an
  rmdir operation against the directory. This made the btrfs receive command
  fail on the second rmdir instruction, as the target directory didn't exist
  anymore.

  btrfs-progs v4.15.1
  See http://btrfs.wiki.kernel.org for more information.

  Performing full device TRIM /dev/loop0 (1.00GiB) ...
  Label:  (null)
  UUID:   b9297d7d-f8b6-469e-b3c5-64ac1bf1e3d8
  Node size:  16384
  Sector size:4096
  Filesystem size:1.00GiB
  Block group profiles:
Data: single8.00MiB
Metadata: DUP  51.19MiB
System:   DUP   8.00MiB
  SSD detected:   no
  Incompat features:  extref, skinny-metadata
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  1 1.00GiB  /dev/loop0

  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
  ERROR: unable to resolve -f
  Create a readonly snapshot of 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in 
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
  ERROR: unable to resolve -f
  btrfs-progs v4.15.1
  See http://btrfs.wiki.kernel.org for more information.

  Performing full device TRIM /dev/loop0 (1.00GiB) ...
  Label:  (null)
  UUID:   e6351943-c767-4339-b662-609e80dae55b
  Node size:  16384
  Sector size:4096
  Filesystem size:1.00GiB
  Block group profiles:
Data: single8.00MiB
Metadata: DUP  51.19MiB
System:   DUP   8.00MiB
  SSD detected:   no
  Incompat features:  extref, skinny-metadata
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  1 1.00GiB  /dev/loop0

  btrfs receive: too many arguments
  usage: btrfs receive [options] 
 btrfs receive --dump [options]

  Receive subvolumes from a stream

  Receives one or more subvolumes that were previously
  sent with btrfs send. The received subvolumes are stored
  into MOUNT.
  The receive will fail in case the receiving subvolume
  already exists. It will also fail in case a previously
  received subvolume has been changed after it was received.
  After receiving a subvolume, it is immediately set to
  read-only.

  -v   increase verbosity about performed actions
  -f FILE  read the stream from FILE instead of stdin
  -e   terminate after receiving an  marker in the 
stream.
   Without this option the receiver side terminates only in 
case
   of an error on end of file.
  -C|--chroot  confine the process to  using chroot
  -E|--max-errors NERR
   terminate as soon as NERR errors occur while
   stream processing commands from the stream.
   Default value is 1. A value of 0 means no limit.
  -m ROOTMOUNT the root mount point of the destination filesystem.
   If /proc is not accessible, use this to tell us where
   this file system is mounted.
  --dump   dump stream metadata, one line per operation,
   does not require the MOUNT parameter

  btrfs receive: too many arguments
  usage: btrfs receive [options] 
 btrfs receive --dump [options]

  Receive subvolumes from a stream

  Receives one or more subvolumes that were previously
  sent with btrfs send. The received subvolumes are stored
  into MOUNT.
  The receive will fail in case the receiving subvolume
  already exists. It will also fail in case a previously
  received subvolume has been changed after it was received.
  After receiving a subvolume, it is immediately set to
  read-only.

  -v   increase verbosity about performed