[Kernel-packages] [Bug 1852244] Re: disco/linux-gcp: 5.0.0-1026.27 -proposed tracker
** Summary changed: - disco/linux-gcp: -proposed tracker + disco/linux-gcp: 5.0.0-1026.27 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1852244 Title: disco/linux-gcp: 5.0.0-1026.27 -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 Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Thursday, 14. November 2019 07:44 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: bionic/linux-gcp: bug 1852241 bionic/linux-gke-5.0: bug 1852243 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852244] Re: disco/linux-gcp: 5.0.0-1026.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 -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Packaging - phase-changed: Tuesday, 12. November 2019 14:02 UTC + phase: Packaging + phase-changed: Thursday, 14. November 2019 07:44 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-gcp: bug 1852241 bionic/linux-gke-5.0: bug 1852243 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/1852244 Title: disco/linux-gcp: 5.0.0-1026.27 -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 Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Thursday, 14. November 2019 07:44 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: bionic/linux-gcp: bug 1852241 bionic/linux-gke-5.0: bug 1852243 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-disco ** 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Proposed - phase-changed: Thursday, 14. November 2019 06:48 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 14. November 2019 07:43 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building + promote-to-proposed: Pending -- ready for review trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1852251 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1852239 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 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/1852253 Title: disco/linux: 5.0.0-37.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Thursday, 14. November 2019 07:43 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1852251 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1852239 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 14. November 2019 06:48 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:queued + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1852251 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1852239 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 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/1852253 Title: disco/linux: 5.0.0-37.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in 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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 14. November 2019 06:48 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1852251 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1852239 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 14. November 2019 06:48 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:failed + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1852251 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1852239 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 14. November 2019 06:48 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building + promote-to-proposed: Pending -- builds not complete in ppa meta:queued trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1852251 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1852239 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 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/1852253 Title: disco/linux: 5.0.0-37.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in 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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 14. November 2019 06:48 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1852251 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1852239 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852386] Re: no HDMI video output since GDM greeter after linux-oem-osp1 version 5.0.0-1026
The second patch has been landed as upstream commit https://cgit.freedesktop.org/drm/drm- tip/commit/?id=50a5065f4474c2dbc1f7462b45a32d33d7b48d88 "drm/i915: Fix detection for a CMP-V PCH". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852386 Title: no HDMI video output since GDM greeter after linux-oem-osp1 version 5.0.0-1026 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: New Bug description: [SRU Justification: oem-osp1-bionic] [Impact] Bug 1849278 introduced a regression on some Comet Lake platforms that device may have no video output on HDMI port. [Fix] A currently in-review patch https://patchwork.freedesktop.org/patch/340416 should be applied to correct PCH's identity and restore HDMI output. [Test Case] 1. Apply the patches to oem-osp1 kernel >= 1026 or Eoan/Focal generic kernels. 2. Boot affected platforms with HDMI cable connected to an external monitor. 3. Check if the monitor lights up when GDM service is started. This was verified in to victim platforms. [Regression Risk] Low. This should affects only systems with matching PCH hw that is currently affected by the regression to be fixed. == [SRU Justification: E/F/U] [Impact] Some Comet Lake platforms got i915 call trace dump due to the lake of support to its PCH id: [2.999233] [ cut here ] [2.999238] eDP powered off while attempting aux channel communication. [2.999338] WARNING: CPU: 2 PID: 296 at drivers/gpu/drm/i915/display/intel_dp.c:1148 intel_dp_aux_xfer+0x767/0x900 [i915] [2.999341] Modules linked in: i915(+) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm r8169 ahci realtek libahci wmi video [2.999350] CPU: 2 PID: 296 Comm: systemd-udevd Not tainted 5.3.0-997-generic #201910072204 [2.999352] Hardware name: Dell Inc. OptiPlex 3280 AIO/, BIOS 99.00.08 10/01/2019 [2.999391] RIP: 0010:intel_dp_aux_xfer+0x767/0x900 [i915] [2.999394] Code: e8 ee b5 ff ff 84 c0 0f 85 ec f9 ff ff 48 8b 7d 80 e8 5d b6 ff ff 84 c0 0f 85 db f9 ff ff 48 c7 c7 50 22 5d c0 e8 84 ea b5 d1 <0f> 0b 48 8b 7d 80 48 8d 75 90 4c 8d ab a8 07 00 00 e8 63 b4 ff ff [2.999398] RSP: 0018:b740b5b8 EFLAGS: 00010286 [2.999400] RAX: RBX: 9bfa9dc2 RCX: 0396 [2.999402] RDX: 0001 RSI: 0082 RDI: 0246 [2.999404] RBP: b740b698 R08: 0396 R09: 0019 [2.999406] R10: 072e R11: b740b420 R12: 0004 [2.999408] R13: 9bfa9fbca120 R14: 9bfa9dc2 R15: 9bfa9dc207a8 [2.999410] FS: 7f0d8613a680() GS:9bfaaec8() knlGS: [2.999412] CS: 0010 DS: ES: CR0: 80050033 [2.999414] CR2: 7ffca955ae58 CR3: 00041e67e002 CR4: 003606e0 [2.999416] DR0: DR1: DR2: [2.999418] DR3: DR6: fffe0ff0 DR7: 0400 [2.999420] Call Trace: [2.999425] ? vprintk_default+0x29/0x50 [2.999464] intel_dp_aux_transfer+0x15e/0x220 [i915] [2.999472] drm_dp_dpcd_access+0x72/0x110 [drm_kms_helper] [2.999478] drm_dp_dpcd_read+0x33/0xc0 [drm_kms_helper] [2.999515] intel_dp_read_dpcd+0x41/0x130 [i915] [2.999551] intel_edp_init_connector+0x136/0x540 [i915] [2.999587] intel_dp_init_connector+0x47f/0x870 [i915] [2.999623] intel_ddi_init+0x425/0x590 [i915] [2.999660] intel_setup_outputs+0x8e4/0xc60 [i915] [Fix] Two patches to be backported to have correct support: * commit 37c92dc303dd "drm/i915: Add new CNL PCH ID seen on a CML platform" from drm-tip tree. * patch "https://patchwork.freedesktop.org/patch/340416; [Test Case] 1. Apply the patches to oem-osp1 kernel >= 1026 or Eoan/Focal generic kernels. 2. Boot affected platforms with HDMI cable connected to an external monitor. 3. Check if the monitor lights up when GDM service is started. This was verified in to victim platforms. [Regression Risk] Low. This should affects only systems with matching PCH hw that is currently affected by the regression to be fixed. ==
[Kernel-packages] [Bug 1842774] Re: Enhanced Hardware Support - Finalize Naming
This got surpassed by a security upload while waiting for SRU Team. I have uploaded rebased versions to -unapproved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842774 Title: Enhanced Hardware Support - Finalize Naming Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in qemu source package in Bionic: In Progress Status in linux source package in Disco: Fix Released Status in qemu source package in Disco: In Progress Bug description: @SRU Team: For SRU template of Qemu please scroll down ... SRU Justification Kernel: = [Impact] * Add / activate support for IBM z15 and LinuxONE III systems [Fix] * a0e2251132995b962281aa80ab54a9288f9e0b6b a0e2251 "s390: add support for IBM z15 machines" [Test Case] * check and verify cpuinfo - regression testing is possible by Canonical/me * functional testing is currently only doable by IBM [Regression Potential] * There is regression potential with having new code in and the flags added/active * but the code changes are pretty straight forward, just add config, cases and defs * and are not used on existing systems, just on the new generation that is not yet out in the field [Other Info] * SRU of LP 1842916 merged with (this) LP 1842774 --- SRU Template for qemu as the impact/scope is different == [Impact] * Update naming of the new HW Generation * Now that the systems are released people might look for types matching the name and no one really knows "IBM 8561 GA1". * Help users to identify the cpu type by backporting the fix that sets the defined name. [Fix] * https://git.qemu.org/?p=qemu.git;a=commit;h=7505deca [Test Case] * qemu-system-s390x -cpu ? | grep gen15 s390 gen15a-base IBM 8561 GA1(static, migration-safe) s390 gen15a IBM 8561 GA1(migration-safe) s390 gen15b-base IBM 8562 GA1(static, migration-safe) s390 gen15b IBM 8562 GA1(migration-safe) * With the fix gen15a should be called "IBM z15 GA1" [Regression Potential] * The only thing changing (for qemu) are some texts e.g. when showing CPU types. The cpu type itself that is used in e.g. scripts / commands will not change. Therefore the regression risk of the qemu change is next to none. The only I can think of is people grepping for the old ID in text output, but that seems theoretical and not important. [Other Info] * For an SRU perspective this is "nice to have" we will only do this "along" other higher impact SRUs. __ This feature request will provide the final naming of the next machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1842774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847948] Re: Improve NVMe guest performance on Bionic QEMU
This got surpassed by a security upload while waiting for SRU Team. I have uploaded rebased versions to -unapproved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847948 Title: Improve NVMe guest performance on Bionic QEMU Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in qemu source package in Bionic: Triaged Bug description: [Impact] * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO. But there can be platforms (like ppc64 spapr) that can and want to do exactly that. * Backport two patches from upstream (in since qemu 2.12 / Disco). * Due to that there is a tremendous speedup, especially useful with page size bigger than 4k. This avoids that being split into chunks and makes direct MMIO access possible for the guest. [Test Case] * On ppc64 pass through an NVME device to the guest and run I/O benchmarks, see below for Details how to set that up. Note: this needs the HWE kernel or another kernel fixup for [1]. Note: the test should also be done with the non-HWE kernel, the expectation there is that it would not show the perf benefits, but still work fine [Regression Potential] * Changes: a) if the host driver allows mapping of MSI-X data the entire BAR is mapped. This is only done if the kernel reports that capability [1]. This ensures that only on kernels able to do so qemu does expose the new behavior (safe against regression in that regard) b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local to just this HW and will not affect other HW. Generally the regressions that come to mind are slight changes in behavior (real HW vs the former emulation) that on some weird/old guests could cause trouble. But then it is limited to only PPC where only a small set of certified HW is really allowed. The mapping that might be added even on other platforms should not consume too much extra memory as long as it isn't used. Further since it depends on the kernel capability it isn't randomly issues on kernels where we expect it to fail. So while it is quite a change, it seems safe to me. [Other Info] * I know, one could as well call that a "feature", but it really is a performance bug fix more than anything else. Also the SRU policy allows exploitation/toleration of new HW especially for LTS releases. Therefore I think this is fine as SRU. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a32295c612c57990d17fb0f41e7134394b2f35f6 == Comment: #0 - Murilo Opsfelder Araujo - 2019-10-11 14:16:14 == ---Problem Description--- Back-port the following patches to Bionic QEMU to improve NVMe guest performance by more than 200%: ?vfio-pci: Allow mmap of MSIX BAR? https://git.qemu.org/?p=qemu.git;a=commit;h=ae0215b2bb56a9d5321a185dde133bfdd306a4c0 ?ppc/spapr, vfio: Turn off MSIX emulation for VFIO devices? https://git.qemu.org/?p=qemu.git;a=commit;h=fcad0d2121976df4b422b4007a5eb7fcaac01134 ---uname output--- na ---Additional Hardware Info--- 0030:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 172Xa/172Xb (rev 01) Machine Type = AC922 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install or setup a guest image and boot it. Once guest is running, passthrough the NVMe disk to the guest using the XML: host$ cat nvme-disk.xml host$ virsh attach-device nvme-disk.xml --live On the guest, run fio benchmarks: guest$ fio --direct=1 --rw=randrw --refill_buffers --norandommap --randrepeat=0 --ioengine=libaio --bs=4k --rwmixread=100 --iodepth=16 --runtime=60 --name=job1 --filename=/dev/nvme0n1 --numjobs=4 Results are similar with numjobs=4 and numjobs=64, respectively: READ: bw=385MiB/s (404MB/s), 78.0MiB/s-115MiB/s (81.8MB/s-120MB/s), io=11.3GiB (12.1GB), run=30001-30001msec READ: bw=382MiB/s (400MB/s), 2684KiB/s-12.6MiB/s (2749kB/s-13.2MB/s), io=11.2GiB (12.0GB), run=30001-30009msec With the two patches applied, performance improved significantly for numjobs=4 and numjobs=64 cases, respectively: READ: bw=1191MiB/s (1249MB/s), 285MiB/s-309MiB/s (299MB/s-324MB/s), io=34.9GiB (37.5GB), run=30001-30001msec READ: bw=4273MiB/s (4481MB/s), 49.7MiB/s-113MiB/s (52.1MB/s-119MB/s), io=125GiB (134GB), run=30001-30005msec Userspace tool common name: qemu Userspace rpm: qemu The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications
[Kernel-packages] [Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 22:26 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:building,meta:failed,signed:depwait
+ promote-to-proposed: Pending -- builds not complete in ppa
main:building,meta:failed,signed:depwait
trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
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/1852232
Title:
eoan/linux: 5.3.0-24.26 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Eoan:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 22:26 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Pending -- builds not complete in ppa
main:building,meta:failed,signed:depwait
trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker
** 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 --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Packaging
- phase-changed: Wednesday, 13. November 2019 19:36 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Thursday, 14. November 2019 06:48 UTC
reason:
- prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:building,meta:failed,signed:building
+ promote-to-proposed: Pending -- builds not complete in ppa meta:failed
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
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/1852253
Title:
disco/linux: 5.0.0-37.40 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in 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 --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Holding before Promote to Proposed
phase-changed: Thursday, 14. November 2019 06:48 UTC
reason:
promote-to-proposed: Pending -- builds not complete in ppa meta:failed
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -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 --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:21 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:depwait,signed:building
+ promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:depwait
trackers:
trusty/linux-aws: bug 1852304
trusty/linux-lts-xenial: bug 1852305
xenial/linux-aws: bug 1852296
xenial/linux-cascade: bug 1852297
xenial/linux-fips: bug 1852303
xenial/linux-kvm: bug 1852298
xenial/linux-raspi2: bug 1852300
xenial/linux-snapdragon: bug 1852302
xenial/linux/caracalla-kernel: bug 1852291
xenial/linux/pc-kernel: bug 1852292
xenial/linux/stlouis-kernel: bug 1852293
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/1852306
Title:
xenial/linux: 4.4.0-170.199 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:21 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:depwait
trackers:
trusty/linux-aws: bug 1852304
trusty/linux-lts-xenial: bug 1852305
xenial/linux-aws: bug 1852296
xenial/linux-cascade: bug 1852297
xenial/linux-fips: bug 1852303
xenial/linux-kvm: bug 1852298
xenial/linux-raspi2: bug 1852300
xenial/linux-snapdragon: bug 1852302
xenial/linux/caracalla-kernel: bug 1852291
xenial/linux/pc-kernel: bug 1852292
xenial/linux/stlouis-kernel: bug 1852293
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -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 --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:21 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
main:building,meta:depwait,signed:queued
+ promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:depwait,signed:building
trackers:
trusty/linux-aws: bug 1852304
trusty/linux-lts-xenial: bug 1852305
xenial/linux-aws: bug 1852296
xenial/linux-cascade: bug 1852297
xenial/linux-fips: bug 1852303
xenial/linux-kvm: bug 1852298
xenial/linux-raspi2: bug 1852300
xenial/linux-snapdragon: bug 1852302
xenial/linux/caracalla-kernel: bug 1852291
xenial/linux/pc-kernel: bug 1852292
xenial/linux/stlouis-kernel: bug 1852293
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/1852306
Title:
xenial/linux: 4.4.0-170.199 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:21 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:depwait,signed:building
trackers:
trusty/linux-aws: bug 1852304
trusty/linux-lts-xenial: bug 1852305
xenial/linux-aws: bug 1852296
xenial/linux-cascade: bug 1852297
xenial/linux-fips: bug 1852303
xenial/linux-kvm: bug 1852298
xenial/linux-raspi2: bug 1852300
xenial/linux-snapdragon: bug 1852302
xenial/linux/caracalla-kernel: bug 1852291
xenial/linux/pc-kernel: bug 1852292
xenial/linux/stlouis-kernel: bug 1852293
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838601] Re: kernel update 5.0.0-23 breaks scroll mouse in xorg
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838601 Title: kernel update 5.0.0-23 breaks scroll mouse in xorg Status in linux package in Ubuntu: Fix Released Bug description: Just updated 18.04 to kernel 5.0.0-23 and scrolling with mouse wheel does not work or works very slowly. Mouse is Microsoft Wireless Optical Mouse 3000 connected via USB to wireless receiver. Rebooting system into kernel 4.18.0-25 and everything works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Wed Jul 31 22:53:44 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-24-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2019-04-05 (118 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 2347GBU ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=c840a596-f648-4a82-98f4-70137859c633 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GBU dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2347GBU:pvrThinkPadT430:rvnLENOVO:rn2347GBU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GBU dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 22:26 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
lrm:queued,main:building,meta:failed,signed:depwait
+ promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:building,meta:failed,signed:depwait
trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
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/1852232
Title:
eoan/linux: 5.3.0-24.26 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Eoan:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 22:26 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:building,meta:failed,signed:depwait
trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -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 --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:36 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
lrm:queued,main:queued,meta:failed,signed:queued
+ promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:building,meta:failed,signed:building
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
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/1852253
Title:
disco/linux: 5.0.0-37.40 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in 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 --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:36 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:building,meta:failed,signed:building
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -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 --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:21 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:depwait,signed:building
+ promote-to-proposed: Pending -- builds not complete in ppa
main:building,meta:depwait,signed:queued
trackers:
trusty/linux-aws: bug 1852304
trusty/linux-lts-xenial: bug 1852305
xenial/linux-aws: bug 1852296
xenial/linux-cascade: bug 1852297
xenial/linux-fips: bug 1852303
xenial/linux-kvm: bug 1852298
xenial/linux-raspi2: bug 1852300
xenial/linux-snapdragon: bug 1852302
xenial/linux/caracalla-kernel: bug 1852291
xenial/linux/pc-kernel: bug 1852292
xenial/linux/stlouis-kernel: bug 1852293
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/1852306
Title:
xenial/linux: 4.4.0-170.199 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:21 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:depwait,signed:building
trackers:
trusty/linux-aws: bug 1852304
trusty/linux-lts-xenial: bug 1852305
xenial/linux-aws: bug 1852296
xenial/linux-cascade: bug 1852297
xenial/linux-fips: bug 1852303
xenial/linux-kvm: bug 1852298
xenial/linux-raspi2: bug 1852300
xenial/linux-snapdragon: bug 1852302
xenial/linux/caracalla-kernel: bug 1852291
xenial/linux/pc-kernel: bug 1852292
xenial/linux/stlouis-kernel: bug 1852293
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 22:26 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
lrm:depwait,main:building,meta:failed,signed:depwait
+ promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:building,meta:failed,signed:depwait
trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
variant: debs
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 22:26 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:building,meta:failed,signed:depwait
+ promote-to-proposed: Pending -- builds not complete in ppa
lrm:queued,main:building,meta:failed,signed:depwait
trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
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/1852232
Title:
eoan/linux: 5.3.0-24.26 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Eoan:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 22:26 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:building,meta:failed,signed:depwait
trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838601] Re: kernel update 5.0.0-23 breaks scroll mouse in xorg
This is no longer occurring in 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838601 Title: kernel update 5.0.0-23 breaks scroll mouse in xorg Status in linux package in Ubuntu: Confirmed Bug description: Just updated 18.04 to kernel 5.0.0-23 and scrolling with mouse wheel does not work or works very slowly. Mouse is Microsoft Wireless Optical Mouse 3000 connected via USB to wireless receiver. Rebooting system into kernel 4.18.0-25 and everything works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Wed Jul 31 22:53:44 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-24-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2019-04-05 (118 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 2347GBU ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=c840a596-f648-4a82-98f4-70137859c633 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GBU dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2347GBU:pvrThinkPadT430:rvnLENOVO:rn2347GBU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GBU dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -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 --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:36 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
lrm:depwait,main:queued,meta:failed,signed:depwait
+ promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:queued,meta:failed,signed:building
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
variant: debs
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:36 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:queued,meta:failed,signed:building
+ promote-to-proposed: Pending -- builds not complete in ppa
lrm:queued,main:queued,meta:failed,signed:queued
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
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/1852253
Title:
disco/linux: 5.0.0-37.40 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in 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 --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:36 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:building,meta:failed,signed:building
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852289] Re: bionic/linux: 4.15.0-71.80 -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 --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Thursday, 14. November 2019 00:16 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Ongoing -- builds not complete in ppa
lrm:depwait,main:building,meta:depwait,signed:depwait
+ promote-to-proposed: Pending -- builds not complete in ppa
lrm:depwait,main:building,meta:failed,signed:depwait
trackers:
bionic/linux-aws: bug 1852270
bionic/linux-fips: bug 1852278
bionic/linux-gke-4.15: bug 1852272
bionic/linux-ibm-gt: bug 1852274
bionic/linux-kvm: bug 1852273
bionic/linux-oem: bug 1852266
bionic/linux-oracle: bug 1852277
bionic/linux-raspi2: bug 1852262
bionic/linux-snapdragon: bug 1852264
bionic/linux/pc-kernel: bug 1852259
bionic/linux/pc-lowlatency-kernel: bug 1852260
xenial/linux-azure: bug 1852282
xenial/linux-gcp: bug 1852285
xenial/linux-hwe: bug 1852288
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/1852289
Title:
bionic/linux: 4.15.0-71.80 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Thursday, 14. November 2019 00:16 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Pending -- builds not complete in ppa
lrm:depwait,main:building,meta:failed,signed:depwait
trackers:
bionic/linux-aws: bug 1852270
bionic/linux-fips: bug 1852278
bionic/linux-gke-4.15: bug 1852272
bionic/linux-ibm-gt: bug 1852274
bionic/linux-kvm: bug 1852273
bionic/linux-oem: bug 1852266
bionic/linux-oracle: bug 1852277
bionic/linux-raspi2: bug 1852262
bionic/linux-snapdragon: bug 1852264
bionic/linux/pc-kernel: bug 1852259
bionic/linux/pc-lowlatency-kernel: bug 1852260
xenial/linux-azure: bug 1852282
xenial/linux-gcp: bug 1852285
xenial/linux-hwe: bug 1852288
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852289/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -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 --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:36 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
lrm:depwait,main:building,meta:failed,signed:depwait
+ promote-to-proposed: Pending -- builds not complete in ppa
lrm:depwait,main:queued,meta:failed,signed:depwait
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
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/1852253
Title:
disco/linux: 5.0.0-37.40 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in 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 --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:36 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Pending -- builds not complete in ppa
lrm:building,main:queued,meta:failed,signed:building
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -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 --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:21 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:depwait,signed:depwait
+ promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:depwait,signed:building
trackers:
trusty/linux-aws: bug 1852304
trusty/linux-lts-xenial: bug 1852305
xenial/linux-aws: bug 1852296
xenial/linux-cascade: bug 1852297
xenial/linux-fips: bug 1852303
xenial/linux-kvm: bug 1852298
xenial/linux-raspi2: bug 1852300
xenial/linux-snapdragon: bug 1852302
xenial/linux/caracalla-kernel: bug 1852291
xenial/linux/pc-kernel: bug 1852292
xenial/linux/stlouis-kernel: bug 1852293
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/1852306
Title:
xenial/linux: 4.4.0-170.199 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:21 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:depwait,signed:building
trackers:
trusty/linux-aws: bug 1852304
trusty/linux-lts-xenial: bug 1852305
xenial/linux-aws: bug 1852296
xenial/linux-cascade: bug 1852297
xenial/linux-fips: bug 1852303
xenial/linux-kvm: bug 1852298
xenial/linux-raspi2: bug 1852300
xenial/linux-snapdragon: bug 1852302
xenial/linux/caracalla-kernel: bug 1852291
xenial/linux/pc-kernel: bug 1852292
xenial/linux/stlouis-kernel: bug 1852293
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Subscribed Adrian Hunter to this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838601] Re: kernel update 5.0.0-23 breaks scroll mouse in xorg
Does this issue still happen under an up-to-date kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838601 Title: kernel update 5.0.0-23 breaks scroll mouse in xorg Status in linux package in Ubuntu: Confirmed Bug description: Just updated 18.04 to kernel 5.0.0-23 and scrolling with mouse wheel does not work or works very slowly. Mouse is Microsoft Wireless Optical Mouse 3000 connected via USB to wireless receiver. Rebooting system into kernel 4.18.0-25 and everything works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Wed Jul 31 22:53:44 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-24-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2019-04-05 (118 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 2347GBU ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=c840a596-f648-4a82-98f4-70137859c633 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GBU dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2347GBU:pvrThinkPadT430:rvnLENOVO:rn2347GBU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GBU dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840936] Re: Cannot log back in after locking screen: Xubuntu 18.04 on Lenovo IdeaPad
Sorry for the belated response. I meant the default GNOME desktop. I was trying to figure out it's a bug in userspace or kernel space. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840936 Title: Cannot log back in after locking screen: Xubuntu 18.04 on Lenovo IdeaPad Status in linux package in Ubuntu: Confirmed Bug description: Xubuntu 18.04 installed on a new Lenovo IdeaPad 330S; system is up to date (I run Software Updater pretty much daily). lsb_release -rd tells me: Description: Ubuntu 18.04.3 LTS Release: 18.04 When the screen gets locked (either when I lock it or when the system locks it after a period of inactivity), there is no way for me to log back in. No matter what I do, no "enter password" box pops up. The screen just stays black and the only thing I can do is to shut the computer down by holding down the power button. This happens regardless of whether an external monitor is connected. My apologies if I didn't report this correctly or left out anything important; I am just an end user and not an expert. Please let me know if I need to provide any further information. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: s 1354 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-07-03 (48 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 81F4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=a0988d83-0fbb-4905-9f48-3753f6ed52d1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/26/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7SCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr7SCN26WW:bd10/26/2018:svnLENOVO:pn81F4:pvrLenovoideapad330S-14IKB:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad330S-14IKB: dmi.product.family: ideapad 330S-14IKB dmi.product.name: 81F4 dmi.product.sku: LENOVO_MT_81F4_BU_idea_FM_ideapad 330S-14IKB dmi.product.version: Lenovo ideapad 330S-14IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824648] Re: black screen after upgrade to kernel 4.15.0-47
Does this issue still happen on an up-to-date kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824648 Title: black screen after upgrade to kernel 4.15.0-47 Status in linux package in Ubuntu: Confirmed Bug description: I install Xubuntu 18.04.2 in kvm(debian 9.8 host), and upgrade to latest 4.15.0-47 kernel recently. I get a black screen after grub boot menu. I had tried to downgrade to 4.15.0-46 kernel, and it's also black screen, but it's ok after downgrade to 4.15.0-45 kernel. Finally, I find I only get black screen after start with 4.15.0-47 kernel(or 4.15.0-46 kernel) if I set my VM display to spice/qxl. My Xubuntu VM can boot normally if I set display to spice/vmvga or any other options. Any help would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 1096 F pulseaudio CurrentDesktop: XFCE Date: Sun Apr 14 03:05:38 2019 InstallationDate: Installed on 2018-12-24 (110 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: ens3 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 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) ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5b6b407c-d00b-4e08-9921-ce2e5612555c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.8 dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.8:cvnQEMU:ct1:cvrpc-i440fx-2.8: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.8 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824648/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841556] Re: cpu frequency stuck below min frequency with power_save governor
Does this issue happen under v5.3? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841556 Title: cpu frequency stuck below min frequency with power_save governor Status in linux package in Ubuntu: Confirmed Bug description: Sometimes my laptop will be very sluggish after rebooting from prime- select = nvidia back into intel and it's because the cpu frequency is stuck in the range approx 450-750 MHz instead of its normal range of 800 MHz to 3.8 GHz. Switching to use the performance governor restores performance, but if I switch back to powersave, the frequency gets stuck again below the minimum. I've attached dumps of /sys/cpuinfo and /sys/devices/system/cpu/cpu0/cpufreq/* to show the current frequency is below 750 MHz even though the minimum frequency is 800 MHz. Usually this resolves after a second reboot but this time it has persisted over several reboots (and it doesn't matter whether I boot into linux 5.2 or 5.3-rc6). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-10-generic 5.2.0-10.11 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1400 F pulseaudio rocko 1829 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Aug 27 16:46:08 2019 InstallationDate: Installed on 2019-07-01 (56 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) MachineType: Dell Inc. XPS 15 9560 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-10-generic root=UUID=f5a24957-19c2-4a22-acc0-3776c6300bf5 ro rootflags=subvol=@ quiet splash scsi_mod.use_blk_mq=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1001) is not owned by us (uid 0), but by uid 1001! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.2.0-10-generic N/A linux-backports-modules-5.2.0-10-generic N/A linux-firmware1.181 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd05/23/2019:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840643] Re: System freezes: BUG: unable to handle kernel paging request at ffff9d26523dfaf8
Does this issue still happen on an up-to-date kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840643 Title: System freezes: BUG: unable to handle kernel paging request at 9d26523dfaf8 Status in linux package in Ubuntu: Confirmed Bug description: The system suddenly freezes. "journalctl" reports: Aug 19 12:43:57 $HOSTNAME kernel: BUG: unable to handle kernel paging request at 9d26523dfaf8 Aug 19 12:43:57 $HOSTNAME kernel: #PF error: [normal kernel read fault] Last program that was executed was Firefox (stock version from Xubuntu 19.04 without any additional add-ons), surfing with 9 tabs opened. "ubuntu-bug linux" has been executed. Ubuntu 5.0.0-25.26-generic 5.0.18 Description: Ubuntu 19.04 Release: 19.04 firefox: Installiert: 68.0.2+build1-0ubuntu0.19.04.1 Installationskandidat: 68.0.2+build1-0ubuntu0.19.04.1 Versionstabelle: *** 68.0.2+build1-0ubuntu0.19.04.1 500 500 http://de.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 100 /var/lib/dpkg/status 66.0.3+build1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu disco/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1641 F pulseaudio CurrentDesktop: XFCE Date: Mon Aug 19 12:55:41 2019 InstallationDate: Installed on 2019-08-19 (0 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq 8100 Elite CMT PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-25-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786H1 v01.05 dmi.board.asset.tag: CZC1248ZDK dmi.board.name: 304Bh dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC1248ZDK dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786H1v01.05:bd06/09/2010:svnHewlett-Packard:pnHPCompaq8100EliteCMTPC:pvr:rvnHewlett-Packard:rn304Bh:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 8100 Elite CMT PC dmi.product.sku: AY031AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819486] Re: Crash from :i915 module with 4.15.0-46-generic using multi-display
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** 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/1819486 Title: Crash from :i915 module with 4.15.0-46-generic using multi-display Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: === SRU Justification === [Impact] 4.15.0-46 breaks once working external display over docking. [Fix] Revert the commit that causes regression. [Test] User confirms reverting the commit solves the regression. [Regression Potential] Low. Docking can works without this commit on Bionic kernel. While previously working using 4.15.0-45-generic, booting my thinkpad T480 on a dock with additional screen connected and "kernel 4.15.0-46-generic" lead to a crash of the system. === Original Bug Report === Laptop is running Ubuntu 18.04.2 LTS. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: user 3449 F...m pulseaudio /dev/snd/controlC1: user 3449 F pulseaudio /dev/snd/pcmC0D0p: user 3449 F...m pulseaudio /dev/snd/controlC0: user 3449 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=c94c8e19-c9cc-49db-b6e7-4e1542a5efa7 InstallationDate: Installed on 2018-06-28 (256 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20L5000AFR Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin netdev plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5000AFR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L5000AFR:pvrThinkPadT480:rvnLENOVO:rn20L5000AFR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5000AFR dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819921] Re: [SRU] [B/OEM] Fix ACPI bug that causes boot failure
Patch available in Focal, mark this as fix-released. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1819921 Title: [SRU] [B/OEM] Fix ACPI bug that causes boot failure Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: V2: Fix non-x86 building error. [Impact] Some lenovo laptops failed to boot at a very early stage, only blackscreen shown. [Fix] Some system BIOS set definition in if statement, it would be deferred to be loaded. Some devices would not work properly and cause a system lockup. add a quirk for these laptops to execute all acpi tables and make system work properly. [Test] Tested on several laptops, the laptop that failed to boot boots well. Other laptops still works fine. [Regression Potential] SAUCE patch.Low, specific changes depends on hardware. Upstream fix: commit 5a8361f7ecceaed64b4064000d16cb703462be49 Author: Schmauss, Erik Date: Thu Feb 15 13:09:30 2018 -0800 ACPICA: Integrate package handling with module-level code Due to the lots of changes in this commit and other regressions concern So made a sauce patch in Bionic kernel with the specific BIOS series. Verified on several laptops. Fix boot failure and no regression found. The upstream fix is in 4.17-rc1, so only Bionic/OEM 4.15 kernels need it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1819921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829378] Re: Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1829378
Title:
Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Released
Bug description:
=== SRU Justification ===
[Impact]
NULL pointer dereference in acpi_quirk_matches_bios_ids() renders kernel
unbootable.
[Fix]
It's a regression caused by commit abd273f52766 ("UBUNTU: SAUCE: ACPI /
bus: Add some Lenovo laptops in list of acpi table term list").
When both bios_vendor and bios_ver are NULL then a NULL string is passed
to strncmp() and the issue occurs.
VMs may not provides string bios_vendor or bios_ver, so bail out early
when either bios_vendor or bios_ver is NULL.
[Test]
User reported the test kernel with proposed fix solves the issue.
[Regression Potenial]
Low. It's quite trivial so I don't think it'll regress anything.
=== Original Bug Report ===
After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel
crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works).
Kernel 4.15.0-48 and prior did boot without any problems as PVH.
We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50.
Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH-
DomU.
See also https://lists.xenproject.org/archives/html/xen-
users/2019-05/msg00010.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829378/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823429] Re: linux v4.15 ftbfs on a newer host kernel (e.g. hwe)
Patch available in Focal, mark this as Fix released. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1823429 Title: linux v4.15 ftbfs on a newer host kernel (e.g. hwe) Status in linux package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oracle source package in Bionic: Fix Released Bug description: [Impact] * linux v4.15.x fails to build on newer host machine kernels (i.e. hwe / v4.18+ ) [Fix] * Instead of relying on a potentially incompatible host system/kernel definitions of PF_MAX, use the one from the source tree. * Upstream commit in v5.1-rc1-2-gdfbd199a7cfe: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=master=dfbd199a7cfe3e3cd8531e1353cdbd7175bfbc5e which was cherrypicked to stable as: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y=145f6a70bb9b422a6df5fb8b9408046151f3e4f9 Submitted to the kernel team mailing list (whilst spamming too many people in CC) at https://lists.ubuntu.com/archives/kernel-team/2019-June/101190.html [Test Case] * Install linux-hwe kernel, reboot, try to rebuild linux GA kernel. [Regression Potential] * This is a FTBFS fix only, to use matching definitions from the target kernel at build time. [Other Info] * Original bug report, autopkgtest regression rebuild test case of the bionic's linux-oracle kernel on newer host kernels: https://launchpadlibrarian.net/417924791/buildlog_ubuntu-disco-amd64 .linux-oracle_4.15.0-1010.12_BUILDING.txt.gz HOSTLD scripts/mod/modpost HOSTCC scripts/selinux/genheaders/genheaders In file included from /<>/scripts/selinux/genheaders/genheaders.c:19: /<>/security/selinux/include/classmap.h:247:2: error: #error New address family defined, please update secclass_map. #error New address family defined, please update secclass_map. ^ make[6]: *** [scripts/Makefile.host:90: scripts/selinux/genheaders/genheaders] Error 1 make[5]: *** [/<>/scripts/Makefile.build:606: scripts/selinux/genheaders] Error 2 make[4]: *** [/<>/scripts/Makefile.build:606: scripts/selinux] Error 2 make[3]: *** [/<>/Makefile:589: scripts] Error 2 make[2]: *** [/<>/Makefile:278: __build_one_by_one] Error 2 make[2]: Leaving directory '/<>/debian/build/build-oracle' make[1]: *** [Makefile:146: sub-make] Error 2 make[1]: Leaving directory '/<>' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818149] Re: backport relevant patches for support of the base_frequency attribute of intel_pstate
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818149 Title: backport relevant patches for support of the base_frequency attribute of intel_pstate Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Bug description: Need to back port the following HWE commits from 4.20/5.0 kernel to 4.18, then 4.15 kernels for Cosmic and Bionic HWE 29523f095397637edca60c627bc3e5c25a02c40f 86d333a8cc7f66c2314ab1e147834a1cd95ec2de To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggressive memory leak
Upstream commit available in Focal, marking this bug as fix released for
linux.
Please open a new bug if you're still experiencing this issue on newer
releases (Cosmic EOL)
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1831751
Title:
rtlwifi: aggressive memory leak
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* Upstream commit 0a9f8f0a1ba9 "rtlwifi: fix btmpinfo timeout while
processing C2H_BT_INFO" fixed a timeout message by adding a fast path
which allowed commands to skip the queue to be processed immediately.
However, the fast path doesn't free the sk_buff when it completes;
this results in a memory leak when commands are fast-tracked.
[Test Case]
* This was tested in the bug report on a RTL8723BE card. As the
system is running, a memory leak is observed until it gets to the
point where a reboot is necessary.
* The following patch was applied and the ever-increasing memory
consumption no longer experienced.
[Regression Potential]
* This was fixed in Linux 4.20 and participants in both the LP bug
and the Github issue reports [1] have reported positive test results
with just this patch applied.
[1] https://github.com/lwfinger/rtlwifi_new/issues/401
Original bug description follows:
---
Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI)
the memory usage grows slowly to take all the available RAM when i let the
computer running over the night (with just top and irssi), and i have to reboot
to get things back to normal. I didn't have this problem on Ubuntu 17.10 but i
was still flooded with message about pci aer taking lots of disk space in the
logs, but pci=noaer fixed this problem and i had no memory leak.
The computer is a common laptop: HP Pavilion.
---
Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly
disabled to capture the AERs.
Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
overnight booted just to console (systemd.unit=multi-user.target).
The memory leak doesn't affect Windows but owner is going to check
Windows Event Log for signs of AERs being logged.
---
Original suspect of AER is not guilty.
This turns out to be a bug in the rtlwifi driver where in some rare
circumstances it fails to free an sk_buf.
Reporter has been testing a DKMS build of rtlwfi with the fix applied
and confirms it solves the issue.
Upstream has the commit. Can we get this cherry-picked into all
releases?
commit 8cfa272b0d321160ebb5b45073e39ef0a6ad73f2
Author: Larry Finger
Date: Sat Nov 17 20:55:03 2018 -0600
rtlwifi: Fix leak of skb when processing C2H_BT_INFO
With commit 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO"), calling rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
the routine returns without freeing that skb, thereby leaking it.
This issue has been discussed at
https://github.com/lwfinger/rtlwifi_new/issues/401
and the fix tested there.
Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO")
Reported-and-tested-by: Francisco Machado Magalhães Neto
Cc: Francisco Machado Magalhães Neto
Cc: Ping-Ke Shih
Cc: Stable # 4.18+
Signed-off-by: Larry Finger
Signed-off-by: Kalle Valo
diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c
b/drivers/net/wireless/realtek/rtlwifi/base.c
index f4122c8fdd97..ef9b502ce576 100644
--- a/drivers/net/wireless/realtek/rtlwifi/base.c
+++ b/drivers/net/wireless/realtek/rtlwifi/base.c
@@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct
sk_buff *skb)
if (rtl_c2h_fast_cmd(hw, skb)) {
rtl_c2h_content_parsing(hw, skb);
+ kfree_skb(skb);
return;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1831751/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819485] Re: x86: add support for AMD Rome
Patchset available in Focal, closing this. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819485 Title: x86: add support for AMD Rome Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] * Some upstream patches are missing to properly support the AMD Rome architecture, without them the affected systems cannot work correctly. [Test Case] * No test case provided (tests have been made by the bug reporter using the affected platform) [Fix] * The following commits are required to properly support this architecture: 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode 210ba1201ff9 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef2 x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baff x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc28 x86/MCE/AMD: Fix the thresholding machinery initialization order [Regression Potential] * All the patches have been applied upstream and they have been tested on the newly supported platform with positive feedback. [Original bug report] The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 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 RfKill: 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/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string dmi.product.name: DAYTONA_X dmi.product.sku: Default string dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AMD Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830433] Re: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all
Patch available in Focal, mark this as fix-released.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1830433
Title:
32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
[Impact]
Commit d653420532d580156c8486686899ea6a9eeb7bf0 in bionic enabled
kernel page table isolation for x86_32, but also introduced a kernel
bug (the BUG_ON() condition in vmalloc_sync_one()) that seems to
happen when vmalloc_sync_all() is called multiple times (e.g., in a
busy loop).
The real problem seems to be a race condition with page-table entries'
initialization that can be fixed applying the upstream commit
9bc4f28af75a91aea0ae383f50b0a430c4509303 ("x86/mm: Use WRITE_ONCE()
when setting PTEs").
[Test Case]
The bug can be easily triggered by rebooting the system a couple of
times and loading this module:
https://launchpadlibrarian.net/428142172/vmalloc-stress-test.c
[Fix]
The following upstream fix seems to resolve the problem:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9bc4f28af75a91aea0ae383f50b0a430c4509303
In addition to that the following other upstream fixes are required
(all clean cherry picks) to do a cleaner backport of
9bc4f28af75a91aea0ae383f50b0a430c4509303:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=86fa949b050184ffc53688516a6a83ae5f98d08a
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=792adb90fa724ce07c0171cbc96b9215af4b1045
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5e0fb5df2ee871b841f96f9cb6a7f2784e96aa4e
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=785a19f9d1dd8a4ab2d0633be4656653bd3de1fc
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f967db0b9ed44ec3057a28f3b28efc51df51b835
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ba6f508d0ec4adb09f0a939af6d5e19cdfa8667d
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f77084d96355f5fba8e2c1fb3a51a393b1570de7
[Regression Potential]
All upstream fixes, tested on the affected platform, backport changes
are minimal.
[Original bug report]
Hi,
I'm reproducing a kernel bug in vmalloc_sync_all() with a 32-bit x86
kernel.
The problem appears in
Linux ubuntu 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:45:45 UTC
2019 i686 i686 i686 GNU/Linux
Kernels 4.15.0-49 and prior work fine.
The kernel 4.18.0-20-generic works fine.
This problem has not been experienced with upstream Linux kernels.
It appears that invoking vmalloc_sync_all() a few times end up
triggering this issue. This can be triggered by restarting the lttng-
sessiond service with lttng-modules-dkms installed (sometimes a few
restarts are needed to trigger the bug). This ends up unloading and
reloading those modules, which issues a few vmalloc_sync_all() as
side-effect.
I'm not reporting this issue with the "ubuntu-bug linux" command
because it crashes the system on that kernel (system hangs, no console
output).
My test system runs within a kvm virtual machine on a 64-bit host.
lsb release:
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Information about my kernel:
linux-image-4.15.0-50-generic:
Installed: 4.15.0-50.54
Candidate: 4.15.0-50.54
Version table:
*** 4.15.0-50.54 500
500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main i386
Packages
100 /var/lib/dpkg/status
Information about lttng-modules-dkms:
lttng-modules-dkms:
Installed: 2.10.5-1ubuntu1.2
Candidate: 2.10.5-1ubuntu1.2
Version table:
*** 2.10.5-1ubuntu1.2 500
500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/universe i386
Packages
100 /var/lib/dpkg/status
2.10.5-1ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830813] Re: TCP : race condition on socket ownership in tcp_close()
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830813 Title: TCP : race condition on socket ownership in tcp_close() Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Bug description: SRU Justification Impact: WARN_ON messages casued by race condition between the close of a TCP socket and another process inspecting the same socket. The code of interest is the following; in tcp_close function : ... release_sock(sk); ... WARN_ON(sock_owned_by_user(sk)); ... While in release_sock(sk), sock_release_owner function is called which sets the sk->sk_lock.owned=0. When WARN_ON(sock_owned_by_user(sk)) is called it expects to find that the socket is not owned by anyone. According to upstream commit 8873c064d1de579ea2341, while a socket is being closed is possible that other threads find it in rtnetlink dump. tcp_get_info() function acquires the socket lock ( and sets sk_lock.owned=1 ) for a short amount of time, however long enough to trigger this warning. Fix: Fixed by upstream commit in v4.20: Commit: 8873c064d1de579ea23412a6d3eee972593f142b "tcp: do not release socket ownership in tcp_close()" Commit 8873c064d1de579ea23412a6d3eee972 fixes this bug by delegating the release of ownership (calling release_sock(sk)) to later; just before exiting tcp_close function. Testcase: Reporter has tested and verified test 4.15 test kernel for Bionic. This bug is difficult to be reproduced locally because the race condition cannot be triggered in a deterministic way. To hit this bug we need the following : a) a process closing a socket and while the execution is between release_sock(s) and WARN_ON(sock_owned_by_user(sk)) b) another process inspecting the same socket to get into tcp_get_info(), acquire ownership of the socket and not release it until the first process reaches the WARN_ON(sock_owned_by_user(sk)). This scenario is difficult to be achieved in a testing environment. Regression Potential: As far as Bionic (4.15 kernel) is concerned the reporter of the bug has tested and verified a test kernel with the fix. Concerning Cosmic (4.18 kernel) the fix has not been tested. However, given that a) this fix essentially removes the WARN_ON(sock_owned_by_user(sk)) and delegates the release of the ownership to later in the tcp_close function, and b) the relevant code paths in 4.15 and 4.18 are largely the same the regression potential should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801052] Re: arm64 kvm-unit-tests timer test failing on 18.04
Hi Andre, Thanks for reporting this. This patch has been applied to Bionic [1]. And our regression-testing shows positive test results. Please feel free to re-open this if you think the status is incorrect. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835972 ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801052 Title: arm64 kvm-unit-tests timer test failing on 18.04 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: kvm-unit-tests performs 12 timer tests in the latest version, one of them failing with the latest Ubuntu LTS kernel. This issue has been fixed in mainline commits 7afc4ddbf299a13aaf28406783d141a34c6b4f5a and 245715cbe83ca934af5d20e078fd85175c62995e (part of 4.19.0 release), which are tagged with "Cc: Stable # 4.15+" and "Fixes: ...". Could you please backport them to your tree? "patch" applies them with some fuzz only (no additional fixing needed). Here is what I did: - Boot 4.15.0-38-generic on an ARM Juno r1 board (but every arm64 h/w would do). - Run kvm-unit-tests: $ git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git $ cd kvm-unit-tests $ ./configure && make $ ./run_tests.sh This will mark the timer test as failed: FAIL timer (12 tests, 1 unexpected failures) A more detailed log can be get by: $ arm/run arm/timer.flat I then fetched the official Ubuntu kernel (apt-get source), applied the two patches mentioned above and rebuilt the kernel (with the .config from /boot). This will report the timer as pass: PASS timer (12 tests) So could you please backport those two patches to make kvm-unit-tests (and its users) happy? Btw: I was wondering whether you have some process to find those stable fixes, even with the 4.15 base kernel being EOL for quite a while now. Please bear with me if you do and I was just too impatient ;-) Thanks! Andre --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 28 2018 seq crw-rw 1 root audio 116, 33 Jan 28 2018 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-38-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyAMA0,115200n8 root=/dev/sda3 rw rootwait earlycon=pl011,0x7ff8 debug ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-38-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 374105] Re: linux-image-$ver packages leave cruft behind
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: virtualbox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/374105 Title: linux-image-$ver packages leave cruft behind Status in linux package in Ubuntu: Confirmed Status in tp-smapi package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: $ ll /lib/modules/ total 6,0K drwxr-xr-x 8 root root 1,0K 2009-03-10 02:41 2.6.24-23-386 drwxr-xr-x 2 root root 1,0K 2009-03-23 05:13 2.6.28-10-generic drwxr-xr-x 5 root root 1,0K 2009-04-20 08:55 2.6.28-11-generic drwxr-xr-x 2 root root 1,0K 2009-03-17 05:54 2.6.28-4-386 drwxr-xr-x 3 root root 1,0K 2009-03-15 04:12 2.6.28-8-generic drwxr-xr-x 3 root root 1,0K 2009-03-12 02:18 2.6.28-9-generic $ dpkg -l linux-image*|grep ii ii linux-image2.6.28.11.15 Generic Linux kernel image. ii linux-image-2.6.24-23-386 2.6.24-23.48 Linux kernel image for version 2.6.24 on i38 ii linux-image-2.6.28-11-generic 2.6.28-11.42 Linux kernel image for version 2.6.28 on x86 ii linux-image-generic2.6.28.11.15 Generic Linux kernel image $ dpkg -S /lib/modules/*/modules.seriomap linux-image-2.6.24-23-386: /lib/modules/2.6.24-23-386/modules.seriomap dpkg: /lib/modules/2.6.28-10-generic/modules.seriomap not found. dpkg: /lib/modules/2.6.28-11-generic/modules.seriomap not found. 2.6.28-10-generic looks like a superseded package that did not properly clean up after itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/374105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 996505] Re: Removing old kernels doesn't clean up
*** This bug is a duplicate of bug 374105 ***
https://bugs.launchpad.net/bugs/374105
** This bug has been marked a duplicate of bug 374105
linux-image-$ver packages leave cruft behind
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/996505
Title:
Removing old kernels doesn't clean up
Status in linux package in Ubuntu:
Triaged
Bug description:
I noticed that the removal of old kernels does not uninstall the
kernel headers for that kernel, nor does it delete the folder in
/lib/modules
Linux-headers are at about 130Mb i memory serves, this could cause a
lot of bloat if a lot of kernels have been installed (through regular
updates). Even if the kernel is removed to save space, the headers
still remain. Is this intentional?
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-generic-pae 3.2.0.24.26
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andy 2313 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 45'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801d6,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 14
Simple ctrls : 7
Date: Tue May 8 13:12:32 2012
HibernationDevice: RESUME=UUID=95e17f36-156e-42a0-a81a-3f1d883e4b62
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120203)
MachineType: Dell Inc. Latitude D420
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic-pae
root=UUID=3cd487d1-a1c9-48fd-9c86-b388897bc6ef ro quiet splash ipv6.disable=1
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-24-generic-pae N/A
linux-backports-modules-3.2.0-24-generic-pae N/A
linux-firmware1.79
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0YJ387
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA06:bd02/02/2008:svnDellInc.:pnLatitudeD420:pvr:rvnDellInc.:rn0YJ387:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D420
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/996505/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -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 --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:36 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Ongoing -- builds not complete in ppa
lrm:depwait,main:building,meta:depwait,signed:depwait
+ promote-to-proposed: Pending -- builds not complete in ppa
lrm:depwait,main:building,meta:failed,signed:depwait
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
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/1852253
Title:
disco/linux: 5.0.0-37.40 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in 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 --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:36 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Pending -- builds not complete in ppa
lrm:depwait,main:building,meta:failed,signed:depwait
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 22:26 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Ongoing -- builds not complete in ppa
lrm:depwait,main:building,meta:depwait,signed:depwait
+ promote-to-proposed: Pending -- builds not complete in ppa
lrm:depwait,main:building,meta:failed,signed:depwait
trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
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/1852232
Title:
eoan/linux: 5.3.0-24.26 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Eoan:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 22:26 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Pending -- builds not complete in ppa
lrm:depwait,main:building,meta:failed,signed:depwait
trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1780590] Re: Add support for Realtek 8723DE wireless adapter
** Tags added: verification-done-bionic verification-done-disco verification-done-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1780590 Title: Add support for Realtek 8723DE wireless adapter Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-firmware source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Confirmed Status in linux-firmware source package in Focal: New Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: === SRU Justification === [Impact] There's no in-kernel support for Realtek 8723DE, so users need to use out-of-tree DKMS which is not from Ubuntu archive. This has security implication and should be avoided. Also this provides pretty bad user experience. [Fix] Add support to Realtek 8723DE. All commits are cherry-picked from Realtek maintained repo: https://github.com/rtlwifi-linux/rtw88_8723de [Test] With the patch series applied, 8723DE can scan and connect to APs succesfully. Also did some S3 smoke test, it continues to work. [Regression Potential] Low. The device in question was never supported, and if there's any regression, we can count on Realtek Wireless team, thy are now pretty responsive on upstream mailing list. === Original Bug Report === recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. Everything in the installation was fine until the moment to start session. The problem is that the wireless network card does not detect me and when entering the configuration I simply get an error message saying that no wireless adapter was found. I have already followed all the tutorials I found on the web. and update the driver of a github repository, and install how much program they told me to install and I still can not connect via wifi. I just do not know what to do. I have a laptop hp 14-bs004 came with windows 10 installed. The information on the network card is as follows: Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: d723] Subsystem: Hewlett-Packard Company Device [103c: 8319] Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort- SERR- Kernel modules: wl already install the most recent kernel, already intale driver driver realtek rtl8723be according to the instructions of the git repository. and nothing has worked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 7 22:57:40 2018 InstallationDate: Installed on 2018-07-08 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_MX.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849598] Re: [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support
** Tags added: verification-done-bionic verification-done-cosmic verification-done-eoan ** Tags removed: verification-done-cosmic ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1849598 Title: [SRU][B/OEM-B/OEM-OSP1/D/E] Add RTL8822cu bluetooth support Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Disco: New Status in linux-firmware source package in Disco: Fix Committed Status in linux-oem source package in Disco: New Status in linux source package in Eoan: New Status in linux-firmware source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: New Bug description: SRU justification: [Impact] Current kernel and firmware lack support of rtl8822cu Bluetooth. [Fix] Add and update the Bluetooth driver and firmware of rtl8822cu. [Test] Verified on hardware. Tests results are good. [Regression Potential] Low. Add new bt chip ID; Add the new firmware and config to enable new bt chip. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1849598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851446] Re: Backport MPLS patches from 5.3 to 4.15
** Changed in: linux (Ubuntu Bionic) 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/1851446 Title: Backport MPLS patches from 5.3 to 4.15 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Bug description: Mellanox is requesting a backport of the following commit IDs from 5.3 back to 4.15. Netdevice HW MPLS features are not passed from device driver's netdevice to upper netdevice, specifically VLAN and bonding netdevice which are created by the kernel when needed. This prevents enablement and usage of HW offloads, such as TSO and checksumming for MPLS tagged traffic when running via VLAN or bonding interface. The patches introduce changes to the initialization steps of the VLAN and bonding netdevices to inherit the MPLS features from lower netdevices to allow the HW offloads. Ariel Levkovich (2): net: bonding: Inherit MPLS features from slave devices net: vlan: Inherit MPLS features from parent device drivers/net/bonding/bond_main.c | 11 +++ net/8021q/vlan_dev.c| 1 + 2 files changed, 12 insertions(+) https://www.mail-archive.com/netdev@vger.kernel.org/msg299084.html Commit IDs (All landed in 5.3) 600bb0318c18e9616d97ad123caaa7c5f7bf222c 8b6912a5019356d7adb1b8a146c9eef5e679bf98 2e770b507ccde8eedc129946e4b78ceed0a22df2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841410] Re: Module extra package is not available for Trusty AWS
This should work, thanks! -- 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/1841410 Title: Module extra package is not available for Trusty AWS Status in ubuntu-kernel-tests: Fix Released Status in linux-aws package in Ubuntu: Won't Fix Status in linux-aws source package in Trusty: Won't Fix Bug description: After bug 1836706, we start shipping the modules-extra for AWS. However this was not applied to Trusty AWS. (As it's ESM now) We will need to turn off the following tests specifically for T-AWS: * quota related test in ubuntu_ltp_syscalls * ubuntu_quota_smoke_test * ubuntu_zram_smoke_test If we're gonna to add this package for it in the future, we can add these tests back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1841410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852521] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852521 Title: Unable to boot "Gave up waiting for root device" for kernel version 5.3.0-19 & 5.3.0-22 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu cannot boot if using kernel version 5.3.0-19 & 5.3.0-22. However, kernel version 5.3.0-18 works fine. The root disk is encrypted. When booting with 5.3.0-18, a passsphrase input field is displayed during boot. However, such an input field does not appear in 5.3.0-19 & 5.3.0-22, which eventually leads to time out and the boot failed. Additional information: When I execute `sudo update-initramfs -c -k 5.3.0-22-generic` It shows the following: > update-initramfs: Generating /boot/initrd.img-5.3.0-22-generic > cryptsetup: WARNING: Skipping root target nvme0n1p5_crypt: uses a key file I feel that the message about the root partition (nvme0n1p5_crypt) using a key file might suggest something wrong? Because actually I didn't use a key file for the root partition, instead only a passphrase is used. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaform2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 21:41:07 2019 InstallationDate: Installed on 2019-11-09 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20LD0017US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic root=UUID=6709141d-5e30-44ef-a676-c3bb559cd47c ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET50W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LD0017US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET50W(1.36):bd07/29/2019:svnLENOVO:pn20LD0017US:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LD0017US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LD0017US dmi.product.sku: LENOVO_MT_20LD_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852521] Re: Unable to boot "Gave up waiting for root device" for kernel version 5.3.0-19 & 5.3.0-22
** Description changed: Ubuntu cannot boot if using kernel version 5.3.0-19 & 5.3.0-22. However, kernel version 5.3.0-18 works fine. The root disk is encrypted. When booting with 5.3.0-18, a passsphrase input field is displayed during boot. However, such an input field does not appear in 5.3.0-19 & 5.3.0-22, which eventually leads to time out and the boot failed. + + Additional information: When I execute `sudo update-initramfs -c -k + 5.3.0-22-generic` + + It shows the following: + + + > update-initramfs: Generating /boot/initrd.img-5.3.0-22-generic + > cryptsetup: WARNING: Skipping root target nvme0n1p5_crypt: uses a key file + + + I feel that the message about the root partition (nvme0n1p5_crypt) using a key file might suggest something wrong? Because actually I didn't use a key file for the root partition, instead only a passphrase is used. + + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: shaform2068 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: shaform2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 21:41:07 2019 InstallationDate: Installed on 2019-11-09 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20LD0017US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic root=UUID=6709141d-5e30-44ef-a676-c3bb559cd47c ro quiet splash RelatedPackageVersions: - linux-restricted-modules-5.3.0-18-generic N/A - linux-backports-modules-5.3.0-18-generic N/A - linux-firmware1.183.1 + linux-restricted-modules-5.3.0-18-generic N/A + linux-backports-modules-5.3.0-18-generic N/A + linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET50W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LD0017US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET50W(1.36):bd07/29/2019:svnLENOVO:pn20LD0017US:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LD0017US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LD0017US dmi.product.sku: LENOVO_MT_20LD_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852521 Title: Unable to boot "Gave up waiting for root device" for kernel version 5.3.0-19 & 5.3.0-22 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu cannot boot if using kernel version 5.3.0-19 & 5.3.0-22. However, kernel version 5.3.0-18 works fine. The root disk is encrypted. When booting with 5.3.0-18, a passsphrase input field is displayed during boot. However, such an input field does not appear in 5.3.0-19 & 5.3.0-22, which eventually leads to time out and the boot failed. Additional information: When I execute `sudo update-initramfs -c -k 5.3.0-22-generic` It shows the following: > update-initramfs: Generating /boot/initrd.img-5.3.0-22-generic > cryptsetup: WARNING: Skipping root target nvme0n1p5_crypt: uses a key file I feel that the message about the root partition (nvme0n1p5_crypt) using a key file might suggest something wrong? Because actually I didn't use a key file for the root partition, instead only a passphrase is used. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaform2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 21:41:07 2019 InstallationDate: Installed on 2019-11-09 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20LD0017US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic root=UUID=6709141d-5e30-44ef-a676-c3bb559cd47c ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183.1 SourcePackage: linux
[Kernel-packages] [Bug 1852521] [NEW] Unable to boot "Gave up waiting for root device" for kernel version 5.3.0-19 & 5.3.0-22
Public bug reported: Ubuntu cannot boot if using kernel version 5.3.0-19 & 5.3.0-22. However, kernel version 5.3.0-18 works fine. The root disk is encrypted. When booting with 5.3.0-18, a passsphrase input field is displayed during boot. However, such an input field does not appear in 5.3.0-19 & 5.3.0-22, which eventually leads to time out and the boot failed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaform2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 21:41:07 2019 InstallationDate: Installed on 2019-11-09 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20LD0017US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic root=UUID=6709141d-5e30-44ef-a676-c3bb559cd47c ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET50W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LD0017US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET50W(1.36):bd07/29/2019:svnLENOVO:pn20LD0017US:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LD0017US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LD0017US dmi.product.sku: LENOVO_MT_20LD_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852521 Title: Unable to boot "Gave up waiting for root device" for kernel version 5.3.0-19 & 5.3.0-22 Status in linux package in Ubuntu: New Bug description: Ubuntu cannot boot if using kernel version 5.3.0-19 & 5.3.0-22. However, kernel version 5.3.0-18 works fine. The root disk is encrypted. When booting with 5.3.0-18, a passsphrase input field is displayed during boot. However, such an input field does not appear in 5.3.0-19 & 5.3.0-22, which eventually leads to time out and the boot failed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaform2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 21:41:07 2019 InstallationDate: Installed on 2019-11-09 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20LD0017US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic root=UUID=6709141d-5e30-44ef-a676-c3bb559cd47c ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET50W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LD0017US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET50W(1.36):bd07/29/2019:svnLENOVO:pn20LD0017US:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LD0017US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LD0017US dmi.product.sku: LENOVO_MT_20LD_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851829] Re: kernel trace found with ubuntu_bpf test on Eoan s390x LPAR
Hi Sean,
there is no report available on the result page, as the job was terminated
abnormally.
For the log on jenkins, you can see that it suddenly stopped:
04:43:31 DEBUG| [stdout] Fork 100 tasks to 'test_hashmap'
04:43:31 DEBUG| [stdout] Fork 100 tasks to 'test_hashmap_percpu'
+ ARCHIVE=/var/lib/jenkins/jobs/sru-1__E_s390x.LPAR
generic__using_s2lp4__for_kernel/builds/3/archive
+ scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -r
ubuntu@s2lp4:kernel-test-results /var/lib/jenkins/jobs/sru-1__E_s390x.LPAR-
generic__using_s2lp4__for_kernel/builds/3/archive
http://10.246.72.4:8080/view/sut-s2lp4/job/sru-1__E_s390x.LPAR-
generic__using_s2lp4__for_kernel/3/consoleText
Or here if the link above is not working:
https://pastebin.ubuntu.com/p/jCDvWBXSKw/
This issue can be reproduced if you run this manually.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851829
Title:
kernel trace found with ubuntu_bpf test on Eoan s390x LPAR
Status in ubuntu-kernel-tests:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Eoan:
Incomplete
Bug description:
This trace can be seen right after you started the test on s390x LPAR.
**
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
** **
** trace_printk() being used. Allocating extra memory. **
** **
** This means that this is a DEBUG kernel and it is **
** unsafe for production use. **
** **
** If you see this message and you are not debugging**
** the kernel, report this immediately to your vendor! **
** **
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
**
WARNING: CPU: 0 PID: 3159 at mm/page_alloc.c:4702
__alloc_pages_nodemask+0x25e/0x318
Modules linked in: xt_conntrack ipt_REJECT nf_reject_ipv4 ip6table_mangle
ip6table_nat nf_tables nfnetlink ip6table_filter ip6_tables iptable_mangle
xt_CHECKSUM iptable_nat xt_MASQUERADE xt_tcpudp bridge iptable_filter bpfilter
aufs overlay 8021q garp stp mrp llc openvswitch nsh nf_conncount nf_nat
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 binfmt_misc zfs(PO) zunicode(PO)
zavl(PO) icp(PO) zlua(PO) zcommon(PO) znvpair(PO) spl(O) genwqe_card crc_itu_t
chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio
sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables
btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear
dm_service_time pkey zcrypt crc32_vx_s390 ghash_s390 prng mlx4_en mlx4_ib
ib_uverbs aes_s390 ib_core ptp pps_core qeth_l2 des_s390 des_generic
sha512_s390 sha256_s390 sha1_s390 sha_common mlx4_core zfcp scsi_transport_fc
qeth qdio ccwgroup
dasd_eckd_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath
CPU: 0 PID: 3159 Comm: test_verifier Tainted: P O
5.3.0-21-generic #22-Ubuntu
Hardware name: IBM 2964 N63 400 (LPAR)
Krnl PSW : 0704c0018000 0002fb832c9e
(__alloc_pages_nodemask+0x25e/0x318)
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
Krnl GPRS: 0003b7efcac0 00040dc0 00040dc0
000a
000a
0002fb6386b8
003d0900 0dc0 03e00b067000
03e00b067000
0003a57a8000 02aa0d1b28e0 03e002b6bb28
03e002b6baa8
Krnl Code: 0002fb832c92: a7212000tmll%r2,8192
0002fb832c96: a774ff87brc 7,2fb832ba4
#0002fb832c9a: a7f40001brc 15,2fb832c9c
>0002fb832c9e: a789lghi%r8,0
0002fb832ca2: a7f4ff83brc 15,2fb832ba8
0002fb832ca6: a718lhi %r1,0
0002fb832caa: a7f4ff1bbrc 15,2fb832ae0
0002fb832cae: e3100344lg %r1,832
Call Trace:
([<03e002b6bb88>] 0x3e002b6bb88)
[<0002fb7ff3a0>] kmalloc_order_trace+0x40/0x100
[<0002fb6386b8>] bpf_int_jit_compile+0x70/0x240
[<0002fb7828ce>] bpf_prog_select_runtime+0x13e/0x190
[<0002fb78614c>] bpf_prog_load+0x2dc/0x6a8
[<0002fb786ca6>] __do_sys_bpf+0x78e/0x10c0
[<0002fbe82228>] system_call+0xdc/0x2c8
Last Breaking-Event-Address:
[<0002fb832c9a>]
[Kernel-packages] [Bug 1852410] Re: package linux-modules-extra-5.3.0-22-generic 5.3.0-22.24 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-extra-5.3.0-22-gener
Do you also have sophos AV installed? It seems to share similar symptom with bug 1852517. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1852410 Title: package linux-modules-extra-5.3.0-22-generic 5.3.0-22.24 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- modules-extra-5.3.0-22-generic.list-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: Bug while doing sudo apt upgrade ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-modules-extra-5.3.0-22-generic 5.3.0-22.24 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1445 F pulseaudio pedro 7241 F pulseaudio Date: Wed Nov 13 09:51:14 2019 ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-extra-5.3.0-22-generic.list-new': Operation not permitted MachineType: ASUSTeK COMPUTER INC. GL552VW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=48209017-932b-457b-9b54-fa05a30fb3cf ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: grub-pc 2.04-1ubuntu12 SourcePackage: linux Title: package linux-modules-extra-5.3.0-22-generic 5.3.0-22.24 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-extra-5.3.0-22-generic.list-new': Operation not permitted UpgradeStatus: Upgraded to eoan on 2019-10-28 (15 days ago) dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.218 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.218:bd03/16/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL552VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852289] Re: bionic/linux: 4.15.0-71.80 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Thursday, 14. November 2019 00:16 UTC
reason:
- prepare-package: Pending -- package not yet uploaded
- prepare-package-lrm: Pending -- package not yet uploaded
- prepare-package-meta: Pending -- package not yet uploaded
- prepare-package-signed: Pending -- package not yet uploaded
+ prepare-package: Ongoing -- {} package not yet fully built
+ promote-to-proposed: Ongoing -- builds not complete in ppa
lrm:depwait,main:building,meta:depwait,signed:depwait
trackers:
bionic/linux-aws: bug 1852270
bionic/linux-fips: bug 1852278
bionic/linux-gke-4.15: bug 1852272
bionic/linux-ibm-gt: bug 1852274
bionic/linux-kvm: bug 1852273
bionic/linux-oem: bug 1852266
bionic/linux-oracle: bug 1852277
bionic/linux-raspi2: bug 1852262
bionic/linux-snapdragon: bug 1852264
bionic/linux/pc-kernel: bug 1852259
bionic/linux/pc-lowlatency-kernel: bug 1852260
xenial/linux-azure: bug 1852282
xenial/linux-gcp: bug 1852285
xenial/linux-hwe: bug 1852288
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/1852289
Title:
bionic/linux: 4.15.0-71.80 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Thursday, 14. November 2019 00:16 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa
lrm:depwait,main:building,meta:depwait,signed:depwait
trackers:
bionic/linux-aws: bug 1852270
bionic/linux-fips: bug 1852278
bionic/linux-gke-4.15: bug 1852272
bionic/linux-ibm-gt: bug 1852274
bionic/linux-kvm: bug 1852273
bionic/linux-oem: bug 1852266
bionic/linux-oracle: bug 1852277
bionic/linux-raspi2: bug 1852262
bionic/linux-snapdragon: bug 1852264
bionic/linux/pc-kernel: bug 1852259
bionic/linux/pc-lowlatency-kernel: bug 1852260
xenial/linux-azure: bug 1852282
xenial/linux-gcp: bug 1852285
xenial/linux-hwe: bug 1852288
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852289/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852517] Re: package linux-headers-5.3.0-22-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.3.0-22-generic/include/config/have/kvm.h.
Solved by disabling sophos AV sudo /opt/sophos-av/bin/savdctl disable -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852517 Title: package linux-headers-5.3.0-22-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: just a failed update in 19.10 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-headers-5.3.0-22-generic (not installed) ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: linux-modules-extra-5.3.0-22-generic:amd64: Install linux-headers-5.3.0-22:amd64: Install linux-headers-5.3.0-22-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1729 F pulseaudio yamin 2092 F pulseaudio /dev/snd/controlC0: gdm1729 F pulseaudio yamin 2092 F pulseaudio Date: Wed Nov 13 20:57:10 2019 DuplicateSignature: package:linux-headers-5.3.0-22-generic:(not installed) Unpacking linux-modules-extra-5.3.0-22-generic (5.3.0-22.24) ... dpkg: error processing archive /var/cache/apt/archives/linux-modules-extra-5.3.0-22-generic_5.3.0-22.24_amd64.deb (--unpack): unable to open '/lib/modules/5.3.0-22-generic/kernel/drivers/input/joystick/spaceball.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=ac7dec92-3af8-4532-8a50-cbbb37da60bd ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: grub-pc 2.04-1ubuntu12 RfKill: SourcePackage: linux Title: package linux-headers-5.3.0-22-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to eoan on 2019-10-25 (19 days ago) dmi.bios.date: 01/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: H87M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd01/13/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852517] [NEW] package linux-headers-5.3.0-22-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.3.0-22-generic/include/config/have/kvm.
Public bug reported: just a failed update in 19.10 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-headers-5.3.0-22-generic (not installed) ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: linux-modules-extra-5.3.0-22-generic:amd64: Install linux-headers-5.3.0-22:amd64: Install linux-headers-5.3.0-22-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1729 F pulseaudio yamin 2092 F pulseaudio /dev/snd/controlC0: gdm1729 F pulseaudio yamin 2092 F pulseaudio Date: Wed Nov 13 20:57:10 2019 DuplicateSignature: package:linux-headers-5.3.0-22-generic:(not installed) Unpacking linux-modules-extra-5.3.0-22-generic (5.3.0-22.24) ... dpkg: error processing archive /var/cache/apt/archives/linux-modules-extra-5.3.0-22-generic_5.3.0-22.24_amd64.deb (--unpack): unable to open '/lib/modules/5.3.0-22-generic/kernel/drivers/input/joystick/spaceball.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=ac7dec92-3af8-4532-8a50-cbbb37da60bd ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: grub-pc 2.04-1ubuntu12 RfKill: SourcePackage: linux Title: package linux-headers-5.3.0-22-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to eoan on 2019-10-25 (19 days ago) dmi.bios.date: 01/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: H87M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd01/13/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852517 Title: package linux-headers-5.3.0-22-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: just a failed update in 19.10 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-headers-5.3.0-22-generic (not installed) ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: linux-modules-extra-5.3.0-22-generic:amd64: Install linux-headers-5.3.0-22:amd64: Install linux-headers-5.3.0-22-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1729 F pulseaudio yamin 2092 F pulseaudio /dev/snd/controlC0: gdm1729 F pulseaudio yamin 2092 F pulseaudio Date: Wed Nov 13 20:57:10 2019 DuplicateSignature: package:linux-headers-5.3.0-22-generic:(not installed) Unpacking linux-modules-extra-5.3.0-22-generic (5.3.0-22.24) ... dpkg: error processing archive /var/cache/apt/archives/linux-modules-extra-5.3.0-22-generic_5.3.0-22.24_amd64.deb (--unpack): unable to open '/lib/modules/5.3.0-22-generic/kernel/drivers/input/joystick/spaceball.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted IwConfig: lono wireless
[Kernel-packages] [Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:21 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
+ prepare-package: Ongoing -- {} package not yet fully built
+ promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:depwait,signed:depwait
trackers:
trusty/linux-aws: bug 1852304
trusty/linux-lts-xenial: bug 1852305
xenial/linux-aws: bug 1852296
xenial/linux-cascade: bug 1852297
xenial/linux-fips: bug 1852303
xenial/linux-kvm: bug 1852298
xenial/linux-raspi2: bug 1852300
xenial/linux-snapdragon: bug 1852302
xenial/linux/caracalla-kernel: bug 1852291
xenial/linux/pc-kernel: bug 1852292
xenial/linux/stlouis-kernel: bug 1852293
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/1852306
Title:
xenial/linux: 4.4.0-170.199 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:21 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa
main:building,meta:depwait,signed:depwait
trackers:
trusty/linux-aws: bug 1852304
trusty/linux-lts-xenial: bug 1852305
xenial/linux-aws: bug 1852296
xenial/linux-cascade: bug 1852297
xenial/linux-fips: bug 1852303
xenial/linux-kvm: bug 1852298
xenial/linux-raspi2: bug 1852300
xenial/linux-snapdragon: bug 1852302
xenial/linux/caracalla-kernel: bug 1852291
xenial/linux/pc-kernel: bug 1852292
xenial/linux/stlouis-kernel: bug 1852293
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852517] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852517 Title: package linux-headers-5.3.0-22-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: just a failed update in 19.10 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-headers-5.3.0-22-generic (not installed) ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: linux-modules-extra-5.3.0-22-generic:amd64: Install linux-headers-5.3.0-22:amd64: Install linux-headers-5.3.0-22-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1729 F pulseaudio yamin 2092 F pulseaudio /dev/snd/controlC0: gdm1729 F pulseaudio yamin 2092 F pulseaudio Date: Wed Nov 13 20:57:10 2019 DuplicateSignature: package:linux-headers-5.3.0-22-generic:(not installed) Unpacking linux-modules-extra-5.3.0-22-generic (5.3.0-22.24) ... dpkg: error processing archive /var/cache/apt/archives/linux-modules-extra-5.3.0-22-generic_5.3.0-22.24_amd64.deb (--unpack): unable to open '/lib/modules/5.3.0-22-generic/kernel/drivers/input/joystick/spaceball.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=ac7dec92-3af8-4532-8a50-cbbb37da60bd ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: grub-pc 2.04-1ubuntu12 RfKill: SourcePackage: linux Title: package linux-headers-5.3.0-22-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to eoan on 2019-10-25 (19 days ago) dmi.bios.date: 01/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: H87M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd01/13/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852510] Re: IO errors when writing large amounts of data to USB storage in eoan on RPI
Note that according to Dave this issue doesn't appear using the Disco kernel -- 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/1852510 Title: IO errors when writing large amounts of data to USB storage in eoan on RPI Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Eoan: New Bug description: Kernel tested: Linux ubuntu 5.3.0-1012-raspi2 #14-Ubuntu SMP Mon Nov 11 10:08:39 UTC 2019 armv7l armv7l armv7l GNU/Linux I've only been able to reproduce this with the armhf kernel and on the following devices: RPI3B+ RPI3B RPI2 At the moment, it does not appear that arm64 is affected, nor are RPI3A+ and RPI4 (at least not the 2GB version) Steps to reproduce: - Insert and mount a USB storage device - cp a large file to it (300-600MB recommended - smaller files will sometimes not trigger it) - sync After running the sync, a lot of IO errors will show up in dmesg like: [ 176.129299] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 176.129326] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 00 2e 24 b0 00 00 f0 00 [ 176.129349] blk_update_request: I/O error, dev sda, sector 3024048 op 0x1:(WRITE) flags 0x4000 phys_seg 15 prio class 0 [ 176.883968] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg [ 177.079960] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg It eventually finishes, and if you unmount/remount the device, the checksum will be different from the original file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852517] Re: package linux-headers-5.3.0-22-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.3.0-22-generic/include/config/have/kvm.h.
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852517 Title: package linux-headers-5.3.0-22-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: just a failed update in 19.10 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-headers-5.3.0-22-generic (not installed) ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: linux-modules-extra-5.3.0-22-generic:amd64: Install linux-headers-5.3.0-22:amd64: Install linux-headers-5.3.0-22-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1729 F pulseaudio yamin 2092 F pulseaudio /dev/snd/controlC0: gdm1729 F pulseaudio yamin 2092 F pulseaudio Date: Wed Nov 13 20:57:10 2019 DuplicateSignature: package:linux-headers-5.3.0-22-generic:(not installed) Unpacking linux-modules-extra-5.3.0-22-generic (5.3.0-22.24) ... dpkg: error processing archive /var/cache/apt/archives/linux-modules-extra-5.3.0-22-generic_5.3.0-22.24_amd64.deb (--unpack): unable to open '/lib/modules/5.3.0-22-generic/kernel/drivers/input/joystick/spaceball.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=ac7dec92-3af8-4532-8a50-cbbb37da60bd ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: grub-pc 2.04-1ubuntu12 RfKill: SourcePackage: linux Title: package linux-headers-5.3.0-22-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.3.0-22-generic/include/config/have/kvm.h.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to eoan on 2019-10-25 (19 days ago) dmi.bios.date: 01/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.40 dmi.board.name: H87M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd01/13/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 22:26 UTC
reason:
- prepare-package: Pending -- package not yet uploaded
- prepare-package-lrm: Pending -- package not yet uploaded
- prepare-package-meta: Pending -- package not yet uploaded
- prepare-package-signed: Pending -- package not yet uploaded
+ prepare-package: Ongoing -- {} package not yet fully built
+ promote-to-proposed: Ongoing -- builds not complete in ppa
lrm:depwait,main:building,meta:depwait,signed:depwait
trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
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/1852232
Title:
eoan/linux: 5.3.0-24.26 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Eoan:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 22:26 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa
lrm:depwait,main:building,meta:depwait,signed:depwait
trackers:
bionic/linux-hwe-edge: bug 1852231
eoan/linux-aws: bug 1852223
eoan/linux-azure: bug 1852225
eoan/linux-gcp: bug 1852227
eoan/linux-kvm: bug 1852228
eoan/linux-oracle: bug 1852230
eoan/linux-raspi2: bug 1852220
eoan/linux/pc-kernel: bug 1852217
eoan/linux/pc-lowlatency-kernel: bug 1852218
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:36 UTC
reason:
- prepare-package: Pending -- package not yet uploaded
- prepare-package-lrm: Pending -- package not yet uploaded
- prepare-package-meta: Pending -- package not yet uploaded
- prepare-package-signed: Pending -- package not yet uploaded
+ prepare-package: Ongoing -- {} package not yet fully built
+ promote-to-proposed: Ongoing -- builds not complete in ppa
lrm:depwait,main:building,meta:depwait,signed:depwait
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
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/1852253
Title:
disco/linux: 5.0.0-37.40 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in 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 --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Packaging
phase-changed: Wednesday, 13. November 2019 19:36 UTC
reason:
prepare-package: Ongoing -- {} package not yet fully built
promote-to-proposed: Ongoing -- builds not complete in ppa
lrm:depwait,main:building,meta:depwait,signed:depwait
trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850574] Re: disco/linux: 5.0.0-34.36 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux (Ubuntu Disco) Status: Fix Released => 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/1850574 Title: disco/linux: 5.0.0-34.36 -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 verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux 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 -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 16:20 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-bluefield: bug 1849002 bionic/linux-hwe: bug 1850587 bionic/linux-oem-osp1: bug 1849001 disco/linux-aws: bug 1848984 disco/linux-azure: bug 1848989 disco/linux-gcp: bug 1848995 disco/linux-kvm: bug 1848996 disco/linux-oracle: bug 1848998 disco/linux-raspi2: bug 1848981 disco/linux-snapdragon: bug 1848999 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849720] Re: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)
@Rafael - Regarding comment #39 The win10.xml dump was after I switched from "e1000e" to "virtio" NIC To reiterate: Freeze happens while using e1000e NO freeze while using virtio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: In Progress Bug description: After upgrading to Ubuntu 19.10 I noticed that all of my Windows Servers VMs would cause a hard crash on the Host OS shortly after starting up the VM. I tracked it down to the Guest OS attempting to use the Network Connection, and if I disabled the virtual NIC for the VM, everything runs OK (albeit without a working network connection for the Guest OS). Note that I'm just using the built in virtual network called "default" that get's installed by default and uses NAT forwarding. I believe the problem is related to AppArmor, as I noticed some errors present in various log files. Unfortunately, due to a time critical project I had to roll back to Ubuntu 19.04 and didn't capture any of the log files. I did, however, find another user on Reddit with the exact same problems that I encountered and he agreed to let me post the log files. Here are what are think are the relevant pieces from the log files: === Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM Oct 22 22:59:23 brian-pc kernel: [ 67.001284] device virbr0-nic left promiscuous mode Oct 22 22:59:23 brian-pc kernel: [ 67.001298] virbr0: port 1(virbr0-nic) entered disabled state Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.3862] device (virbr0-nic): released from master device virbr0 Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer relevant for mDNS. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 192.168.122.1 on virbr0. Oct 22 22:59:23 brian-pc NetworkManager[3557]: [1571799563.6859] device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed') Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that was not added Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that was not added Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script Dispatcher Service... Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection (0x55ccfb376e50), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 0x55ccfb8d15f0 == Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0 55ccfbc736c0 i resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1 55ccfbc73628 i resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2 55ccfbc73588 i resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3 55ccfbc734f0 i resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134) Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4 55ccfbc73430 i self-hosted:979 (7f522262dee0 @ 440) Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9 Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: connectionSettings is null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9 Oct 22 22:59:23 brian-pc gnome-shell[4401]: JS ERROR: TypeError: connectionSettings is
[Kernel-packages] [Bug 1852289] Re: bionic/linux: 4.15.0-71.80 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Packaging - phase-changed: Tuesday, 12. November 2019 14:41 UTC + phase: Packaging + phase-changed: Thursday, 14. November 2019 00:16 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-aws: bug 1852270 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1852274 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1852262 bionic/linux-snapdragon: bug 1852264 bionic/linux/pc-kernel: bug 1852259 bionic/linux/pc-lowlatency-kernel: bug 1852260 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1852288 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/1852289 Title: bionic/linux: 4.15.0-71.80 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Thursday, 14. November 2019 00:16 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-aws: bug 1852270 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1852274 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1852262 bionic/linux-snapdragon: bug 1852264 bionic/linux/pc-kernel: bug 1852259 bionic/linux/pc-lowlatency-kernel: bug 1852260 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1852288 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849855] Re: bionic/linux: 4.15.0-68.77 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Fix Released => 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/1849855 Title: bionic/linux: 4.15.0-68.77 -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 verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 16:25 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-aws: bug 1849016 bionic/linux-fips: bug 1849023 bionic/linux-gke-4.15: bug 1849018 bionic/linux-ibm-gt: bug 1849020 bionic/linux-kvm: bug 1849019 bionic/linux-oem: bug 1851507 bionic/linux-oracle: bug 1849022 bionic/linux-raspi2: bug 1849008 bionic/linux-snapdragon: bug 1849011 bionic/linux/pc-kernel: bug 1849852 bionic/linux/pc-lowlatency-kernel: bug 1849853 unknown/unknown: bug 1849854 xenial/linux-azure: bug 1849027 xenial/linux-gcp: bug 1849031 xenial/linux-hwe: bug 1849854 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852510] Re: IO errors when writing large amounts of data to USB storage in eoan on RPI
** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Critical ** Also affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Eoan) Importance: Undecided => Critical -- 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/1852510 Title: IO errors when writing large amounts of data to USB storage in eoan on RPI Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Eoan: New Bug description: Kernel tested: Linux ubuntu 5.3.0-1012-raspi2 #14-Ubuntu SMP Mon Nov 11 10:08:39 UTC 2019 armv7l armv7l armv7l GNU/Linux I've only been able to reproduce this with the armhf kernel and on the following devices: RPI3B+ RPI3B RPI2 At the moment, it does not appear that arm64 is affected, nor are RPI3A+ and RPI4 (at least not the 2GB version) Steps to reproduce: - Insert and mount a USB storage device - cp a large file to it (300-600MB recommended - smaller files will sometimes not trigger it) - sync After running the sync, a lot of IO errors will show up in dmesg like: [ 176.129299] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 176.129326] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 00 2e 24 b0 00 00 f0 00 [ 176.129349] blk_update_request: I/O error, dev sda, sector 3024048 op 0x1:(WRITE) flags 0x4000 phys_seg 15 prio class 0 [ 176.883968] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg [ 177.079960] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg It eventually finishes, and if you unmount/remount the device, the checksum will be different from the original file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
So far, the latest kernel version is Ubuntu-raspi2-5.3.0-1012.14, it doesn't enable the V3D yet. The next kernel version will include V3D driver module, maybe it will be named 5.3.0-1113. Anyway the kernel that is later than 1012 will include this driver. -- 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/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Committed Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849031] Re: xenial/linux-gcp: 4.15.0-1048.51 -proposed tracker
** Tags removed: kernel-sru-backport-of-1849855 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1849855 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 18:47 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: xenial/linux-gcp/gcp-kernel: bug 1849028 xenial/linux-gcp/gke-kernel: bug 1849029 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-gcp (Ubuntu Xenial) Status: Fix Released => Invalid -- 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/1849031 Title: xenial/linux-gcp: 4.15.0-1048.51 -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 verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 18:47 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: xenial/linux-gcp/gcp-kernel: bug 1849028 xenial/linux-gcp/gke-kernel: bug 1849029 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852289] Re: bionic/linux: 4.15.0-71.80 -proposed tracker
** Summary changed: - bionic/linux: -proposed tracker + bionic/linux: 4.15.0-71.80 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852289 Title: bionic/linux: 4.15.0-71.80 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Thursday, 14. November 2019 00:16 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-aws: bug 1852270 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1852274 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1852262 bionic/linux-snapdragon: bug 1852264 bionic/linux/pc-kernel: bug 1852259 bionic/linux/pc-lowlatency-kernel: bug 1852260 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1852288 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849027] Re: xenial/linux-azure: 4.15.0-1062.67 -proposed tracker
** Tags removed: kernel-sru-backport-of-1849855 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1849855 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 18:46 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: trusty/linux-azure: bug 1849026 xenial/linux-azure-edge: bug 1849025 xenial/linux-azure/azure-kernel: bug 1849024 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-azure (Ubuntu Xenial) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1849027 Title: xenial/linux-azure: 4.15.0-1062.67 -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 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 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 18:46 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: trusty/linux-azure: bug 1849026 xenial/linux-azure-edge: bug 1849025 xenial/linux-azure/azure-kernel: bug 1849024 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852512] [NEW] Update linux-firmware in bionic for 5.3 hwe kernel
Public bug reported: SRU Justification Impact: The transition of the hwe kernel in bionic from 5.0 to 5.3 necessitates addition of new firmware files which are required by drivers in 5.3. Some of these files will also be needed in the installer. Fix: Add the missing files, and update the udebs as required. Test Case: Confirm that the new files are included in the updated packages. Regression Potential: These are new files which are not used by the current kernels in bionic, so no regressions are expected. ** Affects: linux-firmware (Ubuntu) Importance: High Assignee: Seth Forshee (sforshee) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1852512 Title: Update linux-firmware in bionic for 5.3 hwe kernel Status in linux-firmware package in Ubuntu: In Progress Bug description: SRU Justification Impact: The transition of the hwe kernel in bionic from 5.0 to 5.3 necessitates addition of new firmware files which are required by drivers in 5.3. Some of these files will also be needed in the installer. Fix: Add the missing files, and update the udebs as required. Test Case: Confirm that the new files are included in the updated packages. Regression Potential: These are new files which are not used by the current kernels in bionic, so no regressions are expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848989] Re: disco/linux-azure: 5.0.0-1024.25 -proposed tracker
** Tags removed: kernel-sru-derivative-of-1850574 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1850574 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 16:52 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-azure: bug 1848987 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-azure (Ubuntu) Status: Fix Released => Invalid ** Changed in: linux-azure (Ubuntu Disco) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1848989 Title: disco/linux-azure: 5.0.0-1024.25 -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 -- boot-testing-requested: true packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 16:52 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-azure: bug 1848987 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848992] Re: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -proposed tracker
** Tags removed: kernel-sru-backport-of-1848995 ** 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: 1848995 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 16:55 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-gcp-edge: bug 1848991 bionic/linux-gcp/gcp-kernel: bug 1848990 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-gcp (Ubuntu Bionic) Status: Fix Released => Invalid -- 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/1848992 Title: bionic/linux-gcp: 5.0.0-1024.24~18.04.1 -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 verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 16:55 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-gcp-edge: bug 1848991 bionic/linux-gcp/gcp-kernel: bug 1848990 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848995] Re: disco/linux-gcp: 5.0.0-1024.24 -proposed tracker
** Tags removed: kernel-sru-derivative-of-1850574 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1850574 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 16:52 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-gcp: bug 1848992 bionic/linux-gke-5.0: bug 1848994 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-gcp (Ubuntu) Status: Fix Released => Invalid ** Changed in: linux-gcp (Ubuntu Disco) Status: Fix Released => Invalid -- 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/1848995 Title: disco/linux-gcp: 5.0.0-1024.24 -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 verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- boot-testing-requested: true packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 16:52 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-gcp: bug 1848992 bionic/linux-gke-5.0: bug 1848994 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849041] Re: xenial/linux-aws: 4.4.0-1097.108 -proposed tracker
** Tags removed: kernel-sru-derivative-of-1849051 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1849051 packages: main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:47 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: xenial/linux-aws/aws-kernel: bug 1849040 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-aws (Ubuntu Xenial) Status: Fix Released => 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/1849041 Title: xenial/linux-aws: 4.4.0-1097.108 -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 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 packages: main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:47 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: xenial/linux-aws/aws-kernel: bug 1849040 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849051] Re: xenial/linux: 4.4.0-167.196 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Fix Released => 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/1849051 Title: xenial/linux: 4.4.0-167.196 -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 verification-testing series: Invalid 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:46 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: trusty/linux-aws: bug 1849048 trusty/linux-lts-xenial: bug 1849049 xenial/linux-aws: bug 1849041 xenial/linux-fips: bug 1849047 xenial/linux-kvm: bug 1849042 xenial/linux-raspi2: bug 1849044 xenial/linux-snapdragon: bug 1849046 xenial/linux/caracalla-kernel: bug 1849036 xenial/linux/pc-kernel: bug 1849037 xenial/linux/stlouis-kernel: bug 1849038 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849051/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850540] Re: multi-zone raid0 corruption
** Changed in: mdadm (Debian) Status: Unknown => 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/1850540 Title: multi-zone raid0 corruption Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mdadm package in Ubuntu: Confirmed Status in linux source package in Precise: New Status in mdadm source package in Precise: New Status in linux source package in Trusty: Confirmed Status in mdadm source package in Trusty: Confirmed Status in linux source package in Xenial: Confirmed Status in mdadm source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in mdadm source package in Bionic: Confirmed Status in linux source package in Disco: Confirmed Status in mdadm source package in Disco: Confirmed Status in linux source package in Eoan: Confirmed Status in mdadm source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Status in mdadm source package in Focal: Confirmed Status in mdadm package in Debian: New Bug description: Bug 1849682 tracks the temporarily revert of the fix for this issue, while this bug tracks the re-application of that fix once we have a full solution. Fix checklist: [ ] Restore c84a1372df929 md/raid0: avoid RAID0 data corruption due to layout confusion. [ ] Also apply these fixes: 33f2c35a54dfd md: add feature flag MD_FEATURE_RAID0_LAYOUT 3874d73e06c9b md/raid0: fix warning message for parameter default_layout [ ] If upstream, include https://marc.info/?l=linux-raid=157239231220119=2 [ ] mdadm update (see Comment #2) [ ] Packaging work to detect/aide admin before reboot Users of RAID0 arrays are susceptible to a corruption issue if: - The members of the RAID array are not all the same size[*] - Data has been written to the array while running kernels < 3.14 *and* >= 3.14. This is because of an change in v3.14 that accidentally changed how data was written - as described in the upstream commit message: https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 That change has been applied to stable, but we reverted it to fix 1849682 until we have a full solution ready. To summarize, upstream is dealing with this by adding a versioned layout in v5.4, and that is being backported to stable kernels - which is why we're now seeing it. Layout version 1 is the pre-3.14 layout, version 2 is post 3.14. Mixing version 1 & version 2 layouts can cause corruption. However, until an mdadm exists that is able to set a layout in the array, there's no way for the kernel to know which version(s) was used to write the existing data. This undefined mode is considered "Version 0", and the kernel will now refuse to start these arrays w/o user intervention. The user experience is pretty awful here. A user upgrades to the next SRU and all of a sudden their system stops at an (initramfs) prompt. A clueful user can spot something like the following in dmesg: Here's the message which , as you can see from the log in Comment #1, is hidden in a ton of other messages: [ 72.720232] md/raid0:md0: cannot assemble multi-zone RAID0 with default_layout setting [ 72.728149] md/raid0: please set raid.default_layout to 1 or 2 [ 72.733979] md: pers->run() failed ... mdadm: failed to start array /dev/md0: Unknown error 524 What that is trying to say is that you should determine if your data - specifically the data toward the end of your array - was most likely written with a pre-3.14 or post-3.14 kernel. Based on that, reboot with the kernel parameter raid0.default_layout=1 or raid0.default_layout=2 on the kernel command line. And note it should be *raid0.default_layout* not *raid.default_layout* as the message says - a fix for that message is now queued for stable: https://github.com/torvalds/linux/commit/3874d73e06c9b9dc15de0b7382fc223986d75571) IMHO, we should work with upstream to create a web page that clearly walks the user through this process, and update the error message to point to that page. I'd also like to see if we can detect this problem *before* the user reboots (debconf?) and help the user fix things. e.g. "We detected that you have RAID0 arrays that maybe susceptible to a corruption problem", guide the user to choosing a layout, and update the mdadm initramfs hook to poke the answer in via sysfs before starting the array on reboot. Note that it also seems like we should investigate backporting this to < 3.14 kernels. Imagine a user switching between the trusty HWE kernel and the GA kernel. References from users of other distros: https://blog.icod.de/2019/10/10/caution-kernel-5-3-4-and-raid0-default_layout/
[Kernel-packages] [Bug 1849016] Re: bionic/linux-aws: 4.15.0-1053.55 -proposed tracker
** Tags removed: kernel-sru-derivative-of-1849855 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1849855 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 18:41 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-aws-fips: bug 1849014 bionic/linux-aws/aws-kernel: bug 1849013 xenial/linux-aws-hwe: bug 1849015 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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/1849016 Title: bionic/linux-aws: 4.15.0-1053.55 -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 promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 18:41 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-aws-fips: bug 1849014 bionic/linux-aws/aws-kernel: bug 1849013 xenial/linux-aws-hwe: bug 1849015 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848987] Re: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -proposed tracker
** Tags removed: kernel-sru-backport-of-1848989 ** 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: 1848989 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 16:55 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-azure-edge: bug 1848986 bionic/linux-azure/azure-kernel: bug 1848985 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1848987 Title: bionic/linux-azure: 5.0.0-1024.25~18.04.1 -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: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: 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 -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 16:55 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-azure-edge: bug 1848986 bionic/linux-azure/azure-kernel: bug 1848985 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852492] Re: Bionic update: upstream stable patchset 2019-11-13
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852492
Title:
Bionic update: upstream stable patchset 2019-11-13
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2019-11-13
Ported from the following upstream stable releases:
v4.14.152, v4.19.82
from git://git.kernel.org/
zram: fix race between backing_dev_show and backing_dev_store
dm snapshot: use mutex instead of rw_semaphore
dm snapshot: introduce account_start_copy() and account_end_copy()
dm snapshot: rework COW throttling to fix deadlock
dm: Use kzalloc for all structs with embedded biosets/mempools
f2fs: flush quota blocks after turnning it off
scsi: lpfc: Fix a duplicate 0711 log message number.
sc16is7xx: Fix for "Unexpected interrupt: 8"
powerpc/powernv: hold device_hotplug_lock when calling
memtrace_offline_pages()
HID: i2c-hid: add Direkt-Tek DTLAPY133-1 to descriptor override
x86/cpu: Add Atom Tremont (Jacobsville)
HID: i2c-hid: Add Odys Winbook 13 to descriptor override
clk: boston: unregister clks on failure in clk_boston_setup()
scripts/setlocalversion: Improve -dirty check with git-status
--no-optional-locks
HID: Add ASUS T100CHI keyboard dock battery quirks
usb: handle warm-reset port requests on hub resume
rtc: pcf8523: set xtal load capacitance from DT
mlxsw: spectrum: Set LAG port collector only when active
ALSA: hda/realtek - Apply ALC294 hp init also for S4 resume
media: vimc: Remove unused but set variables
exec: load_script: Do not exec truncated interpreter path
PCI/PME: Fix possible use-after-free on remove
power: supply: max14656: fix potential use-after-free
iio: adc: meson_saradc: Fix memory allocation order
iio: fix center temperature of bmc150-accel-core
libsubcmd: Make _FORTIFY_SOURCE defines dependent on the feature
perf tests: Avoid raising SEGV using an obvious NULL dereference
perf map: Fix overlapped map handling
perf jevents: Fix period for Intel fixed counters
staging: rtl8188eu: fix null dereference when kzalloc fails
RDMA/hfi1: Prevent memory leak in sdma_init
RDMA/iwcm: Fix a lock inversion issue
HID: hyperv: Use in-place iterator API in the channel callback
nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request
arm64: ftrace: Ensure synchronisation in PLT setup for Neoverse-N1 #1542419
tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()'
tty: n_hdlc: fix build on SPARC
gpio: max77620: Use correct unit for debounce times
fs: cifs: mute -Wunused-const-variable message
serial: mctrl_gpio: Check for NULL pointer
efi/cper: Fix endianness of PCIe class code
efi/x86: Do not clean dummy variable in kexec path
MIPS: include: Mark __cmpxchg as __always_inline
x86/xen: Return from panic notifier
ocfs2: clear zero in unaligned direct IO
fs: ocfs2: fix possible null-pointer dereferences in ocfs2_xa_prepare_entry()
fs: ocfs2: fix a possible null-pointer dereference in ocfs2_write_end_nolock()
fs: ocfs2: fix a possible null-pointer dereference in
ocfs2_info_scan_inode_alloc()
sched/vtime: Fix guest/system mis-accounting on task switch
perf/x86/amd: Change/fix NMI latency mitigation to use a timestamp
MIPS: include: Mark __xchg as __always_inline
MIPS: fw: sni: Fix out of bounds init of o32 stack
nbd: fix possible sysfs duplicate warning
NFSv4: Fix leak of clp->cl_acceptor string
s390/uaccess: avoid (false positive) compiler warnings
tracing: Initialize iter->seq after zeroing in tracing_read_pipe()
nbd: verify socket is supported during setup
USB: legousbtower: fix a signedness bug in tower_probe()
thunderbolt: Use 32-bit writes when writing ring producer/consumer
fuse: flush dirty data/metadata before non-truncate setattr
fuse: truncate pending writes on O_TRUNC
ALSA: bebob: Fix prototype of helper function to return negative value
UAS: Revert commit 3ae62a42090f ("UAS: fix alignment of scatter/gather
segments")
USB: gadget: Reject endpoints with 0 maxpacket value
usb-storage: Revert commit 747668dbc061 ("usb-storage: Set virt_boundary_mask
to avoid SG overflows")
USB: ldusb: fix ring-buffer locking
USB: ldusb: fix control-message timeout
USB: serial: whiteheat:
[Kernel-packages] [Bug 1852510] [NEW] IO errors when writing large amounts of data to USB storage in eoan on RPI
Public bug reported: Kernel tested: Linux ubuntu 5.3.0-1012-raspi2 #14-Ubuntu SMP Mon Nov 11 10:08:39 UTC 2019 armv7l armv7l armv7l GNU/Linux I've only been able to reproduce this with the armhf kernel and on the following devices: RPI3B+ RPI3B RPI2 At the moment, it does not appear that arm64 is affected, nor are RPI3A+ and RPI4 (at least not the 2GB version) Steps to reproduce: - Insert and mount a USB storage device - cp a large file to it (300-600MB recommended - smaller files will sometimes not trigger it) - sync After running the sync, a lot of IO errors will show up in dmesg like: [ 176.129299] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 176.129326] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 00 2e 24 b0 00 00 f0 00 [ 176.129349] blk_update_request: I/O error, dev sda, sector 3024048 op 0x1:(WRITE) flags 0x4000 phys_seg 15 prio class 0 [ 176.883968] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg [ 177.079960] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg It eventually finishes, and if you unmount/remount the device, the checksum will be different from the original file. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1852510/+attachment/5305257/+files/dmesg.log -- 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/1852510 Title: IO errors when writing large amounts of data to USB storage in eoan on RPI Status in linux-raspi2 package in Ubuntu: New Bug description: Kernel tested: Linux ubuntu 5.3.0-1012-raspi2 #14-Ubuntu SMP Mon Nov 11 10:08:39 UTC 2019 armv7l armv7l armv7l GNU/Linux I've only been able to reproduce this with the armhf kernel and on the following devices: RPI3B+ RPI3B RPI2 At the moment, it does not appear that arm64 is affected, nor are RPI3A+ and RPI4 (at least not the 2GB version) Steps to reproduce: - Insert and mount a USB storage device - cp a large file to it (300-600MB recommended - smaller files will sometimes not trigger it) - sync After running the sync, a lot of IO errors will show up in dmesg like: [ 176.129299] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 176.129326] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 00 2e 24 b0 00 00 f0 00 [ 176.129349] blk_update_request: I/O error, dev sda, sector 3024048 op 0x1:(WRITE) flags 0x4000 phys_seg 15 prio class 0 [ 176.883968] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg [ 177.079960] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg It eventually finishes, and if you unmount/remount the device, the checksum will be different from the original file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852510/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
** Attachment added: "Dmesg for test 5.0 kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+attachment/5305256/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812618] Re: psock_snd from net test in ubuntu_kernel_selftests failed on C
Cosmic has gone EOL. ** Changed in: linux (Ubuntu Cosmic) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812618 Title: psock_snd from net test in ubuntu_kernel_selftests failed on C Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Won't Fix Bug description: This test will fail with Resource temporarily unavailable $ sudo ./psock_snd.sh dgram tx: 128 rx: 142 ./psock_snd: recv: Resource temporarily unavailable ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 21 07:41 seq crw-rw 1 root audio 116, 33 Jan 21 07:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Jan 21 07:49:29 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
By the way, I also tried booting eoan (5.3 kernel) from a USB stick, and it has the same problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
I have just installed your test 5.0 kernel, and unfortunately it does not fix the problem. When I boot the 5.0.0-15 kernel, it works fine. I am using an AMD/RADEON RS780 Gigabyte motherboard. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846486] Re: revert the revert of ext4: make __ext4_get_inode_loc plug
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) 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/1846486 Title: revert the revert of ext4: make __ext4_get_inode_loc plug Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Bug description: == SRU Justification Eoan == Now that 5.4 contains a fix to the bootup regression due to the lack of entropy at bootable we should apply this fix and also revert the revert of commit "Revert "ext4: make __ext4_get_inode_loc plug"". == Fix == So, to clarify, apply the two upstream 5.4-rc commits: commit 50ee7529ec4500c88f8664560770a7a1b65db72b Author: Linus Torvalds Date: Sat Sep 28 16:53:52 2019 -0700 random: try to actively add entropy rather than passively wait for it commit 02f03c4206c1b2a7451d3b3546f86c9c783eac13 Author: Linus Torvalds Date: Sun Sep 29 17:59:23 2019 -0700 Revert "Revert "ext4: make __ext4_get_inode_loc plug"" I've benchmarked the Eoan kernel with these two patches and found theo following speed improvements on an i7-3770 CPU @ 3.40GHz with 8GB and a WDC WD10EZEX-21WN4A HDD (7200RPM, 64MB cache). git grep of the kernel: 0.14% building fwts: 0.40% build stress-ng 0.45% tar up kernel source: 7.6% boot time of eoan cloud image: 10.5% So I think the speed improvements justify the SRU. == Regression potential == minor change to ext4, which has been regression tested, so risk here is small. The entropy change will alter the random number generation, but I believe this does not change the cryptographical security of the random numbers being generated, so think this change is not security risk. originally the ext4 change caused boot time user space regressions because of the entropy change of this fix, but the random fix addresses this, so I believe this risk is now zero. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849214] Re: "nvidia on-demand" mode does not support external displays
After some more research I found out that this is actually due to an unimpelmented feature in Nvidia's drivers. On this model of laptop, the video output ports all connect directly to the discrete Nvidia GPU, and Nvidia's drivers do not yet support the GPU being used as a sink from the integrated GPU and piping the integrated GPU's output to a display. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1849214 Title: "nvidia on-demand" mode does not support external displays Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: In a recent driver, Nvidia finally added Linux support for render offload, where most graphics are rendered on the CPU-onboard GPU and only certain applications are rendered on the discrete Nvidia GPU. I know that Ubuntu 19.10 started shipping some updated Xorg packages to support this. For the most part the mode seems to work great. On my laptop, however, I have found that the "on demand" mode does not detect external monitors (and the monitor says it is not receiving a signal). Switching to "Nvidia" mode, where everything is rendered on the discrete GPU, makes the external displays work. The laptop is a Lenovo Thinkpad X1 Extreme (Gen 1). I have found this occurs both with nvidia-graphics-drivers-435 and nvidia-graphics-drivers-440 in the "graphics-drivers" ppa. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 13:17:38 2019 InstallationDate: Installed on 2019-09-04 (47 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: Upgraded to eoan on 2019-10-21 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-04 (47 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-driver-435 435.21-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: eoan third-party-packages Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-21 (0 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1849214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Packaging - phase-changed: Tuesday, 12. November 2019 13:25 UTC + phase: Packaging + phase-changed: Wednesday, 13. November 2019 22:26 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-hwe-edge: bug 1852231 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1852220 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 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/1852232 Title: eoan/linux: 5.3.0-24.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 13. November 2019 22:26 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-hwe-edge: bug 1852231 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1852220 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850483] Re: eoan/linux-oracle: 5.3.0-1005.5 -proposed tracker
** Tags removed: kernel-sru-derivative-of-1850486 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:43 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-oracle-5.3: bug 1851351 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-oracle (Ubuntu Eoan) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1850483 Title: eoan/linux-oracle: 5.3.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: 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 verification-testing series: Invalid Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: 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 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:43 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-oracle-5.3: bug 1851351 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850481] Re: eoan/linux-gcp: 5.3.0-1007.7 -proposed tracker
** Tags removed: kernel-sru-derivative-of-1850486 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:42 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-gcp-5.3: bug 1850967 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-gcp (Ubuntu Eoan) Status: Fix Released => Invalid -- 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/1850481 Title: eoan/linux-gcp: 5.3.0-1007.7 -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 verification-testing series: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: 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 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:42 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-gcp-5.3: bug 1850967 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** Summary changed: - eoan/linux: -proposed tracker + eoan/linux: 5.3.0-24.26 -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) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** 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) => Connor Kuehl (connork) ** 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) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852232 Title: eoan/linux: 5.3.0-24.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 13. November 2019 22:26 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-hwe-edge: bug 1852231 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1852220 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850486] Re: eoan/linux: 5.3.0-21.22 -proposed tracker
** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux (Ubuntu Eoan) Status: Fix Released => 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/1850486 Title: eoan/linux: 5.3.0-21.22 -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 verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:41 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-hwe-edge: bug 1850485 eoan/linux-aws: bug 1850477 eoan/linux-azure: bug 1850480 eoan/linux-gcp: bug 1850481 eoan/linux-kvm: bug 1850482 eoan/linux-oracle: bug 1850483 eoan/linux-raspi2: bug 1850896 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849022] Re: bionic/linux-oracle: 4.15.0-1028.31 -proposed tracker
** Tags removed: kernel-sru-derivative-of-1849855 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1849855 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: xenial/linux-oracle: bug 1849021 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-oracle (Ubuntu) Status: Fix Released => Invalid ** Changed in: linux-oracle (Ubuntu Bionic) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1849022 Title: bionic/linux-oracle: 4.15.0-1028.31 -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 verification-testing series: Invalid Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: xenial/linux-oracle: bug 1849021 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850477] Re: eoan/linux-aws: 5.3.0-1006.6 -proposed tracker
** Tags removed: kernel-sru-derivative-of-1850486 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:42 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-aws-5.3: bug 1851350 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-aws (Ubuntu Eoan) Status: Fix Released => 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/1850477 Title: eoan/linux-aws: 5.3.0-1006.6 -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 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 Eoan: 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 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:42 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-aws-5.3: bug 1851350 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850480] Re: eoan/linux-azure: 5.3.0-1006.6 -proposed tracker
** Tags removed: kernel-sru-derivative-of-1850486 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1850486 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Signoff phase-changed: Thursday, 07. November 2019 20:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff trackers: bionic/linux-azure-5.3: bug 1850965 variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-azure (Ubuntu Eoan) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1850480 Title: eoan/linux-azure: 5.3.0-1006.6 -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 Eoan: 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 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Signoff phase-changed: Thursday, 07. November 2019 20:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff trackers: bionic/linux-azure-5.3: bug 1850965 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850480/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849682] Re: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting
Aha - found the curtin installation log - this proves the theory in the previous comment: Oct 24 00:03:33 akis cloud-init[2796]: mdadm detail scan after assemble: Oct 24 00:03:33 akis cloud-init[2796]: ARRAY /dev/md/akis:0 level=raid0 num-devices=2 metadata=1.2 name=akis:0 UUID=01fd64cc:287c6b15:429f460f:3d53364b Oct 24 00:03:33 akis cloud-init[2796]:devices=/dev/nvme0n1p2,/dev/nvme1n1 Oct 24 00:03:33 akis cloud-init[2796]: ARRAY /dev/md/akis:1 level=raid0 num-devices=8 metadata=1.2 name=akis:1 UUID=567cc4bb:9ab3f3ac:5d876c61:320a20ad Oct 24 00:03:33 akis cloud-init[2796]: devices=/dev/nvme2n1,/dev/nvme3n1,/dev/nvme4n1,/dev/nvme5n1,/dev/nvme6n1,/dev/nvme7n1,/dev/nvme8n1,/dev/nvme9n1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849682 Title: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Incomplete Bug description: This bug tracks the temporary revert of the upstream fix for a corruption issue. Bug 1850540 tracks the re-application of that fix once we have a full solution. Users of RAID0 arrays are susceptible to a corruption issue if: - The members of the RAID array are not all the same size[*] - Data has been written to the array while running kernels < 3.14 *and* >= 3.14. This is because of an change in v3.14 that accidentally changed how data was written - as described in the upstream commit message: https://github.com/torvalds/linux/commit/c84a1372df929033cb1a0441fb57bd3932f39ac9 To summarize, upstream is dealing with this by adding a versioned layout in v5.4, and that is being backported to stable kernels - which is why we're now seeing it. Layout version 1 is the pre-3.14 layout, version 2 is post 3.14. Mixing version 1 & version 2 layouts can cause corruption. However, unless a layout-version-aware kernel *created* the array, there's no way for the kernel to know which version(s) was used to write the existing data. This undefined mode is considered "Version 0", and the kernel will now refuse to start these arrays w/o user intervention. The user experience is pretty awful here. A user upgrades to the next SRU and all of a sudden their system stops at an (initramfs) prompt. A clueful user can spot something like the following in dmesg: Here's the message which , as you can see from the log in Comment #1, is hidden in a ton of other messages: [ 72.720232] md/raid0:md0: cannot assemble multi-zone RAID0 with default_layout setting [ 72.728149] md/raid0: please set raid.default_layout to 1 or 2 [ 72.733979] md: pers->run() failed ... mdadm: failed to start array /dev/md0: Unknown error 524 What that is trying to say is that you should determine if your data - specifically the data toward the end of your array - was most likely written with a pre-3.14 or post-3.14 kernel. Based on that, reboot with the kernel parameter raid0.default_layout=1 or raid0.default_layout=2 on the kernel command line. And note it should be *raid0.default_layout* not *raid.default_layout* as the message says - a fix for that message is now queued for stable: https://github.com/torvalds/linux/commit/3874d73e06c9b9dc15de0b7382fc223986d75571) IMHO, we should work with upstream to create a web page that clearly walks the user through this process, and update the error message to point to that page. I'd also like to see if we can detect this problem *before* the user reboots (debconf?) and help the user fix things. e.g. "We detected that you have RAID0 arrays that maybe susceptible to a corruption problem", guide the user to choosing a layout, and update the mdadm initramfs hook to poke the answer in via sysfs before starting the array on reboot. Note that it also seems like we should investigate backporting this to < 3.14 kernels. Imagine a user switching between the trusty HWE kernel and the GA kernel. References from users of other distros: https://blog.icod.de/2019/10/10/caution-kernel-5-3-4-and-raid0-default_layout/ https://www.linuxquestions.org/questions/linux-general-1/raid-arrays-not-assembling-4175662774/ [*] Which surprisingly is not the case reported in this bug - the user here had a raid0 of 8 identically-sized devices. I suspect there's a bug in the detection code somewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1849682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1850482] Re: eoan/linux-kvm: 5.3.0-1006.6 -proposed tracker
** Tags removed: kernel-sru-derivative-of-1850486 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1850486 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:43 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-kvm (Ubuntu Eoan) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1850482 Title: eoan/linux-kvm: 5.3.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: 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 Eoan: 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 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Updates phase-changed: Monday, 11. November 2019 10:43 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850967] Re: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -proposed tracker
** Tags removed: kernel-sru-backport-of-1850481 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1850481 packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Ready for Testing phase-changed: Tuesday, 12. November 2019 19:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => 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/1850967 Title: bionic/linux-gcp-5.3: 5.3.0-1007.7~18.04.1 -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 verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules-gcp-5.3 main: linux-gcp-5.3 meta: linux-meta-gcp-5.3 signed: linux-signed-gcp-5.3 phase: Ready for Testing phase-changed: Tuesday, 12. November 2019 19:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850965] Re: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -proposed tracker
** Tags removed: kernel-sru-backport-of-1850480 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1850480 packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Ready for Testing phase-changed: Tuesday, 12. November 2019 19:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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: Fix Released => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => 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/1850965 Title: bionic/linux-azure-5.3: 5.3.0-1006.6~18.04.1 -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 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules-azure-5.3 main: linux-azure-5.3 meta: linux-meta-azure-5.3 signed: linux-signed-azure-5.3 phase: Ready for Testing phase-changed: Tuesday, 12. November 2019 19:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850896] Re: eoan/linux-raspi2: 5.3.0-1011.12 -proposed tracker
** Tags removed: kernel-sru-derivative-of-1850486 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1850486 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Promote to Updates phase-changed: Tuesday, 12. November 2019 22:01 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => 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/security-signoff Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => Invalid ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: Fix Released => Invalid -- 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/1850896 Title: eoan/linux-raspi2: 5.3.0-1011.12 -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-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: 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 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Promote to Updates phase-changed: Tuesday, 12. November 2019 22:01 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1850896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851351] Re: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -proposed tracker
** Tags removed: kernel-sru-backport-of-1850483 ** 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: 1850483 packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Testing phase-changed: Thursday, 07. November 2019 18:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED variant: debs ** Tags removed: kernel-release-tracking-bug-live ** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: Fix Released => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: Fix Released => 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/1851351 Title: bionic/linux-oracle-5.3: 5.3.0-1005.5~18.04.1 -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 verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules-oracle-5.3 main: linux-oracle-5.3 meta: linux-meta-oracle-5.3 signed: linux-signed-oracle-5.3 phase: Testing phase-changed: Thursday, 07. November 2019 18:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1851351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
