[Kernel-packages] [Bug 1850033] Re: Touchpad not working
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc6/ -- 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/1850033 Title: Touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: I use Ubuntu (19.10 since last update) and ever since my touchpad does not work. 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 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nikiforos 2478 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 27 12:20:13 2019 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-01-18 (281 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: PEGATRON CORPORATION C15M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=83c3b3ed-edc2-40ec-b233-eb92e7099029 ro quiet splash i8042.nomux 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 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-26 (1 days ago) dmi.bios.date: 12/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 608 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: C15M dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: PEGATRON CORPORATION dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr608:bd12/17/2013:svnPEGATRONCORPORATION:pnC15M:pvr1.0:rvnPEGATRONCORPORATION:rnC15M:rvr1.0:cvnPEGATRONCORPORATION:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: C15M dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: PEGATRON CORPORATION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850860] Re: 5.0.0-32.34 causes system instability with cephfs
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850860 Title: 5.0.0-32.34 causes system instability with cephfs Status in linux 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/+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 1851230] Re: missing firmware files from oem image
** Also affects: linux-meta-oem (Ubuntu) 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/1851230 Title: missing firmware files from oem image Status in linux package in Ubuntu: Confirmed Status in linux-meta-oem package in Ubuntu: New 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 1851014] Re: WiFi (inbuilt) and Bluetooth not detected
bcmwl, 6.30.223.271+bdcom, 5.0.0-32-generic, x86_64: installed evdi, 5.1.26, 5.0.0-32-generic, x86_64: installed keucr, 0.0.1, 2.6.35-27-generic, x86_64: built oem-audio-hda-daily, 0.1: added -- 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 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** 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: 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 + prepare-package: Stalled -- package tag not yet published + prepare-package-lrm: Stalled -- package tag not yet published + prepare-package-meta: Stalled -- package tag not yet published + prepare-package-signed: Stalled -- package tag not yet published + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,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/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: Fix Committed Status in Kernel SRU Workflow prepare-package-lrm series: Fix Committed Status in Kernel SRU Workflow prepare-package-meta series: Fix Committed Status in Kernel SRU Workflow prepare-package-signed series: Fix Committed 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: Stalled -- package tag not yet published prepare-package-lrm: Stalled -- package tag not yet published prepare-package-meta: Stalled -- package tag not yet published prepare-package-signed: Stalled -- package tag not yet published promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait 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 1851347] [NEW] libmbim-proxy using 100% CPU on a Dell Edge Gateway 3002
Public bug reported: == Impact == A Dell Edge Gateway 3002 user reported that `top` reports around 100% CPU usage for the libmbim-proxy process. Seen in at least 40% of their devices at some point during the last 6 months. The CPU keeps high at ~100% days or weeks, but does return back to normal without a reboot. The LTE connectivity is seemingly still working as usual. The issue starts after an EPIPE error in the syslogs: 'cdc_mbim 1-3:1.12: nonzero urb status received: -EPIPE'. == Fix == 8fec9355a968 USB: cdc-wdm: ignore -EPIPE from GetEncapsulatedResponse This has been in mainline kernel since 4.14. == Testcase == Connect to the LTE network and see if libmbim-proxy uses 100% after some point. == Risk of Regression == Low, since 1. Already tested by original reporter and no issue found after more than a week (usually it fails twice in a week). 2. Ignoring -EPIPE is the default behavior after 4.14. ** Affects: hwe-next Importance: Undecided Assignee: Jesse Sung (wenchien) Status: Fix Released ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux (Ubuntu Xenial) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Tags: oem-priority originate-from-1839516 plano ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Jesse Sung (wenchien) ** Tags added: oem-priority originate-from-1839516 plano ** Changed in: hwe-next Status: New => Fix Released ** Changed in: hwe-next Assignee: (unassigned) => Jesse Sung (wenchien) -- 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/1851347 Title: libmbim-proxy using 100% CPU on a Dell Edge Gateway 3002 Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: == Impact == A Dell Edge Gateway 3002 user reported that `top` reports around 100% CPU usage for the libmbim-proxy process. Seen in at least 40% of their devices at some point during the last 6 months. The CPU keeps high at ~100% days or weeks, but does return back to normal without a reboot. The LTE connectivity is seemingly still working as usual. The issue starts after an EPIPE error in the syslogs: 'cdc_mbim 1-3:1.12: nonzero urb status received: -EPIPE'. == Fix == 8fec9355a968 USB: cdc-wdm: ignore -EPIPE from GetEncapsulatedResponse This has been in mainline kernel since 4.14. == Testcase == Connect to the LTE network and see if libmbim-proxy uses 100% after some point. == Risk of Regression == Low, since 1. Already tested by original reporter and no issue found after more than a week (usually it fails twice in a week). 2. Ignoring -EPIPE is the default behavior after 4.14. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1851347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => 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 -- 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 + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 05. November 2019 09:42 UTC reason: - prepare-package: Stalled -- package tag not yet published - prepare-package-lrm: Stalled -- package tag not yet published - prepare-package-meta: Stalled -- package tag not yet published - prepare-package-signed: Stalled -- package tag not yet published promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,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/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: 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 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: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 09:42 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait 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 1851351] [NEW] linux-oracle-5.3: -proposed tracker
Public bug reported: 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: 1850483 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1850483 kernel-sru-cycle-2019.10.21-6 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lrm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: (unassigned) => Canonical
[Kernel-packages] [Bug 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
Replaced read-only squashfs with read-only ext4 partitions and can't reproduce the error. -- 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 1851350] [NEW] bionic/linux-aws-5.3: -proposed tracker
Public bug reported: 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Ready for Packaging phase-changed: Tuesday, 05. November 2019 10:10 UTC reason: prepare-package: Pending -- version not specified variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1850477 kernel-sru-cycle-2019.10.21-6 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lrm Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: (unassigned) => Canonical Kernel Team (canonical
[Kernel-packages] [Bug 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
Replaced one of the two squashfs with read-only ext4 partitions and can't reproduce the error. Seems that we need 2 stacked squashfs file systems. -- 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 1851351] Re: bionic/linux-oracle-5.3: -proposed tracker
** Summary changed: - linux-oracle-5.3: -proposed tracker + bionic/linux-oracle-5.3: -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** 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: 1850483 + packages: + lrm: linux-restricted-modules-oracle-5.3 + main: linux-oracle-5.3 + meta: linux-meta-oracle-5.3 + signed: linux-signed-oracle-5.3 + phase: Ready for Packaging + phase-changed: Tuesday, 05. November 2019 10:11 UTC + reason: + prepare-package: Pending -- version not specified 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/1851351 Title: bionic/linux-oracle-5.3: -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: Confirmed Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Ready for Packaging phase-changed: Tuesday, 05. November 2019 10:11 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851350] Re: bionic/linux-aws-5.3: -proposed tracker
** Summary changed: - linux-aws-5.3: -proposed tracker + bionic/linux-aws-5.3: -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** 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: 1850477 + packages: + lrm: linux-restricted-modules-aws-5.3 + main: linux-aws-5.3 + meta: linux-meta-aws-5.3 + phase: Ready for Packaging + phase-changed: Tuesday, 05. November 2019 10:10 UTC + reason: + prepare-package: Pending -- version not specified 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/1851350 Title: bionic/linux-aws-5.3: -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: Confirmed Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Ready for Packaging phase-changed: Tuesday, 05. November 2019 10:10 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** 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: verification-testing: Ongoing -- testing in progress + trackers: + bionic/linux-aws-5.3: bug 1851350 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 trackers: bionic/linux-aws-5.3: bug 1851350 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 1850483] Re: eoan/linux-oracle: 5.3.0-1005.5 -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: 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 + trackers: + bionic/linux-oracle-5.3: bug 1851351 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 trackers: bionic/linux-oracle-5.3: bug 1851351 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 1851350] Re: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Summary changed: - bionic/linux-aws-5.3: -proposed tracker + bionic/linux-aws-5.3: 5.3.0-1006.6~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) -- 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/1851350 Title: bionic/linux-aws-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: 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 promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: Invalid 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Packaging phase-changed: Tuesday, 05. November 2019 10:25 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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816548] Re: [MIR] usbguard
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => oem-priority ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816548 Title: [MIR] usbguard Status in OEM Priority Project: New Status in usbguard package in Ubuntu: Incomplete Bug description: * Availability In sync with Debian, built on all architectures https://launchpad.net/ubuntu/+source/usbguard/0.7.4+ds-1 * Rationale We want to increase the security of USB devices, GNOME is working on this feature for next cycle and relying on the usbguard service https://wiki.gnome.org/Internships/2018/Projects/USB-Protection The binaries we want to promote are usbguard and libusbguard0. * Security No known security issues, but due to the nature of this package, a security review is probably needed. https://security-tracker.debian.org/tracker/source-package/usbguard https://people.canonical.com/~ubuntu-security/cve/pkg/usbguard.html * Quality assurance The security team is subscribed to the package https://bugs.launchpad.net/ubuntu/+source/usbguard https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=usbguard https://github.com/USBGuard/usbguard/issues The package build does 'make check' on the basic upstream tests, there is an upstream --enable-full-test-suite but some of those tests can't work in a buildd environment. There is no autopkgtest * Dependencies No universe binary dependencies * Standards compliance current 4.2 standards-version, debhelper compat 11, dh 7 style simple rules * Maintenance Upstream is active, the package is maintained in Debian and in sync for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1816548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851350] Re: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 - phase: Ready for Packaging - phase-changed: Tuesday, 05. November 2019 10:10 UTC + phase: Packaging + phase-changed: Tuesday, 05. November 2019 10:25 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 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/1851350 Title: bionic/linux-aws-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: 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 promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: Invalid 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Packaging phase-changed: Tuesday, 05. November 2019 10:25 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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Hi Bin Li, Thanks for the updates. Could you specify a target date for the bug fix? Thank you! -- 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 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: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 09:42 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/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: 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 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: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 09:42 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/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 1849027] Re: xenial/linux-azure: 4.15.0-1062.67 -proposed tracker
4.15.0-1062.67 - azure Regression test CMPL, RTB. Issue to note in x86_64 (azure): ubuntu_kernel_selftests - cpu-hotplug (bug 1831543) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) port80 (bug 1748105) vmx (bug 1821394) vmx_apicv_test (bug 1827866) failed on Standard_D16s_v3, Standard_D2_v3, Standard_D2s_v3, Standard_E2s_v3, Standard_F2s_v2, Standard_F32s_v2 ubuntu_ltp_syscalls - statx05 (bug 1798524) Skipped / blacklisted: * libhugetlbfs * ubuntu_seccomp ** 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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1849027 Title: xenial/linux-azure: 4.15.0-1062.67 -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 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: 1849855 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 22. October 2019 15:49 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: trusty/linux-azure: bug 1849026 xenial/linux-azure-edge: bug 1849025 xenial/linux-azure/azure-kernel: bug 1849024 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849027] Re: xenial/linux-azure: 4.15.0-1062.67 -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: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 22. October 2019 15:49 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: trusty/linux-azure: bug 1849026 xenial/linux-azure-edge: bug 1849025 xenial/linux-azure/azure-kernel: bug 1849024 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/1849027 Title: xenial/linux-azure: 4.15.0-1062.67 -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 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: 1849855 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 22. October 2019 15:49 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: trusty/linux-azure: bug 1849026 xenial/linux-azure-edge: bug 1849025 xenial/linux-azure/azure-kernel: bug 1849024 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
It's highly unlikely this commit caused the issue. -- 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 1851014] Re: WiFi (inbuilt) and Bluetooth not detected
Please try `sudo dkms install -m bcmwl -k 5.3.0-19-generic` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1849665] Re: zfs diff: Unable to determine path or stats for object
Eoan verification
First, reproducing the bug:
root@nsn7:~# mkdir /zfs-test
root@nsn7:~# cd /zfs-test/
root@nsn7:/zfs-test# truncate -s 10G file.img
root@nsn7:/zfs-test# zpool create -o ashift=12 -O acltype=posixacl -O
compression=lz4 -O xattr=sa -O normalization=formD -O dnodesize=auto tank
$(pwd)/file.img
root@nsn7:/zfs-test# zfs create tank/d1 -o encryption=on -o keyformat=passphrase
Enter passphrase:
Re-enter passphrase:
root@nsn7:/zfs-test# 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,425336 s, 98,6 MB/s
root@nsn7:/zfs-test# zfs snapshot tank/d1@s1
root@nsn7:/zfs-test# 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,260445 s, 161 MB/s
root@nsn7:/zfs-test# zfs diff tank/d1@s1 tank/d1
Unable to determine path or stats for object 3 in tank/d1@s1: File exists
root@nsn7:/zfs-test# uname -a
Linux nsn7 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
Now installing the updated kernel and rebooting into it.
--
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 list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.n
[Kernel-packages] [Bug 1851014] Re: WiFi (inbuilt) and Bluetooth not detected
sudo dkms install -m bcmwl -k 5.3.0-19-generic [sudo] password for alan: Error! Invalid number of arguments passed. Usage: add / or add -m / or add -m -v Assuming this works, why is it ok in a previous kernel but needs this installing with the new kernel? -- 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 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 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: 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: Holding before Promote to Proposed - phase-changed: Tuesday, 05. November 2019 09:42 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 05. November 2019 12:06 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait + 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/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: 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 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: 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 Promote to Proposed phase-changed: Tuesday, 05. November 2019 12:06 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/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 1849665] Re: zfs diff: Unable to determine path or stats for object
Hm, at first glance this didn't work with the new kernel and zfsutils-
linux package:
root@nsn7:/zfs-test# zfs diff tank/d1@s1 tank/d1
Unable to determine path or stats for object 3 in tank/d1@s1: File exists
root@nsn7:/zfs-test# uname -a
Linux nsn7 5.3.0-21-generic #22-Ubuntu SMP Tue Oct 29 22:55:51 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
root@nsn7:/zfs-test# dpkg -l|grep linux-image
ii linux-image-5.3.0-18-generic 5.3.0-18.19+1
amd64Signed kernel image generic
ii linux-image-5.3.0-19-generic 5.3.0-19.20
amd64Signed kernel image generic
ii linux-image-5.3.0-21-generic 5.3.0-21.22
amd64Signed kernel image generic
ii linux-image-generic5.3.0.21.24
amd64Generic Linux kernel image
root@nsn7:/zfs-test#
This was with the existing pool and dataset from the previous test.
Let me try restarting it from scratch:
root@nsn7:/zfs-test# cd
root@nsn7:~# zpool destroy tank
root@nsn7:~# rm -rf /zfs-test/
root@nsn7:~# mkdir /zfs-test
root@nsn7:~# cd /zfs-test
root@nsn7:/zfs-test# truncate -s 10G file.img
root@nsn7:/zfs-test# zpool create -o ashift=12 -O acltype=posixacl -O
compression=lz4 -O xattr=sa -O normalization=formD -O dnodesize=auto tank
$(pwd)/file.img
root@nsn7:/zfs-test# zfs create tank/d1 -o encryption=on -o keyformat=passphrase
Enter passphrase:
Re-enter passphrase:
root@nsn7:/zfs-test# 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,39306 s, 107 MB/s
root@nsn7:/zfs-test# zfs snapshot tank/d1@s1
root@nsn7:/zfs-test# 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,265228 s, 158 MB/s
root@nsn7:/zfs-test# zfs diff tank/d1@s1 tank/d1
Unable to determine path or stats for object 3 in tank/d1@s1: File exists
root@nsn7:/zfs-test# uname -a
Linux nsn7 5.3.0-21-generic #22-Ubuntu SMP Tue Oct 29 22:55:51 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
root@nsn7:/zfs-test# apt-cache policy linux-image-5.3.0-21-generic
zfsutils-linux
linux-image-5.3.0-21-generic:
Installed: 5.3.0-21.22
Candidate: 5.3.0-21.22
Version table:
*** 5.3.0-21.22 500
500 http://br.archive.ubuntu.com/ubuntu eoan-proposed/main amd64
Packages
100 /var/lib/dpkg/status
zfsutils-linux:
Installed: 0.8.1-1ubuntu14.1
Candidate: 0.8.1-1ubuntu14.1
Version table:
*** 0.8.1-1ubuntu14.1 500
500 http://br.archive.ubuntu.com/ubuntu eoan-proposed/main amd64
Packages
100 /var/lib/dpkg/status
0.8.1-1ubuntu14 500
500 http://br.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
Same thing.
--
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-l
[Kernel-packages] [Bug 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64)
For armhf (arm32) kernel, only CORTEX-A7 and CORTEXT-A15 support KVM, for Pi's cpu, they don't support KVM for armhf kernel. ** Summary changed: - CONFIG_KVM is disabled for linux-raspi2 (aarch64 and armhf) + CONFIG_KVM is disabled for linux-raspi2 (aarch64) -- 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/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64) Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Committed Bug description: In contrast to the Linux kernel for x86_64, the CONFIG_KVM option is disabled for the "linux-raspi2" kernel (version 4.15.0-1016-raspi2 aarch64) on Ubuntu 18.04. This prevents running QEMU with the -enable-kvm option to use hardware virtualization capabilities of the CPU. I have recompiled the kernel with CONFIG_KVM set and could successfully run QEMU with -enable-kvm on my Raspberry Pi 3 B+ afterwards. In my opinion, there is no reason for not activating CONFIG_KVM in the official raspi2 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1850033] Re: Touchpad not working
Sorry, what exactly do I need to do after I follow this link?? Στις Τρί, 5 Νοε 2019, 10:15 ο χρήστης Kai-Heng Feng < kai.heng.f...@canonical.com> έγραψε: > Please test latest mainline kernel: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc6/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1850033 > > Title: > Touchpad not working > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I use Ubuntu (19.10 since last update) and ever since my touchpad does > not work. > > 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 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: nikiforos 2478 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Oct 27 12:20:13 2019 > HibernationDevice: RESUME=none > InstallationDate: Installed on 2019-01-18 (281 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > MachineType: PEGATRON CORPORATION C15M > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic > root=UUID=83c3b3ed-edc2-40ec-b233-eb92e7099029 ro quiet splash i8042.nomux > 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 > SourcePackage: linux > UpgradeStatus: Upgraded to eoan on 2019-10-26 (1 days ago) > dmi.bios.date: 12/17/2013 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 608 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: C15M > dmi.board.vendor: PEGATRON CORPORATION > dmi.board.version: 1.0 > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: PEGATRON CORPORATION > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr608:bd12/17/2013:svnPEGATRONCORPORATION:pnC15M:pvr1.0:rvnPEGATRONCORPORATION:rnC15M:rvr1.0:cvnPEGATRONCORPORATION:ct3:cvr1.0: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: C15M > dmi.product.sku: To be filled by O.E.M. > dmi.product.version: 1.0 > dmi.sys.vendor: PEGATRON CORPORATION > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850033/+subscriptions > -- 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/1850033 Title: Touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: I use Ubuntu (19.10 since last update) and ever since my touchpad does not work. 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 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nikiforos 2478 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 27 12:20:13 2019 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-01-18 (281 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: PEGATRON CORPORATION C15M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=83c3b3ed-edc2-40ec-b233-eb92e7099029 ro quiet splash i8042.nomux 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 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-26 (1 days ago) dmi.bios.date: 12/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 608 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: C15M dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: PEGATRON CORPORATION dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr608:bd12/17/2013:svnPEGATRONCORPORATION:pnC15M:pvr1.0:rvnPEGATRONCORPORATION:rnC15M:rvr1.0:cvnPEGATRONCORPORATION:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: C15M dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: PEGATRON CORPORATION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.ne
[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
I can confirm this is working on Ubuntu 19.10. Are we going to see the fix upstream at some point? -- 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/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: In Progress Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835540] Re: Confusing "modinfo: ERROR: missing module or filename." during normal operation
According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943569, this is fixed in debian dkms=2.7.1-5. ** Bug watch added: Debian Bug tracker #943569 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943569 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1835540 Title: Confusing "modinfo: ERROR: missing module or filename." during normal operation Status in dkms package in Ubuntu: Confirmed Bug description: I just installed a new kernel, and when I did so my Nvidia kernel modules were handled through DKMS, as you would expect. However, during what I believe is normal operation, I saw the following stanza (repeated for several nvidia .ko files): nvidia.ko: Running module version sanity check. modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.0.0-20-generic/updates/dkms/ The "ERROR" in here gave me pause, but I _believe_ that's an expected message for a new kernel. It would make for a less troubling user experience if we didn't print out "ERROR" in all caps when there is no error at all. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: dkms 2.7.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Jul 5 09:52:41 2019 InstallationDate: Installed on 2019-05-07 (58 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: Upgraded to eoan on 2019-05-08 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1835540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838245] Re: dkms script is missing function find_module
I'm still seeing this on Eoan, which has dkms 2.7.1-4ubuntu2 - the
symptom is that virtualbox-dkms does not correctly build and install its
kernel modules with the message `modinfo: ERROR: missing module or
filename.`
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1838245
Title:
dkms script is missing function find_module
Status in DKMS:
Fix Released
Status in dkms package in Ubuntu:
Fix Released
Status in dkms source package in Bionic:
Fix Released
Bug description:
update for SRU process:
[Impact]
1. dkms script is missing function find_module
2. priority of OBSOLETE_BY should higher than "force". #89
https://github.com/dell/dkms/issues/89
[Test case]
install the dkms which already patched (also can be found in my ppa[1])
1. install a dkms which for a kernel module system already installed.
e.g. ath10k of my testing ppa : [1]
1.1. the dkms can be installed well.
2. install a dkms which has OBSOLETE_BY and FORCE
e.g.ath10k of my testing ppa : [1] (source code in [2])
- the target dkms defined OBSOLETE_BY and FORCE
- user install dkms on a system which installed kernel version less than
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
- the dkms can be installed well.
[Regression potential]
medium as it touched the version sanity. This change correct the code logic
and land one more change from upstream as well.
The logic has been verified by #5 and me.
Building a kernel module using dkms in Linux Mint 19.1 shows the following
error:
Running module version sanity check.
/usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden
modinfo: ERROR: missing module or filename.
Checking the file the function is indeed missing and another user
confirmed, that it was removed at some point:
https://github.com/linuxmint/linuxmint/issues/142
Possible solution: Readd
find_module()
{
# tree = $1
# module = $2
find "$1" -name "$2$module_uncompressed_suffix" -o -name
"$2$module_suffix" -type f
return $?
}
as found in https://github.com/dell/dkms/blob/master/dkms
To manage notifications about this bug go to:
https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1850033] Re: Touchpad not working
Sorry I just noticed the instructions. Thank you. Στις Τρί, 5 Νοε 2019, 10:15 ο χρήστης Kai-Heng Feng < kai.heng.f...@canonical.com> έγραψε: > Please test latest mainline kernel: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc6/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1850033 > > Title: > Touchpad not working > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I use Ubuntu (19.10 since last update) and ever since my touchpad does > not work. > > 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 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: nikiforos 2478 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Oct 27 12:20:13 2019 > HibernationDevice: RESUME=none > InstallationDate: Installed on 2019-01-18 (281 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > MachineType: PEGATRON CORPORATION C15M > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic > root=UUID=83c3b3ed-edc2-40ec-b233-eb92e7099029 ro quiet splash i8042.nomux > 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 > SourcePackage: linux > UpgradeStatus: Upgraded to eoan on 2019-10-26 (1 days ago) > dmi.bios.date: 12/17/2013 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 608 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: C15M > dmi.board.vendor: PEGATRON CORPORATION > dmi.board.version: 1.0 > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: PEGATRON CORPORATION > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr608:bd12/17/2013:svnPEGATRONCORPORATION:pnC15M:pvr1.0:rvnPEGATRONCORPORATION:rnC15M:rvr1.0:cvnPEGATRONCORPORATION:ct3:cvr1.0: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: C15M > dmi.product.sku: To be filled by O.E.M. > dmi.product.version: 1.0 > dmi.sys.vendor: PEGATRON CORPORATION > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850033/+subscriptions > -- 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/1850033 Title: Touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: I use Ubuntu (19.10 since last update) and ever since my touchpad does not work. 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 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nikiforos 2478 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 27 12:20:13 2019 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-01-18 (281 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: PEGATRON CORPORATION C15M ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=83c3b3ed-edc2-40ec-b233-eb92e7099029 ro quiet splash i8042.nomux 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 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-26 (1 days ago) dmi.bios.date: 12/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 608 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: C15M dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: PEGATRON CORPORATION dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr608:bd12/17/2013:svnPEGATRONCORPORATION:pnC15M:pvr1.0:rvnPEGATRONCORPORATION:rnC15M:rvr1.0:cvnPEGATRONCORPORATION:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: C15M dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: PEGATRON CORPORATION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1849665] Re: zfs diff: Unable to determine path or stats for object
So this is a 2-phase fix. The dkms package is updated, then we test
this, then this gets sync'd into the kernel. I'm testing it right now,
let me sanity check the zfs-dkms part first and get that updated as step
#1.
--
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 list: https://launchpad.net/~kernel-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 agree! It is way more likely to be a commit in the ideapad driver, that one "55167453111d3a1e600e29ba6c8e63906bb4821b" or that one "17f1bf38c8821ce851d95708a1f1e226d17ec2c5". -- 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 1849665] Re: zfs diff: Unable to determine path or stats for object
Installed the new zfsutils + zfs dkms to sanity check the kernel driver
part of the fix:
dmesg | grep ZFS
[ 22.420188] ZFS: Loaded module v0.8.1-1ubuntu14.1, ZFS pool version 5000,
ZFS filesystem version 5
And now the test:
root@eoan-amd64-uefi:~# mkdir /zfs-test
root@eoan-amd64-uefi:~# cd /zfs-test
root@eoan-amd64-uefi:/zfs-test# truncate -s 10G file.img
root@eoan-amd64-uefi:/zfs-test# zpool create -o ashift=12 -O acltype=posixacl
-O compression=lz4 -O xattr=sa -O normalization=formD -O dnodesize=auto tank
$(pwd)/file.img
root@eoan-amd64-uefi:/zfs-test# zfs create tank/d1 -o encryption=on -o
keyformat=passphrase
Enter passphrase:
Re-enter passphrase:
root@eoan-amd64-uefi:/zfs-test# 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.319657 s, 131 MB/s
root@eoan-amd64-uefi:/zfs-test# zfs snapshot tank/d1@s1
root@eoan-amd64-uefi:/zfs-test# 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.312195 s, 134 MB/s
root@eoan-amd64-uefi:/zfs-test# zfs diff tank/d1@s1 tank/d1
M /tank/d1/
+ /tank/d1/somedata2.bin
The zfsutils + dkms package has the fix. Once this lands we can then
sync this into the next kernel release for the complete fix.
** Tags added: verification-done-eoan
--
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
[Kernel-packages] [Bug 1838245] Re: dkms script is missing function find_module
For me, the fix is to change line 812 of /usr/sbin/dkms from:
[ -z $kernels_module ] || return 0
to
[ -z $kernels_module ] && return 0
This was fixed upstream here:
https://github.com/dell/dkms/commit/b95779938805aca8e98d57492b18dee07d35d285
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1838245
Title:
dkms script is missing function find_module
Status in DKMS:
Fix Released
Status in dkms package in Ubuntu:
Fix Released
Status in dkms source package in Bionic:
Fix Released
Bug description:
update for SRU process:
[Impact]
1. dkms script is missing function find_module
2. priority of OBSOLETE_BY should higher than "force". #89
https://github.com/dell/dkms/issues/89
[Test case]
install the dkms which already patched (also can be found in my ppa[1])
1. install a dkms which for a kernel module system already installed.
e.g. ath10k of my testing ppa : [1]
1.1. the dkms can be installed well.
2. install a dkms which has OBSOLETE_BY and FORCE
e.g.ath10k of my testing ppa : [1] (source code in [2])
- the target dkms defined OBSOLETE_BY and FORCE
- user install dkms on a system which installed kernel version less than
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
- the dkms can be installed well.
[Regression potential]
medium as it touched the version sanity. This change correct the code logic
and land one more change from upstream as well.
The logic has been verified by #5 and me.
Building a kernel module using dkms in Linux Mint 19.1 shows the following
error:
Running module version sanity check.
/usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden
modinfo: ERROR: missing module or filename.
Checking the file the function is indeed missing and another user
confirmed, that it was removed at some point:
https://github.com/linuxmint/linuxmint/issues/142
Possible solution: Readd
find_module()
{
# tree = $1
# module = $2
find "$1" -name "$2$module_uncompressed_suffix" -o -name
"$2$module_suffix" -type f
return $?
}
as found in https://github.com/dell/dkms/blob/master/dkms
To manage notifications about this bug go to:
https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
Oh no! I just noticed some flickering in the monitor during work. Is there a way to understand what could be going 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/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: In Progress Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
This by the way, was literally just a couple of flickers for no apparent reason during an hours work under this kernel. -- 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/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) Status in Linux: In Progress Status in linux package in Ubuntu: Confirmed Bug description: A brand new Dell XPS 13 9380 preinstalled with Ubuntu 18.04 flickers to the point of being totally unusable. I have upgraded since to 18.10 and 19.04 with no changes. I have tried several combinations of the i915 parameters fastboot, enable_rc6 and enable_fbc to no avail. Examples of flickering are here: https://photos.app.goo.gl/1PkL2HrjMBP41aML9 https://photos.app.goo.gl/CMzmMwrCPH5wh8aw6 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1430 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X31 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-13 (10 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9380 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1035-oem root=UUID=252898e9-6e96-4705-a709-2db930b7c4c7 ro quiet splash i915.fastboot=1 i915.enable_rc6=0 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1035.40-oem 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-1035-oem N/A linux-backports-modules-4.15.0-1035-oem N/A linux-firmware 1.178 Tags: disco Uname: Linux 4.15.0-1035-oem x86_64 UpgradeStatus: Upgraded to disco on 2019-04-24 (0 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/14/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: 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 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 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/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 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
For eoan, I inherited "DEBUG_INFO=y" from disco raspi2 kernel. -- 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 -- boot-testing-requested: true 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 Promote to Proposed - phase-changed: Tuesday, 05. November 2019 12:06 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 05. November 2019 13:55 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/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: 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 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 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/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 1850574] Re: disco/linux: 5.0.0-34.36 -proposed tracker
Marked as incomplete for possible seccomp test regression (bug 1849844) is going to be fixed in the next release, moving the tracker along. ** 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/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: 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 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 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 1850574] Re: disco/linux: 5.0.0-34.36 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Incomplete => 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 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 -- 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: 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 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 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 1851382] [NEW] Missing modules for cryptography and NFSv4
Public bug reported: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: crypto nfsv4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux-meta package in Ubuntu: New Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] Re: Missing modules for cryptography and NFSv4
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: New Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker
** Summary changed: - bionic/linux-oracle-5.3: -proposed tracker + bionic/linux-oracle-5.3: 5.3.0-1005.5~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/1851351 Title: bionic/linux-oracle-5.3: 5.3.0-1005.5~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: Invalid 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: Invalid 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Packaging phase-changed: Tuesday, 05. November 2019 14:55 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/1851351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 - phase: Ready for Packaging - phase-changed: Tuesday, 05. November 2019 10:11 UTC + phase: Packaging + phase-changed: Tuesday, 05. November 2019 14:55 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/1851351 Title: bionic/linux-oracle-5.3: 5.3.0-1005.5~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: Invalid 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: Invalid 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Packaging phase-changed: Tuesday, 05. November 2019 14:55 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/1851351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: In Progress => Fix Committed ** 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: Stalled -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed 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: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 -- package copied to Proposed 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 1684789] Re: trunc-file.sh.btrfs from ubuntu_ecryptfs test-suite failed on T-LTS
** Tags added: sru-20191021 -- 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/1684789 Title: trunc-file.sh.btrfs from ubuntu_ecryptfs test-suite failed on T-LTS Status in eCryptfs: New Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This test has failed on both amd64, i386 and arm64 T-LTS kernel For this test, it complains about the: size should be > 0 04/15 05:13:22 DEBUG| utils:0116| Running 'apt-get install --yes --force-yes build-essential libglib2.0-dev intltool keyutils libkeyutils-dev libpam0g-dev libnss3-dev libtool acl xfsprogs btrfs-tools libattr1-dev gcc-multilib' 04/15 05:13:22 DEBUG| utils:0153| [stdout] Reading package lists... 04/15 05:13:22 DEBUG| utils:0153| [stdout] Building dependency tree... 04/15 05:13:22 DEBUG| utils:0153| [stdout] Reading state information... 04/15 05:13:22 DEBUG| utils:0153| [stdout] acl is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] build-essential is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] gcc-multilib is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] intltool is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] keyutils is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libattr1-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libkeyutils-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libtool is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] xfsprogs is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] btrfs-tools is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libglib2.0-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libnss3-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libpam0g-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 04/15 05:13:22 DEBUG| utils:0116| Running 'which gcc' 04/15 05:13:22 DEBUG| utils:0153| [stdout] /usr/bin/gcc 04/15 05:13:22 DEBUG| utils:0116| Running 'tests/run_one.sh -K -t trunc-file.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs' 04/15 05:13:34 ERROR| utils:0153| [stderr] size should be > 0 04/15 05:13:35 DEBUG| utils:0153| [stdout] trunc-file FAIL 04/15 05:13:35 DEBUG| utils:0153| [stdout] 04/15 05:13:35 DEBUG| utils:0153| [stdout] Test Summary: 04/15 05:13:35 DEBUG| utils:0153| [stdout] 0 passed 04/15 05:13:35 DEBUG| utils:0153| [stdout] 1 failed 04/15 05:13:35 ERROR| test:0414| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_ecryptfs/ubuntu_ecryptfs.py", line 45, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: tests/run_one.sh -K -t trunc-file.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs Exit status: 1 Duration: 12.9071211815 stdout: trunc-file FAIL Test Summary: 0 passed 1 failed stderr: size should be > 0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-74-generic 4.4.0-74.95~14.04.1 ProcVersionSignature: User Name 4.4.0-74.95~14.04.1-generic 4.4.59 Uname: Linux 4.4.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Thu Apr 20 13:58:58 2017 SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1684789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] 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 1851382 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/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Incomplete Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 Status: In Progress => Fix Committed ** 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed lrm:building,signed:depwait variant: debs ** 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed lrm:building,signed:depwait + promote-to-proposed: Ongoing -- package copied to Proposed 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/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: 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 Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait 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 1837525] Comment bridged from LTC Bugzilla
--- Comment From andreas.kreb...@de.ibm.com 2019-11-05 10:42 EDT--- (In reply to comment #16) > Rebuilding eoan gcc-9.2.1 and comparing test results between -march=zEC12 & > -march=z13 -mtune=z15 > > There appear to be (a) improved test results (FAIL->PASS) (b) not supported > tests anymore (PASS->missing) (c) regressed tests (PASS->FAIL). This needs > investigating. I will publish raw logs (massaged to reduce non-reproducible > directory names) shortly. Here are some highlights. ... I've applied a few patches fixing these issues to GCC mainline and GCC 9 branch: https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00282.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/1837525 Title: [20.04 FEAT] Set Architecture Level (ALS) to z13 Status in Ubuntu on IBM z Systems: Fix Committed Status in gcc-9 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Bug description: IBM requests to update the Architecture Level Set (ALS) as follow.. march=z13 mtune=z15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1837525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed: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: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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: Pending -- package copied to Proposed signed: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 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 -- boot-testing-requested: true 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed: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/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: 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 Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued 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 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu
https://lkml.org/lkml/2019/11/5/398 -- 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/1827961 Title: Lenovo dock MAC Address pass through doesn't work in Ubuntu Status in linux package in Ubuntu: Confirmed Bug description: Similar to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579984 the MAC address pass through does not work with a Lenovo Thunderbolt 3 Workstation Dock. The dock's network port is recognized and working but it has its own MAC address even though MAC Address pass through is enabled in the BIOS. This is the dock in question: https://www.lenovo.com/us/en/accessories-and-monitors/top-tech /Thunderbolt-WS-230W-dock-US/p/40AN0230US and the laptop is a Lenovo P1. Debug files attached. Please let me know if further info is required. Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rauer 2107 F pulseaudio /dev/snd/controlC1: rauer 2107 F pulseaudio /dev/snd/controlC0: rauer 2107 F pulseaudio CurrentDesktop: i3 Date: Mon May 6 19:34:26 2019 InstallationDate: Installed on 2019-04-09 (27 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20MES1WH00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=9c2b3401-a2e2-41ae-bc22-d1de22149ee0 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET39W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MES1WH00 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET39W(1.21):bd04/15/2019:svnLENOVO:pn20MES1WH00:pvrThinkPadP1:rvnLENOVO:rn20MES1WH00:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 dmi.product.name: 20MES1WH00 dmi.product.sku: LENOVO_MT_20ME_BU_Think_FM_ThinkPad P1 dmi.product.version: ThinkPad P1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838245] Re: dkms script is missing function find_module
This changes seems to have been dropped in Ubuntu 19.10 and Focal.
** Changed in: dkms (Ubuntu)
Status: Fix Released => Confirmed
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1838245
Title:
dkms script is missing function find_module
Status in DKMS:
Fix Released
Status in dkms package in Ubuntu:
Confirmed
Status in dkms source package in Bionic:
Fix Released
Bug description:
update for SRU process:
[Impact]
1. dkms script is missing function find_module
2. priority of OBSOLETE_BY should higher than "force". #89
https://github.com/dell/dkms/issues/89
[Test case]
install the dkms which already patched (also can be found in my ppa[1])
1. install a dkms which for a kernel module system already installed.
e.g. ath10k of my testing ppa : [1]
1.1. the dkms can be installed well.
2. install a dkms which has OBSOLETE_BY and FORCE
e.g.ath10k of my testing ppa : [1] (source code in [2])
- the target dkms defined OBSOLETE_BY and FORCE
- user install dkms on a system which installed kernel version less than
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
- the dkms can be installed well.
[Regression potential]
medium as it touched the version sanity. This change correct the code logic
and land one more change from upstream as well.
The logic has been verified by #5 and me.
Building a kernel module using dkms in Linux Mint 19.1 shows the following
error:
Running module version sanity check.
/usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden
modinfo: ERROR: missing module or filename.
Checking the file the function is indeed missing and another user
confirmed, that it was removed at some point:
https://github.com/linuxmint/linuxmint/issues/142
Possible solution: Readd
find_module()
{
# tree = $1
# module = $2
find "$1" -name "$2$module_uncompressed_suffix" -o -name
"$2$module_suffix" -type f
return $?
}
as found in https://github.com/dell/dkms/blob/master/dkms
To manage notifications about this bug go to:
https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851350] Re: bionic/linux-aws-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => 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 -- kernel-stable-master-bug: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 - phase: Packaging - phase-changed: Tuesday, 05. November 2019 10:25 UTC + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 05. November 2019 17:06 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 + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta: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/1851350 Title: bionic/linux-aws-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 promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: Invalid 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303082/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug 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.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.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/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303086/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug 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.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.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/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303088/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug 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.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.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/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303089/+files/WifiSyslog.txt ** 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/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug 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.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.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/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303081/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug 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.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.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/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303083/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug 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.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.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/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303087/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug 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.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.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/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] Re: Missing modules for cryptography and NFSv4
apport information ** Tags added: apport-collected bionic ** Description changed: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. - Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit - much. + Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. + --- + ProblemType: Bug + 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.9-0ubuntu7.9 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + CRDA: N/A + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 + InstallationDate: Installed on 2017-02-11 (996 days ago) + InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 + ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-1048-kvm N/A + linux-backports-modules-4.15.0-1048-kvm N/A + linux-firmware 1.173.9 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic + Uname: Linux 4.15.0-1048-kvm x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) + UserGroups: + + _MarkForUpload: False + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: 1.10.2-1ubuntu1 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-xenial + dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.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 ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303080/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd
[Kernel-packages] [Bug 1851382] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303085/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug 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.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.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/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851382] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1851382/+attachment/5303084/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851382 Title: Missing modules for cryptography and NFSv4 Status in linux package in Ubuntu: Confirmed Bug description: There are two essential kernel modules that are missing from some linux kernel packages under Ubuntu Server 18.04 LTS: nfsv4.ko and aes-x86_64.ko (matter-of-fact any crypto module) I found them both missing in linux-kvm and nfsv4.ko missing in linux- generic - both are present in linux-generic-hwe-18.04. The use cases for these are not far-fetched: In an Ubuntu KVM guest, I often need virtual disks that I can encrypt via LUKS in order to protect them (somewhat). Obviously, this is not possible without the crypto modules, which are not present in the KVM- specialised kernel package 'linux-kvm'. On the other hand, when I want to mount NFS storage, I cannot use NFSv4, which is the preferred way of doing it when you need firewalling. Why this fails is not at all obvious, since the use-level "mount.nfs4" is present, but only gives cryptic messages, not showing that a kernel module is missing. And even with the default kernel (linux-generic), which has some more modules, NFSv4 client support is missing. Do I really have to use linux-generic-hwe-18.04 for that? It seems a bit much. --- ProblemType: Bug 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.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/unifi--vg-swap_1 InstallationDate: Installed on 2017-02-11 (996 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1048-kvm root=/dev/mapper/hostname--vg-root ro net.ifnames=0 biosdevname=0 ProcVersionSignature: Ubuntu 4.15.0-1048.48-kvm 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1048-kvm N/A linux-backports-modules-4.15.0-1048-kvm N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-1048-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2019-06-22 (136 days ago) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.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/+source/linux/+bug/1851382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851416] [NEW] Prime Profiles page could be better
Public bug reported: There are 4 possibly problem points, placement, names, tooltips, help. The 1st 3 are somewhat linked. The new profile, NVIDIA On-Demand is currently placed between the 2 previous & historical ones of NVIDIA.. & Intel.. The placement and name could lead one to believe that it's an app on demand or as needed similar to how optimus works in windows. This is clearly not the case & if picked produces a degraded experience for most users.. It should be the 3rd listed profile and if possible named more towards it's actual use case. There previously were 2 tooltips on hover, currently there still are just 2, the one designed for Intel now exposes only when hovered over NVIDIA On-Demand, hovering over Intel produces nothing NVIDIA On-Demand should get it's own tooltip. The Help button popup shows no info on what NVIDIA On-Demand is about or for, considering the vast majority of users should not use that profile it should be described, ect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Nov 5 12:18:49 2019 InstallationDate: Installed on 2019-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191029.2) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1851416 Title: Prime Profiles page could be better Status in nvidia-settings package in Ubuntu: New Bug description: There are 4 possibly problem points, placement, names, tooltips, help. The 1st 3 are somewhat linked. The new profile, NVIDIA On-Demand is currently placed between the 2 previous & historical ones of NVIDIA.. & Intel.. The placement and name could lead one to believe that it's an app on demand or as needed similar to how optimus works in windows. This is clearly not the case & if picked produces a degraded experience for most users.. It should be the 3rd listed profile and if possible named more towards it's actual use case. There previously were 2 tooltips on hover, currently there still are just 2, the one designed for Intel now exposes only when hovered over NVIDIA On-Demand, hovering over Intel produces nothing NVIDIA On-Demand should get it's own tooltip. The Help button popup shows no info on what NVIDIA On-Demand is about or for, considering the vast majority of users should not use that profile it should be described, ect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Nov 5 12:18:49 2019 InstallationDate: Installed on 2019-10-29 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191029.2) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1851416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 -- boot-testing-requested: true 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: - promote-to-proposed: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync 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: 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 Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync 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
** 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: Pending -- package copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync 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: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 -- packages waiting in -proposed for mirror sync 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 1832151] Re: Unexpected CFS throttling
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832151 Title: Unexpected CFS throttling Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: New Status in linux source package in Eoan: Incomplete Bug description: Basically, this issue: https://bugzilla.kernel.org/show_bug.cgi?id=198197 ..is affecting a cloud provider on a 4.15 kernel. Customer testing with a kernel that is patched with the fix (upstream: de53fd7aedb100f03e5d2231cfce0e4993282425 ) confirms that it resolves the issue. More details in the SalesForce ticket: https://canonical.my.salesforce.com/5003z1yUmC1 [Impact] * Aggressive throttling by CFS causes severe performance degradation in some cases. [Test Case] * This reproducer clearly shows the problem before the fix and shows no problem after the fix: https://gist.github.com/bobrik/2030ff040fad360327a5fab7a09c4ff1 [Regression Potential] * It touches core scheduler code so regression could be bad - but risk is low as the patch is accepted in mainline and tested separately by myself, the cloud provider, and at least 2 others. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.
*** This bug is a duplicate of bug 1808389 *** https://bugs.launchpad.net/bugs/1808389 Ok, this is a complex matter. I just experienced this unpleasant feature on my laptop using the above described driver and hardware for the last two days. =>It seems to be a radio transmission issue.<= (and this is damned complex!) The Linux driver as well as the microcode of the WiFi device must be able to cope with the small frequency jumps of the access point. Yes, frequencies are =>NOT<= very stable. This is shown in the logs by the following messages: wpa_supplicant[971]: wlp1s0: CTRL-EVENT-SIGNAL- CHANGE. When this event occurs, your hardware must resync with the access point. The driver as well as the microcode of your WiFi device may or may not support such a frequency jump. In other term they may or may not be able to cope with the noise. The following log message shows that my system was not able to cope with it: iwlwifi :01:00.0: Microcode SW error detected. What actually solved the issue is re-configuring the access point. I limited the channel width on the 2.4 Ghz frequency to 20 Mhz to avoid interference with other access points in the area. In addition I defined a precise channel for the access. For the channel selection, prefer channel 1, 6 or 11, since they do not overlap. Now my connection is stable and my logs are clean. For the 5 Ghz network, these problem might not occur as frequently as on the 2.4 Ghz one, since it is less used. In case similar issues are faced, proceed similarly. Hope it helps, Illi -- 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/1804841 Title: iwlwifi Microcode SW error detected. Restarting 0x200. Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Bug description: This seems to be a return of an existing bug, in newer hardware and microcode versions. Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78) Firmware version: 34.0.1 Description:Ubuntu 18.04.1 LTS Frequent errors as soon as I connect to wifi: Microcode SW error detected. Restarting 0x200. Expected to happen: Great and stable wifi like a couple of weeks ago What happens: very slow, intermittent internet access, lots of ping loss Found a suggestion of a workaround: adding these lines to /etc/NetworkManager/NetworkManager.conf [device] wifi.scan-rand-mac-address=no These lines were already there, not added by me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode] ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 23 15:23:54 2018 Dependencies: InstallationDate: Installed on 2018-09-03 (81 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
Ok, this is a complex matter. I just experienced this unpleasant feature on my laptop using the above described driver and hardware for the last two days. =>It seems to be a radio transmission issue.<= The Linux driver as well as the microcode of the WiFi device must be able to cope with the small frequency jumps of the access point. Yes, frequencies are =>NOT<= very stable. This is shown in the logs by the following messages: wpa_supplicant[971]: wlp1s0: CTRL-EVENT-SIGNAL- CHANGE. When this event occurs, your hardware must resync with the access point. The driver as well as the microcode of your WiFi device may or may not support such a frequency jump. In other term they may or may not be able to cope with the noise. The following log message shows that my system was not able to cope with it: iwlwifi :01:00.0: Microcode SW error detected. What actually solved the issue is re-configuring the access point. I limited the channel width on the 2.4 Ghz frequency to 20 Mhz to avoid interference with other access points in the area. In addition I defined a precise channel for the access. For the channel selection, prefer channel 1, 6 or 11, since they do not overlap. Now my connection is stable and my logs are clean. For the 5 Ghz network, these problem might not occur as frequently as on the 2.4 Ghz one, since it is less used. In case similar issues are faced, proceed similarly. Hope it helps, Illi Same comment was also posted in the dupplicate of this bug. -- 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/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 Status in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Committed Status in The Bionic Beaver: Confirmed Status in linux-firmware source package in Bionic: Fix Released Status in The Cosmic Cuttlefish: Confirmed Status in linux-firmware source package in Cosmic: Fix Released Bug description: SRU Justification: === [Impact] repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. [Fix] New iwlwifi firmware fix it. [Test] Bug reporter verified with positive result. [Regression Potential] Upstream fix, low risk. Bug reporter confirms fix. Original bug report: = Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. Firmware: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.840159] wlp2s0: send auth to 60:38:e0:70:a2:11 (try 1/3) Dec 13 11:53:36 james-x1 kernel: [ 856.844875] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Dec 13 11:53:36 james-x1 kernel: [ 856.845015] iwlwifi :02:00.0: Start IWL Error Log Dump: Dec 13 11:53:36 james-x1 kernel: [ 856.845018] iwlwifi :02:00.0: Status: 0x0100, count: 6 Dec 13 11:53:36 james-x1 kernel: [ 856.845021] iwlwifi :02:00.0: Loaded firmware version: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.845024] iwlwifi :02:00.0: 0x1006 | ADVANCED_SYSASSERT Dec 13 11:53:36 james-x1 kernel: [ 856.845026] iwlwifi :02:00.0: 0x02F0 | trm_hw_status0 Dec 13 11:53:36 james-x1 kernel: [ 856.845029] iwlwifi :02:00.0: 0x | trm_hw_status1 Dec 13 11:53:36 james-x1 kernel: [ 856.845031] iwlwifi :02:00.0: 0x000248DC | branchlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845034] iwlwifi :02:00.0: 0x0003A7DA | interruptlink1 Dec 13 11:53:36 james-x1 kernel: [ 856.845036] iwlwifi :02:00.0: 0x | interruptlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845039] iwlwifi :02:00.0: 0xFEDA | data1 Dec 13 11:53:36 james-x1 kernel: [ 856.845041] iwlwifi :02:00.0: 0xDEADBEEF | data2 Dec 13 11:53:36 james-x1 kernel: [ 856.845044] iwlwifi :02:00.0: 0xDEADBEEF | data3 Dec 13 11:53:36 james-x1 kernel: [ 856.845046] iwlwifi :02:00.0: 0x0007E1DC | beacon time Dec 13 11:53:36 james-x1 kernel: [ 856.845048] iwlwifi :02:00.0: 0x003B0850 | tsf low Dec 13 11:53:36 james-x1 kernel: [ 856.845051] iwlwifi :02:00.0: 0x | tsf hi Dec 13 11:53:36 james-x1 kernel: [ 856.845053] iwlwifi :02:00.0: 0x | time gp1 Dec 13 11:53:36 james-x1 kernel: [ 856.845055] iwlwifi :02:00.0: 0x003B0852 | time gp2 Dec 13 11:53:36 james-x1 kernel: [ 856.845058] iwlwifi :02:00.0: 0x0001 | uCode revision type Dec 13 11:53:36 james-x1 kernel: [ 856.845060] iwlwifi :02:00.0: 0x0024 | uCode version major Dec 13 11:53:36 james-x1 kernel: [ 856.845063] iwlwifi :02:00.0: 0x7596AFD4 | uCode version minor Dec 13 11:53:36 james-x1 kernel: [ 856.845065] iwlwifi :02:00.0: 0x0230 | hw version Dec 13 11:53:36 james-x1 kernel: [ 856.845068] iwlwifi :02:00.0: 0x18489000 | board version Dec 13 11:53:36 james-x1 kernel: [ 856.845070] iwlwifi :02:00.0: 0x0501
[Kernel-packages] [Bug 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
The following packages ended up in the wrong component in the Proposed pocket: linux-restricted-modules-gcp-5.3 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-5.3.0-1007-gcp 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-gcp-edge 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-5.3.0-1007-gcp 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-gcp-edge 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-headers-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-image-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-modules-extra-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-tools-gcp-edge 5.3.0.1007.7 - is in main instead of universe Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + promote-to-proposed: Stalled -- packages are in the wrong component + 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/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: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component 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/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
The following packages ended up in the wrong component in the Proposed pocket: linux-restricted-modules-azure-5.3 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-5.3.0-1006-azure 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-azure-edge 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-5.3.0-1006-azure 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-azure-edge 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-cloud-tools-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-headers-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-image-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-modules-extra-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-signed-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-signed-image-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-tools-azure-edge 5.3.0.1006.6 - is in main instead of universe Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Fix Released ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** 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 -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + promote-to-proposed: Stalled -- packages are in the wrong component + regression-testing: Ongoing -- testing in progress + stakeholder-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 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: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed 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: 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: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component regression-testing: Ongoing -- testing in progress stakeho
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4
** Also affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: New => Triaged ** Changed in: linux-raspi2 (Ubuntu Eoan) Importance: Undecided => High -- 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 Status in linux-raspi2 source package in Eoan: Triaged 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 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)
I am having this issue with a DELL XPS 13 (Intel HD 620). -- 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/1848741 Title: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have graphics artefacts: screan tearing, pieces of the previous window appear in the newly opened window. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-08 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841288] Re: does not create compressed dump on 5.0 or later kernels
I was able to verify both releases. *** Disco test, with kernel 5.0.0-32-generic *** Running kdump-tools/makedumpfile from -updates pocket : $ file vmcore.201911051825 vmcore.201911051825: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1 (SYSV), SVR4-style Running the -proposed packages for kdump-tools and makedumpfile, version 1:1.6.5-1ubuntu1.3 : $ file dump.201911051840 dump.201911051840: Kdump compressed dump v6, system Linux, node gpiccoli-ppc64, release 5.0.0-32-generic, version #34-Ubuntu SMP Wed Oct 2 02:06:32 UTC 2019, machine ppc64le, domain (none) *** Bionic test, with kernel 5.0.0-32-generic *** Running kdump-tools/makedumpfile from -updates pocket : $ file vmcore.201911051957 vmcore.201911051957: ELF 64-bit LSB core file 64-bit PowerPC or cisco 7500, version 1 (SYSV), SVR4-style Also, saw the following message in console while makedumpfile was trying to collect the compressed dump: "get_machdep_info_ppc64: Can't detect max_physmem_bits." Running the -proposed packages for kdump-tools and makedumpfile, version 1:1.6.5-1ubuntu1~18.04.3 : $ file dump.201911052003 dump.201911052003: Kdump compressed dump v6, system Linux, node bionic-ppc, release 5.0.0-32-generic, version #34~18.04.2-Ubuntu SMP Thu Oct 10 10:35:58 UTC 2019, machine ppc64le, domain (none) ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco ** Tags added: verification-done verification-done-bionic verification-done-disco -- 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/1841288 Title: does not create compressed dump on 5.0 or later kernels Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Disco: Fix Committed Bug description: [Impact] On ppc64el, makedumpfile won't create compressed dumps, causing them to be very large. This affects any kernel later than 4.19 actually. [Test case] Crash a system with kdump-tools installed and enabled, by using the following sequence. Verify the created dumps are compressed by using file. This is the same test as the autopkgtest for makedumpfile. echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Regression potential] This is a small fix and should only impact ppc64el. Older kernels should still work, and should be tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1841288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851412] Re: Verify kexec image signatures on arm64
** Information type changed from Private Security to Public Security
--
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/1851412
Title:
Verify kexec image signatures on arm64
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Disco:
Invalid
Status in linux source package in Eoan:
Invalid
Status in linux source package in Focal:
Invalid
Bug description:
While reviewing our kernel configs in Focal, I noticed that we produce
signed arm64 kernels since Disco but don't seem to be verifying any
signatures during kexec. Specifically, CONFIG_KEXEC_IMAGE_VERIFY_SIG
is not enabled.
== Disco ==
$ git grep CONFIG_KEXEC_IMAGE_VERIFY_SIG
debian.master/debian.master/config/annotations:CONFIG_KEXEC_IMAGE_VERIFY_SIG
policy<{'arm64': 'n'}>
debian.master/config/annotations:CONFIG_KEXEC_IMAGE_VERIFY_SIG
flag
debian.master/config/config.common.ubuntu:# CONFIG_KEXEC_IMAGE_VERIFY_SIG is
not set
== Eoan ==
$ git grep CONFIG_KEXEC_IMAGE_VERIFY_SIG debian.master/
debian.master/config/annotations:CONFIG_KEXEC_IMAGE_VERIFY_SIG
policy<{'arm64': 'n'}>
debian.master/config/annotations:CONFIG_KEXEC_IMAGE_VERIFY_SIG
flag
debian.master/config/config.common.ubuntu:# CONFIG_KEXEC_IMAGE_VERIFY_SIG is
not set
Looking at the Ubuntu-5.3.0-19.20 tag in Eoan, it looks like the
CONFIG_KEXEC_IMAGE_VERIFY_SIG option should be enabled to perform signature
verification of kexec images:
$ cat -n arch/arm64/kernel/kexec_image.c | tail -n 15
116#ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG
117static int image_verify_sig(const char *kernel, unsigned long
kernel_len)
118{
119return verify_pefile_signature(kernel, kernel_len, NULL,
120
VERIFYING_KEXEC_PE_SIGNATURE);
121}
122#endif
123
124const struct kexec_file_ops kexec_image_ops = {
125.probe = image_probe,
126.load = image_load,
127#ifdef CONFIG_KEXEC_IMAGE_VERIFY_SIG
128.verify_sig = image_verify_sig,
129#endif
130};
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851412/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown
** Information type changed from Private Security to Public Security
--
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/1851380
Title:
root can lift kernel lockdown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Invalid
Status in linux source package in Bionic:
Triaged
Status in linux source package in Disco:
Triaged
Status in linux source package in Eoan:
Triaged
Status in linux source package in Focal:
In Progress
Bug description:
Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
though it shouldn't.
If I'm not mistaken, kernel lockdown is meant to create a barrier
between root and the kernel that can only be broken with physical
access to the system. It is automatically enabled when the system is
booted with UEFI Secure Boot, which is the case for me.
This should show the bug:
# echo "x" > /proc/sysrq-trigger
Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from
userspace.
Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
Nov 05 14:58:15 panzersperre kernel: Lifting lockdown
Note that it first says that the operation is disabled and then performs this
operation.
This should only be possible by physically pressing sysrq+x on an attached
keyboard.
I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
I have kernel.sysrq set to 1 - this is important to be able to trigger this
bug. (But I don't think it disqualifies this issue as non-security relevant
because root can trivially execute `sysctl kernel.sysrq=1`.)
I first learned about this by reading a blog post
(https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-
lifting-the-kernel-lockdown/), so I'm not the first to notice this
behavior (even though this post doesn't say it's a bug).
Looking through drivers/tty/sysrq.c, I guess the problem is caused by
this if condition in __handle_sysrq:
554 │ /* Ban synthetic events from some sysrq functionality */
555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
557 │ printk("This sysrq operation is disabled from
userspace.\n");
558 │ /*
559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
560 │ * should not) and is the invoked operation enabled?
561 │ */
562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
563 │ pr_cont("%s\n", op_p->action_msg);
564 │ console_loglevel = orig_log_level;
565 │ op_p->handler(key);
566 │ } else {
567 │ pr_cont("This sysrq operation is disabled.\n");
568 │ }
Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
printk and no change of behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-68-generic 4.15.0-68.77
ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
Uname: Linux 4.15.0-68-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: niklas 2442 F pulseaudio
/dev/snd/controlC0: niklas 2442 F pulseaudio
CurrentDesktop: KDE
Date: Tue Nov 5 14:58:33 2019
InstallationDate: Installed on 2015-12-11 (1424 days ago)
InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: LENOVO 20E8S00600
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-68-generic
root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet
splash kaslr i915.alpha_support=1 vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-68-generic N/A
linux-backports-modules-4.15.0-68-generic N/A
linux-firmware 1.173.11
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-07-05 (487 days ago)
dmi.bios.date: 09/26/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: JHET69WW (1.69 )
dmi.board.asset.tag: Not Available
dmi.board.name: Intel powered classmate PC
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrJHET69WW(1.69):bd09/26/2018:svnLENOVO:pn20E8S00600:pvrThinkPad11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad 11e
dmi.product.name: 20E8S00600
dmi.product.version: ThinkPad 11e
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
[Kernel-packages] [Bug 1846288] Re: 5G connectivity on Intel AC9260 gradually diminishes during usage
Hi, just updating this, the backports solution did not work for me. At this point it is a serious enough problem to roll back and wait for a more durable 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/1846288 Title: 5G connectivity on Intel AC9260 gradually diminishes during usage Status in linux package in Ubuntu: Confirmed Bug description: Intel AC9260 will connect to 5G WiFi without issue. However, after a few minutes of use, the connection will slow to a crawl and eventually time out until manually switched to a traditional WiFi. Other devices on the same 5G network do not experience this behavior. This behavior does not occur under 18.04LTS. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 23:15:35 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-10-01 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eric 1795 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-01 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) MachineType: Dell Inc. XPS 15 9570 NonfreeKernelModules: nvidia_modeset nvidia 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=cbdfb299-4ef9-49ab-adb8-0c346f806bb7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eric 1795 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-01 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) MachineType: Dell Inc. XPS 15 9570 NonfreeKernelModules: nvidia_modeset nvidia 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=cbdfb299-4ef9-49ab-adb8-0c346f806bb7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bu
[Kernel-packages] [Bug 1824407] Re: remount of multilower moved pivoted-root overlayfs root, results in I/O errors on some modified files
4.15: ovl_get_origin_fh detects zero sized files on lower paths and treats these a special zero sized "copied up but origin unknown" magic. [ 25.442916] ovl_check_origin: etc/.pwd.lock 2 [ 25.442918] ovl_get_origin_fh: 104 etc/.pwd.lock [ 25.442919] ovl_get_origin_fh: 107 res=0 [ 25.442920] ovl_get_origin_fh: 117 res == 0, return NULL [ 25.442921] ovl_get_origin: 179 fh = (null) 1 [ 25.442922] ovl_get_origin_fh: 104 etc/.pwd.lock [ 25.442922] ovl_get_origin_fh: 107 res=0 [ 25.442923] ovl_get_origin_fh: 117 res == 0, return NULL [ 25.442923] ovl_get_origin: 179 fh = (null) 1 5.3: the lower is / and hence is a directory hence the S_IFDIR origin return. [ 33.320630] ovl_get_fh: 112 dentry: etc/.pwd.lock name: trusted.overlay.origin [ 33.320632] ovl_get_fh: 115: res = 29 [ 33.320634] ovl_get_fh: 152: return fh = 6e71855c [ 33.320634] ovl_check_origin: 413 fh = 6e71855c [ 33.320635] ovl_check_origin_fh: 354 upperdentry = etc/.pwd.lock [ 33.320635] ovl_decode_real_fh: 174 [ 33.320769] ovl_decode_real_fh: 211 return dentry (OK) [ 33.320769] ovl_check_origin_fh: 360, i=0, origin = / [ 33.320770] ovl_check_origin_fh: level=0 upper: etc/.pwd.lock 100600, lower: / 40755 [ 33.320770] ovl_check_origin_fh: 380 goto invalid [ 33.320771] overlayfs: invalid origin (etc/.pwd.lock, ftype=8000, origin ftype=4000). [ 33.320773] ovl_check_origin: 422 err = -5 [ 33.320774] ovl_check_origin: 429, return -5 -- 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 1851350] Re: bionic/linux-aws-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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:depwait variant: debs ** 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta: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/1851350 Title: bionic/linux-aws-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 promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: Invalid 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown
** Tags added: patch
--
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/1851380
Title:
root can lift kernel lockdown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Invalid
Status in linux source package in Bionic:
Triaged
Status in linux source package in Disco:
Triaged
Status in linux source package in Eoan:
Triaged
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification
Impact: The kernel lockdown support adds a sysrq to allow a physically
present user to disable lockdown from the keyboard. A bug in the
implementation makes it possible to also lift lockdown by writing to
/proc/sysrq-trigger.
Fix: Correct the logic to disallow disabling lockdown via /proc/sysrq-
trigger.
Test Case: Write "x" to /proc/sysrq-trigger. When working properly
there should be no messages in dmesg about lifting lockdown, and
lockdown restrictions (e.g. loading unsigned modules) should remain in
effect.
Regression Potential: Anyone using /proc/sysrq-trigger to disable
lockdown will no longer be able to do so. Implementation bugs could
prevent use of the sysrq from the keyboard from disabling lockdown,
but this has been confrimed to still work with the fix in place.
---
Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
though it shouldn't.
If I'm not mistaken, kernel lockdown is meant to create a barrier
between root and the kernel that can only be broken with physical
access to the system. It is automatically enabled when the system is
booted with UEFI Secure Boot, which is the case for me.
This should show the bug:
# echo "x" > /proc/sysrq-trigger
Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from
userspace.
Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
Nov 05 14:58:15 panzersperre kernel: Lifting lockdown
Note that it first says that the operation is disabled and then performs this
operation.
This should only be possible by physically pressing sysrq+x on an attached
keyboard.
I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
I have kernel.sysrq set to 1 - this is important to be able to trigger this
bug. (But I don't think it disqualifies this issue as non-security relevant
because root can trivially execute `sysctl kernel.sysrq=1`.)
I first learned about this by reading a blog post
(https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-
lifting-the-kernel-lockdown/), so I'm not the first to notice this
behavior (even though this post doesn't say it's a bug).
Looking through drivers/tty/sysrq.c, I guess the problem is caused by
this if condition in __handle_sysrq:
554 │ /* Ban synthetic events from some sysrq functionality */
555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
557 │ printk("This sysrq operation is disabled from
userspace.\n");
558 │ /*
559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
560 │ * should not) and is the invoked operation enabled?
561 │ */
562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
563 │ pr_cont("%s\n", op_p->action_msg);
564 │ console_loglevel = orig_log_level;
565 │ op_p->handler(key);
566 │ } else {
567 │ pr_cont("This sysrq operation is disabled.\n");
568 │ }
Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
printk and no change of behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-68-generic 4.15.0-68.77
ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
Uname: Linux 4.15.0-68-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: niklas 2442 F pulseaudio
/dev/snd/controlC0: niklas 2442 F pulseaudio
CurrentDesktop: KDE
Date: Tue Nov 5 14:58:33 2019
InstallationDate: Installed on 2015-12-11 (1424 days ago)
InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: LENOVO 20E8S00600
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-68-generic
root=UUID=67485aa6-c665-4c53-bf41-328307d0cbf0 ro rootflags=subvol=@ quiet
splash kaslr i915.alpha_support=1 vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-68-generic N/A
linux-backports-modules-4.15.0-68-generic N/A
linux-firmware 1.173.11
SourcePackage: linux
UpgradeStatus:
[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown
** Description changed:
+ SRU Justification
+
+ Impact: The kernel lockdown support adds a sysrq to allow a physically
+ present user to disable lockdown from the keyboard. A bug in the
+ implementation makes it possible to also lift lockdown by writing to
+ /proc/sysrq-trigger.
+
+ Fix: Correct the logic to disallow disabling lockdown via /proc/sysrq-
+ trigger.
+
+ Test Case: Write "x" to /proc/sysrq-trigger. When working properly there
+ should be no messages in dmesg about lifting lockdown, and lockdown
+ restrictions (e.g. loading unsigned modules) should remain in effect.
+
+ Regression Potential: Anyone using /proc/sysrq-trigger to disable
+ lockdown will no longer be able to do so. Implementation bugs could
+ prevent use of the sysrq from the keyboard from disabling lockdown, but
+ this has been confrimed to still work with the fix in place.
+
+ ---
+
Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
though it shouldn't.
If I'm not mistaken, kernel lockdown is meant to create a barrier
between root and the kernel that can only be broken with physical access
to the system. It is automatically enabled when the system is booted
with UEFI Secure Boot, which is the case for me.
This should show the bug:
- # echo "x" > /proc/sysrq-trigger
- Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
+ # echo "x" > /proc/sysrq-trigger
+ Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from
userspace.
Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
Nov 05 14:58:15 panzersperre kernel: Lifting lockdown
Note that it first says that the operation is disabled and then performs this
operation.
This should only be possible by physically pressing sysrq+x on an attached
keyboard.
I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
I have kernel.sysrq set to 1 - this is important to be able to trigger this
bug. (But I don't think it disqualifies this issue as non-security relevant
because root can trivially execute `sysctl kernel.sysrq=1`.)
I first learned about this by reading a blog post
(https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-lifting-
the-kernel-lockdown/), so I'm not the first to notice this behavior
(even though this post doesn't say it's a bug).
Looking through drivers/tty/sysrq.c, I guess the problem is caused by
this if condition in __handle_sysrq:
- 554 │ /* Ban synthetic events from some sysrq functionality */
- 555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
- 556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
- 557 │ printk("This sysrq operation is disabled from
userspace.\n");
- 558 │ /*
- 559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
- 560 │ * should not) and is the invoked operation enabled?
- 561 │ */
- 562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
- 563 │ pr_cont("%s\n", op_p->action_msg);
- 564 │ console_loglevel = orig_log_level;
- 565 │ op_p->handler(key);
- 566 │ } else {
- 567 │ pr_cont("This sysrq operation is disabled.\n");
- 568 │ }
+ 554 │ /* Ban synthetic events from some sysrq functionality */
+ 555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
+ 556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
+ 557 │ printk("This sysrq operation is disabled from
userspace.\n");
+ 558 │ /*
+ 559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
+ 560 │ * should not) and is the invoked operation enabled?
+ 561 │ */
+ 562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
+ 563 │ pr_cont("%s\n", op_p->action_msg);
+ 564 │ console_loglevel = orig_log_level;
+ 565 │ op_p->handler(key);
+ 566 │ } else {
+ 567 │ pr_cont("This sysrq operation is disabled.\n");
+ 568 │ }
Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
printk and no change of behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-68-generic 4.15.0-68.77
ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
Uname: Linux 4.15.0-68-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: niklas 2442 F pulseaudio
- /dev/snd/controlC0: niklas 2442 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: niklas 2442 F pulseaudio
+ /dev/snd/controlC0: niklas 2442 F pulseaudio
CurrentDesktop: KDE
Date: Tue Nov
[Kernel-packages] [Bug 1851380] Re: root can lift kernel lockdown
I'm no expert in either kernel or C programming and I didn't test this
patch, but it looks good to me.
Also, the resulting code is quite similar to the one Fedora is currently using
- they accidentally fixed this bug in
https://src.fedoraproject.org/rpms/kernel/c/5df4c5562f191b434edf57e8c92b176baad37cba.
(Debian also seems to be affected:
https://salsa.debian.org/kernel-team/linux/blob/4dcfa860/debian/patches/features/all/lockdown/0002-Add-a-SysRq-option-to-lift-kernel-lockdown.patch)
--
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/1851380
Title:
root can lift kernel lockdown
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
Invalid
Status in linux source package in Bionic:
Triaged
Status in linux source package in Disco:
Triaged
Status in linux source package in Eoan:
Triaged
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification
Impact: The kernel lockdown support adds a sysrq to allow a physically
present user to disable lockdown from the keyboard. A bug in the
implementation makes it possible to also lift lockdown by writing to
/proc/sysrq-trigger.
Fix: Correct the logic to disallow disabling lockdown via /proc/sysrq-
trigger.
Test Case: Write "x" to /proc/sysrq-trigger. When working properly
there should be no messages in dmesg about lifting lockdown, and
lockdown restrictions (e.g. loading unsigned modules) should remain in
effect.
Regression Potential: Anyone using /proc/sysrq-trigger to disable
lockdown will no longer be able to do so. Implementation bugs could
prevent use of the sysrq from the keyboard from disabling lockdown,
but this has been confrimed to still work with the fix in place.
---
Echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even
though it shouldn't.
If I'm not mistaken, kernel lockdown is meant to create a barrier
between root and the kernel that can only be broken with physical
access to the system. It is automatically enabled when the system is
booted with UEFI Secure Boot, which is the case for me.
This should show the bug:
# echo "x" > /proc/sysrq-trigger
Nov 05 14:58:15 panzersperre kernel: sysrq: SysRq :
Nov 05 14:58:15 panzersperre kernel: This sysrq operation is disabled from
userspace.
Nov 05 14:58:15 panzersperre kernel: Disabling Secure Boot restrictions
Nov 05 14:58:15 panzersperre kernel: Lifting lockdown
Note that it first says that the operation is disabled and then performs this
operation.
This should only be possible by physically pressing sysrq+x on an attached
keyboard.
I'm doing this on 4.15.0-68-generic on Ubuntu 18.04.3 LTS.
I have kernel.sysrq set to 1 - this is important to be able to trigger this
bug. (But I don't think it disqualifies this issue as non-security relevant
because root can trivially execute `sysctl kernel.sysrq=1`.)
I first learned about this by reading a blog post
(https://gehrcke.de/2019/09/running-an-ebpf-program-may-require-
lifting-the-kernel-lockdown/), so I'm not the first to notice this
behavior (even though this post doesn't say it's a bug).
Looking through drivers/tty/sysrq.c, I guess the problem is caused by
this if condition in __handle_sysrq:
554 │ /* Ban synthetic events from some sysrq functionality */
555 │ if ((from == SYSRQ_FROM_PROC || from ==
SYSRQ_FROM_SYNTHETIC) &&
556 │ op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
557 │ printk("This sysrq operation is disabled from
userspace.\n");
558 │ /*
559 │ * Should we check for enabled operations
(/proc/sysrq-trigger
560 │ * should not) and is the invoked operation enabled?
561 │ */
562 │ if (from == SYSRQ_FROM_KERNEL ||
sysrq_on_mask(op_p->enable_mask)) {
563 │ pr_cont("%s\n", op_p->action_msg);
564 │ console_loglevel = orig_log_level;
565 │ op_p->handler(key);
566 │ } else {
567 │ pr_cont("This sysrq operation is disabled.\n");
568 │ }
Note that `op_p->enable_mask & SYSRQ_DISABLE_USERSPACE` just causes a
printk and no change of behavior.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-68-generic 4.15.0-68.77
ProcVersionSignature: Ubuntu 4.15.0-68.77-generic 4.15.18
Uname: Linux 4.15.0-68-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: niklas 2442 F pulseaudio
/dev/snd/controlC0: niklas 2442 F pulseaudio
CurrentDesktop: KDE
Date: Tue Nov 5 14:58:33 2019
InstallationDate: Installed on 2015-12-11 (1424 days ago)
InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (2015
[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: Incomplete => 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/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: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed 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: 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: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- 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/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 Status: Incomplete => 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/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: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component 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/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 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
The following packages ended up in the wrong component in the Proposed pocket: linux-restricted-modules-gcp-5.3 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-5.3.0-1007-gcp 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-gcp-edge 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-5.3.0-1007-gcp 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-gcp-edge 5.3.0-1007.7~18.04.1 - is in restricted instead of multiverse linux-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-headers-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-image-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-modules-extra-gcp-edge 5.3.0.1007.7 - is in main instead of universe linux-tools-gcp-edge 5.3.0.1007.7 - is in main instead of universe Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => 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/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: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component 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/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
The following packages ended up in the wrong component in the Proposed pocket: linux-restricted-modules-azure-5.3 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-5.3.0-1006-azure 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-azure-edge 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-5.3.0-1006-azure 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-430-azure-edge 5.3.0-1006.6~18.04.1 - is in restricted instead of multiverse linux-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-cloud-tools-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-headers-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-image-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-modules-extra-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-signed-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-signed-image-azure-edge 5.3.0.1006.6 - is in main instead of universe linux-tools-azure-edge 5.3.0.1006.6 - is in main instead of universe Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => 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/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: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed 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: 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: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- 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/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 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: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Stalled -- packages are in the wrong component + promote-to-proposed: Ongoing -- package copied to Proposed main:building,signed:building regression-testing: Ongoing -- testing in progress stakeholder-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 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: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed 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: 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: automated-testing: Stalled -- testing FAILED promote-to-proposed: Ongoing -- package copied to Proposed main:building,signed:building regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- 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/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 1780590] Re: Add support for Realtek 8723DE wireless adapter
** Summary changed: - no wireless adapter was found ubuntu 18.04 + Add support for Realtek 8723DE wireless adapter -- 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: Add support for Realtek 8723DE wireless adapter 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 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: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Ongoing -- package copied to Proposed main:building,signed:building + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress stakeholder-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 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: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed 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: 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: automated-testing: Stalled -- testing FAILED promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- 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/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
** 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Stalled -- packages are in the wrong component + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync 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/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: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released 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: 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: Promote to Proposed phase-changed: Tuesday, 05. November 2019 13:55 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync 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/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 1825413] Re: mdadm, mkfs, other io commands hang, stuck task, bad rip
Same on physical HW (Medion with QuadCore) This seems to happen during mdadm run, every time a new initrd is being built. lsblk doesn't hag. blkid hangs. mdadm hangs. In this ps output, mdadm has been hung for almos two hours. jpc@quad:~$ ps -ft pts/4 ; date UIDPID PPID C STIME TTY TIME CMD root 7969 28631 0 20:29 pts/400:00:00 /bin/sh /var/lib/dpkg/info/linux-image-5.3.0-19-generic.postinst triggered l root 7970 7969 0 20:29 pts/400:00:00 sh /usr/lib/linux/triggers/5.3.0-19-generic root 7971 7970 0 20:29 pts/400:00:00 run-parts --report --exit-on-error --arg=5.3.0-19-generic --arg=/boot/vmlinu root 8047 7971 0 20:30 pts/400:00:00 /bin/sh -e /etc/kernel/postinst.d/initramfs-tools 5.3.0-19-generic /boot/vml root 8049 8047 0 20:30 pts/400:00:00 /bin/sh /usr/sbin/update-initramfs -c -k 5.3.0-19-generic -b /boot root 8051 8049 0 20:30 pts/400:00:00 /bin/sh /usr/sbin/mkinitramfs -o /boot/initrd.img-5.3.0-19-generic.new 5.3.0 root 18519 8051 0 20:30 pts/400:00:00 /bin/sh /usr/share/initramfs-tools/hooks/mdadm root 18642 18519 0 20:30 pts/400:00:00 /bin/sh /usr/share/mdadm/mkconf root 18648 18642 0 20:30 pts/400:00:00 /sbin/mdadm --examine --scan --config=partitions root 28631 17100 0 20:29 pts/400:00:00 /usr/bin/dpkg --force-overwrite --status-fd 112 --configure --pending [1499890.437313] INFO: task mdadm:18648 blocked for more than 120 seconds. [1499890.437318] Not tainted 5.0.0-31-generic #33-Ubuntu [1499890.437320] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [1499890.437322] mdadm D0 18648 18642 0x0080 [1499890.437325] Call Trace: [1499890.437335] __schedule+0x2d0/0x840 [1499890.437338] ? __switch_to_asm+0x41/0x70 [1499890.437340] ? __switch_to_asm+0x35/0x70 [1499890.437342] schedule+0x2c/0x70 [1499890.437344] schedule_timeout+0x258/0x360 [1499890.437346] wait_for_completion+0xb7/0x140 [1499890.437350] ? wake_up_q+0x80/0x80 [1499890.437358] __floppy_read_block_0+0x138/0x190 [floppy] [1499890.437362] ? floppy_cmos_show+0x30/0x30 [floppy] [1499890.437367] floppy_revalidate+0xf8/0x230 [floppy] [1499890.437370] check_disk_change+0x62/0x70 [1499890.437374] floppy_open+0x2ae/0x380 [floppy] [1499890.437376] __blkdev_get+0xe5/0x550 [1499890.437378] ? bd_acquire+0xd0/0xd0 [1499890.437380] blkdev_get+0x10c/0x330 [1499890.437382] ? bd_acquire+0xd0/0xd0 [1499890.437384] blkdev_open+0x92/0x100 [1499890.437386] do_dentry_open+0x143/0x3a0 [1499890.437389] vfs_open+0x2d/0x30 [1499890.437391] path_openat+0x2bf/0x1570 [1499890.437394] ? put_device+0x17/0x20 [1499890.437397] ? scsi_device_put+0x2b/0x30 [1499890.437400] do_filp_open+0x93/0x100 [1499890.437403] ? strncpy_from_user+0x57/0x1c0 [1499890.437405] ? __alloc_fd+0x46/0x150 [1499890.437407] do_sys_open+0x177/0x280 [1499890.437409] ? _cond_resched+0x19/0x30 [1499890.437412] __x64_sys_openat+0x20/0x30 [1499890.437415] do_syscall_64+0x5a/0x110 [1499890.437417] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1499890.437419] RIP: 0033:0x7f84b3cc8fdb [1499890.437426] Code: Bad RIP value. [1499890.437427] RSP: 002b:7ffd8cb8fed0 EFLAGS: 0246 ORIG_RAX: 0101 [1499890.437429] RAX: ffda RBX: 4000 RCX: 7f84b3cc8fdb [1499890.437431] RDX: 4000 RSI: 5563a1618b80 RDI: ff9c [1499890.437432] RBP: 5563a1618b80 R08: 1999 R09: [1499890.437433] R10: R11: 0246 R12: 4000 [1499890.437434] R13: R14: 0001 R15: 5563a1612a00 -- 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/1825413 Title: mdadm, mkfs, other io commands hang, stuck task, bad rip Status in linux package in Ubuntu: Confirmed Bug description: 1. disco 2. # apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.0.0.13.14 Candidate: 5.0.0.13.14 Version table: *** 5.0.0.13.14 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 3. installation completes sucessfully 4. Running an installation of Disco creating filesystems and probing things will hang (stuck task) every so often. When it happens, the kernel throws an oops and bad rip value. [ 967.810391] INFO: task mdadm:12213 blocked for more than 120 seconds. [ 967.811787] Tainted: P O 5.0.0-13-generic #14-Ubuntu [ 967.813330] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.815500] mdadm D0 12213 12207 0x [ 967.815503] Call Trace: [ 967.815509] __schedule+0x2d0/0x840 [ 967.815511] ? __switch_to_asm+0x40/0x70 [ 967.815512] ? __switch_to_asm+0x34/0x70 [ 967.815514] schedule
[Kernel-packages] [Bug 1851350] Re: bionic/linux-aws-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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa meta: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/1851350 Title: bionic/linux-aws-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 promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: Invalid 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: 1850477 packages: lrm: linux-restricted-modules-aws-5.3 main: linux-aws-5.3 meta: linux-meta-aws-5.3 phase: Holding before Promote to Proposed phase-changed: Tuesday, 05. November 2019 17:06 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** 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: 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: Promote to Proposed - phase-changed: Tuesday, 05. November 2019 13:55 UTC + phase: Testing + phase-changed: Tuesday, 05. November 2019 23:31 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync 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/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: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 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: 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: Testing phase-changed: Tuesday, 05. November 2019 23:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED 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/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: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** 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 + phase: Testing + phase-changed: Tuesday, 05. November 2019 23:31 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress stakeholder-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 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: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 stakeholder-signoff series: Confirmed 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: 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: Testing phase-changed: Tuesday, 05. November 2019 23:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- 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/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
