[Kernel-packages] [Bug 1850886] Re: Auto-rotate is not working properly when system is booted up while not in its regular orientation
It's a generic bug, I reproduced it on 18.04.3 with 5.0.0-32 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1850886 Title: Auto-rotate is not working properly when system is booted up while not in its regular orientation Status in GNOME Shell: New Status in linux-meta-oem package in Ubuntu: Confirmed Bug description: [RELEASE VERSION] Description: Ubuntu 18.04.3 LTS Release: 18.04 [PACKAGE VERSION] linux-oem: Installed: 4.15.0.1057.61 Candidate: 4.15.0.1057.61 Version table: *** 4.15.0.1057.61 500 500 http://jp.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1004.2 500 500 http://jp.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [EXPECTED OUTPUT] Upon boot up with auto-rotation enabled, display should show the proper screen orientation of the system accordingly [ACTUAL OUTPUT] Auto-rotation is not working properly when system is booted up while not in its regular orientation [STEPS] 1. Make sure auto-rotation is enabled on the system 2. Before turning the system on, put it on tablet mode, with the inverted landscape rotation (the top part/the part with the camera is adjacent to the surface). The system should follow this orientation when the login screen appears. 3. Login to the system 4. Switch to the clam shell mode. The display suddenly becomes inverted/the opposite direction of the expected output. 5. Switch back to the tablet mode. The display also ends up being inverted/in the opposite direction of the expected output [REMARKS] *Using WHL *The system seems to be setting the orientation according to the orientation during boot up ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21 Uname: Linux 5.0.0-1024-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 14:23:14 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso InstallationDate: Installed on 2019-07-25 (98 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1850886/+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 1850886] Re: Auto-rotate is not working properly when system is booted up while not in its regular orientation
I did more debug. I found in the GNOME desktop the dbus message is correct. When I boot up from bottom-up mode, the value of net.hadess.SensorPorxy.AccelerometerOrientation is "bottom-up", after that, I change to normal mode, I found the value is "normal". But the screen is totally revert. I tried to use xrandr to rotate the screen. $ xrandr --output eDP-1 --rotate inverted Although the screen show correctly, but I found the mouse and touch screen is still keep inverted. I thought this issue is not related to kernel, cause we could got correct value from AccelerometerProxy, I doubt the gnome-shell could handle it correctly. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1850886 Title: Auto-rotate is not working properly when system is booted up while not in its regular orientation Status in GNOME Shell: New Status in linux-meta-oem package in Ubuntu: Confirmed Bug description: [RELEASE VERSION] Description: Ubuntu 18.04.3 LTS Release: 18.04 [PACKAGE VERSION] linux-oem: Installed: 4.15.0.1057.61 Candidate: 4.15.0.1057.61 Version table: *** 4.15.0.1057.61 500 500 http://jp.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1004.2 500 500 http://jp.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [EXPECTED OUTPUT] Upon boot up with auto-rotation enabled, display should show the proper screen orientation of the system accordingly [ACTUAL OUTPUT] Auto-rotation is not working properly when system is booted up while not in its regular orientation [STEPS] 1. Make sure auto-rotation is enabled on the system 2. Before turning the system on, put it on tablet mode, with the inverted landscape rotation (the top part/the part with the camera is adjacent to the surface). The system should follow this orientation when the login screen appears. 3. Login to the system 4. Switch to the clam shell mode. The display suddenly becomes inverted/the opposite direction of the expected output. 5. Switch back to the tablet mode. The display also ends up being inverted/in the opposite direction of the expected output [REMARKS] *Using WHL *The system seems to be setting the orientation according to the orientation during boot up ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21 Uname: Linux 5.0.0-1024-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 14:23:14 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso InstallationDate: Installed on 2019-07-25 (98 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1850886/+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 1850886] Re: Auto-rotate is not working properly when system is booted up while not in its regular orientation
I doubt the gnome-shell couldn't handle it correctly. :) ** Also affects: gnome-shell Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1850886 Title: Auto-rotate is not working properly when system is booted up while not in its regular orientation Status in GNOME Shell: New Status in linux-meta-oem package in Ubuntu: Confirmed Bug description: [RELEASE VERSION] Description: Ubuntu 18.04.3 LTS Release: 18.04 [PACKAGE VERSION] linux-oem: Installed: 4.15.0.1057.61 Candidate: 4.15.0.1057.61 Version table: *** 4.15.0.1057.61 500 500 http://jp.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1004.2 500 500 http://jp.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [EXPECTED OUTPUT] Upon boot up with auto-rotation enabled, display should show the proper screen orientation of the system accordingly [ACTUAL OUTPUT] Auto-rotation is not working properly when system is booted up while not in its regular orientation [STEPS] 1. Make sure auto-rotation is enabled on the system 2. Before turning the system on, put it on tablet mode, with the inverted landscape rotation (the top part/the part with the camera is adjacent to the surface). The system should follow this orientation when the login screen appears. 3. Login to the system 4. Switch to the clam shell mode. The display suddenly becomes inverted/the opposite direction of the expected output. 5. Switch back to the tablet mode. The display also ends up being inverted/in the opposite direction of the expected output [REMARKS] *Using WHL *The system seems to be setting the orientation according to the orientation during boot up ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21 Uname: Linux 5.0.0-1024-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 14:23:14 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso InstallationDate: Installed on 2019-07-25 (98 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1850886/+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 1848981] Re: disco/linux-raspi2: 5.0.0-1021.21 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850574 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 23. October 2019 10:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress + certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848981 Title: disco/linux-raspi2: 5.0.0-1021.21 -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: Incomplete 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850574 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 23. October 2019 10:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848981/+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 1848999] Re: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850574 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 15:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress + certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1848999 Title: disco/linux-snapdragon: 5.0.0-1025.26 -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: Incomplete 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850574 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 15:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848999/+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 1849008] Re: bionic/linux-raspi2: 4.15.0-1050.54 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1849008 Title: bionic/linux-raspi2: 4.15.0-1050.54 -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: In Progress 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849855 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 22. October 2019 13:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1849007 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849008/+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 1848999] Re: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1848999 Title: disco/linux-snapdragon: 5.0.0-1025.26 -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: Incomplete 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850574 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 15:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848999/+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 1849051] Re: xenial/linux: 4.4.0-167.196 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- 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/1849051 Title: xenial/linux: 4.4.0-167.196 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 22. October 2019 16:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1849048 trusty/linux-lts-xenial: bug 1849049 xenial/linux-aws: bug 1849041 xenial/linux-fips: bug 1849047 xenial/linux-kvm: bug 1849042 xenial/linux-raspi2: bug 1849044 xenial/linux-snapdragon: bug 1849046 xenial/linux/caracalla-kernel: bug 1849036 xenial/linux/pc-kernel: bug 1849037 xenial/linux/stlouis-kernel: bug 1849038 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849051/+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 1849044] Re: xenial/linux-raspi2: 4.4.0-1125.134 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1849044 Title: xenial/linux-raspi2: 4.4.0-1125.134 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849051 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 22. October 2019 15:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1849043 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849044/+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 1849046] Re: xenial/linux-snapdragon: 4.4.0-1129.137 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1849046 Title: xenial/linux-snapdragon: 4.4.0-1129.137 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849051 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 10:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1849045 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849046/+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 1849011] Re: bionic/linux-snapdragon: 4.15.0-1067.74 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1849011 Title: bionic/linux-snapdragon: 4.15.0-1067.74 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849855 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 23. October 2019 11:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1849010 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849011/+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 1848981] Re: disco/linux-raspi2: 5.0.0-1021.21 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848981 Title: disco/linux-raspi2: 5.0.0-1021.21 -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: Incomplete 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850574 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 23. October 2019 10:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848981/+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 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- 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/1849855 Title: bionic/linux: 4.15.0-68.77 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1850799 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1850574] Re: disco/linux: 5.0.0-34.36 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- 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/1850574 Title: disco/linux: 5.0.0-34.36 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Incomplete Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 30. October 2019 18:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1849002 bionic/linux-hwe: bug 1850587 bionic/linux-oem-osp1: bug 1849001 disco/linux-aws: bug 1848984 disco/linux-azure: bug 1848989 disco/linux-gcp: bug 1848995 disco/linux-kvm: bug 1848996 disco/linux-oracle: bug 1848998 disco/linux-raspi2: bug 1848981 disco/linux-snapdragon: bug 1848999 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850574/+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 1850799] Re: bionic/linux-oem: 4.15.0-1061.70 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1850799 Title: bionic/linux-oem: 4.15.0-1061.70 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849855 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Sunday, 03. November 2019 19:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850799/+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 1850799] Re: bionic/linux-oem: 4.15.0-1061.70 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849855 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Sunday, 03. November 2019 19:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- 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/1850799 Title: bionic/linux-oem: 4.15.0-1061.70 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849855 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Sunday, 03. November 2019 19:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850799/+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 1850799] Re: bionic/linux-oem: 4.15.0-1061.70 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Taihsiang Ho (taihsiangho) -- 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/1850799 Title: bionic/linux-oem: 4.15.0-1061.70 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849855 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Sunday, 03. November 2019 19:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850799/+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 1851014] Re: WiFi (inbuilt) and Bluetooth not detected
Hmm I don't see this issue the XPS 9343 at my hand. Can you attach output of `dkms status`? -- 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/1851014 Title: WiFi (inbuilt) and Bluetooth not detected Status in linux package in Ubuntu: Confirmed Bug description: Mint 19.2 laptop:XPS 13 9343 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: alan 5186 F pulseaudio /dev/snd/controlC1: alan 5186 F pulseaudio /dev/snd/controlC0: alan 5186 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2018-07-24 (466 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 IwConfig: lono wireless extensions. enx803f5d083b2a no wireless extensions. MachineType: Dell Inc. XPS 13 9343 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=7c3f7872-75bd-4816-9eeb-e5ac1d8cddda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.173.9 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: tina Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/23/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.sku: 0665 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851014/+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 1849047] Re: xenial/linux-fips: 4.4.0-1024.29 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849051 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Wednesday, 23. October 2019 13:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- 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/1849047 Title: xenial/linux-fips: 4.4.0-1024.29 -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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849051 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Wednesday, 23. October 2019 13:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849047/+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 1849047] Re: xenial/linux-fips: 4.4.0-1024.29 -proposed tracker
4.4.0-1024.29 - fips Regression test CMPL, RTB. 58 / 59 tests were run, missing: ubuntu_boot Issue to note in amd64: fips_boot - failed on amd64 nodes (bug 1851335) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842270) ubuntu_xfstests_btrfs - btrfs/187 time out ubuntu_xfstests_xfs - generic/438 time out 51 / 55 tests were run, missing: ubuntu_boot, ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_ltp_syscalls - fanotify07 won't fix (bug 1775165) fallocate04, fallocate05, fsetxattr01, fdatasync03, fgetxattr01, fremovexattr01, fremovexattr02, fsync01, fsync04, fanotify13, fanotify14, fanotify15, lremovexattr01, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, setxattr01, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) move_pages12 (bug 1831043) 50 / 51 tests were run, missing: ubuntu_boot Issue to note in s390x (KVM): fips_boot - nested KVM not supported on s390x (bug 1851324) libhugetlbfs - bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - test should be skipped for X s390x KVM ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842314) fanotify06 (bug 1833028) fanotify10 (bug 1802454) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842314) ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1849047 Title: xenial/linux-fips: 4.4.0-1024.29 -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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849051 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Wednesday, 23. October 2019 13:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849047/+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 1850886] Re: Auto-rotate is not working properly when system is booted up while not in its regular orientation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-oem (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1850886 Title: Auto-rotate is not working properly when system is booted up while not in its regular orientation Status in linux-meta-oem package in Ubuntu: Confirmed Bug description: [RELEASE VERSION] Description: Ubuntu 18.04.3 LTS Release: 18.04 [PACKAGE VERSION] linux-oem: Installed: 4.15.0.1057.61 Candidate: 4.15.0.1057.61 Version table: *** 4.15.0.1057.61 500 500 http://jp.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.1004.2 500 500 http://jp.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [EXPECTED OUTPUT] Upon boot up with auto-rotation enabled, display should show the proper screen orientation of the system accordingly [ACTUAL OUTPUT] Auto-rotation is not working properly when system is booted up while not in its regular orientation [STEPS] 1. Make sure auto-rotation is enabled on the system 2. Before turning the system on, put it on tablet mode, with the inverted landscape rotation (the top part/the part with the camera is adjacent to the surface). The system should follow this orientation when the login screen appears. 3. Login to the system 4. Switch to the clam shell mode. The display suddenly becomes inverted/the opposite direction of the expected output. 5. Switch back to the tablet mode. The display also ends up being inverted/in the opposite direction of the expected output [REMARKS] *Using WHL *The system seems to be setting the orientation according to the orientation during boot up ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 5.0.0-1024.27-oem-osp1 5.0.21 Uname: Linux 5.0.0-1024-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 1 14:23:14 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso InstallationDate: Installed on 2019-07-25 (98 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem/+bug/1850886/+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 1851230] Re: missing firmware files from oem image
The latest iwlwifi-9000-pu-b0-jf-b0-43.ucode is from below commit. commit 40e4162adfc91390f6fbbd8269f9439832af1dde Author: Luca Coelho Date: Fri Aug 23 07:35:14 2019 +0300 iwlwifi: update FWs to core45-152 release Build number: Core_build_core45-152 Revision: 77d01142 (8000, 8265) 6bf1df06 (9000, 9260) 4fa0041f (cc, Qu) Signed-off-by: Luca Coelho -- 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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 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:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+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 1851230] Re: missing firmware files from oem image
@hui and @aaron, Is it possible that we push the iwlwifi-9000-pu-b0-jf-b0-43.ucode into oem-kernel? Thanks! -- 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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Bug description: When loading the image for the X1C7 (Knockout) I find that although the kernel is at 5.0.x the iwlwifi firmware files for that load level are missing. Normally that would not be an issue as it will load an older version in this case it starts looking for version 46 and that is not there so it finally finds version 43 which loads, the issue is in when loading securedoc from winmagic it see that the kernel level is 5.0.x and is expecting the firmware version 46 to be present if it is not then the wifi does not come up as the fall back method of loading does not work. Missing file is iwlwifi-9000-pu-bo-jf-bo-46.ucode --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z 2949 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20190722-12+sutton-dijkstra-bionic-amd64+iso DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-25 (101 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190722-05:40 MachineType: LENOVO 20QESITE03 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1015-oem-osp1 root=UUID=85aa11d3-7721-44f1-8652-37f9dd839624 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-1015.16-oem-osp1 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-1015-oem-osp1 N/A linux-backports-modules-5.0.0-1015-oem-osp1 N/A linux-firmware 1.173.10 Tags: bionic Uname: Linux 5.0.0-1015-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET33W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QESITE03 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:bvrN2HET33W(1.16):bd07/29/2019:svnLENOVO:pn20QESITE03:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QESITE03:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QESITE03 dmi.product.sku: LENOVO_MT_20QE_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851230/+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 1839836] Re: acct02 from ubuntu_ltp_syscalls failed on X/B/D/E-s390x
ubuntu@s2lp6g003:~$ lscpu | grep "Byte Order"
Byte Order: Big Endian
Seems to be fixed with the following commit in LTP (acct: fix version check on
big endian system):
https://github.com/linux-test-project/ltp/commit/fe5ffe2701f8dc8115a82808818b9d9d5b41508d
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** No longer affects: linux (Ubuntu Xenial)
** No longer affects: linux (Ubuntu Bionic)
** No longer affects: linux (Ubuntu Disco)
** No longer affects: linux (Ubuntu Eoan)
** Changed in: ubuntu-kernel-tests
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/1839836
Title:
acct02 from ubuntu_ltp_syscalls failed on X/B/D/E-s390x
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Invalid
Bug description:
Error message on D-s390x KVM:
startup='Thu Oct 3 01:17:21 2019'
tst_kconfig.c:62: INFO: Parsing kernel config
'/boot/config-4.15.0-66-generic'
tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
tst_kconfig.c:62: INFO: Parsing kernel config
'/boot/config-4.15.0-66-generic'
acct02.c:239: INFO: Verifying using 'struct acct_v3'
acct02.c:192: INFO: == entry 1 ==
acct02.c:82: INFO: ac_comm != 'acct02_helper' ('systemd-udevd')
acct02.c:133: INFO: ac_exitcode != 32768 (0)
acct02.c:141: INFO: ac_ppid != 32327 (705)
acct02.c:147: INFO: ac_version != 3 (131)
acct02.c:192: INFO: == entry 2 ==
acct02.c:147: INFO: ac_version != 3 (131)
acct02.c:192: INFO: == entry 3 ==
acct02.c:82: INFO: ac_comm != 'acct02_helper' ('acct02')
acct02.c:133: INFO: ac_exitcode != 32768 (0)
acct02.c:141: INFO: ac_ppid != 32327 (32326)
acct02.c:147: INFO: ac_version != 3 (131)
acct02.c:182: FAIL: end of file reached
Summary:
passed 0
failed 1
skipped 0
warnings 0
This was not spotted on other arches on D, just s390x
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-25-generic 5.0.0-25.26
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-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.10-0ubuntu27.1
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:
[435066.563428] LTP: starting acct02
[435067.737885] Process accounting resumed
Date: Mon Aug 12 13:49:49 2019
HibernationDevice: RESUME=UUID=eae923f9-f5a4-41c0-b3e4-04786207dbaa
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcFB:
ProcKernelCmdLine: root=UUID=1a6af794-84a9-4034-a213-39506b9bb91c
crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
linux-restricted-modules-5.0.0-25-generic N/A
linux-backports-modules-5.0.0-25-generic N/A
linux-firmware1.178.4
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-kernel-tests/+bug/1839836/+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 1832963] Re: sound doesn't work
Would it be possible for you to do a kernel bisection? First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the good version you found) $ git bisect bad $(the bad version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If the issue still happens, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression. -- 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/1832963 Title: sound doesn't work Status in linux package in Ubuntu: Confirmed Bug description: after installing new kernel RV770 HDMI Audio [Radeon HD 4850/4870](Radeon 4850 512MB GODR3 PCI-E Dual Slot Fansin. reported as Disabled and off in sound preferences->hardware --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmike1 1895 F pulseaudio /dev/snd/controlC2: bmike1 1895 F pulseaudio /dev/snd/controlC1: bmike1 1895 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2019-01-15 (151 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: Gigabyte Technology Co., Ltd. GA-MA785G-UD3H Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=6298f990-6b80-4665-80ab-e83034a72ae5 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: GA-MA785G-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA785G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA785G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA785G-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832963/+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 1849665] Re: zfs diff: Unable to determine path or stats for object
Hello Andreas, or anyone else affected,
Accepted zfs-linux into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.1-1ubuntu14.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: zfs-linux (Ubuntu Eoan)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849665
Title:
zfs diff: Unable to determine path or stats for object
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Eoan:
Fix Committed
Bug description:
== SRU Justification, Eoan ==
Using zfs diff on an encrypted dataset with large objects one can hit
an error such as follows:
# zfs diff nsnx/trusty-2a@snap1 nsnx/trusty-2a
+ /nsnx/trusty-2a/bin
Unable to determine path or stats for object 5 in
nsnx/trusty-2a@zfs-diff-32359-00010001f165: File exists
== Fix ==
Upstream commit d359e99c38f667 ("diff_cb() does not handle large
dnodes") as addressed in ZFS bug fix:
https://github.com/zfsonlinux/zfs/pull/9343
== Testcase ==
# mkdir /zfs-test
# cd /zfs-test
# truncate -s 10G file.img
# zpool create -o ashift=12 -O acltype=posixacl -O compression=lz4 -O
xattr=sa -O normalization=formD -O dnodesize=auto tank $(pwd)/file.img
# zfs create tank/d1 -o encryption=on -o keyformat=passphrase
Enter passphrase:
Re-enter passphrase:
# dd if=/dev/urandom bs=4k of=/tank/d1/somedata.bin count=10240
10240+0 records in
10240+0 records out
41943040 bytes (42 MB, 40 MiB) copied, 0,304365 s, 138 MB/s
# zfs snapshot tank/d1@s1
# dd if=/dev/urandom bs=4k of=/tank/d1/somedata2.bin count=10240
10240+0 records in
10240+0 records out
41943040 bytes (42 MB, 40 MiB) copied, 0,305324 s, 137 MB/s
Without the fix, one hits an error such as:
# zfs diff tank/d1@s1 tank/d1
Unable to determine path or stats for object 3 in tank/d1@s1: File exists
With the fix, we get:
+ /tank/d1/somedata2.bin
M /tank/d1/
== Regression Potential ==
This is a minor change in module/zfs/dmu_diff.c and it only affects
the zfs diff component, so this should not affect ZFS in terms of file
system corruption/data loss. This has also been upstream regression
tested and passes the Ubuntu ZFS regressions tests too. So the risk
is limited.
-
Eoan 19.10
zfsutils-linux 0.8.1-1ubuntu14
kernel 5.3.0-19-generic #20-Ubuntu
When using zfs diff on an encrypted dataset, I frequently encounter
this error:
# zfs diff nsnx/trusty-2a@snap1 nsnx/trusty-2a
+ /nsnx/trusty-2a/bin
Unable to determine path or stats for object 5 in
nsnx/trusty-2a@zfs-diff-32359-00010001f165: File exists
I believe this to be upstream bug
https://github.com/zfsonlinux/zfs/issues/7678, fixed with
https://github.com/zfsonlinux/zfs/pull/9343
Here is one way to reproduce it:
# mkdir /zfs-test
# cd /zfs-test
# truncate -s 10G file.img
# zpool create -o ashift=12 -O acltype=posixacl -O compression=lz4 -O
xattr=sa -O normalization=formD -O dnodesize=auto tank $(pwd)/file.img
# zfs create tank/d1 -o encryption=on -o keyformat=passphrase
Enter passphrase:
Re-enter passphrase:
# dd if=/dev/urandom bs=4k of=/tank/d1/somedata.bin count=10240
10240+0 records in
10240+0 records out
41943040 bytes (42 MB, 40 MiB) copied, 0,304365 s, 138 MB/s
# zfs snapshot tank/d1@s1
# dd if=/dev/urandom bs=4k of=/tank/d1/somedata2.bin count=10240
10240+0 records in
10240+0 records out
41943040 bytes (42 MB, 40 MiB) copied, 0,305324 s, 137 MB/s
# zfs diff tank/d1@s1 tank/d1
Unable to determine path or stats for object 3 in tank/d1@s1: File exists
There may be a simpler way to test this, but this should be enough to
start with.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1849665/+subscriptions
--
Mailing lis
[Kernel-packages] [Bug 1851216] Re: System hangs at early boot
** Changed in: linux-oem (Ubuntu Bionic) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/1851216 Title: System hangs at early boot Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: After upgrading kernel to linux-image-4.15.0-1061 (proposed), system hangs at very beginning of booting, leaving Grub messages "loading..." on the console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1060-oem 4.15.0-1060.69 ProcVersionSignature: Ubuntu 4.15.0-1060.69-oem 4.15.18 Uname: Linux 4.15.0-1060-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: u 1977 F...m pulseaudio /dev/snd/pcmC1D0p: u 1977 F...m pulseaudio /dev/snd/controlC0: u 1977 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 4 17:15:56 2019 InstallationDate: Installed on 2019-11-04 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Precision 5530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1060-oem root=UUID=baa02b0a-d18f-41d2-9e2b-2d057742013c ro mem_sleep_default=deep nvidia-drm.modeset=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-1060-oem N/A linux-backports-modules-4.15.0-1060-oem N/A linux-firmware 1.173.9 SourcePackage: linux-oem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0184M4 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd06/27/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0184M4:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1851216/+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 1847118] Re: PM / hibernate: fix potential memory corruption
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco ** Tags removed: verification-needed-eoan verification-needed-xenial ** Tags added: verification-done-eoan 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/1847118 Title: PM / hibernate: fix potential memory corruption Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] A caching bug in the hibernation code can lead to potential memory corruptions on resume. The hibernation code is representing all the allocated pages in memory (pfn) using a list of extents, inside each extent it uses a radix tree and each node in the tree contains a bitmap. This structure is used to save the memory image to disk. To speed up lookups in this structure the kernel is caching the position of the previous lookup in the form (current_extent, current_node). However, if two consecutive lookups are distant enough from each other, the extent can change, but the kernel can still use the cached node (current_node), accessing the wrong bitmap and ending up saving to disk the wrong pfn's. [Test Case] Bug has been reproduced in Xenial and Bionic trying to hibernate a large instance with a lot of RAM (100GB+). But we also wrote a custom kernel module to better isolate the code that triggers the problem: https://code.launchpad.net/~arighi/+git/mybitmap This module has exactly the same code as the hibernation code, but it can be used as a fast test case to reproduce the problem without actually triggering a real hibernation/resume cycle. [Fix] This bug can be fixed by properly invalidating the cached pair (extent, node) when the next lookup falls in a different extent or a different node. [Regression Potential] The fix has been sent to the LKML for review/feedback (https://lkml.org/lkml/2019/9/25/393), we have not received any feedback so far, but the bug is pretty clear and well tested on the affected platforms. Moreover, the code is isolated to the hibernation area, so the overall regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847118/+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 1850099] Re: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo
Can you please run fsck on your root partition? -- 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/1850099 Title: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to eoan ermine, my laptop (Dell Precision 5510) got an error message stating "Error: out of memory Press any key to continue..." After pressing a key, nothing changed. I left the room and came back to see that there was a kernel panic. I'll attach picture as I couldn't copy/paste the console output. Description: Ubuntu 19.10 Release: 19.10 linux-image-5.3.0-19-generic I expect the kernel to load without a panic. The kernel panicked. After rebooting and selecting an older kernel, I was able to boot and load the old kernel without issue (5.0.0-32-generic) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lost 1947 F pulseaudio CurrentDesktop: XFCE Date: Mon Oct 28 00:52:26 2019 HibernationDevice: RESUME=UUID=0dba346e-043c-4e62-95a4-911a6a65e626 InstallationDate: Installed on 2016-06-17 (1227 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0WVDX2 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd10/03/2019:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA07:cvnDellInc.:ct9:cvr: dmi.product.family: Precision dmi.product.name: Precision 5510 dmi.product.sku: 06E5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+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 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
SRU request to D/E/F: https://lists.ubuntu.com/archives/kernel-team/2019-November/105221.html -- 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/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in livecd-rootfs source package in Bionic: New Status in linux source package in Disco: In Progress Status in livecd-rootfs source package in Disco: New Status in linux source package in Eoan: In Progress Status in livecd-rootfs source package in Eoan: New Status in linux source package in Focal: Fix Committed Status in livecd-rootfs source package in Focal: Invalid Bug description: === SRU Justification === [Impact] Intel's VF drivers such as igbvf and ixgbevf are already available in generic. It makes sense to add i40evf especially for SR-IOV enabled clouds with Intel X710/XXV710/XL710. [Fix] Add i40evf to linux-modules package [Test] Extract linux-modules to check if i40evf is there [Regression Potential] Low = original bug description = For example with bionic, i40evf module is in linux-modules-extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+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 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake
Same device boots with disable-hpet patches applied to current korg-next HEAD tagged next-20191031. -- 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/1840239 Title: tsc marked unstable after entered PC10 on Intel CoffeeLake Status in HWE Next: Triaged Status in linux package in Ubuntu: Triaged Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: New Status in linux-oem source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: New Status in linux-oem source package in Eoan: Won't Fix Status in linux-oem-osp1 source package in Eoan: Won't Fix Bug description: === SRU Justification === [Impact] TSC marked unstable by skewed HPET after Intel SoC reached PC10 state. [Fix] Disable HPET on affected SoC generations, currently happens to CFL and ICL. [Test] I can confirm disabling HPET can avoid this issue. [Regression Potential] Low. TSC on recent Intel SoC is now an invariant clocksource, so it's harmless to disable HPET on these platforms. === Original Bug Report === This is actually a duplicate to https://bugzilla.kernel.org/show_bug.cgi?id=203183 that is for internal tracking. [Overview] On Intel CoffeeLake it's observed tsc is always marked unstable after turning off screen and let cpu enter idle state Package C10(PC10), and then clock source is switched to hpet. Following messages are printed in dmesg when this occurs: [ 115.454117] clocksource: timekeeping watchdog on CPU2: Marking clocksource 'tsc' as unstable because the skew is too large: [ 115.454146] clocksource: 'hpet' wd_now: a44e6960 wd_last: a42fe23b mask: [ 115.454151] clocksource: 'tsc' cs_now: 69ee1f8d9f cs_last: 699580f6fd mask: [ 115.454160] tsc: Marking TSC unstable due to clocksource watchdog [ 115.454675] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. [ 115.454679] sched_clock: Marking unstable (115712298090, -257671127)<-(115460381128, -5706726) [ 115.455825] clocksource: Switched to clocksource hpet [Step to reproduce] 1. use `powertop` to observe if CPU has ever enter PC10, 2. issue `xset dpms force off` to turn off screen and idle for some minutes, 3. check dmesg for above tsc marked unstable messages [Actual Results] TSC marked unstable and clock source switched to HPET. [Expected Results] TSC remains the clock source across the PC10 event. [Build Date & Hardware] This is reproducible on kernel version 4.14 through 5.1-rc2. Order kernel versions are not tested. [Additional Information] This was first found on Ubuntu (all versions) that system doesn't go suspend after stayed idle for 20 minutes. Clock source was switched to HPET, the system time is no correctly synced with reality so that the system doesn't consider it has stayed idle long enough to begin suspend process. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1840239/+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 1842850] Re: NULL pointer dereference in kvm_mmu_flush_or_zap
[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/1842850 Title: NULL pointer dereference in kvm_mmu_flush_or_zap Status in linux package in Ubuntu: Expired Bug description: tonight one of our systems run into the following panic -- kernel NULL pointer dereference at kernel: [2468259.002689] IP: kvm_mmu_flush_or_zap+0x5/0x40 [kvm] kernel: [2468259.007758] PGD 0 P4D 0 kernel: [2468259.010483] Oops: [#1] SMP PTI kernel: [2468259.014161] Modules linked in: vhost_net vhost tap xt_nat xt_REDIRECT nf_nat_redirect ip6table_mangle xt_mark xt_connmark xt_multiport xt_set ip_set_hash_net ip_set xt_CT xt_mac veth vxlan ip6_udp_tunnel udp_tunnel ip6table_raw xt_physdev xt_comment xt_CHECKSUM xt_tcpudp iptable_mangle iptable_raw ebtable_filter ebtables nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter bridge aufs rbd libceph binfmt_misc 8021q garp mrp stp llc bonding openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 rdma_ucm(OE) ib_ucm(OE) nf_defrag_ipv6 ib_ipoib(OE) ip6table_filter ib_umad(OE) xt_conntrack mlx5_fpga_tools(OE) mlx5_ib(OE) ib_uverbs(OE) iptable_filter mlx4_ib(OE) mlx4_en(OE) mlx4_core(OE) ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_addrtype iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack kernel: [2468259.085884] ip_tables ipmi_ssif intel_rapl skx_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper dell_smbios dcdbas cryptd intel_cstate dell_wmi_descriptor wmi_bmof intel_rapl_perf mei_me mei lpc_ich shpchp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid rdma_cm(OE) iw_cm(OE) ib_cm(OE) ib_core(OE) iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip6_tables x_tables autofs4 mgag200 i2c_algo_bit ttm mlx5_core(OE) mlxfw(OE) devlink drm_kms_helper syscopyarea sysfillrect bnx2x mlx_compat(OE) sysimgblt ptp fb_sys_fops pps_core mdio drm libcrc32c ahci libahci wmi kernel: [2468259.148257] CPU: 21 PID: 3455197 Comm: CPU 11/KVM Tainted: G OE4.15.0-55-generic #60~16.04.2-Ubuntu kernel: [2468259.158712] Hardware name: Dell Inc. PowerEdge R640/0PHYDR, BIOS 2.2.10 05/15/2019 kernel: [2468259.166510] RIP: 0010:kvm_mmu_flush_or_zap+0x5/0x40 [kvm] kernel: [2468259.172097] RSP: 0018:ad129f5b3ac8 EFLAGS: 00010246 kernel: [2468259.177514] RAX: RBX: 93dcbb5df5a8 RCX: kernel: [2468259.184840] RDX: RSI: RDI: 940b7ff38000 kernel: [2468259.192168] RBP: ad129f5b3b30 R08: 0001 R09: kernel: [2468259.199495] R10: 0001 R11: 0781 R12: 940b7ff38000 kernel: [2468259.206820] R13: R14: R15: 00802800 kernel: [2468259.214151] FS: 7f6de8ff9700() GS:9411ff28() knlGS:964c1f4c kernel: [2468259.222431] CS: 0010 DS: ES: CR0: 80050033 kernel: [2468259.228369] CR2: CR3: 00b54b6f8002 CR4: 007626e0 kernel: [2468259.235694] DR0: DR1: DR2: kernel: [2468259.243018] DR3: DR6: fffe0ff0 DR7: 0400 kernel: [2468259.250348] PKRU: 5554 kernel: [2468259.253245] Call Trace: kernel: [2468259.255910] ? kvm_mmu_get_page+0x29a/0x6b0 [kvm] kernel: [2468259.260814] __direct_map.part.124+0xf5/0x220 [kvm] kernel: [2468259.265901] tdp_page_fault+0x264/0x290 [kvm] kernel: [2468259.270462] kvm_mmu_page_fault+0x62/0x170 [kvm] kernel: [2468259.275278] handle_ept_violation+0xae/0x140 [kvm_intel] kernel: [2468259.280781] vmx_handle_exit+0xb3/0xcd0 [kvm_intel] kernel: [2468259.285867] ? vmx_vcpu_run+0x41d/0x600 [kvm_intel] kernel: [2468259.290960] vcpu_enter_guest+0x451/0x1280 [kvm] kernel: [2468259.295774] ? vmx_sync_pir_to_irr+0x39/0x70 [kvm_intel] kernel: [2468259.301307] kvm_arch_vcpu_ioctl_run+0x270/0x3d0 [kvm] kernel: [2468259.306652] ? kvm_arch_vcpu_ioctl_run+0x270/0x3d0 [kvm] kernel: [2468259.312163] kvm_vcpu_ioctl+0x33a/0x610 [kvm] kernel: [2468259.317432] ? do_futex+0x10f/0x500 kernel: [2468259.321830] do_vfs_ioctl+0xa4/0x600 kernel: [2468259.326244] ? SyS_futex+0x7f/0x180 kernel: [2468259.330523] SyS_ioctl+0x79/0x90 kernel: [2468259.334561] do_syscall_64+0x73/0x130 kernel: [2468259.338992] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 kernel: [2468259.344817] RIP: 0033:0x7f6e379b2f47 kernel: [2468259.349187] RSP: 002b:7f6de8ff88f8 EFLAGS: 0246 ORIG_RAX: 0010 kernel: [2468259.357529] RAX: ff
[Kernel-packages] [Bug 1780590] Re: no wireless adapter was found ubuntu 18.04
** Changed in: linux-oem-osp1 (Ubuntu Eoan) Status: New => Won't Fix ** Changed in: linux-oem-osp1 (Ubuntu Focal) Status: New => Won't Fix -- 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/1780590 Title: no wireless adapter was found ubuntu 18.04 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: New Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-firmware source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Confirmed Status in linux-firmware source package in Focal: New Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] There's no in-kernel support for Realtek 8723DE, so users need to use out-of-tree DKMS which is not from Ubuntu archive. This has security implication and should be avoided. Also this provides pretty bad user experience. [Fix] Add support to Realtek 8723DE. All commits are cherry-picked from Realtek maintained repo: https://github.com/rtlwifi-linux/rtw88_8723de [Test] With the patch series applied, 8723DE can scan and connect to APs succesfully. Also did some S3 smoke test, it continues to work. [Regression Potential] Low. The device in question was never supported, and if there's any regression, we can count on Realtek Wireless team, thy are now pretty responsive on upstream mailing list. === Original Bug Report === recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. Everything in the installation was fine until the moment to start session. The problem is that the wireless network card does not detect me and when entering the configuration I simply get an error message saying that no wireless adapter was found. I have already followed all the tutorials I found on the web. and update the driver of a github repository, and install how much program they told me to install and I still can not connect via wifi. I just do not know what to do. I have a laptop hp 14-bs004 came with windows 10 installed. The information on the network card is as follows: Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: d723] Subsystem: Hewlett-Packard Company Device [103c: 8319] Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort- SERR- Kernel modules: wl already install the most recent kernel, already intale driver driver realtek rtl8723be according to the instructions of the git repository. and nothing has worked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 7 22:57:40 2018 InstallationDate: Installed on 2018-07-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_MX.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780590/+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 1848939] Re: Resume from suspend
I ran the bisect and the end result is `3f677f9c998a18d11641b5a2de6f11d0af32a153`. But I'm unsure if this is accurate because at some point the kernel just stop working. -- 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/1848939 Title: Resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: The screen stays black when resume from suspend systematically. Also the trackpad does not always work when booting. A few reboot are needed sometime to have a working environment. I'am unsure if the trackpad issue is related. I tried some mainline kernels. Suspend works with kernels 5.2*, the trackpad issue is still present, but seems less frequent. All kernels 5.3.* and 5.4-rc* have the same issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nathaniel 1328 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 20 13:31:24 2019 InstallationDate: Installed on 2019-10-19 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:55a4 Generic Goodix FingerPrint Device Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20R9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=8df6a4ab-733f-4e29-b46a-e3f7ded2bafd ro quiet splash modprobe.blacklist=nouveau vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9YCN33WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IWL dmi.modalias: dmi:bvnLENOVO:bvr9YCN33WW:bd05/09/2019:svnLENOVO:pn20R9:pvrLenovoThinkBook13s-IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IWL: dmi.product.family: ThinkBook 13s-IWL dmi.product.name: 20R9 dmi.product.sku: LENOVO_MT_20R9_BU_idea_FM_ThinkBook 13s-IWL dmi.product.version: Lenovo ThinkBook 13s-IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848939/+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 1839836] Re: acct02 from ubuntu_ltp_syscalls failed on X/B/D/E-s390x
Passed with X-fips s390x KVM
--
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/1839836
Title:
acct02 from ubuntu_ltp_syscalls failed on X/B/D/E-s390x
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Disco:
New
Status in linux source package in Eoan:
Incomplete
Bug description:
Error message on D-s390x KVM:
startup='Thu Oct 3 01:17:21 2019'
tst_kconfig.c:62: INFO: Parsing kernel config
'/boot/config-4.15.0-66-generic'
tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s
tst_kconfig.c:62: INFO: Parsing kernel config
'/boot/config-4.15.0-66-generic'
acct02.c:239: INFO: Verifying using 'struct acct_v3'
acct02.c:192: INFO: == entry 1 ==
acct02.c:82: INFO: ac_comm != 'acct02_helper' ('systemd-udevd')
acct02.c:133: INFO: ac_exitcode != 32768 (0)
acct02.c:141: INFO: ac_ppid != 32327 (705)
acct02.c:147: INFO: ac_version != 3 (131)
acct02.c:192: INFO: == entry 2 ==
acct02.c:147: INFO: ac_version != 3 (131)
acct02.c:192: INFO: == entry 3 ==
acct02.c:82: INFO: ac_comm != 'acct02_helper' ('acct02')
acct02.c:133: INFO: ac_exitcode != 32768 (0)
acct02.c:141: INFO: ac_ppid != 32327 (32326)
acct02.c:147: INFO: ac_version != 3 (131)
acct02.c:182: FAIL: end of file reached
Summary:
passed 0
failed 1
skipped 0
warnings 0
This was not spotted on other arches on D, just s390x
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-25-generic 5.0.0-25.26
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-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.10-0ubuntu27.1
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:
[435066.563428] LTP: starting acct02
[435067.737885] Process accounting resumed
Date: Mon Aug 12 13:49:49 2019
HibernationDevice: RESUME=UUID=eae923f9-f5a4-41c0-b3e4-04786207dbaa
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcFB:
ProcKernelCmdLine: root=UUID=1a6af794-84a9-4034-a213-39506b9bb91c
crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
linux-restricted-modules-5.0.0-25-generic N/A
linux-backports-modules-5.0.0-25-generic N/A
linux-firmware1.178.4
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-kernel-tests/+bug/1839836/+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 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1850799 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs -- 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/1849855 Title: bionic/linux: 4.15.0-68.77 -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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 29. October 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1850799 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+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 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker
4.15.0-68.77 - generic Regression test CMPL, RTB. Test case ubuntu_seccomp does not exist in the database, please check Issue to note in amd64: ubuntu_bpf - test_maps failed (bug 1837386) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) apic-split timeouted (bug 1821390) ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) cpuset_hotplug (bug 1834006) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01, statx04 (bug 1842266) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) ubuntu_xfstests_btrfs - generic/268 time out ubuntu_xfstests_ext4 - generic/430 time out ubuntu_xfstests_xfs - generic/430 time out Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_bpf - test_maps failed (bug 1837386) ubuntu_ftrace_smoke_test - timeout on node wright, passed on moonshot (bug 1851222) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) raw_skew in timer (bug 1811194) ubuntu_kvm_unit_tests - gicv3-ipi and gicv3-active failed on Moonshot (bug 1790825) ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) cpuhotplug03 (bug 1836167) cpuhotplug04 (bug 1836169) cpuhotplug06 (bug 1836170) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01, statx04 (bug 1842266) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) ubuntu_xfstests_btrfs - generic/390 time out ubuntu_xfstests_ext4 - generic/430 time out ubuntu_xfstests_xfs - generic/430 time out Issue to note in i386: ubuntu_bpf - Some test in test_verifier failed on i386 Bionic (bug 1788578) test_maps failed (bug 1837386) ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) raw_skew in timer (bug 1811194) ubuntu_kvm_unit_tests - msr on i386 (bug 1822235) tsc on i386 (bug 1822235) vmexit_cpuid on i386 (bug 1822235) vmexit_inl_pmtimer on i386 (bug 1822235) vmexit_ipi on i386 (bug 1822235) vmexit_ipi_halt on i386 (bug 1822235) vmexit_mov_from_cr8 on i386 (bug 1822235) vmexit_mov_to_cr8 on i386 (bug 1822235) vmexit_ple_round_robin on i386 (bug 1822235) vmexit_tscdeadline on i386 (bug 1822235) vmexit_tscdeadline_immed on i386 (bug 1822235) vmexit_vmcall on i386 (bug 1822235) ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01, statx04 (bug 1842266) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) ubuntu_xfstests_btrfs - generic/430 time out ubuntu_xfstests_ext4 - generic/256 time out ubuntu_xfstests_xfs - generic/105 time out 52 / 55 tests were run, missing: ubuntu_boot, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in ppc64le (P8): hwclock - hwclock test failed on PowerPC due to 0.x sec difference (bug 1802233) ubuntu_bpf - test_maps failed (bug 1837386) ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) raw_skew in timer (bug 1811194) ubuntu_ltp - proc01 (bug 1829849) fs_fill (bug 1842266) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) cpuset_base_ops cpuset_exclusive cpuset_hierarchy cpuset_hotplug cpuset_inherit cpuset_load_balance cpuset_memory cpuset_memory_pressure cpuset_memory_spread cpuset_sched_domains cpuset_syscall in controller (bug 1836188) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ubuntu_ltp_syscalls - fallocate04, fallocate05, fdatasync03, fremovexattr01, fremovexattr02, fsync01, fsync04, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, sync03, syncfs01, sync_file_range02, copy_file_range01, statx04 (bug 1842266) fallocate05 (bug 1783880) fsetxattr01, fgetxattr01, fanotify13, fanotify14, lremovexattr01, setxattr01 (bug 1842266) stime01 (bug 1845620) ubuntu_lxc - Failed to download image index (bug 1839835) ubuntu_xfstests_btrfs - generic/334 time out 52 / 55 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4
[Kernel-packages] [Bug 1851216] Re: System hangs at early boot
** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux-oem (Ubuntu) Status: Confirmed => Invalid -- 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/1851216 Title: System hangs at early boot Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: After upgrading kernel to linux-image-4.15.0-1061 (proposed), system hangs at very beginning of booting, leaving Grub messages "loading..." on the console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1060-oem 4.15.0-1060.69 ProcVersionSignature: Ubuntu 4.15.0-1060.69-oem 4.15.18 Uname: Linux 4.15.0-1060-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: u 1977 F...m pulseaudio /dev/snd/pcmC1D0p: u 1977 F...m pulseaudio /dev/snd/controlC0: u 1977 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 4 17:15:56 2019 InstallationDate: Installed on 2019-11-04 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Precision 5530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1060-oem root=UUID=baa02b0a-d18f-41d2-9e2b-2d057742013c ro mem_sleep_default=deep nvidia-drm.modeset=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-1060-oem N/A linux-backports-modules-4.15.0-1060-oem N/A linux-firmware 1.173.9 SourcePackage: linux-oem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 0184M4 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd06/27/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0184M4:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1851216/+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 1849041] Re: xenial/linux-aws: 4.4.0-1097.108 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849051 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 22. October 2019 15:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1849040 variant: debs -- 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/1849041 Title: xenial/linux-aws: 4.4.0-1097.108 -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: 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 verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849051 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 22. October 2019 15:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1849040 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849041/+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 1850480] Re: eoan/linux-azure: 5.3.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850486 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 31. October 2019 12:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1850965 variant: debs -- 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/1850480 Title: eoan/linux-azure: 5.3.0-1006.6 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850486 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 31. October 2019 12:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1850965 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850480/+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 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed
** Tags added: sru-20191021 ** Tags added: oracle -- 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/1829979 Title: memcg_max_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Bug description: startup='Wed May 22 05:58:50 2019' memcg_max_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_max_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 1 TINFO: Warming up pid: 30821 memcg_max_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 30821 memcg_max_usage_in_bytes_test 1 TFAIL: memory.max_usage_in_bytes is 4325376, 4194304 expected memcg_max_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TCONF: mem+swap is not enabled memcg_max_usage_in_bytes_test 2 TINFO: Starting test 3 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 2 TINFO: Warming up pid: 30855 memcg_max_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 30855 memcg_max_usage_in_bytes_test 2 TFAIL: memory.max_usage_in_bytes is 4329472, 4194304 expected memcg_max_usage_in_bytes_test 3 TFAIL: memory.max_usage_in_bytes is 8192, 0 expected memcg_max_usage_in_bytes_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_max_usage_in_bytes_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 4 TCONF: mem+swap is not enabled tag=memcg_max_usage_in_bytes stime=1558504730 dur=3 exit=exited stat=33 core=no cu=8 cs=7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:06:31 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829979/+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 1849041] Re: xenial/linux-aws: 4.4.0-1097.108 -proposed tracker
** Tags added: regresion-testing-passed ** Tags removed: regresion-testing-passed ** Tags added: regression-testing-passed -- 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/1849041 Title: xenial/linux-aws: 4.4.0-1097.108 -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: 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 verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849051 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 22. October 2019 15:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1849040 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849041/+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 1850480] Re: eoan/linux-azure: 5.3.0-1006.6 -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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1850480 Title: eoan/linux-azure: 5.3.0-1006.6 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850486 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 31. October 2019 12:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1850965 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850480/+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 1821390] Re: apic-split will fail in kvm_units_tests
** Tags added: sru-20191021 ** Tags removed: cosmic ** Tags added: oracle -- 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/1821390 Title: apic-split will fail in kvm_units_tests Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux source package in Cosmic: Incomplete Status in linux-aws source package in Cosmic: New Status in linux-azure source package in Cosmic: New Bug description: Reproducible: Yes, every time. Series: cosmic Kernel: "linux-aws 4.18.0-1012.14" Steps: 1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd /tmp/tmp.ZHQwPUOuLD qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.8001H:ECX.svm [bit 2] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 apic version: 1050014 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id PASS: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic disabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear PASS: apic_disable: *0xfee00030: PASS: apic_disable: CR8: 0 PASS: apic_disable: CR8: f PASS: apic_disable: *0xfee00080: PASS: apic_disable: Local apic enabled in xAPIC mode PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: *0xfee00030: 1050014 PASS: apic_disable: *0xfee00080: 0 PASS: apic_disable: *0xfee00080: f0 PASS: apic_disable: Local apic enabled in x2APIC mode PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: *0xfee00030: PASS: apic_disable: CR8: 0 PASS: apic_disable: CR8: f PASS: apic_disable: *0xfee00080: x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: x2apic enabled to disabled state PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand FAIL: PV IPIs testing PASS: nmi-after-sti PASS: multiple nmi PASS: APIC LVT timer one shot starting apic change mode PASS: TMICT value reset PASS: TMCCT should have a non-zero value PASS: TMCCT should have reached 0 PASS: TMCCT should have a non-zero value PASS: TMCCT should not be reset to TMICT value PASS: TMCCT should be reset to the initial-count PASS: TMCCT should not be reset to init PASS: TMCCT should have reach zero PASS: TMCCT should stay at zero PASS: tsc deadline timer PASS: tsc deadline timer clearing SUMMARY: 51 tests, 1 unexpected failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+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 1848989] Re: disco/linux-azure: 5.0.0-1024.25 -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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1848989 Title: disco/linux-azure: 5.0.0-1024.25 -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: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850574 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Wednesday, 23. October 2019 09:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1848987 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848989/+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 1848989] Re: disco/linux-azure: 5.0.0-1024.25 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850574 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Wednesday, 23. October 2019 09:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1848987 variant: debs -- 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/1848989 Title: disco/linux-azure: 5.0.0-1024.25 -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: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850574 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Wednesday, 23. October 2019 09:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1848987 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848989/+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 1849020] Re: bionic/linux-ibm-gt: 4.15.0-1040.42 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849855 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Testing phase-changed: Thursday, 24. October 2019 12:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- 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/1849020 Title: bionic/linux-ibm-gt: 4.15.0-1040.42 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849855 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Testing phase-changed: Thursday, 24. October 2019 12:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849020/+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 1849020] Re: bionic/linux-ibm-gt: 4.15.0-1040.42 -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 in Ubuntu. https://bugs.launchpad.net/bugs/1849020 Title: bionic/linux-ibm-gt: 4.15.0-1040.42 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849855 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Testing phase-changed: Thursday, 24. October 2019 12:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849020/+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 1851314] [NEW] upgrade from 19.04 to 19.10 fails to upgrade zfsutils-linux package
Public bug reported: # apt get upgrade tells me: The following packages have been kept back: zfsutils-linux 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. But I'm pretty sure I need the newer 0.8.1-1ubuntu14 package because the previous version 0.7.12-1ubuntu5 zfs command fails: zfs: symbol lookup error: zfs: undefined symbol: libzfs_dataset_cmp When I try to ask for the kept back page to be upgraded: # apt dist-upgrade -y zfsutils-linux The following packages have unmet dependencies: zfsutils-linux : Conflicts: insserv (< 1.18) but 1.14.0-5ubuntu3 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. I really don't understand the <1.18 when 1.14.0 looks less than 1.18. Is there a workaround? whoa... on a whim, I tried apt-get instead of apt. It seems to have worked. $ sudo apt-get install zfsutils-linux I'm filing this bug so that others may find this work around. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1851314 Title: upgrade from 19.04 to 19.10 fails to upgrade zfsutils-linux package Status in zfs-linux package in Ubuntu: New Bug description: # apt get upgrade tells me: The following packages have been kept back: zfsutils-linux 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. But I'm pretty sure I need the newer 0.8.1-1ubuntu14 package because the previous version 0.7.12-1ubuntu5 zfs command fails: zfs: symbol lookup error: zfs: undefined symbol: libzfs_dataset_cmp When I try to ask for the kept back page to be upgraded: # apt dist-upgrade -y zfsutils-linux The following packages have unmet dependencies: zfsutils-linux : Conflicts: insserv (< 1.18) but 1.14.0-5ubuntu3 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. I really don't understand the <1.18 when 1.14.0 looks less than 1.18. Is there a workaround? whoa... on a whim, I tried apt-get instead of apt. It seems to have worked. $ sudo apt-get install zfsutils-linux I'm filing this bug so that others may find this work around. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1851314/+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 1851304] [NEW] BCM4352 802.11ac - driver=wl0 driverversion=6.30.223.271 - can't see 5Ghz Mesh Network
Public bug reported: lsb_release -rd Description:Pop!_OS 19.10 Release:19.10 apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installed: 6.30.223.271+bdcom-0ubuntu5 Candidate: 6.30.223.271+bdcom-0ubuntu5 Version table: *** 6.30.223.271+bdcom-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu eoan/restricted amd64 Packages 100 /var/lib/dpkg/status Expected to be able to use the NIC on a Mesh Network. Instead only 2.4Ghz is found/connected, which perform really bad <10mbps on a 300mbps line. When using a "normal" dual band router the NIC finds 5Ghz network fine also connects fine this, now the performance is round 300mbps. When testing other nic/devices on the mesh network the performance is round 300mbps - hence the mesh network works fine. ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Summary changed: - BCM4352 802.11ac - driver=wl0 driverversion=6.30.223.271 can't see %Ghz Mesh Network + BCM4352 802.11ac - driver=wl0 driverversion=6.30.223.271 can't see 5Ghz Mesh Network ** Summary changed: - BCM4352 802.11ac - driver=wl0 driverversion=6.30.223.271 can't see 5Ghz Mesh Network + BCM4352 802.11ac - driver=wl0 driverversion=6.30.223.271 - can't see 5Ghz Mesh Network -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1851304 Title: BCM4352 802.11ac - driver=wl0 driverversion=6.30.223.271 - can't see 5Ghz Mesh Network Status in bcmwl package in Ubuntu: New Bug description: lsb_release -rd Description: Pop!_OS 19.10 Release: 19.10 apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installed: 6.30.223.271+bdcom-0ubuntu5 Candidate: 6.30.223.271+bdcom-0ubuntu5 Version table: *** 6.30.223.271+bdcom-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu eoan/restricted amd64 Packages 100 /var/lib/dpkg/status Expected to be able to use the NIC on a Mesh Network. Instead only 2.4Ghz is found/connected, which perform really bad <10mbps on a 300mbps line. When using a "normal" dual band router the NIC finds 5Ghz network fine also connects fine this, now the performance is round 300mbps. When testing other nic/devices on the mesh network the performance is round 300mbps - hence the mesh network works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1851304/+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 1742560] Re: zfsutils-linux recommends dkms when it's not needed
Are there any plans to correct the Xenial's package? ** Changed in: zfs-linux (Ubuntu Xenial) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1742560 Title: zfsutils-linux recommends dkms when it's not needed Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Incomplete Status in zfs-linux source package in Artful: Fix Released Status in zfs-linux source package in Bionic: Fix Released Bug description: 1. $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 2. $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu18 Candidate: 0.6.5.6-0ubuntu18 Version table: *** 0.6.5.6-0ubuntu18 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 3. apt install zfsutils-linux does not install dkms,spl-dkms and dependencies since 16.04 kernel already contains zfs.ko 4. apt install zfsutils-linux installs all of the following: dkms fakeroot gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libfakeroot libfreetype6 libgcc-5-dev libgomp1 libitm1 liblsan0 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages-dev spl spl-dkms and then any kernel install/update then attempts to dkms rebuild zfs and spl even though the modules are already provided. % dpkg -S /lib/modules/4.13.0-19-generic/kernel/zfs/zfs/zfs.ko linux-image-4.13.0-19-generic: /lib/modules/4.13.0-19-generic/kernel/zfs/zfs/zfs.ko % dpkg -S /lib/modules/4.13.0-19-generic/kernel/zfs/spl/spl.ko linux-image-4.13.0-19-generic: /lib/modules/4.13.0-19-generic/kernel/zfs/spl/spl.ko We can see from the package requirements, that it Recommends zfs-dkms, but only on Xenial. Releases newer than Xenial do not have this package requirement. % apt-cache show zfsutils-linux Package: zfsutils-linux Architecture: amd64 Version: 0.6.5.6-0ubuntu18 Priority: extra Section: admin Source: zfs-linux Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Darik Horn Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 779 Provides: zfs Depends: init-system-helpers (>= 1.18~), zfs-doc (= 0.6.5.6-0ubuntu18), libblkid1 (>= 2.16), libc6 (>= 2.14), libnvpair1linux, libuuid1 (>= 2.16), libuutil1linux, libzfs2linux, libzpool2linux, python3:any (>= 3.3.2-2~), python3 Recommends: zfs-dkms, zfs-zed Suggests: samba-common-bin (>= 3.0.23), nfs-kernel-server, zfs-initramfs Conflicts: zfs, zfs-fuse Replaces: zfs Filename: pool/main/z/zfs-linux/zfsutils-linux_0.6.5.6-0ubuntu18_amd64.deb Size: 275970 MD5sum: 02ead25f1fed812980d70865da916468 SHA1: e6736c223c3b2198bba8777153836bb8d4789518 SHA256: c4ad2b81ee13072cb3f4e31fd3aed93cf66c7c50872fc542cc2425120b222eed Homepage: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.6 Description-en: Native OpenZFS management utilities for Linux This package provides the zpool and zfs commands that are used to manage OpenZFS filesystems. Description-md5: 7b0f98269f6c33505790717cd478736c Supported: 5y Here's Artful ~$ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache show zfsutils-linux Package: zfsutils-linux Architecture: amd64 Version: 0.6.5.11-1ubuntu3 Priority: extra Section: admin Source: zfs-linux Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian ZFS on Linux maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1100 Provides: zfsutils Depends: init-system-helpers (>= 1.18~), libblkid1 (>= 2.16), libc6 (>= 2.14), libnvpair1linux, libuuid1 (>= 2.16), libuutil1linux, libzfs2linux, libzpool2linux, python3:any, python3 Recommends: lsb-base, zfs-zed Suggests: nfs-kernel-server, samba-common-bin (>= 3.0.23), zfs-initramfs | zfs-dracut Conflicts: zfs, zfs-fuse, zutils Filename: pool/main/z/zfs-linux/zfsutils-linux_0.6.5.11-1ubuntu3_amd64.deb Size: 328574 MD5sum: d1ce7f5ffa75c9b46e7d5285430efff3 SHA1: 8a8ab05186b83c3f25e07d4e8fe04e60ec314640 SHA256: c462a555dda50ed12424a51158666bd3cbe1befb93a34ac81f03548051fa0b50 Homepage: http://www.zfsonlinux.org/ Description-en: command-line tools to manage OpenZFS filesystems The Z file system is a pooled filesystem designed for maximum data integrity, supporting data snapshots, multiple copies, and data checksums. . This package provides the zfs and zpool commands to create and administer OpenZFS filesystems. Description-md5: 3b2c00b92882937cb7252c01e41d8975 Supported: 9m ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubunt
[Kernel-packages] [Bug 1848953] Re: Intel wifi 3165 [8086:3165] subsystem id [8086:4010] not working properly in Ubuntu 19.10
Hi there! I returned home and did the following: 1. Removed dkms driver sudo apt purge backport-iwlwifi-dkms 2. Installed the latest RC mainline kernel ls -al total 70352 drwxr-xr-x 2 florin florin 4096 nov 4 23:37 . drwxr-xr-x 5 florin florin 4096 nov 4 23:48 .. -rw-r--r-- 1 florin florin 10897624 nov 4 23:36 linux-headers-5.4.0-050400rc6_5.4.0-050400rc6.201911031940_all.deb -rw-r--r-- 1 florin florin 1179332 nov 4 23:37 linux-headers-5.4.0-050400rc6-generic_5.4.0-050400rc6.201911031940_amd64.deb -rw-r--r-- 1 florin florin 8766748 nov 4 23:37 linux-image-unsigned-5.4.0-050400rc6-generic_5.4.0-050400rc6.201911031940_amd64.deb -rw-r--r-- 1 florin florin 51181032 nov 4 23:37 linux-modules-5.4.0-050400rc6-generic_5.4.0-050400rc6.201911031940_amd64.deb sudo dpkg -i *.deb 3. Restarted 4. Tested the kernel and tried to connect the 2.4 GHz network. uname -a Linux florin-SATELLITE-P50-C 5.4.0-050400rc6-generic #201911031940 SMP Mon Nov 4 00:43:05 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux 5. Cannot connect 2.4, then it connects automatically to the 5 GHz. Cheked, in the additional drivers list it looks like a not functional wifi card, just like before. In Ubuntu 19.04 it worked, BTW, something changed meanwhile. 6. /var/log/dmesg is attached. ** Attachment added: "dmesg log for 2.4 ghz wifi not working on intel wifi card" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848953/+attachment/5302835/+files/dmesg -- 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/1848953 Title: Intel wifi 3165 [8086:3165] subsystem id [8086:4010] not working properly in Ubuntu 19.10 Status in linux package in Ubuntu: Confirmed Bug description: I have a clean install of the latest Ubuntu, 19.10, but since the live usb, a bug appeared. I could not login to the 2.4 GHz Wifi network at home with the fresh installed Ubuntu, it says the password is wrong, but it is not. I have Dual Band Intel AC 3165 it seems. My card appears in the Additional Drivers list with the notice that the device is not working. I can connect the 5 GHz wifi, but not the 2.4 GHz. See the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: florin 1194 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 22:49:04 2019 InstallationDate: Installed on 2019-10-19 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:5652 IMC Networks TOSHIBA Web Camera - HD Bus 001 Device 006: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA SATELLITE P50-C ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=0b07e060-55a5-4186-8670-bce4c230e596 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.50 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: SATELLITE P50-C dmi.product.sku: PSPUFE dmi.product.version: PSPUFE-001009G6 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848953/+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 1850739] Re: Revert the firmware update for sound/sof
** Also affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Eoan) Importance: Undecided Status: New -- 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/1850739 Title: Revert the firmware update for sound/sof Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Disco: New Status in linux-firmware source package in Eoan: New Bug description: SRU Justification Impact: An update to the sound sof firmware does not set the PV bit for cometlake, and thus will not load. This is a regression on cometlake platforms. Fix: Revert the update. Test Case: Check that the firmware will load on affected platforms. Regression Potential: This fixes a regression on cometlake paltforms, but will regress the platforms fixed by the patch being reverted. --- I submitted a firmware update for sound/sof, the tracking bug number is: https://bugs.launchpad.net/bugs/1847250 Recently we found this update introduced one problem for cometlake platforms, cometlake need to check PV bit when loading the firmware, but this update doesn't set the PV bit for cometlake, as a result, on cometlake platforms, it always fails to load the firmware. So we should revert this update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1850739/+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 1849598] Re: [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support
** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Disco) Importance: Undecided Status: New -- 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/1849598 Title: [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-firmware source package in Bionic: New Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Disco: New Status in linux-firmware source package in Disco: New Status in linux-oem source package in Disco: New Status in linux source package in Eoan: New Status in linux-firmware source package in Eoan: New Status in linux-oem source package in Eoan: New Bug description: SRU justification: [Impact] Current kernel and firmware lack support of rtl8822cu Bluetooth. [Fix] Add and update the Bluetooth driver and firmware of rtl8822cu. [Test] Verified on hardware. Tests results are good. [Regression Potential] Low. Add new bt chip ID; Add the new firmware and config to enable new bt chip. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1849598/+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 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Stalled -- review in progress variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -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-lrm 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+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 1850739] Re: Revert the firmware update for sound/sof
** Description changed: + SRU Justification + + Impact: An update to the sound sof firmware does not set the PV bit for + cometlake, and thus will not load. This is a regression on cometlake + platforms. + + Fix: Revert the update. + + Test Case: Check that the firmware will load on affected platforms. + + Regression Potential: This fixes a regression on cometlake paltforms, + but will regress the platforms fixed by the patch being reverted. + + --- + I submitted a firmware update for sound/sof, the tracking bug number is: https://bugs.launchpad.net/bugs/1847250 Recently we found this update introduced one problem for cometlake platforms, cometlake need to check PV bit when loading the firmware, but this update doesn't set the PV bit for cometlake, as a result, on cometlake platforms, it always fails to load the firmware. So we should revert this update -- 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/1850739 Title: Revert the firmware update for sound/sof Status in linux-firmware package in Ubuntu: Confirmed Bug description: SRU Justification Impact: An update to the sound sof firmware does not set the PV bit for cometlake, and thus will not load. This is a regression on cometlake platforms. Fix: Revert the update. Test Case: Check that the firmware will load on affected platforms. Regression Potential: This fixes a regression on cometlake paltforms, but will regress the platforms fixed by the patch being reverted. --- I submitted a firmware update for sound/sof, the tracking bug number is: https://bugs.launchpad.net/bugs/1847250 Recently we found this update introduced one problem for cometlake platforms, cometlake need to check PV bit when loading the firmware, but this update doesn't set the PV bit for cometlake, as a result, on cometlake platforms, it always fails to load the firmware. So we should revert this update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1850739/+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 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Regarding 1) :
$ uname -a
Linux rog 5.4.0-050400rc5-generic #201910271430 SMP Sun Oct 27 18:33:09 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
and issue is still present.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor 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
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+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 1780590] Re: no wireless adapter was found ubuntu 18.04
** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Expired ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: linux (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux (Ubuntu Eoan) Status: New => Won't Fix ** Changed in: linux (Ubuntu Focal) Status: Expired => Confirmed ** Changed in: linux-oem-osp1 (Ubuntu Disco) Status: New => Won't Fix -- 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/1780590 Title: no wireless adapter was found ubuntu 18.04 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: New Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-firmware source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: Confirmed Status in linux-firmware source package in Focal: New Status in linux-oem-osp1 source package in Focal: New Bug description: === SRU Justification === [Impact] There's no in-kernel support for Realtek 8723DE, so users need to use out-of-tree DKMS which is not from Ubuntu archive. This has security implication and should be avoided. Also this provides pretty bad user experience. [Fix] Add support to Realtek 8723DE. All commits are cherry-picked from Realtek maintained repo: https://github.com/rtlwifi-linux/rtw88_8723de [Test] With the patch series applied, 8723DE can scan and connect to APs succesfully. Also did some S3 smoke test, it continues to work. [Regression Potential] Low. The device in question was never supported, and if there's any regression, we can count on Realtek Wireless team, thy are now pretty responsive on upstream mailing list. === Original Bug Report === recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. Everything in the installation was fine until the moment to start session. The problem is that the wireless network card does not detect me and when entering the configuration I simply get an error message saying that no wireless adapter was found. I have already followed all the tutorials I found on the web. and update the driver of a github repository, and install how much program they told me to install and I still can not connect via wifi. I just do not know what to do. I have a laptop hp 14-bs004 came with windows 10 installed. The information on the network card is as follows: Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: d723] Subsystem: Hewlett-Packard Company Device [103c: 8319] Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort- SERR- Kernel modules: wl already install the most recent kernel, already intale driver driver realtek rtl8723be according to the instructions of the git repository. and nothing has worked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 7 22:57
[Kernel-packages] [Bug 1851273] 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/1851273 Title: monitor continuously goes on/off when energy saver is active Status in linux package in Ubuntu: Confirmed Bug description: Hi, When monitor should power off (because of power saver timeout), he continuously wake on/off: - screen became black - monitor power off as no signal - after a second he wake on again - repeat I know that could be hard to imagine the situation, so i attached a video. I assume that software/hardware info are already included (as i used ubuntu-bug), but if not tell me. Thanks for all your work :) PS sorry if bug report is wrong (that's the first time) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 962 F pulseaudio /dev/snd/controlC2: marco 962 F pulseaudio /dev/snd/controlC1: marco 962 F pulseaudio CurrentDesktop: KDE Date: Mon Nov 4 19:12:28 2019 InstallationDate: Installed on 2019-11-03 (0 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Packard Bell imedia S3840 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=f81de2b9-ff5a-4f92-af94-ac09f37653f4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: imedia S3840 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd07/08/2011:svnPackardBell:pnimediaS3840:pvrP01-B1:rvnPackardBell:rnimediaS3840:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name: imedia S3840 dmi.product.sku: To be filled by O.E.M. dmi.product.version: P01-B1 dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851273/+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 1851273] [NEW] monitor continuously goes on/off when energy saver is active
Public bug reported: Hi, When monitor should power off (because of power saver timeout), he continuously wake on/off: - screen became black - monitor power off as no signal - after a second he wake on again - repeat I know that could be hard to imagine the situation, so i attached a video. I assume that software/hardware info are already included (as i used ubuntu-bug), but if not tell me. Thanks for all your work :) PS sorry if bug report is wrong (that's the first time) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 962 F pulseaudio /dev/snd/controlC2: marco 962 F pulseaudio /dev/snd/controlC1: marco 962 F pulseaudio CurrentDesktop: KDE Date: Mon Nov 4 19:12:28 2019 InstallationDate: Installed on 2019-11-03 (0 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Packard Bell imedia S3840 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=f81de2b9-ff5a-4f92-af94-ac09f37653f4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: imedia S3840 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd07/08/2011:svnPackardBell:pnimediaS3840:pvrP01-B1:rvnPackardBell:rnimediaS3840:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name: imedia S3840 dmi.product.sku: To be filled by O.E.M. dmi.product.version: P01-B1 dmi.sys.vendor: Packard Bell ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan ** Attachment added: "video.mp4" https://bugs.launchpad.net/bugs/1851273/+attachment/5302778/+files/video.mp4 -- 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/1851273 Title: monitor continuously goes on/off when energy saver is active Status in linux package in Ubuntu: Confirmed Bug description: Hi, When monitor should power off (because of power saver timeout), he continuously wake on/off: - screen became black - monitor power off as no signal - after a second he wake on again - repeat I know that could be hard to imagine the situation, so i attached a video. I assume that software/hardware info are already included (as i used ubuntu-bug), but if not tell me. Thanks for all your work :) PS sorry if bug report is wrong (that's the first time) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-19-generic 5.3.0-19.20 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marco 962 F pulseaudio /dev/snd/controlC2: marco 962 F pulseaudio /dev/snd/controlC1: marco 962 F pulseaudio CurrentDesktop: KDE Date: Mon Nov 4 19:12:28 2019 InstallationDate: Installed on 2019-11-03 (0 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Packard Bell imedia S3840 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=f81de2b9-ff5a-4f92-af94-ac09f37653f4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-19-generic N/A linux-backports-modules-5.3.0-19-generic N/A linux-firmware1.183.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: imedia S3840 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd07/08/2011:svnPackardBell:pnimediaS3840:pvrP01-B1:rvnPackardBell:rnimediaS3840:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.
[Kernel-packages] [Bug 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)
Durning instalation this kernel i had this: arek@matebook:~/Pobrane$ sudo dpkg -i linux-image-unsigned-5.4.0-050400rc5-generic_5.4.0-050400rc5.201910271430_amd64.deb > log /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-050400rc5-generic W: Possible missing firmware /lib/firmware/amdgpu/navi12_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_mec2_wks.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_mec_wks.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_me_wks.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_pfp_wks.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_ce_wks.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/renoir_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi14_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/de
[Kernel-packages] [Bug 1850548] Re: Unable to install kdump tools: post install script returning fail
Hi Manoj, I think config changes work great - the whole solution is scripted, so it could be added in there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1850548 Title: Unable to install kdump tools: post install script returning fail Status in The Ubuntu-power-systems project: Triaged Status in makedumpfile package in Ubuntu: New Bug description: ---Problem Description--- Unable to install Kdump-tools. ---Steps to Reproduce--- Unable to Install Kdump-tool Debian package kdump-tools_1.6.3-2_ppc64el.deb Note: Unable to install the Kdump-tool. The problem comes when postinst script is run: root@pok1-qz1-sr1-rk005-s10:~/tar# uname -a Linux pok1-qz1-sr1-rk005-s10 4.15.0-1039-ibm-gt #41-Ubuntu SMP Wed Oct 2 10:52:25 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux root@pok1-qz1-sr1-rk005-s10:~/tar# dmesg | grep crash [0.00] Kernel command line: imgurl=http://192.168.0.2:80//install/netboot/ubuntu18.04/ppc64el/hostos-boot_bionic-4.15.0.1039-20191003-6f8d26a/rootimg.tar.gz XCAT=192.168.0.2:3001 XCATHTTPPORT=80 BOOTIF=08:94:EF:80:1B:54 console=tty0 console=hvc0,115200 default_hugepagesz=1G hugepagesz=1G hugepages=1 transparent_hugepage=never intel_iommu=on iommu=pt cloud-config-url=http://192.168.0.2/install/netboot/cloud-init/pok1-qz1-sr1-rk005-s10.txt ds=nocloud crashkernel=768M,low crashkernel=4G,high Error: = update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/write.1.gz because associated file /usr/share/man/man1/bsd-write.1.gz (of link group write) doesn't exist^M update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/from.1.gz because associated file /usr/share/man/man1/bsd-from.1.gz (of link group from) doesn't exist^M Setting up ifenslave (2.9ubuntu1) ...^M Setting up file (1:5.32-2ubuntu0.2) ...^M Setting up kdump-tools (1:1.6.3-2) ...^M ^M Creating config file /etc/default/kdump-tools with new version^M dpkg: error processing package kdump-tools (--configure):^M installed kdump-tools package post-installation script subprocess returned error exit status 1^M dpkg: dependency problems prevent configuration of linux-crashdump:^M linux-crashdump depends on kdump-tools; however:^M Package kdump-tools is not configured yet.^M ^M Detail Log: === root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic1_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic1_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic1:ppc64el (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic1:ppc64el (1:5.32-2ubuntu0.2) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic-mgc (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic-mgc (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i file_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack file_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking file (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up file (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i bsdmainutils_11.1.2ubuntu1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack bsdmainutils_11.1.2ubuntu1_ppc64el.deb ... Unpacking bsdmainutils (11.1.2ubuntu1) over (11.1.2ubuntu1) ... Setting up bsdmainutils (11.1.2ubuntu1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i makedumpfile_1.6.5-1ubuntu1~18.04.1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack makedumpfile_1.6.5-1ubuntu1~18.04.1_ppc64el.deb ... Unpacking makedumpfile (1:1.6.5-1ubuntu1~18.04.1) over (1:1.6.5-1ubuntu1~18.04.1) ... Setting up makedumpfile (1:1.6.5-1ubuntu1~18.04.1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i kexec-tools_2.0.16-1ubuntu1.1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack kexec-tools_2.0.16-1ubuntu1.1_ppc64el.deb ... Unpacking kexec-tools (1:2.0.16-1ubuntu1.1) over (1:2.0.16-1ubuntu1.1) ... Setting up kexec-tools (1:2.0.16-1ubuntu1.1) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based fr
[Kernel-packages] [Bug 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
And if we change use a different file: /root-tmp/var/log/ubuntu- advantage.log we get the following error too: [ 24.531406] SQUASHFS error: squashfs_read_data failed to read block 0x89c066e0b540 [ 24.531444] SQUASHFS error: Unable to read metadata cache entry [89c066e0b540] -- 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/1824407 Title: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Bionic: Confirmed Bug description: 1) Download focal subiquity pending image, or eoan release image 2) boot, and press ESC and edit boot command line (F6 in bios, e in UEFI) 3) After --- insert the following options break=top debug init=/bin/bash 4) Continue boot (Enter in BIOS, ctrl+x in UEFI) 5) in the initramfs execute: rm /scripts/casper-bottom/25adduser exit 6) you will be dropped into pivoted root filesystem, before systemd is execed as pid one 7) /run/initramfs/ will contain a debug log, showing how everything was mounted. Ie. cdrom mounted, squashfs losetup from there, then multilower overlay setup from them, moved to /root, and then pivot-root to /root done to finally end up as /. Underlying layers are moved into /cow for your convenience. 8) At this point modifying zero-byte length files, that exist in the lowest layer, but not the middle one, in certain ways, will results in them to be corrupted, after / is remounted. 9) Corruption examples (On both focal & eoan) cat /etc/.pwd.lock systemd-sysusers cat /etc/.pwd.lock mount -o remount / cat /etc/.pwd.lock overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000) cat: /etc/.pwd.lock: Input/output error (Only on eoan) cat /etc/machine-id systemd-machine-id-setup cat /etc/machine-id mount -o remount / cat /etc/machine-id overlayfs: invalid origin (etc/machine-id, ftype=8000, origin ftype=4000) cat: /etc/machine-id: Input/output error Lots of things break once machine-id and .pwd.lock are corrupted. I.e. unable to dhcp, connect to dbus, add/remove/change users or groups, etc. We were unable to recreate the issue outside of booting things with casper. Ie. statically on a regular host machine without pivot-root. But hopefully booting to a quite state with nothing running is sufficient to reproduce this. Instead of booting with `bebroken init=/bin/bash` you can boot with `bebroken systemd.mask=systemd-remount-fs.service` this will complete the boot, with /etc/machine-id & .pwd.lock modified, meaning that remount of / will cause IO errors on those files. Currently, we are shipping two hacks in casper's 25adduser script to "rm" the offending files, and create them again on the upper rw layer. They then survive remount without i/o errors. However, we'd rather not ship those hacks, and have kernel overlay fixed to work correctly with multi-lower-dir and not corrupt files upon remounting /. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824407/+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 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
OK, now managed to get a reproducer script to kick this bug even outside the early install context. Seems like we can force this bug by either remounting OR sync'ing and dropping caches. Attached is the reproducer script. Run as root, we hit the error: cat: /root-tmp/etc/.pwd.lock: Input/output error dmesg: [ 42.415432] overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000). ** Attachment added: "repro.sh" https://bugs.launchpad.net/ubuntu/bionic/+source/linux-hwe/+bug/1824407/+attachment/5302762/+files/repro.sh -- 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/1824407 Title: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Bionic: Confirmed Bug description: 1) Download focal subiquity pending image, or eoan release image 2) boot, and press ESC and edit boot command line (F6 in bios, e in UEFI) 3) After --- insert the following options break=top debug init=/bin/bash 4) Continue boot (Enter in BIOS, ctrl+x in UEFI) 5) in the initramfs execute: rm /scripts/casper-bottom/25adduser exit 6) you will be dropped into pivoted root filesystem, before systemd is execed as pid one 7) /run/initramfs/ will contain a debug log, showing how everything was mounted. Ie. cdrom mounted, squashfs losetup from there, then multilower overlay setup from them, moved to /root, and then pivot-root to /root done to finally end up as /. Underlying layers are moved into /cow for your convenience. 8) At this point modifying zero-byte length files, that exist in the lowest layer, but not the middle one, in certain ways, will results in them to be corrupted, after / is remounted. 9) Corruption examples (On both focal & eoan) cat /etc/.pwd.lock systemd-sysusers cat /etc/.pwd.lock mount -o remount / cat /etc/.pwd.lock overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000) cat: /etc/.pwd.lock: Input/output error (Only on eoan) cat /etc/machine-id systemd-machine-id-setup cat /etc/machine-id mount -o remount / cat /etc/machine-id overlayfs: invalid origin (etc/machine-id, ftype=8000, origin ftype=4000) cat: /etc/machine-id: Input/output error Lots of things break once machine-id and .pwd.lock are corrupted. I.e. unable to dhcp, connect to dbus, add/remove/change users or groups, etc. We were unable to recreate the issue outside of booting things with casper. Ie. statically on a regular host machine without pivot-root. But hopefully booting to a quite state with nothing running is sufficient to reproduce this. Instead of booting with `bebroken init=/bin/bash` you can boot with `bebroken systemd.mask=systemd-remount-fs.service` this will complete the boot, with /etc/machine-id & .pwd.lock modified, meaning that remount of / will cause IO errors on those files. Currently, we are shipping two hacks in casper's 25adduser script to "rm" the offending files, and create them again on the upper rw layer. They then survive remount without i/o errors. However, we'd rather not ship those hacks, and have kernel overlay fixed to work correctly with multi-lower-dir and not corrupt files upon remounting /. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824407/+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 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 - phase: Ready for Promote to Proposed - phase-changed: Monday, 04. November 2019 17:01 UTC + phase: Promote to Proposed + phase-changed: Monday, 04. November 2019 17:35 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -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-lrm 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+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 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -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: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Packaging phase-changed: Monday, 04. November 2019 15:20 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+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 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -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) => Andy Whitcroft (apw) -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -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-lrm 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Promote to Proposed phase-changed: Monday, 04. November 2019 17:35 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+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 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
I changed my motherboard and unfortunately can't test out any changes. -- 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/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+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 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 - phase: Holding before Promote to Proposed - phase-changed: Monday, 04. November 2019 14:16 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 04. November 2019 17:01 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:queued + promote-to-proposed: Pending -- ready for review variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -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-lrm 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Ready for Promote to Proposed phase-changed: Monday, 04. November 2019 17:01 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+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 1795659] Re: kernel panic using CIFS share in smb2_push_mandatory_locks()
Hi Guillaume, thanks for your report! Do you have more details on how
did you reproduce it? It was "organic", or can you trigger that using
some workload or test pattern? Also, based on the log output that you
pasted, seems it took about 30 hours to reproduce, correct? Let me know
if possible the topology of the cifs volumes in your system (how many
mount points you have, how many targets - and where are they -, etc).
Do you think you could run a debug kernel in order to collect more data?
I'll take a look in the code and see if I can instrument the cifs code
to narrow how this race might be happening, let me know if you are able
to test that.
Thanks,
Guilherme
--
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/1795659
Title:
kernel panic using CIFS share in smb2_push_mandatory_locks()
Status in linux package in Ubuntu:
Confirmed
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Invalid
Status in linux-azure source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Invalid
Status in linux source package in Cosmic:
Won't Fix
Status in linux-azure source package in Cosmic:
Invalid
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Invalid
Bug description:
[Impact]
* We got reports of a kernel crash in cifs module with the following
signature:
BUG: unable to handle kernel NULL pointer dereference at 0038
IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs]
PGD 0 P4D 0
RIP: 0010:smb2_push_mandatory_locks+0x10e/0x3b0 [cifs]
Call Trace:
cifs_oplock_break+0x12f/0x3d0 [cifs]
process_one_work+0x14d/0x410
worker_thread+0x4b/0x460
kthread+0x105/0x140
[...]
* Low-level analysis (decodecode script output and the objdump of the
function) revealed that we are crashing in a NULL ptr dereference when
trying to access "cfile->tlink"; below, a snippet of the objdump at
function smb2_push_mandatory_locks():
[...]
mov0x10(%r14),%r15 # %r15 = cifsFileInfo *cfile
mov0x18(%r14),%rbx # %rbx = cifsLockInfo *li = (fdlocks->locks)
lea0x18(%r14),%r12
mov0x90(%r15),%rax # %rax = struct tcon_link *tlink (cfile->tlink)
cmp%r12,%rbx
mov0x38(%rax),%rax # <--- TRAP [trying to get cifs_tcon *tl_tcon]
[...]
* After discussing the issue with CIFS maintainers (Steve French and
Pavel Shilovsky) they suggested commit b98749cac4a6 ("CIFS: keep
FileInfo handle live during oplock break")
[http://git.kernel.org/linus/b98749cac4a6] as a fix for multiple
reports of this kind of crash.
* The fix was sent to stable kernels and is present in Ubuntu kernels
5.0 and newer. We are requesting the SRU for this patch here in order
to fix the crashes, after reports of successful testing with the patch
(see below section) and since the patch is restricted to the cifs
module scope and accepted on linux stable.
* Alternatively the issue is known to be avoided when oplocks are
disabled using "cifs.enable_oplocks=N" module parameter.
[Test case]
* Unfortunately we cannot reproduce the issue. The patch proposed here was
validated by us with xfstests (instructions followed from
https://wiki.samba.org/index.php/Xfstesting-cifs) and fio. Also, we
have a user report of test validation using LISA
(https://github.com/LIS/LISAv2).
* Using xfstest with the exclusions proposed in the link above we
managed to get the same results as a non-patched kernel, i.e., the
same tests failed in both kernels, we didn't get worse results with
the patch. Fio also didn't show noticeable performance regression with
the patch.
[Regression potential]
* The patch was validated by the cifs filesystem maintainers (in fact
they suggested its inclusion in Ubuntu) and by the aforementioned
tests; also, the scope is restricted to cifs only so the likelihood of
regressions is considered low.
* Due to the nature of the code modification (add a new reference of a
file handler and manipulate it in different places), I consider that
if we have a regression it'll manifest as deadlock/blocked tasks, not
something more serious like crashes or data corruption.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795659/+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 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Holding before Promote to Proposed phase-changed: Monday, 04. November 2019 14:16 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,meta:building,signed:building + promote-to-proposed: Pending -- builds not complete in ppa lrm:queued variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -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-lrm 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: 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Holding before Promote to Proposed phase-changed: Monday, 04. November 2019 14:16 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+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 1842774] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-11-04 11:27 EDT--- *** Bug 181316 has been marked as a duplicate of this 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/1842774 Title: Enhanced Hardware Support - Finalize Naming Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in qemu source package in Bionic: In Progress Status in linux source package in Disco: Fix Released Status in qemu source package in Disco: In Progress Bug description: @SRU Team: For SRU template of Qemu please scroll down ... SRU Justification Kernel: = [Impact] * Add / activate support for IBM z15 and LinuxONE III systems [Fix] * a0e2251132995b962281aa80ab54a9288f9e0b6b a0e2251 "s390: add support for IBM z15 machines" [Test Case] * check and verify cpuinfo - regression testing is possible by Canonical/me * functional testing is currently only doable by IBM [Regression Potential] * There is regression potential with having new code in and the flags added/active * but the code changes are pretty straight forward, just add config, cases and defs * and are not used on existing systems, just on the new generation that is not yet out in the field [Other Info] * SRU of LP 1842916 merged with (this) LP 1842774 --- SRU Template for qemu as the impact/scope is different == [Impact] * Update naming of the new HW Generation * Now that the systems are released people might look for types matching the name and no one really knows "IBM 8561 GA1". * Help users to identify the cpu type by backporting the fix that sets the defined name. [Fix] * https://git.qemu.org/?p=qemu.git;a=commit;h=7505deca [Test Case] * qemu-system-s390x -cpu ? | grep gen15 s390 gen15a-base IBM 8561 GA1(static, migration-safe) s390 gen15a IBM 8561 GA1(migration-safe) s390 gen15b-base IBM 8562 GA1(static, migration-safe) s390 gen15b IBM 8562 GA1(migration-safe) * With the fix gen15a should be called "IBM z15 GA1" [Regression Potential] * The only thing changing (for qemu) are some texts e.g. when showing CPU types. The cpu type itself that is used in e.g. scripts / commands will not change. Therefore the regression risk of the qemu change is next to none. The only I can think of is people grepping for the old ID in text output, but that seems theoretical and not important. [Other Info] * For an SRU perspective this is "nice to have" we will only do this "along" other higher impact SRUs. __ This feature request will provide the final naming of the next machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1842774/+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 1842916] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1842774 *** https://bugs.launchpad.net/bugs/1842774 --- Comment From heinz-werner_se...@de.ibm.com 2019-11-04 11:27 EDT--- *** This bug has been marked as a duplicate of bug 181268 *** --- Comment From heinz-werner_se...@de.ibm.com 2019-11-04 11:28 EDT--- IBM Bugzilla status -> closed, Will be tracked with LP: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842774 -- 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/1842916 Title: [18.04 FEAT] Enhanced Hardware Support - Finalize Naming Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: This feature request will provide the final naming of the next machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1842916/+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 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Holding before Promote to Proposed phase-changed: Monday, 04. November 2019 14:16 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,meta:building,signed:building variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -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-lrm 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: 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Holding before Promote to Proposed phase-changed: Monday, 04. November 2019 14:16 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,meta:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+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 1795659] Re: kernel panic using CIFS share in smb2_push_mandatory_locks()
Hi, Unfortunately, the patch does not seem to solve the problem. Running Ubuntu 18.04 LTS with kernel 4.15.0-64, the crash still occurs with the same signature : Oct 14 08:00:01 uzorldsp01 kernel: [109699.415372] BUG: unable to handle kernel NULL pointer dereference at 0038 Oct 14 08:00:01 uzorldsp01 kernel: [109699.420042] IP: smb2_push_mandatory_locks+0x10d/0x3c0 [cifs] Oct 14 08:00:01 uzorldsp01 kernel: [109699.420042] PGD 0 P4D 0 Oct 14 08:00:01 uzorldsp01 kernel: [109699.420042] Oops: [#1] SMP PTI Oct 14 08:00:01 uzorldsp01 kernel: [109699.420042] Modules linked in: btrfs zstd_compress xor raid6_pq ufs qnx4 minix ntfs msdos jfs xfs dm_snapshot dm_bufio cmac arc4 md4 nls_utf8 cifs ccm fscache nf_conntr ack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack libcrc32c iptable_security sb_edac kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_rapl_perf input_leds serio_raw hyperv_fb hv_balloon joydev mac_hid sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 hid_generic hid_hyperv hv_util s hv_storvsc ptp hyperv_keyboard hv_netvsc hid scsi_transport_fc pps_core psmouse i2c_piix4 pata_acpi hv_vmbus floppy Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] CPU: 0 PID: 50766 Comm: kworker/0:0 Not tainted 4.15.0-64-generic #73-Ubuntu Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] Workqueue: cifsoplockd cifs_oplock_break [cifs] Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] RIP: 0010:smb2_push_mandatory_locks+0x10d/0x3c0 [cifs] Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] RSP: :ab360da2bdd8 EFLAGS: 00010246 Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] RAX: RBX: 9887646617d8 RCX: Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] RDX: 1000 RSI: RDI: 98876d006b80 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] RBP: ab360da2be28 R08: 988568596000 R09: 98876d006b80 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] R10: ab360da2bd98 R11: 988568596000 R12: 00aa Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] R13: 9887646617d8 R14: 9887646617c0 R15: 988764d7f200 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] FS: () GS:98876d60() knlGS: Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] CS: 0010 DS: ES: CR0: 80050033 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] CR2: 0038 CR3: 00046d80a003 CR4: 001606f0 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] Call Trace: Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] cifs_oplock_break+0x131/0x410 [cifs] Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] process_one_work+0x1de/0x420 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] worker_thread+0x32/0x410 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] kthread+0x121/0x140 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] ? process_one_work+0x420/0x420 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] ? kthread_create_worker_on_cpu+0x70/0x70 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] ret_from_fork+0x35/0x40 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] Code: c8 00 00 00 00 48 89 45 b0 49 39 c6 0f 84 e5 00 00 00 4d 89 fb 4d 8b 7e 10 49 8b 5e 18 4d 8d 6e 18 49 8b 87 90 00 00 00 4c 39 eb <48> 8b 40 38 48 89 4 5 d0 0f 84 ae 00 00 00 45 31 d2 4c 89 75 b8 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] RIP: smb2_push_mandatory_locks+0x10d/0x3c0 [cifs] RSP: ab360da2bdd8 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] CR2: 0038 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] ---[ end trace ee6628b4e2b5174b ]--- -- 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/1795659 Title: kernel panic using CIFS share in smb2_push_mandatory_locks() Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-azure source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux source package in Cosmic: Won't Fix Status in linux-azure source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Invalid Bug description: [Impact] * We got reports of a kernel crash in cifs module with the following signature: BUG: unable to handle kernel NULL pointer dereference at 0038 IP: smb2_push_mandatory_locks+0x10
[Kernel-packages] [Bug 1848746] Re: Refresh rate change requests to 40Hz are "adjusted" back to 60Hz
I made the switch to 19.10 and the problem is the same in the logs. There is a slight difference however, the screen doesn't flicker any more upon the change request. I suppose it now detects the adjusted modeline is the same as the current one, hence nothing to do. Here's some output extracted from dmesg (ISO date format) : 2019-11-04T16:39:13,088276+01:00 [drm:intel_dump_pipe_config [i915]] requested mode: 2019-11-04T16:39:13,088290+01:00 [drm:drm_mode_debug_printmodeline [drm]] Modeline "": 0 92450 1920 1968 2000 2080 1080 1083 1088 0x0 0x9 2019-11-04T16:39:13,088323+01:00 [drm:intel_dump_pipe_config [i915]] adjusted mode: 2019-11-04T16:39:13,088336+01:00 [drm:drm_mode_debug_printmodeline [drm]] Modeline "1920x1080": 60 140490 1920 1972 2007 2094 1080 1083 1089 1118 0x48 0x9 So it's the current 19.10 kernel (5.3.0-19-generic). I'm considering trying v5.4-rc5. I will report back once (and if) it's done. -- 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/1848746 Title: Refresh rate change requests to 40Hz are "adjusted" back to 60Hz Status in linux package in Ubuntu: Confirmed Bug description: Dear Launchpad readers, Changes to a 40Hz-based mode are adjusted back to a 60Hz display mode by KMS, as can be seen in the logs with the drm.debug=4 option : oct. 18 16:27:24 NovHak-P2 kernel: [drm:intel_dump_pipe_config [i915]] requested mode: oct. 18 16:27:24 NovHak-P2 kernel: [drm:drm_mode_debug_printmodeline [drm]] Modeline 0:"" 0 92450 1920 1968 2000 2080 1080 1083 1088 0x0 0x9 oct. 18 16:27:24 NovHak-P2 kernel: [drm:intel_dump_pipe_config [i915]] adjusted mode: oct. 18 16:27:24 NovHak-P2 kernel: [drm:drm_mode_debug_printmodeline [drm]] Modeline 0:"1920x1080" 60 140490 1920 1972 2007 2094 1080 1083 1089 1118 0x48 0x9 I managed to have 40Hz through EDID modification, swapping the two DTDs it contains, one being 60Hz, the other 40Hz, hence placing the 40Hz DTD first, but then it remains sticked to 40Hz and unable to switch to a 60Hz mode. I suppose the bug is i915-related rather than Xorg-related, since the modelines seem correctly sent for KMS. I can provide additional information if needed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.32.33 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: olivier 12097 F pulseaudio /dev/snd/controlC0: olivier 12097 F pulseaudio /dev/snd/controlC1: olivier 12097 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 18 16:43:01 2019 InstallationDate: Installed on 2019-09-22 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Notebook P17SM-A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=788f8a5e-9667-4cfb-abf4-bc76ebcb86bb ro quiet splash mtrr_spare_reg_nr=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-32-generic N/A linux-backports-modules-5.0.0-32-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: P17SM-A dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/27/2014:svnNotebook:pnP17SM-A:pvrNotApplicable:rvnNotebook:rnP17SM-A:rvrNotApplicable:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: Not Applicable dmi.product.name: P17SM-A dmi.product.sku: Not Applicable 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/1848746/+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 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
ok, this looks a bit more reasonable now ... $ ls -lh pi4-kernel_raspi2-5.3.0-1011.12_armhf.snap -rw-r--r-- 1 ogra ogra 211M Nov 4 17:05 pi4-kernel_raspi2-5.3.0-1011.12_armhf.snap so CONFIG_DEBUG_INFO=y should better be turned off by default for people building snaps from our trees ;) -- 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/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Confirmed Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+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 1850483] Re: eoan/linux-oracle: 5.3.0-1005.5 -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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1850483 Title: eoan/linux-oracle: 5.3.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850486 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 30. October 2019 20:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850483/+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 1850483] Re: eoan/linux-oracle: 5.3.0-1005.5 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850486 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 30. October 2019 20:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1850483 Title: eoan/linux-oracle: 5.3.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850486 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 30. October 2019 20:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850483/+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 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Holding before Promote to Proposed phase-changed: Monday, 04. November 2019 14:16 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait variant: debs -- 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -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-lrm 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: 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Holding before Promote to Proposed phase-changed: Monday, 04. November 2019 14:16 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+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 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
BTW, I can generate the mount move failure with the cut down script as follows (which follows the same mount patterns as the casper script) #!/bin/bash -x mkdir -p /cdrom mount -t iso9660 -o ro,noatime /dev/sr0 /cdrom sleep 1 mkdir -p /cow mount -t tmpfs -o 'rw,noatime,mode=755' tmpfs /cow sleep 1 mkdir -p /cow/upper mkdir -p /cow/work modprobe -q -b overlay sleep 1 modprobe -q -b loop sleep 1 dev=$(losetup -f) mkdir -p /filesystem.squashfs losetup $dev /cdrom/casper/filesystem.squashfs mount -t squashfs -o ro,noatime $dev /filesystem.squashfs sleep 1 dev=$(losetup -f) mkdir -p /installer.squashfs losetup $dev /cdrom/casper/installer.squashfs mount -t squashfs -o ro,noatime $dev /installer.squashfs sleep 1 mount -t overlay -o 'upperdir=/cow/upper,lowerdir=/installer.squashfs:/filesystem.squashfs,workdir=/cow/work' /cow /root mkdir -p /root/rofs mount -o move /filesystem.squashfs /root/rofs -- 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/1824407 Title: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Bionic: Confirmed Bug description: 1) Download focal subiquity pending image, or eoan release image 2) boot, and press ESC and edit boot command line (F6 in bios, e in UEFI) 3) After --- insert the following options break=top debug init=/bin/bash 4) Continue boot (Enter in BIOS, ctrl+x in UEFI) 5) in the initramfs execute: rm /scripts/casper-bottom/25adduser exit 6) you will be dropped into pivoted root filesystem, before systemd is execed as pid one 7) /run/initramfs/ will contain a debug log, showing how everything was mounted. Ie. cdrom mounted, squashfs losetup from there, then multilower overlay setup from them, moved to /root, and then pivot-root to /root done to finally end up as /. Underlying layers are moved into /cow for your convenience. 8) At this point modifying zero-byte length files, that exist in the lowest layer, but not the middle one, in certain ways, will results in them to be corrupted, after / is remounted. 9) Corruption examples (On both focal & eoan) cat /etc/.pwd.lock systemd-sysusers cat /etc/.pwd.lock mount -o remount / cat /etc/.pwd.lock overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000) cat: /etc/.pwd.lock: Input/output error (Only on eoan) cat /etc/machine-id systemd-machine-id-setup cat /etc/machine-id mount -o remount / cat /etc/machine-id overlayfs: invalid origin (etc/machine-id, ftype=8000, origin ftype=4000) cat: /etc/machine-id: Input/output error Lots of things break once machine-id and .pwd.lock are corrupted. I.e. unable to dhcp, connect to dbus, add/remove/change users or groups, etc. We were unable to recreate the issue outside of booting things with casper. Ie. statically on a regular host machine without pivot-root. But hopefully booting to a quite state with nothing running is sufficient to reproduce this. Instead of booting with `bebroken init=/bin/bash` you can boot with `bebroken systemd.mask=systemd-remount-fs.service` this will complete the boot, with /etc/machine-id & .pwd.lock modified, meaning that remount of / will cause IO errors on those files. Currently, we are shipping two hacks in casper's 25adduser script to "rm" the offending files, and create them again on the upper rw layer. They then survive remount without i/o errors. However, we'd rather not ship those hacks, and have kernel overlay fixed to work correctly with multi-lower-dir and not corrupt files upon remounting /. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824407/+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 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
Hi Dimitri,
while debugging this I found the following in setup_unionfs() in
scripts/casper:
# move the first mount; no head in busybox-initramfs
for d in $(mount -t squashfs | cut -d\ -f 3); do
mkdir -p "${rootmnt}/rofs"
if [ "${UNIONFS}" = unionfs-fuse ]; then
mount -o bind "${d}" "${rootmnt}/rofs"
else
mount -o move "${d}" "${rootmnt}/rofs"
fi
break
done
and looking at the debug /run/initramfs/initramfs.debug log for the
above stanza I see:
+ cut '-d ' -f 3
+ mount -t squashfs
+ mkdir -p /root/rofs
+ '[' overlay '=' unionfs-fuse ]
+ mount -o move /filesystem.squashfs /root/rofs
+ break
however, when I cannot reproduce this mount -o move operation by hand as
I get the mount error:
mount: /root/rofs: /filesystem.squashfs is not a block device.
It appears to me that the scripts/casper mount seems to silently ignore
this failure. Should the mount be a bind mount instead?
--
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/1824407
Title:
remount of multilower moved pivoted-root overlayfs root, results in
I/O errors on some modified files
Status in linux package in Ubuntu:
Confirmed
Status in linux-hwe package in Ubuntu:
Invalid
Status in linux-hwe source package in Bionic:
Confirmed
Bug description:
1) Download focal subiquity pending image, or eoan release image
2) boot, and press ESC and edit boot command line (F6 in bios, e in UEFI)
3) After --- insert the following options
break=top debug init=/bin/bash
4) Continue boot (Enter in BIOS, ctrl+x in UEFI)
5) in the initramfs execute:
rm /scripts/casper-bottom/25adduser
exit
6) you will be dropped into pivoted root filesystem, before systemd is execed
as pid one
7) /run/initramfs/ will contain a debug log, showing how everything was
mounted. Ie. cdrom mounted, squashfs losetup from there, then multilower
overlay setup from them, moved to /root, and then pivot-root to /root done to
finally end up as /. Underlying layers are moved into /cow for your convenience.
8) At this point modifying zero-byte length files, that exist in the
lowest layer, but not the middle one, in certain ways, will results in
them to be corrupted, after / is remounted.
9) Corruption examples
(On both focal & eoan)
cat /etc/.pwd.lock
systemd-sysusers
cat /etc/.pwd.lock
mount -o remount /
cat /etc/.pwd.lock
overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000)
cat: /etc/.pwd.lock: Input/output error
(Only on eoan)
cat /etc/machine-id
systemd-machine-id-setup
cat /etc/machine-id
mount -o remount /
cat /etc/machine-id
overlayfs: invalid origin (etc/machine-id, ftype=8000, origin ftype=4000)
cat: /etc/machine-id: Input/output error
Lots of things break once machine-id and .pwd.lock are corrupted. I.e.
unable to dhcp, connect to dbus, add/remove/change users or groups,
etc.
We were unable to recreate the issue outside of booting things with
casper. Ie. statically on a regular host machine without pivot-root.
But hopefully booting to a quite state with nothing running is
sufficient to reproduce this.
Instead of booting with `bebroken init=/bin/bash` you can boot with
`bebroken systemd.mask=systemd-remount-fs.service` this will complete
the boot, with /etc/machine-id & .pwd.lock modified, meaning that
remount of / will cause IO errors on those files.
Currently, we are shipping two hacks in casper's 25adduser script to
"rm" the offending files, and create them again on the upper rw layer.
They then survive remount without i/o errors. However, we'd rather not
ship those hacks, and have kernel overlay fixed to work correctly with
multi-lower-dir and not corrupt files upon remounting /.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824407/+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 1851202] Re: Need iw 5.3 in 18.04 Bionic
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => oem-priority ** Changed in: oem-priority Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851202 Title: Need iw 5.3 in 18.04 Bionic Status in OEM Priority Project: New Status in iw package in Ubuntu: Opinion Bug description: Current iw verion in Bionic is 4.14. Need iw 5.3 for better 802.11ax High-Efficiency Wireless support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1851202/+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 1850482] Re: eoan/linux-kvm: 5.3.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850486 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Wednesday, 30. October 2019 17:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1850482 Title: eoan/linux-kvm: 5.3.0-1006.6 -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: 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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850486 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Wednesday, 30. October 2019 17:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850482/+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 1850482] Re: eoan/linux-kvm: 5.3.0-1006.6 -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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1850482 Title: eoan/linux-kvm: 5.3.0-1006.6 -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: 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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850486 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Wednesday, 30. October 2019 17:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850482/+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 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
yup, seems this is (surprisingly) on by default ... $ grep DEBUG_INFO parts/kernel/build/.config CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_INFO_REDUCED is not set # CONFIG_DEBUG_INFO_SPLIT is not set CONFIG_DEBUG_INFO_DWARF4=y # CONFIG_DEBUG_INFO_BTF is not set i'll try a re-build and override that option from snapcraft.yaml ... -- 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/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Confirmed Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+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 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 - phase: Ready for Packaging - phase-changed: Friday, 01. November 2019 17:36 UTC + phase: Packaging + phase-changed: Monday, 04. November 2019 15:20 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded variant: debs -- 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -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: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Packaging phase-changed: Monday, 04. November 2019 15:20 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+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 1850477] Re: eoan/linux-aws: 5.3.0-1006.6 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1850477 Title: eoan/linux-aws: 5.3.0-1006.6 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850486 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 31. October 2019 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850477/+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 1850477] Re: eoan/linux-aws: 5.3.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850486 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 31. October 2019 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- 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/1850477 Title: eoan/linux-aws: 5.3.0-1006.6 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850486 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 31. October 2019 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850477/+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 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
** Summary changed: - bionic/linux-gcp-5.3: -proposed tracker + bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -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: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Packaging phase-changed: Monday, 04. November 2019 15:20 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+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 1847948] Re: Improve NVMe guest performance on Bionic QEMU
** Changed in: ubuntu-power-systems Status: Triaged => Fix Released ** Changed in: ubuntu-power-systems Status: Fix Released => 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/1847948 Title: Improve NVMe guest performance on Bionic QEMU Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in qemu source package in Bionic: Triaged Bug description: [Impact] * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO. But there can be platforms (like ppc64 spapr) that can and want to do exactly that. * Backport two patches from upstream (in since qemu 2.12 / Disco). * Due to that there is a tremendous speedup, especially useful with page size bigger than 4k. This avoids that being split into chunks and makes direct MMIO access possible for the guest. [Test Case] * On ppc64 pass through an NVME device to the guest and run I/O benchmarks, see below for Details how to set that up. Note: this needs the HWE kernel or another kernel fixup for [1]. Note: the test should also be done with the non-HWE kernel, the expectation there is that it would not show the perf benefits, but still work fine [Regression Potential] * Changes: a) if the host driver allows mapping of MSI-X data the entire BAR is mapped. This is only done if the kernel reports that capability [1]. This ensures that only on kernels able to do so qemu does expose the new behavior (safe against regression in that regard) b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local to just this HW and will not affect other HW. Generally the regressions that come to mind are slight changes in behavior (real HW vs the former emulation) that on some weird/old guests could cause trouble. But then it is limited to only PPC where only a small set of certified HW is really allowed. The mapping that might be added even on other platforms should not consume too much extra memory as long as it isn't used. Further since it depends on the kernel capability it isn't randomly issues on kernels where we expect it to fail. So while it is quite a change, it seems safe to me. [Other Info] * I know, one could as well call that a "feature", but it really is a performance bug fix more than anything else. Also the SRU policy allows exploitation/toleration of new HW especially for LTS releases. Therefore I think this is fine as SRU. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a32295c612c57990d17fb0f41e7134394b2f35f6 == Comment: #0 - Murilo Opsfelder Araujo - 2019-10-11 14:16:14 == ---Problem Description--- Back-port the following patches to Bionic QEMU to improve NVMe guest performance by more than 200%: ?vfio-pci: Allow mmap of MSIX BAR? https://git.qemu.org/?p=qemu.git;a=commit;h=ae0215b2bb56a9d5321a185dde133bfdd306a4c0 ?ppc/spapr, vfio: Turn off MSIX emulation for VFIO devices? https://git.qemu.org/?p=qemu.git;a=commit;h=fcad0d2121976df4b422b4007a5eb7fcaac01134 ---uname output--- na ---Additional Hardware Info--- 0030:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 172Xa/172Xb (rev 01) Machine Type = AC922 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install or setup a guest image and boot it. Once guest is running, passthrough the NVMe disk to the guest using the XML: host$ cat nvme-disk.xml host$ virsh attach-device nvme-disk.xml --live On the guest, run fio benchmarks: guest$ fio --direct=1 --rw=randrw --refill_buffers --norandommap --randrepeat=0 --ioengine=libaio --bs=4k --rwmixread=100 --iodepth=16 --runtime=60 --name=job1 --filename=/dev/nvme0n1 --numjobs=4 Results are similar with numjobs=4 and numjobs=64, respectively: READ: bw=385MiB/s (404MB/s), 78.0MiB/s-115MiB/s (81.8MB/s-120MB/s), io=11.3GiB (12.1GB), run=30001-30001msec READ: bw=382MiB/s (400MB/s), 2684KiB/s-12.6MiB/s (2749kB/s-13.2MB/s), io=11.2GiB (12.0GB), run=30001-30009msec With the two patches applied, performance improved significantly for numjobs=4 and numjobs=64 cases, respectively: READ: bw=1191MiB/s (1249MB/s), 285MiB/s-309MiB/s (299MB/s-324MB/s), io=34.9GiB (37.5GB), run=30001-30001msec READ: bw=4273MiB/s (4481MB/s), 49.7MiB/s-113MiB/s (52.1MB/s-119MB/s), io=125GiB (134GB), run=30001-30005msec Userspace tool common name: qemu Userspace rpm: qemu The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project web
[Kernel-packages] [Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) -- 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/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Confirmed Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+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 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
I am wondering if CONFIG_DEBUG_INFO is turned on? -- 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/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Confirmed Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+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 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Confirmed Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+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 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
i also tried using the "source-branch: raspi2" argument in the snapcraft.yaml instead of using teh master branch and the "source-tag:" option, but this results in the same big size ... additionally i'd like to remark that due to the transactional nature of UbuntuCore we need to keep the kernel three times on the device for the automatic rollback feature ... the current size would mean 2.1GB for compressed kernels alone. -- 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/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Confirmed Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+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 1849623] Re: linux-raspi2: rebase the Eoan kernel to the latest rpi-5.3.y branch (2a085c9b42ea)
@all, The new raspi2 kernel in -proposed contains these changes. Please test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1849623 Title: linux-raspi2: rebase the Eoan kernel to the latest rpi-5.3.y branch (2a085c9b42ea) Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Committed Bug description: [Impact] https://bugs.launchpad.net/bugs/1848790 https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703 Recently we had 2 bugs about the usb host on rpi4 with 4G ram, and I found the kernel in the github already had the fix for this issue, and besides this fix, it also had 106 more patches than our eoan kernel, those patches were merged during or after we prepared our eoan kernel, now let us pick those patches to our eoan too. [Fix] For the usb host issue, it adds a fix by setting the usb dma bounce buffer under 1G. [Test Case] some users and I alreaady tested the armhf and arm64 kernel on pi4 and pi3 boards, the usb host worked well and no other regressions introduced. [Regression Risk] Low, these patches are from the github which is the pi official kernel repository. And we already tested armhf and arm64 kernel on pi4/3 boards. The rpi kernel of https://github.com/raspberrypi/linux.git has been updated, for the branch of rpi-5.3.y (Eoan kernel base on this branch), there are 107 new patches merged, we also need to merge those patches to Eoan kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849623/+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 1850548] Re: Unable to install kdump tools: post install script returning fail
Would it be acceptable if we suggest a workaround of incorporating config file changes in the "diskless custom image" that you are using to boot? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1850548 Title: Unable to install kdump tools: post install script returning fail Status in The Ubuntu-power-systems project: Triaged Status in makedumpfile package in Ubuntu: New Bug description: ---Problem Description--- Unable to install Kdump-tools. ---Steps to Reproduce--- Unable to Install Kdump-tool Debian package kdump-tools_1.6.3-2_ppc64el.deb Note: Unable to install the Kdump-tool. The problem comes when postinst script is run: root@pok1-qz1-sr1-rk005-s10:~/tar# uname -a Linux pok1-qz1-sr1-rk005-s10 4.15.0-1039-ibm-gt #41-Ubuntu SMP Wed Oct 2 10:52:25 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux root@pok1-qz1-sr1-rk005-s10:~/tar# dmesg | grep crash [0.00] Kernel command line: imgurl=http://192.168.0.2:80//install/netboot/ubuntu18.04/ppc64el/hostos-boot_bionic-4.15.0.1039-20191003-6f8d26a/rootimg.tar.gz XCAT=192.168.0.2:3001 XCATHTTPPORT=80 BOOTIF=08:94:EF:80:1B:54 console=tty0 console=hvc0,115200 default_hugepagesz=1G hugepagesz=1G hugepages=1 transparent_hugepage=never intel_iommu=on iommu=pt cloud-config-url=http://192.168.0.2/install/netboot/cloud-init/pok1-qz1-sr1-rk005-s10.txt ds=nocloud crashkernel=768M,low crashkernel=4G,high Error: = update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/write.1.gz because associated file /usr/share/man/man1/bsd-write.1.gz (of link group write) doesn't exist^M update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode^M update-alternatives: warning: skip creation of /usr/share/man/man1/from.1.gz because associated file /usr/share/man/man1/bsd-from.1.gz (of link group from) doesn't exist^M Setting up ifenslave (2.9ubuntu1) ...^M Setting up file (1:5.32-2ubuntu0.2) ...^M Setting up kdump-tools (1:1.6.3-2) ...^M ^M Creating config file /etc/default/kdump-tools with new version^M dpkg: error processing package kdump-tools (--configure):^M installed kdump-tools package post-installation script subprocess returned error exit status 1^M dpkg: dependency problems prevent configuration of linux-crashdump:^M linux-crashdump depends on kdump-tools; however:^M Package kdump-tools is not configured yet.^M ^M Detail Log: === root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic1_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic1_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic1:ppc64el (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic1:ppc64el (1:5.32-2ubuntu0.2) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack libmagic-mgc_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking libmagic-mgc (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up libmagic-mgc (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i file_5.32-2ubuntu0.2_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack file_5.32-2ubuntu0.2_ppc64el.deb ... Unpacking file (1:5.32-2ubuntu0.2) over (1:5.32-2ubuntu0.2) ... Setting up file (1:5.32-2ubuntu0.2) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i bsdmainutils_11.1.2ubuntu1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack bsdmainutils_11.1.2ubuntu1_ppc64el.deb ... Unpacking bsdmainutils (11.1.2ubuntu1) over (11.1.2ubuntu1) ... Setting up bsdmainutils (11.1.2ubuntu1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i makedumpfile_1.6.5-1ubuntu1~18.04.1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack makedumpfile_1.6.5-1ubuntu1~18.04.1_ppc64el.deb ... Unpacking makedumpfile (1:1.6.5-1ubuntu1~18.04.1) over (1:1.6.5-1ubuntu1~18.04.1) ... Setting up makedumpfile (1:1.6.5-1ubuntu1~18.04.1) ... root@pok1-qz1-sr1-rk005-s10:~/tar# dpkg -i kexec-tools_2.0.16-1ubuntu1.1_ppc64el.deb (Reading database ... 65250 files and directories currently installed.) Preparing to unpack kexec-tools_2.0.16-1ubuntu1.1_ppc64el.deb ... Unpacking kexec-tools (1:2.0.16-1ubuntu1.1) over (1:2.0.16-1ubuntu1.1) ... Setting up kexec-tools (1:2.0.16-1ubuntu1.1) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program i
[Kernel-packages] [Bug 1850860] Re: 5.0.0-32.34 causes system instability with cephfs
Seeing the same in our farm. journalctl -k -p err -b --no-full --no-pager -- Logs begin at Sat 2019-11-02 16:23:20 PDT, end at Sun 2019-11-03 01:57:55 PDT. -- Nov 02 20:36:59 10.173.164.1-7e6e6109 kernel: cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info Nov 02 20:36:59 10.173.164.1-7e6e6109 kernel: cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info Nov 02 20:37:07 10.173.164.1-7e6e6109 kernel: cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info Nov 02 20:37:07 10.173.164.1-7e6e6109 kernel: cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info -- 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/1850860 Title: 5.0.0-32.34 causes system instability with cephfs Status in linux-signed package in Ubuntu: Confirmed Bug description: On Ubuntu 18.04 linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 According to https://www.mail-archive.com/ceph- us...@ceph.io/msg00940.html the same happens on Disco with this kernel version. Processes that read data from CephFS get stuck, the system becomes unstable. dmesg contains messages like this: [ 1510.703090] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.711590] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.720093] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.728592] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.737086] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.745587] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info [ 1510.754080] cache_from_obj: Wrong slab cache. inode_cache but object is from ceph_inode_info According to the discussion here: https://github.com/coreos/bugs/issues/2616 this is caused by a faulty patch. If that information is correct the problematic patch should be https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco/commit/?id=100a8eb40c492f2525cdae434c50d53ec7f5cc23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1850860/+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 1848790] Re: USB not working under arm64 on Pi4
@all There is a new kernel in -proposed that should fix these USB issues as well as the KVM support. There is still a known issue with audio as is explained in comment #14 above. Please test the -proposed kernel and let us know of any issues that you find. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1851243] 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 1851243 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/1851243 Title: overlayfs : broken access to r/w files Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Bug description: [Description] TBD [Test Case] TBD [Regression Potential] TBD [Other] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851243/+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
