[Kernel-packages] [Bug 1761930] [NEW] System lockup immediatly after Unity launches on upgrade to 4.13.0-38-generic
Public bug reported: After upgrade to 4.13.0-38-generic my system (Acer S7 392) locks up after unity launches on startup. The mouse cursor is present but non responsive. ctrl-alt-delete/backspace/F1/F2... have no effect. Power off by holding power button is the only way to shutdown. Rebooting with 4.13.0-7-generic works as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jasper 2791 F pulseaudio /dev/snd/controlC0: jasper 2791 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Apr 7 17:49:22 2018 HibernationDevice: RESUME=UUID=26d3afe5-0e06-4669-8d23-c639f3ca7011 InstallationDate: Installed on 2015-04-14 (1089 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-30 (158 days ago) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.family: Sharkbay System dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug artful -- 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/1761930 Title: System lockup immediatly after Unity launches on upgrade to 4.13.0-38-generic Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to 4.13.0-38-generic my system (Acer S7 392) locks up after unity launches on startup. The mouse cursor is present but non responsive. ctrl-alt-delete/backspace/F1/F2... have no effect. Power off by holding power button is the only way to shutdown. Rebooting with 4.13.0-7-generic works as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jasper 2791 F pulseaudio /dev/snd/controlC0: jasper 2791 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Apr 7 17:49:22 2018 HibernationDevice: RESUME=UUID=26d3afe5-0e06-4669-8d23-c639f3ca7011 InstallationDate: Installed on 2015-04-14 (1089 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-30 (158 days ago) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.family: Sharkbay System dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761930/+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 1761930] Status changed to Confirmed
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/1761930 Title: System lockup immediatly after Unity launches on upgrade to 4.13.0-38-generic Status in linux package in Ubuntu: Confirmed Bug description: After upgrade to 4.13.0-38-generic my system (Acer S7 392) locks up after unity launches on startup. The mouse cursor is present but non responsive. ctrl-alt-delete/backspace/F1/F2... have no effect. Power off by holding power button is the only way to shutdown. Rebooting with 4.13.0-7-generic works as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jasper 2791 F pulseaudio /dev/snd/controlC0: jasper 2791 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Apr 7 17:49:22 2018 HibernationDevice: RESUME=UUID=26d3afe5-0e06-4669-8d23-c639f3ca7011 InstallationDate: Installed on 2015-04-14 (1089 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: Acer Aspire S7-392 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-37-generic.efi.signed root=UUID=57b63ba3-bc33-40b5-931f-8654d6c5cab4 ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-30 (158 days ago) dmi.bios.date: 05/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm2 dmi.board.vendor: Acer dmi.board.version: V2.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.12:bd05/20/2014:svnAcer:pnAspireS7-392:pvrV2.12:rvnAcer:rnStorm2:rvrV2.12:cvnAcer:ct10:cvrV2.12: dmi.product.family: Sharkbay System dmi.product.name: Aspire S7-392 dmi.product.version: V2.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761930/+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 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
4.8.0 works, 4.9.0 panics. I'll see about bisecting. -- 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/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel panics before initrd. Going back to xenial 4.4.0 works correctly. linux-image-4.15.0-13-generic: Installed: 4.15.0-13.14 Candidate: 4.15.0-13.14 Version table: *** 4.15.0-13.14 500 500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main ppc64el Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 16:11 seq crw-rw 1 root audio 116, 33 Apr 5 16:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: ppc64el 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: Date: Thu Apr 5 16:13:28 2018 HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221 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 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro ProcLoadAvg: 3.04 2.18 0.92 3/119 1643 ProcLocks: 1: POSIX ADVISORY WRITE 1225 00:12:470 0 EOF 2: POSIX ADVISORY WRITE 841 00:12:459 0 EOF 3: FLOCK ADVISORY WRITE 832 00:12:449 0 EOF 4: POSIX ADVISORY WRITE 802 00:12:432 0 EOF 5: POSIX ADVISORY WRITE 350 00:12:294 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/vda3 partition1408960 0 -1 ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP Mon Apr 2 16:08:02 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.4.0-119-generic N/A linux-backports-modules-4.4.0-119-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago) cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+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 1761751] Re: Black screen on 18.04 + AMD RX460
4.15.0-041500rc2-generic - Boots normally 4.15.0-041500rc3-generic - Black screen 4.15.0-041500rc4-generic - Not tested So something between rc2 and rc3 it is then... -- 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/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761751] Re: Black screen on 18.04 + AMD RX460
v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ - Boots normally v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ - Boots normally v4.15-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc5/ - Black screen v4.15-rc9: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9/ - Black screen v4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/ - Black screen v4.16-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/ - Not tested I'll try rc2, rc3 and rc4 next. -- 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/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761179] Re: linux-aws: 4.15.0-1003.3 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1761177 phase: Uploaded + kernel-phase:Promoted to proposed + kernel-phase-changed:Saturday, 07. April 2018 04:30 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1761177 - phase: Uploaded - kernel-phase:Promoted to proposed - kernel-phase-changed:Saturday, 07. April 2018 04:30 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1761179 Title: linux-aws: 4.15.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1761177 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761179/+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 1761183] Re: linux-kvm: 4.15.0-1004.4 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1761177 phase: Uploaded + kernel-phase:Promoted to proposed + kernel-phase-changed:Saturday, 07. April 2018 04:33 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1761177 - phase: Uploaded - kernel-phase:Promoted to proposed - kernel-phase-changed:Saturday, 07. April 2018 04:33 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1761183 Title: linux-kvm: 4.15.0-1004.4 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1761177 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761183/+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 1746482] Re: mount.cifs stopped working with protocol version>1 and sec=ntlm
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1746482 Title: mount.cifs stopped working with protocol version>1 and sec=ntlm Status in linux package in Ubuntu: Expired Bug description: On a Xenial installation after upgrading to the HWE 4.13.0-32-generic kernel it is not possible to use mount.cifs with -o vers=x.y different than 1.0. Steps to reproduce: 1. Setup a local Samba share with ntlm auth = yes. 2. Run: mount.cifs -o user=,sec=ntlm,vers=2.0 //localhost/theshare/ /mnt/theshare 3. This may be repeated for the following versions: 2.0, 2.1, 3.0. Expected result: The share gets mounted at /mnt/theshare. Actual result: The share is not mounted, this gets printed in the console: mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and in dmesg: [ 61.935687] CIFS VFS: Unable to select appropriate authentication method! [ 61.935689] CIFS VFS: Send error in SessSetup = -22 [ 61.935744] CIFS VFS: cifs_mount failed w/return code = -22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746482/+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 1745646] Re: Battery drains when laptop is off (shutdown)
4.12.0-041200-generic #201804061744 is good . 4.12.0-041200-generic #201804061744 -- 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/1745646 Title: Battery drains when laptop is off (shutdown) Status in Linux: Unknown Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in acpi source package in Artful: New Status in linux source package in Artful: In Progress Bug description: I am using hp AY008tx laptop , and many other laptop users (HP) are also facing the same issue . The problem don't occur when i install windows 10 . Now, only ubuntu is installed. i am using latest bios insyde20 rev 5.(latest) WOL disabled and no usb device connected checked my battery . it don't happen when i remove battery and plug it again after shutdown. tried laptop_mode_tools and tpl too ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 26 22:50:53 2018 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gopal 2391 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0a5c:216d Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.58 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1745646/+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 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
I can test earlier mainlines, but keep in mind that ppc64el is very slow on my home qemu setup (note "only" "very slow"; ppc64 is "amazingly slow", presumably due to endian swapping). Does Kernel have a POWER8 playground machine, if it comes to bisect compiling? -- 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/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel panics before initrd. Going back to xenial 4.4.0 works correctly. linux-image-4.15.0-13-generic: Installed: 4.15.0-13.14 Candidate: 4.15.0-13.14 Version table: *** 4.15.0-13.14 500 500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main ppc64el Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 16:11 seq crw-rw 1 root audio 116, 33 Apr 5 16:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: ppc64el 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: Date: Thu Apr 5 16:13:28 2018 HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221 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 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro ProcLoadAvg: 3.04 2.18 0.92 3/119 1643 ProcLocks: 1: POSIX ADVISORY WRITE 1225 00:12:470 0 EOF 2: POSIX ADVISORY WRITE 841 00:12:459 0 EOF 3: FLOCK ADVISORY WRITE 832 00:12:449 0 EOF 4: POSIX ADVISORY WRITE 802 00:12:432 0 EOF 5: POSIX ADVISORY WRITE 350 00:12:294 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/vda3 partition1408960 0 -1 ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP Mon Apr 2 16:08:02 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.4.0-119-generic N/A linux-backports-modules-4.4.0-119-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago) cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+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 1746340] Re: Samsung SSD corruption (fsck needed)
And it just happened again. It's common to happend again right after I rebooted ans fscked from a previous one. Then it calms down for some days -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdL
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Ok, the error just happened now in the main machine. Took much more days to happen. I picked my computer while it were sleeping but opened, and moved the mouse and saw a black screen with nothing on it. Then pressed power and soething appeared: /.../libvirt read only file system and then it turned off. Libvirt was running at the time so I think it was just an error saying that libvirt was trying to write to the disk. Don't know if it's related. -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseau
[Kernel-packages] [Bug 1761179] Re: linux-aws: 4.15.0-1003.3 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1761177 phase: Packaging + kernel-phase-changed:Saturday, 07. April 2018 02:30 UTC + kernel-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1761177 - phase: Packaging - kernel-phase-changed:Saturday, 07. April 2018 02:30 UTC - kernel-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1761179 Title: linux-aws: 4.15.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1761177 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761179/+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 1761183] Re: linux-kvm: 4.15.0-1004.4 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1761177 phase: Packaging + kernel-phase-changed:Saturday, 07. April 2018 02:33 UTC + kernel-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1761177 - phase: Packaging - kernel-phase-changed:Saturday, 07. April 2018 02:33 UTC - kernel-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1761183 Title: linux-kvm: 4.15.0-1004.4 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1761177 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761183/+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 1761757] Re: use correct path for tbtacl in udev rules
This bug was fixed in the package thunderbolt-tools - 0.9.3-2 --- thunderbolt-tools (0.9.3-2) unstable; urgency=medium * Set UDEV_BIN_DIR to /lib/udev (LP: #1761757) -- Colin King Fri, 6 Apr 2018 14:52:11 +0100 ** Changed in: thunderbolt-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1761757 Title: use correct path for tbtacl in udev rules Status in thunderbolt-tools package in Ubuntu: Fix Released Bug description: ./thunderbolt-tools_0.9.3-1_amd64/lib/udev/rules.d/tbtacl.rules: # Thunderbolt udev rules for ACL (device auto approval) SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="add" ATTR{authorized}=="0" RUN+="@UDEV_BIN_DIR@/tbtacl add $devpath" SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="change" ATTR{authorized}!="0" RUN+="@UDEV_BIN_DIR@/tbtacl change $devpath" should changed to fix up @UDEV_BIN_DIR@ to be: SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="add" ATTR{authorized}=="0" RUN+="/lib/udev/tbtacl add$devpath" SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="change" ATTR{authorized}!="0" RUN+="/lib/udev/tbtacl change $devpath" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1761757/+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 1754370] Re: Sync makedumpfile 1:1.6.3-2 (main) from Debian unstable (main)
This bug was fixed in the package makedumpfile - 1:1.6.3-2 Sponsored for Thadeu Lima de Souza Cascardo (cascardo) --- makedumpfile (1:1.6.3-2) unstable; urgency=medium * Add support for SPARSEMEM_EXTREME mem_section as a pointer. (LP: #1750021) * Add an autopkgtest that test that a crash produces a compressed dump file. * Create initrd for previously installed kernels. (LP: #1751329) -- Thadeu Lima de Souza Cascardo Mon, 05 Mar 2018 09:28:55 -0300 ** Changed in: makedumpfile (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1754370 Title: Sync makedumpfile 1:1.6.3-2 (main) from Debian unstable (main) Status in makedumpfile package in Ubuntu: Fix Released Bug description: Please sync makedumpfile 1:1.6.3-2 (main) from Debian unstable (main) Changelog entries since current bionic version 1:1.6.3-1: makedumpfile (1:1.6.3-2) unstable; urgency=medium * Add support for SPARSEMEM_EXTREME mem_section as a pointer. (LP: #1750021) * Add an autopkgtest that test that a crash produces a compressed dump file. * Create initrd for previously installed kernels. (LP: #1751329) -- Thadeu Lima de Souza Cascardo Mon, 05 Mar 2018 09:28:55 -0300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1754370/+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 1751329] Re: kdump-tools won't load until after network is online
** Also affects: makedumpfile (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Bionic) Importance: Low Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Confirmed ** No longer affects: makedumpfile (Ubuntu Bionic) ** Changed in: makedumpfile (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: makedumpfile (Ubuntu Xenial) Status: New => Triaged ** Changed in: makedumpfile (Ubuntu Artful) Importance: Undecided => Low ** Changed in: makedumpfile (Ubuntu Artful) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1751329 Title: kdump-tools won't load until after network is online Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Xenial: Triaged Status in makedumpfile source package in Artful: Triaged Bug description: This, at least, causes kdump-tools to load only after some timeout. It could be loaded much earlier. kdump-tools only requires the network to be online when it's configured to dump to ssh or nfs, and only when dumping, not when loading. We should have three services/units here: 1) the loading service, does not require network; 2) the dumping service, that works for local dumps, does not require network; 3) the dumping service, that works remotely, requires network. Now, as per LP#1681909, maybe we should not require network-online, but use some other way to verify that the host where we want to dump is online, given a certain (configured) timeout. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1751329/+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 1761757] Re: use correct path for tbtacl in udev rules
I think the real fix is easier... This still has two copies of the file: sarnold@hunt:/tmp/bolt$ ar x thunderbolt-tools_0.9.3-2_amd64.deb sarnold@hunt:/tmp/bolt$ tar tf data.tar.xz ./ ./lib/ ./lib/udev/ ./lib/udev/rules.d/ ./lib/udev/rules.d/60-tbtacl.rules ./lib/udev/rules.d/60-tbtxdomain.rules ./lib/udev/rules.d/tbtacl.rules ./lib/udev/tbtacl ./lib/udev/tbtacl-write ./lib/udev/tbtxdomain ./usr/ ./usr/bin/ ./usr/bin/tbtadm ./usr/share/ ./usr/share/bash-completion/ ./usr/share/bash-completion/completions/ ./usr/share/bash-completion/completions/tbtadm ./usr/share/doc/ ./usr/share/doc/thunderbolt-tools/ ./usr/share/doc/thunderbolt-tools/changelog.Debian.gz ./usr/share/doc/thunderbolt-tools/copyright ./usr/share/doc/thunderbolt-user-space/ ./usr/share/doc/thunderbolt-user-space/copyright ./usr/share/man/ ./usr/share/man/man1/ ./usr/share/man/man1/tbtadm.1.gz sarnold@hunt:/tmp/bolt$ tar xf data.tar.xz sarnold@hunt:/tmp/bolt$ cat lib/udev/rules.d/*tbtacl* # Thunderbolt udev rules for ACL (device auto approval) SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="add" ATTR{authorized}=="0" RUN+="/lib/udev/tbtacl add$devpath" SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="change" ATTR{authorized}!="0" RUN+="/lib/udev/tbtacl change $devpath" # Thunderbolt udev rules for ACL (device auto approval) SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="add" ATTR{authorized}=="0" RUN+="/lib/udev/tbtacl add$devpath" SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="change" ATTR{authorized}!="0" RUN+="/lib/udev/tbtacl change $devpath" I think the better solution is to delete this line from debian/rules: cp tbtacl/tbtacl.rules.in tbtacl/tbtacl.rules Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1761757 Title: use correct path for tbtacl in udev rules Status in thunderbolt-tools package in Ubuntu: Fix Released Bug description: ./thunderbolt-tools_0.9.3-1_amd64/lib/udev/rules.d/tbtacl.rules: # Thunderbolt udev rules for ACL (device auto approval) SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="add" ATTR{authorized}=="0" RUN+="@UDEV_BIN_DIR@/tbtacl add $devpath" SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="change" ATTR{authorized}!="0" RUN+="@UDEV_BIN_DIR@/tbtacl change $devpath" should changed to fix up @UDEV_BIN_DIR@ to be: SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="add" ATTR{authorized}=="0" RUN+="/lib/udev/tbtacl add$devpath" SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="change" ATTR{authorized}!="0" RUN+="/lib/udev/tbtacl change $devpath" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1761757/+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 1761889] Re: Sync thunderbolt-tools 0.9.3-2 (universe) from Debian unstable (main)
https://launchpad.net/ubuntu/+source/thunderbolt-tools/0.9.3-2 ** Changed in: thunderbolt-tools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1761889 Title: Sync thunderbolt-tools 0.9.3-2 (universe) from Debian unstable (main) Status in thunderbolt-tools package in Ubuntu: Fix Released Bug description: Please sync thunderbolt-tools 0.9.3-2 (universe) from Debian unstable (main) Changelog entries since current bionic version 0.9.3-1: thunderbolt-tools (0.9.3-2) unstable; urgency=medium * Set UDEV_BIN_DIR to /lib/udev (LP: #1761757) -- Colin King Fri, 6 Apr 2018 14:52:11 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1761889/+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 1748157] Re: [MIR] thunderbolt-tools
I reviewed thunderbolt-tools version 0.9.3-1 as checked into bionic. This shouldn't be considered a full security audit but rather a quick gauge of maintainability. - No CVEs in our database - thunderbolt-tools provides a simple interface to authorize thunderbolt devices that are being added to a computer, since thunderbolt devices have immense control over the safety of the system - Build-Depends: debhelper, libboost-dev, libboost-filesystem-dev, libboost-program-options-dev, cmake, pkg-config, udev, txt2tags - Does not daemonize; udev hook scripts are used - No pre/post inst/rm scripts - No initscript / systemd unit files - No DBus services - No setuid files - /usr/bin/tbtadm added to the PATH - No sudo fragments - udev rules -- appear to be configured for works-by-default behaviour, some examples on how to configure for authorization-required would be nice - No tests, a bit unfortunate - No cronjobs - Clean build logs - No subprocesses spawned - C++ RAII memory management - File IO done via RAII-C++ classes, not exactly obvious when it happens - Some C++ exceptions, some C++ iostream - No environment variable use - The only privileged operations are file writes - No cryptography - No network connections - No privileged portions of code - No temporary files - No WebKit - No JavaScript - No PolicyKit - Clean cppcheck thunderbolt-tools is short and sweet authorization tool. It's written in modern C++, looks careful, and shouldn't be an undue maintenance burden. It uses std::random_device for security uses -- I believe this is safe but direct use of getrandom(2) would not have questions about underlying C++ library implementation choices. Security team ACK for promoting thunderbolt-tools to main once the extra udev configuration file is sorted out. Thanks ** Changed in: thunderbolt-tools (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rul
[Kernel-packages] [Bug 1761439] Re: linux-aws: 4.4.0-1017.17 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Saturday, 07. April 2018 00:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Saturday, 07. April 2018 00:01 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1761439 Title: linux-aws: 4.4.0-1017.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761439/+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 1747661] Re: ecryptfs complains about "Error encrypting page" on 4.13 Artful
This is present in 4.13.0-37-generic on 16.04LTS too: [280691.914572] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-5] [280691.914581] ecryptfs_writepage: Error encrypting page (upper index [0x0004]) [280722.634521] ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-5] [280722.634529] ecryptfs_writepage: Error encrypting page (upper index [0x0005]) -- 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/1747661 Title: ecryptfs complains about "Error encrypting page" on 4.13 Artful Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This issue was spotted on my computer for work (CID 201408-15386), installed with disk encrypted The following error message could be found in syslog ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-4] ecryptfs_writepage: Error encrypting page (upper index [0x]) Found this issue because the system is crashing frequently today, but I think this is not the cause of the crash, as the error can be found on last Thursday and Friday but the system is stable. Check through my archived syslog, this issue was first spotted on Jan. 30 19:00, 4.13.0-32 was install earlier that day in the morning. For older log before Jan.30 (Jan.25 / 26) with 4.13.0-31, there is no such error message in the syslog. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-32-generic 4.13.0-32.35 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sam1530 F pulseaudio /dev/snd/controlC0: sam1530 F pulseaudio CurrentDesktop: GNOME Date: Tue Feb 6 19:54:10 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=3a922472-e01e-42fa-a61d-7d7f645e3672 InstallationDate: Installed on 2017-07-12 (209 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Latitude 7250 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2018-01-24 (13 days ago) dmi.bios.date: 12/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0N248W dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2016:svnDellInc.:pnLatitude7250:pvr:rvnDellInc.:rn0N248W:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 7250 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747661/+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 1761445] Re: linux-kvm: 4.4.0-1021.26 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 06. April 2018 23:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 06. April 2018 23:01 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1761445 Title: linux-kvm: 4.4.0-1021.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761445/+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 1761889] [NEW] Sync thunderbolt-tools 0.9.3-2 (universe) from Debian unstable (main)
Public bug reported: Please sync thunderbolt-tools 0.9.3-2 (universe) from Debian unstable (main) Changelog entries since current bionic version 0.9.3-1: thunderbolt-tools (0.9.3-2) unstable; urgency=medium * Set UDEV_BIN_DIR to /lib/udev (LP: #1761757) -- Colin King Fri, 6 Apr 2018 14:52:11 +0100 ** Affects: thunderbolt-tools (Ubuntu) Importance: Wishlist Status: New ** Changed in: thunderbolt-tools (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1761889 Title: Sync thunderbolt-tools 0.9.3-2 (universe) from Debian unstable (main) Status in thunderbolt-tools package in Ubuntu: New Bug description: Please sync thunderbolt-tools 0.9.3-2 (universe) from Debian unstable (main) Changelog entries since current bionic version 0.9.3-1: thunderbolt-tools (0.9.3-2) unstable; urgency=medium * Set UDEV_BIN_DIR to /lib/udev (LP: #1761757) -- Colin King Fri, 6 Apr 2018 14:52:11 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1761889/+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 1760876] Re: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel
This also affects linux-azure and linux-azure-edge. -- 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/1760876 Title: DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel Status in linux package in Ubuntu: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Was installing the kernel 4.15.0-14-generic when that crash happened. Now libelf-dev is requested and need to be added as a dependency. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fwts-efi-runtime-dkms 18.03.00-0ubuntu1 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: r8168 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.15.0-14-generic Date: Tue Apr 3 15:39:06 2018 PackageVersion: 18.03.00-0ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: fwts Title: fwts-efi-runtime-dkms 18.03.00-0ubuntu1: fwts-efi-runtime-dkms kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760876/+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 1761870] Status changed to Confirmed
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/1761870 Title: BUG: scheduling while atomic: FarmTogether.x8/19291/0x0002 Status in linux package in Ubuntu: Confirmed Bug description: - ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-lowlatency 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10 Uname: Linux 4.15.0-13-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Fri Apr 6 22:59:16 2018 Failure: oops HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb InstallationDate: Installed on 2018-03-02 (35 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-13-lowlatency root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: scheduling while atomic: FarmTogether.x8/19291/0x0002 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.50:bd09/25/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761870/+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 1761439] Re: linux-aws: 4.4.0-1017.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1761439 Title: linux-aws: 4.4.0-1017.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761439/+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 1761443] Re: linux-aws: 4.4.0-1055.64 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 06. April 2018 21:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 06. April 2018 21:01 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1761443 Title: linux-aws: 4.4.0-1055.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761443/+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 1761870] [NEW] BUG: scheduling while atomic: FarmTogether.x8/19291/0x00000002
Public bug reported: - ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-lowlatency 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10 Uname: Linux 4.15.0-13-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Fri Apr 6 22:59:16 2018 Failure: oops HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb InstallationDate: Installed on 2018-03-02 (35 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-13-lowlatency root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: scheduling while atomic: FarmTogether.x8/19291/0x0002 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.50:bd09/25/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops bionic kernel-oops -- 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/1761870 Title: BUG: scheduling while atomic: FarmTogether.x8/19291/0x0002 Status in linux package in Ubuntu: New Bug description: - ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-lowlatency 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10 Uname: Linux 4.15.0-13-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Fri Apr 6 22:59:16 2018 Failure: oops HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb InstallationDate: Installed on 2018-03-02 (35 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) MachineType: Micro-Star International Co., Ltd MS-7A32 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-13-lowlatency root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A SourcePackage: linux Title: BUG: scheduling while atomic: FarmTogether.x8/19291/0x0002 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.50:bd09/25/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761870/+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 1761825] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1761825/+attachment/5104720/+files/ProcEnviron.txt -- 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/1761825 Title: amdgpu.dc fails on AMD (Kaveri) A10-7300 Status in linux package in Ubuntu: Incomplete Bug description: Booting kernel 4.16 ( BOOT_IMAGE=/vmlinuz-4.16.0-041600-generic ) with external monitor attached to VGA port of Lenovo Ideapad Z50-75 (AMD Kaveri A10-7300) results in blank external display when amdgpu.ci_support is forced (i.e. radeon disabled). key dmesg messages are: [1.897177] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.897266] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.897380] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [1.897489] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:6! type 0 expected 3 Kernel boot options are: amdgpu.cik_support=1 radeon.cik_support=0 If I boot the same kernel with the following options: amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.dc=0 The VGA attached display works. Attached in the tar are: version.log - output of cat /proc/version lspci-vnvn.log - output of sudo lscpi -vnvn dmesg_amdgpu.dc-(default-one) - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc left to deafult dmesg_amdgpu.dc-0 - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc disabled --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-09-05 (213 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Failed to search journal ACL: Operation not supported No journal files were opened due to insufficient permissions. Package: linux (not installed) Tags: xenial Uname: Linux 4.16.0-041600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kismet libvirtd lpadmin plugdev sambashare scanner sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761825/+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 1761825] Re: amdgpu.dc fails on AMD (Kaveri) A10-7300
apport information ** Tags added: apport-collected xenial ** Description changed: Booting kernel 4.16 ( BOOT_IMAGE=/vmlinuz-4.16.0-041600-generic ) with external monitor attached to VGA port of Lenovo Ideapad Z50-75 (AMD Kaveri A10-7300) results in blank external display when amdgpu.ci_support is forced (i.e. radeon disabled). key dmesg messages are: [1.897177] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.897266] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.897380] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [1.897489] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:6! type 0 expected 3 Kernel boot options are: amdgpu.cik_support=1 radeon.cik_support=0 If I boot the same kernel with the following options: amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.dc=0 The VGA attached display works. Attached in the tar are: version.log - output of cat /proc/version lspci-vnvn.log - output of sudo lscpi -vnvn dmesg_amdgpu.dc-(default-one) - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc left to deafult dmesg_amdgpu.dc-0 - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc disabled + --- + ApportVersion: 2.20.1-0ubuntu2.15 + Architecture: amd64 + CurrentDesktop: LXDE + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2017-09-05 (213 days ago) + InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + JournalErrors: + Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Failed to search journal ACL: Operation not supported + No journal files were opened due to insufficient permissions. + Package: linux (not installed) + Tags: xenial + Uname: Linux 4.16.0-041600-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip kismet libvirtd lpadmin plugdev sambashare scanner sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1761825/+attachment/5104719/+files/ProcCpuinfoMinimal.txt -- 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/1761825 Title: amdgpu.dc fails on AMD (Kaveri) A10-7300 Status in linux package in Ubuntu: Incomplete Bug description: Booting kernel 4.16 ( BOOT_IMAGE=/vmlinuz-4.16.0-041600-generic ) with external monitor attached to VGA port of Lenovo Ideapad Z50-75 (AMD Kaveri A10-7300) results in blank external display when amdgpu.ci_support is forced (i.e. radeon disabled). key dmesg messages are: [1.897177] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.897266] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.897380] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [1.897489] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:6! type 0 expected 3 Kernel boot options are: amdgpu.cik_support=1 radeon.cik_support=0 If I boot the same kernel with the following options: amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.dc=0 The VGA attached display works. Attached in the tar are: version.log - output of cat /proc/version lspci-vnvn.log - output of sudo lscpi -vnvn dmesg_amdgpu.dc-(default-one) - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc left to deafult dmesg_amdgpu.dc-0 - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc disabled --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-09-05 (213 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Failed to search journal ACL: Operation not supported No journal files were opened due to insufficient permissions. Package: linux (not installed) Tags: xenial Uname: Linux 4.16.0-041600-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kismet libvirtd lpadmin
[Kernel-packages] [Bug 1761445] Re: linux-kvm: 4.4.0-1021.26 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1761445 Title: linux-kvm: 4.4.0-1021.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761445/+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 1761439] Re: linux-aws: 4.4.0-1017.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1761438 phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1761439 Title: linux-aws: 4.4.0-1017.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761439/+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 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy
How do I do this ? I booted a live stick but libinput-tools isn't there and there is no way to run tests the good old way when disk-creator allowed to have a user partition or install software in the live session. How can I run these tests please without breaking my Trusty ? -- 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/1746740 Title: XPS13 L322X Bionic (daily dev) touchpad laggy Status in libinput: Incomplete Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Also, all function keys work as expected, even F6 (keyboard 3-states backlight), but OSD picture for this last feature randomly auto- triggers. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1876 F pulseaudio CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 1 14:05:22 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201) MachineType: Dell Inc. XPS L322X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1746740/+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 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy
Silvio, I gave a try with latest daily Bionic which comes with libinput10 1.10.3 and the result is exactly the way you describe. My "laggy" word is not accurate. -- 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/1746740 Title: XPS13 L322X Bionic (daily dev) touchpad laggy Status in libinput: Incomplete Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Also, all function keys work as expected, even F6 (keyboard 3-states backlight), but OSD picture for this last feature randomly auto- triggers. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1876 F pulseaudio CasperVersion: 1.388 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 1 14:05:22 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201) MachineType: Dell Inc. XPS L322X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.170 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1746740/+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 1761593] Re: Uninstall left nouveau blacklisted
** Also affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1761593 Title: Uninstall left nouveau blacklisted Status in nvidia-settings package in Ubuntu: New Status in software-properties package in Ubuntu: Confirmed Bug description: Following a successful install and subsequent use of nvidia-340 - uninstallation of nvidia via Additional Drivers led to a reboot to a desktop at 640x480 px. Investigation found an nvidia created file left on the system blacklisting nouveau, deleted file and rebooted to normal desktop. Didn't think about ubuntu-reporting this - can try and replicate and apport-collect if it's of any use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1761593/+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 1761856] [NEW] kata-containers: netlink protocol not supported
Public bug reported: Kata container agent is not able to configure the network inside the container level=error msg="update interface request failed" arch=amd64 error="rpc error: code = Unknown desc = protocol not supported" interface- requested="device:\"eth0\" name:\"eth0\" IPAddresses: mtu:1500 hwAddr:\"02:42:ac:11:00:02\" " name=kata-runtime pid=29665 resulting- interface="" source=virtcontainers subsystem=kata_agent ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1761856 Title: kata-containers: netlink protocol not supported Status in linux-kvm package in Ubuntu: New Bug description: Kata container agent is not able to configure the network inside the container level=error msg="update interface request failed" arch=amd64 error="rpc error: code = Unknown desc = protocol not supported" interface-requested="device:\"eth0\" name:\"eth0\" IPAddresses: mtu:1500 hwAddr:\"02:42:ac:11:00:02\" " name=kata-runtime pid=29665 resulting- interface="" source=virtcontainers subsystem=kata_agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1761856/+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 1761438] Re: linux: 4.4.0-120.144 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1761438 Title: linux: 4.4.0-120.144 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1761439 (linux-aws), bug 1761441 (linux-lts-xenial) derivatives: bug 1761443 (linux-aws), bug 1761444 (linux-euclid), bug 1761445 (linux-kvm), bug 1761446 (linux-raspi2), bug 1761448 (linux-snapdragon) -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761438/+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 1761456] Re: linux: 4.13.0-39.44 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1761456 Title: linux: 4.13.0-39.44 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem) derivatives: bug 1761458 (linux-raspi2) -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761456/+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 1761430] Re: linux: 3.13.0-145.194 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- 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/1761430 Title: linux: 3.13.0-145.194 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1761433 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761430/+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 1761854] [NEW] kata-containers: Cannot open root device "pmem0p1"
Public bug reported: Cannot run kata containers on Ubuntu linux KVM level=info msg="VFS: Cannot open root device \"pmem0p1\" or unknown-block(0,0): error -6\n" name=kata-proxy pid=17025 source=agent level=info msg="Please append a correct \"root=\" boot option; here are the available partitions:\n" name=kata-proxy pid=17025 source=agent level=info msg="01004096 ram0 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01014096 ram1 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01024096 ram2 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01034096 ram3 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01044096 ram4 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01054096 ram5 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01064096 ram6 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01074096 ram7 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01084096 ram8 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01094096 ram9 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="010a4096 ram10 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="010b4096 ram11 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="010c4096 ram12 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="010d4096 ram13 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="010e4096 ram14 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="010f4096 ram15 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)\n" name=kata-proxy pid=17025 source=agent level=info msg="Kernel Offset: 0x3c40 from 0x8100 (relocation range: 0x8000-0xbfff)\n" name=kata-proxy pid=17025 source=agent level=info msg="Rebooting in 1 seconds..\n" name=kata-proxy pid=17025 source=agent ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1761854 Title: kata-containers: Cannot open root device "pmem0p1" Status in linux-kvm package in Ubuntu: New Bug description: Cannot run kata containers on Ubuntu linux KVM level=info msg="VFS: Cannot open root device \"pmem0p1\" or unknown-block(0,0): error -6\n" name=kata-proxy pid=17025 source=agent level=info msg="Please append a correct \"root=\" boot option; here are the available partitions:\n" name=kata-proxy pid=17025 source=agent level=info msg="01004096 ram0 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01014096 ram1 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01024096 ram2 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01034096 ram3 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01044096 ram4 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01054096 ram5 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" name=kata-proxy pid=17025 source=agent level=info msg="01064096 ram6 \n" name=kata-proxy pid=17025 source=agent level=info msg=" (driver?)\n" n
[Kernel-packages] [Bug 1761729] Re: Ubuntu 18.04 Machine crashed while running ltp.
** Changed in: ubuntu-power-systems 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/1761729 Title: Ubuntu 18.04 Machine crashed while running ltp. Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: ---Problem Description--- Ubuntu 18.04 [ Briggs P8 ]: Machine crashed while running ltp. ---Environment-- Kernel Build: Ubuntu 18.04 System Name : ltc-briggs2 Model/Type : P8 Platform: BML ---Uname output--- root@ltc-briggs2:~# uname -a Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Steps to reproduce-- $ git clone https://github.com/linux-test-project/ltp.git $ cd ltp $ make autotools $ ./configure $ make $ make install ltp = root@ltc-briggs2:~# root@ltc-briggs2:~# [10781.098337] LTP: starting fs_inod01 (fs_inod $TMPDIR 10 10 10) [10782.837910] LTP: starting linker01 (linktest.sh 1000 1000) [10784.504474] LTP: starting openfile01 (openfile -f10 -t10) [10784.534953] LTP: starting inode01 [10784.550767] LTP: starting inode02 [10784.739104] LTP: starting stream01 [10784.740840] LTP: starting stream02 [10784.742487] LTP: starting stream03 [10784.744532] LTP: starting stream04 [10784.746087] LTP: starting stream05 [10784.747722] LTP: starting ftest01 [10785.142054] LTP: starting ftest02 [10785.158852] LTP: starting ftest03 [10785.404760] LTP: starting ftest04 [10785.527197] LTP: starting ftest05 [10785.937164] LTP: starting ftest06 [10785.958360] LTP: starting ftest07 [10786.463382] LTP: starting ftest08 [10786.592998] LTP: starting lftest01 (lftest 100) [10786.672707] LTP: starting writetest01 (writetest) [10786.774292] LTP: starting fs_di (fs_di -d $TMPDIR) [10792.973510] LTP: starting proc01 (proc01 -m 128) [10793.865686] ICMPv6: process `proc01' is using deprecated sysctl (syscall) net.ipv6.neigh.default.base_reachable_time - use net.ipv6.neigh.default.base_reachable_time_ms instead [10795.785593] LTP: starting read_all_dev (read_all -d /dev -e '/dev/watchdog?(0)' -q -r 10) [10795.895774] NET: Registered protocol family 40 [10795.918763] Bluetooth: Core ver 2.22 [10795.918866] NET: Registered protocol family 31 [10795.918909] Bluetooth: HCI device and connection manager initialized [10795.918955] Bluetooth: HCI socket layer initialized [10795.918991] Bluetooth: L2CAP socket layer initialized [10795.919032] Bluetooth: SCO socket layer initialized [10798.374850] usercopy: kernel memory exposure attempt detected from 29431ea4 () (1023 bytes) [10798.374952] [ cut here ] [10798.374988] kernel BUG at /build/linux-2BXDjB/linux-4.15.0/mm/usercopy.c:72! [10798.375041] Oops: Exception in kernel mode, sig: 5 [#1] [10798.375080] LE SMP NR_CPUS=2048 [10871.343999650,5] OPAL: Switch to big-endian OS NUMA PowerNV [10798.375117] [10876.190849323,5] OPAL: Switch to little-endian OS Modules linked in: hci_vhci bluetooth ecdh_generic vhost_vsock cuse vmw_vsock_virtio_transport_common userio vsock uhid vhost_net vhost tap snd_seq snd_seq_device snd_timer snd soundcore binfmt_misc sctp quota_v2 quota_tree nls_iso8859_1 ntfs xfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter kvm_hv kvm idt_89hpesx vmx_crypto ofpart cmdlinepart ipmi_powernv powernv_flash ipmi_devintf mtd ipmi_msghandler ibmpowernv opal_prd at24 powernv_rng joydev input_leds mac_hid uio_pdrv_genirq uio sch_fq_codel nfsd ib_iser rdma_cm auth_rpcgss iw_cm nfs_acl lockd ib_cm grace iscsi_tcp [10798.375636] libiscsi_tcp libiscsi sunrpc scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure scsi_transport_sas hid_generic usbhid hid ib_core qla2xxx ast i2c_algo_bit ttm mlx5_core drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme_fc crct10dif_vpmsum nvme_fabrics ahci mlxfw crc32c_vpmsum i40e drm devlink scsi_transport_fc megaraid_sas libahci [10798.375961] CPU: 87 PID: 4085 Comm: read_all Not tainted 4.15.0-13-generic #14-Ubuntu [10798.376013] NIP: c03c76f0 LR: c03c76ec CTR: 300378e8 [10798.376068] REGS: c076c63aba00 TRAP: 0700 Not tainted (4.15.0-13-generic) [10798.376120] MSR: 90029033 CR: 2800 XER: 2000 [10798.376176] CFAR: c018cce4 SOFTE: 1 [10798.376176] GPR00: c0
[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU
Thanks @walterzjunior. Those kernel versions linked in comment #50 are proceeding towards release regardless, but additional test results from other people affected by this bug would be very much appreciated. -- 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/1746806 Title: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU Status in cloud-images: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Status in linux-aws source package in Xenial: In Progress Bug description: After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5 EC2 instances after starting the service and CPU goes to 100%. We do not experience this issue with t2 or c4 instance types and we do not see this issue on any instance types using Ubuntu Cloud images from 20180109 or before. I have verified that this is kernel related as I booted an image that we created using the Ubuntu cloud image from 20180109 which works fine on a c5. I then did a "apt update && apt install --only-upgrade linux-aws && systemctl disable sssd", rebooted the server, verified I was on the new kernel and started sssd with "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU usage for that instance went to 100%. I haven't been able to find much in the syslog, kern.log, journalctl logs, etc. The only thing I have been able to find is that when this happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in the syslog and sssd log files. I have attached several log files and the output of a "apport-bug /usr/sbin/sssd". Let me know if you need anything else to help track this down. Thanks, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1746806/+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 1761831] Re: ASUS B150M Gaming hibernate/resume failure
Please, is it possible to check / fix Hibernate / Resume from Hibernate ? I have only Desktop PCs and Hibernate is one of the main features of an OS I use. Sleep works but is not an option for Desktop PCs that are offline (down) for more than 14 hours a day. Thank you. See also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759860 Additional information: Acer X3-710 PC - Ubuntu MATE 17.10 and kernel 4.15.x / 4.16.x - Hibernate / Resume from Hibernate works as expected Acer X3-710 PC - Ubuntu MATE 18.04 Beta 2 fresh install or upgrade from Ubuntu MATE 17.10 and kernel 4.15.x / 4.16.x - Hibernate / Resume from Hibernate does NOT WORK -- 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/1761831 Title: ASUS B150M Gaming hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate / Resume from Hibernate - does not work ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mihai 1718 F pulseaudio /dev/snd/controlC0: mihai 1718 F pulseaudio Date: Fri Apr 6 20:19:49 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:0601 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03 InstallationDate: Installed on 2018-04-06 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InterpreterPath: /usr/bin/python3.6 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [System manufacturer System Product Name] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: Default string dmi.board.name: B150M PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761831/+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 1761831] Re: ASUS B150M Gaming hibernate/resume failure
Installed kernel 4.16 from here http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.16/ Hibernate / Resume from Hibernate does not work. -- 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/1761831 Title: ASUS B150M Gaming hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate / Resume from Hibernate - does not work ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mihai 1718 F pulseaudio /dev/snd/controlC0: mihai 1718 F pulseaudio Date: Fri Apr 6 20:19:49 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:0601 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03 InstallationDate: Installed on 2018-04-06 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InterpreterPath: /usr/bin/python3.6 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [System manufacturer System Product Name] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: Default string dmi.board.name: B150M PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761831/+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 1745646] Re: Battery drains when laptop is off (shutdown)
4.12.0-041200-generic #201804061744 Before shutdown : http://paste.ubuntu.com/p/5fKrt9RXB9/ -- 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/1745646 Title: Battery drains when laptop is off (shutdown) Status in Linux: Unknown Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in acpi source package in Artful: New Status in linux source package in Artful: In Progress Bug description: I am using hp AY008tx laptop , and many other laptop users (HP) are also facing the same issue . The problem don't occur when i install windows 10 . Now, only ubuntu is installed. i am using latest bios insyde20 rev 5.(latest) WOL disabled and no usb device connected checked my battery . it don't happen when i remove battery and plug it again after shutdown. tried laptop_mode_tools and tpl too ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 26 22:50:53 2018 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gopal 2391 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0a5c:216d Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.58 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1745646/+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 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
collecting logs with mainline kernel. ** Summary changed: - Rebooting bionic fails with hardware error + Rebooting bionic fails with hardware error on ProLiant DL360 Gen9 ** Description changed: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd09/13/2016:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 6 17:53
[Kernel-packages] [Bug 1761796] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104521/+files/ProcCpuinfoMinimal.txt ** Description changed: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd09/13/2016:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 6 17:53 seq crw-rw
[Kernel-packages] [Bug 1761796] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104523/+files/ProcCpuinfoMinimal.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi
[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)
I've been cutting and pasting my comments and didn't notice I'm repeating the string for uname -a. Just ignore that sentence. -- 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/1745646 Title: Battery drains when laptop is off (shutdown) Status in Linux: Unknown Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in acpi source package in Artful: New Status in linux source package in Artful: In Progress Bug description: I am using hp AY008tx laptop , and many other laptop users (HP) are also facing the same issue . The problem don't occur when i install windows 10 . Now, only ubuntu is installed. i am using latest bios insyde20 rev 5.(latest) WOL disabled and no usb device connected checked my battery . it don't happen when i remove battery and plug it again after shutdown. tried laptop_mode_tools and tpl too ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 26 22:50:53 2018 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gopal 2391 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0a5c:216d Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.58 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1745646/+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 1745646] Re: Battery drains when laptop is off (shutdown)
I built the next test kernel, up to the following commit: d62eb5edf6643ede7e48b4d03ba972c0e8949acc The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1745646 When you run uname -a this time, the kernel should have this string in the name: 201804041858 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- 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/1745646 Title: Battery drains when laptop is off (shutdown) Status in Linux: Unknown Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in acpi source package in Artful: New Status in linux source package in Artful: In Progress Bug description: I am using hp AY008tx laptop , and many other laptop users (HP) are also facing the same issue . The problem don't occur when i install windows 10 . Now, only ubuntu is installed. i am using latest bios insyde20 rev 5.(latest) WOL disabled and no usb device connected checked my battery . it don't happen when i remove battery and plug it again after shutdown. tried laptop_mode_tools and tpl too ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 26 22:50:53 2018 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gopal 2391 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0a5c:216d Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.58 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1745646/+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 1761439] Re: linux-aws: 4.4.0-1017.17 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1761438 phase: Packaging + kernel-stable-phase-changed:Friday, 06. April 2018 18:31 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1761438 - phase: Packaging - kernel-stable-phase-changed:Friday, 06. April 2018 18:31 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1761439 Title: linux-aws: 4.4.0-1017.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1761438 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761439/+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 1761825] Missing required logs.
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 1761825 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/1761825 Title: amdgpu.dc fails on AMD (Kaveri) A10-7300 Status in linux package in Ubuntu: Incomplete Bug description: Booting kernel 4.16 ( BOOT_IMAGE=/vmlinuz-4.16.0-041600-generic ) with external monitor attached to VGA port of Lenovo Ideapad Z50-75 (AMD Kaveri A10-7300) results in blank external display when amdgpu.ci_support is forced (i.e. radeon disabled). key dmesg messages are: [1.897177] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.897266] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.897380] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [1.897489] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:6! type 0 expected 3 Kernel boot options are: amdgpu.cik_support=1 radeon.cik_support=0 If I boot the same kernel with the following options: amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.dc=0 The VGA attached display works. Attached in the tar are: version.log - output of cat /proc/version lspci-vnvn.log - output of sudo lscpi -vnvn dmesg_amdgpu.dc-(default-one) - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc left to deafult dmesg_amdgpu.dc-0 - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761825/+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 1761831] Status changed to Confirmed
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/1761831 Title: ASUS B150M Gaming hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate / Resume from Hibernate - does not work ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mihai 1718 F pulseaudio /dev/snd/controlC0: mihai 1718 F pulseaudio Date: Fri Apr 6 20:19:49 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:0601 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03 InstallationDate: Installed on 2018-04-06 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InterpreterPath: /usr/bin/python3.6 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [System manufacturer System Product Name] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: Default string dmi.board.name: B150M PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761831/+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 1761831] Re: ASUS B150M Gaming hibernate/resume failure
** Tags removed: need-duplicate-check -- 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/1761831 Title: ASUS B150M Gaming hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate / Resume from Hibernate - does not work ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mihai 1718 F pulseaudio /dev/snd/controlC0: mihai 1718 F pulseaudio Date: Fri Apr 6 20:19:49 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:0601 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03 InstallationDate: Installed on 2018-04-06 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InterpreterPath: /usr/bin/python3.6 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [System manufacturer System Product Name] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: Default string dmi.board.name: B150M PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761831/+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 1761796] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104427/+files/UdevDb.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:b
[Kernel-packages] [Bug 1761796] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104424/+files/ProcCpuinfoMinimal.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP d
[Kernel-packages] [Bug 1761729] Re: Ubuntu 18.04 Machine crashed while running ltp.
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16 ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Kernel Team (canonical-kernel-team) ** Also affects: linux (Ubuntu Bionic) Importance: Critical Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Incomplete ** Changed in: linux (Ubuntu Bionic) Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph Salisbury (jsalisbury) -- 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/1761729 Title: Ubuntu 18.04 Machine crashed while running ltp. Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: ---Problem Description--- Ubuntu 18.04 [ Briggs P8 ]: Machine crashed while running ltp. ---Environment-- Kernel Build: Ubuntu 18.04 System Name : ltc-briggs2 Model/Type : P8 Platform: BML ---Uname output--- root@ltc-briggs2:~# uname -a Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Steps to reproduce-- $ git clone https://github.com/linux-test-project/ltp.git $ cd ltp $ make autotools $ ./configure $ make $ make install ltp = root@ltc-briggs2:~# root@ltc-briggs2:~# [10781.098337] LTP: starting fs_inod01 (fs_inod $TMPDIR 10 10 10) [10782.837910] LTP: starting linker01 (linktest.sh 1000 1000) [10784.504474] LTP: starting openfile01 (openfile -f10 -t10) [10784.534953] LTP: starting inode01 [10784.550767] LTP: starting inode02 [10784.739104] LTP: starting stream01 [10784.740840] LTP: starting stream02 [10784.742487] LTP: starting stream03 [10784.744532] LTP: starting stream04 [10784.746087] LTP: starting stream05 [10784.747722] LTP: starting ftest01 [10785.142054] LTP: starting ftest02 [10785.158852] LTP: starting ftest03 [10785.404760] LTP: starting ftest04 [10785.527197] LTP: starting ftest05 [10785.937164] LTP: starting ftest06 [10785.958360] LTP: starting ftest07 [10786.463382] LTP: starting ftest08 [10786.592998] LTP: starting lftest01 (lftest 100) [10786.672707] LTP: starting writetest01 (writetest) [10786.774292] LTP: starting fs_di (fs_di -d $TMPDIR) [10792.973510] LTP: starting proc01 (proc01 -m 128) [10793.865686] ICMPv6: process `proc01' is using deprecated sysctl (syscall) net.ipv6.neigh.default.base_reachable_time - use net.ipv6.neigh.default.base_reachable_time_ms instead [10795.785593] LTP: starting read_all_dev (read_all -d /dev -e '/dev/watchdog?(0)' -q -r 10) [10795.895774] NET: Registered protocol family 40 [10795.918763] Bluetooth: Core ver 2.22 [10795.918866] NET: Registered protocol family 31 [10795.918909] Bluetooth: HCI device and connection manager initialized [10795.918955] Bluetooth: HCI socket layer initialized [10795.918991] Bluetooth: L2CAP socket layer initialized [10795.919032] Bluetooth: SCO socket layer initialized [10798.374850] usercopy: kernel memory exposure attempt detected from 29431ea4 () (1023 bytes) [10798.374952] [ cut here ] [10798.374988] kernel BUG at /build/linux-2BXDjB/linux-4.15.0/mm/usercopy.c:72! [10798.375041] Oops: Exception in kernel mode, sig: 5 [#1] [10798.375080] LE SMP NR_CPUS=2048 [10871.343999650,5] OPAL: Switch to big-endian OS NUMA PowerNV [10798.375117] [10876.190849323,5] OPAL: Switch to little-endian OS Modules linked in: hci_vhci bluetooth ecdh_generic vhost_vsock cuse vmw_vsock_virtio_transport_common userio vsock uhid vhost_net vhost tap snd_seq snd_seq_device snd_timer snd soundcore binfmt_misc sctp quota_v2 quota_tree nls_iso8859_1 ntfs xfs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter kvm_hv kvm idt_89hpesx vmx_crypto ofpart cmdlinepart ipmi_powernv power
[Kernel-packages] [Bug 1761619] Re: eventfd / poll interaction bug
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1761619 Title: eventfd / poll interaction bug Status in linux package in Ubuntu: Incomplete Bug description: In 17.10, I'm running into a new problem. This didn't happen to me on 16.04. I have some code that uses eventfds to signal things, and the code is not working -- after writing the eventfd, it does not come back readable from another thread using poll(). Here's a snippet from strace: ``` eventfd2(0, 0) = 5 fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0 write(1, "OPEN FD 5\n", 10OPEN FD 5 ) = 10 write(5, "\1\0\0\0\0\0\0\0", 8) = 8 nanosleep({tv_sec=0, tv_nsec=1}, 0x7fffd0cea1a0) = 0 poll([{fd=5, events=POLLRDNORM}], 1, 100) = 0 (Timeout) ``` The write(1,... ) is debugging output. The nanosleep was intended to see if sleeping a bit before polling would help. Note that the write(5, ...) and the poll() come from different threads. Note that using two descriptors from a pipe() (which I do for other platforms) is fine, so this is some kind of issue specific to eventfd. Also, trying to reproduce this with a simpler single threaded program did not succeed. I'm wondering if there is some underlying cache synchronization problem? I'm testing this in a VMware Fusion virtual machine (Fusion 10.1.1) running on 2017 macbook pro (underlying OS is macOS 10.13). For now I'm going to switch back to pipes, since eventfd() seems unreliable -- if you can spot anything obviously wrong about the system call sequence above, I'd love to hear it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761619/+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 1761626] Re: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el
We should probably also report this upstream, since it still affects current mainline. https://wiki.ubuntu.com/Bugs/Upstream/kernel We can also perform a kernel bisect to identify the commit that introduced this bug. We would first need to identify the last kernel version that did not have the bug and the first version that did. Can you test the following kernels: v4.6 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ v4.8 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/ v4.10 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/ You don't have to test every kernel, just up until the kernel that first has this bug. Thanks in advance! ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key ** Also affects: linux (Ubuntu Bionic) Importance: High Status: Confirmed ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Importance: Undecided => High ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Triaged ** Tags added: kernel-key ** Tags added: performing-bisect -- 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/1761626 Title: [regression] bionic 4.15.0-13-generic panics on qemu ppc64el Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel panics before initrd. Going back to xenial 4.4.0 works correctly. linux-image-4.15.0-13-generic: Installed: 4.15.0-13.14 Candidate: 4.15.0-13.14 Version table: *** 4.15.0-13.14 500 500 http://nibbler.snowman.lan/deb-proxy/ubuntu-ports bionic/main ppc64el Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 16:11 seq crw-rw 1 root audio 116, 33 Apr 5 16:11 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: ppc64el 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: Date: Thu Apr 5 16:13:28 2018 HibernationDevice: RESUME=UUID=2e904a57-3ce7-4b31-97ed-6c63b81b2221 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 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-119-generic root=UUID=294515c8-75f2-4996-8e4f-a838e6c75804 ro ProcLoadAvg: 3.04 2.18 0.92 3/119 1643 ProcLocks: 1: POSIX ADVISORY WRITE 1225 00:12:470 0 EOF 2: POSIX ADVISORY WRITE 841 00:12:459 0 EOF 3: FLOCK ADVISORY WRITE 832 00:12:449 0 EOF 4: POSIX ADVISORY WRITE 802 00:12:432 0 EOF 5: POSIX ADVISORY WRITE 350 00:12:294 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /dev/vda3 partition1408960 0 -1 ProcVersion: Linux version 4.4.0-119-generic (buildd@bos02-ppc64el-006) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) ) #143-Ubuntu SMP Mon Apr 2 16:08:02 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.4.0-119-generic N/A linux-backports-modules-4.4.0-119-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-05 (0 days ago) cpu_cores: Number of cores present = 1 cpu_coreson: Number of cores online = 1 cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+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 1761583] Re: Asus 200ha, no keyboard or touchpad support
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) 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/1761583 Title: Asus 200ha, no keyboard or touchpad support Status in linux package in Ubuntu: Incomplete Bug description: 17.10.1 - Asus 200ha, keyboard and touchpad not supported, working under 16.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761583/+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 1761796] Re: Rebooting bionic fails with hardware error
Test both -proposed & 4.16 kernels, and the issue persists. ** Tags added: kernel-bug-exists-upstream -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd09/13/2016:svnHP:pnProLi
[Kernel-packages] [Bug 1761831] [NEW] ASUS B150M Gaming hibernate/resume failure
Public bug reported: Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate / Resume from Hibernate - does not work ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mihai 1718 F pulseaudio /dev/snd/controlC0: mihai 1718 F pulseaudio Date: Fri Apr 6 20:19:49 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:0601 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03 InstallationDate: Installed on 2018-04-06 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InterpreterPath: /usr/bin/python3.6 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [System manufacturer System Product Name] hibernate/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: Default string dmi.board.name: B150M PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops bionic hibernate resume -- 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/1761831 Title: ASUS B150M Gaming hibernate/resume failure Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate / Resume from Hibernate - does not work ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: boot/vmlinuz-4.15.0-13-generic] ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 Annotation: This occurred during a previous hibernation, and prevented the system from resuming properly. ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mihai 1718 F pulseaudio /dev/snd/controlC0: mihai 1718 F pulseaudio Date: Fri Apr 6 20:19:49 2018 DuplicateSignature: hibernate/resume:System manufacturer System Product Name:0601 ExecutablePath: /usr/share/apport/apportcheckresume Failure: hibernate/resume HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03 InstallationDate: Installed on 2018-04-06 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InterpreterPath: /usr/bin/python3.6 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 046a:00
[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460
I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue. Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug: v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ v4.15-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc5/ v4.15-rc9: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9/ v4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/ v4.16-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/ You don't have to test every kernel, just up until the kernel that first has this bug. Thanks in advance! ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Tags added: kernel-da-key ** Also affects: linux (Ubuntu Bionic) Importance: High Status: Triaged ** Tags added: performing-bisect -- 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/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1761694] Re: Ubuntu-Server does not launch after kernel update to 4.4.0-116
If the mainline kernel still exhibits the bug, we can perform a kernel bisect to identify the commit that introduce the regression. ** Changed in: linux (Ubuntu) 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/1761694 Title: Ubuntu-Server does not launch after kernel update to 4.4.0-116 Status in linux package in Ubuntu: Incomplete Bug description: I am running Ubuntu-Server 14.04.5 LTS in a HyperV-VM with the Xenial HWE-Stack enabled. Until the kernel 4.4.0-112 everything ran smoothly, but with the kernel update to 4.4.0-116 the system cannot be launched and stops during the boot with the following error message: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait for the right device?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/99acf869-911c-47ae-917f-7e82d3c99b8e does not exists. Dropping to a shell! Also same behaviour with the latest kernel 4.4.0-119. I already tried to boot with the rootdelay=10 argument but this has no effect. If you need further informations please tell me. Thanks for your support. Best regards Falk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761694/+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 1761694] Re: Ubuntu-Server does not launch after kernel update to 4.4.0-116
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key -- 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/1761694 Title: Ubuntu-Server does not launch after kernel update to 4.4.0-116 Status in linux package in Ubuntu: Incomplete Bug description: I am running Ubuntu-Server 14.04.5 LTS in a HyperV-VM with the Xenial HWE-Stack enabled. Until the kernel 4.4.0-112 everything ran smoothly, but with the kernel update to 4.4.0-116 the system cannot be launched and stops during the boot with the following error message: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait for the right device?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/99acf869-911c-47ae-917f-7e82d3c99b8e does not exists. Dropping to a shell! Also same behaviour with the latest kernel 4.4.0-119. I already tried to boot with the rootdelay=10 argument but this has no effect. If you need further informations please tell me. Thanks for your support. Best regards Falk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761694/+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 1761674] Re: [Ubuntu 16.04] kernel: fix rwlock implementation
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Status: New => Triaged -- 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/1761674 Title: [Ubuntu 16.04] kernel: fix rwlock implementation Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: Description: kernel: fix rwlock implementation Symptom: Kernel hangs, due to deadlock on an rwlock. Problem: With upstream commit 94232a4332de ("s390/rwlock: improve writer fairness") rwlock writer fairness was supposed to be implemented. If a writer tries to take an rwlock it sets unconditionally the writer bit within the lock word and waits until all readers have released the lock. This however can lead to a deadlock since rwlocks can be taken recursively by readers. If e.g. CPU 0 holds the lock as a reader, and CPU 1 wants to write-lock the lock, then CPU 1 sets the writer bit and afterwards busy waits for CPU 0 to release the lock. If now CPU 0 tries to read-lock the lock again (recursively) it will also busy wait until CPU 1 removes the writer bit, which will never happen, since it waits for the first reader on CPU 0 to release the lock. Solution: Revert the rwlock writer fairness semantics again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1761674/+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 1761674] Re: [Ubuntu 16.04] kernel: fix rwlock implementation
Is the patch posted in comment #1 only needed in 16.04? Also, can you post a comment here when the patch gets accepted upstream? ** Tags added: kernel-da-key -- 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/1761674 Title: [Ubuntu 16.04] kernel: fix rwlock implementation Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: Description: kernel: fix rwlock implementation Symptom: Kernel hangs, due to deadlock on an rwlock. Problem: With upstream commit 94232a4332de ("s390/rwlock: improve writer fairness") rwlock writer fairness was supposed to be implemented. If a writer tries to take an rwlock it sets unconditionally the writer bit within the lock word and waits until all readers have released the lock. This however can lead to a deadlock since rwlocks can be taken recursively by readers. If e.g. CPU 0 holds the lock as a reader, and CPU 1 wants to write-lock the lock, then CPU 1 sets the writer bit and afterwards busy waits for CPU 0 to release the lock. If now CPU 0 tries to read-lock the lock again (recursively) it will also busy wait until CPU 1 removes the writer bit, which will never happen, since it waits for the first reader on CPU 0 to release the lock. Solution: Revert the rwlock writer fairness semantics again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1761674/+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 1761443] Re: linux-aws: 4.4.0-1055.64 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1761443 Title: linux-aws: 4.4.0-1055.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761438 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761443/+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 1761825] [NEW] amdgpu.dc fails on AMD (Kaveri) A10-7300
Public bug reported: Booting kernel 4.16 ( BOOT_IMAGE=/vmlinuz-4.16.0-041600-generic ) with external monitor attached to VGA port of Lenovo Ideapad Z50-75 (AMD Kaveri A10-7300) results in blank external display when amdgpu.ci_support is forced (i.e. radeon disabled). key dmesg messages are: [1.897177] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.897266] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.897380] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [1.897489] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:6! type 0 expected 3 Kernel boot options are: amdgpu.cik_support=1 radeon.cik_support=0 If I boot the same kernel with the following options: amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.dc=0 The VGA attached display works. Attached in the tar are: version.log - output of cat /proc/version lspci-vnvn.log - output of sudo lscpi -vnvn dmesg_amdgpu.dc-(default-one) - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc left to deafult dmesg_amdgpu.dc-0 - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc disabled ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amdgpu -- 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/1761825 Title: amdgpu.dc fails on AMD (Kaveri) A10-7300 Status in linux package in Ubuntu: New Bug description: Booting kernel 4.16 ( BOOT_IMAGE=/vmlinuz-4.16.0-041600-generic ) with external monitor attached to VGA port of Lenovo Ideapad Z50-75 (AMD Kaveri A10-7300) results in blank external display when amdgpu.ci_support is forced (i.e. radeon disabled). key dmesg messages are: [1.897177] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.897266] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.897380] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [1.897489] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:6! type 0 expected 3 Kernel boot options are: amdgpu.cik_support=1 radeon.cik_support=0 If I boot the same kernel with the following options: amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.dc=0 The VGA attached display works. Attached in the tar are: version.log - output of cat /proc/version lspci-vnvn.log - output of sudo lscpi -vnvn dmesg_amdgpu.dc-(default-one) - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc left to deafult dmesg_amdgpu.dc-0 - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761825/+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 1761796] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104425/+files/ProcInterrupts.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modal
[Kernel-packages] [Bug 1761796] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104423/+files/ProcCpuinfo.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias:
[Kernel-packages] [Bug 1761796] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104421/+files/Lspci.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvr
[Kernel-packages] [Bug 1761646] Re: Can't mount kvm image file on new kernel of 16.04(linux 4.4.0-119)
Would it be possible for you to test the proposed kernel and post back if it resolves this bug? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance! ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Tags added: kernel-da-key -- 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/1761646 Title: Can't mount kvm image file on new kernel of 16.04(linux 4.4.0-119) Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: When I use 4.4.0-62-generic kernel, I can mount kvm image file. But when I use 4.4.0-116-generic or 119 kernel, I can't mount the kvm image file. Is there some way to mount the kvm image file on 4.4.0-116-generic later kernel? - release root@ofaci1:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial root@ofaci1:~# - packages root@ofaci1:~# dpkg -l | egrep "qemu|mount|linux-image-4.4.0-11" ii cgroupfs-mount 1.2 all Light-weight package to set up cgroupfs mounts ii ipxe-qemu 1.0.0+git-20150424.a25a16d-1ubuntu1.2 all PXE boot firmware - ROM images for qemu ii libmount1:amd64 2.27.1-6ubuntu3.4 amd64device mounting library ii linux-image-4.4.0-116-generic 4.4.0-116.140 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP ii linux-image-4.4.0-119-generic 4.4.0-119.143 amd64Linux kernel image for version 4.4.0 on 64 bit x86 SMP ii mount 2.27.1-6ubuntu3.4 amd64tools for mounting and manipulating filesystems ii qemu-block-extra:amd64 1:2.5+dfsg-5ubuntu10.24 amd64extra block backend modules for qemu-system and qemu-utils ii qemu-kvm1:2.5+dfsg-5ubuntu10.24 amd64QEMU Full virtualization ii qemu-system-common 1:2.5+dfsg-5ubuntu10.24 amd64QEMU full system emulation binaries (common files) ii qemu-system-x86 1:2.5+dfsg-5ubuntu10.24 amd64QEMU full system emulation binaries (x86) ii qemu-utils 1:2.5+dfsg-5ubuntu10.24 amd64QEMU utilities root@ofaci1:~# - Use 4.4.0-62-generic root@ofaci1:~# uname -a Linux ofaci1 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@ofaci1:~# qemu-nbd --connect /dev/nbd1 /opt/ci-pool/slave1.qcow2 root@ofaci1:~# fdisk /dev/nbd1 Welcome to fdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/nbd1: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000dfd65 Device Boot Start End Sectors Size Id Type /dev/nbd1p1 2048 3905535 3903488 1.9G 82 Linux swap / Solaris /dev/nbd1p2 *3905536 83884031 79978496 38.1G 83 Linux Command (m for help): q root@ofaci1:~# mount /dev/nbd1p2 /mnt/d1 root@ofaci1:~# ls /mnt/d1 bin etc initrd.img.old lost+found opt run sys var boot homelib media proc sbin tmp vmlinuz dev initrd.img lib64 mnt root srv usr vmlinuz.old root@ofaci1:~# umount /mnt/d1 - Use 4.4.0-119-generic root@ofaci1:~# uname -a Linux ofaci1 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@ofaci1:~# qemu-nbd --connect /dev/nbd1 /opt/ci-pool/slave1.qcow2 root@ofaci1:~# echo $? 0 root@ofaci1:~# fdisk /dev/nbd1 Welcome to fdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/nbd1: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identi
[Kernel-packages] [Bug 1761693] Re: Wifi realtek 8822be BUG <=18.04
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1761693 Title: Wifi realtek 8822be BUG <=18.04 Status in linux package in Ubuntu: Incomplete Bug description: I am a regular linux user and i have bought last week a new computer that comes with the realtek 8822be wireless chipset. While using Ubuntu 16.04(Kernel version updated to 4.14 where we started to have support to this chipset) or both 18.04 beta 1 and final version i found a problem: 1º when i boot all this versions with the kernel version >= 4.14, i found out that the driver is instaled and she is detected in the network manager.Anyway, when i used she won´t work and in few secconds later will shutdown. When i go to the wifi settings i can´t find networks! 2º I use modprobe so that i can manipulate my drivers/modules and i can start to work with my wifi card: -> modprobe -rv r8822be -> modprobe -v r8822be aspm=0 The problem is that when i connect to a 5ghz frequency router, i have very slow download speed 8 mbps max (Usually my speed is approximately 200/210 mbps in wifi mode).In the outher hand when i connect to a 2.4ghz frequency router it works fine! Thanks Best regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761693/+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 1761439] Re: linux-aws: 4.4.0-1017.17 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1017.17 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1761439 Title: linux-aws: 4.4.0-1017.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1761438 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761439/+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 1761796] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104426/+files/ProcModules.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias:
[Kernel-packages] [Bug 1761796] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104428/+files/WifiSyslog.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dm
[Kernel-packages] [Bug 1761796] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104422/+files/Lsusb.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvr
[Kernel-packages] [Bug 1761796] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104392/+files/ProcCpuinfoMinimal.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP d
[Kernel-packages] [Bug 1761796] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104394/+files/ProcModules.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias:
[Kernel-packages] [Bug 1761796] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104420/+files/CurrentDmesg.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias:
[Kernel-packages] [Bug 1761796] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104396/+files/WifiSyslog.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dm
[Kernel-packages] [Bug 1761796] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104391/+files/ProcCpuinfo.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias:
[Kernel-packages] [Bug 1761796] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104393/+files/ProcInterrupts.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modal
[Kernel-packages] [Bug 1761796] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104390/+files/Lsusb.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvr
[Kernel-packages] [Bug 1761796] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104395/+files/UdevDb.txt -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:b
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16 ** Also affects: linux (Ubuntu Bionic) Importance: High Status: Incomplete ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed ** Tags added: kernel-da-key -- 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/1761796 Title: Rebooting bionic fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error
apport information ** Summary changed: - Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error + Rebooting bionic fails with hardware error ** Description changed: From an ephemeral environment in an HPGen9, the machine fails to reboot - with the following hardware error. - - This doesn't happen on xenial, it only happens in Bionic. + when the ephemeral environment is Bionic (it does not fail in Xenial). Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ - + The actual failure is: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. - --- + --- AlsaDevices: - total 0 - crw-rw 1 root audio 116, 33 Apr 6 17:40 timer + total 0 + crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: - + ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: - linux-restricted-modules-4.15.0-13-generic N/A - linux-backports-modules-4.15.0-13-generic N/A - linux-firmware N/A + linux-restricted-modules-4.15.0-13-generic N/A + linux-backports-modules-4.15.0-13-generic N/A + linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor:
[Kernel-packages] [Bug 1745646] Re: Battery drains when laptop is off (shutdown)
4.12.0-041200-generic #201804061120 is good. http://paste.ubuntu.com/p/55HMBFVSJY/ -- 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/1745646 Title: Battery drains when laptop is off (shutdown) Status in Linux: Unknown Status in acpi package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in acpi source package in Artful: New Status in linux source package in Artful: In Progress Bug description: I am using hp AY008tx laptop , and many other laptop users (HP) are also facing the same issue . The problem don't occur when i install windows 10 . Now, only ubuntu is installed. i am using latest bios insyde20 rev 5.(latest) WOL disabled and no usb device connected checked my battery . it don't happen when i remove battery and plug it again after shutdown. tried laptop_mode_tools and tpl too ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 26 22:50:53 2018 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gopal 2391 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994 InstallationDate: Installed on 2018-01-25 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 002: ID 0a5c:216d Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.58 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1745646/+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 1761796] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104389/+files/Lspci.txt -- 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/1761796 Title: Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot with the following hardware error. This doesn't happen on xenial, it only happens in Bionic. Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.ch
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error
** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1761796 Title: Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: From an ephemeral environment in an HPGen9, the machine fails to reboot with the following hardware error. This doesn't happen on xenial, it only happens in Bionic. Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 33 Apr 6 17:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 09/13/2016 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd09/13/2016:svnHP:
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error
apport information ** Tags added: apport-collected uec-images ** Description changed: From an ephemeral environment in an HPGen9, the machine fails to reboot with the following hardware error. This doesn't happen on xenial, it only happens in Bionic. Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 33 Apr 6 17:40 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu2 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + DistroRelease: Ubuntu 18.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + MachineType: HP ProLiant DL360 Gen9 + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 BOOTIF=01-94:18:82:7a:82:c8 + ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-13-generic N/A + linux-backports-modules-4.15.0-13-generic N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic uec-images + Uname: Linux 4.15.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video + _MarkForUpload: True + dmi.bios.date: 09/13/2016 + dmi.bios.vendor: HP + dmi.bios.version: P89 + dmi.board.name: ProLiant DL360 Gen9 + dmi.board.vendor: HP + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrP89:bd09/13/2016:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: + dmi.product.family: ProLiant + dmi.product.name: ProLiant DL360 Gen9 + dmi.sys.vendor: HP ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1761796/+attachment/5104388/+files/CurrentDmesg.txt -- You received this bug notification because you are
[Kernel-packages] [Bug 1761796] Re: Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error
** Description changed: + From an ephemeral environment in an HPGen9, the machine fails to reboot + with the following hardware error. + + This doesn't happen on xenial, it only happens in Bionic. + + Full log from the moment the 'sudo reboot' was executed: + https://pastebin.ubuntu.com/p/hyD6VY7CbW/ + [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. - Starting Reboot... + Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. - Stopping LVM2 metadata daemon... + Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. ** Description changed: From an ephemeral environment in an HPGen9, the machine fails to reboot with the following hardware error. This doesn't happen on xenial, it only happens in Bionic. Full log from the moment the 'sudo reboot' was executed: https://pastebin.ubuntu.com/p/hyD6VY7CbW/ + + [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.8158
[Kernel-packages] [Bug 1759445] Re: kernel panic when trying to reboot in bionic
Possibly a reproduction but in this case Xenial is deployed and rsyslog shows the kernel upgraded to 4.4.0-119-generic. These are automated runs and we don't have the console output to confirm a kernel panic. ** Attachment added: "rsyslog.swoobat_run_11e7681c-d91b-44dc-adb6-143acbb897c1" https://bugs.launchpad.net/maas/+bug/1759445/+attachment/5104336/+files/rsyslog.swoobat_run_11e7681c-d91b-44dc-adb6-143acbb897c1 -- 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/1759445 Title: kernel panic when trying to reboot in bionic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: cpe_foundation test deployment of Bionic failed. After some investigation, it looks like the nodes deployed and installed bionic, but never came back from a reboot. Accessing the ILO console of a node in question (all nodes failed), it revealed a kernel panic (attached) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1759445/+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 1715609] Re: kernel warning: skb_warn_bad_offload
I built a test kernel with commit b2504a5dbef3305ef41988ad270b0e8ec289331c reverted. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1715609 Note, to test this kernel, you need to install both the linux-image and linux-image-extra .deb packages. It might also be worth testing the latest mainline kernel, to see if this bug was fixed another way. That kernel can be downloaded from: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/ Thanks in advance! -- 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/1715609 Title: kernel warning: skb_warn_bad_offload Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Since upgrading to kernel version 4.10.0-33.37, we're seeing a lot of call traces triggered by skb_warn_bad_offload in the syslog. Regression introduced when fixing this bug? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705447 kernel: [570943.49] [ cut here ] kernel: [570943.494448] WARNING: CPU: 3 PID: 21982 at /build/linux-hwe-YA6IuF/linux-hwe-4.10.0/net/core/dev.c:2576 skb_warn_bad_offload+0xd1/0x120 kernel: [570943.494450] e1000e: caps=(0x0030002149a9, 0x) len=1701 data_len=1659 gso_size=1480 gso_type=2 ip_summed=0 kernel: [570943.494451] Modules linked in: udp_diag tcp_diag inet_diag echainiv authenc xfrm4_mode_tunnel xt_state binfmt_misc veth xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo bridge stp llc iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ppdev irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf hci_uart ie31200_edac btbcm edac_core intel_pch_thermal btqca serio_raw btintel bluetooth parport_pc parport mac_hid intel_lpss_acpi acpi_pad intel_lpss autofs4 kernel: [570943.494500] btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 e1000e psmouse ptp ahci pps_core libahci wmi pinctrl_sunrisepoint i2c_hid video pinctrl_intel hid fjes kernel: [570943.494524] CPU: 3 PID: 21982 Comm: charon Tainted: GW 4.10.0-33-generic #37~16.04.1-Ubuntu kernel: [570943.494524] Hardware name: ... kernel: [570943.494525] Call Trace: kernel: [570943.494541] kernel: [570943.494544] dump_stack+0x63/0x90 kernel: [570943.494545] __warn+0xcb/0xf0 kernel: [570943.494546] warn_slowpath_fmt+0x5f/0x80 kernel: [570943.494547] ? ___ratelimit+0xa2/0xf0 kernel: [570943.494549] skb_warn_bad_offload+0xd1/0x120 kernel: [570943.494550] __skb_gso_segment+0x17d/0x190 kernel: [570943.494564] validate_xmit_skb+0x14f/0x2a0 kernel: [570943.494565] validate_xmit_skb_list+0x43/0x70 kernel: [570943.494567] sch_direct_xmit+0x16b/0x1c0 kernel: [570943.494568] __dev_queue_xmit+0x47e/0x690 kernel: [570943.494569] dev_queue_xmit+0x10/0x20 kernel: [570943.494570] ip_finish_output2+0x27a/0x370 kernel: [570943.494571] ip_finish_output+0x176/0x270 kernel: [570943.494571] ip_output+0x76/0xe0 kernel: [570943.494572] ? ip_fragment.constprop.49+0x80/0x80 kernel: [570943.494573] ip_forward_finish+0x43/0x70 kernel: [570943.494574] ip_forward+0x385/0x460 kernel: [570943.494575] ? ip_frag_mem+0x50/0x50 kernel: [570943.494575] ip_rcv_finish+0x11b/0x400 kernel: [570943.494576] ip_rcv+0x28b/0x3a0 ... kernel: [570943.494632] ---[ end trace f01d0adcc1256afe ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715609/+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 1761433] Re: linux-lts-trusty: 3.13.0-145.194~precise2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1761433 Title: linux-lts-trusty: 3.13.0-145.194~precise2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1761430 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1761433/+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 1743094] Re: [regression] hibernation (freezes on resume) since 4.13.0-25.29
Ubuntu MATE 17.10 with kernel 4.15.x & 4.16.x - hibernate / resume from hibernate works as expected. Ubuntu (vanilla) & Ubuntu MATE 18.04 Beta 1 / Beta 2 with kernel 4.15.x & 4.16.x - resume from hibernate does not work. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759860 -- 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/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+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 1761796] Missing required logs.
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 1761796 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: bionic -- 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/1761796 Title: Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error Status in linux package in Ubuntu: Incomplete Bug description: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761796/+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 1761796] [NEW] Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error
Public bug reported: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic -- 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/1761796 Title: Rebooting bionic running on an ephemeral env (overlayfs) fails with hardware error Status in linux package in Ubuntu: Incomplete Bug description: [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Reached target Shutdown. [ OK ] Reached target Final Step. Starting Reboot... [ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. [ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 257.160530] {1}[Hardware Error]: event severity: fatal [ 257.160533] {1}[Hardware Error]: Error 0, type: fatal [ 257.160534] {1}[Hardware Error]: section_type: PCIe error [ 257.160536] {1}[Hardware Error]: port_type: 4, root port [ 257.160541] {1}[Hardware Error]: version: 1.16 [ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160546] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160547] {1}[Hardware Error]: slot: 0 [ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160552] {1}[Hardware Error]: class_code: 040600 [ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160556] {1}[Hardware Error]: Error 1, type: fatal [ 257.160557] {1}[Hardware Error]: section_type: PCIe error [ 257.160559] {1}[Hardware Error]: port_type: 4, root port [ 257.160560] {1}[Hardware Error]: version: 1.16 [ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143 [ 257.160564] {1}[Hardware Error]: device_id: :00:01.0 [ 257.160565] {1}[Hardware Error]: slot: 0 [ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03 [ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02 [ 257.160568] {1}[Hardware Error]: class_code: 040600 [ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000, control: 0x0003 [ 257.160570] Kernel panic - not syncing: Fatal hardware error! [ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation range: 0x8000-0xbfff) [ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://l