[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
** Changed in: libvirt (Ubuntu Disco) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: libvirt (Ubuntu Bionic) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: libvirt (Ubuntu Eoan) Status: Fix Released => In Progress ** Changed in: libvirt (Ubuntu Eoan) Assignee: (unassigned) => Christian Ehrhardt (paelzer) ** No longer affects: libvirt (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: qemu (Ubuntu Cosmic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Released Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Released Status in libvirt source package in Eoan: In Progress Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840004] Re: xenial/linux-deeplens: 4.15.0-1006.6 -proposed tracker
** 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: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Packaging phase-changed: Monday, 19. August 2019 12:41 UTC reason: prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Stalled -- package tag not yet published 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/1840004 Title: xenial/linux-deeplens: 4.15.0-1006.6 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Packaging phase-changed: Monday, 19. August 2019 12:41 UTC reason: prepare-package: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840275] Re: disco/linux-azure: 5.0.0-1016.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 backports: bug 1840274 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Security - phase-changed: Monday, 19. August 2019 16:26 UTC + phase: Ready for Security + phase-changed: Tuesday, 20. August 2019 08:25 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: bionic/linux-azure: bug 1840274 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840275 Title: disco/linux-azure: 5.0.0-1016.17 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Disco: Fix Released 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 backports: bug 1840274 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Security phase-changed: Tuesday, 20. August 2019 08:25 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy trackers: bionic/linux-azure: bug 1840274 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840324] Re: bionic/linux-azure: 5.0.0-1017.18~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 derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Monday, 19. August 2019 22:25 UTC reason: automated-testing: Ongoing -- testing in progress - promote-to-proposed: Stalled -- packages are in the wrong component + promote-to-proposed: Ongoing -- package copied to Proposed lrm:building regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840324 Title: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Monday, 19. August 2019 22:25 UTC reason: automated-testing: Ongoing -- testing in progress promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840750] [NEW] [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests
Public bug reported: This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument [PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming[PASS] [39] Kprobe dynamic event with function tracer [PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco package-from-proposed uec-images ** Package changed: linux-signed-gcp (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1840750 Title: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests Status in linux package in Ubuntu: New Status in linux source package in Disco: New Bug description: This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument[PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer[PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840324] Re: bionic/linux-azure: 5.0.0-1017.18~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 derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Monday, 19. August 2019 22:25 UTC reason: automated-testing: Ongoing -- testing in progress - promote-to-proposed: Ongoing -- package copied to Proposed lrm:building + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840324 Title: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Monday, 19. August 2019 22:25 UTC reason: automated-testing: Ongoing -- testing in progress promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840004] Re: xenial/linux-deeplens: 4.15.0-1006.6 -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 ** 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: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens - phase: Packaging - phase-changed: Monday, 19. August 2019 12:41 UTC + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 20. August 2019 08:46 UTC reason: - prepare-package: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840004 Title: xenial/linux-deeplens: 4.15.0-1006.6 -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: 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 Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Holding before Promote to Proposed phase-changed: Tuesday, 20. August 2019 08:46 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840750] Re: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests
** Description changed: This issue is 100% reproducible. It looks like this has something to do - with the kernel in proposed + with the Disco kernel in proposed (5.0.0-1014.14). - Combinations: + Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK - + The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument[PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer[PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Description changed: This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument[PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer[PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe + Tried with use "tail -f /var/log/syslog" and "dmesg -w" to see what + happened, but it will just disconnected and reboot itself. + + ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840750 Title: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests Status in linux package in Ubuntu: New Status in linux source package in Disco: New Bug description: This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument[PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer[PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe Tried with use "tail -f /var/log/syslog" and "dmesg -w" to see what happened, but it will just disconnected and reboot itself. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgr
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/371504 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Released Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Released Status in libvirt source package in Eoan: In Progress Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
Recent libvirt versions (5.5) added more for arch_capabilities. Lets get that into Eoan before considering the SRUs back to Bionic afterwards. commit ver subject 2674d00e 5.5 qemu: Drop MSR features from host-model with old QEMU 8eb4a89f 5.5 qemu: Forbid MSR features with old QEMU c8ec678f 5.5 cpu_map: Introduce IA32_ARCH_CAPABILITIES MSR features 56b254dc 5.5 cpu_x86: Read CPU features from IA32_ARCH_CAPABILITIES MSR bcfed7f1 5.5 cpu_x86: Introduce virCPUx86FeatureFilter*MSR b8e086a5 5.5 cpu_x86: Turn virCPUx86DataIteratorInit into a function 4e6f58b8 5.5 conf: Introduce virCPUDefCheckFeatures 511df17a 5.0 cpu_map: Add support for arch-capabilities feature -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Released Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Released Status in libvirt source package in Eoan: In Progress Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
I started a test PPA [1] and an MP [2] to get this into Eoan. @Rafael could you test this on the same system you used last time and review the MP? [1]: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1828495-archcap-eoan [2]: https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/371504 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Released Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Released Status in libvirt source package in Eoan: In Progress Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840750] 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 1840750 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Disco) 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/1840750 Title: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Incomplete Bug description: This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument[PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer[PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe Tried with use "tail -f /var/log/syslog" and "dmesg -w" to see what happened, but it will just disconnected and reboot itself. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840674] Re: xenial/linux-gcp: 4.15.0-1041.43 -proposed tracker
** Summary changed: - xenial/linux-gcp: -proposed tracker + xenial/linux-gcp: 4.15.0-1041.43 -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) => Stefan Bader (smb) ** 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) => Stefan Bader (smb) ** 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) => Stefan Bader (smb) -- 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/1840674 Title: xenial/linux-gcp: 4.15.0-1041.43 -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-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 derivatives: bug 1840672 (gcp-kernel), bug 1840673 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1840006 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Tuesday, 20. August 2019 09:15 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 trackers: xenial/linux-gcp/gcp-kernel: bug 1840672 xenial/linux-gcp/gke-kernel: bug 1840673 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840674] Re: xenial/linux-gcp: 4.15.0-1041.43 -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 derivatives: bug 1840672 (gcp-kernel), bug 1840673 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1840006 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Ready for Packaging - phase-changed: Monday, 19. August 2019 14:12 UTC + phase: Packaging + phase-changed: Tuesday, 20. August 2019 09:15 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 trackers: xenial/linux-gcp/gcp-kernel: bug 1840672 xenial/linux-gcp/gke-kernel: bug 1840673 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/1840674 Title: xenial/linux-gcp: 4.15.0-1041.43 -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-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 derivatives: bug 1840672 (gcp-kernel), bug 1840673 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1840006 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Tuesday, 20. August 2019 09:15 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 trackers: xenial/linux-gcp/gcp-kernel: bug 1840672 xenial/linux-gcp/gke-kernel: bug 1840673 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Had the same issue with my Magic Trackpad. After reading this possibly related bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385113 I decided to disable upower: systemctl stop upower systemctl disable upower This works around the problem for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
I don't think that's recommended. As I understand it, disabling upower means to disable the power management for the entire machine :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: Applying InputClass "
[Kernel-packages] [Bug 1840324] Re: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Promote to Proposed - phase-changed: Monday, 19. August 2019 22:25 UTC + phase: Testing + phase-changed: Tuesday, 20. August 2019 10:15 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840324 Title: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed 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-azure package in Ubuntu: Invalid Status in linux-azure 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 derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 10:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840004] Re: xenial/linux-deeplens: 4.15.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug 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: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens - phase: Holding before Promote to Proposed - phase-changed: Tuesday, 20. August 2019 08:46 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 20. August 2019 10:40 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840004 Title: xenial/linux-deeplens: 4.15.0-1006.6 -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: 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 Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Tuesday, 20. August 2019 10:40 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
You can still do power management using any non-gnome power management tool. Somewhat annoying indeed, but less so than losing my trackpad every hour ;-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: Ap
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Please try adding kernel parameter: btusb.enable_autosuspend=0 (copied from bug 1801642) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: Applying InputClass "libinput touchpad catchall" de juny 13 2
[Kernel-packages] [Bug 1840750] Re: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840750 Title: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Incomplete Bug description: This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument[PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer[PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe Tried with use "tail -f /var/log/syslog" and "dmesg -w" to see what happened, but it will just disconnected and reboot itself. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840750] Re: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests
** Tags added: sru-20190812 ubuntu-kernel-selftests -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840750 Title: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument[PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer[PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe Tried with use "tail -f /var/log/syslog" and "dmesg -w" to see what happened, but it will just disconnected and reboot itself. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840750] Re: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests
I was able to get some kernel messages from a qemu console: [ 208.672687] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 208.673786] BUG: unable to handle kernel paging request at c054f694 [ 208.674779] #PF error: [PROT] [INSTR] [ 208.675571] PGD 45a12067 P4D 45a12067 PUD 45a14067 PMD 79808067 PTE 8000722f8061 [ 208.679132] Oops: 0011 [#1] SMP PTI [ 208.680526] CPU: 0 PID: 3836 Comm: ftracetest Not tainted 5.0.0-26-generic #27-Ubuntu [ 208.683102] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 208.686150] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 208.686150] BUG: unable to handle kernel paging request at c054feae [ 208.686151] #PF error: [PROT] [INSTR] [ 208.686151] PGD 45a12067 P4D 45a12067 PUD 45a14067 PMD 79808067 PTE 8000722f8061 [ 208.686152] Oops: 0011 [#2] SMP PTI [ 208.686153] CPU: 0 PID: 3836 Comm: ftracetest Not tainted 5.0.0-26-generic #27-Ubuntu [ 208.686153] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 208.686154] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 208.686154] BUG: unable to handle kernel paging request at c054feae [ 208.686154] #PF error: [PROT] [INSTR] [ 208.686154] PGD 45a12067 P4D 45a12067 PUD 45a14067 PMD 79808067 PTE 8000722f8061 [ 208.686156] Oops: 0011 [#3] SMP PTI [ 208.686156] CPU: 0 PID: 3836 Comm: ftracetest Not tainted 5.0.0-26-generic #27-Ubuntu [ 208.686156] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 208.686157] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 208.686168] BUG: unable to handle kernel paging request at c054feae [ 208.686169] #PF error: [PROT] [INSTR] [ 208.686169] PGD 45a12067 P4D 45a12067 PUD 45a14067 PMD 79808067 PTE 8000722f8061 [ 208.686170] Oops: 0011 [#4] SMP PTI [ 208.686170] CPU: 0 PID: 3836 Comm: ftracetest Not tainted 5.0.0-26-generic #27-Ubuntu [ 208.686170] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 208.686171] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 208.686171] BUG: unable to handle kernel paging request at c054feae [ 208.686171] #PF error: [PROT] [INSTR] [ 208.686171] PGD 45a12067 P4D 45a12067 PUD 45a14067 PMD 79808067 PTE 8000722f8061 [ 208.686172] Oops: 0011 [#5] SMP PTI [ 208.686173] CPU: 0 PID: 3836 Comm: ftracetest Not tainted 5.0.0-26-generic #27-Ubuntu [ 208.686173] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 208.686174] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 208.686174] BUG: unable to handle kernel paging request at c054feae [ 208.686174] #PF error: [PROT] [INSTR] [ 208.686174] PGD 45a12067 P4D 45a12067 PUD 45a14067 PMD 79808067 PTE 8000722f8061 [ 208.686176] Oops: 0011 [#6] SMP PTI [ 208.686176] CPU: 0 PID: 3836 Comm: ftracetest Not tainted 5.0.0-26-generic #27-Ubuntu [ 208.686176] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 208.686177] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 208.686177] BUG: unable to handle kernel paging request at c054feae [ 208.686177] #PF error: [PROT] [INSTR] [ 208.686177] PGD 45a12067 P4D 45a12067 PUD 45a14067 PMD 79808067 PTE 8000722f8061 [ 208.686178] Oops: 0011 [#7] SMP PTI [ 208.686179] CPU: 0 PID: 3836 Comm: ftracetest Not tainted 5.0.0-26-generic #27-Ubuntu [ 208.686179] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 208.686179] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 208.686180] BUG: unable to handle kernel paging request at c054feae [ 208.686180] #PF error: [PROT] [INSTR] [ 208.686180] PGD 45a12067 P4D 45a12067 PUD 45a14067 PMD 79808067 PTE 8000722f8061 [ 208.686181] Oops: 0011 [#8] SMP PTI [ 208.686182] CPU: 0 PID: 3836 Comm: ftracetest Not tainted 5.0.0-26-generic #27-Ubuntu [ 208.686182] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 208.686182] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 208.686183] BUG: unable to handle kernel paging request at c054feae [ 208.686183] #PF error: [PROT] [INSTR] [ 208.686183] PGD 45a12067 P4D 45a12067 PUD 45a14067 PMD 79808067 PTE 8000722f8061 [ 208.686184] Oops: 0011 [#9] SMP PTI [ 208.686184] CPU: 0 PID: 3836 Comm: ftracetest Not tainted 5.0.0-26-generic #27-Ubuntu [ 208.686185] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 208.686185] BUG: stack guard page was hit at 2ef8e073 (stack is dd001bee..b92ae6d7) [ 208.686185] kernel stack overflow (double-fault): [#10] SMP PTI [ 208.6861
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
Definitely! Will provide feedback soon! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Released Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Released Status in libvirt source package in Eoan: In Progress Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840750] Re: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests
Upstream discussion https://lkml.org/lkml/2019/6/9/781 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840750 Title: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument[PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer[PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe Tried with use "tail -f /var/log/syslog" and "dmesg -w" to see what happened, but it will just disconnected and reboot itself. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840326] Re: disco/linux-azure: 5.0.0-1017.18 -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 backports: bug 1840324 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839972 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 02:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Ongoing -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840324 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840326 Title: disco/linux-azure: 5.0.0-1017.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840324 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839972 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 02:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Ongoing -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840324 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840766] [NEW] Roll bionic/linux-gcp to 5.0
Public bug reported: With consent of Google we roll the GCP kernel in Bionic forward to be based on kernel version 5.0. This was provided as linux-gcp-edge before. While not directly related, this requires changes to how xenial/linux- gcp is maintained. Until now this was done as a backport of the bionic /linux-gcp but as xenial/linux-gcp is supposed to remain at kernel version 4.15 it has to become a derivative of bionic/linux. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-gcp (Ubuntu Xenial) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Affects: linux-gcp (Ubuntu Bionic) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Bionic) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux-gcp (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux-gcp (Ubuntu) Status: In Progress => Invalid ** Changed in: linux-gcp (Ubuntu) Assignee: Stefan Bader (smb) => (unassigned) ** Changed in: linux-gcp (Ubuntu) Importance: Medium => Undecided -- 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/1840766 Title: Roll bionic/linux-gcp to 5.0 Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: In Progress Status in linux-gcp source package in Bionic: In Progress Bug description: With consent of Google we roll the GCP kernel in Bionic forward to be based on kernel version 5.0. This was provided as linux-gcp-edge before. While not directly related, this requires changes to how xenial/linux- gcp is maintained. Until now this was done as a backport of the bionic /linux-gcp but as xenial/linux-gcp is supposed to remain at kernel version 4.15 it has to become a derivative of bionic/linux. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1840766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
Another bunch of related changes might be important. Not sure how much of that will go into SRUs - I hope not all of it. Already in Eoan we should try to use a reduced set or we could go directly to 5.5 which has other known issues. 63acb7bf qemu_process: Prefer generic qemuMonitorGetGuestCPU cc6d6b3c qemu: Introduce generic qemuMonitorGetGuestCPU 430023e5 qemu: Add type filter to qemuMonitorJSONParsePropsList df73078c cpu: Introduce virCPUDataAddFeature 055f8f6b qemu: Make qemuMonitorGetGuestCPU usable on x86 only a3f2c802 qemu: Don't use full CPU model expansion ec232c5d qemu: Translate feature names from query-cpu-model-expansion 5030a745 qemu_command: Use canonical names of CPU features 6f6401fb qemu: Probe host CPU after capabilities XX 0d254bce qemu: Probe for "unavailable-features" CPU property XX 2a4c2321 qemu: Probe for max-x86_64-cpu type 61ee757e qemu: Add APIs for translating CPU features 24aa210d qemuxml2argvtest: Add test for CPU features translation 0b763774 qemu: Filter CPU features in active XML XX c145b660 cpu_conf: Introduce virCPUDefFilterFeatures 955fd6e7 qemu_process: Drop cleanup label from qemuProcessUpdateGuestCPU b1286526 qemu: Drop qemuFeatureNoEffect I hope I might get away with only those I marked with XX, but still this keeps growing to an uncompfortable amount -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Released Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Released Status in libvirt source package in Eoan: In Progress Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-
[Kernel-packages] [Bug 1840710] Re: EULA never offered for Nvidia drivers install
** Tags added: id-5ccb523c44820c66015caeb2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1840710 Title: EULA never offered for Nvidia drivers install Status in linux-restricted-modules package in Ubuntu: New Bug description: Relevant system information here: https://pastebin.canonical.com/p/q6XqWt6THQ/ I was expecting that when I installed linux-modules-nvidia-generic-418 that I would get an option to accept or reject a EULA. However, on installation, no prompt is given to me, and after a reboot, I am able to see the driver with a `nvidia-smi` command. After doing some digging, installing this package writes out /etc/default/linux-modules-nvidia with latelink=true, and my debconf database also has a boolean for nvidia latelink set to true. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1840710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840686] Re: Xenial images won't reboot if disk size is > 2TB when using GPT
** Tags added: id-5d484a6466c79944a30e4644 -- 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/1840686 Title: Xenial images won't reboot if disk size is > 2TB when using GPT Status in cloud-init: New Status in linux-gcp package in Ubuntu: New Bug description: CPC team has recently converted Xenial images to use GPT instead of MBR. However, after booting an instance that has a disk size of 2049 GB or higher, we hang on the next subsequent boot (Logs indicate it hanging on "Booting Hard Disk 0". This works on Bionic, but what makes it strange is that they have the same kernel revision - 4.15.0-1-37. patrick_viafore@patviafore-test-3072-xenial:~$ lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 patrick_viafore@patviafore-test-3072-xenial:~$ sudo dpkg -l | grep linux-gcp ii linux-gcp4.15.0.1037.51 amd64Complete Google Cloud Platform (GCP) Linux kernel and headers ii linux-gcp-headers-4.15.0-10374.15.0-1037.39~16.04.1 amd64Header files related to Linux kernel version 4.15.0 To reproduce: 1) Create an image with a disk size of 3072 using a serial that has GPT gcloud compute instances create test-3072-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 3072 Reboot the instance 2) It will hang on reboot and you cannot connect 3) Please note that later serials have the GPT change reverted. You can replace xenial with bionic in the above commands to get a bionic instance instead. To test this out in a more slower fashion: 1) Create an image with a disk size of 2048 using a serial that has GPT gcloud compute instances create test-2048-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 2048 2) Resize the disk to 3072 3) Issue growpart /dev/sda 1 4) Issue resize2fs /dev/sda1 5) Issue rsize2fs /dev/sda1 instead On the second resize2fs, it tries to resize again, but on a working instance, it says there's nothing to resize. I've tried starting from a Xenial instance and doing a do-release-upgrade to get to bionic and then doing the growpart/resize2fs, but the issue still shows up. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1840686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840274] Re: bionic/linux-azure: 5.0.0-1016.17~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 derivatives: bug 1840273 (azure-kernel), bug 1840357 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840275 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Security - phase-changed: Monday, 19. August 2019 20:46 UTC + phase: Ready for Security + phase-changed: Tuesday, 20. August 2019 12:46 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: bionic/linux-azure-edge: bug 1840357 bionic/linux-azure/azure-kernel: bug 1840273 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840274 Title: bionic/linux-azure: 5.0.0-1016.17~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: Invalid 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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Fix Released 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 derivatives: bug 1840273 (azure-kernel), bug 1840357 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840275 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Security phase-changed: Tuesday, 20. August 2019 12:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy trackers: bionic/linux-azure-edge: bug 1840357 bionic/linux-azure/azure-kernel: bug 1840273 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840004] Re: xenial/linux-deeplens: 4.15.0-1006.6 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Tuesday, 20. August 2019 10:40 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840004 Title: xenial/linux-deeplens: 4.15.0-1006.6 -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: 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 Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Tuesday, 20. August 2019 10:40 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840326] Re: disco/linux-azure: 5.0.0-1017.18 -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 backports: bug 1840324 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839972 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 02:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - stakeholder-signoff: Ongoing -- waiting for signoff + stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840324 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840326 Title: disco/linux-azure: 5.0.0-1017.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840324 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839972 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 02:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840324 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840750] Re: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests
Running tests with the mainline builds the conclusion is that the bug was introduced with stable v5.0.20. From the thread on comment #4, we are missing the following fix: 7298e24f9042 x86/kprobes: Set instruction page as executable I'm building a test kernel to verify it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840750 Title: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument[PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer[PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe Tried with use "tail -f /var/log/syslog" and "dmesg -w" to see what happened, but it will just disconnected and reboot itself. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840275] Re: disco/linux-azure: 5.0.0-1016.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840275 Title: disco/linux-azure: 5.0.0-1016.17 -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: In Progress Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Disco: Fix Released 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 backports: bug 1840274 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Security phase-changed: Tuesday, 20. August 2019 08:25 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy trackers: bionic/linux-azure: bug 1840274 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840686] Re: Xenial images won't reboot if disk size is > 2TB when using GPT
** Description changed: CPC team has recently converted Xenial images to use GPT instead of MBR. However, after booting an instance that has a disk size of 2049 GB or higher, we hang on the next subsequent boot (Logs indicate it hanging on "Booting Hard Disk 0". This works on Bionic, but what makes it strange is that they have the same kernel revision - 4.15.0-1-37. patrick_viafore@patviafore-test-3072-xenial:~$ lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 patrick_viafore@patviafore-test-3072-xenial:~$ sudo dpkg -l | grep linux-gcp ii linux-gcp4.15.0.1037.51 amd64Complete Google Cloud Platform (GCP) Linux kernel and headers ii linux-gcp-headers-4.15.0-10374.15.0-1037.39~16.04.1 amd64Header files related to Linux kernel version 4.15.0 To reproduce: 1) Create an image with a disk size of 3072 using a serial that has GPT gcloud compute instances create test-3072-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 3072 Reboot the instance 2) It will hang on reboot and you cannot connect 3) Please note that later serials have the GPT change reverted. You can replace xenial with bionic in the above commands to get a bionic instance instead. - To test this out in a more slower fashion: - 1) Create an image with a disk size of 2048 using a serial that has GPT gcloud compute instances create test-2048-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 2048 2) Resize the disk to 3072 3) Issue growpart /dev/sda 1 4) Issue resize2fs /dev/sda1 - 5) Issue rsize2fs /dev/sda1 instead + 5) Issue rsize2fs /dev/sda1 again On the second resize2fs, it tries to resize again, but on a working instance, it says there's nothing to resize. - - I've tried starting from a Xenial instance and doing a do-release-upgrade to get to bionic and then doing the growpart/resize2fs, but the issue still shows up. + I've tried starting from a Xenial instance and doing a do-release- + upgrade to get to bionic and then doing the growpart/resize2fs, but the + issue still shows up. -- 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/1840686 Title: Xenial images won't reboot if disk size is > 2TB when using GPT Status in cloud-init: New Status in linux-gcp package in Ubuntu: New Bug description: CPC team has recently converted Xenial images to use GPT instead of MBR. However, after booting an instance that has a disk size of 2049 GB or higher, we hang on the next subsequent boot (Logs indicate it hanging on "Booting Hard Disk 0". This works on Bionic, but what makes it strange is that they have the same kernel revision - 4.15.0-1-37. patrick_viafore@patviafore-test-3072-xenial:~$ lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 patrick_viafore@patviafore-test-3072-xenial:~$ sudo dpkg -l | grep linux-gcp ii linux-gcp4.15.0.1037.51 amd64Complete Google Cloud Platform (GCP) Linux kernel and headers ii linux-gcp-headers-4.15.0-10374.15.0-1037.39~16.04.1 amd64Header files related to Linux kernel version 4.15.0 To reproduce: 1) Create an image with a disk size of 3072 using a serial that has GPT gcloud compute instances create test-3072-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 3072 Reboot the instance 2) It will hang on reboot and you cannot connect 3) Please note that later serials have the GPT change reverted. You can replace xenial with bionic in the above commands to get a bionic instance instead. To test this out in a more slower fashion: 1) Create an image with a disk size of 2048 using a serial that has GPT gcloud compute instances create test-2048-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 2048 2) Resize the disk to 3072 3) Issue growpart /dev/sda 1 4) Issue resize2fs /dev/sda1 5) Issue rsize2fs /dev/sda1 again On the second resize2fs, it tries to resize again, but on a working instance, it says there's nothing to resize. I've tried starting from a Xenial instance and doing a do-release- upgrade to get to bionic and then doing the growpart/resize2fs, but the issue still shows up. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1840686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1840274] Re: bionic/linux-azure: 5.0.0-1016.17~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840274 Title: bionic/linux-azure: 5.0.0-1016.17~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: Invalid 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: In Progress Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Fix Released 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 derivatives: bug 1840273 (azure-kernel), bug 1840357 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840275 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Security phase-changed: Tuesday, 20. August 2019 12:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy trackers: bionic/linux-azure-edge: bug 1840357 bionic/linux-azure/azure-kernel: bug 1840273 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840275] Re: disco/linux-azure: 5.0.0-1016.17 -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 backports: bug 1840274 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Security - phase-changed: Tuesday, 20. August 2019 08:25 UTC + phase: Security + phase-changed: Tuesday, 20. August 2019 13:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Pending -- ready to copy + promote-to-security: Ongoing -- packages not yet published trackers: bionic/linux-azure: bug 1840274 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840275 Title: disco/linux-azure: 5.0.0-1016.17 -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: In Progress Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Disco: Fix Released 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 backports: bug 1840274 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Security phase-changed: Tuesday, 20. August 2019 13:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Ongoing -- packages not yet published trackers: bionic/linux-azure: bug 1840274 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840686] Re: Xenial images won't reboot if disk size is > 2TB when using GPT
Based on IRC conversation, I don't believe this is a cloud-init bug. Please set the task back to New if I'm mistaken! ** Changed in: cloud-init Status: New => Won't Fix -- 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/1840686 Title: Xenial images won't reboot if disk size is > 2TB when using GPT Status in cloud-init: Won't Fix Status in linux-gcp package in Ubuntu: New Bug description: CPC team has recently converted Xenial images to use GPT instead of MBR. However, after booting an instance that has a disk size of 2049 GB or higher, we hang on the next subsequent boot (Logs indicate it hanging on "Booting Hard Disk 0". This works on Bionic, but what makes it strange is that they have the same kernel revision - 4.15.0-1-37. patrick_viafore@patviafore-test-3072-xenial:~$ lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 patrick_viafore@patviafore-test-3072-xenial:~$ sudo dpkg -l | grep linux-gcp ii linux-gcp4.15.0.1037.51 amd64Complete Google Cloud Platform (GCP) Linux kernel and headers ii linux-gcp-headers-4.15.0-10374.15.0-1037.39~16.04.1 amd64Header files related to Linux kernel version 4.15.0 To reproduce: 1) Create an image with a disk size of 3072 using a serial that has GPT gcloud compute instances create test-3072-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 3072 Reboot the instance 2) It will hang on reboot and you cannot connect 3) Please note that later serials have the GPT change reverted. You can replace xenial with bionic in the above commands to get a bionic instance instead. To test this out in a more slower fashion: 1) Create an image with a disk size of 2048 using a serial that has GPT gcloud compute instances create test-2048-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 2048 2) Resize the disk to 3072 3) Issue growpart /dev/sda 1 4) Issue resize2fs /dev/sda1 5) Issue rsize2fs /dev/sda1 again On the second resize2fs, it tries to resize again, but on a working instance, it says there's nothing to resize. I've tried starting from a Xenial instance and doing a do-release- upgrade to get to bionic and then doing the growpart/resize2fs, but the issue still shows up. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1840686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840274] Re: bionic/linux-azure: 5.0.0-1016.17~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 derivatives: bug 1840273 (azure-kernel), bug 1840357 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840275 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Security - phase-changed: Tuesday, 20. August 2019 12:46 UTC + phase: Security + phase-changed: Tuesday, 20. August 2019 13:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Pending -- ready to copy + promote-to-security: Ongoing -- packages not yet published trackers: bionic/linux-azure-edge: bug 1840357 bionic/linux-azure/azure-kernel: bug 1840273 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840274 Title: bionic/linux-azure: 5.0.0-1016.17~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: Invalid 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: In Progress Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Fix Released 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 derivatives: bug 1840273 (azure-kernel), bug 1840357 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840275 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Security phase-changed: Tuesday, 20. August 2019 13:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Ongoing -- packages not yet published trackers: bionic/linux-azure-edge: bug 1840357 bionic/linux-azure/azure-kernel: bug 1840273 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840004] Re: xenial/linux-deeplens: 4.15.0-1006.6 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Tuesday, 20. August 2019 10:40 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840004 Title: xenial/linux-deeplens: 4.15.0-1006.6 -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: 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 Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Tuesday, 20. August 2019 10:40 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840275] Re: disco/linux-azure: 5.0.0-1016.17 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840274 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Security - phase-changed: Tuesday, 20. August 2019 13:50 UTC + phase: Complete + phase-changed: Tuesday, 20. August 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-security: Ongoing -- packages not yet published trackers: bionic/linux-azure: bug 1840274 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840275 Title: disco/linux-azure: 5.0.0-1016.17 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Disco: Fix Released 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 backports: bug 1840274 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Complete phase-changed: Tuesday, 20. August 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-azure: bug 1840274 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840274] Re: bionic/linux-azure: 5.0.0-1016.17~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840273 (azure-kernel), bug 1840357 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840275 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Security - phase-changed: Tuesday, 20. August 2019 13:55 UTC + phase: Complete + phase-changed: Tuesday, 20. August 2019 14:06 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-security: Ongoing -- packages not yet published trackers: bionic/linux-azure-edge: bug 1840357 bionic/linux-azure/azure-kernel: bug 1840273 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840274 Title: bionic/linux-azure: 5.0.0-1016.17~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: Invalid 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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Fix Released 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 derivatives: bug 1840273 (azure-kernel), bug 1840357 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840275 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Complete phase-changed: Tuesday, 20. August 2019 14:06 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-azure-edge: bug 1840357 bionic/linux-azure/azure-kernel: bug 1840273 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
** Description changed: Last known good image: Eoan Ubuntu Desktop 20190715 Test Case: 1. Boot eoan desktop to a live session 2. Wait a couple of minutes until snapd settles 3. Reboot the system from the system menu or from the command line Expected result: The system reboots Actual result: The systems fails to reboot or shutdown and displays some errors about failing to unmount /cdrom and squashfs errors in a loop. Unmounting /cdrom... [FAILED] Failed unmounting /cdrom. [ OK ] Started Shuts down the "li…" preinstalled system cleanly. [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. [ 115.744188] print_req_error: I/O error, dev sr0, sector 1508872 flags 80700 [ 115.768139] print_req_error: I/O error, dev sr0, sector 1508872 flags 0 [ 115.771469] print_req_error: I/O error, dev loop0, sector 1501550 flags 0 [ 115.775824] SQUASHFS error: squashfs_read_data failed to read block 0x2dd2d998 - This also causes daily tests to fail. + This also causes daily tests to fail and is reproducible in a VM and + bare metal booted in legacy bios mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: casper 1.414 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 14 08:31:30 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190813) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Package: linux PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 1788 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 IwConfig: - lono wireless extensions. - - ens3 no wireless extensions. + lono wireless extensions. + + ens3 no wireless extensions. LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Lsusb: - Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 RelatedPackageVersions: - linux-restricted-modules-5.2.0-10-generic N/A - linux-backports-modules-5.2.0-10-generic N/A - linux-firmware1.181 + linux-restricted-modules-5.2.0-10-generic N/A + linux-backports-modules-5.2.0-10-generic N/A + linux-firmware1.181 RfKill: - + Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1
[Kernel-packages] [Bug 1840750] Re: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests
** Description changed: - This issue is 100% reproducible. It looks like this has something to do - with the Disco kernel in proposed (5.0.0-1014.14). + [Impact] + ftrace test in ubuntu_kernel_selftests causes a system crash + reboot when testing "Register/unregister many kprobe events". + + [Fix] + The issue has been discussed in the following LKML thread: + https://lkml.org/lkml/2019/6/5/274 + + and the following 3 upstream commits have been identified to resolve + this issue: + + d2a68c4effd8 x86/ftrace: Do not call function graph from dynamic trampolines + 3c0dab44e227 x86/ftrace: Set trampoline pages as executable + 7298e24f9042 x86/kprobes: Set instruction page as executable + + From these commits, the Disco kernel currently in -proposed + (5.0.0-26.27) is missing only the following commit, which has been + already committed as part of LP: #1839887 (Disco update: upstream stable + patchset 2019-08-12) but not yet released: + + 7298e24f9042 x86/kprobes: Set instruction page as executable + + [Regression potential] + The commit touches the x86/kprobes code so there's a chance of regression there which I would flag as medium. However, it has been applied upstream for v5.2-rc1 and there is no follow-up commits marked as fix for it. + + -- + This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument[PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer[PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe Tried with use "tail -f /var/log/syslog" and "dmesg -w" to see what happened, but it will just disconnected and reboot itself. - ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: linux (Ubuntu Disco) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840750 Title: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: In Progress Bug description: [Impact] ftrace test in ubuntu_kernel_selftests causes a system crash + reboot when testing "Register/unregister many kprobe events". [Fix] The issue has been discussed in the following LKML thread: https://lkml.org/lkml/2019/6/5/274 and the following 3 upstream commits have been identified to resolve this issue: d2a68c4effd8 x86/ftrace: Do not call function graph from dynamic trampolines 3c0dab44e227 x86/ftrace: Set trampoline pages as executable 7298e24f9042 x86/kprobes: Set instruction page as executable From these commits, the Disco kernel currently in -proposed (5.0.0-26.27) is missing only the following commit, which has been already committed as part of LP: #1839887 (Disco update: upstream stable patchset 2019-08-12) but not yet released: 7298e24f9042 x86/kprobes: Set instruction page as executable [Regression potential] The commit touches the x86/kprobes code so there's a chance of regression there which I would flag as medium. However, it has been applied upstream for v5.2-rc1 and there is no follow-up commits marked as fix for it. -- This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe eve
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
** Changed in: linux-aws (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Disco) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Disco) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws (Ubuntu Artful) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-aws (Ubuntu) Status: New => In Progress ** Changed in: linux-aws (Ubuntu) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux-aws source package in Artful: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux-aws source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-aws source package in Disco: In Progress Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840326] Re: disco/linux-azure: 5.0.0-1017.18 -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 backports: bug 1840324 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839972 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 02:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840324 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840326 Title: disco/linux-azure: 5.0.0-1017.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840324 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839972 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 02:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840324 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840324] Re: bionic/linux-azure: 5.0.0-1017.18~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 derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 10:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840324 Title: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed 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-azure package in Ubuntu: Invalid Status in linux-azure 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 derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 10:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
** Also affects: linux-aws-edge (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws-edge (Ubuntu Artful) Status: New => Invalid ** Changed in: linux-aws-edge (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-aws-edge (Ubuntu Disco) Status: New => Invalid ** Changed in: linux-aws-edge (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-aws-edge (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws-edge (Ubuntu) Status: New => In Progress ** Changed in: linux-aws-edge (Ubuntu) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: In Progress Status in linux-aws-edge package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux-aws source package in Artful: Invalid Status in linux-aws-edge source package in Artful: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: In Progress Status in linux-aws-edge source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux-aws source package in Cosmic: Invalid Status in linux-aws-edge source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-aws source package in Disco: In Progress Status in linux-aws-edge source package in Disco: Invalid Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840275] Re: disco/linux-azure: 5.0.0-1016.17 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1840275 Title: disco/linux-azure: 5.0.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Disco: Fix Released 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 backports: bug 1840274 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Complete phase-changed: Tuesday, 20. August 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-azure: bug 1840274 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840750] Re: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests
Eoan already has the fixing commit, so the development series shouldn't be affected. ** 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/1840750 Title: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: In Progress Bug description: [Impact] ftrace test in ubuntu_kernel_selftests causes a system crash + reboot when testing "Register/unregister many kprobe events". [Fix] The issue has been discussed in the following LKML thread: https://lkml.org/lkml/2019/6/5/274 and the following 3 upstream commits have been identified to resolve this issue: d2a68c4effd8 x86/ftrace: Do not call function graph from dynamic trampolines 3c0dab44e227 x86/ftrace: Set trampoline pages as executable 7298e24f9042 x86/kprobes: Set instruction page as executable From these commits, the Disco kernel currently in -proposed (5.0.0-26.27) is missing only the following commit, which has been already committed as part of LP: #1839887 (Disco update: upstream stable patchset 2019-08-12) but not yet released: 7298e24f9042 x86/kprobes: Set instruction page as executable [Regression potential] The commit touches the x86/kprobes code so there's a chance of regression there which I would flag as medium. However, it has been applied upstream for v5.2-rc1 and there is no follow-up commits marked as fix for it. -- This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument[PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer[PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe Tried with use "tail -f /var/log/syslog" and "dmesg -w" to see what happened, but it will just disconnected and reboot itself. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839945] Re: linux-kvm: -proposed tracker
** Tags removed: kernel-sru-cycle-2019.08.12-1 -- 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/1839945 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid 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: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: 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 -- variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840274] Re: bionic/linux-azure: 5.0.0-1016.17~18.04.1 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1840274 Title: bionic/linux-azure: 5.0.0-1016.17~18.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: Invalid 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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Fix Released 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 derivatives: bug 1840273 (azure-kernel), bug 1840357 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840275 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Complete phase-changed: Tuesday, 20. August 2019 14:06 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-azure-edge: bug 1840357 bionic/linux-azure/azure-kernel: bug 1840273 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840274/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839936] Re: linux-aws: -proposed tracker
** Tags removed: kernel-sru-cycle-2019.08.12-1 -- 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/1839936 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid 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: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: 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 -- variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840793] [NEW] linux-azure: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Disco) Importance: Medium Status: Confirmed ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.08.12-4 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: disco kernel-release-tracking-bug ** Also affects: linux-azure (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Disco) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
[Kernel-packages] [Bug 1840792] [NEW] linux-azure: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840365 (linux-azure-edge), bug 1840791 (azure-kernel) -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.08.12-4 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in:
[Kernel-packages] [Bug 1840789] [NEW] bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled
Public bug reported: Description/patches to be provided this week. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Mauricio Faria de Oliveira (mfo) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840789 Title: bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled Status in linux package in Ubuntu: In Progress Bug description: Description/patches to be provided this week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840790] [NEW] linux-aws: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839951 (bionic/linux-aws-edge) -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: Invalid ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Invalid ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Disco) Importance: Medium Status: Confirmed ** Tags: disco kernel-release-tracking-bug ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: disco kernel-release-tracking-bug ** Also affects: linux-aws (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Disco) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-updates Importance: Un
[Kernel-packages] [Bug 1839395] Re: Regressions in CMA allocation rework
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1839395 Title: Regressions in CMA allocation rework Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: Introduced by the fixes for bug 1823753. [Impact] Crashes (as observed on a nigrogen8m device), and a potential memory leak. [Test Case] Regression tested only. [Fix] f46cc0152501e dma-contiguous: page-align the size in dma_free_contiguous() c6622a425acd1 dma-contiguous: do not overwrite align in dma_alloc_contiguous() [Regression Risk] Bugs in CMA code could lead to device driver errors/crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839956] Re: bionic/linux-azure: -proposed tracker
*** This bug is a duplicate of bug 1840792 *** https://bugs.launchpad.net/bugs/1840792 ** This bug is no longer a duplicate of bug 1840324 bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker ** This bug has been marked a duplicate of bug 1840792 linux-azure: -proposed tracker -- 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/1839956 Title: bionic/linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 derivatives: bug 1839955 (linux-azure-edge) -- swm properties -- packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Thursday, 15. August 2019 11:01 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-azure-edge: bug 1839955 bionic/linux-azure/azure-kernel: bug 1839954 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839968] Re: disco/linux-snapdragon: 5.0.0-1019.20 -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: 1839972 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 15. August 2019 10:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1839968 Title: disco/linux-snapdragon: 5.0.0-1019.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839972 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 15. August 2019 10:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840324] Re: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker
*** This bug is a duplicate of bug 1840792 *** https://bugs.launchpad.net/bugs/1840792 ** 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 - derivatives: bug 1840323 (azure-kernel), bug 1840365 (linux-azure-edge) + derivatives: bug 1840365 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 10:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs ** Tags removed: kernel-sru-backport-of-1840326 ** 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 derivatives: bug 1840365 (linux-azure-edge) -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1840326 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 10:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs ** This bug has been marked a duplicate of bug 1840792 linux-azure: -proposed tracker -- 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/1840324 Title: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed 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-azure package in Ubuntu: Invalid Status in linux-azure 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 derivatives: bug 1840365 (linux-azure-edge) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 10:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1839673] Re: [linux-azure] Important InfiniBand patches for Ubuntu 18.04
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-bionic
--
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/1839673
Title:
[linux-azure] Important InfiniBand patches for Ubuntu 18.04
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Disco:
Fix Committed
Bug description:
The following two patches are critical for unblocking kernel sign-off
for the 5.0 kernel in Ubuntu 18.04:
("Don't wait in hvnd_query_gid after interface is already bound to ND")
("Expose extended attributes for user IB verbs QUERY_DEVICE, CREATE_CQ and
CREATE_QP")
The patches have not landed in linux-next yet, but are needed to
unblock 18.04 IB. The patches have been attached to this bug report.
Please consider including these patches as SAUCE until they land in
mainline.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1839673/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837788] Re: bcache kernel warning when attaching device
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1837788 Title: bcache kernel warning when attaching device Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Invalid Bug description: [Impact] * Users can get a Warning or even Oops the kernel if bcache/writeback_percent is set before attaching a caching device to the bcache device. * The fix is trivial, upstream, and consists of just checking whether the caching device is attached in order to set flags and schedule thread (which oops). [Test Case] * See attachment 'setup-bcache-wb_percent-before-attach.sh' used in comment #5 and #6 to reproduce the problem(s). * for 'Warning': # make-bcache -B # make-bcache -C # echo 11 > /sys/block//bcache/writeback_percent # sleep 1 # echo > /sys/block//bcache/attach * for 'Oops': (steps above, but don't run last command / 'attach'). [Regression Potential] * Low. The fix is trivial, contained, and exclusive to bcache sysfs handler. * The modified path has been exercised with synthetic testing (script). [Original Bug Description] See attached dmesg, each time this server is rebooted it emits a concerning bcache warning. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-54-generic. 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/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Wed Jul 24 12:28:06 2019 InstallationDate: Installed on 2013-10-04 (2119 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MachineType: Supermicro X9DAi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic root=UUID=8577302d-1f37-40a6-afcd-385beb26059f ro nomodeset elevator=deadline nvme_core.default_ps_max_latency_us=0 nopti noibrs noibpb RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-06-09 (409 days ago) dmi.bios.date: 05/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DAi dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd05/09/2015:svnSupermicro:pnX9DAi:pvr0123456789:rvnSupermicro:rnX9DAi:rvr0123456789:cvnSupermicro:ct3:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: X9DAi dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/183
[Kernel-packages] [Bug 1839953] Re: disco/linux-aws: 5.0.0-1013.15 -proposed tracker
** Tags removed: kernel-sru-derivative-of-1839972 ** 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 backports: bug 1839951 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1839972 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 19. August 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839951 variant: debs ** This bug has been marked a duplicate of bug 1840790 linux-aws: -proposed tracker -- 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/1839953 Title: disco/linux-aws: 5.0.0-1013.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 backports: bug 1839951 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 19. August 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839951 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836916] Re: alsa/hdmi: add icelake hdmi audio support for a Dell machine
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1836916 Title: alsa/hdmi: add icelake hdmi audio support for a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] On a Dell icelake platform, the hdmi audio doesn't work at all, when users plug hdmi cable, they can't find hdmi audio from gnome-sound-setting. [Fix] add icl hdmi audio id and related support patch to alsa driver. [Test Case] after applying the patchset, we plug hdmi cable and the hdmi audio shows up in the sound-setting and works well, after unplugging the cable, the hdmi audio disappears as expected. [Regression Risk] Low. this patchset is specific to a icl hdmi audio codec. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838677] Re: shiftfs: allow overlayfs
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1838677 Title: shiftfs: allow overlayfs Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: Currently it is not possible to use overlayfs on top of shiftfs. This means Docker inside of LXD cannot make user of the overlay2 graph driver which is blocking users such as Travis from making use of it efficiently. Regression Potential: Limited to shiftfs and overlayfs on top of shiftfs. Overlayfs does prevent "remote" filesystems such as ceph, nfs, etc. from being used as the underlay. With this patch shiftfs however can be used as an underlay and we special case it as a suitable filesystem to be used under overlayfs. I verified that the patch does not lead to regression on overlayfs workloads that do not make use of shiftfs as underlay. Additionally, I tested Docker with the overlay2 graphdriver on top of shiftfs. This also has not lead to any regressions. Test case: Building a kernel with the patch: sudo snap install lxd sudo lxd init sudo lxc launch images:ubuntu/bionic b1 sudo lxc config set b1 security.nesting true sudo lxc restart --force b1 sudo lxc shell b1 sudo apt-get install \ apt-transport-https \ ca-certificates \ curl \ gnupg-agent \ software-properties-common curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - curl -fsSL get.docker.com | CHANNEL=test sh sudo add-apt-repository \ "deb [arch=amd64] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) \ stable" sudo apt-get update sudo apt-get install docker-ce docker-ce-cli containerd.io sudo systemctl stop docker cat
[Kernel-packages] [Bug 1840326] Re: disco/linux-azure: 5.0.0-1017.18 -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 - - backports: bug 1840324 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839972 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 02:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840324 variant: debs ** Tags removed: kernel-sru-derivative-of-1839972 ** 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: 1839972 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 02:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840324 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840326 Title: disco/linux-azure: 5.0.0-1017.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 02:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840324 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840324] Re: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker
*** This bug is a duplicate of bug 1840792 *** https://bugs.launchpad.net/bugs/1840792 ** 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 derivatives: bug 1840365 (linux-azure-edge) -- swm properties -- boot-testing-requested: true + bugs-spammed: true packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 10:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840324 Title: bionic/linux-azure: 5.0.0-1017.18~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed 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-azure package in Ubuntu: Invalid Status in linux-azure 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 derivatives: bug 1840365 (linux-azure-edge) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 10:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1840365 bionic/linux-azure/azure-kernel: bug 1840323 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837117] Re: EeePC 1005px laptop backlight is off after system boot up
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1837117
Title:
EeePC 1005px laptop backlight is off after system boot up
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Released
Bug description:
== SRU Justification ==
Commit 78f3ac76d9e5 ("platform/x86: asus-wmi: Tell the EC the OS will
handle the display off hotkey") causes the backlight to be permanently off
on various EeePC laptop models using the eeepc-wmi driver (Asus EeePC
1015BX, Asus EeePC 1025C).
== Fix ==
* 1dd93f87 (platform/x86: asus-wmi: Only Tell EC the OS will handle
display hotkeys from asus_nb_wmi)
This patch addes a .wmi_backlight_set_devstate quirk for specific
models to make asus_wmi_set_devstate(ASUS_WMI_DEVID_BACKLIGHT, 2, NULL)
conditional.
Only X/D contain the commit that introduce this issue (78f3ac76), this
patch can be cherry-picked into D.
For X, it needs some content adjustment to add quirks only to those
models that exist in Xenial tree.
== Test ==
Test kernels could be found here:
https://people.canonical.com/~phlin/kernel/lp-1837117-eeepc/
Bug reporter has verified that this fix works as expected on X.
== Regression Potential ==
Low, quirks limited to specific ASUS laptops and by far there is no
further change to this in upstream kernel.
== Original Bug Report ==
After kernel update the backlight on my Asus eeepc 1005px becomes off during
boot up. I can see the login screen if I point light to the screen. The
backlight is not reacting on brightness adjustment keys. The backlight starts
working only if I close and open the laptop lid.
I have tried to:
* echo 10 > /sys/class/backlight/acpi_video0/brightness
* echo 125 > /sys/class/backlight/intel_backlight/brightness
* vbetool dpms on
* pass "acpi_backlight=vendor" kernel parameter
* install gdm instead of lightdm
* create /usr/share/X11/xorg.conf.d/80-backlight.conf with content
recommended in Kernel/Debugging/Backlight Wiki article
with no luck.
The backlight works fine if I pass "acpi_osi=" kernel parameter, the
brightness is adjusted by keys, but the applet does not react to
adjustments.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-145-generic 4.4.0-145.171
ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
Uname: Linux 4.4.0-145-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jul 18 22:30:44 2019
InstallationDate: Installed on 2019-02-17 (151 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837117/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839972] Re: disco/linux: 5.0.0-26.27 -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 backports: bug 1839969 (bionic/linux-hwe), bug 1839971 (bionic/linux-oem-osp1) - derivatives: bug 1839949 (linux-raspi2), bug 1839953 (linux-aws), bug 1839965 (linux-kvm), bug 1839967 (linux-oracle), bug 1839968 (linux-snapdragon), bug 1840326 (linux-azure), bug 1840665 (linux-gcp) + derivatives: bug 1839949 (linux-raspi2), bug 1839965 (linux-kvm), bug 1839967 (linux-oracle), bug 1839968 (linux-snapdragon), bug 1840326 (linux-azure), bug 1840665 (linux-gcp) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 15. August 2019 10:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1839969 bionic/linux-oem-osp1: bug 1839971 disco/linux-aws: bug 1839953 disco/linux-azure: bug 1840326 disco/linux-gcp: bug 1840665 disco/linux-kvm: bug 1839965 disco/linux-oracle: bug 1839967 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 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/1839972 Title: disco/linux: 5.0.0-26.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 backports: bug 1839969 (bionic/linux-hwe), bug 1839971 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839965 (linux-kvm), bug 1839967 (linux-oracle), bug 1839968 (linux-snapdragon), bug 1840326 (linux-azure), bug 1840665 (linux-gcp) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 15. August 2019 10:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1839969 bionic/linux-oem-osp1: bug 1839971 disco/linux-aws: bug 1839953 disco/linux-azure: bug 1840326 disco/linux-gcp: bug 1840665 disco/linux-kvm: bug 1839965 disco/linux-oracle: bug 1839967 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839972] Re: disco/linux: 5.0.0-26.27 -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 backports: bug 1839969 (bionic/linux-hwe), bug 1839971 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839965 (linux-kvm), bug 1839967 (linux-oracle), bug 1839968 (linux-snapdragon), bug 1840326 (linux-azure), bug 1840665 (linux-gcp) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 15. August 2019 10:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1839969 bionic/linux-oem-osp1: bug 1839971 disco/linux-aws: bug 1839953 disco/linux-azure: bug 1840326 disco/linux-gcp: bug 1840665 disco/linux-kvm: bug 1839965 disco/linux-oracle: bug 1839967 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 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/1839972 Title: disco/linux: 5.0.0-26.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 backports: bug 1839969 (bionic/linux-hwe), bug 1839971 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839965 (linux-kvm), bug 1839967 (linux-oracle), bug 1839968 (linux-snapdragon), bug 1840326 (linux-azure), bug 1840665 (linux-gcp) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 15. August 2019 10:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1839969 bionic/linux-oem-osp1: bug 1839971 disco/linux-aws: bug 1839953 disco/linux-azure: bug 1840326 disco/linux-gcp: bug 1840665 disco/linux-kvm: bug 1839965 disco/linux-oracle: bug 1839967 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837661] Re: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1837661 Title: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Invalid Status in linux-azure source package in Disco: Fix Committed Bug description: Can you please pick up the following 4 patches? They resolve this live migration that was reported by a mutual customer. PCI: hv: Add pci_destroy_slot() in pci_devices_present_work(), if necessary PCI: hv: Add hv_pci_remove_slots() when we unload the driver PCI: hv: Fix a memory leak in hv_eject_device_work() PCI: hv: Fix a use-after-free bug in hv_eject_device_work()pci/hv This is a known issue in linux pci-hyperv driver and is fixed by these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839949] Re: disco/linux-raspi2: 5.0.0-1015.15 -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: 1839972 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 15. August 2019 10:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1839949 Title: disco/linux-raspi2: 5.0.0-1015.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839972 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Thursday, 15. August 2019 10:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836910] Re: br_netfilter: namespace sysctl operations
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1836910 Title: br_netfilter: namespace sysctl operations Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: Currently, the /proc/sys/net/bridge folder is only created in the initial network namespace. This blocks use-cases where users would like to e.g. not do bridge filtering for bridges in a specific network namespace while doing so for bridges located in another network namespace. Fix: The patches linked below ensure that the /proc/sys/net/bridge folder is available in each network namespace if the module is loaded and disappears from all network namespaces when the module is unloaded. In doing so the patch makes the sysctls: bridge-nf-call-arptables bridge-nf-call-ip6tables bridge-nf-call-iptables bridge-nf-filter-pppoe-tagged bridge-nf-filter-vlan-tagged bridge-nf-pass-vlan-input-dev apply per network namespace. Regression Potential: Low since it is limited to the br_netfilter module. I tested the patchset extensively by compiling a kernel with the patches applied. I loaded and unloaded the module and verified that it works correctly for the container usecase and does not crash. The Google ChromeOS team has also backported this patchset to their kernel and has not seen any issues so far: https://bugs.chromium.org/p/chromium/issues/detail?id=878034 Security considerations around netfilter rules are also low. The netfilter rules are already per network namespace so it should be safe for users to specify whether bridge devices inside a network namespace are supposed to go through iptables et al. or not. Also, this can already be done per-bridge by setting an option for each individual bridge via Netlink. It should also be possible to do this for all bridges in a network namespace via sysctls. Test Case: Tested with LXD on a kernel with the patches applied and per-network namespace iptables. Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the patchset upstream. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff6d090d0db41425aef0cfe5dc58bb3cc12514a2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=22567590b2e634247931b3d2351384ba45720ebe https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7e6daf50e1f4ea0ecd56406beb64ffc66e1e94db To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839953] Re: disco/linux-aws: 5.0.0-1013.15 -proposed tracker
** This bug is no longer a duplicate of bug 1840790 linux-aws: -proposed tracker -- 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/1839953 Title: disco/linux-aws: 5.0.0-1013.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 backports: bug 1839951 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 19. August 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839951 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840790] Re: linux-aws: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live kernel-sru- cycle-2019.08.12-4 ** Changed in: kernel-sru-workflow Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-aws (Ubuntu Disco) Status: Confirmed => Invalid -- 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/1840790 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid 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: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: 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 backports: bug 1839951 (bionic/linux-aws-edge) -- swm properties -- variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837638] Re: Add the EFA driver into linux-aws
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- 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/1837638 Title: Add the EFA driver into linux-aws Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-aws source package in Xenial: Fix Committed Status in linux source package in Bionic: Invalid Status in linux-aws source package in Bionic: Fix Committed Status in linux source package in Disco: Invalid Status in linux-aws source package in Disco: Fix Committed Bug description: [Impact] * The open source EFA driver belongs in the AWS kernels (https://github.com/amzn/amzn-drivers/tree/master/kernel/linux/efa) [Test Case] * Boot tested into each kernel. Loaded and unloaded the module. [Regression Potential] This is a new feature constrained to a custom kernel. Most of the patches have been reviewed and applied to mainline. The compatibility fixup sauce patch is big, but is all preprocessor directives for conditional compilation and these have been maintained in the Github repo during the driver's development. Basically, the blast radius of this pull request should be confined only to this new module and should not impact any other area of the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840326] Re: disco/linux-azure: 5.0.0-1017.18 -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: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 02:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840324 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1840326 Title: disco/linux-azure: 5.0.0-1017.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 20. August 2019 02:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1840324 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839673] Re: [linux-azure] Important InfiniBand patches for Ubuntu 18.04
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag 'verification-needed-disco' to 'verification-failed-disco'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-disco
--
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/1839673
Title:
[linux-azure] Important InfiniBand patches for Ubuntu 18.04
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Disco:
Fix Committed
Bug description:
The following two patches are critical for unblocking kernel sign-off
for the 5.0 kernel in Ubuntu 18.04:
("Don't wait in hvnd_query_gid after interface is already bound to ND")
("Expose extended attributes for user IB verbs QUERY_DEVICE, CREATE_CQ and
CREATE_QP")
The patches have not landed in linux-next yet, but are needed to
unblock 18.04 IB. The patches have been attached to this bug report.
Please consider including these patches as SAUCE until they land in
mainline.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1839673/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837661] Re: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- 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/1837661 Title: [linux-azure] CRI-RDOS | Live migration only takes 10 seconds, but the VM was unavailable for 2 hours Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: Invalid Status in linux-azure source package in Disco: Fix Committed Bug description: Can you please pick up the following 4 patches? They resolve this live migration that was reported by a mutual customer. PCI: hv: Add pci_destroy_slot() in pci_devices_present_work(), if necessary PCI: hv: Add hv_pci_remove_slots() when we unload the driver PCI: hv: Fix a memory leak in hv_eject_device_work() PCI: hv: Fix a use-after-free bug in hv_eject_device_work()pci/hv This is a known issue in linux pci-hyperv driver and is fixed by these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839953] Re: disco/linux-aws: 5.0.0-1013.15 -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 backports: bug 1839951 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true + bugs-spammed: true packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 19. August 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839951 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/1839953 Title: disco/linux-aws: 5.0.0-1013.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 backports: bug 1839951 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 19. August 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839951 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839953] Re: disco/linux-aws: 5.0.0-1013.15 -proposed tracker
*** This bug is a duplicate of bug 1840790 *** https://bugs.launchpad.net/bugs/1840790 ** This bug has been marked a duplicate of bug 1840790 linux-aws: -proposed tracker -- 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/1839953 Title: disco/linux-aws: 5.0.0-1013.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 backports: bug 1839951 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 19. August 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-edge: bug 1839951 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
** Also affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xrdp-hwe-18.04 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: xorg-server (Ubuntu Bionic) Status: New => Invalid ** Changed in: xrdp-hwe-18.04 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xrdp-hwe-18.04 package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in xorg-server source package in Bionic: Invalid Status in xrdp-hwe-18.04 source package in Bionic: Fix Released Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
This bug was fixed in the package xrdp-hwe-18.04 - 0.9.5-2~18.04.1 --- xrdp-hwe-18.04 (0.9.5-2~18.04.1) bionic; urgency=medium * Rename for 18.04.3 HWE stack update. (LP: #1817225) - build only xorgxrdp-hwe-18.04 binary -- Timo Aaltonen Tue, 23 Jul 2019 23:52:02 +0300 ** Changed in: xrdp-hwe-18.04 (Ubuntu Bionic) Status: Fix Committed => 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/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xrdp-hwe-18.04 package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in xorg-server source package in Bionic: Invalid Status in xrdp-hwe-18.04 source package in Bionic: Fix Released Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Hey, adding that parameter to /etc/default/grub seemed to work! I have not had a single disconnection for more than three hours now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: Applying InputClass "li
[Kernel-packages] [Bug 1817225] Update Released
The verification of the Stable Release Update for xrdp-hwe-18.04 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xrdp-hwe-18.04 package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in xorg-server source package in Bionic: Invalid Status in xrdp-hwe-18.04 source package in Bionic: Fix Released Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840796] [NEW] sound not working in 4.15.0-58, but does in 4.15.0-55
Public bug reported: First excuse me, this is my very first bug report, if anything is missing, notify me on email. -- I find it rather hard to believe, but since I installed kernel: > 4.15.0-**58** several days ago, my sound on Linux Mint 19.2 Cinnamon stopped working, and no matter what I tried like: sudo apt reinstall alsa-base pulseaudio sudo alsa force-reload + reboot(-s) + alsamixer nothing brought me sound back, so I just installed an older kernel, namely the littlest bit older one: > 4.15.0-**55** now everything works like a charm. --- How can I debug this and figure out if the problem is a bug in the kernel itself or in some other audio-related package? I don't know what exact information you could require for this. --- I have just reproduced the problem by upgrading back to 4.15.0-**58** from 4.15.0-**55**. Sound not working again. Plus, by switching to an older kernel proves sound is functional. --- Hardware: laptop Dell HG6D142: [direct link to product page][1] -- $ lsb_release -rd Description:Linux Mint 19.2 Tina Release:19.2 --- expectation: sound working --- happened: sound does not work at all, neither with Intel GPU, nor Nvidia GPU online, tried all I could mentioned above I attach a simple diff between 55 and 58 loaded. --- Thank you! [1]: https://www.dell.com/support/home/us/en/04/product- support/servicetag/0-dVRqMHhSVXVMa3ZPOVFNUUEzSk1mQT090/overview ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug ** Attachment added: "lspci--diff--55vs58.log" https://bugs.launchpad.net/bugs/1840796/+attachment/5283492/+files/lspci--diff--55vs58.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840796 Title: sound not working in 4.15.0-58, but does in 4.15.0-55 Status in linux package in Ubuntu: New Bug description: First excuse me, this is my very first bug report, if anything is missing, notify me on email. -- I find it rather hard to believe, but since I installed kernel: > 4.15.0-**58** several days ago, my sound on Linux Mint 19.2 Cinnamon stopped working, and no matter what I tried like: sudo apt reinstall alsa-base pulseaudio sudo alsa force-reload + reboot(-s) + alsamixer nothing brought me sound back, so I just installed an older kernel, namely the littlest bit older one: > 4.15.0-**55** now everything works like a charm. --- How can I debug this and figure out if the problem is a bug in the kernel itself or in some other audio-related package? I don't know what exact information you could require for this. --- I have just reproduced the problem by upgrading back to 4.15.0-**58** from 4.15.0-**55**. Sound not working again. Plus, by switching to an older kernel proves sound is functional. --- Hardware: laptop Dell HG6D142: [direct link to product page][1] -- $ lsb_release -rd Description: Linux Mint 19.2 Tina Release: 19.2 --- expectation: sound working --- happened: sound does not work at all, neither with Intel GPU, nor Nvidia GPU online, tried all I could mentioned above I attach a simple diff between 55 and 58 loaded. --- Thank you! [1]: https://www.dell.com/support/home/us/en/04/product- support/servicetag/0-dVRqMHhSVXVMa3ZPOVFNUUEzSk1mQT090/overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1658219] Re: flock not mediated by 'k'
Hello.
I would like to note, that when Linux kernel has been updated to
4.4.0-160.188 version[1] (with, among others, patches for LP:#1658219
and LP:#1838090), I've had to update a few profiles (such as Audacious,
Parole, Xorg, Logrotate etc.), because of a lot of "DENIED" entries in
system log files. If it's about access controls (vide
'requested{denied}_mask'): most new rules required 'm' (memory map as
executable), but some of them needed 'k' (file locking) etc.)
However, it seems everything is okay now and I hope, that there will be
no such issues anymore. Anyway, Mr Tyler Hicks was right: "users with
custom policy have some reasonable expectation that upgrading to the new
Ubuntu release or kernel version will require them to update their
custom policy".
By the way; what is an impact of these changes? (I mean LP:#1658219 and
LP:#1838090). Does it means, that now, use of 'm' and 'k' access is
secured/restricted/checked correctly by AppArmor? And one more thing:
this problem is related to v4.4 kernel only, right?
Thanks, best regards.
__
[1] https://launchpad.net/ubuntu/+source/linux/4.4.0-160.188
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1658219
Title:
flock not mediated by 'k'
Status in AppArmor:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Won't Fix
Bug description:
$ cat ./apparmor.profile
#include
profile test {
#include
/bin/bash ixr,
/dev/pts/* rw,
/usr/bin/flock ixr,
# Not blocked:
# aa-exec -p test -- flock -w 1 /tmp/test.lock -c true
/tmp/test.lock rw,
}
$ sudo apparmor_parser -r ./apparmor.profile
$ aa-exec -p test -- flock -w 1 /tmp/test.lock -c true && echo yes
yes
$ ls -l /tmp/test.lock
-rw-rw-r-- 1 jamie jamie 0 Jan 20 15:57 /tmp/test.lock
The flock command uses flock(LOCK_EX) and I expected it to be blocked
due to the lack of 'k'.
apparmor userspace 2.10.95-0ubuntu2.5 (xenial) and 4.9.0-12.13-generic
kernel on amd64.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1658219/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838090] Re: Ubuntu 16.04: read access incorrectly implies 'm' rule
*** This bug is a duplicate of bug 1658219 ***
https://bugs.launchpad.net/bugs/1658219
Hello.
I would like to note, that when Linux kernel has been updated to
4.4.0-160.188 version[1] (with, among others, patches for LP:#1658219
and LP:#1838090), I've had to update a few profiles (such as Audacious,
Parole, Xorg, Logrotate etc.), because of a lot of "DENIED" entries in
system log files. If it's about access controls (vide
'requested{denied}_mask'): most new rules required 'm' (memory map as
executable), but some of them needed 'k' (file locking) etc.)
However, it seems everything is okay now and I hope, that there will be
no such issues anymore. Anyway, Mr Tyler Hicks was right: "users with
custom policy have some reasonable expectation that upgrading to the new
Ubuntu release or kernel version will require them to update their
custom policy".
By the way; what is an impact of these changes? (I mean LP:#1658219 and
LP:#1838090). Does it means, that now, use of 'm' and 'k' access is
secured/restricted/checked correctly by AppArmor? And one more thing:
this problem is related to v4.4 kernel only, right?
Thanks, best regards.
__
[1] https://launchpad.net/ubuntu/+source/linux/4.4.0-160.188
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838090
Title:
Ubuntu 16.04: read access incorrectly implies 'm' rule
Status in AppArmor:
Invalid
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
Confirmed
Bug description:
I've already been corresponding with jjohansen privately via email on
this, filing a bug here based on our conversation. To summarize the
email thread:
I was poking around some stuff today, and noticed that it seems like
the 'm' rule doesn't actually do anything. I've tested this on two
separate machines, both running Ubuntu 16.04:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.6 LTS
Release: 16.04
Codename: xenial
PoC:
$ sudo dmesg -c
$ cp /bin/ls /tmp
$ echo "/tmp/ls {
> /** r,
> }" > /tmp/tmp.ls
$ sudo apparmor_parser -C -r /tmp/tmp.ls
$ /tmp/ls
.
$ sudo dmesg
[1746349.392925] audit: type=1400 audit(1562018298.880:81): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/tmp/ls" pid=28205
comm="apparmor_parser"
There are no "ALLOWED" messages stating that we're missing the
necessary "mr," rule for mmap'ing shared objects such as libc.
As a follow-up, even with an empty profile running in complain mode, I
do not see any mention of needing the 'm' rule in the requested /
denied mask, it just asks for read access:
[1748198.369441] audit: type=1400 audit(1562020148.006:82): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/tmp/ls" pid=28677
comm="apparmor_parser"
[1748203.023838] audit: type=1400 audit(1562020152.662:83):
apparmor="ALLOWED" operation="open" profile="/tmp/ls" name="/etc/ld.so.cache"
pid=28678 comm="ls" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[1748203.023877] audit: type=1400 audit(1562020152.662:84):
apparmor="ALLOWED" operation="open" profile="/tmp/ls"
name="/lib/x86_64-linux-gnu/libselinux.so.1" pid=28678 comm="ls"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[1748203.023945] audit: type=1400 audit(1562020152.662:85):
apparmor="ALLOWED" operation="open" profile="/tmp/ls"
name="/lib/x86_64-linux-gnu/libc-2.23.so" pid=28678 comm="ls"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[1748203.023998] audit: type=1400 audit(1562020152.662:86):
apparmor="ALLOWED" operation="open" profile="/tmp/ls"
name="/lib/x86_64-linux-gnu/libpcre.so.3.13.2" pid=28678 comm="ls"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[1748203.024039] audit: type=1400 audit(1562020152.662:87):
apparmor="ALLOWED" operation="open" profile="/tmp/ls"
name="/lib/x86_64-linux-gnu/libdl-2.23.so" pid=28678 comm="ls"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[1748203.024076] audit: type=1400 audit(1562020152.662:88):
apparmor="ALLOWED" operation="open" profile="/tmp/ls"
name="/lib/x86_64-linux-gnu/libpthread-2.23.so" pid=28678 comm="ls"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
I tested this on Ubuntu 12.04, 18.04, and 19.04, and the expected
behavior is indeed there. Seems like a regression in specifically
16.04.
Response from jjohansen:
"This bug was fixed in Ubuntu in the Ubuntu zesty kernel (4.10) but
the fix was for a different issue and never cherry-picked back to
Xenial. We are going to need a bug report to get this fixed in the
Xenial kernel. So please do file a bug report. I can then attach the
patch and send it to the kt for inclusion in the next SRU."
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1838090/+subsc
[Kernel-packages] [Bug 1840796] Re: sound not working in 4.15.0-58, but does in 4.15.0-55
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1840796 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** 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/1840796 Title: sound not working in 4.15.0-58, but does in 4.15.0-55 Status in linux package in Ubuntu: Incomplete Bug description: First excuse me, this is my very first bug report, if anything is missing, notify me on email. -- I find it rather hard to believe, but since I installed kernel: > 4.15.0-**58** several days ago, my sound on Linux Mint 19.2 Cinnamon stopped working, and no matter what I tried like: sudo apt reinstall alsa-base pulseaudio sudo alsa force-reload + reboot(-s) + alsamixer nothing brought me sound back, so I just installed an older kernel, namely the littlest bit older one: > 4.15.0-**55** now everything works like a charm. --- How can I debug this and figure out if the problem is a bug in the kernel itself or in some other audio-related package? I don't know what exact information you could require for this. --- I have just reproduced the problem by upgrading back to 4.15.0-**58** from 4.15.0-**55**. Sound not working again. Plus, by switching to an older kernel proves sound is functional. --- Hardware: laptop Dell HG6D142: [direct link to product page][1] -- $ lsb_release -rd Description: Linux Mint 19.2 Tina Release: 19.2 --- expectation: sound working --- happened: sound does not work at all, neither with Intel GPU, nor Nvidia GPU online, tried all I could mentioned above I attach a simple diff between 55 and 58 loaded. --- Thank you! [1]: https://www.dell.com/support/home/us/en/04/product- support/servicetag/0-dVRqMHhSVXVMa3ZPOVFNUUEzSk1mQT090/overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840793] Re: linux-azure: -proposed tracker
** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-azure (Ubuntu Disco) Status: Confirmed => Invalid ** Tags removed: kernel-sru-cycle-2019.08.12-4 -- 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/1840793 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid 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: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: 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 -- variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840792] Re: linux-azure: -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 - derivatives: bug 1840365 (linux-azure-edge), bug 1840791 (azure-kernel) + derivatives: bug 1840365 (linux-azure-edge) -- swm properties -- variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: - https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - derivatives: bug 1840365 (linux-azure-edge) -- swm properties -- variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-azure (Ubuntu Bionic) Status: Confirmed => Invalid ** Tags removed: kernel-sru-cycle-2019.08.12-4 -- 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/1840792 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-lrm series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid 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: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 -- variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840790] Re: linux-aws: -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 + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - backports: bug 1839951 (bionic/linux-aws-edge) -- swm properties -- 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/1840790 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid 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: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: 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 -- variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840800] [NEW] linux-aws: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Disco) Importance: Medium Status: Confirmed ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.08.12-4 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: disco kernel-release-tracking-bug ** Also affects: linux-aws (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Disco) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-updates Importance: Undecided => Medium *
[Kernel-packages] [Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured
This bug was fixed in the package makedumpfile - 1:1.6.6-2ubuntu1 --- makedumpfile (1:1.6.6-2ubuntu1) eoan; urgency=medium [ Thadeu Lima de Souza Cascardo ] * Merge from Debian unstable. Remaining changes: - Bump amd64 crashkernel from 384M-:128M to 512M-:192M. * Add kdump retry/delay mechanism when dumping over network (LP: #1681909) * Allow proper reload of kdump after multiple hotplug events. (LP: #1828596) [ Connor Kuehl ] * Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860) makedumpfile (1:1.6.6-2) unstable; urgency=medium [ Guilherme G. Piccoli ] * Add kdump retry/delay mechanism when dumping over network [ Thadeu Lima de Souza Cascardo ] * Use a different service for vmcore dump. * Use maxcpus instead of nr_cpus on ppc64el. * Reload kdump when CPU is brought online. * Allow proper reload of kdump after multiple hotplug events. makedumpfile (1:1.6.6-1) unstable; urgency=medium * Update to new upstream version 1.6.6. -- Thadeu Lima de Souza Cascardo Tue, 06 Aug 2019 12:18:15 -0300 ** Changed in: makedumpfile (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1681909 Title: kdump is not captured in remote host when kdump over ssh is configured Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Cosmic: Won't Fix Status in makedumpfile source package in Disco: In Progress Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] * Kdump over network (like NFS mount or SSH dump) relies on network- online target from systemd. Even so, there are some NICs that report "Link Up" state but aren't ready to transmit packets. This is a generally bad behavior that is credited probably to NIC firmware delays, usually not fixable from drivers. Some adapters known to act like this are bnx2x, tg3 and ixgbe. * Kdump is a mechanism that may be a last resort to debug complex/hard to reproduce issues, so it's interesting to increase its reliability / resilience. We then propose here a solution/quirk to this issue on network dump by adding a retry/delay mechanism; if it's a network dump, kdump will retry some times and sleep between the attempts in order to exclude the case of NICs that aren't ready yet but will soon be able to transmit packets. * Although first reported by IBM in PowerPC arch, the scope for this issue is the NIC, and it was later reported in x86 arch too. [Test case] Usually it's difficult to naturally reproduce this issue in a deterministic way, but we have an artificial test case on comment #24 of this LP. Also, we have a report from this bug in which the user managed to reproduce the problem consistently - it's fixed after testing our solution. [Regression potential] There's not a clear regression potential here since it's just a retry/delay mechanism. Some potential problems may come from bad coding in the script. The delay between attempts is only 3 sec per iteration, so it shouldn't block the kdump progress for a high amount of time at once. [Other information] Salsa Debian commit: https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840796] Re: sound not working in 4.15.0-58, but does in 4.15.0-55
ok, apport-collect 1840796 as root or normal user? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840796 Title: sound not working in 4.15.0-58, but does in 4.15.0-55 Status in linux package in Ubuntu: Incomplete Bug description: First excuse me, this is my very first bug report, if anything is missing, notify me on email. -- I find it rather hard to believe, but since I installed kernel: > 4.15.0-**58** several days ago, my sound on Linux Mint 19.2 Cinnamon stopped working, and no matter what I tried like: sudo apt reinstall alsa-base pulseaudio sudo alsa force-reload + reboot(-s) + alsamixer nothing brought me sound back, so I just installed an older kernel, namely the littlest bit older one: > 4.15.0-**55** now everything works like a charm. --- How can I debug this and figure out if the problem is a bug in the kernel itself or in some other audio-related package? I don't know what exact information you could require for this. --- I have just reproduced the problem by upgrading back to 4.15.0-**58** from 4.15.0-**55**. Sound not working again. Plus, by switching to an older kernel proves sound is functional. --- Hardware: laptop Dell HG6D142: [direct link to product page][1] -- $ lsb_release -rd Description: Linux Mint 19.2 Tina Release: 19.2 --- expectation: sound working --- happened: sound does not work at all, neither with Intel GPU, nor Nvidia GPU online, tried all I could mentioned above I attach a simple diff between 55 and 58 loaded. --- Thank you! [1]: https://www.dell.com/support/home/us/en/04/product-support/servicetag/0-dVRqMHhSVXVMa3ZPOVFNUUEzSk1mQT090/overview --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vlastimil 2458 F pulseaudio /dev/snd/controlC1: vlastimil 2458 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2018-06-16 (430 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180531 MachineType: Dell Inc. Inspiron 7577 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=f1fc7345-be7a-4c6b-9559-fc6e2d445bfa ro ipv6.disable=1 quiet splash fsck.mode=force fsck.repair=yes vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 Tags: tina Uname: Linux 4.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0J8HMF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd04/19/2019:svnDellInc.:pnInspiron7577:pvr:rvnDellInc.:rn0J8HMF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7577 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741860] Re: Use the kernel default for crashkernel offset
This bug was fixed in the package makedumpfile - 1:1.6.6-2ubuntu1 --- makedumpfile (1:1.6.6-2ubuntu1) eoan; urgency=medium [ Thadeu Lima de Souza Cascardo ] * Merge from Debian unstable. Remaining changes: - Bump amd64 crashkernel from 384M-:128M to 512M-:192M. * Add kdump retry/delay mechanism when dumping over network (LP: #1681909) * Allow proper reload of kdump after multiple hotplug events. (LP: #1828596) [ Connor Kuehl ] * Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860) makedumpfile (1:1.6.6-2) unstable; urgency=medium [ Guilherme G. Piccoli ] * Add kdump retry/delay mechanism when dumping over network [ Thadeu Lima de Souza Cascardo ] * Use a different service for vmcore dump. * Use maxcpus instead of nr_cpus on ppc64el. * Reload kdump when CPU is brought online. * Allow proper reload of kdump after multiple hotplug events. makedumpfile (1:1.6.6-1) unstable; urgency=medium * Update to new upstream version 1.6.6. -- Thadeu Lima de Souza Cascardo Tue, 06 Aug 2019 12:18:15 -0300 ** Changed in: makedumpfile (Ubuntu Eoan) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1741860 Title: Use the kernel default for crashkernel offset Status in The Ubuntu-power-systems project: In Progress Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: In Progress Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Disco: In Progress Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] * The value chosen for ppc64el of 128MB aligns with that of the kernel default. That may change some day, so it would be best to let the kernel decide what value it should use. If the value does change and the kernel is not allowed to choose a value, this may stop the kernel from booting on a production system. [Test Case] Run `cat /etc/default/grub.d/kdump-tools.cfg` * Expected result: there is no offset specified at the end of the line (.e.g, @128M). * Actual result: For Xenial, Bionic, Disco, and Eoan there are offsets specified. [Regression Potential] * Right now, the offset described in the kdump-tools.cfg aligns with that of what the kernel would select, so since they are the same we would expect no change in operation. Original bug description follows: - == Comment: #0 - Hari Krishna Bathini - 2018-01-08 01:06:41 == ---Problem Description--- A default offset of 128MB is enforced for crashkernel by kdump-tools utility overriding the kernel default. While the kernel default offset for crashkernel is also 128MB, that may change and the right thing to do would be to let the kernel decide on the offset of crashkernel in the default scenario.. Get rid of "@128M" in kdump-tools.cfg file Contact Information = hbath...@in.ibm.com ---uname output--- na Machine Type = na ---Debugger--- A debugger is not configured ---Steps to Reproduce--- # cat /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M" --- The offset is specified via kdump-tools where as the kernel may be the right place to set an offset by default.. Userspace tool common name: kdump-tools The userspace tool has the following bit modes: 64-bit Userspace rpm: kdump-tools Userspace tool obtained from project website: na *Additional Instructions for hbath...@in.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #3 - MAMATHA INAMDAR - 2018-01-08 03:05:05 == This bug is opened to follow-up other bug based on the comment 19 https://bugzilla.linux.ibm.com/show_bug.cgi?id=152905#c19 (Canonical Launchpad1676884 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840810] [NEW] linux-kvm: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-kvm (Ubuntu Disco) Importance: Medium Status: Confirmed ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.08.12-4 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: disco kernel-release-tracking-bug ** Also affects: linux-kvm (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Disco) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-updates Importance: Undecided => Medium *
[Kernel-packages] [Bug 1840808] [NEW] linux-gcp: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839959 (bionic/linux-gke-5.0), bug 1840806 (bionic /linux-gcp) -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-gcp (Ubuntu Disco) Importance: Medium Status: Confirmed ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.08.12-4 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: disco kernel-release-tracking-bug ** Also affects: linux-gcp (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Disco) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Ker
