[Kernel-packages] [Bug 1765366] Re: Unable to build kvm-unit-test on i386 system
Issue reported upstream: https://www.spinics.net/lists/kvm/msg168472.html Fix available at: https://www.spinics.net/lists/kvm/msg168677.html Therefore I'm closing this bug, thanks. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- 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/1765366 Title: Unable to build kvm-unit-test on i386 system Status in linux package in Ubuntu: Fix Released Bug description: When trying to build the kvm-unit-test on i386 node, it will fail with: gcc -m32 -O1 -g -MMD -MF lib/x86/.usermode.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Werror -fno-omit-frame-pointer -Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -ffreestanding -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I lib -c -o lib/x86/usermode.o lib/x86/usermode.c : recipe for target 'lib/x86/usermode.o' failed stderr: lib/x86/usermode.c: In function ‘run_in_user’: lib/x86/usermode.c:49:2: error: inconsistent operand constraints in an ‘asm’ asm volatile ( ^~~ make: *** [lib/x86/usermode.o] Error 1 Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. ./configure 3. make This is a test suite issue, not a regression, as it can be reproduced on 4.13.0-38 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 19 09:39 seq crw-rw 1 root audio 116, 33 Apr 19 09:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.8 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu Apr 19 10:12:48 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765366/+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 1774362] [NEW] package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1u
*** This bug is a duplicate of bug 1772985 *** https://bugs.launchpad.net/bugs/1772985 Public bug reported: standard upgrade on 4.4.0-128-generic ProblemType: Package DistroRelease: Ubuntu 16.04 Package: crda 3.13-1 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed May 23 21:03:34 2018 DuplicateSignature: package:crda:3.13-1 Unpacking crda (3.13-1ubuntu0.16.04.1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.13-1ubuntu0.16.04.1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 InstallationDate: Installed on 2016-05-31 (729 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: crda Title: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: crda (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1774362 Title: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 Status in crda package in Ubuntu: New Bug description: standard upgrade on 4.4.0-128-generic ProblemType: Package DistroRelease: Ubuntu 16.04 Package: crda 3.13-1 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed May 23 21:03:34 2018 DuplicateSignature: package:crda:3.13-1 Unpacking crda (3.13-1ubuntu0.16.04.1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.13-1ubuntu0.16.04.1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 InstallationDate: Installed on 2016-05-31 (729 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: crda Title: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1774362/+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 1774126] Re: linux-oem: 4.13.0-1030.33 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774126 Title: linux-oem: 4.13.0-1030.33 -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-oem package in Ubuntu: Invalid Status in linux-oem 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: 1774124 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774126/+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 1774362] Re: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubu
*** This bug is a duplicate of bug 1772985 *** https://bugs.launchpad.net/bugs/1772985 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1772985, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1772985 package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crda in Ubuntu. https://bugs.launchpad.net/bugs/1774362 Title: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 Status in crda package in Ubuntu: New Bug description: standard upgrade on 4.4.0-128-generic ProblemType: Package DistroRelease: Ubuntu 16.04 Package: crda 3.13-1 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed May 23 21:03:34 2018 DuplicateSignature: package:crda:3.13-1 Unpacking crda (3.13-1ubuntu0.16.04.1) over (3.13-1) ... dpkg: error processing archive /var/cache/apt/archives/crda_3.13-1ubuntu0.16.04.1_amd64.deb (--unpack): trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 InstallationDate: Installed on 2016-05-31 (729 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: crda Title: package crda 3.13-1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package wireless-regdb 2015.07.20-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1774362/+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 1772933] Re: linux-oem: 4.15.0-1007.10 -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: 1772927 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Thursday, 31. May 2018 09: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: 1772927 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Thursday, 31. May 2018 09: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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1772933 Title: linux-oem: 4.15.0-1007.10 -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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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 -- boot-testing-requested: true kernel-stable-master-bug: 1772927 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/1772933/+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 1774124] Re: linux: 4.13.0-45.50 -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 => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => 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 backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 (linux-hwe) derivatives: bug 1774125 (linux-raspi2) - kernel-stable-phase-changed:Wednesday, 30. May 2018 09:01 UTC - kernel-stable-phase:Uploaded - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Thursday, 31. May 2018 09:04 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 backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 (linux-hwe) derivatives: bug 1774125 (linux-raspi2) -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Thursday, 31. May 2018 09:04 UTC + bugs-spammed: true + 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 in Ubuntu. https://bugs.launchpad.net/bugs/1774124 Title: linux: 4.13.0-45.50 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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: Confirmed 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 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 (linux-hwe) derivatives: bug 1774125 (linux-raspi2) -- swm properties -- boot-testing-requested: true bugs-spammed: 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/1774124/+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 1772934] Re: linux-gcp: 4.15.0-1009.9 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1772934 Title: linux-gcp: 4.15.0-1009.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid 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: Fix Released 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-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- boot-testing-requested: true kernel-stable-master-bug: 1772927 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/1772934/+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
I can't wake from standby with linux-image-4.15.0-22-generic But: linux-image-4.15.0-1006-oem is working for me GDriver: NVidia proprietry --- Adding "nouveau.modeset=0" to GRUB_CMDLINE_LINUX didn't work either. https://www.dell.com/community/Inspiron/Suspend-resume-problems-on-Ubuntu-18-04/td-p/6072410 -- 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-hwe package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau 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 1774126] Re: linux-oem: 4.13.0-1030.33 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774126 Title: linux-oem: 4.13.0-1030.33 -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: In Progress 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-oem package in Ubuntu: Invalid Status in linux-oem 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: 1774124 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774126/+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 1774375] [NEW] Kernel panic at boot with 4.15.0-20-generic
Public bug reported: Kernel panic on boot with 4.15.0-20-generic. Call trace: dump_stack +0x63/0x8b panic+0xe4/0x244 mount_block_root+0x1f6/0x2da kernel offset: 0x3e0 end kernel panic - not syncing: VFS unable to mount root on unknown block (0,0) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.15.0.22.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danr 2384 F pulseaudio /dev/snd/controlC0: danr 2384 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu May 31 11:01:48 2018 HibernationDevice: RESUME=UUID=45b1ba4d-ef5d-4027-b18b-9ca310c4fb2a InstallationDate: Installed on 2018-03-24 (67 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1774375 Title: Kernel panic at boot with 4.15.0-20-generic Status in linux package in Ubuntu: New Bug description: Kernel panic on boot with 4.15.0-20-generic. Call trace: dump_stack +0x63/0x8b panic+0xe4/0x244 mount_block_root+0x1f6/0x2da kernel offset: 0x3e0 end kernel panic - not syncing: VFS unable to mount root on unknown block (0,0) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.15.0.22.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danr 2384 F pulseaudio /dev/snd/controlC0: danr 2384 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu May 31 11:01:48 2018 HibernationDevice: RESUME=UUID=45b1ba4d-ef5d-4027-b18b-9ca310c4fb2a InstallationDate: Installed on 2018-03-24 (67 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774375/+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 1774190] Re: linux: 3.13.0-151.201 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1774190 Title: linux: 3.13.0-151.201 -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: In Progress 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: Invalid Status in Kernel SRU Workflow verification-testing series: New 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 1774191 (linux-lts-trusty) derivatives: kernel-stable-phase-changed:Wednesday, 30. May 2018 14:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774190/+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 1774191] Re: linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** 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-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1774191 Title: linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid 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: In Progress 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: 1774190 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774191/+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 1774190] Re: linux: 3.13.0-151.201 -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 in Ubuntu. https://bugs.launchpad.net/bugs/1774190 Title: linux: 3.13.0-151.201 -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: 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: Invalid Status in Kernel SRU Workflow verification-testing series: New 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 1774191 (linux-lts-trusty) derivatives: kernel-stable-phase-changed:Wednesday, 30. May 2018 14:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774190/+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 1774375] 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/1774375 Title: Kernel panic at boot with 4.15.0-20-generic Status in linux package in Ubuntu: Confirmed Bug description: Kernel panic on boot with 4.15.0-20-generic. Call trace: dump_stack +0x63/0x8b panic+0xe4/0x244 mount_block_root+0x1f6/0x2da kernel offset: 0x3e0 end kernel panic - not syncing: VFS unable to mount root on unknown block (0,0) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.15.0.22.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danr 2384 F pulseaudio /dev/snd/controlC0: danr 2384 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu May 31 11:01:48 2018 HibernationDevice: RESUME=UUID=45b1ba4d-ef5d-4027-b18b-9ca310c4fb2a InstallationDate: Installed on 2018-03-24 (67 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774375/+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 1767603] Re: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel
Duplicate of https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836 -- 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/1767603 Title: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel Status in linux package in Ubuntu: Incomplete Bug description: I can confirm the following bug in kernel version 4.15 in bionic, https://bugzilla.kernel.org/show_bug.cgi?id=199035 WORKAROUND: Boot into kernel 4.13. WORKAROUND: Disable bluetooth in BIOS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767603/+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 1772933] Re: linux-oem: 4.15.0-1007.10 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1772933 Title: linux-oem: 4.15.0-1007.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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 -- boot-testing-requested: true kernel-stable-master-bug: 1772927 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/1772933/+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 1774191] Re: linux-lts-trusty: 3.13.0-151.201~precise1 -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-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1774191 Title: linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid 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 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-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: 1774190 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774191/+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 1774375] Re: Kernel panic at boot with 4.15.0-20-generic
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1774375 Title: Kernel panic at boot with 4.15.0-20-generic Status in linux package in Ubuntu: Fix Released Bug description: Kernel panic on boot with 4.15.0-20-generic. Call trace: dump_stack +0x63/0x8b panic+0xe4/0x244 mount_block_root+0x1f6/0x2da kernel offset: 0x3e0 end kernel panic - not syncing: VFS unable to mount root on unknown block (0,0) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.15.0.22.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danr 2384 F pulseaudio /dev/snd/controlC0: danr 2384 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu May 31 11:01:48 2018 HibernationDevice: RESUME=UUID=45b1ba4d-ef5d-4027-b18b-9ca310c4fb2a InstallationDate: Installed on 2018-03-24 (67 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/08/2015:svnDellInc.:pnXPS159530:pvrA08:rvnDellInc.:rnXPS159530:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774375/+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 1767603] Re: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel
** Tags removed: kernel-bug-exists-upstream ** Tags added: needs-apport-collect needs-upstream-testing ** Changed in: linux (Ubuntu) Importance: Medium => Low -- 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/1767603 Title: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel Status in linux package in Ubuntu: Incomplete Bug description: I can confirm the following bug in kernel version 4.15 in bionic, https://bugzilla.kernel.org/show_bug.cgi?id=199035 WORKAROUND: Boot into kernel 4.13. WORKAROUND: Disable bluetooth in BIOS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767603/+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 1772940] Re: linux-azure: 4.15.0-1013.13~16.04.2 -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 ** 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/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** 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: 1772927 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Thursday, 31. May 2018 11:31 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: 1772927 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Thursday, 31. May 2018 11:31 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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1772940 Title: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid 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-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 stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1772927 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/1772940/+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 1766052] Re: Incorrect blacklist of bcm2835_wdt
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kees Cook (kees) -- 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/1766052 Title: Incorrect blacklist of bcm2835_wdt Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Fix Committed Bug description: Without bcm2835_wdt loaded, Raspberry Pi systems cannot reboot or shut down. This needs to be removed from the automatic blacklist generated by the kernel build that ends up in /lib/modprobe.d/blacklist_linux_$(uname -r).conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766052/+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 1774406] [NEW] package linux-headers-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: instalado linux-headers-4.15.0-22-generic paquete post-installation guión el subpr
Public bug reported: I am working in render in blender and popup this Notice ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-headers-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 AptOrdering: python3-apport:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu May 31 06:45:07 2018 ErrorMessage: instalado linux-headers-4.15.0-22-generic paquete post-installation guión el subproceso devolvió un error con estado de salida 1 HibernationDevice: RESUME=UUID=c7c7402c-dc17-4beb-82c2-c64e9085ad10 InstallationDate: Installed on 2017-10-24 (218 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. B85M-DS3H ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f515d285-287f-46eb-8aa9-a0eb819d6aed ro quiet splash nomodeset 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.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8 RfKill: SourcePackage: linux Title: package linux-headers-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: instalado linux-headers-4.15.0-22-generic paquete post-installation guión el subproceso devolvió un error con estado de salida 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd08/25/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-DS3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-DS3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-DS3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1774406 Title: package linux-headers-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: instalado linux-headers-4.15.0-22-generic paquete post-installation guión el subproceso devolvió un error con estado de salida 1 Status in linux package in Ubuntu: New Bug description: I am working in render in blender and popup this Notice ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-headers-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 AptOrdering: python3-apport:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu May 31 06:45:07 2018 ErrorMessage: instalado linux-headers-4.15.0-22-generic paquete post-installation guión el subproceso devolvió un error con estado de salida 1 HibernationDevice: RESUME=UUID=c7c7402c-dc17-4beb-82c2-c64e9085ad10 InstallationDate: Installed on 2017-10-24 (218 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. B85M-DS3H ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f515d285-287f-46eb-8aa9-a0eb819d6aed ro quiet splash nomodeset 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.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8 RfKill: SourcePackage: linux Title: package linux-headers-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: instalado linux-headers-4.15.0-22-generic paquete post-installation guión el subproceso devolvió un error con estado de salida 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd.
[Kernel-packages] [Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
I built the next test kernel, up to the following commit:
1849f800fba32cd5a0b647f824f11426b85310d8
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
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/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1766052] Re: Incorrect blacklist of bcm2835_wdt
Not sure if this raspbery pi is armhf or arm64. Comparing armhf & arm64 blacklists, neither are changed between release pocket and -proposed. armhf does not have bcm2835_wdt listed, and arm64 does. These are for the generic kernel. $ grep bcm2835 *.conf blacklist_linux_4.15.0-20-generic.conf:blacklist bcm2835_wdt blacklist_linux_4.15.0-23-generic.conf:blacklist bcm2835_wdt $ diff -u blacklist_linux_4.15.0-20-generic.conf blacklist_linux_4.15.0-23-generic.conf --- blacklist_linux_4.15.0-20-generic.conf 2018-04-24 05:56:17.0 +0100 +++ blacklist_linux_4.15.0-23-generic.conf 2018-05-23 17:54:55.0 +0100 @@ -1,4 +1,4 @@ -# Kernel supplied blacklist for linux 4.15.0-20-generic arm64 +# Kernel supplied blacklist for linux 4.15.0-23-generic arm64 # modprobe.d/common.conf # LP:1434842 -- disable OSS drivers by default to allow pulseaudio to emulate blacklist snd-mixer-oss This is fine to ship, but it seems like the bug is not fixed yet?! Or which kernel flavour I should be checking, if not generic?! -- 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/1766052 Title: Incorrect blacklist of bcm2835_wdt Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Fix Committed Bug description: Without bcm2835_wdt loaded, Raspberry Pi systems cannot reboot or shut down. This needs to be removed from the automatic blacklist generated by the kernel build that ends up in /lib/modprobe.d/blacklist_linux_$(uname -r).conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766052/+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 1766052] Re: Incorrect blacklist of bcm2835_wdt
I wonder if grep -v '^bcm2835_wdt$$' | \ should actually be grep -v '^bcm2835_wdt.ko$$' | \ given that next line strips .ko suffix: sed -e 's/^/blacklist /' -e 's/.ko$$//' | \ -- 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/1766052 Title: Incorrect blacklist of bcm2835_wdt Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Fix Committed Bug description: Without bcm2835_wdt loaded, Raspberry Pi systems cannot reboot or shut down. This needs to be removed from the automatic blacklist generated by the kernel build that ends up in /lib/modprobe.d/blacklist_linux_$(uname -r).conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766052/+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 1751243] Re: ubuntu_unionmount_overlayfs_suite failed with Bionic kernel
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751243 Title: ubuntu_unionmount_overlayfs_suite failed with Bionic kernel Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: In Progress Bug description: This issue can be found on different architectures of the Bionic kernel. Steps: 1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next 2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest 3. rm -fr autotest/client/tests 4. ln -sf ~/autotest-client-tests autotest/client/tests 5. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_qrt_kernel_security/control Result: * Command: ./run --ov Exit status: 1 Duration: 0.465664863586 stdout: *** *** ./run --ov --ts=0 open-plain *** TEST open-plain.py:10: Open O_RDONLY /mnt/a/foo100: File unexpectedly on union layer ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Fri Feb 23 09:57:36 2018 HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.171 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1751243/+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 1774126] Re: linux-oem: 4.13.0-1030.33 -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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774126 Title: linux-oem: 4.13.0-1030.33 -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: 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-oem package in Ubuntu: Invalid Status in linux-oem 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: 1774124 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774126/+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 1774407] [NEW] package linux-firmware 1.157.19 failed to install/upgrade: pacote linux-firmware já está instalado e configurado
Public bug reported: Installation of linux-firmware fails to update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.19 ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu May 31 09:06:02 2018 Dependencies: ErrorMessage: pacote linux-firmware já está instalado e configurado InstallationDate: Installed on 2018-04-09 (51 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-firmware Title: package linux-firmware 1.157.19 failed to install/upgrade: pacote linux-firmware já está instalado e configurado UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1774407 Title: package linux-firmware 1.157.19 failed to install/upgrade: pacote linux-firmware já está instalado e configurado Status in linux-firmware package in Ubuntu: New Bug description: Installation of linux-firmware fails to update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.19 ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu May 31 09:06:02 2018 Dependencies: ErrorMessage: pacote linux-firmware já está instalado e configurado InstallationDate: Installed on 2018-04-09 (51 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-firmware Title: package linux-firmware 1.157.19 failed to install/upgrade: pacote linux-firmware já está instalado e configurado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1774407/+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 1774406] 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/1774406 Title: package linux-headers-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: instalado linux-headers-4.15.0-22-generic paquete post-installation guión el subproceso devolvió un error con estado de salida 1 Status in linux package in Ubuntu: Confirmed Bug description: I am working in render in blender and popup this Notice ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-headers-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 AptOrdering: python3-apport:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu May 31 06:45:07 2018 ErrorMessage: instalado linux-headers-4.15.0-22-generic paquete post-installation guión el subproceso devolvió un error con estado de salida 1 HibernationDevice: RESUME=UUID=c7c7402c-dc17-4beb-82c2-c64e9085ad10 InstallationDate: Installed on 2017-10-24 (218 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. B85M-DS3H ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=f515d285-287f-46eb-8aa9-a0eb819d6aed ro quiet splash nomodeset 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.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8 RfKill: SourcePackage: linux Title: package linux-headers-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: instalado linux-headers-4.15.0-22-generic paquete post-installation guión el subproceso devolvió un error con estado de salida 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd08/25/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-DS3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-DS3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-DS3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774406/+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 1774190] Re: linux: 3.13.0-151.201 -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 => 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 backports: bug 1774191 (linux-lts-trusty) derivatives: - kernel-stable-phase-changed:Wednesday, 30. May 2018 14:31 UTC - kernel-stable-phase:Uploaded - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase-changed:Thursday, 31. May 2018 13:02 UTC + kernel-stable-phase:Promoted to 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 backports: bug 1774191 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase-changed:Thursday, 31. May 2018 13:02 UTC - kernel-stable-phase:Promoted to proposed + bugs-spammed: true + 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 in Ubuntu. https://bugs.launchpad.net/bugs/1774190 Title: linux: 3.13.0-151.201 -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: Confirmed 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 1774191 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: 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/1774190/+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 1774082] Re: Trusty cannot load microcode for family 17h AMD processors
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- trusty' to 'verification-done-trusty'. If the problem still exists, change the tag 'verification-needed-trusty' to 'verification-failed- trusty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1774082 Title: Trusty cannot load microcode for family 17h AMD processors Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Bug description: [Impact] AMD has recently updated the microcode in the linux-firmware tree for family 17h processors to address Spectre variant 2. The Trusty 3.13 kernel cannot load the microcode because it is missing a backport of upstream patch f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf which leaves AMD machines vulnerable. [Test Case (option 1)] Test must be done on a 17h family processor: 1) Take note of the microcode version before applying updated microcode: $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version 0x8001227 2) Get updated amd64-microcode package from the Ubuntu Security Team. Install it and reboot machine. 3) Verify that the microcode version has changed. [Test Case (option 2)] Alternate test case (useful in the situation that the test system is already running the latest microcode revision due to a BIOS update): 1) Fetch the latest 17h family microcode revision from here (you may want to verify the signature): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/amd-ucode/microcode_amd_fam17h.bin 2) Move it into /lib/firmware/amd-ucode/ 3) Force a microcode reload: $ echo 1 | sudo tee /sys/devices/system/cpu/microcode/reload 4) Verify that the following error message is *not* in your syslog: May 30 04:22:55 lodygin kernel: [ 388.290105] microcode: patch size mismatch May 30 04:22:55 lodygin kernel: [ 388.290149] microcode: Patch-ID 0x08001227: size mismatch. [Regression Potential] The regression potential to the kernel revolves around the fact that the IBRS/IBPB implementation in the 3.13 kernel may not have been put through its paces yet due to a lack of available microcode updates. There could be a latent bug present that is uncovered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774082/+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 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
Joshua R. Poulson: I will try reverting that patch, but I see the same behavior in Ubuntu-4.15.0-9.10 which I believe is before that commit. -- 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/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Triaged Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port, it usually shows only a blank screen after grub and I have to hard power off the laptop. The issue is present when the bios and grub are in mirror mode to both screens. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers This occurs with both a Dell U2515H using an HDMI cord, and a HP Compaq LA2405wg connected via HDMI-to-DVI adapter. WORKAROUND: Keep the monitor unplugged until the Ubuntu loading screen shows up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" But I tested without the acpi_osi parameter and see the same issue although the system now randomly crashes later on. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+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 1773906] Re: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick
I only use the internet key rarely, so it is hard for me to give any precise indication about when the issue was introduced. I would say that at the release of artful the issue was not there. Tested mainline 2.16 and it is OK. Correctly reports "setup of pktcdvd device failed" rather than oopsing. -- 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/1773906 Title: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick Status in linux package in Ubuntu: Incomplete Bug description: On insertion of a Huawei E173 mobile internet USB stick the artful kernel now oopses: BUG: unable to handle kernel NULL pointer dereference at 03d0 [ 633.710837] IP: pkt_setup_dev+0x2af/0x650 [pktcdvd] Issue seems to be related to the setup of the cdrom-like device hosted on the stick together with the UMTS modem. May possibly be due to some race as the usb stick configuration keeps changing until the device is properly switched to operate as a modem. Some of the times, UMTS modem remains detected notwithstanding the issue. After the issue, the system has problems in shutting down, though. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.13.0.43.46 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2654 F pulseaudio /dev/snd/controlC1: callegar 2654 F pulseaudio CurrentDesktop: KDE Date: Tue May 29 08:27:52 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c7dd5aac-abad-4cd0-9cac-552d49960853 InstallationDate: Installed on 2013-12-12 (1628 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-26 (214 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773906/+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 1774425] [NEW] i915 driver limits virtual resolution to 8192x8192
Public bug reported: I have an Intel Iris Pro 580 in my Intel Skull Canyon NUC6I7KYK, a nice little device that has 3 video outputs: * HDMI 2.0 * Mini DisplayPort * Thunderbolt USB-C The product specifications states that the device is able to output three 4K signals. Unfortunately, whenever I tried this in Ubuntu it failed, without any clear error message. After fiddling with other DEs, Kubuntu told me the virtual resolution was not supported. And indeed, as soon as I limited the virtual resolution of the 3 screens to fit in 8192x8192 pixels, all screens worked. Apparently, the i915 driver (in "drivers/gpu/drm/i915/intel_display.c") has not been updated for newer devices when reporting the maximum resolution. As you can see here: https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c#L14671 Only GEN_2 & GEN_3 are checked for, but since the 7th generation max virtual resolutions of 16384x16384 are supported. This issue has been reported to the i915 maintainers a few times, but nothing has changed yet :/ ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1774425 Title: i915 driver limits virtual resolution to 8192x8192 Status in linux package in Ubuntu: Incomplete Bug description: I have an Intel Iris Pro 580 in my Intel Skull Canyon NUC6I7KYK, a nice little device that has 3 video outputs: * HDMI 2.0 * Mini DisplayPort * Thunderbolt USB-C The product specifications states that the device is able to output three 4K signals. Unfortunately, whenever I tried this in Ubuntu it failed, without any clear error message. After fiddling with other DEs, Kubuntu told me the virtual resolution was not supported. And indeed, as soon as I limited the virtual resolution of the 3 screens to fit in 8192x8192 pixels, all screens worked. Apparently, the i915 driver (in "drivers/gpu/drm/i915/intel_display.c") has not been updated for newer devices when reporting the maximum resolution. As you can see here: https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c#L14671 Only GEN_2 & GEN_3 are checked for, but since the 7th generation max virtual resolutions of 16384x16384 are supported. This issue has been reported to the i915 maintainers a few times, but nothing has changed yet :/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774425/+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 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
well. I have just tested the proposed kernel (*) for 16.04. strangely my camera is not seen at all, there is not trace of any "UVC" activity in syslog/dmesh, and when I load the module "by hand" it does not detect any camera. only lsusb does. Am I still missing something? [4.4.0-128-generic #154], maybe this is wrong?] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1763748 Title: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50 Status in Dell Sputnik: New Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: In Progress Bug description: ===SRU Justification=== [Impact] UVC1.5 Realtek webcam on XPS 9370 does not work. [Test] Both the bug reporter and I can confirm the patch from Realtek works. [Fix] Use correct version control length for UVC1.5. [Regression Potential] Low. This only affects UVC1.5 webcams, which is quite rare in the wild. ===Original Bug Report=== The webcam is detected by the system, but no applications detect it. sudo lsusb -v: (relevant part) Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x58f4 bcdDevice 72.79 iManufacturer 3 CN0FFMHCLOG0081SB0M1A01 iProduct1 Integrated_Webcam_HD iSerial 2 200901010001 In syslog (firmware can be seen in first line - 1.50): Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new interface driver btusb Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query (129) UVC probe control : -75 (exp. 34). Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to initialize the device (-5). Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) ProblemType: Bug 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 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wgarcia2145 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 13 16:59:02 2018 HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc InstallationDate: Installed on 2018-04-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+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.
Re: [Kernel-packages] [Bug 1768208] Re: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
Ok. Here the result: assuming you only need the log files. Executed as stated: - ls /sys/class/backlight > backlight - grep -r . /proc/acpi > acpi - sudo acpidump -o acpidump.txt - acpixtract acpidump.txt - Please note this must be done after the prior command, as it uses the newly created acpidump.txt, in order to produce the files to attach DSDT.dat, SSDT1.dat, SSDT2.dat, and SSDT3.dat. - iasl -d DSDT.dat - Please note this must be done after the prior command, as it uses the newly created DSDT.dat to create the file to attach DSDT.dsl. - sudo fwts > fwts - sudo fwts method > fwts_method - sudo dmidecode > dmidecode.log On Mon, May 28, 2018 at 9:43 PM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > marvin: > > 1) Regarding the scaling and mouse issues, these are outside the scope of > this report. Hence, feel free to file a separate report about each one by > ensuring you have the package xdiagnose installed, and that you click the > Yes button for attaching additional debugging information via a terminal: > ubuntu-bug xorg > > 2) Regarding the scope of this report, could you please provide the > missing information from > https://wiki.ubuntu.com/Kernel/Debugging/Backlight? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1768208 > > Title: > [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > The screen brightness cannot be changed. > > In 16.04, I could change the brightness via: > xrandr --output eDP-1 --brightness 0.7 > > WORKAROUND: Execute at a terminal: > xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8 > > --- > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: marvin 1768 F pulseaudio > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 18.04 > HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 > MachineType: LENOVO 20FRS2M600 > Package: linux (not installed) > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > RelatedPackageVersions: >linux-restricted-modules-4.15.0-20-generic N/A >linux-backports-modules-4.15.0-20-generic N/A >linux-firmware 1.173 > Tags: bionic > Uname: Linux 4.15.0-20-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 06/23/2016 > dmi.bios.vendor: LENOVO > dmi.bios.version: N1FET41W (1.15 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 20FRS2M600 > dmi.board.vendor: LENOVO > dmi.board.version: Not Defined > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: None > dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO: > pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600: > rvrNotDefined:cvnLENOVO:ct10:cvrNone: > dmi.product.family: ThinkPad X1 Yoga 1st > dmi.product.name: 20FRS2M600 > dmi.product.version: ThinkPad X1 Yoga 1st > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1768208/+subscriptions > ** Attachment added: "results.log" https://bugs.launchpad.net/bugs/1768208/+attachment/5146961/+files/results.log ** Attachment added: "dmidecode.log" https://bugs.launchpad.net/bugs/1768208/+attachment/5146962/+files/dmidecode.log -- 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/1768208 Title: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness Status in linux package in Ubuntu: Incomplete Bug description: The screen brightness cannot be changed. In 16.04, I could change the brightness via: xrandr --output eDP-1 --brightness 0.7 WORKAROUND: Execute at a terminal: xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-ge
[Kernel-packages] [Bug 1774082] Re: Trusty cannot load microcode for family 17h AMD processors
I've tested 3.13.0-151.201-generic from trusty-proposed and was able to verify the fix via [Test Case (option 2)]. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-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/1774082 Title: Trusty cannot load microcode for family 17h AMD processors Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Bug description: [Impact] AMD has recently updated the microcode in the linux-firmware tree for family 17h processors to address Spectre variant 2. The Trusty 3.13 kernel cannot load the microcode because it is missing a backport of upstream patch f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf which leaves AMD machines vulnerable. [Test Case (option 1)] Test must be done on a 17h family processor: 1) Take note of the microcode version before applying updated microcode: $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version 0x8001227 2) Get updated amd64-microcode package from the Ubuntu Security Team. Install it and reboot machine. 3) Verify that the microcode version has changed. [Test Case (option 2)] Alternate test case (useful in the situation that the test system is already running the latest microcode revision due to a BIOS update): 1) Fetch the latest 17h family microcode revision from here (you may want to verify the signature): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/amd-ucode/microcode_amd_fam17h.bin 2) Move it into /lib/firmware/amd-ucode/ 3) Force a microcode reload: $ echo 1 | sudo tee /sys/devices/system/cpu/microcode/reload 4) Verify that the following error message is *not* in your syslog: May 30 04:22:55 lodygin kernel: [ 388.290105] microcode: patch size mismatch May 30 04:22:55 lodygin kernel: [ 388.290149] microcode: Patch-ID 0x08001227: size mismatch. [Regression Potential] The regression potential to the kernel revolves around the fact that the IBRS/IBPB implementation in the 3.13 kernel may not have been put through its paces yet due to a lack of available microcode updates. There could be a latent bug present that is uncovered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774082/+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 1774082] Re: Trusty cannot load microcode for family 17h AMD processors
It is also worth mentioning that I tested with the amd64-microcode 3.20180524.1~ubuntu0.14.04.1 package from the ubuntu-security- proposed/ppa. -- 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/1774082 Title: Trusty cannot load microcode for family 17h AMD processors Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Bug description: [Impact] AMD has recently updated the microcode in the linux-firmware tree for family 17h processors to address Spectre variant 2. The Trusty 3.13 kernel cannot load the microcode because it is missing a backport of upstream patch f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf which leaves AMD machines vulnerable. [Test Case (option 1)] Test must be done on a 17h family processor: 1) Take note of the microcode version before applying updated microcode: $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version 0x8001227 2) Get updated amd64-microcode package from the Ubuntu Security Team. Install it and reboot machine. 3) Verify that the microcode version has changed. [Test Case (option 2)] Alternate test case (useful in the situation that the test system is already running the latest microcode revision due to a BIOS update): 1) Fetch the latest 17h family microcode revision from here (you may want to verify the signature): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/amd-ucode/microcode_amd_fam17h.bin 2) Move it into /lib/firmware/amd-ucode/ 3) Force a microcode reload: $ echo 1 | sudo tee /sys/devices/system/cpu/microcode/reload 4) Verify that the following error message is *not* in your syslog: May 30 04:22:55 lodygin kernel: [ 388.290105] microcode: patch size mismatch May 30 04:22:55 lodygin kernel: [ 388.290149] microcode: Patch-ID 0x08001227: size mismatch. [Regression Potential] The regression potential to the kernel revolves around the fact that the IBRS/IBPB implementation in the 3.13 kernel may not have been put through its paces yet due to a lack of available microcode updates. There could be a latent bug present that is uncovered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774082/+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 1774425] 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 1774425 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/1774425 Title: i915 driver limits virtual resolution to 8192x8192 Status in linux package in Ubuntu: Incomplete Bug description: I have an Intel Iris Pro 580 in my Intel Skull Canyon NUC6I7KYK, a nice little device that has 3 video outputs: * HDMI 2.0 * Mini DisplayPort * Thunderbolt USB-C The product specifications states that the device is able to output three 4K signals. Unfortunately, whenever I tried this in Ubuntu it failed, without any clear error message. After fiddling with other DEs, Kubuntu told me the virtual resolution was not supported. And indeed, as soon as I limited the virtual resolution of the 3 screens to fit in 8192x8192 pixels, all screens worked. Apparently, the i915 driver (in "drivers/gpu/drm/i915/intel_display.c") has not been updated for newer devices when reporting the maximum resolution. As you can see here: https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c#L14671 Only GEN_2 & GEN_3 are checked for, but since the 7th generation max virtual resolutions of 16384x16384 are supported. This issue has been reported to the i915 maintainers a few times, but nothing has changed yet :/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774425/+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 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
** Tags removed: needs-reverse-bisect ** Tags added: needs-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/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Triaged Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port, it usually shows only a blank screen after grub and I have to hard power off the laptop. The issue is present when the bios and grub are in mirror mode to both screens. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers This occurs with both a Dell U2515H using an HDMI cord, and a HP Compaq LA2405wg connected via HDMI-to-DVI adapter. WORKAROUND: Keep the monitor unplugged until the Ubuntu loading screen shows up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" But I tested without the acpi_osi parameter and see the same issue although the system now randomly crashes later on. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+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 1772940] Re: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1772940 Title: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid 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-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1772927 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/1772940/+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 1773718] Re: mouse ponter disappear after screen off
Hi, I've seen this problem since I install linux in this computer (2 years ago), but my workaround was to use the nvidia propietary driver. Now that nvidia stop developing the 304 driver, I will have to use nouveau. I installed 4.17.0-041700rc7-generic and the problem still is there. It might be that I had to wait a couple of minutes more oafter the screen switch off or suspended, but the problem is still there. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream ** Summary changed: - mouse ponter disappear after screen off + mouse pointer disappear after screen off -- 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/1773718 Title: mouse pointer disappear after screen off Status in linux package in Ubuntu: Confirmed Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+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 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
Well, you are not wrong. There's one missing commit for Xenial. I've already filed LP: #1773905 for that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1763748 Title: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50 Status in Dell Sputnik: New Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: In Progress Bug description: ===SRU Justification=== [Impact] UVC1.5 Realtek webcam on XPS 9370 does not work. [Test] Both the bug reporter and I can confirm the patch from Realtek works. [Fix] Use correct version control length for UVC1.5. [Regression Potential] Low. This only affects UVC1.5 webcams, which is quite rare in the wild. ===Original Bug Report=== The webcam is detected by the system, but no applications detect it. sudo lsusb -v: (relevant part) Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x58f4 bcdDevice 72.79 iManufacturer 3 CN0FFMHCLOG0081SB0M1A01 iProduct1 Integrated_Webcam_HD iSerial 2 200901010001 In syslog (firmware can be seen in first line - 1.50): Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new interface driver btusb Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query (129) UVC probe control : -75 (exp. 34). Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to initialize the device (-5). Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) ProblemType: Bug 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 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wgarcia2145 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 13 16:59:02 2018 HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc InstallationDate: Installed on 2018-04-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+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 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50
Ok thanks, sorry. Now I understand the meaning of your message #47. I'll wait. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1763748 Title: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50 Status in Dell Sputnik: New Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux-oem source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Status in linux-oem source package in Artful: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: In Progress Bug description: ===SRU Justification=== [Impact] UVC1.5 Realtek webcam on XPS 9370 does not work. [Test] Both the bug reporter and I can confirm the patch from Realtek works. [Fix] Use correct version control length for UVC1.5. [Regression Potential] Low. This only affects UVC1.5 webcams, which is quite rare in the wild. ===Original Bug Report=== The webcam is detected by the system, but no applications detect it. sudo lsusb -v: (relevant part) Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.01 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 ? bDeviceProtocol 1 Interface Association bMaxPacketSize064 idVendor 0x0bda Realtek Semiconductor Corp. idProduct 0x58f4 bcdDevice 72.79 iManufacturer 3 CN0FFMHCLOG0081SB0M1A01 iProduct1 Integrated_Webcam_HD iSerial 2 200901010001 In syslog (firmware can be seen in first line - 1.50): Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new interface driver btusb Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround. Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query (129) UVC probe control : -75 (exp. 34). Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to initialize the device (-5). Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video format 0032-0002-0010-8000-00aa00389b71 Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:58f4) ProblemType: Bug 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 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wgarcia2145 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Apr 13 16:59:02 2018 HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc InstallationDate: Installed on 2018-04-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1763748/+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 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
1849f80 has the bug.
--
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/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
discovered
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Artful:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
See attached dmesg outputs for booting kernels 4.11.x (working) and
4.13.x (not working).
dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have
been discovered by the kernel. The btrfs RAID1 filesystem mounts, and
everything is good.
dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
btrfs scans for devices after only 2 (sda, sdb) of the devices have been
discovered by the kernel. The btrfs RAID1 filesystem fails to mount ("failed
to read the system array: -5"). The remaining 2 devices (sdc, sdd) are
discovered by the kernel immediately afterward. At the end of the log, I run
`btrfs device scan` and mount the filesystem manually.
Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: aplay: device_list:270: no soundcards found...
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
ArecordDevices: arecord: device_list:270: no soundcards found...
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2015-10-15 (933 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: HP ProLiant MicroServer Gen8
Package: linux (not installed)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@
rootdelay=10
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Tags: bionic apport-hook-error
Uname: Linux 4.15.0-20-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 07/16/2015
dmi.bios.vendor: HP
dmi.bios.version: J06
dmi.chassis.type: 7
dmi.chassis.vendor: HP
dmi.modalias:
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen8
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1769120] Re: [Dell Precision 5520] wifi is very unreliable to connect over b and g protocol
network module: 01:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter is this issue still there after cold boot ? -- 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/1769120 Title: [Dell Precision 5520] wifi is very unreliable to connect over b and g protocol Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: Dell Precision 5520 (CID 201610-25144) pre-installed (oem) image (16.04) [Description] When the wifi tries to connect SSID over b and g protocol, it is very hard to build connection successfully. The reproducing rate is 9/10. [Steps to Reproduce] 1. Update the system to use the last stack. 2. Reboot 3. Connect the bg wifi by network-manager applet [Expected Result] The network-manager builds the connection. [Actual Result] The network-manger could not connect to the target SSID. - ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1972 F pulseaudio Date: Fri May 4 19:16:50 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=395dc72d-da55-4d11-8875-2240537ead7f InstallationDate: Installed on 2018-05-04 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-123-generic.efi.signed root=UUID=f71a7ab1-fcc5-4873-839b-1b7955196b53 ro automatic-oem-config quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.18 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.4 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1769120/+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 1774127] Re: linux-gcp: 4.13.0-1019.23 -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: 1774124 phase: Packaging + kernel-stable-phase-changed:Thursday, 31. May 2018 16:33 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: 1774124 - phase: Packaging - kernel-stable-phase-changed:Thursday, 31. May 2018 16:33 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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1774127 Title: linux-gcp: 4.13.0-1019.23 -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: Invalid 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 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-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- kernel-stable-master-bug: 1774124 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774127/+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 1772940] Re: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1772940 Title: linux-azure: 4.15.0-1013.13~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid 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-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-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-azure package in Ubuntu: Invalid Status in linux-azure 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: 1772927 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/1772940/+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 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
I got some help from #ubuntu-kernel Thadeu Cascardo suggested I try drm.debug=0x4 The crash seems to happen every time when the laptop has been off for a while, but sometimes it doesn't if I power it down then bootup. So I captured two logs attached, one where the system booted normally, and one where it crashed. ** Attachment added: "drm.debug.0x4_crash.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+attachment/5147054/+files/drm.debug.0x4_crash.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/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Triaged Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port, it usually shows only a blank screen after grub and I have to hard power off the laptop. The issue is present when the bios and grub are in mirror mode to both screens. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers This occurs with both a Dell U2515H using an HDMI cord, and a HP Compaq LA2405wg connected via HDMI-to-DVI adapter. WORKAROUND: Keep the monitor unplugged until the Ubuntu loading screen shows up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" But I tested without the acpi_osi parameter and see the same issue although the system now randomly crashes later on. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+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 1768139] Re: Kernel crash when booting laptop with hdmi monitor connected
** Attachment added: "drm.debug.0x4_nocrash.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+attachment/5147056/+files/drm.debug.0x4_nocrash.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/1768139 Title: Kernel crash when booting laptop with hdmi monitor connected Status in linux package in Ubuntu: Triaged Bug description: When I boot a Dell Inspiron 7559 with an external monitor connected to the hdmi port, it usually shows only a blank screen after grub and I have to hard power off the laptop. The issue is present when the bios and grub are in mirror mode to both screens. I can see the following stack trace in journalctl: syslog contains: kernel: Missing switch case (6) in intel_prepare_dp_ddi_buffers This occurs with both a Dell U2515H using an HDMI cord, and a HP Compaq LA2405wg connected via HDMI-to-DVI adapter. WORKAROUND: Keep the monitor unplugged until the Ubuntu loading screen shows up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:22:20 2018 InstallationDate: Installed on 2018-04-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) This is a fresh install. I have modified grub defaults to include "acpi_osi=!Windows 2015" But I tested without the acpi_osi parameter and see the same issue although the system now randomly crashes later on. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apatterson 1965 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=7b947b8e-de50-4ab6-b7f3-254a5dea924a InstallationDate: Installed on 2018-04-28 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7559 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=77f1cfec-1fe4-4201-9a91-9f00a5d7782b ro quiet splash "acpi_osi=!Windows 2015" ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic wayland-session Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd09/26/2017:svnDellInc.:pnInspiron7559:pvr1.2.5:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768139/+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 1774466] [NEW] hisi_sas robustness fixes
Public bug reported: [Impact] Several issues have been uncovered during testing. [Test Case] Not all of these changes have a reliable reproducer - some are corner cases hit during error recovery, etc. However, we can regression test w/ e.g. iozone3 on the two Ubuntu-supported platforms that use this device, as well as remove/reload the module to make sure those tests survive. [Fix] All fixes here are upstream cherry-picks - see the individual commits for details. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774466 Title: hisi_sas robustness fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] Several issues have been uncovered during testing. [Test Case] Not all of these changes have a reliable reproducer - some are corner cases hit during error recovery, etc. However, we can regression test w/ e.g. iozone3 on the two Ubuntu-supported platforms that use this device, as well as remove/reload the module to make sure those tests survive. [Fix] All fixes here are upstream cherry-picks - see the individual commits for details. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774466/+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 1768099] Re: linux-azure-edge headers have bad symlinks
*** This bug is a duplicate of bug 1772058 *** https://bugs.launchpad.net/bugs/1772058 ** Changed in: linux-azure (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1768099 Title: linux-azure-edge headers have bad symlinks Status in linux-azure package in Ubuntu: Fix Released Bug description: Note that the symlinks point to "linux-azure-edge-headers" but the directory is actually named "linux-azure-headers". This breaks DKMS modules. jrp@jrpcudau:/usr/src/linux-headers-4.15.0-1006-azure$ ls -l total 940 drwxr-xr-x 3 root root 4096 Apr 19 16:06 arch lrwxrwxrwx 1 root root 45 Apr 18 23:07 block -> ../linux-azure-edge-headers-4.15.0-1006/block lrwxrwxrwx 1 root root 45 Apr 18 23:07 certs -> ../linux-azure-edge-headers-4.15.0-1006/certs lrwxrwxrwx 1 root root 46 Apr 18 23:07 crypto -> ../linux-azure-edge-headers-4.15.0-1006/crypto lrwxrwxrwx 1 root root 53 Apr 18 23:07 Documentation -> ../linux-azure-edge-headers-4.15.0-1006/Documentation lrwxrwxrwx 1 root root 47 Apr 18 23:07 drivers -> ../linux-azure-edge-headers-4.15.0-1006/drivers lrwxrwxrwx 1 root root 48 Apr 18 23:07 firmware -> ../linux-azure-edge-headers-4.15.0-1006/firmware lrwxrwxrwx 1 root root 42 Apr 18 23:07 fs -> ../linux-azure-edge-headers-4.15.0-1006/fs drwxr-xr-x 4 root root 4096 Apr 19 16:06 include lrwxrwxrwx 1 root root 44 Apr 18 23:07 init -> ../linux-azure-edge-headers-4.15.0-1006/init lrwxrwxrwx 1 root root 43 Apr 18 23:07 ipc -> ../linux-azure-edge-headers-4.15.0-1006/ipc lrwxrwxrwx 1 root root 46 Apr 18 23:07 Kbuild -> ../linux-azure-edge-headers-4.15.0-1006/Kbuild lrwxrwxrwx 1 root root 47 Apr 18 23:07 Kconfig -> ../linux-azure-edge-headers-4.15.0-1006/Kconfig drwxr-xr-x 2 root root 4096 Apr 19 16:06 kernel lrwxrwxrwx 1 root root 43 Apr 18 23:07 lib -> ../linux-azure-edge-headers-4.15.0-1006/lib lrwxrwxrwx 1 root root 48 Apr 18 23:07 Makefile -> ../linux-azure-edge-headers-4.15.0-1006/Makefile lrwxrwxrwx 1 root root 42 Apr 18 23:07 mm -> ../linux-azure-edge-headers-4.15.0-1006/mm -rw-r--r-- 1 root root 930941 Apr 18 23:08 Module.symvers lrwxrwxrwx 1 root root 43 Apr 18 23:07 net -> ../linux-azure-edge-headers-4.15.0-1006/net lrwxrwxrwx 1 root root 47 Apr 18 23:07 samples -> ../linux-azure-edge-headers-4.15.0-1006/samples drwxr-xr-x 6 root root 12288 Apr 19 16:06 scripts lrwxrwxrwx 1 root root 48 Apr 18 23:07 security -> ../linux-azure-edge-headers-4.15.0-1006/security lrwxrwxrwx 1 root root 45 Apr 18 23:07 sound -> ../linux-azure-edge-headers-4.15.0-1006/sound lrwxrwxrwx 1 root root 43 Apr 18 23:07 spl -> ../linux-azure-edge-headers-4.15.0-1006/spl drwxr-xr-x 3 root root 4096 Apr 19 16:06 tools lrwxrwxrwx 1 root root 46 Apr 18 23:07 ubuntu -> ../linux-azure-edge-headers-4.15.0-1006/ubuntu lrwxrwxrwx 1 root root 43 Apr 18 23:07 usr -> ../linux-azure-edge-headers-4.15.0-1006/usr lrwxrwxrwx 1 root root 44 Apr 18 23:07 virt -> ../linux-azure-edge-headers-4.15.0-1006/virt lrwxrwxrwx 1 root root 43 Apr 18 23:07 zfs -> ../linux-azure-edge-headers-4.15.0-1006/zfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1768099/+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 1774466] 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 1774466 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 ** Changed in: linux (Ubuntu Bionic) 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/1774466 Title: hisi_sas robustness fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] Several issues have been uncovered during testing. [Test Case] Not all of these changes have a reliable reproducer - some are corner cases hit during error recovery, etc. However, we can regression test w/ e.g. iozone3 on the two Ubuntu-supported platforms that use this device, as well as remove/reload the module to make sure those tests survive. [Fix] All fixes here are upstream cherry-picks - see the individual commits for details. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774466/+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 1768099] Re: linux-azure-edge headers have bad symlinks
*** This bug is a duplicate of bug 1772058 *** https://bugs.launchpad.net/bugs/1772058 ** This bug has been marked a duplicate of bug 1772058 linux-azure-edge headers are broken after change to support scripted rebases -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1768099 Title: linux-azure-edge headers have bad symlinks Status in linux-azure package in Ubuntu: Fix Released Bug description: Note that the symlinks point to "linux-azure-edge-headers" but the directory is actually named "linux-azure-headers". This breaks DKMS modules. jrp@jrpcudau:/usr/src/linux-headers-4.15.0-1006-azure$ ls -l total 940 drwxr-xr-x 3 root root 4096 Apr 19 16:06 arch lrwxrwxrwx 1 root root 45 Apr 18 23:07 block -> ../linux-azure-edge-headers-4.15.0-1006/block lrwxrwxrwx 1 root root 45 Apr 18 23:07 certs -> ../linux-azure-edge-headers-4.15.0-1006/certs lrwxrwxrwx 1 root root 46 Apr 18 23:07 crypto -> ../linux-azure-edge-headers-4.15.0-1006/crypto lrwxrwxrwx 1 root root 53 Apr 18 23:07 Documentation -> ../linux-azure-edge-headers-4.15.0-1006/Documentation lrwxrwxrwx 1 root root 47 Apr 18 23:07 drivers -> ../linux-azure-edge-headers-4.15.0-1006/drivers lrwxrwxrwx 1 root root 48 Apr 18 23:07 firmware -> ../linux-azure-edge-headers-4.15.0-1006/firmware lrwxrwxrwx 1 root root 42 Apr 18 23:07 fs -> ../linux-azure-edge-headers-4.15.0-1006/fs drwxr-xr-x 4 root root 4096 Apr 19 16:06 include lrwxrwxrwx 1 root root 44 Apr 18 23:07 init -> ../linux-azure-edge-headers-4.15.0-1006/init lrwxrwxrwx 1 root root 43 Apr 18 23:07 ipc -> ../linux-azure-edge-headers-4.15.0-1006/ipc lrwxrwxrwx 1 root root 46 Apr 18 23:07 Kbuild -> ../linux-azure-edge-headers-4.15.0-1006/Kbuild lrwxrwxrwx 1 root root 47 Apr 18 23:07 Kconfig -> ../linux-azure-edge-headers-4.15.0-1006/Kconfig drwxr-xr-x 2 root root 4096 Apr 19 16:06 kernel lrwxrwxrwx 1 root root 43 Apr 18 23:07 lib -> ../linux-azure-edge-headers-4.15.0-1006/lib lrwxrwxrwx 1 root root 48 Apr 18 23:07 Makefile -> ../linux-azure-edge-headers-4.15.0-1006/Makefile lrwxrwxrwx 1 root root 42 Apr 18 23:07 mm -> ../linux-azure-edge-headers-4.15.0-1006/mm -rw-r--r-- 1 root root 930941 Apr 18 23:08 Module.symvers lrwxrwxrwx 1 root root 43 Apr 18 23:07 net -> ../linux-azure-edge-headers-4.15.0-1006/net lrwxrwxrwx 1 root root 47 Apr 18 23:07 samples -> ../linux-azure-edge-headers-4.15.0-1006/samples drwxr-xr-x 6 root root 12288 Apr 19 16:06 scripts lrwxrwxrwx 1 root root 48 Apr 18 23:07 security -> ../linux-azure-edge-headers-4.15.0-1006/security lrwxrwxrwx 1 root root 45 Apr 18 23:07 sound -> ../linux-azure-edge-headers-4.15.0-1006/sound lrwxrwxrwx 1 root root 43 Apr 18 23:07 spl -> ../linux-azure-edge-headers-4.15.0-1006/spl drwxr-xr-x 3 root root 4096 Apr 19 16:06 tools lrwxrwxrwx 1 root root 46 Apr 18 23:07 ubuntu -> ../linux-azure-edge-headers-4.15.0-1006/ubuntu lrwxrwxrwx 1 root root 43 Apr 18 23:07 usr -> ../linux-azure-edge-headers-4.15.0-1006/usr lrwxrwxrwx 1 root root 44 Apr 18 23:07 virt -> ../linux-azure-edge-headers-4.15.0-1006/virt lrwxrwxrwx 1 root root 43 Apr 18 23:07 zfs -> ../linux-azure-edge-headers-4.15.0-1006/zfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1768099/+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 1774467] [NEW] hisi_sas: Support newer v3 hardware
Public bug reported: [Impact] Changes in the hisi_sas v3 hardware design require corresponding changes in the driver. [Test Case] I don't have a way to inject these errors, so testing here will be limited to regression testing on the two Ubuntu-supported platforms that have hisi_sas controllers (D05/D06). [Fix] Include various cherry-picks from upstream that add the necessary support. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774467 Title: hisi_sas: Support newer v3 hardware Status in linux package in Ubuntu: New Bug description: [Impact] Changes in the hisi_sas v3 hardware design require corresponding changes in the driver. [Test Case] I don't have a way to inject these errors, so testing here will be limited to regression testing on the two Ubuntu-supported platforms that have hisi_sas controllers (D05/D06). [Fix] Include various cherry-picks from upstream that add the necessary support. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774467/+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 1774466] Re: hisi_sas robustness fixes
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Description changed: [Impact] Several issues have been uncovered during testing. [Test Case] - Not all of these changes have a reliable reproducer - some are corner cases hit during error recovery, etc. However, we can regression test w/ e.g. iozone3 on the two Ubuntu-supported platforms that use this device, as well as remove/reload the module to make sure those tests survive. + Not all of these changes have a reliable reproducer - some are corner cases hit during error recovery, etc. However, we can regression test w/ e.g. iozone3 on the two Ubuntu-supported platforms that use this device, as well as remove/reload the module, which is a trigger for some of these issues. [Fix] All fixes here are upstream cherry-picks - see the individual commits for details. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. -- 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/1774466 Title: hisi_sas robustness fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] Several issues have been uncovered during testing. [Test Case] Not all of these changes have a reliable reproducer - some are corner cases hit during error recovery, etc. However, we can regression test w/ e.g. iozone3 on the two Ubuntu-supported platforms that use this device, as well as remove/reload the module, which is a trigger for some of these issues. [Fix] All fixes here are upstream cherry-picks - see the individual commits for details. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774466/+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 1774471] [NEW] Various fixes for CXL kernel module
You have been subscribed to a public bug: ---Problem Description--- Couple of CXL patches need to be merged to Ubuntu 18.04.1 kernel source tree. They fix various issues found after the 18.04 kernel freeze: 401dca8cbd14 cxl: Set the PBCQ Tunnel BAR register when enabling capi mode 497a0790e2c6 cxl: Report the tunneled operations status ad7b4e8022b9 cxl: Fix possible deadlock when processing page faults from cxllib 02b63b420223 cxl: Remove function write_timebase_ctrl_psl9() for PSL9 cxl: Configure PSL to not use APC virtual machines : http://patchwork.ozlabs.org/patch/899062/ cxl: Disable prefault_mode in Radix mode : http://patchwork.ozlabs.org/patch/916159/ ---uname output--- 4.15.0-12-generic ---Additional Hardware Info--- a compatible capi FPGA adapter Machine Type = Boston-LC ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-168467 severity-high targetmilestone-inin1804 -- Various fixes for CXL kernel module https://bugs.launchpad.net/bugs/1774471 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1774471] [NEW] Various fixes for CXL kernel module
Public bug reported: ---Problem Description--- Couple of CXL patches need to be merged to Ubuntu 18.04.1 kernel source tree. They fix various issues found after the 18.04 kernel freeze: 401dca8cbd14 cxl: Set the PBCQ Tunnel BAR register when enabling capi mode 497a0790e2c6 cxl: Report the tunneled operations status ad7b4e8022b9 cxl: Fix possible deadlock when processing page faults from cxllib 02b63b420223 cxl: Remove function write_timebase_ctrl_psl9() for PSL9 cxl: Configure PSL to not use APC virtual machines : http://patchwork.ozlabs.org/patch/899062/ cxl: Disable prefault_mode in Radix mode : http://patchwork.ozlabs.org/patch/916159/ ---uname output--- 4.15.0-12-generic ---Additional Hardware Info--- a compatible capi FPGA adapter Machine Type = Boston-LC ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-168467 severity-high targetmilestone-inin1804 ** Tags added: architecture-ppc64le bugnameltc-168467 severity-high targetmilestone-inin1804 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- 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/1774471 Title: Various fixes for CXL kernel module Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Couple of CXL patches need to be merged to Ubuntu 18.04.1 kernel source tree. They fix various issues found after the 18.04 kernel freeze: 401dca8cbd14 cxl: Set the PBCQ Tunnel BAR register when enabling capi mode 497a0790e2c6 cxl: Report the tunneled operations status ad7b4e8022b9 cxl: Fix possible deadlock when processing page faults from cxllib 02b63b420223 cxl: Remove function write_timebase_ctrl_psl9() for PSL9 cxl: Configure PSL to not use APC virtual machines : http://patchwork.ozlabs.org/patch/899062/ cxl: Disable prefault_mode in Radix mode : http://patchwork.ozlabs.org/patch/916159/ ---uname output--- 4.15.0-12-generic ---Additional Hardware Info--- a compatible capi FPGA adapter Machine Type = Boston-LC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774471/+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 1774467] Re: hisi_sas: Support newer v3 hardware
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774467 Title: hisi_sas: Support newer v3 hardware Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] Changes in the hisi_sas v3 hardware design require corresponding changes in the driver. [Test Case] I don't have a way to inject these errors, so testing here will be limited to regression testing on the two Ubuntu-supported platforms that have hisi_sas controllers (D05/D06). [Fix] Include various cherry-picks from upstream that add the necessary support. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774467/+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 1774472] [NEW] hisi_sas: improve performance by optimizing DQ locking
Public bug reported: [Impact] The way the driver deals with locking the DQ causes performance to suffer. [Test Case] Run iozone3 and validate performance is >= previous. [Fix] Once a DQ slot is allocated, it must be used. So, currently the driver locks the DQ while it builds and sends each task to the hardware, just in case there is a failure, so that it can reuse that slot. However - there is a point at which we the build/send is guaranteed to succeed, so we can release the lock at that point allowing new slots to be allocated. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1774472 Title: hisi_sas: improve performance by optimizing DQ locking Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The way the driver deals with locking the DQ causes performance to suffer. [Test Case] Run iozone3 and validate performance is >= previous. [Fix] Once a DQ slot is allocated, it must be used. So, currently the driver locks the DQ while it builds and sends each task to the hardware, just in case there is a failure, so that it can reuse that slot. However - there is a point at which we the build/send is guaranteed to succeed, so we can release the lock at that point allowing new slots to be allocated. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774472/+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 1774472] 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 1774472 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/1774472 Title: hisi_sas: improve performance by optimizing DQ locking Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The way the driver deals with locking the DQ causes performance to suffer. [Test Case] Run iozone3 and validate performance is >= previous. [Fix] Once a DQ slot is allocated, it must be used. So, currently the driver locks the DQ while it builds and sends each task to the hardware, just in case there is a failure, so that it can reuse that slot. However - there is a point at which we the build/send is guaranteed to succeed, so we can release the lock at that point allowing new slots to be allocated. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774472/+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 1773520] Re: After update to 4.13-43 Intel Graphics are Laggy
Hi Joseph Linux hp-green 4.13.0-45-generic #51~lp1773520 SMP Wed May 30 17:15:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Just tried that one and it fixes the issue, I haven't had a chance to test the second yet, but will try later tonight hopefully Regards James -- 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/1773520 Title: After update to 4.13-43 Intel Graphics are Laggy Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: After update to Kernel 4.13-43 the intel graphics seem to really lag - especially noticeable in apps which are using vsync, which, at least on my system, locks to 40fps unlike the previous kernel I have installed (4.13-41) which locks at a steady 60fps. See https://askubuntu.com/questions/1039189/today-i-got-an-update-and- graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for some other users with the same issue In short 4.13-41 doesn't have the problem 4.13-43 has the laggy problem --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 2835 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ac1331a0-15f2-4832-aebc-48e3ad655add InstallationDate: Installed on 2016-05-31 (724 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Gaming Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.157.18 Tags: xenial Uname: Linux 4.13.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker libvirtd lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/16/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A9 dmi.board.vendor: HP dmi.board.version: 91.18 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd09/16/2015:svnHP:pnHPPavilionGamingNotebook:pvrType1ProductConfigId:rvnHP:rn80A9:rvr91.18:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Gaming Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773520/+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 1774126] Re: linux-oem: 4.13.0-1030.33 -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 => 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: 1774124 phase: Uploaded + kernel-stable-phase-changed:Thursday, 31. May 2018 18:03 UTC + kernel-stable-phase:Promoted to 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: 1774124 - phase: Uploaded - kernel-stable-phase-changed:Thursday, 31. May 2018 18:03 UTC - kernel-stable-phase:Promoted to proposed + 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774126 Title: linux-oem: 4.13.0-1030.33 -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: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1774124 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/1774126/+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 1774471] Re: Various fixes for CXL kernel module
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: triage-g -- 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/1774471 Title: Various fixes for CXL kernel module Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Couple of CXL patches need to be merged to Ubuntu 18.04.1 kernel source tree. They fix various issues found after the 18.04 kernel freeze: 401dca8cbd14 cxl: Set the PBCQ Tunnel BAR register when enabling capi mode 497a0790e2c6 cxl: Report the tunneled operations status ad7b4e8022b9 cxl: Fix possible deadlock when processing page faults from cxllib 02b63b420223 cxl: Remove function write_timebase_ctrl_psl9() for PSL9 cxl: Configure PSL to not use APC virtual machines : http://patchwork.ozlabs.org/patch/899062/ cxl: Disable prefault_mode in Radix mode : http://patchwork.ozlabs.org/patch/916159/ ---uname output--- 4.15.0-12-generic ---Additional Hardware Info--- a compatible capi FPGA adapter Machine Type = Boston-LC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1774471/+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 1521173] Re: AER: Corrected error received: id=00e0
I have this error on my Asus X541U, with Ubuntu 18.04, please solve it. It generates an endless list with this error: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID) device [8086:9d15] error status/mask=0001/2000 And I can't log in. And it is related to the Wi-Fi board of my PC, which is the following:Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Triaged Bug description: Note: Current workaround is to add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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 1773643] Re: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working
Hello, I have dowlowded a deb archive and install it but after start, the test kernel is not present to in the menu if I type shift key on startup to show grub I have just tested git kernel git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git /mainline-crack v4.17-rc7 but when I tried to compile the kernel I get this error make menuconfig *** Unable to find the ncurses libraries or the *** required header files. *** 'make menuconfig' requires the ncurses libraries. *** *** Install ncurses (ncurses-devel or libncurses-dev *** depending on your distribution) and try again. *** scripts/kconfig/Makefile:219: recipe for target 'scripts/kconfig/dochecklxdialog' failed make[1]: *** [scripts/kconfig/dochecklxdialog] Error 1 Makefile:528: recipe for target 'menuconfig' failed make: *** [menuconfig] Error 2 mparchet@battant-why:~/src/v4.17-rc7$ make menuconfig *** Unable to find the ncurses libraries or the *** required header files. *** 'make menuconfig' requires the ncurses libraries. *** *** Install ncurses (ncurses-devel or libncurses-dev *** depending on your distribution) and try again. *** scripts/kconfig/Makefile:219: recipe for target 'scripts/kconfig/dochecklxdialog' failed make[1]: *** [scripts/kconfig/dochecklxdialog] Error 1 Makefile:528: recipe for target 'menuconfig' failed make: *** [menuconfig] Error 2 mparchet@battant-why:~/src/v4.17-rc7$ make menuconfig *** Unable to find the ncurses libraries or the *** required header files. *** 'make menuconfig' requires the ncurses libraries. *** *** Install ncurses (ncurses-devel or libncurses-dev *** depending on your distribution) and try again. *** scripts/kconfig/Makefile:219: recipe for target 'scripts/kconfig/dochecklxdialog' failed make[1]: *** [scripts/kconfig/dochecklxdialog] Error 1 Makefile:528: recipe for target 'menuconfig' failed make: *** [menuconfig] Error 2 Could you help me please ? Thanks for your support Best regards Battant -- 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/1773643 Title: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Since long time my [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working For more information see this link bellow https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068 Could you help me to fix this bug ? Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 27 13:21:46 2018 InstallationDate: Installed on 2018-04-29 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. --- ApportVersion: 2.20.9-0ubuntu7
[Kernel-packages] [Bug 1774484] [NEW] package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127
Public bug reported: The failure has something to do with live patch ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Tue May 29 09:03:40 2018 Dependencies: DuplicateSignature: package:linux-firmware:1.173.1 Setting up linux-firmware (1.173.1) ... awk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: UP dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 127 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-firmware Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1774484 Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127 Status in linux-firmware package in Ubuntu: New Bug description: The failure has something to do with live patch ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Tue May 29 09:03:40 2018 Dependencies: DuplicateSignature: package:linux-firmware:1.173.1 Setting up linux-firmware (1.173.1) ... awk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: UP dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 127 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-firmware Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1774484/+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 1774484] Re: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1774484 Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127 Status in linux-firmware package in Ubuntu: New Bug description: The failure has something to do with live patch ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Tue May 29 09:03:40 2018 Dependencies: DuplicateSignature: package:linux-firmware:1.173.1 Setting up linux-firmware (1.173.1) ... awk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: UP dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 127 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 127 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: linux-firmware Title: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1774484/+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 1774191] Re: linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker
** 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 => 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: 1774190 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Thursday, 31. May 2018 19: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: 1774190 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Thursday, 31. May 2018 19: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-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1774191 Title: linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid 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: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1774190 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/1774191/+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 1773520] Re: After update to 4.13-43 Intel Graphics are Laggy
Just to update, have tested the 4.15 kernel as well and that is also working well and doesn't show the 40fps lag/slowdown issue Regards James -- 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/1773520 Title: After update to 4.13-43 Intel Graphics are Laggy Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: After update to Kernel 4.13-43 the intel graphics seem to really lag - especially noticeable in apps which are using vsync, which, at least on my system, locks to 40fps unlike the previous kernel I have installed (4.13-41) which locks at a steady 60fps. See https://askubuntu.com/questions/1039189/today-i-got-an-update-and- graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for some other users with the same issue In short 4.13-41 doesn't have the problem 4.13-43 has the laggy problem --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 2835 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ac1331a0-15f2-4832-aebc-48e3ad655add InstallationDate: Installed on 2016-05-31 (724 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Gaming Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.157.18 Tags: xenial Uname: Linux 4.13.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker libvirtd lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/16/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A9 dmi.board.vendor: HP dmi.board.version: 91.18 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd09/16/2015:svnHP:pnHPPavilionGamingNotebook:pvrType1ProductConfigId:rvnHP:rn80A9:rvr91.18:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Gaming Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773520/+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 1774472] Re: hisi_sas: improve performance by optimizing DQ locking
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- 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/1774472 Title: hisi_sas: improve performance by optimizing DQ locking Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: [Impact] The way the driver deals with locking the DQ causes performance to suffer. [Test Case] Run iozone3 and validate performance is >= previous. [Fix] Once a DQ slot is allocated, it must be used. So, currently the driver locks the DQ while it builds and sends each task to the hardware, just in case there is a failure, so that it can reuse that slot. However - there is a point at which we the build/send is guaranteed to succeed, so we can release the lock at that point allowing new slots to be allocated. [Regression Risk] All fixes are localized to the hisi_sas drivers, which are drivers for the controllers in the hip06/hip07 SoCs, where we have directly tested these updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774472/+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 1774490] [NEW] update ENA driver to latest mainline version 1.5.0K
Public bug reported: Apply the following ENA driver commits from mainline to update to ENA driver version 1.5.0K: linux-aws-xenial needs: 6d2e1a8 net: ena: Eliminate duplicate barriers on weakly-ordered archs ee4552a net: ena: fix error handling in ena_down() sequence 7009744 net: ena: increase ena driver version to 1.5.0 8510e1a net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X d18e4f6 net: ena: fix race condition between device reset and link up setup linux-aws-bionic needs: 6d2e1a8 net: ena: Eliminate duplicate barriers on weakly-ordered archs 7009744 net: ena: increase ena driver version to 1.5.0 8510e1a net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X ** Affects: linux-aws (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux-aws (Ubuntu Xenial) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux-aws (Ubuntu Bionic) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Bionic) Status: New => In Progress -- 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/1774490 Title: update ENA driver to latest mainline version 1.5.0K Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Xenial: In Progress Status in linux-aws source package in Bionic: In Progress Bug description: Apply the following ENA driver commits from mainline to update to ENA driver version 1.5.0K: linux-aws-xenial needs: 6d2e1a8 net: ena: Eliminate duplicate barriers on weakly-ordered archs ee4552a net: ena: fix error handling in ena_down() sequence 7009744 net: ena: increase ena driver version to 1.5.0 8510e1a net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X d18e4f6 net: ena: fix race condition between device reset and link up setup linux-aws-bionic needs: 6d2e1a8 net: ena: Eliminate duplicate barriers on weakly-ordered archs 7009744 net: ena: increase ena driver version to 1.5.0 8510e1a net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1774490/+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 1774191] Re: linux-lts-trusty: 3.13.0-151.201~precise1 -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-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1774191 Title: linux-lts-trusty: 3.13.0-151.201~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1774190 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/1774191/+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 1774190] Re: linux: 3.13.0-151.201 -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/1774190 Title: linux: 3.13.0-151.201 -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 1774191 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: 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/1774190/+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 1774124] Re: linux: 4.13.0-45.50 -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/1774124 Title: linux: 4.13.0-45.50 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 (linux-hwe) derivatives: bug 1774125 (linux-raspi2) -- swm properties -- boot-testing-requested: true bugs-spammed: 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/1774124/+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 1774126] Re: linux-oem: 4.13.0-1030.33 -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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774126 Title: linux-oem: 4.13.0-1030.33 -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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1774124 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/1774126/+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 1768143] Re: vmxnet3: update to latest ToT
Looks good. Thanks, Ronak -- 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/1768143 Title: vmxnet3: update to latest ToT Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Bug description: Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit reset and rxvlan disabled fix. Below are the commits: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=7a4c003d6921e2af215f4790aa43a292bdc78be0 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=034f405793897a3c8f642935f5494b86c340cde7 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=65ec0bd1c7c14522670a5294de35710fb577a7fd This is a request to bring Ubuntu vmxnet3 driver up to date with ToT Linux kernel. Could you please backport it to 16.04 and 18.04 LTS releases? Thanks, Ronak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768143/+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 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
-- Bionic verification -- ubuntu@starbuck:~$ uname -a Linux starbuck 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:52 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@starbuck:~$ dmesg | grep -i "W+X" [ 34.983869] Checked W+X mappings: passed, no W+X pages found ubuntu@starbuck:~$ -- Artful verification -- ubuntu@starbuck:~$ uname -a Linux starbuck 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:23:03 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@starbuck:~$dmesg | grep -i "W+X" [ 35.566350] Checked W+X mappings: passed, no W+X pages found ubuntu@starbuck:~$ -- Xenial Verification -- ubuntu@seuss:~$ uname -a Linux seuss 4.4.0-128-generic #154-Ubuntu SMP Fri May 25 14:17:06 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@seuss:~$ dmesg | grep -i "W+X" ubuntu@seuss:~$ ** Tags removed: verification-needed-artful verification-needed-bionic verification-needed-xenial ** Tags added: verification-done-artful verification-done-bionic verification-done-xenial -- 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/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Confirmed 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: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** 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: 1774124 phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1774127 Title: linux-gcp: 4.13.0-1019.23 -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: Invalid 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 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-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1774124 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774127/+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 1773718] Re: mouse pointer disappear after screen off
I just realize that it only happen after login (lxde, lubuntu) in lightdm this does not happen. -- 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/1773718 Title: mouse pointer disappear after screen off Status in linux package in Ubuntu: Confirmed Bug description: With nouveau driver (doesn't happened with propietary nvidia) after screen switch off because of power management, the mouse pointer disappear. Mouse still works, you can hover, select, click, but the pointer is invisible. In a dual monitor configuration, this only happened in the screen where the mouse was when it turned off. If It firs happened in one monitor and tehn I left the mouse in the other and it also turn off, mouse end up disappearing in both. My video card is an nvidia GeForce Go6150 (NV4E C51). Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773718/+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 1774531] [NEW] [Dell Inspiron 7577] shutdown/reboot hangs
Public bug reported: https://answers.launchpad.net/ubuntu-certification/+question/669743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 1 01:19:51 2018 InstallationDate: Installed on 2018-05-30 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1774531 Title: [Dell Inspiron 7577] shutdown/reboot hangs Status in linux-signed package in Ubuntu: New Bug description: https://answers.launchpad.net/ubuntu-certification/+question/669743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 1 01:19:51 2018 InstallationDate: Installed on 2018-05-30 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1774531/+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 1773643] Re: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working
Battant: >"I have dowlowded a deb archive and install it..." The way this is worded indicates only one .deb file was installed, which would be why it didn't show up in GRUB. Did you get a chance to review https://wiki.ubuntu.com/Kernel/MainlineBuilds for guidance? >"but when I tried to compile the kernel..." You would't have to compile kernels, as the .debs are compiled for you. -- 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/1773643 Title: [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Since long time my [Clevo W253EUQ] Turn on bluetooth with Fn+F12 not working For more information see this link bellow https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322068 Could you help me to fix this bug ? Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 27 13:21:46 2018 InstallationDate: Installed on 2018-04-29 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mparchet 1714 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-29 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=9d6286f1-598b-46c8-a491-3e29fc732cb9 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/11/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W2
[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value
I tried thermald 1.7.2, and I can make it work for me, but I don't think it is the best solution. Please pardon the length at which I explain my confusion. I find the thermal-conf files to be confusing. Ubuntu 18.04's thermald-1.7.0 package installs file /etc/thermald/thermal-conf.xml. Based on the way other packages are configured, I would expect this to be the configuration file, but thermald-1.7.0 ignores it. It seems to be just a collection of examples. Is that /etc/thermald/thermal-conf.xml file really suitable for every system to use as a default configuration? If it is not OK, then the file probably should be placed in /usr/share/doc instead of /etc. The thermal-conf.xml.auto file that 1.7.0 generates for my system seems to be OK, except for the Temperature element. Do you see any other problems with it? As far as I know, my only problem is that I can't override the generated Temperature. My system runs well if I stop thermald. I don't know how much better it would run *with* thermald, but "just stop thermald" seems to be an acceptable fall-back position. The new thermald-1.7.2 also attempts to read /etc/thermald/thermal-conf.xml.auto, and I could edit a generated thermal-conf.xml.auto to correct the Temperature element and put it there. However, the ".auto" suffix would be misleading. I would rather put the edited file in /etc/thermal-conf.xml. Thermald-1.7.2 *only* reads the files in /etc if it *can't* generate the /var/run file. It still doesn't provide a way to override a successfully generated file. What if the generated file has a bug in it? What if the user wants to fine-tune the configuration in some way? Now consider what happens when I install thermald-1.7.2 on my 18.04 system. Similar things could happen to other people in the future, if Cosmic Cuttlefish adopts 1.7.2 and other people upgrade to Cosmic from 18.04. - Because of the int3400 check in line 169 of thd_trt_art_reader.cpp, thermald does not try to generate /var/run/thermald/thermal-conf.xml.auto. - Then cthd_parse::parser_init() looks for /etc/thermald/thermal-conf.xml.auto, and does not find it. - Finally cthd_parse::parser_init() looks for /etc/thermald/thermal-conf.xml, finds the "examples" file, and loads it. As I mentioned above, I don't know if that's a good idea. - I'd like to suggest the following: - The thermald package should *not* install /etc/thermald/thermal-conf.xml. - thermald should first look for /etc/thermald/thermal-conf.xml and load it if it exists. - If /etc/thermald/thermal-conf.xml does not exist, thermald should generate /var/run/thermald/thermal-conf.xml.auto and load it. - Two unimportant points: - The new thd_log_info message at thd_trt_art_reader.cpp, line 170, should end with a \n. - I recommend that cthd_parse::parser_init() log the chosen xml_config_file's name every time, not just if it chooses the generated file. -- 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/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: New Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requeste
[Kernel-packages] [Bug 1730150] Re: Nautilus unable to see the storage in my Fuji HS30EXR PTP canera since upgrading from Ubuntu 17.04 to 17.10
Problem appears to have been resolved via one or more updates to 18.04 released by late May 2018. When connected via USB, the Fuji camera is now recognised by Nautilus and a new window pops up for "USB PTP Camera". -- 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/1730150 Title: Nautilus unable to see the storage in my Fuji HS30EXR PTP canera since upgrading from Ubuntu 17.04 to 17.10 Status in linux package in Ubuntu: Expired Bug description: What happens: Something appears to have changed in Nautilus after Nautilus version 1:3.20.4-0ubuntu2 (as in Ubuntu 17.04) and by version 1:3.26.0.0ubuntu1 (as in Ubuntu 17.10)*, causing the storage on my USB PTP camera (a Fujifilm HS30EXR) not to be visible to Nautilus when the camera is connected to the computer via USB and switched on. (Camera firmware was updated and the camera retested on two Ubuntu 17.10 computers) What is expected to happen: On my remaining Ubuntu 17.04 computer (and earlier versions) the camera always pops up in the Nautilus left-hand sidebar when the camera is connected via USB and switched on. To reproduce the bug: 1. Launch "Files" from the Dock 2. Connect a Fujifilm HS30EXR camera (WITH an SD card installed) via USB 3. Observe if camera can be browsed in Nautilus. What is still working: Three other cameras were tested and found not to have this problem with Nautilus: Acorn Ltl5310A (with SD card storage), Nikon P340 (SD card) and Olympus C8080WZ (xD and CF cards). More detail: Apport information report attached. Problem occurs when logged in to either Gnome or Unity Desktop in Ubuntu 17.10. On a prompt from an askubuntu.com user I also tested the Fuji camera on a Ubuntu 17.10 live USB (64 bit ISO downloaded 2 Nov 2017) and found the problem to occur there as well. Problems with Fuji cameras may have occurred in the past and been fixed - see Bug #1273498 * Problem may have appeared on or before Nautilus version 3.24.2.1 (Fedora WS 26), but was not observed in Fedora 25 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: alan 1376 F pulseaudio /dev/snd/controlC0: alan 1376 F pulseaudio /dev/snd/controlC1: alan 1376 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 11:33:43 2017 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=d20ac35f-b382-4cd9-8e3d-89b62ff15b02 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2017-02-09 (268 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7817 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=4f5ff60f-71fa-4354-8c46-85a532f5e205 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux Symptom: storage UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 11:34:19.352: The udisks-daemon is running (name-owner :1.1). UpgradeStatus: Upgraded to artful on 2017-10-20 (15 days ago) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730150/+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 1774563] [NEW] Support SocketCAN over USB on Dell IoT 300x Gateways
Public bug reported: This driver is from IXXAT and supports SocketCAN over USB. (https://www.ixxat.com) This bug is for tracking purposes only, please do not triage. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1774563 Title: Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Incomplete Bug description: This driver is from IXXAT and supports SocketCAN over USB. (https://www.ixxat.com) This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774563/+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 1774563] 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 1774563 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/1774563 Title: Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Incomplete Bug description: This driver is from IXXAT and supports SocketCAN over USB. (https://www.ixxat.com) This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774563/+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 1765279] Re: Unable to build libhugetlbfs test on 4.15 Bionic
We have the test disabled for Bionic (and all the newer releases) http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?h =master-next&id=e1b49796e4403506227038f095761ffa40aedc92 Calling this fix-released now. ** Changed in: linux (Ubuntu) Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => (unassigned) ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Released ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Fix Released ** Changed in: linux-kvm (Ubuntu) Status: New => Fix Released -- 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/1765279 Title: Unable to build libhugetlbfs test on 4.15 Bionic Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-kvm source package in Bionic: Fix Released Bug description: When trying to build the libhugetlbfs test Bionic, it will fail with: CC32 obj32/linkhuge_nofd.o LD32 (hugelink test) obj32/linkhuge_nofd CC32 obj32/linkshare.o LD32 (hugelink test) obj32/linkshare LD32 (xB test) obj32/xB.linkhuge /usr/bin/x86_64-linux-gnu-ld: unrecognized option '--hugetlbfs-link=B' /usr/bin/x86_64-linux-gnu-ld: use the --help option for usage information collect2: error: ld returned 1 exit status Makefile:227: recipe for target 'obj32/xB.linkhuge' failed make[1]: *** [obj32/xB.linkhuge] Error 1 Makefile:242: recipe for target 'tests/all' failed make: *** [tests/all] Error 2 Steps: 1. git clone --depth=1 -b next https://github.com/libhugetlbfs/libhugetlbfs.git 2. cd libhugetlbfs 3. make ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1003-kvm 4.15.0-1003.3 ProcVersionSignature: User Name 4.15.0-1003.3-kvm 4.15.10 Uname: Linux 4.15.0-1003-kvm x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 04:44:08 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765279/+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 1774563] Re: Support SocketCAN over USB on Dell IoT 300x Gateways
** Description changed: This driver is from IXXAT and supports SocketCAN over USB. (https://www.ixxat.com) + == SRU Justification == + Dell IoT 300x gateways support CAN peripherals over USB. Dell expects these devices also support the SocketCAN over USB. Dell is working with HMS to develop and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE patch to support our Ubuntu Core 16 release. + + == Fix == + UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device + + == Regression Potential == + Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. This bug is for tracking purposes only, please do not triage. ** Description changed: This driver is from IXXAT and supports SocketCAN over USB. (https://www.ixxat.com) == SRU Justification == - Dell IoT 300x gateways support CAN peripherals over USB. Dell expects these devices also support the SocketCAN over USB. Dell is working with HMS to develop and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE patch to support our Ubuntu Core 16 release. + Dell IoT 300x gateways support CAN peripherals over USB. Dell expects these devices also support the SocketCAN over USB and is working with HMS to develop and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE patch to support our Ubuntu Core 16 release. == Fix == UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. This bug is for tracking purposes only, please do not triage. -- 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/1774563 Title: Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Incomplete Bug description: This driver is from IXXAT and supports SocketCAN over USB. (https://www.ixxat.com) == SRU Justification == Dell IoT 300x gateways support CAN peripherals over USB. Dell expects these devices also support the SocketCAN over USB and is working with HMS to develop and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE patch to support our Ubuntu Core 16 release. == Fix == UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774563/+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 1759865] Re: general protection fault: 0000 [#1] SMP NOPTI
[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/1759865 Title: general protection fault: [#1] SMP NOPTI Status in linux package in Ubuntu: Expired Bug description: I was using chrome and saw the update-notifier warn me of "" Went to the command line to try to figure out what the problem was. Most commands just core dumped (including apt and su) however I was able to get this from dmesg [ 693.573723] cron[5576]: segfault at 7fff196473d0 ip 7fff196473d0 sp 7fff19645a80 error 15 [ 695.126425] phpquery[5587]: segfault at 7ffd0388c258 ip 56454f0e4650 sp 7ffd0388a180 error 6 in dash[56454f0d2000+1c000] [ 695.234845] phpquery[5591]: segfault at 7ffd0388c258 ip 56454f0e4650 sp 7ffd0388a180 error 6 in dash[56454f0d2000+1c000] [ 695.343616] phpquery[5589]: segfault at 7ffd0388c258 ip 56454f0e4650 sp 7ffd0388a180 error 6 in dash[56454f0d2000+1c000] [ 695.452099] phpquery[5585]: segfault at 7ffd0388c258 ip 56454f0e4650 sp 7ffd0388a180 error 6 in dash[56454f0d2000+1c000] [ 695.583528] sessionclean[5598]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 695.692891] sessionclean[5597]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 695.801617] sessionclean[5581]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 695.904212] sessionclean[5584]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 696.013519] sessionclean[5580]: segfault at 7ffc09ce50e8 ip 55936e2f0650 sp 7ffc09ce3010 error 6 in dash[55936e2de000+1c000] [ 696.695912] systemd: 35 output lines suppressed due to ratelimiting [ 769.048253] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Connection refused [ 828.941426] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 908.937238] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 999.871627] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 1005.962536] systemd-journald[545]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected [ 1005.975570] show_signal_msg: 1 callbacks suppressed [ 1005.975573] which[6212]: segfault at 7ffeadceb8a8 ip 55d161a5e650 sp 7ffeadce97d0 error 6 in dash[55d161a4c000+1c000] [ 1006.089011] which[6218]: segfault at 7fff2ad5e448 ip 561b807f8650 sp 7fff2ad5c370 error 6 in dash[561b807e6000+1c000] [ 1006.219235] which[6223]: segfault at 7ffcee0a0118 ip 5621a961f650 sp 7ffcee09e040 error 6 in dash[5621a960d000+1c000] [ 1006.343970] which[6228]: segfault at 7ffc9fda2948 ip 55b0a1fb5650 sp 7ffc9fda0870 error 6 in dash[55b0a1fa3000+1c000] [ 1006.472231] which[6234]: segfault at 7ffc991e4528 ip 555b82672650 sp 7ffc991e2450 error 6 in dash[555b8266+1c000] [ 1006.597085] which[6240]: segfault at 7fff395ec008 ip 5652da3aa650 sp 7fff395e9f30 error 6 in dash[5652da398000+1c000] [ 1008.042333] idea_tmp_check.[6414]: segfault at 7ffd634cb518 ip 5633b025e650 sp 7ffd634c9440 error 6 in dash[5633b024c000+1c000] ProblemType: KernelOops DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-13-generic 4.15.0-13.14 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic 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: Thu Mar 29 06:49:08 2018 Failure: oops MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=9320ec1f-aa3c-477d-b5d8-b02d82864086 ro pcie_aspm=off 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: general protection fault: [#1] SMP NOPTI UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0902 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default s
[Kernel-packages] [Bug 1774563] Re: Support SocketCAN over USB on Dell IoT 300x Gateways
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** 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/1774563 Title: Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Confirmed Bug description: This driver is from IXXAT and supports SocketCAN over USB. (https://www.ixxat.com) == SRU Justification == Dell IoT 300x gateways support CAN peripherals over USB. Dell expects these devices also support the SocketCAN over USB and is working with HMS to develop and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE patch to support our Ubuntu Core 16 release. == Fix == UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774563/+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 1773973] Re: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel.
*** This bug is a duplicate of bug 1773162 *** https://bugs.launchpad.net/bugs/1773162 ** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1804 -- 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/1773973 Title: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. Status in The Ubuntu-power-systems project: New Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in debian-installer source package in Bionic: New Status in linux source package in Bionic: Incomplete Bug description: ---Problem Description--- Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. ---Environment-- Kernel Build: 4.15.0-22-generic System Name : ltc-garri1 Model/Type : P8 Platform: BML ---Uname output--- Unable to boot. ---Steps to reproduce-- 1. Install Ubuntu 18.04 on Garison BML from http://ports.ubuntu.com /ubuntu-ports/dists/bionic/main/installer- ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ and try to boot. ---Logs Attaching console lob. [4.578205] Bad kernel stack pointer 7b0dd870 at c000b9ec [4.578244] Oops: Bad kernel stack pointer, sig: 6 [#11] [4.578271] LE SMP NR_CPUS=2048 NUMA PowerNV [4.578301] Modules linked in: [4.578324] CPU: 27 PID: 1225 Comm: modprobe Tainted: G D 4.15.0-22-generic #24-Ubuntu [4.578371] NIP: c000b9ec LR: CTR: [4.578413] REGS: c0003febbd40 TRAP: 0300 Tainted: G D (4.15.0-22-generic) [4.578460] MSR: 90001031 CR: XER: [4.578504] CFAR: c000b934 DAR: 0002b200 DSISR: 4000 SOFTE: -4611686018403131680 [4.578504] GPR00: 7b0dd870 [4.578504] GPR04: [4.578504] GPR08: [4.578504] GPR12: 75dcd8781700 0002b200 [4.578504] GPR16: [4.578504] GPR20: [4.578504] GPR24: [4.578504] GPR28: [4.615667] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [4.616210] LR [] (null) [4.616237] Call Trace: [4.616768] Instruction dump: [4.616789] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [4.617697] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 63ff [4.618195] ---[ end trace a0d70ba94f583cca ]--- [4.675899] usb 1-3.3: new high-speed USB device number 5 using xhci_hcd [4.782923] [4.783061] Key type encrypted registered [4.783087] AppArmor: AppArmor sha1 policy hashing enabled [4.783117] ima: No TPM chip found, activating TPM-bypass! (rc=-19) [4.783181] evm: HMAC attrs: 0x1 [4.806062] rtc-opal opal-rtc: setting system clock to 2018-05-29 07:49:29 UTC (1527580169) [4.806350] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [4.806353] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [4.807260] Freeing unused kernel memory: 4800K [4.807321] This architecture does not have kernel memory protection. == Comment: #2 - SEETEENA THOUFEEK - 2018-05-29 06:47:06 == Symptoms looks exactly like . https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691978 . https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656908 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1773973/+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 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)
I'm pasting Pavithra comments on testing with fixed kernel: > Pavithra's update: (In reply to comment #8) > --- Comment From jsalisbury 2018-05-30 01:19:05 UTC--- > Did this issue start with the 4.15.0-22 kernel? Was there a prior 4.15 > based kernel that did not exhibit this bug? > > Could you also see if this bug happens with the Bionic -proposed or mainline > kernel: > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to > enable and use -proposed. > > Mainline can be downloaded from: > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7/ Tested with given kernels below is the summary. 4.15.0-20-generic -> System boots 4.15.0-22-generic -> System fails to boots with oops 4.15.0-23-generic -> System fails to boots with oops 4.15.0-23-generic #26~lp1773162 -> System boots Thanks, Pavithra -- 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/1773162 Title: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot with 4.15.0-22-generic and is in a reboot cycle. ``` Exiting petitboot. Type 'exit' to return. The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes [31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1 [32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2 [2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec [2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1] [2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV [2.660462] Modules linked in: [2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic #24-Ubuntu [2.660549] NIP: c000b9ec LR: CTR: [2.660603] REGS: c0003fd0bd40 TRAP: 0300 Not tainted (4.15.0-22-generic) [2.660657] MSR: 90001031 CR: XER: [2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000 SOFTE: -4611686018408771536 [2.660713] GPR00: 7fffcd511100 [2.660713] GPR04: [2.660713] GPR08: [2.660713] GPR12: 75501b231700 000200f0 [2.660713] GPR16: [2.660713] GPR20: [2.660713] GPR24: [2.660713] GPR28: [2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184 [2.661249] LR [] (null) [2.661285] Call Trace: [2.661303] Instruction dump: [2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 e8810090 [2.661387] e8210078 7db243a6 7db142a6 7c0004ac 63ff 7db242a6 4810 [2.661445] ---[ end trace b607b09fe6490607 ]--- […] ``` Please find the full log attached. Selecting Linux 4.4.0-124-generic works. ``` $ uname -a Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux $ dpkg -l linux-image-4.15.0-22-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-==-==-= ii linux-image-4.15.0-22-generic 4.15.0-22.24 ppc64elSigned kernel image generic $ more /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic ``` --- AlsaDevices: total 0 crw-rw
[Kernel-packages] [Bug 1774571] [NEW] sigq test from stress-ng will get stuck with Artful kernel
Public bug reported: This issue can be spotted on s390x, ARM64 and AMD64 Artful kernel. 10:02:39 DEBUG| [stdout] sigpending STARTING 10:02:44 DEBUG| [stdout] sigpending RETURNED 0 10:02:44 DEBUG| [stdout] sigpending PASSED 10:02:44 DEBUG| [stdout] sigpipe STARTING 10:02:49 DEBUG| [stdout] sigpipe RETURNED 0 10:02:49 DEBUG| [stdout] sigpipe PASSED 10:02:49 DEBUG| [stdout] sigq STARTING ... This is the last entry related to stress-ng in syslog of a s390x node: May 31 10:46:39 s2lp6g004 stress-ng: system: 's2lp6g004' Linux 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:21:19 UTC 2018 s390x May 31 10:46:39 s2lp6g004 stress-ng: memory (MB): total 1805.91, free 1409.97, shared 6.06, buffer 134.56, swap 2001.63, free swap 1890.19 May 31 10:46:39 s2lp6g004 stress-ng: info: [20125] dispatching hogs: 4 sigq No more stress-ng related message after this. ubuntu@s2lp6g004:/tmp$ cat stress-9234.log stress-ng: debug: [20125] 2 processors online, 2 processors configured stress-ng: info: [20125] dispatching hogs: 4 sigq stress-ng: debug: [20125] cache allocate: reducing cache level from L3 (too high) to L2 stress-ng: debug: [20125] cache allocate: default cache size: 2048K stress-ng: debug: [20125] starting stressors stress-ng: debug: [20126] stress-ng-sigq: started [20126] (instance 0) stress-ng: debug: [20125] 4 stressors spawned stress-ng: debug: [20129] stress-ng-sigq: started [20129] (instance 3) stress-ng: debug: [20128] stress-ng-sigq: started [20128] (instance 2) stress-ng: debug: [20127] stress-ng-sigq: started [20127] (instance 1) stress-ng: debug: [20126] stress-ng-sigq: parent sent termination notice stress-ng: debug: [20130] stress-ng-sigq: child got termination notice ubuntu@s2lp6g004:/tmp$ ps aux | grep stress-ng root 5948 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 7654 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 7728 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 7740 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 20125 0.0 0.2 13612 5008 ?SL May31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20126 1.0 0.1 13612 1852 ?SMay31 12:03 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20127 1.0 0.1 13612 1852 ?SMay31 12:11 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20128 1.0 0.1 13612 1852 ?SMay31 12:04 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20129 1.0 0.1 13612 1852 ?SMay31 12:06 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20131 0.0 0.0 13612 312 ?SMay31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20132 0.0 0.0 13612 312 ?SMay31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20133 0.0 0.0 13612 312 ?SMay31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-45-generic 4.13.0-45.50 ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16 Uname: Linux 4.13.0-45-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.9 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Fri Jun 1 05:29:54 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.13.0-45-generic N/A linux-backports-modules-4.13.0-45-generic N/A linux-firmware 1.169.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ub
[Kernel-packages] [Bug 1774571] 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 1774571 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/1774571 Title: sigq test from stress-ng will get stuck with Artful kernel Status in linux package in Ubuntu: Incomplete Bug description: This issue can be spotted on s390x, ARM64 and AMD64 Artful kernel. 10:02:39 DEBUG| [stdout] sigpending STARTING 10:02:44 DEBUG| [stdout] sigpending RETURNED 0 10:02:44 DEBUG| [stdout] sigpending PASSED 10:02:44 DEBUG| [stdout] sigpipe STARTING 10:02:49 DEBUG| [stdout] sigpipe RETURNED 0 10:02:49 DEBUG| [stdout] sigpipe PASSED 10:02:49 DEBUG| [stdout] sigq STARTING ... This is the last entry related to stress-ng in syslog of a s390x node: May 31 10:46:39 s2lp6g004 stress-ng: system: 's2lp6g004' Linux 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:21:19 UTC 2018 s390x May 31 10:46:39 s2lp6g004 stress-ng: memory (MB): total 1805.91, free 1409.97, shared 6.06, buffer 134.56, swap 2001.63, free swap 1890.19 May 31 10:46:39 s2lp6g004 stress-ng: info: [20125] dispatching hogs: 4 sigq No more stress-ng related message after this. ubuntu@s2lp6g004:/tmp$ cat stress-9234.log stress-ng: debug: [20125] 2 processors online, 2 processors configured stress-ng: info: [20125] dispatching hogs: 4 sigq stress-ng: debug: [20125] cache allocate: reducing cache level from L3 (too high) to L2 stress-ng: debug: [20125] cache allocate: default cache size: 2048K stress-ng: debug: [20125] starting stressors stress-ng: debug: [20126] stress-ng-sigq: started [20126] (instance 0) stress-ng: debug: [20125] 4 stressors spawned stress-ng: debug: [20129] stress-ng-sigq: started [20129] (instance 3) stress-ng: debug: [20128] stress-ng-sigq: started [20128] (instance 2) stress-ng: debug: [20127] stress-ng-sigq: started [20127] (instance 1) stress-ng: debug: [20126] stress-ng-sigq: parent sent termination notice stress-ng: debug: [20130] stress-ng-sigq: child got termination notice ubuntu@s2lp6g004:/tmp$ ps aux | grep stress-ng root 5948 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 7654 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 7728 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 7740 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 20125 0.0 0.2 13612 5008 ?SL May31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20126 1.0 0.1 13612 1852 ?SMay31 12:03 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20127 1.0 0.1 13612 1852 ?SMay31 12:11 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20128 1.0 0.1 13612 1852 ?SMay31 12:04 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20129 1.0 0.1 13612 1852 ?SMay31 12:06 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20131 0.0 0.0 13612 312 ?SMay31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20132 0.0 0.0 13612 312 ?SMay31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20133 0.0 0.0 13612 312 ?SMay31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-45-generic 4.13.0-45.50 ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16 Uname: Linux 4.13.0-45-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.9 Architec
[Kernel-packages] [Bug 1774575] [NEW] hwinfo --framebuffer | VirtualBox 5.2.12 | empty output
Public bug reported: 1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS Release:18.04 2) lspci-vnvn+hwinfo_policy.log attached 3) What happens: The command "sudo hwinfo --framebuffer" provides an empty output. (Possibly can't find framebuffer info.) 4) Expected: a list of supported video modes (https://askubuntu.com/a/824182/621093) Some additional info A) Enviroment: A1) Ubuntu 18.04 server A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't help. B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: framebuffer hwinfo server ubuntu18.04 virtualbox5.2.12 ** Attachment added: "lspci-vnvn+hwinfo_policy.log" https://bugs.launchpad.net/bugs/1774575/+attachment/5147234/+files/lspci-vnvn+hwinfo_policy.log -- 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/1774575 Title: hwinfo --framebuffer | VirtualBox 5.2.12 | empty output Status in linux package in Ubuntu: New Bug description: 1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS Release:18.04 2) lspci-vnvn+hwinfo_policy.log attached 3) What happens: The command "sudo hwinfo --framebuffer" provides an empty output. (Possibly can't find framebuffer info.) 4) Expected: a list of supported video modes (https://askubuntu.com/a/824182/621093) Some additional info A) Enviroment: A1) Ubuntu 18.04 server A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't help. B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774575/+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 1774575] 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 1774575 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/1774575 Title: hwinfo --framebuffer | VirtualBox 5.2.12 | empty output Status in linux package in Ubuntu: Incomplete Bug description: 1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS Release:18.04 2) lspci-vnvn+hwinfo_policy.log attached 3) What happens: The command "sudo hwinfo --framebuffer" provides an empty output. (Possibly can't find framebuffer info.) 4) Expected: a list of supported video modes (https://askubuntu.com/a/824182/621093) Some additional info A) Enviroment: A1) Ubuntu 18.04 server A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't help. B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774575/+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 1521173] Re: AER: Corrected error received: id=00e0
** Changed in: linux (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Triaged Bug description: Note: Current workaround is to add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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 1726159] Re: PCIe BUS Error causing really slow laptop performance
I have this error on my Asus X541U, with Ubuntu 18.04, please solve it. It generates an endless list with this error: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID) device [8086:9d15] error status/mask=0001/2000 And I can't log in. And it is related to the Wi-Fi board of my PC, which is the following:Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter -- 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/1726159 Title: PCIe BUS Error causing really slow laptop performance Status in linux package in Ubuntu: Confirmed Bug description: I recently bought the following laptop: Asus VivoBook X542UQ-DM148T - 15.6" (i7-7500U/8GB/256GB/GT 940MX 2GB) It came pre-installed with Win10 and I did a fresh install of Ubuntu 16.04 LTS. The screen was flickering for some reason and installing Ubuntu 17.04 fixed the issue. The real problem is that when I'm booting the laptop, the following error is being shown on my screen: [ 12.866073] pcieport :00:1c.5: can't find device of ID00e5 [ 12.898481] pcieport :00:1c.5: AER: Multiple Corrected error received: id=00e5 [ 12.898488] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID) [ 12.898491] pcieport :00:1c.5: device [8086:9d15] error status/mask=2041/2000 [ 12.898492] pcieport :00:1c.5:[ 0] Receiver Error (First) [ 12.898493] pcieport :00:1c.5:[ 6] Bad TLP I know that this error can be hid with one of the following kernel boot arguments: pci=nomsi / pci=noaer / pcie_aspm=off / pci=nommconf. The weird thing is that the above output is only being shown when the laptop is on AC Power (charging). When the laptop is not connected to AC (battery-mode), it has performance issues (slow boot and slow application launching). I was trying all day long to fix the problem. I removed everything that had to do with power-saving, reinstalled, re-tweaked for performance, tried different kernels but had no luck. While diagnosing, I had the idea to benchmark the "M2 SATA-3 SSD" that my laptop had. The results are: * On AC Power: 522MB/s (READ) | 416MB/s (WRITE) * On Battery Power: 32MB/s (READ) | 31MB/s (WRITE) This explains everyting. That's why I'm having a slow boot and slow application launching! Commands "lspci" and "dmesg" say that the error comes from the following device: 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) I will attach lspci and dmesg output on a tar.gz file. -- UPDATE: When the laptop is fully charged and still on AC (but not charging since it is 100% charged), the errors appear again but the SSD speed is normal (~500 Read/Write). -- UPDATE: I installed 'tlp' Advanced Power Management package and when using the command 'tlp ac', the SSD speed gets back to normal! The option does not persist across reboots. -- ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: georgem2557 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sun Oct 22 23:17:57 2017 InstallationDate: Installed on 2017-10-20 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3496 IMC Networks Bus 001 Device 003: ID 13d3:5a01 IMC Networks Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X542UQ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed root=UUID=38d32efc-d0cb-4a82-9e6c-e6a3bd62e51d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X542UQ.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X542UQ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vend
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
Hi. I have this problem too on T440s with 18.04 (kernel 4.15.0-22). The previous workaround worked perfectly for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+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 1521173] Re: AER: Corrected error received: id=00e0
** Changed in: linux (Ubuntu) Status: In Progress => 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Triaged Bug description: Note: Current workaround is to add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+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
