[Kernel-packages] [Bug 1844355] Re: bionic/linux-oracle-edge: 5.0.0-1004.5~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Invalid => New ** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => New ** Changed in: kernel-sru-workflow/prepare-package Assignee: Khaled El Mously (kmously) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => New ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => New ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Khaled El Mously (kmously) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844355 Title: bionic/linux-oracle-edge: 5.0.0-1004.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: New Status in Kernel SRU Workflow prepare-package 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: 1845436 packages: main: linux-oracle-edge meta: linux-meta-oracle-edge signed: linux-signed-oracle-edge phase: Packaging phase-changed: Friday, 27. September 2019 04:16 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1842843 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844355] Re: bionic/linux-oracle-edge: 5.0.0-1004.5~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: 1845436 packages: main: linux-oracle-edge meta: linux-meta-oracle-edge signed: linux-signed-oracle-edge - phase: Ready for Packaging - phase-changed: Friday, 27. September 2019 00:17 UTC + phase: Packaging + phase-changed: Friday, 27. September 2019 04:16 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1842843 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/1844355 Title: bionic/linux-oracle-edge: 5.0.0-1004.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-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1845436 packages: main: linux-oracle-edge meta: linux-meta-oracle-edge signed: linux-signed-oracle-edge phase: Packaging phase-changed: Friday, 27. September 2019 04:16 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1842843 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845127] Re: bionic/linux-gcp: 5.0.0-1019.19~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: 1845128 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Wednesday, 25. September 2019 22:35 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 replaces: bug 1844346 trackers: - bionic/linux-gcp-edge: bug 1845513, bug 1844345 + bionic/linux-gcp-edge: bug 1844345, bug 1845513 bionic/linux-gcp/gcp-kernel: bug 1845126 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1845127 Title: bionic/linux-gcp: 5.0.0-1019.19~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug 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: 1845128 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Wednesday, 25. September 2019 22:35 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 replaces: bug 1844346 trackers: bionic/linux-gcp-edge: bug 1844345, bug 1845513 bionic/linux-gcp/gcp-kernel: bug 1845126 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845584] Re: intel-lpss driver conflicts with write-combining MTRR region
** 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/1845584 Title: intel-lpss driver conflicts with write-combining MTRR region Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in FF-Series: In Progress Bug description: [Impact] The memory region intel-lpss-pci uses has been declared as write-combining [0.001728] 5 base 40 mask 60 write-combining This leads to the system hangs up during booting up. This is a BIOS issue, but there are some platforms on the market and users are struggling on booting up the machines. So, we may have to fix this in the kernel. [Fix] Tuowen Zhao(ztuo...@gmail.com)[1] provides a diff patch for intel-lpss driver to claim to use un-catchable memory while calling __devm_ioremap(), and it works well. But it didn't be accepted by maintainer yet. To avoid the potential impact on other machines, I add a quirk to list the machines which has the write-combining area in MTRR which overlaps with the address that intel-lpss uses, only the machines in the list pass the DEVM_IOREMAP_UC to __devm_ioremap(). [Test] Verified on Dell XPS 13 7390 2-in-1 [Regression Potential] Low, without this patch, the machine even can't boot. And the quirk only for specific machines, so the modification won't affect other machines. 1. https://bugzilla.kernel.org/show_bug.cgi?id=203485#c23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845436] Re: disco/linux-oracle: 5.0.0-1004.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 -- kernel-stable-master-bug: 1844362 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Promote to Proposed phase-changed: Friday, 27. September 2019 00:06 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait,signed:depwait replaces: bug 1844358 trackers: bionic/linux-oracle-edge: bug 1844355 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/1845436 Title: disco/linux-oracle: 5.0.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- kernel-stable-master-bug: 1844362 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Promote to Proposed phase-changed: Friday, 27. September 2019 00:06 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait,signed:depwait replaces: bug 1844358 trackers: bionic/linux-oracle-edge: bug 1844355 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844362] Re: disco/linux: 5.0.0-30.32 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Signoff phase-changed: Wednesday, 25. September 2019 11:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842561 trackers: bionic/linux-hwe: bug 1844360 bionic/linux-oem-osp1: bug 1844361 disco/linux-aws: bug 1844338 disco/linux-azure: bug 1844343 disco/linux-gcp: bug 1845128 disco/linux-kvm: bug 1844353 - disco/linux-oracle: bug 1844358, bug 1845436 + disco/linux-oracle: bug 1845436, bug 1844358 disco/linux-raspi2: bug 1844336 disco/linux-snapdragon: bug 1844359 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/1844362 Title: disco/linux: 5.0.0-30.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed 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: Signoff phase-changed: Wednesday, 25. September 2019 11:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842561 trackers: bionic/linux-hwe: bug 1844360 bionic/linux-oem-osp1: bug 1844361 disco/linux-aws: bug 1844338 disco/linux-azure: bug 1844343 disco/linux-gcp: bug 1845128 disco/linux-kvm: bug 1844353 disco/linux-oracle: bug 1845436, bug 1844358 disco/linux-raspi2: bug 1844336 disco/linux-snapdragon: bug 1844359 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844962] Re: apparent memory usage regression - not getting freed?
899fbde1464639e3d12eaffdad8481a59b367fcb is the first bad commit commit 899fbde1464639e3d12eaffdad8481a59b367fcb Author: Philip Yang Date: Thu Dec 13 15:35:28 2018 -0500 drm/amdgpu: replace get_user_pages with HMM mirror helpers Use HMM helper function hmm_vma_fault() to get physical pages backing userptr and start CPU page table update track of those pages. Then use hmm_vma_range_done() to check if those pages are updated before amdgpu_cs_submit for gfx or before user queues are resumed for kfd. If userptr pages are updated, for gfx, amdgpu_cs_ioctl will restart from scratch, for kfd, restore worker is rescheduled to retry. HMM simplify the CPU page table concurrent update check, so remove guptasklock, mmu_invalidations, last_set_pages fields from amdgpu_ttm_tt struct. HMM does not pin the page (increase page ref count), so remove related operations like release_pages(), put_page(), mark_page_dirty(). Signed-off-by: Philip Yang Reviewed-by: Felix Kuehling Reviewed-by: Christian König Signed-off-by: Alex Deucher :04 04 0c9f0e2e82e5e4d2d3a4c0daea22eb911244b771 fdcdc7c80f5383486962edf4561e205b55bd8c21 M drivers $ git bisect log # bad: [f74c2bb98776e2de508f4d607cd519873065118e] Linux 5.3-rc8 # good: [1c163f4c7b3f621efff9b28a47abb36f7378d783] Linux 5.0 git bisect start 'v5.3-rc8' 'v5.0' # good: [a2d635decbfa9c1e4ae15cb05b68b2559f7f827c] Merge tag 'drm-next-2019-05-09' of git://anongit.freedesktop.org/drm/drm git bisect good a2d635decbfa9c1e4ae15cb05b68b2559f7f827c # good: [a2d635decbfa9c1e4ae15cb05b68b2559f7f827c] Merge tag 'drm-next-2019-05-09' of git://anongit.freedesktop.org/drm/drm git bisect good a2d635decbfa9c1e4ae15cb05b68b2559f7f827c # good: [8f6ccf6159aed1f04c6d179f61f6fb2691261e84] Merge tag 'clone3-v5.3' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux git bisect good 8f6ccf6159aed1f04c6d179f61f6fb2691261e84 # good: [8f6ccf6159aed1f04c6d179f61f6fb2691261e84] Merge tag 'clone3-v5.3' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux git bisect good 8f6ccf6159aed1f04c6d179f61f6fb2691261e84 # bad: [be8454afc50f43016ca8b6130d9673bdd0bd56ec] Merge tag 'drm-next-2019-07-16' of git://anongit.freedesktop.org/drm/drm git bisect bad be8454afc50f43016ca8b6130d9673bdd0bd56ec # bad: [be8454afc50f43016ca8b6130d9673bdd0bd56ec] Merge tag 'drm-next-2019-07-16' of git://anongit.freedesktop.org/drm/drm git bisect bad be8454afc50f43016ca8b6130d9673bdd0bd56ec # good: [d72619706abc4aa7e540ea882dae883cee7cc3b3] Merge tag 'tty-5.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty git bisect good d72619706abc4aa7e540ea882dae883cee7cc3b3 # bad: [83145f110eb2ada9d54fcbcf416c02de126381c1] drm/amdgpu: don't invalidate caches in RELEASE_MEM, only do the writeback git bisect bad 83145f110eb2ada9d54fcbcf416c02de126381c1 # bad: [b239c01727459ba08c44b79e6225d3c58723f282] drm/amdgpu: add mcbp driver parameter git bisect bad b239c01727459ba08c44b79e6225d3c58723f282 # good: [e1dc68a4b149d47536cd001d0d0abadbb62d37bd] drm: atmel-hlcdc: avoid initializing cfg with zero git bisect good e1dc68a4b149d47536cd001d0d0abadbb62d37bd # bad: [c53e4db71276bf257b09010935a04bdafddd458e] drm/amdgpu: cancel late_init_work before gpu reset git bisect bad c53e4db71276bf257b09010935a04bdafddd458e # good: [2da4605dce38b84cd2e5b86686f43adae1b2cacb] drm/amd/display: Use DCN functions instead of DCE git bisect good 2da4605dce38b84cd2e5b86686f43adae1b2cacb # bad: [1c1e53f7f2ce191e6787d3d0648fe8ce7088ceaa] drm/amd/doc: Add XGMI sysfs documentation git bisect bad 1c1e53f7f2ce191e6787d3d0648fe8ce7088ceaa # good: [89cd9d23e9a74d94f0db5bbbaf2ef1f6ede36ae5] drm/amdkfd: avoid HMM change cause circular lock git bisect good 89cd9d23e9a74d94f0db5bbbaf2ef1f6ede36ae5 # bad: [0803e7a9e850f9d6397c594d6c6deac9b2b6d696] drm/amdkfd: Allocate hiq and sdma mqd from mqd trunk git bisect bad 0803e7a9e850f9d6397c594d6c6deac9b2b6d696 # bad: [972fcdb52fe865a2f639e3200b97e648f34a0f41] drm/amdkfd: Introduce asic-specific mqd_manager_init function git bisect bad 972fcdb52fe865a2f639e3200b97e648f34a0f41 # bad: [6c55d6e90e68a4789cbd72a0287026d4dfb4a9f9] drm/amdkfd: support concurrent userptr update for HMM git bisect bad 6c55d6e90e68a4789cbd72a0287026d4dfb4a9f9 # bad: [ad595b8634f36f04bf69bef4eff854091d94f8b3] drm/amdgpu: fix HMM config dependency issue git bisect bad ad595b8634f36f04bf69bef4eff854091d94f8b3 # bad: [899fbde1464639e3d12eaffdad8481a59b367fcb] drm/amdgpu: replace get_user_pages with HMM mirror helpers git bisect bad 899fbde1464639e3d12eaffdad8481a59b367fcb # first bad commit: [899fbde1464639e3d12eaffdad8481a59b367fcb] drm/amdgpu: replace get_user_pages with HMM mirror helpers -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844962 Title: apparent memory usage regression - not getting freed?
[Kernel-packages] [Bug 1845586] 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 1845586 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/1845586 Title: System can NOT be installed only if add a kernel parameter nomodeset on Eoan 19.10 Status in linux package in Ubuntu: Incomplete Bug description: [Summary] System can NOT be installed only if add a kernel parameter nomodeset in booting grub. [Steps to reproduce] 1. Make a usb stick. 2. Boot from the usb stick to install system. 3. Check the result. 4. Add a parameter nomodeset in boot grub if step 3 is failed. [Expected result] System can be install without any parameter. [Actual result] Need a kernel parameter system can be installed. [Failure rate] 100% [Additional information] bios-version: N2EET41W (1.23 ) GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c8c (rev a1) system-product-name: 20MGZ484US system-manufacturer: LENOVO kernel-version: 5.3.0-10-generic CPU: Intel(R) Core(TM) i5-8400H CPU @ 2.50GHz (8x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845586] [NEW] System can NOT be installed only if add a kernel parameter nomodeset on Eoan 19.10
Public bug reported: [Summary] System can NOT be installed only if add a kernel parameter nomodeset in booting grub. [Steps to reproduce] 1. Make a usb stick. 2. Boot from the usb stick to install system. 3. Check the result. 4. Add a parameter nomodeset in boot grub if step 3 is failed. [Expected result] System can be install without any parameter. [Actual result] Need a kernel parameter system can be installed. [Failure rate] 100% [Additional information] bios-version: N2EET41W (1.23 ) GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c8c (rev a1) system-product-name: 20MGZ484US system-manufacturer: LENOVO kernel-version: 5.3.0-10-generic CPU: Intel(R) Core(TM) i5-8400H CPU @ 2.50GHz (8x) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: ce-qa-concern eoan ** Attachment added: "u-ThinkPad-X1-Extreme-sysreport.tar.gz" https://bugs.launchpad.net/bugs/1845586/+attachment/5291634/+files/u-ThinkPad-X1-Extreme-sysreport.tar.gz ** Summary changed: - System can NOT be installed only if add a kernel parameter nomodeset + System can NOT be installed only if add a kernel parameter nomodeset on Eoan 19.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845586 Title: System can NOT be installed only if add a kernel parameter nomodeset on Eoan 19.10 Status in linux package in Ubuntu: New Bug description: [Summary] System can NOT be installed only if add a kernel parameter nomodeset in booting grub. [Steps to reproduce] 1. Make a usb stick. 2. Boot from the usb stick to install system. 3. Check the result. 4. Add a parameter nomodeset in boot grub if step 3 is failed. [Expected result] System can be install without any parameter. [Actual result] Need a kernel parameter system can be installed. [Failure rate] 100% [Additional information] bios-version: N2EET41W (1.23 ) GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c8c (rev a1) system-product-name: 20MGZ484US system-manufacturer: LENOVO kernel-version: 5.3.0-10-generic CPU: Intel(R) Core(TM) i5-8400H CPU @ 2.50GHz (8x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730924]
Hi, this still seems to be an issue on a lot of Surface devices and I'm not sure if it was ever solved. I own a Surface Pro 2017 and I'm seeing the same issues as in #Comment74, the issue happens randomly after some time (sometimes hours, sometimes minutes) and is easily reproducible by suspending and resuming multiple times. As long as you're not suspending the device, a workaround is to manually set PCIe ASPM to L0-only for the wifi card. I'm running a 5.3 kernel right now, are there any patches I could try? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845584] Re: intel-lpss driver conflicts with write-combining MTRR region
** Description changed: [Impact] The memory region intel-lpss-pci uses has been declared as write-combining [0.001728] 5 base 40 mask 60 write-combining This leads to the system hangs up during booting up. This is a BIOS issue, but there are some platforms on the market and users are struggling on booting up the machines. So, we may have to fix this in the kernel. [Fix] Tuowen Zhao(ztuo...@gmail.com)[1] provides a diff patch for intel-lpss driver to claim to use un-catchable memory while calling - __devm_ioremap(), and it works well. + __devm_ioremap(), and it works well. But it didn't be accepted by + maintainer yet. To avoid the potential impact on other machines, I add a quirk to list the machines which has the write-combining area in MTRR which overlaps with the address that intel-lpss uses, only the machines in the list pass the DEVM_IOREMAP_UC to __devm_ioremap(). [Test] Verified on Dell XPS 13 7390 2-in-1 [Regression Potential] Low, without this patch, the machine even can't boot. And the quirk only for specific machines, so the modification won't affect other machines. 1. https://bugzilla.kernel.org/show_bug.cgi?id=203485#c23 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845584 Title: intel-lpss driver conflicts with write-combining MTRR region Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in FF-Series: In Progress Bug description: [Impact] The memory region intel-lpss-pci uses has been declared as write-combining [0.001728] 5 base 40 mask 60 write-combining This leads to the system hangs up during booting up. This is a BIOS issue, but there are some platforms on the market and users are struggling on booting up the machines. So, we may have to fix this in the kernel. [Fix] Tuowen Zhao(ztuo...@gmail.com)[1] provides a diff patch for intel-lpss driver to claim to use un-catchable memory while calling __devm_ioremap(), and it works well. But it didn't be accepted by maintainer yet. To avoid the potential impact on other machines, I add a quirk to list the machines which has the write-combining area in MTRR which overlaps with the address that intel-lpss uses, only the machines in the list pass the DEVM_IOREMAP_UC to __devm_ioremap(). [Test] Verified on Dell XPS 13 7390 2-in-1 [Regression Potential] Low, without this patch, the machine even can't boot. And the quirk only for specific machines, so the modification won't affect other machines. 1. https://bugzilla.kernel.org/show_bug.cgi?id=203485#c23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845584] Re: intel-lpss driver conflicts with write-combining MTRR region
** Patch added: "0001-mfd-intel-lpss-add-quirk-for-Dell-XPS-13-7390-2-in-1.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845584/+attachment/5291627/+files/0001-mfd-intel-lpss-add-quirk-for-Dell-XPS-13-7390-2-in-1.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/1845584 Title: intel-lpss driver conflicts with write-combining MTRR region Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in FF-Series: In Progress Bug description: [Impact] The memory region intel-lpss-pci uses has been declared as write-combining [0.001728] 5 base 40 mask 60 write-combining This leads to the system hangs up during booting up. This is a BIOS issue, but there are some platforms on the market and users are struggling on booting up the machines. So, we may have to fix this in the kernel. [Fix] Tuowen Zhao(ztuo...@gmail.com)[1] provides a diff patch for intel-lpss driver to claim to use un-catchable memory while calling __devm_ioremap(), and it works well. To avoid the potential impact on other machines, I add a quirk to list the machines which has the write-combining area in MTRR which overlaps with the address that intel-lpss uses, only the machines in the list pass the DEVM_IOREMAP_UC to __devm_ioremap(). [Test] Verified on Dell XPS 13 7390 2-in-1 [Regression Potential] Low, without this patch, the machine even can't boot. And the quirk only for specific machines, so the modification won't affect other machines. 1. https://bugzilla.kernel.org/show_bug.cgi?id=203485#c23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845584] [NEW] intel-lpss driver conflicts with write-combining MTRR region
Public bug reported: [Impact] The memory region intel-lpss-pci uses has been declared as write-combining [0.001728] 5 base 40 mask 60 write-combining This leads to the system hangs up during booting up. This is a BIOS issue, but there are some platforms on the market and users are struggling on booting up the machines. So, we may have to fix this in the kernel. [Fix] Tuowen Zhao(ztuo...@gmail.com)[1] provides a diff patch for intel-lpss driver to claim to use un-catchable memory while calling __devm_ioremap(), and it works well. To avoid the potential impact on other machines, I add a quirk to list the machines which has the write-combining area in MTRR which overlaps with the address that intel-lpss uses, only the machines in the list pass the DEVM_IOREMAP_UC to __devm_ioremap(). [Test] Verified on Dell XPS 13 7390 2-in-1 [Regression Potential] Low, without this patch, the machine even can't boot. And the quirk only for specific machines, so the modification won't affect other machines. 1. https://bugzilla.kernel.org/show_bug.cgi?id=203485#c23 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Ff-series) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux (Ubuntu Ff-series) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Ff-series) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Ff-series) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845584 Title: intel-lpss driver conflicts with write-combining MTRR region Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in FF-Series: In Progress Bug description: [Impact] The memory region intel-lpss-pci uses has been declared as write-combining [0.001728] 5 base 40 mask 60 write-combining This leads to the system hangs up during booting up. This is a BIOS issue, but there are some platforms on the market and users are struggling on booting up the machines. So, we may have to fix this in the kernel. [Fix] Tuowen Zhao(ztuo...@gmail.com)[1] provides a diff patch for intel-lpss driver to claim to use un-catchable memory while calling __devm_ioremap(), and it works well. To avoid the potential impact on other machines, I add a quirk to list the machines which has the write-combining area in MTRR which overlaps with the address that intel-lpss uses, only the machines in the list pass the DEVM_IOREMAP_UC to __devm_ioremap(). [Test] Verified on Dell XPS 13 7390 2-in-1 [Regression Potential] Low, without this patch, the machine even can't boot. And the quirk only for specific machines, so the modification won't affect other machines. 1. https://bugzilla.kernel.org/show_bug.cgi?id=203485#c23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845467] Re: Force version override by file in /usr/share/dkms/modules_to_force_install
*** This bug is a duplicate of bug 1838921 ***
https://bugs.launchpad.net/bugs/1838921
** This bug has been marked a duplicate of bug 1838921
ability to install dkms without version checking and retire it when kernel
fixed issue
--
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/1845467
Title:
Force version override by file in
/usr/share/dkms/modules_to_force_install
Status in OEM Priority Project:
Confirmed
Status in OEM Priority Project bionic series:
New
Status in dkms package in Ubuntu:
New
Bug description:
refer to https://github.com/dell/dkms/pull/98
And this patch will override
https://bugs.launchpad.net/oem-priority/+bug/1838921
[Impact]
to have a way for this case
"user need to force install the dkms, but also would like to retire that dkms
once kernel fixes the issue."
- upstream patch : https://github.com/dell/dkms/pull/98
[Test case]
1. install the dkms package which already patched
2. install a DKMS which has file content "{dkms name}_version-override" under
/usr/share/dkms/modules_to_force_install/
- the installation should ignore module version checking.
3. update that installed DKMS to a new one which added OBSOLETE_BY in
dkms.conf
- on the kernel which version lower than OBSOLETE_BY, the dkms should be
installed.
- on the kernel which version higher than OBSOLETE_BY, the dkms should NOT
be installed.
[Regression potential]
medium as it touched the version sanity. This change already there in
upstream.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1845467/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844186] Re: [regression] NoNewPrivileges incompatible with Apparmor
okay, thanks for testing. I'll submit the patch for 4.4 and 4.15 kernels and look into why the 5.0 kernel is blocking policy loads -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844186 Title: [regression] NoNewPrivileges incompatible with Apparmor Status in linux package in Ubuntu: Confirmed Bug description: Description: Host: Bionic 64 bit with GA kernel (4.15) Container: Bionic 64 bit The container runs a binary (/usr/sbin/nsd) locked by an Apparmor profile. The systemd service is configured with NoNewPrivileges=yes. # systemctl show nsd | grep ^NoNew NoNewPrivileges=yes This setup worked fine with 4.15.0-58-generic and before but stopped working with the 4.15.0-60-generic update. When running the bogus kernel, starting the nsd service fails and the following is logged in the host's dmesg: audit: type=1400 audit(1568387834.381:73): apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="lxd-ns0_" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="lxd-ns0_//&:lxd-ns0_:/usr/sbin/nsd" audit: type=1400 audit(1568387834.381:74): apparmor="DENIED" operation="exec" info="no new privs" error=-1 namespace="root//lxd-ns0_" profile="unconfined" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="/usr/sbin/nsd" Disabling the Apparmor profile OR setting NoNewPrivileges=no in the container makes it work again. I check with a couple of kernels: 4.15.0-52-generic works 4.15.0-58-generic works 4.15.0-60-generic is broken The 5.0 HWE kernel has always been broken it seems: 5.0.0-15-generic is broken 5.0.0-17-generic is broken 5.0.0-20-generic is broken 5.0.0-23-generic is broken 5.0.0-25-generic is broken 5.0.0-27-generic is broken I have another similar setup but using Xenial host/container and it broke in a similar fashion where 4.4.0-159-generic works but 4.4.0-161-generic is broken. Additional information: # lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 # apt-cache policy nsd nsd: Installed: 4.1.26-1ubuntu0.18.04.1~ppa2 Candidate: 4.1.26-1ubuntu0.18.04.1~ppa2 Version table: *** 4.1.26-1ubuntu0.18.04.1~ppa2 500 500 http://ppa.launchpad.net/sdeziel.info/infra/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 4.1.17-1build1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages nsd comes from a custom backport this should be irrelevant. nsd's custom Apparmor profile: https://paste.ubuntu.com/p/BB3ZYzH8WQ/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 16 18:02 seq crw-rw 1 root audio 116, 33 Sep 16 18:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 16 18:14:02 2019 InstallationDate: Installed on 2019-08-22 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. Inspiron 530s PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=7c11931f-ee1e-4d07-bc03-d167b9c39ef0 ro apt-setup/restricted=false apt-setup/multiverse=false kaslr nmi_watchdog=0 nr_cpus=2 pti=on vsyscall=none RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.18 dmi.board.name: 0RY007 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.18:bd02/24/2009:svnDellInc.:pnInspiron530s:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name:
[Kernel-packages] [Bug 1844355] Re: bionic/linux-oracle-edge: 5.0.0-1004.5~18.04.1 -proposed tracker
** Summary changed: - bionic/linux-oracle-edge: -proposed tracker + bionic/linux-oracle-edge: 5.0.0-1004.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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844355 Title: bionic/linux-oracle-edge: 5.0.0-1004.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-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1845436 packages: main: linux-oracle-edge meta: linux-meta-oracle-edge signed: linux-signed-oracle-edge phase: Ready for Packaging phase-changed: Friday, 27. September 2019 00:17 UTC reason: prepare-package: Pending -- version not specified replaces: bug 1842843 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844680] Re: Thunderbolt support for ICL
The test kernel is here, including lpss fix and thunderbolt patches https://people.canonical.com/~acelan/bugs/big_boss -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844680 Title: Thunderbolt support for ICL Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: In Progress Bug description: v5.4 has commits to fix Thunderbolt support for ICL ce19f91eae43e39 thunderbolt: Correct path indices for PCIe tunnel f437c24bf694b02 thunderbolt: Move NVM upgrade support flag to struct icm 943795219d3cb9f thunderbolt: Use 32-bit writes when writing ring producer/consumer d94dcbb10183f3b thunderbolt: Do not fail adding switch if some port is not implemented 58f414fa435cf72 thunderbolt: Hide switch attributes that are not set 3f415e5ee18b009 thunderbolt: Expose active parts of NVM even if upgrade is not supported 3cdb9446a117d5d thunderbolt: Add support for Intel Ice Lake dfda204198848b4 ACPI / property: Add two new Thunderbolt property GUIDs to the list To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1844680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844383] Re: bionic/linux-kvm: 4.15.0-1047.47 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1844403 packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Tuesday, 24. September 2019 14:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842810 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1844383 Title: bionic/linux-kvm: 4.15.0-1047.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1844403 packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Tuesday, 24. September 2019 14:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842810 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844383] Re: bionic/linux-kvm: 4.15.0-1047.47 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1844383 Title: bionic/linux-kvm: 4.15.0-1047.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1844403 packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Tuesday, 24. September 2019 14:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842810 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844386] Re: bionic/linux-ibm-gt: 4.15.0-1038.40 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1844403 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Ready for Testing phase-changed: Monday, 23. September 2019 11:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844386 Title: bionic/linux-ibm-gt: 4.15.0-1038.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1844403 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Ready for Testing phase-changed: Monday, 23. September 2019 11:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844386] Re: bionic/linux-ibm-gt: 4.15.0-1038.40 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844386 Title: bionic/linux-ibm-gt: 4.15.0-1038.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1844403 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Ready for Testing phase-changed: Monday, 23. September 2019 11:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844355] Re: bionic/linux-oracle-edge: -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: 1845436 packages: main: linux-oracle-edge meta: linux-meta-oracle-edge signed: linux-signed-oracle-edge - phase: Holding before Packaging - phase-changed: Thursday, 26. September 2019 06:50 UTC + phase: Ready for Packaging + phase-changed: Friday, 27. September 2019 00:17 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified replaces: bug 1842843 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/1844355 Title: bionic/linux-oracle-edge: -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-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: 1845436 packages: main: linux-oracle-edge meta: linux-meta-oracle-edge signed: linux-signed-oracle-edge phase: Ready for Packaging phase-changed: Friday, 27. September 2019 00:17 UTC reason: prepare-package: Pending -- version not specified replaces: bug 1842843 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844355/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845436] Re: disco/linux-oracle: 5.0.0-1004.5 -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-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** 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: 1844362 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Ready for Packaging - phase-changed: Thursday, 26. September 2019 06:51 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 27. September 2019 00:06 UTC reason: - prepare-package: Pending -- version not specified + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait replaces: bug 1844358 trackers: bionic/linux-oracle-edge: bug 1844355 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/1845436 Title: disco/linux-oracle: 5.0.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- kernel-stable-master-bug: 1844362 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Promote to Proposed phase-changed: Friday, 27. September 2019 00:06 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait replaces: bug 1844358 trackers: bionic/linux-oracle-edge: bug 1844355 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)
** Changed in: oem-priority Status: Fix Committed => Fix Released -- 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/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Released Status in linux-firmware source package in Disco: Fix Released Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844362] Re: disco/linux: 5.0.0-30.32 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Signoff phase-changed: Wednesday, 25. September 2019 11:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842561 trackers: bionic/linux-hwe: bug 1844360 bionic/linux-oem-osp1: bug 1844361 disco/linux-aws: bug 1844338 disco/linux-azure: bug 1844343 disco/linux-gcp: bug 1845128 disco/linux-kvm: bug 1844353 - disco/linux-oracle: bug 1845436, bug 1844358 + disco/linux-oracle: bug 1844358, bug 1845436 disco/linux-raspi2: bug 1844336 disco/linux-snapdragon: bug 1844359 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/1844362 Title: disco/linux: 5.0.0-30.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed 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: Signoff phase-changed: Wednesday, 25. September 2019 11:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842561 trackers: bionic/linux-hwe: bug 1844360 bionic/linux-oem-osp1: bug 1844361 disco/linux-aws: bug 1844338 disco/linux-azure: bug 1844343 disco/linux-gcp: bug 1845128 disco/linux-kvm: bug 1844353 disco/linux-oracle: bug 1844358, bug 1845436 disco/linux-raspi2: bug 1844336 disco/linux-snapdragon: bug 1844359 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845572] [NEW] udevadm trigger will fail when trying to add /sys/devices/vio/
Public bug reported: [Impact] This will cause the installer to exit early, causing a kernel panic before any prompt to the user. This is restricted to some Power systems. [Test case] A build vmlinux was used to boot the installer, and a prompt was available. 'add' was written to /sys/devices/vio/uevent was written to, and no error was found. 'add' was written to /sys/devices/vio/*/uevent, and modalias information was found when 'udevadm monitor -p' was run in the background. [Regression potential] Events may be missing and coldplug/hotplug of vio devices may fail. That was tested in the test case and not found to be the case. ** Affects: linux (Ubuntu) Importance: Critical Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845572 Title: udevadm trigger will fail when trying to add /sys/devices/vio/ Status in linux package in Ubuntu: In Progress Bug description: [Impact] This will cause the installer to exit early, causing a kernel panic before any prompt to the user. This is restricted to some Power systems. [Test case] A build vmlinux was used to boot the installer, and a prompt was available. 'add' was written to /sys/devices/vio/uevent was written to, and no error was found. 'add' was written to /sys/devices/vio/*/uevent, and modalias information was found when 'udevadm monitor -p' was run in the background. [Regression potential] Events may be missing and coldplug/hotplug of vio devices may fail. That was tested in the test case and not found to be the case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845436] Re: disco/linux-oracle: 5.0.0-1004.5 -proposed tracker
** Summary changed: - disco/linux-oracle: -proposed tracker + disco/linux-oracle: 5.0.0-1004.5 -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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) -- 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/1845436 Title: disco/linux-oracle: 5.0.0-1004.5 -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-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- kernel-stable-master-bug: 1844362 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Ready for Packaging phase-changed: Thursday, 26. September 2019 06:51 UTC reason: prepare-package: Pending -- version not specified replaces: bug 1844358 trackers: bionic/linux-oracle-edge: bug 1844355 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844186] Re: [regression] NoNewPrivileges incompatible with Apparmor
Tests results on Xenial: Xenial/4.4: # uname -a | sed 's/lxd01\.[^ ]\+/lxd01/' Linux lxd01 4.4.0-164-generic #192+lp1844186 SMP Thu Sep 26 15:17:42 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux *result*: works Xenial/4.15: # uname -a | sed 's/lxd01\.[^ ]\+/lxd01/' Linux lxd01 4.15.0-64-generic #73+lp1844186 SMP Thu Sep 26 15:17:27 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux *result*: works -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844186 Title: [regression] NoNewPrivileges incompatible with Apparmor Status in linux package in Ubuntu: Confirmed Bug description: Description: Host: Bionic 64 bit with GA kernel (4.15) Container: Bionic 64 bit The container runs a binary (/usr/sbin/nsd) locked by an Apparmor profile. The systemd service is configured with NoNewPrivileges=yes. # systemctl show nsd | grep ^NoNew NoNewPrivileges=yes This setup worked fine with 4.15.0-58-generic and before but stopped working with the 4.15.0-60-generic update. When running the bogus kernel, starting the nsd service fails and the following is logged in the host's dmesg: audit: type=1400 audit(1568387834.381:73): apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="lxd-ns0_" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="lxd-ns0_//&:lxd-ns0_:/usr/sbin/nsd" audit: type=1400 audit(1568387834.381:74): apparmor="DENIED" operation="exec" info="no new privs" error=-1 namespace="root//lxd-ns0_" profile="unconfined" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="/usr/sbin/nsd" Disabling the Apparmor profile OR setting NoNewPrivileges=no in the container makes it work again. I check with a couple of kernels: 4.15.0-52-generic works 4.15.0-58-generic works 4.15.0-60-generic is broken The 5.0 HWE kernel has always been broken it seems: 5.0.0-15-generic is broken 5.0.0-17-generic is broken 5.0.0-20-generic is broken 5.0.0-23-generic is broken 5.0.0-25-generic is broken 5.0.0-27-generic is broken I have another similar setup but using Xenial host/container and it broke in a similar fashion where 4.4.0-159-generic works but 4.4.0-161-generic is broken. Additional information: # lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 # apt-cache policy nsd nsd: Installed: 4.1.26-1ubuntu0.18.04.1~ppa2 Candidate: 4.1.26-1ubuntu0.18.04.1~ppa2 Version table: *** 4.1.26-1ubuntu0.18.04.1~ppa2 500 500 http://ppa.launchpad.net/sdeziel.info/infra/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 4.1.17-1build1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages nsd comes from a custom backport this should be irrelevant. nsd's custom Apparmor profile: https://paste.ubuntu.com/p/BB3ZYzH8WQ/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 16 18:02 seq crw-rw 1 root audio 116, 33 Sep 16 18:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 16 18:14:02 2019 InstallationDate: Installed on 2019-08-22 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. Inspiron 530s PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=7c11931f-ee1e-4d07-bc03-d167b9c39ef0 ro apt-setup/restricted=false apt-setup/multiverse=false kaslr nmi_watchdog=0 nr_cpus=2 pti=on vsyscall=none RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.18 dmi.board.name: 0RY007
[Kernel-packages] [Bug 1845454] Re: Kernel panic with 19.10 beta image
Provided this in irc, but posting here also. Instructions for installing
a MOK that you can use to sign kernels are found here:
https://ubuntu.com/blog/how-to-sign-things-for-secure-boot
Note the comment under "Enrolling the key" about omitting OID
1.3.6.1.4.1.2312.16.1.2 if you want to use the key to sign kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845454
Title:
Kernel panic with 19.10 beta image
Status in linux package in Ubuntu:
Incomplete
Bug description:
Image: http://cdimage.ubuntu.com/daily-live/20190926/eoan-desktop-amd64.iso
Device: Dell XPS 13 7390 (201908-27305)
When trying to start the live session ("try Ubuntu") or trying to
install the ISO ("install Ubuntu"), the boot process stops within 1
second with a kernel panic (see attached screenshot).
The system could boot with a previous version of Eoan image:
2019-09-09 09:11 (kernel 5.3.0-10)
Workaround: disable TPM2 in the BIOS.
/!\ Please note: the information below (and the attached file
ProcCpuinfoMinimal.txt) come from a 18.04 live session, since I cannot boot
anything with 19.10 beta image.
==
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: syslinux 3:6.03+dfsg1-2
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 07:41:16 2019
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
mtools 4.0.18-2ubuntu1
syslinux-common 3:6.03+dfsg1-2
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: syslinux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843960] Re: cherrypick has_sipl fix
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1843960 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1843960 Title: cherrypick has_sipl fix Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: cherrypick has_sipl fix from the s390 maintainer tree https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/patch/?id=4df9a82549cfed5b52da21e7d007b79b2ea1769a Otherwise, has_secure sysfs attribute is never correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1843960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845454] Re: Kernel panic with 19.10 beta image
This is the same bug as bug 1844101 I think? If it is, it doesn't
reproduce with secure boot off and we'll need a signed kernel to test.
I'm happy to enrol whatever key in my firmware to test a self-signed
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/1845454
Title:
Kernel panic with 19.10 beta image
Status in linux package in Ubuntu:
Incomplete
Bug description:
Image: http://cdimage.ubuntu.com/daily-live/20190926/eoan-desktop-amd64.iso
Device: Dell XPS 13 7390 (201908-27305)
When trying to start the live session ("try Ubuntu") or trying to
install the ISO ("install Ubuntu"), the boot process stops within 1
second with a kernel panic (see attached screenshot).
The system could boot with a previous version of Eoan image:
2019-09-09 09:11 (kernel 5.3.0-10)
Workaround: disable TPM2 in the BIOS.
/!\ Please note: the information below (and the attached file
ProcCpuinfoMinimal.txt) come from a 18.04 live session, since I cannot boot
anything with 19.10 beta image.
==
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: syslinux 3:6.03+dfsg1-2
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 07:41:16 2019
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
mtools 4.0.18-2ubuntu1
syslinux-common 3:6.03+dfsg1-2
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: syslinux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844144] Re: eoan/linux: 5.3.0-12.13 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-eoan ** Tags removed: 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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Testing - phase-changed: Thursday, 19. September 2019 09:56 UTC + phase: Ready for Promote to Release + phase-changed: Thursday, 26. September 2019 21:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-release: Pending -- ready to copy trackers: bionic/linux-hwe-edge: bug 1844142 eoan/linux-aws: bug 1844138 eoan/linux-azure: bug 1844139 eoan/linux-gcp: bug 1844140 eoan/linux-kvm: bug 1844141 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/1844144 Title: eoan/linux: 5.3.0-12.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux 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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Release phase-changed: Thursday, 26. September 2019 21:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy trackers: bionic/linux-hwe-edge: bug 1844142 eoan/linux-aws: bug 1844138 eoan/linux-azure: bug 1844139 eoan/linux-gcp: bug 1844140 eoan/linux-kvm: bug 1844141 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844144] Re: eoan/linux: 5.3.0-12.13 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844144 Title: eoan/linux: 5.3.0-12.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux 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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Release phase-changed: Thursday, 26. September 2019 21:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy trackers: bionic/linux-hwe-edge: bug 1844142 eoan/linux-aws: bug 1844138 eoan/linux-azure: bug 1844139 eoan/linux-gcp: bug 1844140 eoan/linux-kvm: bug 1844141 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB
** Changed in: linux (Ubuntu) Status: Expired => 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/1788098 Title: Avoid migration issues with aligned 2MB THB Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Bug description: FYI: This blocks bug 1781526 - once this one here is resolved we can go on with SRU considerations for 1781526 --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774994] Re: Laptop wakes up immediately after suspend or hibernation
I have a similar issue, maybe the same. But I found out I can suspend my notebook by disabling bluetooth. If bluetooth is enabled, trying to suspend will immediately (2 - 3 seconds) make the notebook wake up again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774994 Title: Laptop wakes up immediately after suspend or hibernation Status in linux package in Ubuntu: Expired Bug description: After going into suspend (via command line or lid close), the MacBook Pro (early 2015) wakes up immediately again. Same for hibernation. Running Ubuntu 18.04. extract from dmesg for a lid-close -> suspend -> wake-up -> lid-open cycle: [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 2018 (Ubuntu 4.15.0-22.24-generic 4.15.17) [ ... ] [ 778.968982] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23 [ 783.011399] PM: suspend entry (deep) [ 783.011400] PM: Syncing filesystems ... done. [ 783.028538] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 783.030844] OOM killer disabled. [ 783.030844] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 783.032193] Suspending console(s) (use no_console_suspend to debug) [ 783.049960] sd 1:0:0:0: [sda] Synchronizing SCSI cache [ 783.054107] sd 1:0:0:0: [sda] Stopping disk [ 783.146124] thunderbolt :07:00.0: suspending... [ 783.146685] thunderbolt :07:00.0: suspend finished [ 783.146689] thunderbolt :07:00.0: stopping RX ring 0 [ 783.146698] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1) [ 783.146710] thunderbolt :07:00.0: stopping TX ring 0 [ 783.146718] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0) [ 783.146725] thunderbolt :07:00.0: control channel stopped [ 783.246464] ACPI: Preparing to enter system sleep state S3 [ 783.418015] ACPI: EC: event blocked [ 783.418016] ACPI: EC: EC stopped [ 783.418018] PM: Saving platform NVS memory [ 783.418027] Disabling non-boot CPUs ... [ 783.434574] IRQ 65: no longer affine to CPU1 [ 783.435629] smpboot: CPU 1 is now offline [ 783.454574] IRQ 66: no longer affine to CPU2 [ 783.456378] smpboot: CPU 2 is now offline [ 783.478405] IRQ 21: no longer affine to CPU3 [ 783.478414] IRQ 43: no longer affine to CPU3 [ 783.478435] IRQ 71: no longer affine to CPU3 [ 783.479449] smpboot: CPU 3 is now offline [ 783.481656] ACPI: Low-level resume complete [ 783.481733] ACPI: EC: EC started [ 783.481734] PM: Restoring platform NVS memory [ 783.482160] Enabling non-boot CPUs ... [ 783.482240] x86: Booting SMP configuration: [ 783.482241] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 783.558589] cache: parent cpu1 should not be sleeping [ 783.687159] CPU1 is up [ 783.687212] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 783.687812] cache: parent cpu2 should not be sleeping [ 783.688001] CPU2 is up [ 783.688028] smpboot: Booting Node 0 Processor 3 APIC 0x3 [ 783.783709] cache: parent cpu3 should not be sleeping [ 783.978233] CPU3 is up [ 783.982020] ACPI: Waking up from system sleep state S3 [ 784.093246] pcieport :06:03.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093249] pcieport :06:04.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093362] pcieport :06:06.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.093475] pcieport :06:05.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [ 784.112655] thunderbolt :07:00.0: control channel starting... [ 784.112660] thunderbolt :07:00.0: starting TX ring 0 [ 784.112673] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) [ 784.112677] thunderbolt :07:00.0: starting RX ring 0 [ 784.112689] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) [ 784.112696] thunderbolt :07:00.0: resuming... [ 784.112699] thunderbolt :07:00.0: resetting switch at 0 [ 784.113249] thunderbolt :07:00.0: 0: resuming switch [ 784.144609] thunderbolt :07:00.0: resume finished [ 784.213878] thunderbolt :07:00.0: resetting error on 0:b. [ 784.213897] thunderbolt :07:00.0: 0:b: hotplug: scanning [ 784.213901] thunderbolt :07:00.0: 0:b: hotplug: no switch found [ 784.213984] thunderbolt :07:00.0: resetting error on 0:c. [ 784.213995] thunderbolt :07:00.0: 0:c: hotplug: scanning [ 784.213999] thunderbolt :07:00.0: 0:c: hotplug: no switch found [ 785.225640] ACPI: EC: event unblocked [ 785.226264] brcmfmac: brcmf_fil_cmd_data: bus is down. we have
[Kernel-packages] [Bug 1836635] Re: Bionic: support for Solarflare X2542 network adapter (sfc driver)
Verification successful with netboot image from bionic-proposed:
http://archive.ubuntu.com/ubuntu/dists/bionic-
proposed/main/installer-$ARCH/20101020ubuntu543.11/
Same testing as done on comment #8:
I have tested the installer with regular/lvm disk partition layouts
on amd64/i386/arm64/ppc64el/s390x on virtual machines with QEMU and
on amd64 bare metal machine.
The netboot installer boots the 4.15.0-62 kernel, finishes correctly,
and the installed system w/ the 4.15.0-64 kernel (from bionic-updates)
boots correctly.
The copy of the installer log in it (/var/log/installer/syslog)
shows no weird kernel messages at all, all good.
** 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/1836635
Title:
Bionic: support for Solarflare X2542 network adapter (sfc driver)
Status in debian-installer package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in debian-installer source package in Bionic:
Fix Committed
Status in linux source package in Bionic:
Fix Released
Status in debian-installer source package in Cosmic:
Invalid
Status in linux source package in Cosmic:
Invalid
Status in debian-installer source package in Disco:
Invalid
Status in linux source package in Disco:
Invalid
Status in debian-installer source package in Eoan:
Invalid
Status in linux source package in Eoan:
Invalid
Bug description:
[Impact]
* Support for Solarflare X2542 network adapter
(Medford2 / SFC9250) in the Bionic sfc driver.
* This network adapter is present on recent hardware,
at least HP 2019 and Dell PowerEdge R740xd systems.
* On recent-hardware deployments that would rather use
the Bionic LTS / GA supported kernel and cannot move
to HWE kernels this adapter is non functional at all.
[Test Case]
* The X2542 adapter has been exercised with iperf3 and nc
across 2 hosts on 25G link speed w/ MTUs 1400/1500/9000
on both directions, for 1 week.
Its performance is on par with the Cosmic 4.18 kernel
(which contains all these patches) and the out-of-tree
driver from the vendor.
* The 7000 series adapter (for regression testing an old model,
supported previously) has been exercised with iperf and netperf
(TCP_STREAM, UDP_STREAM, TCP_RR, UDP_RR, and TCP_CRR) in one
host (client/server in different adapter ports isolated with
network namespaces, so traffic goes through the network switch),
on 10G link speed on MTUs 1500/9000, for 1 weekend.
No regressions observed between the original and test kernels.
[Regression Potential]
* The patchset touches a lot of the sfc driver, so the potential
for regression definitely exists. Thus, a lot of consideration
and testing happened:
* It has been tested on other adapter which uses the old code,
and no regressions were found so far (see 7000 series above).
* The patchset is exclusively cherry-picks, no single backport.
* The patchset essentially moves the Bionic driver up in the
upstream 'git log --oneline -- drivers/net/ethernet/sfc/':
- since commit d4a7a8893d4c ("sfc: pass valid pointers from
efx_enqueue_unwind")
- until commit 7f61e6c6279b ("sfc: support FEC configuration through
ethtool")
- except for 2 commits (not needed / unrelated)
- commit 42356d9a137b ("sfc: support RSS spreading of ethtool ntuple
filters")
- commit 9baeb5eb1f83 ("sfc: falcon: remove duplicated bit-wise or of
LOOPBACK_SGMII")
- plus 2 more recent commits (fixes)
- commit 458bd99e4974 ("sfc: remove ctpio_dmabuf_start from stats")
- commit 0c235113b3c4 ("sfc: stop the TX queue before pushing new
buffers")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1836635/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844378] Re: bionic/linux-aws-fips: 4.15.0-2001.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: 1844380 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips - phase: Holding before Promote to Proposed - phase-changed: Thursday, 26. September 2019 14:41 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 26. September 2019 20:17 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,meta:queued,signed:queued + promote-to-proposed: Pending -- ready for review replaces: bug 1842804 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/1844378 Title: bionic/linux-aws-fips: 4.15.0-2001.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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1844380 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Thursday, 26. September 2019 20:17 UTC reason: promote-to-proposed: Pending -- ready for review replaces: bug 1842804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788098] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2019-09-26 15:42 EDT--- Re-opening on our side to test in 19.10. Everything should be there for that, but it would be good to confirm this in time to get any needed fixes to 20.04, too. Just being clear at this point we don't need to target bionic - but validate on 19.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid migration issues with aligned 2MB THB Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Expired Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Bug description: FYI: This blocks bug 1781526 - once this one here is resolved we can go on with SRU considerations for 1781526 --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837726] Re: Installation fails on eoan/PowerVM : missing /dev/nvram
Hi, @frediz.
I will open a new bug, so we can track the nvram and vio issues
independently. I can't tell for sure if I will be able to provide a new
ISO or initrd for the installer, but will try.
Thanks.
Cascardo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1837726
Title:
Installation fails on eoan/PowerVM : missing /dev/nvram
Status in linux package in Ubuntu:
Fix Committed
Bug description:
Hi,
since eoan and kernel 5.2, the installation fails when installing grub at the
end.
Actually /dev/nvram does not exist.
nvram support was previously built in the kernel and is now built as a module,
and the module is not shipped within the iso or in udebs.
This is probably due to commit d7d73492dc5f2 in Ubuntu's linux git tree :
---
commit d7d73492dc5f2ccc5c76b042341370838af148e4
Author: Seth Forshee
Date: Wed Jun 5 10:47:33 2019 -0500
UBUNTU: [Config] update annotations following config review
...
-CONFIG_NVRAMpolicy<{'amd64': 'm',
'i386': 'm'}>
+CONFIG_NVRAMpolicy<{'amd64': 'm',
'i386': 'm', 'ppc64el': 'm'}>
...
---
F.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837726/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844186] Re: [regression] NoNewPrivileges incompatible with Apparmor
Tests results on Bionic: Bionic/4.15: $ uname -a Linux c2d.mgmt.sdeziel.info 4.15.0-64-generic #73+lp1844186 SMP Thu Sep 26 15:17:27 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux *result*: works! Bionic/5.0: $ uname -a Linux c2d.mgmt.sdeziel.info 5.0.0-8-generic #9+lp1844186 SMP Thu Sep 26 15:03:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux *result*: doesn't work/couldn't test properly. That kernel doesn't let me load an Apparmor policy in the container: root@ns0:~# aa-status apparmor module is loaded. You do not have enough privilege to read the profile set. Maybe it's just too old or the kernel isn't compatible with the Apparmor version from Bionic? The binary/service starts fine with NoNewPrivileges=yes but there is no Apparmor policy loaded in the container, only in the host. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844186 Title: [regression] NoNewPrivileges incompatible with Apparmor Status in linux package in Ubuntu: Confirmed Bug description: Description: Host: Bionic 64 bit with GA kernel (4.15) Container: Bionic 64 bit The container runs a binary (/usr/sbin/nsd) locked by an Apparmor profile. The systemd service is configured with NoNewPrivileges=yes. # systemctl show nsd | grep ^NoNew NoNewPrivileges=yes This setup worked fine with 4.15.0-58-generic and before but stopped working with the 4.15.0-60-generic update. When running the bogus kernel, starting the nsd service fails and the following is logged in the host's dmesg: audit: type=1400 audit(1568387834.381:73): apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="lxd-ns0_" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="lxd-ns0_//&:lxd-ns0_:/usr/sbin/nsd" audit: type=1400 audit(1568387834.381:74): apparmor="DENIED" operation="exec" info="no new privs" error=-1 namespace="root//lxd-ns0_" profile="unconfined" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="/usr/sbin/nsd" Disabling the Apparmor profile OR setting NoNewPrivileges=no in the container makes it work again. I check with a couple of kernels: 4.15.0-52-generic works 4.15.0-58-generic works 4.15.0-60-generic is broken The 5.0 HWE kernel has always been broken it seems: 5.0.0-15-generic is broken 5.0.0-17-generic is broken 5.0.0-20-generic is broken 5.0.0-23-generic is broken 5.0.0-25-generic is broken 5.0.0-27-generic is broken I have another similar setup but using Xenial host/container and it broke in a similar fashion where 4.4.0-159-generic works but 4.4.0-161-generic is broken. Additional information: # lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 # apt-cache policy nsd nsd: Installed: 4.1.26-1ubuntu0.18.04.1~ppa2 Candidate: 4.1.26-1ubuntu0.18.04.1~ppa2 Version table: *** 4.1.26-1ubuntu0.18.04.1~ppa2 500 500 http://ppa.launchpad.net/sdeziel.info/infra/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 4.1.17-1build1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages nsd comes from a custom backport this should be irrelevant. nsd's custom Apparmor profile: https://paste.ubuntu.com/p/BB3ZYzH8WQ/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 16 18:02 seq crw-rw 1 root audio 116, 33 Sep 16 18:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 16 18:14:02 2019 InstallationDate: Installed on 2019-08-22 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. Inspiron 530s PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=7c11931f-ee1e-4d07-bc03-d167b9c39ef0 ro apt-setup/restricted=false apt-setup/multiverse=false kaslr nmi_watchdog=0 nr_cpus=2 pti=on vsyscall=none RelatedPackageVersions:
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Same here, Linux szabolaszlo-ZenBook-UX433FN-UX433FN 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843018] Re: 5.0.0-27-generic: /proc//maps: Pathnames are '/' inside a container
github actions CI/CD is broken because of this as well -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1843018 Title: 5.0.0-27-generic: /proc//maps: Pathnames are '/' inside a container Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Bug description: Using kernel 5.0.0-27-generic on Ubuntu 18.04 in a container, every pathname in /proc//maps is / instead of the mapped file path. This appears to be a regression in 5.0.0-27-generic; it works on 5.0.0-25-generic. The problem can be reproduced in various Ubuntu releases, e.g. 18.04 and 19.04. 5.0.0-25-generic (working): $ sudo docker run ubuntu cat /proc/1/maps 56324a3f5000-56324a3fd000 r-xp fc:01 665673 /bin/cat 56324a5fc000-56324a5fd000 r--p 7000 fc:01 665673 /bin/cat 56324a5fd000-56324a5fe000 rw-p 8000 fc:01 665673 /bin/cat 56324a8eb000-56324a90c000 rw-p 00:00 0 [heap] 7f8ab5f91000-7f8ab6178000 r-xp fc:01 666073 /lib/x86_64-linux-gnu/libc-2.27.so 7f8ab6178000-7f8ab6378000 ---p 001e7000 fc:01 666073 /lib/x86_64-linux-gnu/libc-2.27.so 7f8ab6378000-7f8ab637c000 r--p 001e7000 fc:01 666073 /lib/x86_64-linux-gnu/libc-2.27.so 7f8ab637c000-7f8ab637e000 rw-p 001eb000 fc:01 666073 /lib/x86_64-linux-gnu/libc-2.27.so 7f8ab637e000-7f8ab6382000 rw-p 00:00 0 7f8ab6382000-7f8ab63a9000 r-xp fc:01 666055 /lib/x86_64-linux-gnu/ld-2.27.so 7f8ab6583000-7f8ab65a7000 rw-p 00:00 0 7f8ab65a9000-7f8ab65aa000 r--p 00027000 fc:01 666055 /lib/x86_64-linux-gnu/ld-2.27.so 7f8ab65aa000-7f8ab65ab000 rw-p 00028000 fc:01 666055 /lib/x86_64-linux-gnu/ld-2.27.so 7f8ab65ab000-7f8ab65ac000 rw-p 00:00 0 7ffc25954000-7ffc25975000 rw-p 00:00 0 [stack] 7ffc259f1000-7ffc259f4000 r--p 00:00 0 [vvar] 7ffc259f4000-7ffc259f5000 r-xp 00:00 0 [vdso] ff60-ff601000 r-xp 00:00 0 [vsyscall] 5.0.0-27-generic (broken): $ sudo docker run ubuntu cat /proc/1/maps 55de0e052000-55de0e05a000 r-xp fc:01 665673 / 55de0e259000-55de0e25a000 r--p 7000 fc:01 665673 / 55de0e25a000-55de0e25b000 rw-p 8000 fc:01 665673 / 55de0fcb3000-55de0fcd4000 rw-p 00:00 0 [heap] 7f7a8d881000-7f7a8da68000 r-xp fc:01 666073 / 7f7a8da68000-7f7a8dc68000 ---p 001e7000 fc:01 666073 / 7f7a8dc68000-7f7a8dc6c000 r--p 001e7000 fc:01 666073 / 7f7a8dc6c000-7f7a8dc6e000 rw-p 001eb000 fc:01 666073 / 7f7a8dc6e000-7f7a8dc72000 rw-p 00:00 0 7f7a8dc72000-7f7a8dc99000 r-xp fc:01 666055 / 7f7a8de73000-7f7a8de97000 rw-p 00:00 0 7f7a8de99000-7f7a8de9a000 r--p 00027000 fc:01 666055 / 7f7a8de9a000-7f7a8de9b000 rw-p 00028000 fc:01 666055 / 7f7a8de9b000-7f7a8de9c000 rw-p 00:00 0 7ffc744bd000-7ffc744de000 rw-p 00:00 0 [stack] 7ffc7452d000-7ffc7453 r--p 00:00 0 [vvar] 7ffc7453-7ffc74531000 r-xp 00:00 0 [vdso] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844784] Re: X1 carbon gen 6 cannot boot 5.3.0-12
1. Re-enabled secure boot 2. Failed to boot 5.3.0-12 3. Disabled TPM 4. Successfully booted 5.3.0-12 with secure boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844784 Title: X1 carbon gen 6 cannot boot 5.3.0-12 Status in linux package in Ubuntu: Confirmed Bug description: My X1 carbon gen6 will not boot the 5.3.0-12 (or 5.3.0-10) kernel. It gets as far as saying: EFI stub: Secure boot enabled Nothing else is printed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: powersj1385 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=1eb43198-8ef5-4035-8b81-74c3e2936ad7 InstallationDate: Installed on 2018-12-06 (288 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:2115 Acer, Inc Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KHCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-15-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 RelatedPackageVersions: linux-restricted-modules-5.2.0-15-generic N/A linux-backports-modules-5.2.0-15-generic N/A linux-firmware1.182 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.2.0-15-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-08-27 (24 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET65W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET65W(1.40):bd07/02/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844784] Re: X1 carbon gen 6 cannot boot 5.3.0-12
FWIW here is the firmware version: DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET65W (1.40 ) 07/02/2019 I am running with an encrypted disk with UEFI secure boot enabled. While I was not doing anything with the TPM it was enabled by default I believe. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844784 Title: X1 carbon gen 6 cannot boot 5.3.0-12 Status in linux package in Ubuntu: Confirmed Bug description: My X1 carbon gen6 will not boot the 5.3.0-12 (or 5.3.0-10) kernel. It gets as far as saying: EFI stub: Secure boot enabled Nothing else is printed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: powersj1385 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=1eb43198-8ef5-4035-8b81-74c3e2936ad7 InstallationDate: Installed on 2018-12-06 (288 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:2115 Acer, Inc Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KHCTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-15-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 RelatedPackageVersions: linux-restricted-modules-5.2.0-15-generic N/A linux-backports-modules-5.2.0-15-generic N/A linux-firmware1.182 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.2.0-15-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-08-27 (24 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET65W (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET65W(1.40):bd07/02/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844021] Re: Suspend stopped working from 4.4.0-157 onwards
diddly, I think you can be right, the same patch was introduced since Ubuntu-4.15.0-59.66. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844021 Title: Suspend stopped working from 4.4.0-157 onwards Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading the kernel above 4.4.0-154, starting with 4.4.0-157, suspend does not work for me anymore. Never had such an issue in the last 6 years. This is the relevant output when suspend fails: [ 328.25] PM: Suspending system (mem) [ 328.288902] Suspending console(s) (use no_console_suspend to debug) [ 328.289118] wlp1s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 328.289209] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [ 328.289570] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 328.289600] sd 0:0:0:0: [sda] Stopping disk [ 328.291700] sd 1:0:0:0: [sdb] Stopping disk [ 328.312413] xhci_hcd :03:00.0: WARN: xHC save state timeout [ 328.312456] suspend_common(): xhci_pci_suspend+0x0/0x70 returns -110 [ 328.312461] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110 [ 328.312465] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110 [ 328.312483] PM: Device :03:00.0 failed to suspend async: error -110 [ 328.848109] PM: Some devices failed to suspend, or early wake event detected This is my relevant lspci -v output: 03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller (prog-if 30 [XHCI]) Subsystem: Samsung Electronics Co Ltd ASM1042 SuperSpeed USB Host Controller Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f050 (64-bit, non-prefetchable) [size=32K] Capabilities: Kernel driver in use: xhci_hcd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844021] Re: Suspend stopped working from 4.4.0-157 onwards
https://lkml.org/lkml/2019/9/26/581 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844021 Title: Suspend stopped working from 4.4.0-157 onwards Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading the kernel above 4.4.0-154, starting with 4.4.0-157, suspend does not work for me anymore. Never had such an issue in the last 6 years. This is the relevant output when suspend fails: [ 328.25] PM: Suspending system (mem) [ 328.288902] Suspending console(s) (use no_console_suspend to debug) [ 328.289118] wlp1s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 328.289209] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [ 328.289570] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 328.289600] sd 0:0:0:0: [sda] Stopping disk [ 328.291700] sd 1:0:0:0: [sdb] Stopping disk [ 328.312413] xhci_hcd :03:00.0: WARN: xHC save state timeout [ 328.312456] suspend_common(): xhci_pci_suspend+0x0/0x70 returns -110 [ 328.312461] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110 [ 328.312465] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110 [ 328.312483] PM: Device :03:00.0 failed to suspend async: error -110 [ 328.848109] PM: Some devices failed to suspend, or early wake event detected This is my relevant lspci -v output: 03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller (prog-if 30 [XHCI]) Subsystem: Samsung Electronics Co Ltd ASM1042 SuperSpeed USB Host Controller Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f050 (64-bit, non-prefetchable) [size=32K] Capabilities: Kernel driver in use: xhci_hcd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB
These patches are still needed to solve the bug, so this bug need to be reopened. We are waiting for Paul's reply. ** Changed in: linux (Ubuntu Bionic) Status: Expired => 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/1788098 Title: Avoid migration issues with aligned 2MB THB Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Expired Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Bug description: FYI: This blocks bug 1781526 - once this one here is resolved we can go on with SRU considerations for 1781526 --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844021] Re: Suspend stopped working from 4.4.0-157 onwards
diddly, it's highly likely a different issue since it's a different kernel. Please file a separate bug report. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844021 Title: Suspend stopped working from 4.4.0-157 onwards Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading the kernel above 4.4.0-154, starting with 4.4.0-157, suspend does not work for me anymore. Never had such an issue in the last 6 years. This is the relevant output when suspend fails: [ 328.25] PM: Suspending system (mem) [ 328.288902] Suspending console(s) (use no_console_suspend to debug) [ 328.289118] wlp1s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 328.289209] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [ 328.289570] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 328.289600] sd 0:0:0:0: [sda] Stopping disk [ 328.291700] sd 1:0:0:0: [sdb] Stopping disk [ 328.312413] xhci_hcd :03:00.0: WARN: xHC save state timeout [ 328.312456] suspend_common(): xhci_pci_suspend+0x0/0x70 returns -110 [ 328.312461] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110 [ 328.312465] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110 [ 328.312483] PM: Device :03:00.0 failed to suspend async: error -110 [ 328.848109] PM: Some devices failed to suspend, or early wake event detected This is my relevant lspci -v output: 03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller (prog-if 30 [XHCI]) Subsystem: Samsung Electronics Co Ltd ASM1042 SuperSpeed USB Host Controller Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f050 (64-bit, non-prefetchable) [size=32K] Capabilities: Kernel driver in use: xhci_hcd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843644] Re: touchpad not working on LHMZNIY Yepbook
Can you please test this kernel and attach dmesg: https://people.canonical.com/~khfeng/lp1843644/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1843644 Title: touchpad not working on LHMZNIY Yepbook Status in linux package in Ubuntu: Confirmed Bug description: Fresh install, but the touchpad isn't showing in the device list at all.And it perfectly work on Windows. Device list attached. Works ok if you attach a mouse. ProblemType: Bug Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-27-generic 5.0.0-27.28~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 21:40:32 2019 InstallationDate: Installed on 2019-09-10 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: quentin1138 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-17 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Insyde Braswell Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=f12f1e0c-114b-401a-9a27-af7ccef1c0b6 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/25/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: E115C.intel.C005 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrE115C.intel.C005:bd05/25/2016:svnInsyde:pnBraswell:pvrType1-TBDbyOEM:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: Braswell dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Insyde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845323] Re: Trying to online dasd drive results in invalid input/output from the kernel on z/VM
** Description changed: + SRU Justification: + == + + [Impact] + + * Trying to online dasd drive results in invalid input/output from the + kernel on z/VM + + [Fix] + + * ? TODO - hopefully patch attached ? + + [Test Case] + + * Ubuntu on z/VM guest installation and selecting at least one DASD + device (that's not defined as dedicated). + + * Alternatively doing an Ubuntu on z/VM guest installation on zFCP/SCSI + disk and manually activating a DASD device post-install with 'chzdev -e + '. + + [Regression Potential] + + * The kernel (aka DASD module) currently just fails on activating a (non + dedicated) DASD. + + * But regressions might be introduced in the DASD stack so that is fails + later on LPAR installation, too - but this can easily be tested (and + will be). + + * The chance that zFCP/SCSI disks are harmed by accident is quite low, + since this is a very different stack. + + [Other Info] + + * This is a regression that was introduced with the thin dasd provisioning feature that landed upstream with kernel 5.2/5.3, so affects Eoan only. + __ + Sep 25 12:06:39 s390-dasd[4637]: ECKD DASD 0.0.0200 configure failed Sep 25 12:06:39 s390-dasd[4637]: Error: Could not write file /sys/bus/ccw/drivers/dasd-eckd/0.0.0200/online: Input/output error Sep 25 12:06:39 s390-dasd[4637]: Configuring devices in the active configuration only Sep 25 12:06:39 main-menu[421]: WARNING **: Configuring 's390-dasd' failed with error code 1 Sep 25 12:06:39 main-menu[421]: WARNING **: Menu item 's390-dasd' failed. Sep 25 12:06:39 kernel: [ 137.472853] dasd-eckd.401b68: 0.0.0200: A channel path to the device has become operational Sep 25 12:06:39 kernel: [ 137.473914] dasd-eckd.6b7759: 0.0.0200: Reading the volume storage information failed with rc=-5 Sep 25 12:06:39 kernel: [ 137.473917] dasd.3e7d29: 0.0.0200 Setting the DASD online with discipline ECKD failed with rc=-5 Sep 25 12:06:39 kernel: [ 137.473918] [ cut here ] Sep 25 12:06:39 kernel: [ 137.473943] WARNING: CPU: 0 PID: 4638 at kernel/module.c:1137 module_put.part.0+0xe2/0xe8 Sep 25 12:06:39 kernel: [ 137.473944] Modules linked in: lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod qeth_l2 pkey crc32_vx_s390 qeth qdio zcrypt_cex4 ccwgroup zcrypt Sep 25 12:06:39 kernel: [ 137.473953] CPU: 0 PID: 4638 Comm: chzdev Not tainted 5.3.0-10-generic #11-Ubuntu Sep 25 12:06:39 kernel: [ 137.473954] Hardware name: IBM 2964 N63 400 (z/VM 6.4.0) Sep 25 12:06:39 kernel: [ 137.473955] Krnl PSW : 0704c0018000 2b2c3372 (module_put.part.0+0xe2/0xe8) Sep 25 12:06:39 kernel: [ 137.473958]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 Sep 25 12:06:39 kernel: [ 137.473959] Krnl GPRS: 0004 0006 0024 0007 Sep 25 12:06:39 kernel: [ 137.473960]0007 7f2ce800 fffb 03ff80151578 Sep 25 12:06:39 kernel: [ 137.473961]fffb 03ff80074df8 03ff80151900 78105800 Sep 25 12:06:39 kernel: [ 137.473962]7e17e600 0bf8 2b2c336e 03e000c5fb08 Sep 25 12:06:39 kernel: [ 137.473969] Krnl Code: 2b2c3362: c0200048859a larl%r2,2bbd3e96 Sep 25 12:06:39 kernel: [ 137.473969]2b2c3368: c0e5fffe16a4 brasl %r14,2b2860b0 Sep 25 12:06:39 kernel: [ 137.473969] #2b2c336e: a7f40001 brc 15,2b2c3370 Sep 25 12:06:39 kernel: [ 137.473969] >2b2c3372: a7f4ffb1 brc 15,2b2c32d4 Sep 25 12:06:39 kernel: [ 137.473969]2b2c3376: 0707 bcr 0,%r7 Sep 25 12:06:39 kernel: [ 137.473969]2b2c3378: c004 brcl0,2b2c3378 Sep 25 12:06:39 kernel: [ 137.473969]2b2c337e: ec280006007c cgij%r2,0,8,2b2c338a Sep 25 12:06:39 kernel: [ 137.473969]2b2c3384: c0f4ff86 brcl15,2b2c3290 Sep 25 12:06:39 kernel: [ 137.473980] Call Trace: Sep 25 12:06:39 kernel: [ 137.473982] ([<2b2c336e>] module_put.part.0+0xde/0xe8) - Sep 25 12:06:39 kernel: [ 137.473994] [<03ff80074df8>] dasd_generic_free_discipline+0x68/0x80 [dasd_mod] - Sep 25 12:06:39 kernel: [ 137.473998] [<03ff8007f5ba>] dasd_delete_device+0x122/0x1c8 [dasd_mod] - Sep 25 12:06:39 kernel: [ 137.474001] [<03ff8007bcfa>] dasd_generic_set_online+0x2ea/0x310 [dasd_mod] - Sep 25 12:06:39 kernel: [ 137.474006] [<2b84db48>] ccw_device_set_online+0x110/0x528 - Sep 25 12:06:39 kernel: [ 137.474008] [<2b84dfb0>] online_store_recog_and_online+0x50/0x130 - Sep 25 12:06:39 kernel: [ 137.474009] [<2b84f042>] online_store+0x1b2/0x2e0 - Sep 25 12:06:39 kernel: [ 137.474013] [<2b50b7a0>]
[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez
@yura9, @mauromol, or anyone experiencing this, if you are running Bionic or Disco, can you please test with the 'bluez' package currently in -proposed? See the previous 2 comments for instructions how. This bug does need someone affected by this bug (i.e. with the affected hardware) to verify it before it's released. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bluez source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Invalid Status in bluez source package in Disco: Fix Committed Status in linux source package in Disco: Invalid Status in systemd source package in Disco: Invalid Status in bluez source package in Eoan: Fix Released Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Invalid Status in bluez package in Debian: New Bug description: [impact] on specific Dell systems, with a specific usb bluetooth device built- in, the udev rule 'hid2hci' provided by the 'bluez' package causes an endless loop of uevents resulting from 'bind' or 'unbind' kernel uevents. These new events were added to the kernel after the 'hid2hci' udev rule was written. [test case] the specific Dell system is required to be able to reproduce this, or at least the specific usb bluetooth hardware included in that system. Reproducing this is reportedly easy, for example comment 75 indicates it happens on every boot. When this happens, any process monitor (e.g. ps, top, etc) will show the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should show repeated 'bind' and 'unbind' events as mentioned in comment 39. [regression potential] as this alters what kernel uevents the 'hid2hci' udev rule processes, regressions would involve the affected usb bluetooth device failing to be set up, or otherwise not processing the uevents correctly. [other info] this is not fixed yet upstream, as of my last check, but has been submitted upstream as mentioned in comment 95. original description: -- The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830084] Re: ubuntu_kernel_selftests ftrace fails
** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1830084 Title: ubuntu_kernel_selftests ftrace fails Status in ubuntu-kernel-tests: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-gcp package in Ubuntu: New Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: Confirmed Status in linux-gcp source package in Disco: Confirmed Bug description: Cloud: Azure Series: Disco Kernel: 5.0.0-1007.7 linux-azure Instance: Standard_D2_v3 and others. 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > /proc/sys/net/ipv4/conf/all/accept_local'' 05/20 14:24:27 DEBUG| utils:0116| Running 'sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done for 'all'. 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Leaving directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] make[1]: Entering directory '/home/azure/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' 05/20 14:24:27 DEBUG| utils:0153| [stdout] TAP version 13 05/20 14:24:27 DEBUG| utils:0153| [stdout] selftests: ftrace: ftracetest 05/20 14:24:27 DEBUG| utils:0153| [stdout] 05/20 14:24:27 ERROR| utils:0153| [stderr] ./ftracetest: 163: [: Illegal number: 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e === Ftrace unit tests === 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [1] Basic trace file check 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:27 DEBUG| utils:0153| [stdout] -e -n [2] Basic test for tracers 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:31 DEBUG| utils:0153| [stdout] -e -n [3] Basic trace clock test 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [4] Basic event tracing check 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:32 DEBUG| utils:0153| [stdout] -e -n [5] Change the ringbuffer size 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [6] Snapshot and tracing setting 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [7] trace_pipe and trace_marker 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [8] Generic dynamic event - add/remove kprobe events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [9] Generic dynamic event - add/remove synthetic events 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:33 DEBUG| utils:0153| [stdout] -e -n [10] Generic dynamic event - selective clear (compatibility) 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [11] Generic dynamic event - generic clear event 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [12] event tracing - enable/disable with event level files 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:34 DEBUG| utils:0153| [stdout] -e -n [13] event tracing - restricts events based on pid 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [14] event tracing - enable/disable with subsystem level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [15] event tracing - enable/disable with top level files 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:35 DEBUG| utils:0153| [stdout] -e -n [16] Test trace_printk from module 05/20 14:24:36 DEBUG| utils:0153| [stdout] -e [UNRESOLVED] 05/20 14:24:36 DEBUG| utils:0153| [stdout] -e -n [17] ftrace - function graph filters with stack tracer 05/20 14:24:38 DEBUG| utils:0153| [stdout] -e [PASS] 05/20 14:24:38 DEBUG| utils:0153| [stdout] -e -n [18] ftrace - function graph
[Kernel-packages] [Bug 1844387] Re: xenial/linux-oracle: 4.15.0-1026.29~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1844388 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Signoff phase-changed: Monday, 23. September 2019 23:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842580 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/1844387 Title: xenial/linux-oracle: 4.15.0-1026.29~16.04.1 -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 verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1844388 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Signoff phase-changed: Monday, 23. September 2019 23:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842580 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844387] Re: xenial/linux-oracle: 4.15.0-1026.29~16.04.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1844387 Title: xenial/linux-oracle: 4.15.0-1026.29~16.04.1 -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 verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1844388 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Signoff phase-changed: Monday, 23. September 2019 23:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842580 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844378] Re: bionic/linux-aws-fips: 4.15.0-2001.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: 1844380 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 26. September 2019 14:41 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,meta:queued,signed:queued replaces: bug 1842804 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/1844378 Title: bionic/linux-aws-fips: 4.15.0-2001.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-signing-to-proposed series: New 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: 1844380 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 26. September 2019 14:41 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,meta:queued,signed:queued replaces: bug 1842804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845323] Re: Trying to online dasd drive results in invalid input/output from the kernel on z/VM
Got feedback that this problems occurs not only on z/VM 6.4 but also on 7.1, and it indeed seems to be an issue with thin provisioning (LP 1830731 #3). It seems to happen with virtual devices and MDISKS, but not with dedicated DASDs. Fix is in progress by IBM. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845323 Title: Trying to online dasd drive results in invalid input/output from the kernel on z/VM Status in linux package in Ubuntu: Confirmed Bug description: Sep 25 12:06:39 s390-dasd[4637]: ECKD DASD 0.0.0200 configure failed Sep 25 12:06:39 s390-dasd[4637]: Error: Could not write file /sys/bus/ccw/drivers/dasd-eckd/0.0.0200/online: Input/output error Sep 25 12:06:39 s390-dasd[4637]: Configuring devices in the active configuration only Sep 25 12:06:39 main-menu[421]: WARNING **: Configuring 's390-dasd' failed with error code 1 Sep 25 12:06:39 main-menu[421]: WARNING **: Menu item 's390-dasd' failed. Sep 25 12:06:39 kernel: [ 137.472853] dasd-eckd.401b68: 0.0.0200: A channel path to the device has become operational Sep 25 12:06:39 kernel: [ 137.473914] dasd-eckd.6b7759: 0.0.0200: Reading the volume storage information failed with rc=-5 Sep 25 12:06:39 kernel: [ 137.473917] dasd.3e7d29: 0.0.0200 Setting the DASD online with discipline ECKD failed with rc=-5 Sep 25 12:06:39 kernel: [ 137.473918] [ cut here ] Sep 25 12:06:39 kernel: [ 137.473943] WARNING: CPU: 0 PID: 4638 at kernel/module.c:1137 module_put.part.0+0xe2/0xe8 Sep 25 12:06:39 kernel: [ 137.473944] Modules linked in: lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod qeth_l2 pkey crc32_vx_s390 qeth qdio zcrypt_cex4 ccwgroup zcrypt Sep 25 12:06:39 kernel: [ 137.473953] CPU: 0 PID: 4638 Comm: chzdev Not tainted 5.3.0-10-generic #11-Ubuntu Sep 25 12:06:39 kernel: [ 137.473954] Hardware name: IBM 2964 N63 400 (z/VM 6.4.0) Sep 25 12:06:39 kernel: [ 137.473955] Krnl PSW : 0704c0018000 2b2c3372 (module_put.part.0+0xe2/0xe8) Sep 25 12:06:39 kernel: [ 137.473958]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 Sep 25 12:06:39 kernel: [ 137.473959] Krnl GPRS: 0004 0006 0024 0007 Sep 25 12:06:39 kernel: [ 137.473960]0007 7f2ce800 fffb 03ff80151578 Sep 25 12:06:39 kernel: [ 137.473961]fffb 03ff80074df8 03ff80151900 78105800 Sep 25 12:06:39 kernel: [ 137.473962]7e17e600 0bf8 2b2c336e 03e000c5fb08 Sep 25 12:06:39 kernel: [ 137.473969] Krnl Code: 2b2c3362: c0200048859a larl%r2,2bbd3e96 Sep 25 12:06:39 kernel: [ 137.473969]2b2c3368: c0e5fffe16a4 brasl %r14,2b2860b0 Sep 25 12:06:39 kernel: [ 137.473969] #2b2c336e: a7f40001 brc 15,2b2c3370 Sep 25 12:06:39 kernel: [ 137.473969] >2b2c3372: a7f4ffb1 brc 15,2b2c32d4 Sep 25 12:06:39 kernel: [ 137.473969]2b2c3376: 0707 bcr 0,%r7 Sep 25 12:06:39 kernel: [ 137.473969]2b2c3378: c004 brcl0,2b2c3378 Sep 25 12:06:39 kernel: [ 137.473969]2b2c337e: ec280006007c cgij%r2,0,8,2b2c338a Sep 25 12:06:39 kernel: [ 137.473969]2b2c3384: c0f4ff86 brcl15,2b2c3290 Sep 25 12:06:39 kernel: [ 137.473980] Call Trace: Sep 25 12:06:39 kernel: [ 137.473982] ([<2b2c336e>] module_put.part.0+0xde/0xe8) Sep 25 12:06:39 kernel: [ 137.473994] [<03ff80074df8>] dasd_generic_free_discipline+0x68/0x80 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.473998] [<03ff8007f5ba>] dasd_delete_device+0x122/0x1c8 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.474001] [<03ff8007bcfa>] dasd_generic_set_online+0x2ea/0x310 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.474006] [<2b84db48>] ccw_device_set_online+0x110/0x528 Sep 25 12:06:39 kernel: [ 137.474008] [<2b84dfb0>] online_store_recog_and_online+0x50/0x130 Sep 25 12:06:39 kernel: [ 137.474009] [<2b84f042>] online_store+0x1b2/0x2e0 Sep 25 12:06:39 kernel: [ 137.474013] [<2b50b7a0>] kernfs_fop_write+0xd8/0x1f8 Sep 25 12:06:39 kernel: [ 137.474017] [<2b4585f8>] vfs_write+0xb0/0x1b8 Sep 25 12:06:39 kernel: [ 137.474018] [<2b459eb8>] ksys_write+0x68/0xf8 Sep 25 12:06:39 kernel: [ 137.474023] [<2ba4c4b8>] system_call+0xdc/0x2c8 Sep 25 12:06:39 kernel: [ 137.474024] Last Breaking-Event-Address: Sep 25 12:06:39 kernel: [ 137.474025] [<2b2c336e>] module_put.part.0+0xde/0xe8 Sep 25 12:06:39 kernel: [ 137.474026] ---[ end trace 94b382399e0f8876 ]--- Cannot
[Kernel-packages] [Bug 1843222] Re: Old Linux version booted after upgrade to Ubuntu 19.10
Some additional info from conky about the configuration: ** Attachment added: "Screenshot from 2019-09-26 12-09-32.png" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1843222/+attachment/5291518/+files/Screenshot%20from%202019-09-26%2012-09-32.png -- 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/1843222 Title: Old Linux version booted after upgrade to Ubuntu 19.10 Status in zfs-linux package in Ubuntu: New Bug description: I have a triple boot with the following systems: - Xubuntu 19.10 from zfs 0.8.1 - Ubuntu Mate 18.04.3 from zfs 0.7.12 - Ubuntu 19.10 from ext4 Upgrading the first system Xubuntu to 19.10 worked fine and I was very happy with the almost perfect result and the nice grub-menu. Upgrading to Ubuntu 19.10 created the following problems: - That system booted after the upgrade to Ubuntu 19.10 in Linux 5.0 with zfs 0.7.12 - All grub entries with the ZFS systems disappeared and the whole nice grub-menu was gone. Running update-grub and grub install; I did see the Linux 5.2 version appear, but it still booted from 5.0. There were some error messages about mounting/importing during the zfs part of the upgrade, but they were the same as the ones during the Xubuntu upgrade and that upgrade worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: zfsutils-linux 0.8.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 9 01:37:21 2019 InstallationDate: Installed on 2019-03-10 (183 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: zfs-linux UpgradeStatus: Upgraded to eoan on 2019-09-09 (0 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1843222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844398] Re: xenial/linux-gcp: 4.15.0-1045.47 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1844403 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Monday, 23. September 2019 22:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842590 trackers: xenial/linux-gcp/gcp-kernel: bug 1844396 xenial/linux-gcp/gke-kernel: bug 1844397 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1844398 Title: xenial/linux-gcp: 4.15.0-1045.47 -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 verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1844403 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Monday, 23. September 2019 22:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842590 trackers: xenial/linux-gcp/gcp-kernel: bug 1844396 xenial/linux-gcp/gke-kernel: bug 1844397 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803692] Re: bionic 4.15 nvme regression from trusty 4.4 with two identical devices
A fix for those who has this issue with Intel SSD / NVMe drives: Firmware update with Intel SSD Data Center Tool (DCT) https://downloadcenter.intel.com/search?keyword=SSD+Firmware+Update+Tool wget https://downloadmirror.intel.com/28999/eng/Intel_SSD_Data_Center_Tool_3.0.20_Linux.zip -O /tmp/Intel_SSD_Data_Center_Tool_3.0.20_Linux.zip unzip -d /tmp /tmp/Intel_SSD_Data_Center_Tool_3.0.20_Linux.zip sudo dpkg -i /tmp/isdct_3.0.20-1_amd64.deb # show nvme data isdct show -intelssd isdct load -intelssd 0 reboot isdct load -intelssd 1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803692 Title: bionic 4.15 nvme regression from trusty 4.4 with two identical devices Status in linux package in Ubuntu: Fix Released Bug description: I have a system containing two identical nvme devices. When booting a trusty PXE image with kernel 4.4.0-38-generic both devices are detected and available: # nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x8086 ssvid : 0x8086 sn : BTHH82250N1X1P0E mn : INTEL SSDPEKKF010T8L fr : L08P ... # nvme id-ctrl /dev/nvme1 NVME Identify Controller: vid : 0x8086 ssvid : 0x8086 sn : BTHH82250N261P0E mn : INTEL SSDPEKKF010T8L fr : L08P ... # dmesg | grep nvme [5.106516] nvme0n1: p1 p2 p3 p4 [5.106615] nvme1n1: p1 p2 After booting a bionic PXE image based on 4.15.0-38-generic only the first nvme device is enabled, the second is detected but disabled as both devices have the same nqn: nvme nvme1: ignoring ctrl due to duplicate subnqn (nqn.2017-12.org.nvmeexpress:uuid:----). nvme nvme1: Removing after probe failure status: -22 The nqn string is found in the device firmware rather than being generated by Linux but there does not seem to be an operation in nvme-cli to change this. (It is also questionable if the device firmware value is correct according to section 7.9 of https://nvmexpress.org/wp-content/uploads/NVM-Express-1_3a-20171024_ratified.pdf. My reading of the specification is that the string should start nqn.2014-08.org.nvmeexpress:uuid: with a random UUID, and I assume a random UUID per device.) The Windows 10 installation provided on the system did not have any problems operating with both devices. Looking at the kernel nvme driver history suggests that in 4.4 it didn't care or validate the nqn but now it does there is a problem. Our typical installation is a zpool mirror across two devices and this is preventing us moving from trusty to bionic. This is a report of a similar issue: https://ask.fedoraproject.org/en/question/128422/one-of-two- identical-m2-nvme-drives-disabling-due-to-same-nqn/ It may be worth noting that if the nvme device does not provide an nqn then it seems one is generated based on the device serial number so a system with two Samsung MZVLB256HAHQ devices works fine. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 3440 F pulseaudio CasperVersion: 1.340.2 CurrentDmesg: [ 151.172010] init: plymouth-stop pre-start process (4137) terminated with status 1 DistroRelease: Ubuntu 14.04 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. LiveMediaBuild: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 89e5:1001 Bus 001 Device 002: ID 17ef:6099 Lenovo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 30C8S04Y00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: us1931.efi root=/dev/nfs boot=casper netboot=nfs nfsroot=192.168.10.150:/srv/boot/us1931 locale=en_GB.UTF-8 keyb=gb mirror/country=GB ip=dhcp zinstall= BOOTIF=01-30-9c-23-cb-2a-46 toram ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.127.22 RfKill: Tags: trusty Uname: Linux 4.4.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M1VKT1BA dmi.board.name: 3138 dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1844398] Re: xenial/linux-gcp: 4.15.0-1045.47 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1844398 Title: xenial/linux-gcp: 4.15.0-1045.47 -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 verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1844403 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Monday, 23. September 2019 22:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842590 trackers: xenial/linux-gcp/gcp-kernel: bug 1844396 xenial/linux-gcp/gke-kernel: bug 1844397 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843222] Re: Old Linux version booted after upgrade to Ubuntu 19.10
Note that I only can use the datapools after I exported and re-imported them again. But I have to do that on all boots, so I wrote a small script for it. I did not upgrade the datapool itself, because 2 of the 3 systems still run Ubuntu 19.04 one also from the zfs systems datapool and the other from ext4 on sdc5 with swap on sdc6. -- 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/1843222 Title: Old Linux version booted after upgrade to Ubuntu 19.10 Status in zfs-linux package in Ubuntu: New Bug description: I have a triple boot with the following systems: - Xubuntu 19.10 from zfs 0.8.1 - Ubuntu Mate 18.04.3 from zfs 0.7.12 - Ubuntu 19.10 from ext4 Upgrading the first system Xubuntu to 19.10 worked fine and I was very happy with the almost perfect result and the nice grub-menu. Upgrading to Ubuntu 19.10 created the following problems: - That system booted after the upgrade to Ubuntu 19.10 in Linux 5.0 with zfs 0.7.12 - All grub entries with the ZFS systems disappeared and the whole nice grub-menu was gone. Running update-grub and grub install; I did see the Linux 5.2 version appear, but it still booted from 5.0. There were some error messages about mounting/importing during the zfs part of the upgrade, but they were the same as the ones during the Xubuntu upgrade and that upgrade worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: zfsutils-linux 0.8.1-1ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 9 01:37:21 2019 InstallationDate: Installed on 2019-03-10 (183 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: zfs-linux UpgradeStatus: Upgraded to eoan on 2019-09-09 (0 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1843222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844378] Re: bionic/linux-aws-fips: 4.15.0-2001.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: 1844380 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 26. September 2019 14:41 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 replaces: bug 1842804 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/1844378 Title: bionic/linux-aws-fips: 4.15.0-2001.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-signing-to-proposed series: New 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: 1844380 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 26. September 2019 14:41 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait replaces: bug 1842804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844186] Re: [regression] NoNewPrivileges incompatible with Apparmor
There are some test kernels at https://people.canonical.com/~jj/lp1844186/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844186 Title: [regression] NoNewPrivileges incompatible with Apparmor Status in linux package in Ubuntu: Confirmed Bug description: Description: Host: Bionic 64 bit with GA kernel (4.15) Container: Bionic 64 bit The container runs a binary (/usr/sbin/nsd) locked by an Apparmor profile. The systemd service is configured with NoNewPrivileges=yes. # systemctl show nsd | grep ^NoNew NoNewPrivileges=yes This setup worked fine with 4.15.0-58-generic and before but stopped working with the 4.15.0-60-generic update. When running the bogus kernel, starting the nsd service fails and the following is logged in the host's dmesg: audit: type=1400 audit(1568387834.381:73): apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="lxd-ns0_" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="lxd-ns0_//&:lxd-ns0_:/usr/sbin/nsd" audit: type=1400 audit(1568387834.381:74): apparmor="DENIED" operation="exec" info="no new privs" error=-1 namespace="root//lxd-ns0_" profile="unconfined" name="/usr/sbin/nsd" pid=8568 comm="(nsd)" requested_mask="x" denied_mask="x" fsuid=1065536 ouid=1065536 target="/usr/sbin/nsd" Disabling the Apparmor profile OR setting NoNewPrivileges=no in the container makes it work again. I check with a couple of kernels: 4.15.0-52-generic works 4.15.0-58-generic works 4.15.0-60-generic is broken The 5.0 HWE kernel has always been broken it seems: 5.0.0-15-generic is broken 5.0.0-17-generic is broken 5.0.0-20-generic is broken 5.0.0-23-generic is broken 5.0.0-25-generic is broken 5.0.0-27-generic is broken I have another similar setup but using Xenial host/container and it broke in a similar fashion where 4.4.0-159-generic works but 4.4.0-161-generic is broken. Additional information: # lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 # apt-cache policy nsd nsd: Installed: 4.1.26-1ubuntu0.18.04.1~ppa2 Candidate: 4.1.26-1ubuntu0.18.04.1~ppa2 Version table: *** 4.1.26-1ubuntu0.18.04.1~ppa2 500 500 http://ppa.launchpad.net/sdeziel.info/infra/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 4.1.17-1build1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages nsd comes from a custom backport this should be irrelevant. nsd's custom Apparmor profile: https://paste.ubuntu.com/p/BB3ZYzH8WQ/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 16 18:02 seq crw-rw 1 root audio 116, 33 Sep 16 18:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Sep 16 18:14:02 2019 InstallationDate: Installed on 2019-08-22 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. Inspiron 530s PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-generic root=UUID=7c11931f-ee1e-4d07-bc03-d167b9c39ef0 ro apt-setup/restricted=false apt-setup/multiverse=false kaslr nmi_watchdog=0 nr_cpus=2 pti=on vsyscall=none RelatedPackageVersions: linux-restricted-modules-5.0.0-27-generic N/A linux-backports-modules-5.0.0-27-generic N/A linux-firmware1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.18 dmi.board.name: 0RY007 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.18:bd02/24/2009:svnDellInc.:pnInspiron530s:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530s dmi.sys.vendor: Dell Inc. To manage
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Same here, UX433FN $uname -a Linux lambda 5.1.15-050115-generic #201906250430 SMP Tue Jun 25 04:33:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845127] Re: bionic/linux-gcp: 5.0.0-1019.19~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: 1845128 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Wednesday, 25. September 2019 22:35 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 replaces: bug 1844346 trackers: - bionic/linux-gcp-edge: bug 1844345 + bionic/linux-gcp-edge: bug 1845513, bug 1844345 bionic/linux-gcp/gcp-kernel: bug 1845126 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1845127 Title: bionic/linux-gcp: 5.0.0-1019.19~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug 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: 1845128 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Wednesday, 25. September 2019 22:35 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 replaces: bug 1844346 trackers: bionic/linux-gcp-edge: bug 1845513, bug 1844345 bionic/linux-gcp/gcp-kernel: bug 1845126 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'
See: https://github.com/lxc/lxd/issues/4656#issuecomment-535531229 In https://github.com/lxc/lxd/blob/master/lxd/storage_zfs_utils.go#L255 the umount is done by err := unix.Unmount(mountpoint, unix.MNT_DETACH) The umount2(2) manpage writes about MNT_DETACH: Perform a lazy unmount: make the mount point unavailable for new accesses, immediately disconnect the filesystem and all filesystems mounted below it from each other and from the mount table, and actually perform the unmount when the mount point ceases to be busy. Could this be it? The MNT_DETACH umount looks partially asynchronous. All the subsequent destroy commands may fail because they keep the mount point busy. Finally the retry loop ends, the umount happens for real and the following destroy succeeds. — -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779156 Title: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy' Status in linux package in Ubuntu: Triaged Status in lxc package in Ubuntu: Confirmed Status in linux source package in Cosmic: Triaged Status in lxc source package in Cosmic: Confirmed Status in linux source package in Disco: New Status in lxc source package in Disco: New Status in linux source package in Eoan: Triaged Status in lxc source package in Eoan: Confirmed Bug description: I'm not sure exactly what got me into this state, but I have several lxc containers that cannot be deleted. $ lxc info api_status: stable api_version: "1.0" auth: trusted public: false auth_methods: - tls environment: addresses: [] architectures: - x86_64 - i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificate_fingerprint: 3af6f8b8233c5d9e898590a9486ded5c0bec045488384f30ea921afce51f75cb driver: lxc driver_version: 3.0.1 kernel: Linux kernel_architecture: x86_64 kernel_version: 4.15.0-23-generic server: lxd server_pid: 15123 server_version: "3.2" storage: zfs storage_version: 0.7.5-1ubuntu15 server_clustered: false server_name: milhouse $ lxc delete --force b1 Error: Failed to destroy ZFS filesystem: cannot destroy 'default/containers/b1': dataset is busy Talking in #lxc-dev, stgraber and sforeshee provided diagnosis: | short version is that something unshared a mount namespace causing | them to get a copy of the mount table at the time that dataset was | mounted, which then prevents zfs from being able to destroy it) The work around provided was | you can unstick this particular issue by doing: | grep default/containers/b1 /proc/*/mountinfo | then for any of the hits, do: | nsenter -t PID -m -- umount /var/snap/lxd/common/lxd/storage-pools/default/containers/b1 | then try the delete again ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: smoser31412 F pulseaudio /dev/snd/controlC2: smoser31412 F pulseaudio /dev/snd/controlC0: smoser31412 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jun 28 10:42:45 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (1071 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) MachineType: b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' 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-4.15.0-23-generic root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0246.2015.0309.1355 dmi.board.asset.tag: � dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-503 dmi.chassis.asset.tag: � dmi.chassis.type: 3 dmi.chassis.vendor: � dmi.chassis.version:
[Kernel-packages] [Bug 1844378] Re: bionic/linux-aws-fips: 4.15.0-2001.1 -proposed tracker
** 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-signed Status: In Progress => Fix Committed ** 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: 1844380 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips - phase: Packaging - phase-changed: Wednesday, 25. September 2019 21:02 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 26. September 2019 14:41 UTC reason: - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait replaces: bug 1842804 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/1844378 Title: bionic/linux-aws-fips: 4.15.0-2001.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-signing-to-proposed series: New 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: 1844380 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 26. September 2019 14:41 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait replaces: bug 1842804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844378] Re: bionic/linux-aws-fips: 4.15.0-2001.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-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: 1844380 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Packaging phase-changed: Wednesday, 25. September 2019 21:02 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 replaces: bug 1842804 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/1844378 Title: bionic/linux-aws-fips: 4.15.0-2001.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-signing-to-proposed series: New 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: 1844380 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 26. September 2019 14:41 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait replaces: bug 1842804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844806] Re: kernel panic after upgrading from 19.04 to 19.10
thanks for the hints. I tried the workaround of disabling secure boot and it did not panic and the system started. But I would like to keep secure boot enabled, note that booting 19.10 with the Kernel linux-image-5.0.0-29-generic from 19.04 works properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844806 Title: kernel panic after upgrading from 19.04 to 19.10 Status in linux package in Ubuntu: Confirmed Bug description: I have Package: linux-image-5.3.0-10-generic, Version: 5.3.0-10.11 after upgrading from 19.04 to 19.10 today. I get a kernel panic on boot, before I'm asked to enter the passphrase for my hard drive. I obviously can't cut-and-paste the kernel panic text, but I took a photo, attached. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jik2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 10:55:36 2019 InstallationDate: Installed on 2019-09-12 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20QD001VUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QD001VUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QD001VUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QD001VUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QD001VUS dmi.product.sku: LENOVO_MT_20QD_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/1844806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845405] Re: Xenial update: 4.4.194 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + * bridge/mdb: remove wrong use of NLM_F_MULTI + * cdc_ether: fix rndis support for Mediatek based smartphones + * ipv6: Fix the link time qualifier of 'ping_v6_proc_exit_net()' + * isdn/capi: check message length in capi_write() + * net: Fix null de-reference of device refcount + * sch_hhf: ensure quantum and hhf_non_hh_weight are non-zero + * sctp: Fix the link time qualifier of 'sctp_ctrlsock_exit()' + * sctp: use transport pf_retrans in sctp_do_8_2_transport_strike + * tcp: fix tcp_ecn_withdraw_cwr() to clear TCP_ECN_QUEUE_CWR + * tipc: add NULL pointer check before calling kfree_rcu + * tun: fix use-after-free when register netdev failed + * Revert "MIPS: SiByte: Enable swiotlb for SWARM, LittleSur and BigSur" + * Btrfs: fix assertion failure during fsync and use of stale transaction + * genirq: Prevent NULL pointer dereference in resend_irqs() + * KVM: s390: Do not leak kernel stack data in the KVM_S390_INTERRUPT ioctl + * KVM: x86: work around leak of uninitialized stack contents + * KVM: nVMX: handle page fault in vmread + * MIPS: VDSO: Prevent use of smp_processor_id() + * MIPS: VDSO: Use same -m%-float cflag as the kernel proper + * clk: rockchip: Don't yell about bad mmc phases when getting + * driver core: Fix use-after-free and double free on glue directory + * crypto: talitos - check AES key size + * crypto: talitos - check data blocksize in ablkcipher. + * x86/build: Add -Wnoaddress-of-packed-member to REALMODE_CFLAGS, to silence GCC9 build warning + * MIPS: netlogic: xlr: Remove erroneous check in nlm_fmn_send() + * ARC: configs: Remove CONFIG_INITRAMFS_SOURCE from defconfigs + * USB: usbcore: Fix slab-out-of-bounds bug during device reset + * media: tm6000: double free if usb disconnect while streaming + * x86/boot: Add missing bootparam that breaks boot on some platforms + * xen-netfront: do not assume sk_buff_head list is empty in error handling + * KVM: coalesced_mmio: add bounds checking + * serial: sprd: correct the wrong sequence of arguments + * tty/serial: atmel: reschedule TX after RX was started + * mwifiex: Fix three heap overflow at parsing element in cfg80211_ap_settings + * s390/bpf: fix lcgr instruction encoding + * ARM: OMAP2+: Fix omap4 errata warning on other SoCs + * s390/bpf: use 32-bit index for tail calls + * NFSv4: Fix return values for nfs4_file_open() + * NFS: Fix initialisation of I/O result struct in nfs_pgio_rpcsetup + * Kconfig: Fix the reference to the IDT77105 Phy driver in the description of ATM_NICSTAR_USE_IDT77105 + * ARM: 8874/1: mm: only adjust sections of valid mm structures + * r8152: Set memory to all 0xFFs on failed reg reads + * x86/apic: Fix arch_dynirq_lower_bound() bug for DT enabled machines + * netfilter: nf_conntrack_ftp: Fix debug output + * NFSv2: Fix eof handling + * NFSv2: Fix write regression + * cifs: set domainName when a domain-key is used in multiuser + * cifs: Use kzfree() to zero out the password + * sky2: Disable MSI on yet another ASUS boards (P6Xxxx) + * tools/power turbostat: fix buffer overrun + * net: seeq: Fix the function used to release some memory in an error handling path + * dmaengine: ti: omap-dma: Add cleanup in omap_dma_probe() + * keys: Fix missing null pointer check in request_key_auth_describe() + * floppy: fix usercopy direction + * media: technisat-usb2: break out of loop at end of buffer + * ARC: export "abort" for modules + * net_sched: let qdisc_put() accept NULL pointer + * Linux 4.4.194 -4.4.194 upstream stable release -from git://git.kernel.org/ + 4.4.194 upstream stable release + from git://git.kernel.org/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845405 Title: Xenial update: 4.4.194 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates
[Kernel-packages] [Bug 1845454] Re: Kernel panic with 19.10 beta image
Test build is available at:
https://people.canonical.com/~sforshee/lp1845454/5.3.0-13.14+lp1845454v201909260743/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845454
Title:
Kernel panic with 19.10 beta image
Status in linux package in Ubuntu:
Incomplete
Bug description:
Image: http://cdimage.ubuntu.com/daily-live/20190926/eoan-desktop-amd64.iso
Device: Dell XPS 13 7390 (201908-27305)
When trying to start the live session ("try Ubuntu") or trying to
install the ISO ("install Ubuntu"), the boot process stops within 1
second with a kernel panic (see attached screenshot).
The system could boot with a previous version of Eoan image:
2019-09-09 09:11 (kernel 5.3.0-10)
Workaround: disable TPM2 in the BIOS.
/!\ Please note: the information below (and the attached file
ProcCpuinfoMinimal.txt) come from a 18.04 live session, since I cannot boot
anything with 19.10 beta image.
==
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: syslinux 3:6.03+dfsg1-2
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 07:41:16 2019
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
mtools 4.0.18-2ubuntu1
syslinux-common 3:6.03+dfsg1-2
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: syslinux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance
I kicked off another ~20K reboot tests with Standard_B2S instances and hit hangs again: IP addr Mac AddrKernel Reboots 104.42.3.16100:0d:3a:37:82:ee 5.0.0-1020-azure100 13.91.5.23 00:0d:3a:5a:74:23 5.0.0-1020-azure57 [ HANG ] 13.91.5.222 00:0d:3a:5a:75:1a 5.0.0-1020-azure100 13.64.117.146 00:0d:3a:5a:74:da 5.0.0-1020-azure100 13.64.117.1700:0d:3a:37:67:0e 5.0.0-1020-azure100 13.91.6.207 00:0d:3a:3a:cc:2c 5.0.0-1020-azure100 40.78.30.12900:0d:3a:36:6e:eb 5.0.0-1020-azure100 104.210.36.238 00:0d:3a:5a:73:da 5.0.0-1020-azure100 13.91.6.143 00:0d:3a:3a:c8:ec 5.0.0-1020-azure100 40.83.249.5800:0d:3a:3a:c0:7a 5.0.0-1020-azure100 104.45.216.53 00:0d:3a:3b:8a:55 5.0.0-1020-azure100 104.210.42.18 00:0d:3a:5a:73:5c 5.0.0-1020-azure100 40.78.27.21 00:0d:3a:3a:c9:19 5.0.0-1020-azure100 40.83.252.110 00:0d:3a:5a:79:93 5.0.0-1020-azure100 13.64.119.204 00:0d:3a:5a:7e:bc 5.0.0-1020-azure100 104.210.34.400:0d:3a:31:18:ee 5.0.0-1020-azure250 138.91.197.202 00:0d:3a:31:1d:c1 5.0.0-1020-azure94 [ HANG ] 138.91.196.241 00:0d:3a:31:15:2b 5.0.0-1020-azure250 104.210.33.44 00:0d:3a:31:16:f3 5.0.0-1020-azure250 40.83.248.7600:0d:3a:32:af:a7 5.0.0-1020-azure250 40.83.253.204 00:0d:3a:32:ba:09 5.0.0-1020-azure250 168.62.202.800:0d:3a:32:a0:11 5.0.0-1020-azure250 40.83.249.8 00:0d:3a:32:bd:ce 5.0.0-1020-azure250 40.83.249.9300:0d:3a:32:b7:32 5.0.0-1020-azure250 40.83.253.187 00:0d:3a:32:b9:cd 5.0.0-1020-azure250 23.99.9.88 00:0d:3a:37:96:c9 5.0.0-1020-azure250 104.40.29.184 00:0d:3a:36:9f:e0 5.0.0-1020-azure250 137.135.40.122 00:0d:3a:36:9f:eb 5.0.0-1020-azure250 137.135.49.43 00:0d:3a:36:92:aa 5.0.0-1020-azure250 138.91.251.800:0d:3a:37:9e:ef 5.0.0-1020-azure250 13.64.146.175 00:0d:3a:31:de:ee 5.0.0-1020-azure500 104.42.23.145 00:0d:3a:31:da:d7 5.0.0-1020-azure500 104.42.29.9900:0d:3a:31:d4:4f 5.0.0-1020-azure500 40.78.106.1200:0d:3a:31:d9:8a 5.0.0-1020-azure500 138.91.233.210 00:0d:3a:31:df:84 5.0.0-1020-azure500 104.42.25.3000:0d:3a:31:c9:a4 5.0.0-1020-azure500 13.64.150.6900:0d:3a:31:dd:47 5.0.0-1020-azure321 [ HANG ] 104.42.25.2300:0d:3a:31:d3:c9 5.0.0-1020-azure500 104.42.24.176 00:0d:3a:31:d8:36 5.0.0-1020-azure500 13.64.79.13300:0d:3a:31:d5:b4 5.0.0-1020-azure500 104.42.29.146 00:0d:3a:31:de:73 5.0.0-1020-azure500 104.42.19.191 00:0d:3a:31:d4:78 5.0.0-1020-azure500 40.118.249.118 00:0d:3a:31:db:20 5.0.0-1020-azure500 40.112.219.112 00:0d:3a:31:dc:da 5.0.0-1020-azure500 104.42.17.115 00:0d:3a:31:d3:21 5.0.0-1020-azure500 40.83.212.164 00:0d:3a:5a:ab:48 5.0.0-1020-azure500 52.160.123.400:0d:3a:36:0d:6a 5.0.0-1020-azure500 52.160.83.3700:0d:3a:5a:ab:79 5.0.0-1020-azure500 52.160.122.92 00:0d:3a:36:00:4c 5.0.0-1020-azure500 52.160.122.71 00:0d:3a:36:0f:bd 5.0.0-1020-azure500 52.160.123.12 00:0d:3a:36:04:39 5.0.0-1020-azure500 104.210.60.218 00:0d:3a:36:b6:25 5.0.0-1020-azure500 52.160.123.221 00:0d:3a:5a:a9:a3 5.0.0-1020-azure500 52.160.123.234 00:0d:3a:5a:a7:1c 5.0.0-1020-azure500 104.210.61.139 00:0d:3a:37:b7:84 5.0.0-1020-azure500 104.210.61.43 00:0d:3a:36:b5:96 5.0.0-1020-azure500 40.83.212.185 00:0d:3a:5a:af:9c 5.0.0-1020-azure500 52.160.82.111 00:0d:3a:5a:a9:a9 5.0.0-1020-azure500 52.160.82.167 00:0d:3a:5a:a7:17 5.0.0-1020-azure500 104.210.61.135 00:0d:3a:36:b3:97 5.0.0-1020-azure500 -- 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/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28
[Kernel-packages] [Bug 1844406] Re: xenial/linux-aws: 4.4.0-1095.106 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1844416 packages: main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Monday, 23. September 2019 22:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff replaces: bug 1842597 trackers: xenial/linux-aws/aws-kernel: bug 1844405 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/1844406 Title: xenial/linux-aws: 4.4.0-1095.106 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1844416 packages: main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Monday, 23. September 2019 22:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff replaces: bug 1842597 trackers: xenial/linux-aws/aws-kernel: bug 1844405 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844406] Re: xenial/linux-aws: 4.4.0-1095.106 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1844406 Title: xenial/linux-aws: 4.4.0-1095.106 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1844416 packages: main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Monday, 23. September 2019 22:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- security signoff not verified security-signoff: Stalled -- waiting for signoff replaces: bug 1842597 trackers: xenial/linux-aws/aws-kernel: bug 1844405 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance
So the best way to reproduce this issue is to run ~500 reboots across multiple instances rather than 5000-1 reboots on once instance. -- 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/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812352] Re: Handle the skip return code in kernel_selftests
** Tags added: sru-20190902 ** Tags added: linux-kvm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812352 Title: Handle the skip return code in kernel_selftests Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: New Status in linux source package in Bionic: New Bug description: In the selftests tool, we are using a KSFT_SKIP=4 return code for those skipped tests in the latest upstream kernel tree. But the corresponding code to take care of this return value does not exist in Bionic and Xenial kernel, this will cause the test still being marked as failed: selftests: test_user_copy.sh user: module test_user_copy is not found [SKIP] not ok 1..1 selftests: test_user_copy.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760087] Re: net test in ubuntu_kernel_selftest failed on linux-kvm
** Tags added: bionic ** Tags added: linux-kvm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1760087 Title: net test in ubuntu_kernel_selftest failed on linux-kvm Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Steps: 1. Deploy a KVM node with Xenial, install linux-kvm on it. 2. git clone --depth 1 https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial linux 3. Run the "net" sub set in the kernel_selftest Result: * test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory * test_bpf: [FAIL] * selftests: test_bpf.sh [FAIL] Output: $ sudo make -C linux/tools/testing/selftests/net all run_tests make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make: Nothing to be done for 'all'. running socket test [PASS] selftests: run_netsocktests [PASS] running psock_fanout test test: control single socket test: control multiple sockets test: datapath 0x0 info: count=0,0, expect=0,0 info: count=15,5, expect=15,5 info: count=20,5, expect=20,5 test: datapath 0x1000 info: count=0,0, expect=0,0 info: count=15,5, expect=15,5 info: count=20,15, expect=20,15 test: datapath 0x1 info: count=0,0, expect=0,0 info: count=10,10, expect=10,10 info: count=18,17, expect=18,17 test: datapath 0x3 info: count=0,0, expect=0,0 info: count=15,5, expect=15,5 info: count=20,15, expect=20,15 test: datapath 0x6 info: count=0,0, expect=0,0 info: count=5,15, expect=15,5 info: count=20,15, expect=15,20 test: datapath 0x7 bpf: Function not implemented bpf verifier: ���ߟ [FAIL] running psock_tpacket test test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory [FAIL] selftests: run_afpackettests [PASS] test_bpf: [FAIL] selftests: test_bpf.sh [FAIL] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 30 12:12:46 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1760087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688587] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [khugepaged:38]
assuming this got fixed since then, reopen if not ** Package changed: linux-meta-hwe-edge (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1688587 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [khugepaged:38] Status in linux package in Ubuntu: Invalid Bug description: On kernel 4.10 from the linux-hwe-edge package, I'm experiencing frequent freezes on my surface pro 3. This starts mostly when using firefox, where first firefox freezes (window is becoming grey). When I don't close firefox immediately (killing it, as its window greyed out), the complete system kinda locks up. When I kill it, its process is still as defunct visible in the process list, and I can't start a new instance of firefox. When I don't kill it, the NMI watchdog BUG occurs shortly after and I have to shut down the system via power button. It's not completely dead, as I can still ping the device and when I'm ssh'd into it, the shell is not completely dead. I'm having a tail -f /var/log/syslog open via ssh, as I can't look into it anymore when the desktop environment locked up. Here I can close the tail -f command, but can't start any new processes. This did not happen with the linux-signed-image-generic-hwe-16.04 (4.8.0.51.22) yet. apt-cache policy linux-image-generic-hwe-16.04-edge: 4.10.0.20.13 lsb_release -rd: Ubuntu 16.04.2 LTS I attached the excerpt of /var/log/syslog. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04-edge (not installed) ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 5 16:41:03 2017 InstallationDate: Installed on 2015-11-12 (540 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-hwe-edge UpgradeStatus: Upgraded to xenial on 2016-07-29 (279 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811072] Re: df locks up with 100% cpu with zfs on usb, df unkillable
assuming fixed in later versions, reopen if not ** Package changed: linux-meta-hwe-edge (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811072 Title: df locks up with 100% cpu with zfs on usb, df unkillable Status in linux package in Ubuntu: Invalid Bug description: Last reproduced with linux-image-generic-hwe-18.04-edge 4.18.0.13.62 on bionic with cpu AMD Ryzen 7 1700 Eight-Core Processor external usb hdd drive /dev/disk/by-id/usb-WD_My_Passport_0820_5758353x:0-part1 luks encrypted partition zfs pool zfs pool used only for backups using syncoid initially after zpool import -a `df -h` works 30 minutes later `df -h` hangs, doesn't print any output at all, probably after a zfs receive df process using 100% cpu kill -KILL has no change in df process, it doesn't die, it's still in R and using 100% cpu strace -p hangs, doesn't print any output, also can't be killed unplugging the usb doesn't have any effect, df still in R at 100% cpu reproducible, happens every time. I can't reproduce with kernel 4.15.0-43-generic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1745169] Re: Kernel tried to execute NX-protected page - exploit attempt?
** Changed in: linux-meta-hwe-edge (Ubuntu) Status: New => Invalid -- 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/1745169 Title: Kernel tried to execute NX-protected page - exploit attempt? Status in linux-azure package in Ubuntu: Fix Released Status in linux-meta-hwe-edge package in Ubuntu: Invalid Bug description: Hi, This morning I had an issue in the install of elasticsearch-2.4.6, and when I have a look in journalctl, I have this BUG: unable to handle kernel paging request at 7f7d7d67e7a0 My configuration: elasticsearch@es-usb:~$ uname -r 4.13.0-1006-azure When I do the downgrade on the 4.11.0-1016-azure kernel version, everything is working well. More information of my journalctl: Jan 24 12:12:53 es-usb systemd[1]: Starting Elasticsearch... Jan 24 12:12:53 es-usb systemd[1]: Started Elasticsearch. Jan 24 12:12:53 es-usb sudo[18774]: pam_unix(sudo:session): session closed for user root Jan 24 12:12:55 es-usb kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 1000) Jan 24 12:12:55 es-usb kernel: BUG: unable to handle kernel paging request at 7f7d7d67e7a0 Jan 24 12:12:55 es-usb kernel: IP: 0x7f7d7d67e7a0 Jan 24 12:12:55 es-usb kernel: PGD 8001b6e97067 Jan 24 12:12:55 es-usb kernel: P4D 8001b6e97067 Jan 24 12:12:55 es-usb kernel: PUD 1b55fd067 Jan 24 12:12:55 es-usb kernel: PMD 1b55fc067 Jan 24 12:12:55 es-usb kernel: PTE 8001aa5ac867 Jan 24 12:12:55 es-usb kernel: Jan 24 12:12:55 es-usb kernel: Oops: 0011 [#7] SMP PTI Jan 24 12:12:55 es-usb kernel: Modules linked in: xt_nat xt_tcpudp veth ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc overlay xt_multiport iptable_filter nf_conntrack_ipv4 n Jan 24 12:12:55 es-usb kernel: hyperv_keyboard hid cfbimgblt cfbcopyarea hv_utils ptp pps_core hv_netvsc Jan 24 12:12:55 es-usb kernel: CPU: 0 PID: 18809 Comm: java Tainted: G D 4.13.0-1006-azure #8-Ubuntu Jan 24 12:12:55 es-usb kernel: Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 Jan 24 12:12:55 es-usb kernel: task: 9c04b5e42e80 task.stack: b490c5aa Jan 24 12:12:55 es-usb kernel: RIP: 0010:0x7f7d7d67e7a0 Jan 24 12:12:55 es-usb kernel: RSP: 0018:b490c5aa3f50 EFLAGS: 00010202 Jan 24 12:12:55 es-usb kernel: RAX: 03e7 RBX: RCX: 7f7d7cf914d9 Jan 24 12:12:55 es-usb kernel: RDX: 7f7d7d67ef50 RSI: 7f7d7d67f030 RDI: Jan 24 12:12:55 es-usb kernel: RBP: R08: R09: 000c Jan 24 12:12:55 es-usb kernel: R10: 7f7d7d67e7a0 R11: 9c04b5e42e80 R12: Jan 24 12:12:55 es-usb kernel: R13: R14: R15: Jan 24 12:12:55 es-usb kernel: FS: 7f7d7d680700() GS:9c04b9e0() knlGS: Jan 24 12:12:55 es-usb kernel: CS: 0010 DS: ES: CR0: 80050033 Jan 24 12:12:55 es-usb kernel: CR2: 7f7d7d67e7a0 CR3: 0001a33b8000 CR4: 001406f0 Jan 24 12:12:55 es-usb kernel: Call Trace: Jan 24 12:12:55 es-usb kernel: ? entry_SYSCALL_64_fastpath+0x33/0xa3 Jan 24 12:12:55 es-usb kernel: Code: Bad RIP value. Jan 24 12:12:55 es-usb kernel: RIP: 0x7f7d7d67e7a0 RSP: b490c5aa3f50 Jan 24 12:12:55 es-usb kernel: CR2: 7f7d7d67e7a0 Jan 24 12:12:55 es-usb kernel: ---[ end trace 3100a53c6de7c0c4 ]--- Thanks for your help Damien To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1745169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804898] Re: System crashes hard after Intel GPU hang
fixed in 5.0 ** Package changed: linux-meta-hwe-edge (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804898 Title: System crashes hard after Intel GPU hang Status in linux package in Ubuntu: Fix Released Bug description: With any kernel starting from 4.18-rc1, if the system has an Intel GPU and suffers a GPU hang, the system will crash a bit later, mostly when another demanding tasks is started or finished. This crash or leaves nothing in the logs or ends corrupting the logs, making it nigh impossible to get relevant information about it. The crash was observed after GPU hangs caused by multiple applications, from web browsers to games using DXVK. The upstream bug is at https://bugs.freedesktop.org/show_bug.cgi?id=107945 While this bug is not new on upstream, soon Ubuntu Bionic Beaver will have 4.18 available, so I think it's relevant to report this here too. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-signed-lowlatency-hwe-18.04-edge 4.18.0.12.61 ProcVersionSignature: Ubuntu 4.18.0-12.13~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-12-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Nov 23 20:55:28 2018 InstallationDate: Installed on 2017-06-13 (527 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-meta-hwe-edge UpgradeStatus: Upgraded to bionic on 2017-10-20 (399 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804898/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688587] [NEW] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [khugepaged:38]
You have been subscribed to a public bug: On kernel 4.10 from the linux-hwe-edge package, I'm experiencing frequent freezes on my surface pro 3. This starts mostly when using firefox, where first firefox freezes (window is becoming grey). When I don't close firefox immediately (killing it, as its window greyed out), the complete system kinda locks up. When I kill it, its process is still as defunct visible in the process list, and I can't start a new instance of firefox. When I don't kill it, the NMI watchdog BUG occurs shortly after and I have to shut down the system via power button. It's not completely dead, as I can still ping the device and when I'm ssh'd into it, the shell is not completely dead. I'm having a tail -f /var/log/syslog open via ssh, as I can't look into it anymore when the desktop environment locked up. Here I can close the tail -f command, but can't start any new processes. This did not happen with the linux-signed-image-generic-hwe-16.04 (4.8.0.51.22) yet. apt-cache policy linux-image-generic-hwe-16.04-edge: 4.10.0.20.13 lsb_release -rd: Ubuntu 16.04.2 LTS I attached the excerpt of /var/log/syslog. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04-edge (not installed) ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 5 16:41:03 2017 InstallationDate: Installed on 2015-11-12 (540 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-hwe-edge UpgradeStatus: Upgraded to xenial on 2016-07-29 (279 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug xenial -- NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [khugepaged:38] https://bugs.launchpad.net/bugs/1688587 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811072] [NEW] df locks up with 100% cpu with zfs on usb, df unkillable
You have been subscribed to a public bug: Last reproduced with linux-image-generic-hwe-18.04-edge 4.18.0.13.62 on bionic with cpu AMD Ryzen 7 1700 Eight-Core Processor external usb hdd drive /dev/disk/by-id/usb-WD_My_Passport_0820_5758353x:0-part1 luks encrypted partition zfs pool zfs pool used only for backups using syncoid initially after zpool import -a `df -h` works 30 minutes later `df -h` hangs, doesn't print any output at all, probably after a zfs receive df process using 100% cpu kill -KILL has no change in df process, it doesn't die, it's still in R and using 100% cpu strace -p hangs, doesn't print any output, also can't be killed unplugging the usb doesn't have any effect, df still in R at 100% cpu reproducible, happens every time. I can't reproduce with kernel 4.15.0-43-generic. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid -- df locks up with 100% cpu with zfs on usb, df unkillable https://bugs.launchpad.net/bugs/1811072 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804898] [NEW] System crashes hard after Intel GPU hang
You have been subscribed to a public bug: With any kernel starting from 4.18-rc1, if the system has an Intel GPU and suffers a GPU hang, the system will crash a bit later, mostly when another demanding tasks is started or finished. This crash or leaves nothing in the logs or ends corrupting the logs, making it nigh impossible to get relevant information about it. The crash was observed after GPU hangs caused by multiple applications, from web browsers to games using DXVK. The upstream bug is at https://bugs.freedesktop.org/show_bug.cgi?id=107945 While this bug is not new on upstream, soon Ubuntu Bionic Beaver will have 4.18 available, so I think it's relevant to report this here too. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-signed-lowlatency-hwe-18.04-edge 4.18.0.12.61 ProcVersionSignature: Ubuntu 4.18.0-12.13~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-12-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Nov 23 20:55:28 2018 InstallationDate: Installed on 2017-06-13 (527 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-meta-hwe-edge UpgradeStatus: Upgraded to bionic on 2017-10-20 (399 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: amd64 apport-bug bionic package-from-proposed -- System crashes hard after Intel GPU hang https://bugs.launchpad.net/bugs/1804898 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844680] Re: Thunderbolt support for ICL
My WIP branch for Eoan kernel: https://code.launchpad.net/~vicamo/+git /ubuntu-kernel/+ref/bug-1844680/wip/eoan . This has integrated proposed change for intel lpss/mtrr overlap issue tracked in https://bugzilla.kernel.org/show_bug.cgi?id=203485 . ** Bug watch added: Linux Kernel Bug Tracker #203485 https://bugzilla.kernel.org/show_bug.cgi?id=203485 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844680 Title: Thunderbolt support for ICL Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: In Progress Bug description: v5.4 has commits to fix Thunderbolt support for ICL ce19f91eae43e39 thunderbolt: Correct path indices for PCIe tunnel f437c24bf694b02 thunderbolt: Move NVM upgrade support flag to struct icm 943795219d3cb9f thunderbolt: Use 32-bit writes when writing ring producer/consumer d94dcbb10183f3b thunderbolt: Do not fail adding switch if some port is not implemented 58f414fa435cf72 thunderbolt: Hide switch attributes that are not set 3f415e5ee18b009 thunderbolt: Expose active parts of NVM even if upgrade is not supported 3cdb9446a117d5d thunderbolt: Add support for Intel Ice Lake dfda204198848b4 ACPI / property: Add two new Thunderbolt property GUIDs to the list To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1844680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845454] Re: Kernel panic with 19.10 beta image
I agree this looks the same as the bug reported against fedora. I've
started a test build with these commits. I know this was reported with
the ISO image, but hopefully we can work out a way to test. I suspect
disabling the tpm in the firmware settings will get the machine to
boot/install, and then it could be re-enabled to confirm that the panic
still happens with the kernel from -release and to check whether it is
gone in the test build.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845454
Title:
Kernel panic with 19.10 beta image
Status in linux package in Ubuntu:
Incomplete
Bug description:
Image: http://cdimage.ubuntu.com/daily-live/20190926/eoan-desktop-amd64.iso
Device: Dell XPS 13 7390 (201908-27305)
When trying to start the live session ("try Ubuntu") or trying to
install the ISO ("install Ubuntu"), the boot process stops within 1
second with a kernel panic (see attached screenshot).
The system could boot with a previous version of Eoan image:
2019-09-09 09:11 (kernel 5.3.0-10)
Workaround: disable TPM2 in the BIOS.
/!\ Please note: the information below (and the attached file
ProcCpuinfoMinimal.txt) come from a 18.04 live session, since I cannot boot
anything with 19.10 beta image.
==
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: syslinux 3:6.03+dfsg1-2
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 07:41:16 2019
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
mtools 4.0.18-2ubuntu1
syslinux-common 3:6.03+dfsg1-2
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: syslinux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed
** Tags added: sru-20190902 ** Tags removed: cosmic ** Tags added: bionic ** Tags added: linux-aws-edge -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812622 Title: fib related test in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: New Status in linux source package in Disco: New Status in linux-aws source package in Disco: New Status in linux-kvm source package in Disco: New Bug description: These tests: * fib_tests.sh * fib-onlink-tests.sh * fib_rule_tests.sh All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not supported: selftests: net: fib_tests.sh Single path route test RTNETLINK answers: Operation not supported not ok 1..11 selftests: net: fib_tests.sh [FAIL] selftests: net: fib-onlink-tests.sh Configuring interfaces RTNETLINK answers: Operation not supported not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL] selftests: net: fib_rule_tests.sh RTNETLINK answers: Operation not supported not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL] (works on generic Cosmic kernel) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6 ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17 Uname: Linux 4.18.0-1006-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Mon Jan 21 08:00:22 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822246] Re: binfmt_misc02 in LTP kernel/fs/ failed with Bionic
** Tags added: linux-aws-edge -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822246 Title: binfmt_misc02 in LTP kernel/fs/ failed with Bionic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Found on a KVM node, I think this test case might need some investigation, as the LTP suite should be chop down into pieces like the syscalls variant. <<>> tag=binfmt_misc02 stime=1553796942 cmdline="binfmt_misc02.sh" contacts="" analysis=exit <<>> binfmt_misc02 1 TINFO: timeout per run is 0h 5m 0s binfmt_misc02 1 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 2 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 3 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 4 TFAIL: Recognise a disabled binary type successfully binfmt_misc02 5 TFAIL: Recognise a binary type successfully binfmt_misc02 6 TFAIL: Recognise a binary type successfully binfmt_misc02 7 TINFO: AppArmor enabled, this may affect test results binfmt_misc02 7 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 (requires super/root) binfmt_misc02 7 TINFO: loaded AppArmor profiles: none Summary: passed 0 failed 6 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=14 cstime=6 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 29 06:45 seq crw-rw 1 root audio 116, 33 Mar 29 06:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 29 06:48:07 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829978] Re: cpuacct_100_100 from controllers test suite in LTP failed
** Tags added: aws linux-aws-edge -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829978 Title: cpuacct_100_100 from controllers test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Fix Released Bug description: startup='Wed May 22 06:50:45 2019' cpuacct 1 TINFO: timeout per run is 0h 5m 0s cpuacct 1 TINFO: cpuacct: /sys/fs/cgroup/cpu,cpuacct cpuacct 1 TINFO: Creating 100 subgroups each with 100 processes /opt/ltp/testcases/bin/cpuacct.sh: -2110094999: /opt/ltp/testcases/bin/cpuacct.sh: Cannot fork tag=cpuacct_100_100 stime=1558507845 dur=9 exit=exited stat=2 core=no cu=30 cs=53 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 06:59:27 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed
** Tags added: linux-aws-edge -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829979 Title: memcg_max_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: startup='Wed May 22 05:58:50 2019' memcg_max_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_max_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 1 TINFO: Warming up pid: 30821 memcg_max_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 30821 memcg_max_usage_in_bytes_test 1 TFAIL: memory.max_usage_in_bytes is 4325376, 4194304 expected memcg_max_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TCONF: mem+swap is not enabled memcg_max_usage_in_bytes_test 2 TINFO: Starting test 3 sh: echo: I/O error memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_max_usage_in_bytes_test 2 TINFO: Warming up pid: 30855 memcg_max_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 30855 memcg_max_usage_in_bytes_test 2 TFAIL: memory.max_usage_in_bytes is 4329472, 4194304 expected memcg_max_usage_in_bytes_test 3 TFAIL: memory.max_usage_in_bytes is 8192, 0 expected memcg_max_usage_in_bytes_test 4 TINFO: Starting test 4 sh: echo: I/O error memcg_max_usage_in_bytes_test 4 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_max_usage_in_bytes_test 4 TCONF: mem+swap is not enabled tag=memcg_max_usage_in_bytes stime=1558504730 dur=3 exit=exited stat=33 core=no cu=8 cs=7 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:06:31 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837543] Re: crypto_user02 in crypto from ubuntu_ltp failed
** Tags added: linux-aws-edge -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837543 Title: crypto_user02 in crypto from ubuntu_ltp failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Status in linux source package in Eoan: Confirmed Bug description: This is a new test, test will fail with: <<>> tag=crypto_user02 stime=1563881396 cmdline="crypto_user02" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s crypto_user02.c:59: INFO: Starting crypto_user larval deletion test. May crash buggy kernels. crypto_user02.c:91: BROK: unexpected error from tst_crypto_del_alg(): EBUSY Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> Nothing interesting in syslog: Jul 23 11:29:20 amaura systemd[1]: Started Session 1 of user ubuntu. Jul 23 11:29:56 amaura kernel: [ 619.646330] LTP: starting crypto_user02 Jul 23 11:30:23 amaura kernel: [ 646.554403] cfg80211: Loading compiled-in X.509 certificates for regulatory database Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "crypto_user02 crypto_user02" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-21-generic 5.0.0-21.22 ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 23 11:19 seq crw-rw 1 root audio 116, 33 Jul 23 11:19 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 23 11:30:15 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.178.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.sku: To be filled by O.E.M. dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819116] Re: sync_file_range02 in ubuntu_ltp_syscalls fails
** Tags added: sru-20190902 -- 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/1819116 Title: sync_file_range02 in ubuntu_ltp_syscalls fails Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux-gke source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-aws source package in Cosmic: New Status in linux-azure source package in Cosmic: New Status in linux source package in Disco: Incomplete Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: New Status in linux source package in Eoan: Incomplete Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Status in linux-gke source package in Eoan: New Bug description: syslog output attached as attachment. <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_supported_fs_types.c:72: INFO: Kernel supports ext2 tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext3 tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext4 tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist tst_supported_fs_types.c:72: INFO: Kernel supports xfs tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports btrfs tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports vfat tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported tst_supported_fs_types.c:72: INFO: Kernel supports ntfs tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist tst_test.c:1157: INFO: Testing on ext2 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ext3 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ext4 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on vfat tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ntfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts='' The partition start sector was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. The number of sectors per track was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. The number of heads was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set. Windows will not be able to boot from this device. safe_macros.c:739: INFO: Trying FUSE... tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:56: FAIL: Synced 0, expected 33554432 Summary: passed 6 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=11 termination_type=exited termination_id=1 corefile=no cutime=10 cstime=157 <<>> INFO: ltp-pan reported some tests FAIL LTP Version: 20190115 ### Done executing testcases. LTP Version:
[Kernel-packages] [Bug 1845127] Re: bionic/linux-gcp: 5.0.0-1019.19~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: 1845128 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Wednesday, 25. September 2019 22:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1844346 trackers: bionic/linux-gcp-edge: bug 1844345 bionic/linux-gcp/gcp-kernel: bug 1845126 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1845127 Title: bionic/linux-gcp: 5.0.0-1019.19~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug 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: 1845128 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Wednesday, 25. September 2019 22:35 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 replaces: bug 1844346 trackers: bionic/linux-gcp-edge: bug 1844345 bionic/linux-gcp/gcp-kernel: bug 1845126 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829982] Re: ltp_acpi from kernel_misc test suite in LTP failed
** Tags added: linux-aws-edge -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829982 Title: ltp_acpi from kernel_misc test suite in LTP failed Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: New Bug description: startup='Wed May 22 07:02:13 2019' ltp_acpi1 TPASS : Test-case '0' ltp_acpi2 TPASS : Test-case '1' ltp_acpi3 TPASS : Test-case '2' ltp_acpi4 TPASS : Test-case '3' ltp_acpi5 TPASS : Test-case '4' ltp_acpi6 TPASS : Test-case '5' ltp_acpi7 TPASS : Test-case '6' ltp_acpi8 TPASS : Test-case '7' ltp_acpi9 TFAIL : ltp_acpi.c:139: Test-case '8' ltp_acpi 10 TPASS : Test-case '9' tag=ltp_acpi stime=1558508533 dur=0 exit=exited stat=1 core=no cu=0 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-20-generic 4.18.0-20.21 ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 06:28 seq crw-rw 1 root audio 116, 33 May 22 06:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 07:15:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-20-generic N/A linux-backports-modules-4.18.0-20-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
I tested an upgrade from Ubuntu 18.10 to Ubuntu 19.04 today with some of the packages from the DuplicateSignature.txt installed e.g.: Start-Date: 2019-09-25 17:14:37 Commandline: apt-get install bamfdaemon mime-support Requested-By: bdmurray (1000) Install: bamfdaemon:amd64 (0.5.3+18.04.20180207.2-0ubuntu1), libbamf3-2:amd64 (0.5.3+18.04.20180207.2-0ubuntu1, automatic) End-Date: 2019-09-25 17:14:38 Start-Date: 2019-09-25 17:15:21 Commandline: apt-get install libvlc-bin gnome-icon-theme hicolor-icon-theme Requested-By: bdmurray (1000) Install: gnome-icon-theme:amd64 (3.12.0-3), libvlc5:amd64 (3.0.4-2build1, automatic), libvlccore9:amd64 (3.0.4-2build1, automatic), libvlc-bin:amd64 (3.0.4-2build1), libproxy-tools:amd64 (0.4.15-2, automatic) End-Date: 2019-09-25 17:15:29 The upgraded proceeded without issue and I did not encounter any issues with triggers looping. -- 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/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: Invalid Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash 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. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838961] Re: timer_create01 from ubuntu_ltp_syscalls failed on X-kvm / B-KVM
** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: linux-kvm (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1838961 Title: timer_create01 from ubuntu_ltp_syscalls failed on X-kvm / B-KVM Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: In Progress Status in linux-kvm source package in Xenial: New Status in linux-kvm source package in Bionic: New Bug description: The timer_create01 failed on X-kvm Steps to reproduce: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "timer_create01 timer_create01" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs <<>> tag=timer_create01 stime=1565000454 cmdline="timer_create01" contacts="" analysis=exit <<>> tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s incrementing stop timer_create01.c:48: INFO: Testing notification type: SIGEV_NONE timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: SIGEV_SIGNAL timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: SIGEV_THREAD timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: SIGEV_THREAD_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI timer_create01.c:48: INFO: Testing notification type: NULL timer_create01.c:93: PASS: Timer successfully created for CLOCK_REALTIME timer_create01.c:93: PASS: Timer successfully created for CLOCK_MONOTONIC timer_create01.c:93: PASS: Timer successfully created for CLOCK_PROCESS_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_THREAD_CPUTIME_ID timer_create01.c:93: PASS: Timer successfully created for CLOCK_BOOTTIME timer_create01.c:87: FAIL: Failed to create timer for CLOCK_BOOTTIME_ALARM: ??? timer_create01.c:87: FAIL: Failed to create timer for CLOCK_REALTIME_ALARM: ??? timer_create01.c:93: PASS: Timer successfully created for CLOCK_TAI Summary: passed 30 failed 10 skipped 0 warnings 0 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1052-kvm 4.4.0-1052.59 ProcVersionSignature: User Name 4.4.0-1052.59-kvm 4.4.181 Uname: Linux 4.4.0-1052-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Mon Aug 5 10:17:57 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1844362] Re: disco/linux: 5.0.0-30.32 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Signoff phase-changed: Wednesday, 25. September 2019 11:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842561 trackers: bionic/linux-hwe: bug 1844360 bionic/linux-oem-osp1: bug 1844361 disco/linux-aws: bug 1844338 disco/linux-azure: bug 1844343 disco/linux-gcp: bug 1845128 disco/linux-kvm: bug 1844353 - disco/linux-oracle: bug 1844358, bug 1845436 + disco/linux-oracle: bug 1845436, bug 1844358 disco/linux-raspi2: bug 1844336 disco/linux-snapdragon: bug 1844359 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/1844362 Title: disco/linux: 5.0.0-30.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed 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: Signoff phase-changed: Wednesday, 25. September 2019 11:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress replaces: bug 1842561 trackers: bionic/linux-hwe: bug 1844360 bionic/linux-oem-osp1: bug 1844361 disco/linux-aws: bug 1844338 disco/linux-azure: bug 1844343 disco/linux-gcp: bug 1845128 disco/linux-kvm: bug 1844353 disco/linux-oracle: bug 1845436, bug 1844358 disco/linux-raspi2: bug 1844336 disco/linux-snapdragon: bug 1844359 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1844362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844926] Re: Kernel panic when booting Razer Blade 15" 2018
I'm willing to try, but I honestly don't really know how to do that safely and in an orderly fashion. Is there a written guide I can use? Which versions should be tested? On the first look I don't see more versions in eoan. Am I supposed to compile them myself? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844926 Title: Kernel panic when booting Razer Blade 15" 2018 Status in linux package in Ubuntu: Confirmed Bug description: A few days ago I decided to test the upcoming 19.10 release. After rebooting, I faced a very early kernel panic. The whole disk is encrypted and I couldn't even reach the decryption phase where it asks for the password. The kernel package is `linux-image-generic/eoan,now 5.3.0.10.11` I am currently running 5.0.0-29-generic without problems. I don't have any versions installed in-between those two. Following https://wiki.ubuntu.com/DebuggingKernelBoot I collected photos of the kernel booting. There is a little bit scrolled out, but it scrolls way too fast for me to capture even on video. Please let me know if I can provide any further information. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-generic 5.3.0.10.11 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tamas 1813 F pulseaudio /dev/snd/controlC0: tamas 1813 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Sep 22 14:56:18 2019 InstallationDate: Installed on 2019-06-09 (104 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1532:0233 Razer USA, Ltd Razer Blade Bus 001 Device 003: ID 1bcf:2c9a Sunplus Innovation Technology Inc. USB Camera Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Razer Blade ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.182 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-09-20 (1 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: Razer dmi.bios.version: 1.06 dmi.board.name: C1_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr1.06:bd09/05/2018:svnRazer:pnBlade:pvr1.05:rvnRazer:rnC1_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582000 Razer Blade dmi.product.name: Blade dmi.product.sku: RZ09-02385W92 dmi.product.version: 1.05 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845128] Re: disco/linux-gcp: 5.0.0-1019.19 -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: 1844362 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Wednesday, 25. September 2019 21:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1845127 bionic/linux-gke-5.0: bug 1845131 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1845128 Title: disco/linux-gcp: 5.0.0-1019.19 -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: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1844362 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Wednesday, 25. September 2019 21:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1845127 bionic/linux-gke-5.0: bug 1845131 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845323] Re: Trying to online dasd drive results in invalid input/output from the kernel on z/VM
** Summary changed: - Trying to online dasd drive results in invalid input/output from the kernel + Trying to online dasd drive results in invalid input/output from the kernel on z/VM ** Tags added: bot-stop-nagging ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel (canonical-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/1845323 Title: Trying to online dasd drive results in invalid input/output from the kernel on z/VM Status in linux package in Ubuntu: Confirmed Bug description: Sep 25 12:06:39 s390-dasd[4637]: ECKD DASD 0.0.0200 configure failed Sep 25 12:06:39 s390-dasd[4637]: Error: Could not write file /sys/bus/ccw/drivers/dasd-eckd/0.0.0200/online: Input/output error Sep 25 12:06:39 s390-dasd[4637]: Configuring devices in the active configuration only Sep 25 12:06:39 main-menu[421]: WARNING **: Configuring 's390-dasd' failed with error code 1 Sep 25 12:06:39 main-menu[421]: WARNING **: Menu item 's390-dasd' failed. Sep 25 12:06:39 kernel: [ 137.472853] dasd-eckd.401b68: 0.0.0200: A channel path to the device has become operational Sep 25 12:06:39 kernel: [ 137.473914] dasd-eckd.6b7759: 0.0.0200: Reading the volume storage information failed with rc=-5 Sep 25 12:06:39 kernel: [ 137.473917] dasd.3e7d29: 0.0.0200 Setting the DASD online with discipline ECKD failed with rc=-5 Sep 25 12:06:39 kernel: [ 137.473918] [ cut here ] Sep 25 12:06:39 kernel: [ 137.473943] WARNING: CPU: 0 PID: 4638 at kernel/module.c:1137 module_put.part.0+0xe2/0xe8 Sep 25 12:06:39 kernel: [ 137.473944] Modules linked in: lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod qeth_l2 pkey crc32_vx_s390 qeth qdio zcrypt_cex4 ccwgroup zcrypt Sep 25 12:06:39 kernel: [ 137.473953] CPU: 0 PID: 4638 Comm: chzdev Not tainted 5.3.0-10-generic #11-Ubuntu Sep 25 12:06:39 kernel: [ 137.473954] Hardware name: IBM 2964 N63 400 (z/VM 6.4.0) Sep 25 12:06:39 kernel: [ 137.473955] Krnl PSW : 0704c0018000 2b2c3372 (module_put.part.0+0xe2/0xe8) Sep 25 12:06:39 kernel: [ 137.473958]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 Sep 25 12:06:39 kernel: [ 137.473959] Krnl GPRS: 0004 0006 0024 0007 Sep 25 12:06:39 kernel: [ 137.473960]0007 7f2ce800 fffb 03ff80151578 Sep 25 12:06:39 kernel: [ 137.473961]fffb 03ff80074df8 03ff80151900 78105800 Sep 25 12:06:39 kernel: [ 137.473962]7e17e600 0bf8 2b2c336e 03e000c5fb08 Sep 25 12:06:39 kernel: [ 137.473969] Krnl Code: 2b2c3362: c0200048859a larl%r2,2bbd3e96 Sep 25 12:06:39 kernel: [ 137.473969]2b2c3368: c0e5fffe16a4 brasl %r14,2b2860b0 Sep 25 12:06:39 kernel: [ 137.473969] #2b2c336e: a7f40001 brc 15,2b2c3370 Sep 25 12:06:39 kernel: [ 137.473969] >2b2c3372: a7f4ffb1 brc 15,2b2c32d4 Sep 25 12:06:39 kernel: [ 137.473969]2b2c3376: 0707 bcr 0,%r7 Sep 25 12:06:39 kernel: [ 137.473969]2b2c3378: c004 brcl0,2b2c3378 Sep 25 12:06:39 kernel: [ 137.473969]2b2c337e: ec280006007c cgij%r2,0,8,2b2c338a Sep 25 12:06:39 kernel: [ 137.473969]2b2c3384: c0f4ff86 brcl15,2b2c3290 Sep 25 12:06:39 kernel: [ 137.473980] Call Trace: Sep 25 12:06:39 kernel: [ 137.473982] ([<2b2c336e>] module_put.part.0+0xde/0xe8) Sep 25 12:06:39 kernel: [ 137.473994] [<03ff80074df8>] dasd_generic_free_discipline+0x68/0x80 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.473998] [<03ff8007f5ba>] dasd_delete_device+0x122/0x1c8 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.474001] [<03ff8007bcfa>] dasd_generic_set_online+0x2ea/0x310 [dasd_mod] Sep 25 12:06:39 kernel: [ 137.474006] [<2b84db48>] ccw_device_set_online+0x110/0x528 Sep 25 12:06:39 kernel: [ 137.474008] [<2b84dfb0>] online_store_recog_and_online+0x50/0x130 Sep 25 12:06:39 kernel: [ 137.474009] [<2b84f042>] online_store+0x1b2/0x2e0 Sep 25 12:06:39 kernel: [ 137.474013] [<2b50b7a0>] kernfs_fop_write+0xd8/0x1f8 Sep 25 12:06:39 kernel: [ 137.474017] [<2b4585f8>] vfs_write+0xb0/0x1b8 Sep 25 12:06:39 kernel: [ 137.474018] [<2b459eb8>] ksys_write+0x68/0xf8 Sep 25 12:06:39 kernel: [ 137.474023] [<2ba4c4b8>] system_call+0xdc/0x2c8 Sep 25 12:06:39 kernel: [ 137.474024] Last Breaking-Event-Address: Sep 25 12:06:39 kernel: [ 137.474025] [<2b2c336e>] module_put.part.0+0xde/0xe8 Sep 25 12:06:39 kernel: [
