[Kernel-packages] [Bug 1839352] [NEW] disco/linux-azure: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839351 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Wednesday, 07. August 2019 16:30 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-azure: bug 1839351 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Disco) Importance: Medium Status: Confirmed ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.07.22-6 kernel-sru-derivative-of-1839106 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: disco kernel-release-tracking-bug ** Also affects: linux-azure (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Disco) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package
[Kernel-packages] [Bug 1839351] [NEW] bionic/linux-azure: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839075 (linux-azure-edge), bug 1839350 (azure-kernel) -- swm properties -- kernel-stable-master-bug: 1839352 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Wednesday, 07. August 2019 16:29 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-azure-edge: bug 1839075 bionic/linux-azure/azure-kernel: bug 1839350 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1839352 kernel-sru-cycle-2019.07.22-6 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing
[Kernel-packages] [Bug 1839106] Re: disco/linux: 5.0.0-25.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 backports: bug 1839099 (bionic/linux-hwe), bug 1839101 (bionic/linux-oem-osp1) - derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug 1839072 (linux-aws), bug 1839082 (linux-azure), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm) + derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug 1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm) -- swm properties -- bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 06. August 2019 19:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1839099 bionic/linux-oem-osp1: bug 1839101 disco/linux-aws: bug 1839072 disco/linux-azure: bug 1839082 disco/linux-gcp: bug 1839093 disco/linux-kvm: bug 1839096 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 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 backports: bug 1839099 (bionic/linux-hwe), bug 1839101 (bionic/linux-oem-osp1) - derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug 1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm) + derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug 1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm), bug 1839352 (linux-azure) -- swm properties -- bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 06. August 2019 19:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1839099 bionic/linux-oem-osp1: bug 1839101 disco/linux-aws: bug 1839072 disco/linux-azure: bug 1839082 disco/linux-gcp: bug 1839093 disco/linux-kvm: bug 1839096 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 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/1839106 Title: disco/linux: 5.0.0-25.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839099 (bionic/linux-hwe), bug 1839101 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug 1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm), bug 1839352 (linux-azure) -- swm properties -- bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signe
[Kernel-packages] [Bug 1837567] Re: disco/linux-azure: 5.0.0-1013.13 -proposed tracker
*** This bug is a duplicate of bug 1839352 *** https://bugs.launchpad.net/bugs/1839352 ** This bug is no longer a duplicate of bug 1839082 disco/linux-azure: 5.0.0-1014.14 -proposed tracker ** This bug has been marked a duplicate of bug 1839352 linux-azure: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1837567 Title: disco/linux-azure: 5.0.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Tuesday, 06. August 2019 05:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1838087 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker
** Summary changed: - xenial/linux-gcp: -proposed tracker + xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Wednesday, 07. August 2019 16:28 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839079] Re: bionic/linux-azure: 5.0.0-1014.14~18.04.1 -proposed tracker
*** This bug is a duplicate of bug 1839351 *** https://bugs.launchpad.net/bugs/1839351 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - derivatives: bug 1839074 (azure-kernel), bug 1839075 (linux-azure-edge) + derivatives: bug 1839075 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1839082 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 06. August 2019 19:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1839075 bionic/linux-azure/azure-kernel: bug 1839074 variant: debs ** Tags removed: kernel-sru-backport-of-1839082 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839075 (linux-azure-edge) -- swm properties -- - kernel-stable-master-bug: 1839082 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 06. August 2019 19:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1839075 bionic/linux-azure/azure-kernel: bug 1839074 variant: debs ** This bug has been marked a duplicate of bug 1839351 linux-azure: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1839079 Title: bionic/linux-azure: 5.0.0-1014.14~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839075 (linux-azure-edge) -- swm properties -- packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 06. August 2019 19:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1839075 bionic/linux-azure/azure-kernel: bug 1839074 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827884] Re: x86: mm: early boot problem on i386 with KPTI enabled
*** This bug is a duplicate of bug 1838115 *** https://bugs.launchpad.net/bugs/1838115 So we use this tags for repositories only? I thought it can be used for a fix in the bug report thread too. ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827884 Title: x86: mm: early boot problem on i386 with KPTI enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Commit d653420532d580156c8486686899ea6a9eeb7bf0 in bionic enabled kernel page table isolation for x86_32, but also introduced regressions. One of them ("BUG_ON() condition in vmalloc_sync_one()") has been addressed by bug 1830433, but there are other issues reported on i386. Specifically on some i386 systems the kernel seems to fail in the early stage of boot (black screen and frozen keyboard) with no error reported on the console. If the kernel is booted with "mitigations=off" and "nopti" the problem doesn't happen (that is a clear indication of being a kernel page table isolation issue). However, users have been reported positive results with the following upstream fixes applied (all clean cherry picks), even with mitigations *and* kernel page table isolation enabled. [Test Case] Unfortuantely this problem is not easily reproducible, the kernel simply fails to boot (black screen and frozen keyboard) after the GRUB prompt, so we don't have a real test case (except asking the bug reporters to boot the kernel and see if it works). [Fix] The following upstream fix seems to resolve (prevent) the problem: 1d8ca3be86ebc6a38dad8236f45c7a9c61681e78 x86/mm/fault: Allow stack access below %rsp aa37c51b9421d66f7931c5fdcb9ce80c450974be x86/mm: Break out user address space handling 8fed6239058adfd8b663344e2f448aed1e7a x86/mm: Break out kernel address space handling 164477c2331be75d9bd57fb76704e676b2bcd1cd x86/mm: Clarify hardware vs. software "error_code" 0e664eee65337082be49fbbd2ee24aa0d111d0f2 Revert "perf/core: Make sure the ring-buffer is mapped in all page-tables" [Regression Potential] All upstream fixes, tested on the affected platform, backport changes are minimal. [Original bug report] NOTE: Boot problems on TWO different laptops after Software Updater updated to kernel 4.15.0-48 Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu desktop. Both fresh installs from minimal CD in early April, originally kernel 0.4.15.0-47, both working fine. Bug report filed on THIS MACHINE: HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel integrated graphics controller GM965/GL960 (with kernel command line parameter ¨video=SVIDEO-1:d¨) SYMPTOM: 4.15.0-48 requires a second ´recovery´ boot to get it up and running. Will not boot properly after a normal shutdown - screen goes funny and it hangs Does boot successfully after a hard shutdown - detects improper shutdown, loads grub menu, then boot successfully Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48 Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots normally after a normal shutdown) OTHER MACHINE: Even older!!! ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility Radeon 9600 GPU. Running with command line parameter "forcepae". SYMPTOM: Won't boot at all. Was working fine under 4.15.0-47 as originally installed, until software updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I can't even get into the grub menu to try the older kernel. More Info on what I've already tried for troubleshooting (on the HP6710b) is outlined in https://answers.launchpad.net/ubuntu/+question/680486 Happy to provide more info if needed, but I'm just an end user user and new to Linux, so will be on a learning curve at this end. (and apologies in advance if this a user problem, and not an actual bug). Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic i686 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1681 F pulseaudio CurrentDesktop: XFCE Date: Mon May 6 21:16:34 2019 MachineType: Hewlett-Packard HP Compaq 6710b PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A
[Kernel-packages] [Bug 1839082] Re: disco/linux-azure: 5.0.0-1014.14 -proposed tracker
*** This bug is a duplicate of bug 1839352 *** https://bugs.launchpad.net/bugs/1839352 ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - - backports: bug 1839079 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 06. August 2019 19:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1839079 variant: debs ** Tags removed: kernel-sru-derivative-of-1839106 ** 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: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 06. August 2019 19:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1839079 variant: debs ** This bug has been marked a duplicate of bug 1839352 linux-azure: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1839082 Title: disco/linux-azure: 5.0.0-1014.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 06. August 2019 19:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1839079 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838087] Re: bionic/linux-azure: 5.0.0-1013.13~18.04.2 -proposed tracker
*** This bug is a duplicate of bug 1839351 *** https://bugs.launchpad.net/bugs/1839351 ** This bug is no longer a duplicate of bug 1839079 bionic/linux-azure: 5.0.0-1014.14~18.04.1 -proposed tracker ** This bug has been marked a duplicate of bug 1839351 linux-azure: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1838087 Title: bionic/linux-azure: 5.0.0-1013.13~18.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 05. August 2019 13:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1837566 bionic/linux-azure/azure-kernel: bug 1838086 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830116] Re: linux-generic: missing module intel_pmc_core
I was check kernel v5.3-rc3. The module exist and currently is build in the kernel but is not load for specific device [ 8086:9d21 ]. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830116 Title: linux-generic: missing module intel_pmc_core Status in linux package in Ubuntu: Confirmed Bug description: Description: linux-5.0.0-15-generic has missing module named 'intel_pmc_core' for device: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) Similar bug #1730770 ? Release: 19.04 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1887 F pulseaudio CasperVersion: 1.405 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 LiveMediaBuild: Ubuntu 19.04 (Disco Dingo) - amd64 (20190523.21) MachineType: Dell Inc. Latitude E7270 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz noprompt boot=casper persistent persistent-path= iso-scan/filename=/disco-desktop-amd64.iso splash toram ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.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: 08/20/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 027I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn027I7V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7270 dmi.product.sku: 06DB dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.2.0-050200rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.2.0-050200rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1186 F pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) MachineType: Dell Inc. Latitude E7270 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=bcc7-cd87-42d3-b789-d5de5ca73c24 ro toram quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 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.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/20/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.6 dmi.board.name: 027I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type
[Kernel-packages] [Bug 1839351] Re: bionic/linux-azure: -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + bionic/linux-azure: -proposed tracker ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839075 (linux-azure-edge), bug 1839350 (azure-kernel) -- swm properties -- kernel-stable-master-bug: 1839352 + packages: + main: linux-azure + meta: linux-meta-azure + signed: linux-signed-azure + phase: Holding before Packaging + phase-changed: Wednesday, 07. August 2019 16:29 UTC + reason: + prepare-package: Holding -- waiting for master bug + trackers: + bionic/linux-azure-edge: bug 1839075 + bionic/linux-azure/azure-kernel: bug 1839350 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1839351 Title: bionic/linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839075 (linux-azure-edge), bug 1839350 (azure- kernel) -- swm properties -- kernel-stable-master-bug: 1839352 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Wednesday, 07. August 2019 16:29 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-azure-edge: bug 1839075 bionic/linux-azure/azure-kernel: bug 1839350 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Ready for Packaging - phase-changed: Wednesday, 07. August 2019 15:36 UTC + phase: Packaging + phase-changed: Wednesday, 07. August 2019 16:28 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 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/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Wednesday, 07. August 2019 16:28 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839352] Re: disco/linux-azure: -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + disco/linux-azure: -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839351 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1839106 + packages: + main: linux-azure + meta: linux-meta-azure + signed: linux-signed-azure + phase: Ready for Packaging + phase-changed: Wednesday, 07. August 2019 16:30 UTC + reason: + prepare-package: Pending -- version not specified + trackers: + bionic/linux-azure: bug 1839351 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1839352 Title: disco/linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839351 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Wednesday, 07. August 2019 16:30 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-azure: bug 1839351 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839106] Re: disco/linux: 5.0.0-25.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 backports: bug 1839099 (bionic/linux-hwe), bug 1839101 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug 1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm), bug 1839352 (linux-azure) -- swm properties -- bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 06. August 2019 19:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1839099 bionic/linux-oem-osp1: bug 1839101 disco/linux-aws: bug 1839072 - disco/linux-azure: bug 1839082 + disco/linux-azure: bug 1839352 disco/linux-gcp: bug 1839093 disco/linux-kvm: bug 1839096 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 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/1839106 Title: disco/linux: 5.0.0-25.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839099 (bionic/linux-hwe), bug 1839101 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug 1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm), bug 1839352 (linux-azure) -- swm properties -- bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 06. August 2019 19:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1839099 bionic/linux-oem-osp1: bug 1839101 disco/linux-aws: bug 1839072 disco/linux-azure: bug 1839352 disco/linux-gcp: bug 1839093 disco/linux-kvm: bug 1839096 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839277] Re: bionic/linux-ibm-gt: 4.15.0-1031.33 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt - phase: Packaging - phase-changed: Wednesday, 07. August 2019 16:09 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 07. August 2019 16:36 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839277 Title: bionic/linux-ibm-gt: 4.15.0-1031.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:36 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837573] Re: disco/linux-snapdragon: 5.0.0-1018.19 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839106 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Testing - phase-changed: Tuesday, 30. July 2019 22:01 UTC + phase: Ready for Testing + phase-changed: Wednesday, 07. August 2019 16:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1837573 Title: disco/linux-snapdragon: 5.0.0-1018.19 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839106 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Ready for Testing phase-changed: Wednesday, 07. August 2019 16:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839260] Re: bionic/linux-snapdragon: 4.15.0-1060.66 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839259 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Packaging - phase-changed: Wednesday, 07. August 2019 15:35 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 07. August 2019 16:36 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839259 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1839260 Title: bionic/linux-snapdragon: 4.15.0-1060.66 -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-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839259 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:36 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839259 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838115] Re: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220
xenial-proposed still doesn't too. The fix for 4.15 does work (https://kernel.ubuntu.com/~cking/lp1827884/4.15). Just copy it to xenial-proposed or something. (Sorry for adding wrong tag, now I know we need to wait for kernel-bot request). ** Tags removed: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838115 Title: linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Fix Released Bug description: == SRU Justification BIONIC HWE, DISCO == Installed Bionic 18.04.2 i386 Desktop (using xubuntu) on a Lenovo x220i and upgraded to proposed. The 5.0.0.22 kernel crashes in various ways with video corruption being a main visible featured. The CPU is a i3-2350M CPU, a 64 bit capable CPU, being booted with EUFI firmware disabled, so using traditional BIOS. 1. Crashes can be just complete hangs, no ability to switch virtual console 2. Crashes may just result in screen turning off, no video and hang and/or reboot 3. Crashes sometimes allow virtual console. Can see watchdog hang checks appearing on 1 or more CPUs. Tried the i386 https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D kernels: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.21/ - same issue https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.17/ - same issue https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.61/ - OK We therefore can conclude: 1. Issue appears between 4.19.61 and 4.20.17 2. Issue is in upstream kernel 3. Issue not a kernel patch per-se (e.g. security fix, ubuntu sauce patch, etc) I repeated this with a VM installation and I don't see the issue, so this probably is a hardware (or firmware?) specific issue. == Fix == Backport wiggle of upstream fix 3f8fd02b1bf1d7ba964485a56f2f4b53ae88c167 ("mm/vmalloc: Sync unmappings in __purge_vmap_area_lazy()") == Test == Without the fix, i386 xubuntu on various Lenovo platforms crash during early boot with random video corruption, hangs,lockups or even reboots. With the fix, it boots fine. == Regression Potential == Higher than normal as this touches the mm sync and the fix has only just hit upstream so it has not much of a soak test. Testing with this shows it fixes a kitten killer breakage, so I think the risk vs benefit is worth considering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839266] Re: bionic/linux-aws: 4.15.0-1045.47 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839264 (xenial/linux-aws-hwe) derivatives: bug 1839263 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-aws meta: linux-meta-aws - phase: Testing - phase-changed: Wednesday, 07. August 2019 14:16 UTC + phase: Ready for Testing + phase-changed: Wednesday, 07. August 2019 16:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws/aws-kernel: bug 1839263 xenial/linux-aws-hwe: bug 1839264 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839266 Title: bionic/linux-aws: 4.15.0-1045.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 backports: bug 1839264 (xenial/linux-aws-hwe) derivatives: bug 1839263 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Testing phase-changed: Wednesday, 07. August 2019 16:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws/aws-kernel: bug 1839263 xenial/linux-aws-hwe: bug 1839264 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839280] Re: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Packaging - phase-changed: Wednesday, 07. August 2019 15:45 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 07. August 2019 16:46 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 + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait trackers: xenial/linux-oracle: bug 1839278 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1839280 Title: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in 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 backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:46 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait trackers: xenial/linux-oracle: bug 1839278 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-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 derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Packaging - phase-changed: Wednesday, 07. August 2019 16:28 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 07. August 2019 16:47 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 + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:depwait trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 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/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:47 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:depwait trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839260] Re: bionic/linux-snapdragon: 4.15.0-1060.66 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839259 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:36 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839259 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1839260 Title: bionic/linux-snapdragon: 4.15.0-1060.66 -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-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839259 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:36 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839259 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839278] Re: xenial/linux-oracle: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Holding before Packaging - phase-changed: Wednesday, 07. August 2019 08:59 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 07. August 2019 16:47 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1839278 Title: xenial/linux-oracle: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Ready for Packaging phase-changed: Wednesday, 07. August 2019 16:47 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830116] Re: linux-generic: missing module intel_pmc_core
One note, the PC has no device ACPI HID "INT33A1" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830116 Title: linux-generic: missing module intel_pmc_core Status in linux package in Ubuntu: Confirmed Bug description: Description: linux-5.0.0-15-generic has missing module named 'intel_pmc_core' for device: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) Similar bug #1730770 ? Release: 19.04 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1887 F pulseaudio CasperVersion: 1.405 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 LiveMediaBuild: Ubuntu 19.04 (Disco Dingo) - amd64 (20190523.21) MachineType: Dell Inc. Latitude E7270 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz noprompt boot=casper persistent persistent-path= iso-scan/filename=/disco-desktop-amd64.iso splash toram ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.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: 08/20/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 027I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn027I7V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7270 dmi.product.sku: 06DB dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.2.0-050200rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.2.0-050200rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1186 F pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) MachineType: Dell Inc. Latitude E7270 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=bcc7-cd87-42d3-b789-d5de5ca73c24 ro toram quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 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.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/20/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.6 dmi.board.name: 027I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.6:bd05/
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:47 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 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/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:47 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839272] Re: bionic/linux-gcp: 4.15.0-1040.42 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839270 (xenial/linux-gcp) derivatives: bug 1839267 (gcp-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 15:36 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait trackers: bionic/linux-gcp/gcp-kernel: bug 1839267 xenial/linux-gcp: bug 1839270 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/1839272 Title: bionic/linux-gcp: 4.15.0-1040.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839270 (xenial/linux-gcp) derivatives: bug 1839267 (gcp-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 15:36 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait trackers: bionic/linux-gcp/gcp-kernel: bug 1839267 xenial/linux-gcp: bug 1839270 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832384] Re: Unable to unmount apparently unused filesystem
We are still seeing this issue and still working on tracking it down. We've done some tracing to track all of the refcount changes by stack when this occurs. However, the refcount is manipulated from many different contexts, making it difficult to identify which increment is the odd one out. We are currently working on a fix / work-around for another bug (https://www.spinics.net/lists/linux-nfs/msg74131.html) that is making our testing of this issue more difficult. Once we have that resolved, it should be a bit easier to make progress on this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832384 Title: Unable to unmount apparently unused filesystem Status in linux package in Ubuntu: Incomplete Bug description: We periodically see an issue where unmounting a ZFS filesystem fails with EBUSY, even though there appears to be no one using it. # cat /proc/self/mounts | grep /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive zfs rw,nosuid,nodev,noexec,relatime,xattr,noacl 0 0 'lsof' and 'fuser' show no processes using any of the files in the problematic filesystem: # ls -l /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/ total 221 -rw-r- 1 500 500 52736 May 22 11:01 1_19_1008904362.dbf -rw-r- 1 500 500 541696 May 22 11:03 1_20_1008904362.dbf # fuser /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/1_20_1008904362.dbf # fuser /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/1_19_1008904362.dbf # fuser /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive/ # lsof | grep /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive # The filesystem was shared over NFS, but has since been unshared: # showmount -e | grep /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive # Since no one appears to be using the filesystem, our expectation is that it should be possible to unmount the filesystem. However, attempts to unmount the filesystem fail with EBUSY: # zfs destroy domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive umount: /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive: target is busy. cannot unmount '/domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive': umount failed # umount /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive umount: /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive: target is busy. Using bpftrace, we can see that the unmount is failing in 'propagate_mount_busy()' in the kernel. Using a live kernel debugger, we can look at the 'mount' struct for this particular mount and see that the 'mnt_count' refcount summed across all CPUs is 2. For filesystems that are eligible for unmounting, the refcount is 1. The only way to work around this issue that we have found is to reboot, at which point the filesystem can be unmounted and destroyed. So far, we have only been able to reproduce this using a workload driven by our application. The application mananges ZFS filesystems in groups, and the lifecycle of each group looks something like - Create and mount a group of filesystems, 1 parent and 4 children: /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370 /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/datafile /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/external /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/archive /domain0/group-38/oracle_db_container-202/oracle_timeflow-16370/temp - Share all 5 filesystems over NFS - A client mounts all 5 shares using NFSv3 - For a few hours, the client does NFS operations on the filesystems and the server occasionally takes ZFS snapshots of them - Unshare filesystems - Unmount filesystems - Delete filesystems These groups of filesystems are constantly being created and destroyed. At any given time, we have ~30k filesystems on the system, about 5k of which are shared. On average, one out of ~200-300k unmounts fails with this EBUSY error. To create and destroy this many filesystems takes us about a week or so. Note that we are using ZFS built from https://github.com/delphix/zfs, which is essentially master ZFS on Linux. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86
[Kernel-packages] [Bug 1839093] Re: disco/linux-gcp: 5.0.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1839093 Title: disco/linux-gcp: 5.0.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839086 (bionic/linux-gke-5.0), bug 1839090 (bionic /linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Tuesday, 06. August 2019 19:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1839090 bionic/linux-gke-5.0: bug 1839086 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
Apologies, comment #32 is incorrect, this worked a couple times but the problem is still present intermittently. I have since downgraded to BIOS v1.2.0 to avoid the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839093] Re: disco/linux-gcp: 5.0.0-1013.13 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839086 (bionic/linux-gke-5.0), bug 1839090 (bionic /linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Tuesday, 06. August 2019 19:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1839090 bionic/linux-gke-5.0: bug 1839086 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/1839093 Title: disco/linux-gcp: 5.0.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839086 (bionic/linux-gke-5.0), bug 1839090 (bionic /linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Tuesday, 06. August 2019 19:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-edge: bug 1839090 bionic/linux-gke-5.0: bug 1839086 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839096] Re: disco/linux-kvm: 5.0.0-1013.14 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839096 Title: disco/linux-kvm: 5.0.0-1013.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1839106 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 06. August 2019 19:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839096] Re: disco/linux-kvm: 5.0.0-1013.14 -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: 1839106 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 06. August 2019 19:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839096 Title: disco/linux-kvm: 5.0.0-1013.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1839106 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 06. August 2019 19:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830116] Re: linux-generic: missing module intel_pmc_core
Hmm I think it exists: P: /devices/platform/INT33A1:00 L: 0 E: DEVPATH=/devices/platform/INT33A1:00 E: SUBSYSTEM=platform E: MODALIAS=acpi:INT33A1:PNP0D80: E: USEC_INITIALIZED=45658112 E: ID_VENDOR_FROM_DATABASE=Interphase Corporation -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830116 Title: linux-generic: missing module intel_pmc_core Status in linux package in Ubuntu: Confirmed Bug description: Description: linux-5.0.0-15-generic has missing module named 'intel_pmc_core' for device: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) Similar bug #1730770 ? Release: 19.04 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1887 F pulseaudio CasperVersion: 1.405 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 LiveMediaBuild: Ubuntu 19.04 (Disco Dingo) - amd64 (20190523.21) MachineType: Dell Inc. Latitude E7270 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz noprompt boot=casper persistent persistent-path= iso-scan/filename=/disco-desktop-amd64.iso splash toram ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.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: 08/20/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 027I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn027I7V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7270 dmi.product.sku: 06DB dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.2.0-050200rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.2.0-050200rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1186 F pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) MachineType: Dell Inc. Latitude E7270 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=bcc7-cd87-42d3-b789-d5de5ca73c24 ro toram quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 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.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/20/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21
[Kernel-packages] [Bug 1839151] [NEW] acpi warnings at boot time
You have been subscribed to a public bug: slow boot with black screen $ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 $ dmesg | grep "report a bug" [0.937327] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug $ lsmod | grep acpi toshiba_acpi 53248 0 sparse_keymap 16384 1 toshiba_acpi industrialio 73728 1 toshiba_acpi wmi28672 2 toshiba_acpi,wmi_bmof video 45056 1 toshiba_acpi $ dmesg | grep acpi [0.156523] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.942577] acpi ABCD:00: ACPI dock station (docks/bays count: 1) [0.947594] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.947816] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM [0.988306] clocksource: acpi_pm: mask: 0xff max_cycles: 0xff, max_idle_ns: 2085701024 ns [5.169375] acpi device:37: registered as cooling_device2 [ 18.730234] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.24 [ 18.838815] toshiba_acpi: WMI event detected, hotkeys will not be monitored [ 18.907530] toshiba_acpi: Supported laptop features: touchpad special-function-keys cooling-method $ dmesg | grep "ACPI" [0.00] BIOS-e820: [mem 0xaa1ee000-0xaa976fff] ACPI NVS [0.00] BIOS-e820: [mem 0xaa99a000-0xaa99efff] ACPI NVS [0.00] BIOS-e820: [mem 0xaf6bf000-0xaf7befff] ACPI NVS [0.00] BIOS-e820: [mem 0xaf7bf000-0xaf7fefff] ACPI data [0.017303] ACPI: Early table checksum verification disabled [0.017551] ACPI: RSDP 0x000FE020 24 (v02 TOSASU) [0.017555] ACPI: XSDT 0xAF7FE210 A4 (v01 TOSASU TOSASU00 0100 0113) [0.017562] ACPI: FACP 0xAF7FA000 00010C (v05 TOSASU TOSASU00 0100 ACPI 0004) [0.017569] ACPI: DSDT 0xAF7DF000 017D26 (v01 TOSASU TOSASU00 ACPI 0004) [0.017573] ACPI: FACS 0xAF7B2000 40 [0.017576] ACPI: ECDT 0xAF7FD000 C1 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017580] ACPI: UEFI 0xAF7FC000 000236 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017584] ACPI: ASF! 0xAF7FB000 A5 (v32 TOSASU TOSASU00 0001 ACPI 0004) [0.017588] ACPI: HPET 0xAF7F9000 38 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017591] ACPI: APIC 0xAF7F8000 8C (v03 TOSASU TOSASU00 0001 ACPI 0004) [0.017595] ACPI: MCFG 0xAF7F7000 3C (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017599] ACPI: SLIC 0xAF7DE000 000176 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017602] ACPI: WDAT 0xAF7DD000 000224 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017606] ACPI: SSDT 0xAF7DB000 001068 (v01 INSYDE CR CRB 1000 ACPI 0004) [0.017610] ACPI: BOOT 0xAF7D9000 28 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017614] ACPI: ASPT 0xAF7D4000 34 (v07 TOSASU TOSASU00 0001 ACPI 0004) [0.017618] ACPI: FPDT 0xAF7D2000 44 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017621] ACPI: SSDT 0xAF7D1000 000937 (v01 INSYDE CR CRB 3000 ACPI 0004) [0.017625] ACPI: SSDT 0xAF7D 000A92 (v01 INSYDE CR CRB 3000 ACPI 0004) [0.017629] ACPI: SSDT 0xAF7CF000 0004AF (v01 INSYDE CR CRB 1000 ACPI 0004) [0.017641] ACPI: Local APIC address 0xfee0 [0.074282] ACPI: PM-Timer IO Port: 0x408 [0.074286] ACPI: Local APIC address 0xfee0 [0.074308] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.074310] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.074312] ACPI: IRQ0 used by override. [0.074314] ACPI: IRQ9 used by override. [0.074316] Using ACPI (MADT) for SMP configuration information [0.074318] ACPI: HPET id: 0x8086a201 base: 0xfed0 [0.122794] ACPI: Core revision 20181213 [0.156523] PM: Registering ACPI NVS region [mem 0xaa1ee000-0xaa976fff] (7901184 bytes) [0.156523] PM: Registering ACPI NVS region [mem 0xaa99a000-0xaa99efff] (20480 bytes) [0.156523] PM: Registering ACPI NVS region [mem 0xaf6bf000-0xaf7befff] (1048576 bytes) [0.156523] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [0.156523] ACPI: bus type PCI registered [0.156523] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.160035] ACPI: Added _OSI(Module Device) [0.160035] ACPI: Added _OSI(Processor Device) [0.160035] ACPI: Added _OSI(3.0 _SCP Extensions) [0.160035] ACPI: Added _OSI(Processor Aggregator Device) [0.160035] ACPI: Added _OSI(Linux-Dell-Video) [0.160035] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [0.160035] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) [0.181030] ACPI: 5 ACPI AML tables
[Kernel-packages] [Bug 1839106] Re: disco/linux: 5.0.0-25.26 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839106 Title: disco/linux: 5.0.0-25.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839099 (bionic/linux-hwe), bug 1839101 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug 1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm), bug 1839352 (linux-azure) -- swm properties -- bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 06. August 2019 19:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1839099 bionic/linux-oem-osp1: bug 1839101 disco/linux-aws: bug 1839072 disco/linux-azure: bug 1839352 disco/linux-gcp: bug 1839093 disco/linux-kvm: bug 1839096 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839119] Re: xenial/linux: 4.4.0-159.187 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839119 Title: xenial/linux: 4.4.0-159.187 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed 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 backports: bug 1839115 (trusty/linux-aws), bug 1839117 (trusty/linux-lts-xenial) derivatives: bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1839103 (pc-kernel), bug 1839107 (linux-aws), bug 1839110 (linux-kvm), bug 1839155 (linux-fips) -- swm properties -- bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 06. August 2019 19:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1839115 trusty/linux-lts-xenial: bug 1839117 xenial/linux-aws: bug 1839107 xenial/linux-fips: bug 1839155 xenial/linux-kvm: bug 1839110 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1839103 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839110] Re: xenial/linux-kvm: 4.4.0-1054.61 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839110 Title: xenial/linux-kvm: 4.4.0-1054.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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 -- kernel-stable-master-bug: 1839119 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 06. August 2019 19:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839106] Re: disco/linux: 5.0.0-25.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 backports: bug 1839099 (bionic/linux-hwe), bug 1839101 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug 1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm), bug 1839352 (linux-azure) -- swm properties -- bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 06. August 2019 19:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1839099 bionic/linux-oem-osp1: bug 1839101 disco/linux-aws: bug 1839072 disco/linux-azure: bug 1839352 disco/linux-gcp: bug 1839093 disco/linux-kvm: bug 1839096 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 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/1839106 Title: disco/linux: 5.0.0-25.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839099 (bionic/linux-hwe), bug 1839101 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug 1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm), bug 1839352 (linux-azure) -- swm properties -- bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 06. August 2019 19:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1839099 bionic/linux-oem-osp1: bug 1839101 disco/linux-aws: bug 1839072 disco/linux-azure: bug 1839352 disco/linux-gcp: bug 1839093 disco/linux-kvm: bug 1839096 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839151] Re: acpi warnings at boot time
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839151 Title: acpi warnings at boot time Status in linux package in Ubuntu: New Bug description: slow boot with black screen $ lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 $ dmesg | grep "report a bug" [0.937327] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug $ lsmod | grep acpi toshiba_acpi 53248 0 sparse_keymap 16384 1 toshiba_acpi industrialio 73728 1 toshiba_acpi wmi28672 2 toshiba_acpi,wmi_bmof video 45056 1 toshiba_acpi $ dmesg | grep acpi [0.156523] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.942577] acpi ABCD:00: ACPI dock station (docks/bays count: 1) [0.947594] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.947816] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM [0.988306] clocksource: acpi_pm: mask: 0xff max_cycles: 0xff, max_idle_ns: 2085701024 ns [5.169375] acpi device:37: registered as cooling_device2 [ 18.730234] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.24 [ 18.838815] toshiba_acpi: WMI event detected, hotkeys will not be monitored [ 18.907530] toshiba_acpi: Supported laptop features: touchpad special-function-keys cooling-method $ dmesg | grep "ACPI" [0.00] BIOS-e820: [mem 0xaa1ee000-0xaa976fff] ACPI NVS [0.00] BIOS-e820: [mem 0xaa99a000-0xaa99efff] ACPI NVS [0.00] BIOS-e820: [mem 0xaf6bf000-0xaf7befff] ACPI NVS [0.00] BIOS-e820: [mem 0xaf7bf000-0xaf7fefff] ACPI data [0.017303] ACPI: Early table checksum verification disabled [0.017551] ACPI: RSDP 0x000FE020 24 (v02 TOSASU) [0.017555] ACPI: XSDT 0xAF7FE210 A4 (v01 TOSASU TOSASU00 0100 0113) [0.017562] ACPI: FACP 0xAF7FA000 00010C (v05 TOSASU TOSASU00 0100 ACPI 0004) [0.017569] ACPI: DSDT 0xAF7DF000 017D26 (v01 TOSASU TOSASU00 ACPI 0004) [0.017573] ACPI: FACS 0xAF7B2000 40 [0.017576] ACPI: ECDT 0xAF7FD000 C1 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017580] ACPI: UEFI 0xAF7FC000 000236 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017584] ACPI: ASF! 0xAF7FB000 A5 (v32 TOSASU TOSASU00 0001 ACPI 0004) [0.017588] ACPI: HPET 0xAF7F9000 38 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017591] ACPI: APIC 0xAF7F8000 8C (v03 TOSASU TOSASU00 0001 ACPI 0004) [0.017595] ACPI: MCFG 0xAF7F7000 3C (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017599] ACPI: SLIC 0xAF7DE000 000176 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017602] ACPI: WDAT 0xAF7DD000 000224 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017606] ACPI: SSDT 0xAF7DB000 001068 (v01 INSYDE CR CRB 1000 ACPI 0004) [0.017610] ACPI: BOOT 0xAF7D9000 28 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017614] ACPI: ASPT 0xAF7D4000 34 (v07 TOSASU TOSASU00 0001 ACPI 0004) [0.017618] ACPI: FPDT 0xAF7D2000 44 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017621] ACPI: SSDT 0xAF7D1000 000937 (v01 INSYDE CR CRB 3000 ACPI 0004) [0.017625] ACPI: SSDT 0xAF7D 000A92 (v01 INSYDE CR CRB 3000 ACPI 0004) [0.017629] ACPI: SSDT 0xAF7CF000 0004AF (v01 INSYDE CR CRB 1000 ACPI 0004) [0.017641] ACPI: Local APIC address 0xfee0 [0.074282] ACPI: PM-Timer IO Port: 0x408 [0.074286] ACPI: Local APIC address 0xfee0 [0.074308] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.074310] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.074312] ACPI: IRQ0 used by override. [0.074314] ACPI: IRQ9 used by override. [0.074316] Using ACPI (MADT) for SMP configuration information [0.074318] ACPI: HPET id: 0x8086a201 base: 0xfed0 [0.122794] ACPI: Core revision 20181213 [0.156523] PM: Registering ACPI NVS region [mem 0xaa1ee000-0xaa976fff] (7901184 bytes) [0.156523] PM: Registering ACPI NVS region [mem 0xaa99a000-0xaa99efff] (20480 bytes) [0.156523] PM: Registering ACPI NVS region [mem 0xaf6bf000-0xaf7befff] (1048576 bytes) [0.156523] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [0.156523] ACPI: bus type PCI registered [0.156523] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.160035] ACPI: Adde
[Kernel-packages] [Bug 1839110] Re: xenial/linux-kvm: 4.4.0-1054.61 -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: 1839119 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 06. August 2019 19:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839110 Title: xenial/linux-kvm: 4.4.0-1054.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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 -- kernel-stable-master-bug: 1839119 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Tuesday, 06. August 2019 19:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839119] Re: xenial/linux: 4.4.0-159.187 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839115 (trusty/linux-aws), bug 1839117 (trusty/linux-lts-xenial) derivatives: bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1839103 (pc-kernel), bug 1839107 (linux-aws), bug 1839110 (linux-kvm), bug 1839155 (linux-fips) -- swm properties -- bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 06. August 2019 19:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1839115 trusty/linux-lts-xenial: bug 1839117 xenial/linux-aws: bug 1839107 xenial/linux-fips: bug 1839155 xenial/linux-kvm: bug 1839110 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1839103 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/1839119 Title: xenial/linux: 4.4.0-159.187 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed 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 backports: bug 1839115 (trusty/linux-aws), bug 1839117 (trusty/linux-lts-xenial) derivatives: bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1839103 (pc-kernel), bug 1839107 (linux-aws), bug 1839110 (linux-kvm), bug 1839155 (linux-fips) -- swm properties -- bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 06. August 2019 19:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1839115 trusty/linux-lts-xenial: bug 1839117 xenial/linux-aws: bug 1839107 xenial/linux-fips: bug 1839155 xenial/linux-kvm: bug 1839110 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1839103 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839280] Re: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:46 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait,signed:depwait trackers: xenial/linux-oracle: bug 1839278 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1839280 Title: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in 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 backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:46 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait,signed:depwait trackers: xenial/linux-oracle: bug 1839278 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839277] Re: bionic/linux-ibm-gt: 4.15.0-1031.33 -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: 1839293 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:36 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839277 Title: bionic/linux-ibm-gt: 4.15.0-1031.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:36 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839151] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1839151 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839151 Title: acpi warnings at boot time Status in linux package in Ubuntu: Incomplete Bug description: slow boot with black screen $ lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 $ dmesg | grep "report a bug" [0.937327] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug $ lsmod | grep acpi toshiba_acpi 53248 0 sparse_keymap 16384 1 toshiba_acpi industrialio 73728 1 toshiba_acpi wmi28672 2 toshiba_acpi,wmi_bmof video 45056 1 toshiba_acpi $ dmesg | grep acpi [0.156523] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [0.942577] acpi ABCD:00: ACPI dock station (docks/bays count: 1) [0.947594] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.947816] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM [0.988306] clocksource: acpi_pm: mask: 0xff max_cycles: 0xff, max_idle_ns: 2085701024 ns [5.169375] acpi device:37: registered as cooling_device2 [ 18.730234] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.24 [ 18.838815] toshiba_acpi: WMI event detected, hotkeys will not be monitored [ 18.907530] toshiba_acpi: Supported laptop features: touchpad special-function-keys cooling-method $ dmesg | grep "ACPI" [0.00] BIOS-e820: [mem 0xaa1ee000-0xaa976fff] ACPI NVS [0.00] BIOS-e820: [mem 0xaa99a000-0xaa99efff] ACPI NVS [0.00] BIOS-e820: [mem 0xaf6bf000-0xaf7befff] ACPI NVS [0.00] BIOS-e820: [mem 0xaf7bf000-0xaf7fefff] ACPI data [0.017303] ACPI: Early table checksum verification disabled [0.017551] ACPI: RSDP 0x000FE020 24 (v02 TOSASU) [0.017555] ACPI: XSDT 0xAF7FE210 A4 (v01 TOSASU TOSASU00 0100 0113) [0.017562] ACPI: FACP 0xAF7FA000 00010C (v05 TOSASU TOSASU00 0100 ACPI 0004) [0.017569] ACPI: DSDT 0xAF7DF000 017D26 (v01 TOSASU TOSASU00 ACPI 0004) [0.017573] ACPI: FACS 0xAF7B2000 40 [0.017576] ACPI: ECDT 0xAF7FD000 C1 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017580] ACPI: UEFI 0xAF7FC000 000236 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017584] ACPI: ASF! 0xAF7FB000 A5 (v32 TOSASU TOSASU00 0001 ACPI 0004) [0.017588] ACPI: HPET 0xAF7F9000 38 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017591] ACPI: APIC 0xAF7F8000 8C (v03 TOSASU TOSASU00 0001 ACPI 0004) [0.017595] ACPI: MCFG 0xAF7F7000 3C (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017599] ACPI: SLIC 0xAF7DE000 000176 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017602] ACPI: WDAT 0xAF7DD000 000224 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017606] ACPI: SSDT 0xAF7DB000 001068 (v01 INSYDE CR CRB 1000 ACPI 0004) [0.017610] ACPI: BOOT 0xAF7D9000 28 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017614] ACPI: ASPT 0xAF7D4000 34 (v07 TOSASU TOSASU00 0001 ACPI 0004) [0.017618] ACPI: FPDT 0xAF7D2000 44 (v01 TOSASU TOSASU00 0001 ACPI 0004) [0.017621] ACPI: SSDT 0xAF7D1000 000937 (v01 INSYDE CR CRB 3000 ACPI 0004) [0.017625] ACPI: SSDT 0xAF7D 000A92 (v01 INSYDE CR CRB 3000 ACPI 0004) [0.017629] ACPI: SSDT 0xAF7CF000 0004AF (v01 INSYDE CR CRB 1000 ACPI 0004) [0.017641] ACPI: Local APIC address 0xfee0 [0.074282] ACPI: PM-Timer IO Port: 0x408 [0.074286] ACPI: Local APIC address 0xfee0 [0.074308] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.074310] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.074312] ACPI: IRQ0 used by override. [0.074314] ACPI: IRQ9 used by override. [0.074316] Using ACPI (MADT) for SMP configuration information [0.074318] ACPI: HPET id: 0x8
[Kernel-packages] [Bug 1834962] Re: add support for Amazon Graviton PCIe controller
** Changed in: linux-aws (Ubuntu Cosmic) Status: In Progress => 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/1834962 Title: add support for Amazon Graviton PCIe controller Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws source package in Cosmic: Invalid Status in linux-aws source package in Disco: Fix Committed Status in linux-aws source package in Eoan: In Progress Status in linux-aws source package in FF-Series: New Bug description: Three patches are needed to add support for Amazon / Annapurna Labs "Graviton" PCIe controller, which is required for future AWS instance types. The feature is to be enabled for Ubuntu kernels >= linux-aws-bionic. The first patch is from mainline; the other two are AWS specific quirks from Amazon Linux, not yet upstream. 4166bfe530 PCI: al: Add Amazon Annapurna Labs PCIe host controller driver UBUNTU: SAUCE: [aws] irqchip/gic-v2m: invoke from gic-v3 initialization and add acpi quirk flow UBUNTU: SAUCE: [aws] arm64: acpi/pci: invoke _DSM whether to preserve firmware PCI setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1834962/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839280] Re: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 07. August 2019 16:46 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 07. August 2019 19:07 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait,signed:depwait + promote-to-proposed: Pending -- ready for review trackers: xenial/linux-oracle: bug 1839278 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1839280 Title: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-oracle package in Ubuntu: Invalid Status in linux-oracle 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 backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Ready for Promote to Proposed phase-changed: Wednesday, 07. August 2019 19:07 UTC reason: promote-to-proposed: Pending -- ready for review trackers: xenial/linux-oracle: bug 1839278 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839272] Re: bionic/linux-gcp: 4.15.0-1040.42 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839270 (xenial/linux-gcp) derivatives: bug 1839267 (gcp-kernel) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 07. August 2019 15:36 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 07. August 2019 19:06 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait + promote-to-proposed: Pending -- ready for review trackers: bionic/linux-gcp/gcp-kernel: bug 1839267 xenial/linux-gcp: bug 1839270 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/1839272 Title: bionic/linux-gcp: 4.15.0-1040.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839270 (xenial/linux-gcp) derivatives: bug 1839267 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Wednesday, 07. August 2019 19:06 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux-gcp/gcp-kernel: bug 1839267 xenial/linux-gcp: bug 1839270 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839277] Re: bionic/linux-ibm-gt: 4.15.0-1031.33 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 07. August 2019 16:36 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 07. August 2019 19:07 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839277 Title: bionic/linux-ibm-gt: 4.15.0-1031.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Ready for Promote to Proposed phase-changed: Wednesday, 07. August 2019 19:07 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:47 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 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/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Wednesday, 07. August 2019 16:47 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805631] Re: Freeze when usb-data-collision with usb-mouse
I'm currently not running that computer, since it became unbearable. During the weekend I will start testing it again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805631 Title: Freeze when usb-data-collision with usb-mouse Status in linux package in Ubuntu: Confirmed Bug description: To my computer I have connected a USB-hub and to that I have attached a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes freezes completely and power button is the only escape. This happens when I scroll the mouse, press a button or moves the mouse (any event from the mouse). This can happen in any running program: Firefox, pdf-viewer, Libreoffice Writer... Most often this comes with my usb-to-ethernet LEDs switch off (during blink), but not always. Seems to be a collision event between my USB-mouse and USB-to-ethernet adapter, i.e mutex. An other computer without the USB-to-ethernet adapter never freezes. Configured in the same way. (I used Ubuntu 14.04 for a long time and this freeze never happened. In 18.04 this happens at least every two weeks. It is the same hardware.) $ uname -a Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 5276 F pulseaudio /dev/snd/controlC0: user 5276 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 MachineType: TOSHIBA SATELLITE Z30-B Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers wireshark WifiSyslog: _MarkForUpload: False dmi.bios.date: 04/09/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.20 dmi.board.asset.tag: 00 dmi.board.name: SATELLITE Z30-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.family: 00 dmi.product.name: SATELLITE Z30-B dmi.product.version: PT258E-007015N5 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830116] Re: linux-generic: missing module intel_pmc_core
Oh, yes. Sorry for confuse. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830116 Title: linux-generic: missing module intel_pmc_core Status in linux package in Ubuntu: Confirmed Bug description: Description: linux-5.0.0-15-generic has missing module named 'intel_pmc_core' for device: 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21) Similar bug #1730770 ? Release: 19.04 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1887 F pulseaudio CasperVersion: 1.405 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 LiveMediaBuild: Ubuntu 19.04 (Disco Dingo) - amd64 (20190523.21) MachineType: Dell Inc. Latitude E7270 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz noprompt boot=casper persistent persistent-path= iso-scan/filename=/disco-desktop-amd64.iso splash toram ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.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: 08/20/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 027I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn027I7V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7270 dmi.product.sku: 06DB dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.2.0-050200rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.2.0-050200rc2-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1186 F pulseaudio DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) MachineType: Dell Inc. Latitude E7270 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=bcc7-cd87-42d3-b789-d5de5ca73c24 ro toram quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 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.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/20/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.6 dmi.board.name: 027I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.6:bd05/20/2019:svnDellInc.:pn
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
Has there been any response from NVIDIA? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839260] Re: bionic/linux-snapdragon: 4.15.0-1060.66 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839259 (dragonboard-kernel) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 07. August 2019 16:36 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 07. August 2019 19:31 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Pending -- ready for review trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839259 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1839260 Title: bionic/linux-snapdragon: 4.15.0-1060.66 -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-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839259 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Ready for Promote to Proposed phase-changed: Wednesday, 07. August 2019 19:31 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839259 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839097] Re: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0
Chceked Wayland login option and still the same bug in dmesg: [ 54.394453] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839097 Title: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 Status in linux package in Ubuntu: Confirmed Bug description: Purged Open source PPA and problem persists: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 10:54:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (226 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro text resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A 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 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839376] [NEW] Bionic update: upstream stable patchset 2019-08-07
Public bug reported: 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-08-07 Ported from the following upstream stable releases: v4.14.137, v4.19.65 from git://git.kernel.org/ ARM: riscpc: fix DMA ARM: dts: rockchip: Make rk3288-veyron-minnie run at hs200 ARM: dts: rockchip: Make rk3288-veyron-mickey's emmc work again ARM: dts: rockchip: Mark that the rk3288 timer might stop in suspend ftrace: Enable trampoline when rec count returns back to one kernel/module.c: Only return -EEXIST for modules that have finished loading MIPS: lantiq: Fix bitfield masking dmaengine: rcar-dmac: Reject zero-length slave DMA requests clk: tegra210: fix PLLU and PLLU_OUT1 fs/adfs: super: fix use-after-free bug btrfs: fix minimum number of chunk errors for DUP cifs: Fix a race condition with cifs_echo_request ceph: fix improper use of smp_mb__before_atomic() ceph: return -ERANGE if virtual xattr value didn't fit in buffer ACPI: blacklist: fix clang warning for unused DMI table scsi: zfcp: fix GCC compiler warning emitted with -Wmaybe-uninitialized x86: kvm: avoid constant-conversion warning ACPI: fix false-positive -Wuninitialized warning be2net: Signal that the device cannot transmit during reconfiguration x86/apic: Silence -Wtype-limits compiler warnings x86: math-emu: Hide clang warnings for 16-bit overflow mm/cma.c: fail if fixed declaration can't be honored coda: add error handling for fget coda: fix build using bare-metal toolchain uapi linux/coda_psdev.h: move upc_req definition from uapi to kernel side headers drivers/rapidio/devices/rio_mport_cdev.c: NUL terminate some strings ipc/mqueue.c: only perform resource calculation if user valid xen/pv: Fix a boot up hang revealed by int3 self test x86/kvm: Don't call kvm_spurious_fault() from .fixup x86/paravirt: Fix callee-saved function ELF sizes x86, boot: Remove multiple copy of static function sanitize_boot_params() drm/nouveau: fix memory leak in nouveau_conn_reset() kbuild: initialize CLANG_FLAGS correctly in the top Makefile Btrfs: fix incremental send failure after deduplication Btrfs: fix race leading to fs corruption after transaction abort mmc: dw_mmc: Fix occasional hang after tuning on eMMC gpiolib: fix incorrect IRQ requesting of an active-low lineevent IB/hfi1: Fix Spectre v1 vulnerability selinux: fix memory leak in policydb_init() s390/dasd: fix endless loop after read unit address configuration parisc: Fix build of compressed kernel even with debug enabled drivers/perf: arm_pmu: Fix failure path in PM notifier nbd: replace kill_bdev() with __invalidate_device() again xen/swiotlb: fix condition for calling xen_destroy_contiguous_region() IB/mlx5: Fix unreg_umr to ignore the mkey state IB/mlx5: Use direct mkey destroy command upon UMR unreg failure IB/mlx5: Move MRs to a kernel PD when freeing them to the MR cache IB/mlx5: Fix RSS Toeplitz setup to be aligned with the HW specification IB/hfi1: Check for error on call to alloc_rsm_map_table eeprom: at24: make spd world-readable again objtool: Support GCC 9 cold subfunction naming scheme gcc-9: properly declare the {pv,hv}clock_page storage x86/vdso: Prevent segfaults due to hoisted vclock reads Documentation: Add swapgs description to the Spectre v1 documentation firmware/psci: psci_checker: Park kthreads before stopping them btrfs: qgroup: Don't hold qgroup_ioctl_lock in btrfs_qgroup_inherit() lib/test_string.c: avoid masking memset16/32/64 failures mmc: meson-mx-sdio: Fix misuse of GENMASK macro arm64: compat: Allow single-byte watchpoints on all addresses arm64: cpufeature: Fix feature comparison for CTR_EL0.{CWG,ERG} IB/mlx5: Fix clean_mr() to work in the expected order ARC: enable uboot support unconditionally scsi: mpt3sas: Use 63-bit DMA addressing on SAS35 HBA UBUNTU: upstream stable to v4.14.137, v4.19.65 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree
[Kernel-packages] [Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers (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/1836630 Title: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend Status in Linux: Unknown Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: After upgrading the Ubuntu kernel to version 5.0.0-21, the System76 Oryx Pro (oryp5) fails to resume from suspend when using discrete NVIDIA graphics The issue can be created on this hardware by following these steps: - Install Ubuntu 18.04.2 - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed - Upgrade: sudo apt-get updatesudo apt-get dist-upgrade - Install 5.0 HWE kernel: sudo apt-get install linux-generic-hwe-18.04-edge - Install NVIDIA driver: sudo apt-get install nvidia-driver-430 - Reboot: sudo reboot - Attempt suspend/resume cycle This occurred after upgrading the kernel from version 5.0.0-20. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: system76 1721 F pulseaudio /dev/snd/controlC0: system76 1721 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 MachineType: System76 Oryx Pro NonfreeKernelModules: nvidia_modeset nvidia Package: linux-hwe-edge ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-21-generic N/A linux-backports-modules-5.0.0-21-generic N/A linux-firmware1.173.9 Tags: bionic Uname: Linux 5.0.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True dmi.bios.date: 05/07/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: oryp5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp5 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1836630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839278] Re: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker
** Summary changed: - xenial/linux-oracle: -proposed tracker + xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => 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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1839278 Title: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Packaging phase-changed: Wednesday, 07. August 2019 20:15 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839278] Re: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Ready for Packaging - phase-changed: Wednesday, 07. August 2019 16:47 UTC + phase: Packaging + phase-changed: Wednesday, 07. August 2019 20:15 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1839278 Title: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Packaging phase-changed: Wednesday, 07. August 2019 20:15 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828578] Re: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
Thanks, I've installed that firmware update and will give it a try. As I expected, disabling bluetooth in BIOS didn't resolve the issue. Apparently in the Dell XPS 13 9730 the wifi card is soldered to the motherboard, so replacing it is sadly not an option. I'm also keeping an eye on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799988 which seems relevant at least to my case. -- 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/1828578 Title: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello Team, Env - Dell XPS 9570 Ubuntu 18.04.2 , HWE kernel We are facing intermittently wifi reconnection issue on Ubuntu 18.04. Software upgrade is up-to date. Also some time we facing freezing issue due to this hard reset required to make machine back to normal. Please let me know if there are any known issue with this particular model on 18.04 ? Please let me know. Thanks Jay --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: itops 1579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-25 (17 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:671d Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=c41f7762-f3a2-4b42-a019-97ca9bd85edc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT-07384 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
Kai-Heng Feng pisze: > Yes I think it's possible. Mount it, chroot (e.g. systemd-nspawn) into > the system and install the kernel packages. > It's all done on kernel v5.2, which is fully bootable and working. The conclusion is that Ubuntu from 16.4.3 till now and all Live CD are unusable, because they are using buggy kernel's >= 4.10 && kernel's < 5.2. They should be patched. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Confirmed Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 07. August 2019 16:47 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 07. August 2019 22:11 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait + promote-to-proposed: Pending -- ready for review trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 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/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Wednesday, 07. August 2019 22:11 UTC reason: promote-to-proposed: Pending -- ready for review trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836971] Re: sched: Prevent CPU lockups when task groups take longer than the period
I installed linux-hwe 4.15.0-57 #63~16.04.1-Ubuntu on xenial, placed a heavy load on the system. Everything seemed stable and no lockups occurred. Due to the successful tests in the hadoop environment under bionic and the nature of this patch being from upstream stable, I am happy to mark this as verified for xenial. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836971 Title: sched: Prevent CPU lockups when task groups take longer than the period Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1836971 [Impact] On machines with extremely high CPU usage, parent task groups which have a large number of children can make the for loop in sched_cfs_period_timer() run until the watchdog fires when the cfs_period_us setting is too short. In this particular case, it is unlikely that the call to hrtimer_forward_now() will return 0, meaning the for loop is never left, and tasks are never rescheduled. The large number of children makes do_sched_cfs_period_timer() take longer than the period, which impacts calls to hrtimer_forward_now(). The kernel will produce this call trace: CPU: 51 PID: 0 Comm: swapper/51 Tainted: P OELK 4.15.0-50-generic #54-Ubuntu Call Trace: ? sched_clock+0x9/0x10 walk_tg_tree_from+0x61/0xd0 ? task_rq_unlock+0x30/0x30 unthrottle_cfs_rq+0xcb/0x1a0 distribute_cfs_runtime+0xd7/0x100 sched_cfs_period_timer+0xd9/0x1a0 ? sched_cfs_slack_timer+0xe0/0xe0 __hrtimer_run_queues+0xdf/0x230 hrtimer_interrupt+0xa0/0x1d0 smp_apic_timer_interrupt+0x6f/0x130 apic_timer_interrupt+0x84/0x90 This has been hit in production in a particularly highly utilised hadoop cluster which is powering an analytics platform. About 30% of the cluster experiences this issue every week, and the machines need a manual reboot to get back online. [Fix] This was fixed in 5.1 upstream with the below commit: commit 2e8e19226398db8265a8e675fcc0118b9e80c9e8 Author: Phil Auld Date: Tue Mar 19 09:00:05 2019 -0400 subject: sched/fair: Limit sched_cfs_period_timer() loop to avoid hard lockup This commit adds a check to see if the loop has run too many times, and if it has, scales up the period and quota, so the timer can complete before the next period expires, which enables the task to be rescheduled normally. Note, 2e8e19226398db8265a8e675fcc0118b9e80c9e8 was included in upstream stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10. This patch requires minor backporting for 4.15, so please cherry pick d069fe4844f8d799d771659a745fe91870c93fda from upstream stable 4.14.y, where the backport has been done by the original author, to all bionic kernels. [Testcase] Kind of hard to reproduce, so this was tested on a production hadoop cluster with extremely high CPU load. I built a test kernel, which is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf232784-test For unpatched kernels, expect the machine to lockup and print the call trace in the impact section. For patched kernels, if the machine hits the condition, it will print a warning to the kernel log with the new period and quota which has been used: Example from the same hadoop cluster with a machine running the test kernel: % uname -a 4.15.0-50-generic #54+hf232784v20190626b1-Ubuntu % sudo grep cfs /var/log/kern.log.* cfs_period_timer[cpu40]: period too short, scaling up (new cfs_period_us 67872, cfs_quota_us = 3475091) cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 22430, cfs_quota_us = 1148437) cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 25759, cfs_quota_us = 1318908) cfs_period_timer[cpu68]: period too short, scaling up (new cfs_period_us 29583, cfs_quota_us = 1514684) cfs_period_timer[cpu49]: period too short, scaling up (new cfs_period_us 33974, cfs_quota_us = 1739519) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 39017, cfs_quota_us = 1997729) cfs_period_timer[cpu10]: period too short, scaling up (new cfs_period_us 44809, cfs_quota_us = 2294267) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 51460, cfs_quota_us = 2634823) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 59099, cfs_quota_us = 3025929) cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 67872, cfs_quota_us = 3475091) [Regression Potential] This patch was accepted into upstream stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10, and is thus treated as stable and trusted by the community. Xenial received this patch in 4.4.0-150.176, as per LP
[Kernel-packages] [Bug 1762940] Re: hibmc-drm Causes Unreadable Display for Huawei amd64 Servers
I installed linux-hwe 4.15.0-57 #63~16.04.1-Ubuntu on xenial, and ensured the -modules and -modules-extra package was installed. I went into /var/lib/modules/4.15.0-56/ and did a search for hibmc_drm. There was no mention apart from a header Makefile. The module was not built and not present on amd64. Tests have been successful on bionic, so I am happy to mark this as fixed for xenial. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: hibmc-drm Causes Unreadable Display for Huawei amd64 Servers Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1762940 [Impact] amd64 based Huawei servers have problems where the display output of their iBMC chips is broken, resulting in a "blurry" screen when viewed from their in house remote kvm-like console. Example: https://launchpadlibrarian.net/365907668/creen_picture_for_blur.png The issue is caused by the hibmc_drm kernel module being loaded. The PCI ID for the iBMC chips on amd64 hardware is the same as arm64 hardware, but the hibmc_drm driver was developed only for use on arm64 hardware, most notably for the Huawei D05 development board. The impact to Huawei is that their customers cannot use Ubuntu server install media as the screen goes "blurry" when the d-i install media or subuqity installer loads the hibmc_drm kernel module after language selection. The only workaround for their customers is to press the "E" key during the very first installer menu and adding "modprobe.blacklist=hibmc_drm" to the kernel command line in the grub menu. This is not good for customer experience with their servers. Other problems exist for the hibmc_drm driver on amd64, such as working on bios, but not uefi, and not being wayland compatible, making the screen blurry whenever a desktop session is started and gdm loaded. Huawei have asked us to remove hibmc_drm from all architectures except arm64, and this aligns with advice from Hisilicon. [Fix] I modified the config/annotations file to remove all architectures except arm64, and created a patch for Kconfig to set a firm requirement on ARM64 for hibmc_drm. I will send the Kconfig patch upstream in the coming days for a more permanent fix. [Testcase] Apply the patches and run: ubuntu-bionic/CONFIGS$ fakeroot debian/rules genconfigs ubuntu-bionic/CONFIGS$ grep -Rin "hibmc" . ./arm64-config.flavour.generic:5739:CONFIG_DRM_HISI_HIBMC=m You should see that only arm64 has the config option enabled. A test kernel has been built, and is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf232667-test Huawei requested a test d-i install iso to test server install with, which can be found here and uses the kernel from the ppa above: https://people.canonical.com/~mruffell/sf232667_ubuntu_server_d-i_20190711b1.iso Both the test kernel and the custom d-i install iso have been tested on amd64 Huawei server hardware successfully and video output is functional. [Regression Potential] Regressions will be limited to hardware containing the iBMC chips from Hisilicon, which I believe are exclusive to Huawei servers. I have taken care to ensure that hibmc_drm is enabled for ARM64 so it should not impact kernels built for the Huawei D05 arm64 development board, and d-i will still load the hibmc_drm driver during startup for arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836816] Re: Fix nf_conntrack races when dealing with same origin requests in NAT environments
I installed linux-hwe 4.15.0-57 #63~16.04.1-Ubuntu on xenial. I have run the reproducers on both bionic and xenial, and both have positive results. This has been tested in the kubernetes environment which had issues, and is performing well. I am happy to mark this as verified for xenial. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836816 Title: Fix nf_conntrack races when dealing with same origin requests in NAT environments Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Bug description: BugLink: https://bugs.launchpad.net/bugs/1836816 [Impact] There are a number of races in nf_conntrack when multiple packets are sent from the same origin to the same destination at the same time, where there is no pre-existing confirmed conntrack entry, in a NAT environment. This is most frequently seen in users with kubernetes workloads, where dns requests are sent from the same socket at the same time, from different threads. One request is for a A record, the other . A conntrack race happens, which leads to one request being dropped, which leads to 5 second dns timeouts. This problem is not specific to kubernetes, as any multi-threaded process which sends UDP packets from the same socket at the same time from different threads is affected. Note that since UDP is connectionless, no packet is sent when connect() is called, so no conntrack entries are created until a packet is first sent. In the scenario where two UDP packets are sent at the same time from the same socket on different threads, there are the following possible races: 1.) Neither of the packets find a confirmed conntrack entry. This leads to two conntrack entries being created with the same tuples. 2.) Same as 1), but a conntrack entry is confirmed for one of the packets before the other calls get_unique_tuple(). The other packet gets a different reply tuple with the source port changed. The outcomes of the races are the same, one of the packets is dropped when it comes time to confirm conntrack entries with __nf_conntrack_confirm(). For more information, read the technical blog post: https://www.weave.works/blog/racy-conntrack-and-dns-lookup-timeouts [Fix] The fix to race 1) was included in 4.19 upstream by this commit: netfilter: nf_conntrack: resolve clash for matching conntracks commit ed07d9a021df6da53456663a76999189badc432a Author: Martynas Pumputis Date: Mon Jul 2 16:52:14 2018 +0200 This commit adds an extra check to see if the two entries are the same and to merge the entries if they are. The fix to race 2) was included in 5.0 upstream by this commit: netfilter: nf_nat: skip nat clash resolution for same-origin entries commit 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 Author: Martynas Pumputis Date: Tue Jan 29 15:51:42 2019 +0100 This commit ensures that a new source port is not allocated to a duplicated entry, and forwards the duplicated entries to be resolved later on. Note that 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 was also backported to stable releases 4.9.163, 4.14.106, 4.19.29, 4.20.16. Both commits cherry-pick to 4.15 bionic cleanly. Please cherry-pick both commits to all bionic kernels. [Testcase] The reproducer has been provided by the author of the fixes, and is best viewed here: https://github.com/brb/conntrack-race The dmesg logs and packet traces in the above github repo are best viewed while reading upstream discussion: https://patchwork.ozlabs.org/patch/937963/ I have built a test kernel for xenial HWE, which can be found here: https://launchpad.net/~mruffell/+archive/ubuntu/sf00227747-test-kernel The test kernel has been tested with a kubernetes workload and aided with resolution of kubernetes problems. [Regression Potential] As noted previously, 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 has been backported to stable releases 4.9.163, 4.14.106, 4.19.29, 4.20.16 and has no changes to the primary commit. This commit is well tested and considered stable by the community. Both commits have also been present in the -azure kernels since 4.15.0-1030.31 and 4.18.0-1004.4, as per LP #1795493, http://bugs.launchpad.net/bugs/1795493 They have received wide testing, and no problems have been reported. The changes are specifically limited to resolving clashes between duplicate conntrack entries, and any regressions will be limited to that scenario. The overall risk of regression is very low. [Notes] The commits in the -azure kernels will need to be reverted before importing the generic bionic updates, since they are the pre-upstream commits, and have had
[Kernel-packages] [Bug 1426216] Re: pci driver messages - BAR 13: no space for
This happens on my system. Meerkat> uname -a Linux Meerkat 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Meerkat> lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic BIOS is up-to-date Meerkat> sudo dmidecode BIOS Information Vendor: Intel Corp. Version: BNKBL357.86A.0069.2018.0920.1250 Release Date: 09/20/2018 Meerkat> dmesg | tail -20 [ 117.574049] pcieport :01:00.0: BAR 13: failed to assign [io size 0x3000] [ 117.574050] pcieport :01:00.0: BAR 13: no space for [io size 0x3000] [ 117.574051] pcieport :01:00.0: BAR 13: failed to assign [io size 0x3000] [ 117.574055] pcieport :02:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] [ 117.574056] pcieport :02:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [ 117.574057] pcieport :02:01.0: BAR 13: no space for [io size 0x1000] [ 117.574057] pcieport :02:01.0: BAR 13: failed to assign [io size 0x1000] [ 117.574058] pcieport :02:02.0: BAR 13: no space for [io size 0x1000] [ 117.574059] pcieport :02:02.0: BAR 13: failed to assign [io size 0x1000] [ 117.574061] pcieport :02:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] [ 117.574062] pcieport :02:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [ 117.574063] pcieport :02:02.0: BAR 13: no space for [io size 0x1000] [ 117.574063] pcieport :02:02.0: BAR 13: failed to assign [io size 0x1000] [ 117.574064] pcieport :02:01.0: BAR 13: no space for [io size 0x1000] [ 117.574065] pcieport :02:01.0: BAR 13: failed to assign [io size 0x1000] [ 122.022075] pcieport :02:00.0: Refused to change power state, currently in D3 [ 122.051009] pci_bus :03: busn_res: [bus 03] is released [ 122.051213] pci_bus :04: busn_res: [bus 04-38] is released [ 122.051378] pci_bus :39: busn_res: [bus 39] is released [ 122.051462] pci_bus :02: busn_res: [bus 02-39] is released Meerkat> sudo lspci -t -[:00]-+-00.0 +-02.0 +-08.0 +-14.0 +-14.2 +-16.0 +-17.0 +-1c.0-[01-39]-- +-1c.5-[3a]00.0 +-1c.7-[3b]00.0 +-1d.0-[3c]00.0 +-1f.0 +-1f.2 +-1f.3 +-1f.4 \-1f.6 Meerkat> sudo lspci -v -nn -s :001c.0 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 16 Bus: primary=00, secondary=01, subordinate=39, sec-latency=0 I/O behind bridge: 2000-2fff Memory behind bridge: c400-da0f Prefetchable memory behind bridge: a000-c1ff Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Intel Corporation Sunrise Point-LP PCI Express Root Port [8086:2068] Capabilities: [a0] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Access Control Services Capabilities: [220] #19 Kernel driver in use: pcieport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1426216 Title: pci driver messages - BAR 13: no space for Status in linux package in Ubuntu: Invalid Bug description: ---Problem Description--- pci driver messages - BAR 13: no space for ---uname output--- 3.18.0-12-generic Machine Type = POWER8 ---Steps to Reproduce--- Install Ubuntu 15.04 daily build running bare-metal After the installation following messages are seen in dmesg. Not sure if these indicate a problem. Can some one look at these and confirm if this is problem or can be ignored ? Messages from dmesg log [0.714476] pci_bus 0001:00: max bus depth: 3 pci_try_num: 4 [0.714519] pci 0001:04:00.0: reg 0x16c: [mem 0x-0x 64bit] [0.714541] pci 0001:04:00.0: reg 0x174: [mem 0x-0x 64bit] [0.714577] pci 0001:00:00.0: BAR 15: assigned [mem 0x3b101000-0x3b103fff 64bit pref] [0.714579] pci 0001:00:00.0: BAR 14: assigned [mem 0x3fe08000-0x3fe081ff] [0.714581] pci 0001:00:00.0: BAR 13: no space for [io size 0x3000] [0.714583] pci 0001:00:00.0: BAR 13: failed to assign [io size 0x3000] [0.714586] pci 0001:01:00.0: BAR 15: assigned [mem 0x3b101000-0x3b103fff 64bit pref] [0.714588] pci 0001:01:00.0: BAR 14: assigned [mem 0x3fe08000-0x3fe0817f] [0.714590] pci 0001:01:00.0: BAR 0: assigned [mem 0x3fe08180-0x3fe08183] [
[Kernel-packages] [Bug 1839395] [NEW] Regressions in CMA allocation rework
Public bug reported: Introduced by the fixes for bug 1823753. [Impact] Crashes (as observed on a nigrogen8m device), and a potential memory leak. [Test Case] Regression tested only. [Fix] f46cc0152501e dma-contiguous: page-align the size in dma_free_contiguous() c6622a425acd1 dma-contiguous: do not overwrite align in dma_alloc_contiguous() [Regression Risk] Bugs in CMA code could lead to device driver errors/crashes. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) 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/1839395 Title: Regressions in CMA allocation rework Status in linux package in Ubuntu: New Status in linux source package in Disco: New Bug description: Introduced by the fixes for bug 1823753. [Impact] Crashes (as observed on a nigrogen8m device), and a potential memory leak. [Test Case] Regression tested only. [Fix] f46cc0152501e dma-contiguous: page-align the size in dma_free_contiguous() c6622a425acd1 dma-contiguous: do not overwrite align in dma_alloc_contiguous() [Regression Risk] Bugs in CMA code could lead to device driver errors/crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839395] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1839395 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Disco) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839395 Title: Regressions in CMA allocation rework Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Incomplete Bug description: Introduced by the fixes for bug 1823753. [Impact] Crashes (as observed on a nigrogen8m device), and a potential memory leak. [Test Case] Regression tested only. [Fix] f46cc0152501e dma-contiguous: page-align the size in dma_free_contiguous() c6622a425acd1 dma-contiguous: do not overwrite align in dma_alloc_contiguous() [Regression Risk] Bugs in CMA code could lead to device driver errors/crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839395] Re: Regressions in CMA allocation rework
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Disco) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839395 Title: Regressions in CMA allocation rework Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Bug description: Introduced by the fixes for bug 1823753. [Impact] Crashes (as observed on a nigrogen8m device), and a potential memory leak. [Test Case] Regression tested only. [Fix] f46cc0152501e dma-contiguous: page-align the size in dma_free_contiguous() c6622a425acd1 dma-contiguous: do not overwrite align in dma_alloc_contiguous() [Regression Risk] Bugs in CMA code could lead to device driver errors/crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838878] Re: Branch 430 does not support K1100M
** Also affects: nvidia-graphics-drivers-418 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1838878 Title: Branch 430 does not support K1100M Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: Branch 430 does not support K1100M, yet it is proposed as an update to branch 418 users with an nVidia K1100M GPU. Please see supported devices for 430 branch here https://www.nvidia.com/Download/driverResults.aspx/149138/en-us and 418 branch here https://www.nvidia.com/Download/driverResults.aspx/149219/en-us It is not possible to downgrade to 418 because the ppa package was replaced by a "transition layer" to branch 430. No changelog was presented by synaptic prior to upgrade to inform user that the nVidia K1100M support was dropped. $ apt-cache showpkg nvidia-driver-418 Package: nvidia-driver-418 Versions: 430.40-0ubuntu0~gpu18.04.1 (/var/lib/apt/lists/ppa.launchpad.net_graphics-drivers_ppa_ubuntu_dists_bionic_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/ppa.launchpad.net_graphics-drivers_ppa_ubuntu_dists_bionic_main_binary-amd64_Packages MD5: 4827e73f0efd6022196ef03ec384d854 Description Language: en File: /var/lib/apt/lists/ppa.launchpad.net_graphics-drivers_ppa_ubuntu_dists_bionic_main_i18n_Translation-en MD5: 4827e73f0efd6022196ef03ec384d854 Reverse Depends: Dependencies: 430.40-0ubuntu0~gpu18.04.1 - nvidia-driver-430 (0 (null)) Provides: 430.40-0ubuntu0~gpu18.04.1 - Reverse Provides: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1838878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1426216] Re: pci driver messages - BAR 13: no space for
** Changed in: linux (Ubuntu) Status: Invalid => 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/1426216 Title: pci driver messages - BAR 13: no space for Status in linux package in Ubuntu: Confirmed Bug description: ---Problem Description--- pci driver messages - BAR 13: no space for ---uname output--- 3.18.0-12-generic Machine Type = POWER8 ---Steps to Reproduce--- Install Ubuntu 15.04 daily build running bare-metal After the installation following messages are seen in dmesg. Not sure if these indicate a problem. Can some one look at these and confirm if this is problem or can be ignored ? Messages from dmesg log [0.714476] pci_bus 0001:00: max bus depth: 3 pci_try_num: 4 [0.714519] pci 0001:04:00.0: reg 0x16c: [mem 0x-0x 64bit] [0.714541] pci 0001:04:00.0: reg 0x174: [mem 0x-0x 64bit] [0.714577] pci 0001:00:00.0: BAR 15: assigned [mem 0x3b101000-0x3b103fff 64bit pref] [0.714579] pci 0001:00:00.0: BAR 14: assigned [mem 0x3fe08000-0x3fe081ff] [0.714581] pci 0001:00:00.0: BAR 13: no space for [io size 0x3000] [0.714583] pci 0001:00:00.0: BAR 13: failed to assign [io size 0x3000] [0.714586] pci 0001:01:00.0: BAR 15: assigned [mem 0x3b101000-0x3b103fff 64bit pref] [0.714588] pci 0001:01:00.0: BAR 14: assigned [mem 0x3fe08000-0x3fe0817f] [0.714590] pci 0001:01:00.0: BAR 0: assigned [mem 0x3fe08180-0x3fe08183] [0.714595] pci 0001:01:00.0: BAR 13: no space for [io size 0x3000] [0.714597] pci 0001:01:00.0: BAR 13: failed to assign [io size 0x3000] [0.714600] pci 0001:02:01.0: BAR 15: assigned [mem 0x3b101000-0x3b101fff 64bit pref] [0.714602] pci 0001:02:08.0: BAR 15: assigned [mem 0x3b102000-0x3b102fff 64bit pref] [0.714604] pci 0001:02:09.0: BAR 15: assigned [mem 0x3b103000-0x3b103fff 64bit pref] [0.714606] pci 0001:02:01.0: BAR 14: assigned [mem 0x3fe08000-0x3fe0807f] [0.714608] pci 0001:02:08.0: BAR 14: assigned [mem 0x3fe08080-0x3fe080ff] [0.714609] pci 0001:02:09.0: BAR 14: assigned [mem 0x3fe08100-0x3fe0817f] [0.714611] pci 0001:02:01.0: BAR 13: no space for [io size 0x1000] [0.714613] pci 0001:02:01.0: BAR 13: failed to assign [io size 0x1000] [0.714614] pci 0001:02:08.0: BAR 13: no space for [io size 0x1000] [0.714616] pci 0001:02:08.0: BAR 13: failed to assign [io size 0x1000] [0.714618] pci 0001:02:09.0: BAR 13: no space for [io size 0x1000] [0.714619] pci 0001:02:09.0: BAR 13: failed to assign [io size 0x1000] [0.714622] pci 0001:03:00.0: BAR 6: assigned [mem 0x3fe08000-0x3fe08003 pref] [0.714624] pci 0001:03:00.1: BAR 6: assigned [mem 0x3fe08004-0x3fe08007 pref] [0.714627] pci 0001:03:00.0: BAR 2: assigned [mem 0x3fe08008-0x3fe080083fff 64bit] [0.714641] pci 0001:03:00.1: BAR 2: assigned [mem 0x3fe080084000-0x3fe080087fff 64bit] [0.714656] pci 0001:03:00.0: BAR 0: assigned [mem 0x3fe080088000-0x3fe080088fff 64bit] [0.714670] pci 0001:03:00.1: BAR 0: assigned [mem 0x3fe080089000-0x3fe080089fff 64bit] [0.714685] pci 0001:03:00.0: BAR 4: no space for [io size 0x0100] [0.714686] pci 0001:03:00.0: BAR 4: failed to assign [io size 0x0100] [0.714688] pci 0001:03:00.1: BAR 4: no space for [io size 0x0100] [0.714690] pci 0001:03:00.1: BAR 4: failed to assign [io size 0x0100] [0.714691] pci 0001:02:01.0: PCI bridge to [bus 03] # lspci :00:00.0 PCI bridge: IBM Device 03dc 0001:00:00.0 PCI bridge: IBM Device 03dc 0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:03:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) 0001:03:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) 0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01) 0002:00:00.0 PCI bridge: IBM Device 03dc 0003:00:00.0 PCI bridge: IBM Device 03dc 0003:01:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0003:02:01.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0003:02:08.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0003:02:09.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0003:02:10.0 PCI bridge: PLX Techn
[Kernel-packages] [Bug 1834550] Re: System hangs after play video from thunderbolt HDD and then S3
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1834550 Title: System hangs after play video from thunderbolt HDD and then S3 Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Fix Released Bug description: [Impact] System hangs after played video from TBT storage, and then suspend the system. It enters suspend correctly, but hangs during waking up. [Fix] There are 2 commits in upstream which fix this issue. 95c80bc6952b PCI/PME: Fix hotplug/sysfs remove deadlock in pcie_pme_remove() 3943af9d01e9 PCI: pciehp: Ignore Link State Changes after powering off a slot [Test] Verified on below thunderbolt interface with thunderbolt HDD 01:00.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev 02) [Regression Potential] Low, both commits have been SRU to Ubuntu Disco 5.0 kernel through stable update, and the fix on remove functions are small and reasonable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1834550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833484] Re: Sometimes touchpad automatically trigger double click
** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833484 Title: Sometimes touchpad automatically trigger double click Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] Dell machines which uses goodix touchpad IC emit double click event while touching the touchpad if designware i2c adapter is in runtime suspend. Goodix re-assert the interrupt if host doesn't read the data within 100ms and designware takes a longer time to wake up from runtime suspend. In the case, it got a second interrupt during resuming, so it thinks it's a double click. [Fix] There is no simple way to fix this, it's a firmware issue and goodix agrees to fix this in their firmware on next release, but this issue is still affects the machines that don't come with an updated firmware. So, add a quirk to mark those machines and avoid the designware from entering runtime suspend. [Regression Potential] Low, it only affects the listed machines, and prevent designware from entering runtime suspend impacts the power consumption little or none during short or long idle. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1833484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] Re: TPM event log does not contain events measured after ExitBootServices
** Description changed: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. - There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 - --- + There are upstream patches to fix this in the mainline kernel tree: https://lore.kernel.org/lkml/20190520205501.177637-1-matthewgarr...@google.com/ + --- 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: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: - eth0 no wireless extensions. - - lono wireless extensions. + eth0 no wireless extensions. + + lono wireless extensions. Lspci: - + Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: - linux-restricted-modules-4.18.0-22-generic N/A - linux-backports-modules-4.18.0-22-generic N/A - linux-firmware 1.173.3 + linux-restricted-modules-4.18.0-22-generic N/A + linux-backports-modules-4.18.0-22-generic N/A + linux-firmware 1.173.3 RfKill: - + Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lore.kernel.org/lkml/20190520205501.177637-1-matthewgarr...@google.com/ --- 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: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_
[Kernel-packages] [Bug 1838796] Re: TPM event log does not contain events measured after ExitBootServices
Hi Jordan - This seems like a nice enhancement and something that will be in Ubuntu once we are shipping a kernel that's v5.3 or newer. I don't expect that we'll backport these patches to our stable releases that ship kernels older than v5.3. This seems to reflect the TPM subsystem maintainer's thoughts as he did not target these patches for linux- stable. If you feel like these patches should be backported, please provide additional justification. Otherwise, we'll have this functionality in a future release. Thanks! ** Information type changed from Public to Public Security ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Triaged Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lore.kernel.org/lkml/20190520205501.177637-1-matthewgarr...@google.com/ --- 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: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine 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 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839253] [NEW] Excessive screen tearing and flickering
You have been subscribed to a public bug: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 02:06:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] InstallationDate: Installed on 2019-08-06 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5201 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:56b9 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA ProcEnviron: TERM=xterm-256color 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=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug disco ubuntu -- Excessive screen tearing and flickering https://bugs.launchpad.net/bugs/1839253 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839253] Re: Excessive screen tearing and flickering
Thanks. The videos seem to show this is a problem with aligning the entire display image. So it's not traditional "tearing", but I totally agree that "tearing" and "flickering" is the best description. Please try logging in to "Ubuntu on Wayland" and tell us if that avoids the problem. Please also try installing a newer kernel such as: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc3/ If the problem still continues then please open a Terminal window and run: dmesg -w Now do you see any new messages appearing in that window when the flickering happens? ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839253 Title: Excessive screen tearing and flickering Status in linux package in Ubuntu: Incomplete Bug description: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 02:06:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] InstallationDate: Installed on 2019-08-06 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5201 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:56b9 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA ProcEnviron: TERM=xterm-256color 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=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832388] Re: [power9] [Cosmic] kernel panic while testing kdump
Manoj, what is next with this bug? Were we able to isolate it to a particular hardware platform? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832388 Title: [power9] [Cosmic] kernel panic while testing kdump Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: I installed cosmic on power9 (boston) a non-nvme system, installed initramfs-tools from -proposed and install kdump-tools. Triggered a dump, but I got a kernel panic. This might be a kernel bug/regression. ubuntu@tiselius:~$ uname -a Linux tiselius 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@tiselius:~$ ubuntu@tiselius:~$ apt policy initramfs-tools initramfs-tools: Installed: 0.131ubuntu15.2 Candidate: 0.131ubuntu15.2 Version table: *** 0.131ubuntu15.2 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic-proposed/main ppc64el Packages ubuntu@tiselius:~$ ubuntu@tiselius:~$ apt policy kdump-tools kdump-tools: Installed: 1:1.6.5-1ubuntu1~18.10.1 Candidate: 1:1.6.5-1ubuntu1~18.10.1 Version table: *** 1:1.6.5-1ubuntu1~18.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic-updates/main ppc64el Packages 100 /var/lib/dpkg/status 1:1.6.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic/main ppc64el Packages ubuntu@tiselius:~$ ubuntu@tiselius:~$ sudo kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.18.0-21-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.18.0-21-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz ubuntu@tiselius:~$ ubuntu@tiselius:~$ cat /proc/cmdline root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M ubuntu@tiselius:~$ ubuntu@tiselius:~$ dmesg | grep Reser [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System RAM: 131072MB) [0.00] cma: Reserved 6560 MiB at 0x200e6200 ubuntu@tiselius:~$ root@tiselius:/home/ubuntu# echo 1 > /proc/sys/kernel/sysrq root@tiselius:/home/ubuntu# echo c > /proc/sysrq-trigger tiselius login: [ 150.167288] cloud-init[4529]: Cloud-init v. 19.1-1-gbaa47854-0ubuntu1~18.10.1 running 'modules:final' at Mon, 10 Jun 2019 19:53:40 +. Up 149.80 seconds. [ 150.167687] cloud-init[4529]: Cloud-init v. 19.1-1-gbaa47854-0ubuntu1~18.10.1 finished at Mon, 10 Jun 2019 19:53:40 +. Datasource DataSourceMAAS [http://10-245-64-0--21.maas-internal:5248/MAAS/metadata/]. Up 150.11 seconds [ 360.313029] kdump-tools[4915]: Stopping kdump-tools: * unloaded kdump kernel [ 376.552452] kdump-tools[10449]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz [ 376.553743] kdump-tools[10449]: * Creating symlink /var/lib/kdump/initrd.img [ 376.585085] kdump-tools[10449]: Modified cmdline:root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb elfcorehdr=158784K [ 376.953223] kdump-tools[10449]: * loaded kdump kernel [ 398.517900] sysrq: SysRq : Trigger a crash [ 398.517952] Unable to handle kernel paging request for data at address 0x [ 398.518000] Faulting instruction address: 0xc082a3a8 [ 398.518071] Oops: Kernel access of bad area, sig: 11 [#1] [ 398.518115] LE SMP NR_CPUS=2048 NUMA PowerNV [ 398.518172] Modules linked in: joydev input_leds mac_hid vmx_crypto ofpart crct10dif_vpmsum ipmi_powernv ipmi_devintf at24 uio_pdrv_genirq ipmi_msghandler uio cmdlinepart powernv_flash mtd opal_prd ibmpowernv sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas hid_generic usbhid hid ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm crc32c_vpmsum i40e aacraid drm_panel_orientation_quirks [ 398.518769] CPU: 0 PID: 10529 Comm: bash Kdump: loaded Not tainted 4.18.0-21-generic #22-Ubuntu [ 398.518881] NIP: c082a3a8 LR: c082b234 CTR: c00
[Kernel-packages] [Bug 1839006] Re: No sound is playing from this laptop
** Attachment added: "client_2.conf" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+attachment/5281523/+files/client_2.conf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839006] Re: No sound is playing from this laptop
Adding this line to the conf file does not generate the a.txt file on startup. I tried adding the line, altering the line with the extra arguments tags and adding to the extra arguments variable ** Attachment added: "tmp_list.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+attachment/5281521/+files/tmp_list.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839006] Re: No sound is playing from this laptop
** Attachment added: "client_1.conf" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+attachment/5281522/+files/client_1.conf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839006] Re: No sound is playing from this laptop
** Attachment added: "client_3.conf" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+attachment/5281524/+files/client_3.conf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835001] Re: System does not auto detect disconnection of external monitor
These are the -1014 changelog, there is only one commit related to Nvidia linux-oem-osp1 (5.0.0-1014.15) bionic; urgency=medium * linux-oem-osp1: 5.0.0-1014.15 -proposed tracker (LP: #1836161) * Intel ethernet I219 may wrongly detect connection speed as 10Mbps (LP: #1836177) - e1000e: Make watchdog use delayed work * Intel ethernet I219 has slow RX speed (LP: #1836152) - e1000e: add workaround for possible stalled packet - e1000e: disable force K1-off feature * headphone-mic doesn't work on a couple of dell machines (alsa/realtek) (LP: #1836132) - SAUCE: ALSA: hda/realtek - headphone mic doesn't work on two Dell machines * Unhide Nvidia HDA audio controller (LP: #1836308) - PCI: Enable NVIDIA HDA controllers * Sometimes touchpad(goodix) can't use tap function (LP: #1836020) - SAUCE: i2c: designware: add Inpiron/Vostro 7590 into i2c quirk - SAUCE: i2c: designware: add Inpiron 7591 into i2c quirk * enable realtek ethernet device ASPM function (LP: #1836030) - SAUCE: PCI/ASPM: add L1 sub-state support to pci_disable_link_state - SAUCE: PCI/ASPM: allow to re-enable Clock PM - SAUCE: PCI/ASPM: add sysfs attribute for controlling ASPM - SAUCE: Revert "r8169: disable ASPM again" * backport pmc_core (LP: #1836012) - platform/x86: intel_pmc_core: Fix file permissions for ltr_show - platform/x86: intel_pmc_core: Include Reserved IP for LTR - platform/x86: intel_pmc_core: Avoid a u32 overflow - platform/x86: intel_pmc_core: Convert to INTEL_CPU_FAM6 macro - platform/x86: intel_pmc_core: Add ICL platform support - platform/x86: intel_pmc_core: Add Package cstates residency info - platform/x86: intel_pmc_core: Mark local function static - platform/x86: intel_pmc_core: Convert to a platform_driver - platform/x86: intel_pmc_core: Allow to dump debug registers on S0ix failure * Intel Wireless-AC 9462/9560 not supported on ICL (LP: #1835879) - iwlwifi: add new cards for 9000 and 2 series - iwlwifi: pcie: add support for qu c-step devices * Add DMIC support to oem-kernel (LP: #1826181) - ASoC: SOF: hda: fix link DMA config - ASoC: SOF: hda: fix stream id setting - ALSA: hda: realtek - Headphone Mic can't record after S3 -- 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/1835001 Title: System does not auto detect disconnection of external monitor Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: In Progress Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: In Progress Status in linux-oem source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux source package in Disco: In Progress Status in linux-oem source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: Won't Fix Status in linux-oem-osp1 source package in Eoan: Won't Fix Bug description: [Impact] System does not auto detect disconnection of external monitor Steps to reproduce: 1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS 2. open "system settings > display settings" 3. connect laptop to an external HDMI monitor via HDMI port & cable 4. unplug the HDMI cable 5. check if "display settings" automatically detects the removal of the external monitor Expected result: display settings should automatically detect the removal of external monitor when unplugging the HDMI cable Actual result: System does not automatically detect the removal of the external monitor when HDMI cable is removed. Sound setting also list HDMI audio in output tab after removal external monitor. Failure rate: 2/10 to 1/10 [Fix] two commits from upstream drm-intel-next-queued branch [Test case] see "steps to reproduce" [Regression potential] still possible, but for the distro only Eoan will get it. OEM kernels will get tested on systems that get it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835001] Re: System does not auto detect disconnection of external monitor
Giraffe, Could you run this command to see if it helps sudo powertop --auto-tune ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1835001 Title: System does not auto detect disconnection of external monitor Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: In Progress Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: In Progress Status in linux-oem source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux source package in Disco: In Progress Status in linux-oem source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: Won't Fix Status in linux-oem-osp1 source package in Eoan: Won't Fix Bug description: [Impact] System does not auto detect disconnection of external monitor Steps to reproduce: 1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS 2. open "system settings > display settings" 3. connect laptop to an external HDMI monitor via HDMI port & cable 4. unplug the HDMI cable 5. check if "display settings" automatically detects the removal of the external monitor Expected result: display settings should automatically detect the removal of external monitor when unplugging the HDMI cable Actual result: System does not automatically detect the removal of the external monitor when HDMI cable is removed. Sound setting also list HDMI audio in output tab after removal external monitor. Failure rate: 2/10 to 1/10 [Fix] two commits from upstream drm-intel-next-queued branch [Test case] see "steps to reproduce" [Regression potential] still possible, but for the distro only Eoan will get it. OEM kernels will get tested on systems that get it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839006] Re: No sound is playing from this laptop
The client_3.conf should work, put this file to /etc/pulse/client.conf reboot check if there is /tmp/a.txt if there isn't, please run 'ps -aux | grep pulseaudio" to check if pulseaudio is running. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812620] Re: msg_zerocopy in net from ubuntu_kernel_selftests failed
Saw this on 5.0 D-AWS (at lease on c4.large, m4.large) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812620 Title: msg_zerocopy in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: New Status in linux source package in Disco: New Bug description: This test will return 1 $ sudo ./msg_zerocopy.sh ipv4 tcp -t 1 ./msg_zerocopy: setaffinity 2 ./msg_zerocopy: setaffinity 3 $ echo $? 1 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:50:33 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/1812620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819116] Re: sync_file_range02 in ubuntu_ltp_syscalls fails
Failed on D-AWS (t3.medium), this failure was not spotted across all instances Test failed with vfat.: tst_mkfs.c:90: INFO: Formatting /dev/loop3 with vfat opts='' extra opts='' sync_file_range02.c:111: INFO: Pre-filling file sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:74: FAIL: Sync inside of write: Synced 27854336, expected 16777216 sync_file_range02.c:71: PASS: Sync overlaps with write -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1819116 Title: sync_file_range02 in ubuntu_ltp_syscalls fails Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux-gke source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-aws source package in Cosmic: New Status in linux-azure source package in Cosmic: New Status in linux source package in Disco: Incomplete Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: New Status in linux source package in Eoan: Incomplete Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Status in linux-gke source package in Eoan: New Bug description: syslog output attached as attachment. <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_supported_fs_types.c:72: INFO: Kernel supports ext2 tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext3 tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext4 tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist tst_supported_fs_types.c:72: INFO: Kernel supports xfs tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports btrfs tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports vfat tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported tst_supported_fs_types.c:72: INFO: Kernel supports ntfs tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist tst_test.c:1157: INFO: Testing on ext2 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ext3 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ext4 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on vfat tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ntfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts='' The partition start sector was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. The number of sectors per track was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. The number of heads was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set. Windows will not be able to boot from this device. safe_macros.c:739: INFO: Trying FUSE... tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:56: FAIL: Synced 0, expected 33554432 Summary:
[Kernel-packages] [Bug 1837688] Re: Ubuntu won't boot on Dell Inspiron 7375
Bisected and reported to upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837688 Title: Ubuntu won't boot on Dell Inspiron 7375 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu is unable to boot from the installation USB on a Dell Inspiron 7375, with a Ryzen CPU. This affects Ubuntu 19.10 (latest daily), 19.04 and 18.04.2 (videos of each unsuccessful boot will be attached). I was able to boot using a workaround, by adding to the kernel line: amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 You can see it here: https://askubuntu.com/questions/1036357/ubuntu-18-04-wont-boot-on- dell-inspiron-7375 I used this workaround to run the apport-bug tool. The problem should be in an ubuntu specific vendor patch or configuration since I was able to boot successfully in: * CentOS 7 (kernel 3.10) * OpenSUSE Leap 15.1 (kernel 4.12.14) * OpenSUSE tumbleweed (kernel 5.1.16) * Fedora 30 (kernel 5.0.9) * Manjaro (kernel 4.19) * SystemRescueCd (kernel 4.19.34) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.0.0-20-generic 5.0.0-20.21 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2186 F pulseaudio /dev/snd/controlC0: ubuntu 2186 F pulseaudio CasperVersion: 1.411 CurrentDesktop: ubuntu:GNOME Date: Tue Jul 23 21:14:36 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) MachineType: Dell Inc. Inspiron 7375 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 --- RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.180 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0GTNWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.5.0 dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd07/09/2018:svnDellInc.:pnInspiron7375:pvr1.5.0:rvnDellInc.:rn0GTNWX:rvrA00:cvnDellInc.:ct10:cvr1.5.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 7375 dmi.product.sku: 0884 dmi.product.version: 1.5.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836152] Re: Intel ethernet I219 has slow RX speed
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1836152 Title: Intel ethernet I219 has slow RX speed Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] RX speed on Intel ethernet I219 v6 is extremely slow due to multiple RX CRC errors. [Fix] Disable e1000e K1 feature to make I219 and PCH operate at higher speed to avoid the issue. [Test] Before applying the patch, the RX is slower than 150Kbps. After applying the fix the RX speed can achive gigabits. [Regression Potential] Low. This only applies to recent I219 generations. I've also test several other systems with e1000e and I don't see any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839006] Re: No sound is playing from this laptop
Again, I have followed the instructions here. There is no a.txt file in the tmp folder. It seems like pulseaudio is running. ** Attachment added: "pulse_fun" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+attachment/5281539/+files/pulse_fun -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839236] Re: failed to configure linux-firmware in minimal cloud image based vm in cloud-init: Can't open /etc/initramfs-tools/initramfs.conf
>From the full log, the original minimal cloud image doesn't have initramfs-* packages installed in the first place. So when it's configuring linux-firmware, all those tools are in unpacked state except initramfs-tools-bin has been full setup then. So this happened in some intermediate state that initramfs-tools is not fully configured yet, and maybe some other dependencies, checks should be added in either initramfs-tools or linux-firmeware. -- 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/1839236 Title: failed to configure linux-firmware in minimal cloud image based vm in cloud-init: Can't open /etc/initramfs-tools/initramfs.conf Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Disco: New Bug description: When running a patched `autopkgtest-buildvm-ubuntu-cloud` that enables constructing autopkgtest vm with minial cloud images [1], it fails to install linux-firmware at postinst stage because /etc/initramfs-tools/initramfs.conf from package initramfs-tools-core may not have been installed: ``` cloud-init[528]: Setting up linux-firmware (1.173.9) ... cloud-init[528]: update-initramfs: Generating /boot/initrd.img-4.15.0-1039-kvm cloud-init[528]: /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf cloud-init[528]: update-initramfs: failed for /boot/initrd.img-4.15.0-1039-kvm with 2. cloud-init[528]: dpkg: error processing package linux-firmware (--configure): cloud-init[528]: installed linux-firmware package post-installation script subprocess returned error exit status 2 ``` See https://gitlab.com/hustle-ci/autopkgtest-ubuntu/-/jobs/265419649 for full log. [1]: https://cloud-images.ubuntu.com/minimal/daily/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1839236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839278] Re: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Packaging - phase-changed: Wednesday, 07. August 2019 20:15 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 08. August 2019 05:35 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 + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1839278 Title: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in 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 -- kernel-stable-master-bug: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 05:35 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
OK, so I booted up with the mouse in USB3 port. All good. Put mouse in USB2 port. Problem appears (as expected). output from dmesg attached ** Attachment added: "dm.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+attachment/5281540/+files/dm.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Confirmed Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839276] Re: bionic/linux-kvm: 4.15.0-1042.42 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-kvm meta: linux-meta-kvm - phase: Packaging - phase-changed: Wednesday, 07. August 2019 16:00 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 08. August 2019 05:51 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839276 Title: bionic/linux-kvm: 4.15.0-1042.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 05:51 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839258] Re: bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839257 (pi-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Packaging - phase-changed: Wednesday, 07. August 2019 16:10 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 08. August 2019 05:50 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building trackers: bionic/linux-raspi2/pi-kernel: bug 1839257 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1839258 Title: bionic/linux-raspi2: 4.15.0-1043.46 -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-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839257 (pi-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 05:50 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building trackers: bionic/linux-raspi2/pi-kernel: bug 1839257 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839258] Re: bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839257 (pi-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 05:50 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building trackers: bionic/linux-raspi2/pi-kernel: bug 1839257 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1839258 Title: bionic/linux-raspi2: 4.15.0-1043.46 -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-meta 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839257 (pi-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 05:50 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building trackers: bionic/linux-raspi2/pi-kernel: bug 1839257 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839281] Re: bionic/linux-fips: 4.15.0-1015.18 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Packaging - phase-changed: Wednesday, 07. August 2019 14:30 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 08. August 2019 06:06 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 + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839281 Title: bionic/linux-fips: 4.15.0-1015.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Holding before Promote to Proposed phase-changed: Thursday, 08. August 2019 06:06 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839006] Re: No sound is playing from this laptop
your output is different from mine: gdm 1194 0.1 0.0 1153544 11656 ? Ssl 14:13 0:00 /usr/bin/pulseaudio --daemonize=no hwang42205 0.5 0.0 1172556 12604 ? Shttps://bugs.launchpad.net/bugs/1839006 Title: No sound is playing from this laptop Status in linux package in Ubuntu: Confirmed Bug description: I recently installed Ubuntu 19.04 on this protab laptop. In the settings menu the sound output shows a headphone and a multichannel output option. There is no sound coming out of either system, despite there being sound detection demonstrated in the sound bars in the output menu moving with the playback audio. I have tried force restarting/reinstalling Alsa mixer and pulse audio and all the obvious things such as checking sound level settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 02:09:12 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-02-22 (164 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1685 F pulseaudio /dev/snd/controlC0: adrian 1685 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-02-22 (165 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Visage Telecom Pty Ltd PTBNWXM14GRY Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 RelatedPackageVersions: linux-restricted-modules-5.0.0-23-generic N/A linux-backports-modules-5.0.0-23-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-23-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-08-04 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: PROTABx.WT314D.NANNGEN0 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Insyde dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrPROTABx.WT314D.NANNGEN0:bd11/04/2016:svnVisageTelecomPtyLtd:pnPTBNWXM14GRY:pvrType1-TBDbyOEM:rvnInsyde:rnType2-BoardProductName:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1 - Family dmi.product.name: PTBNWXM14GRY dmi.product.sku: Type1 - SKU0 dmi.product.version: Type1 - TBD by OEM dmi.sys.vendor: Visage Telecom Pty Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839006/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839276] Re: bionic/linux-kvm: 4.15.0-1042.42 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-kvm meta: linux-meta-kvm - phase: Holding before Promote to Proposed - phase-changed: Thursday, 08. August 2019 05:51 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 08. August 2019 06:20 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839276 Title: bionic/linux-kvm: 4.15.0-1042.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Promote to Proposed phase-changed: Thursday, 08. August 2019 06:20 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837688] Re: Ubuntu won't boot on Dell Inspiron 7375
Great! Hit me if you need some testing when the changes arrive ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837688 Title: Ubuntu won't boot on Dell Inspiron 7375 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu is unable to boot from the installation USB on a Dell Inspiron 7375, with a Ryzen CPU. This affects Ubuntu 19.10 (latest daily), 19.04 and 18.04.2 (videos of each unsuccessful boot will be attached). I was able to boot using a workaround, by adding to the kernel line: amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 You can see it here: https://askubuntu.com/questions/1036357/ubuntu-18-04-wont-boot-on- dell-inspiron-7375 I used this workaround to run the apport-bug tool. The problem should be in an ubuntu specific vendor patch or configuration since I was able to boot successfully in: * CentOS 7 (kernel 3.10) * OpenSUSE Leap 15.1 (kernel 4.12.14) * OpenSUSE tumbleweed (kernel 5.1.16) * Fedora 30 (kernel 5.0.9) * Manjaro (kernel 4.19) * SystemRescueCd (kernel 4.19.34) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.0.0-20-generic 5.0.0-20.21 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2186 F pulseaudio /dev/snd/controlC0: ubuntu 2186 F pulseaudio CasperVersion: 1.411 CurrentDesktop: ubuntu:GNOME Date: Tue Jul 23 21:14:36 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) MachineType: Dell Inc. Inspiron 7375 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 --- RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.180 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0GTNWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.5.0 dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd07/09/2018:svnDellInc.:pnInspiron7375:pvr1.5.0:rvnDellInc.:rn0GTNWX:rvrA00:cvnDellInc.:ct10:cvr1.5.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 7375 dmi.product.sku: 0884 dmi.product.version: 1.5.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1426216] Re: pci driver messages - BAR 13: no space for
Removing currently assigned team, as this issue is now being seen with Intel systems. ** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1426216 Title: pci driver messages - BAR 13: no space for Status in linux package in Ubuntu: Confirmed Bug description: ---Problem Description--- pci driver messages - BAR 13: no space for ---uname output--- 3.18.0-12-generic Machine Type = POWER8 ---Steps to Reproduce--- Install Ubuntu 15.04 daily build running bare-metal After the installation following messages are seen in dmesg. Not sure if these indicate a problem. Can some one look at these and confirm if this is problem or can be ignored ? Messages from dmesg log [0.714476] pci_bus 0001:00: max bus depth: 3 pci_try_num: 4 [0.714519] pci 0001:04:00.0: reg 0x16c: [mem 0x-0x 64bit] [0.714541] pci 0001:04:00.0: reg 0x174: [mem 0x-0x 64bit] [0.714577] pci 0001:00:00.0: BAR 15: assigned [mem 0x3b101000-0x3b103fff 64bit pref] [0.714579] pci 0001:00:00.0: BAR 14: assigned [mem 0x3fe08000-0x3fe081ff] [0.714581] pci 0001:00:00.0: BAR 13: no space for [io size 0x3000] [0.714583] pci 0001:00:00.0: BAR 13: failed to assign [io size 0x3000] [0.714586] pci 0001:01:00.0: BAR 15: assigned [mem 0x3b101000-0x3b103fff 64bit pref] [0.714588] pci 0001:01:00.0: BAR 14: assigned [mem 0x3fe08000-0x3fe0817f] [0.714590] pci 0001:01:00.0: BAR 0: assigned [mem 0x3fe08180-0x3fe08183] [0.714595] pci 0001:01:00.0: BAR 13: no space for [io size 0x3000] [0.714597] pci 0001:01:00.0: BAR 13: failed to assign [io size 0x3000] [0.714600] pci 0001:02:01.0: BAR 15: assigned [mem 0x3b101000-0x3b101fff 64bit pref] [0.714602] pci 0001:02:08.0: BAR 15: assigned [mem 0x3b102000-0x3b102fff 64bit pref] [0.714604] pci 0001:02:09.0: BAR 15: assigned [mem 0x3b103000-0x3b103fff 64bit pref] [0.714606] pci 0001:02:01.0: BAR 14: assigned [mem 0x3fe08000-0x3fe0807f] [0.714608] pci 0001:02:08.0: BAR 14: assigned [mem 0x3fe08080-0x3fe080ff] [0.714609] pci 0001:02:09.0: BAR 14: assigned [mem 0x3fe08100-0x3fe0817f] [0.714611] pci 0001:02:01.0: BAR 13: no space for [io size 0x1000] [0.714613] pci 0001:02:01.0: BAR 13: failed to assign [io size 0x1000] [0.714614] pci 0001:02:08.0: BAR 13: no space for [io size 0x1000] [0.714616] pci 0001:02:08.0: BAR 13: failed to assign [io size 0x1000] [0.714618] pci 0001:02:09.0: BAR 13: no space for [io size 0x1000] [0.714619] pci 0001:02:09.0: BAR 13: failed to assign [io size 0x1000] [0.714622] pci 0001:03:00.0: BAR 6: assigned [mem 0x3fe08000-0x3fe08003 pref] [0.714624] pci 0001:03:00.1: BAR 6: assigned [mem 0x3fe08004-0x3fe08007 pref] [0.714627] pci 0001:03:00.0: BAR 2: assigned [mem 0x3fe08008-0x3fe080083fff 64bit] [0.714641] pci 0001:03:00.1: BAR 2: assigned [mem 0x3fe080084000-0x3fe080087fff 64bit] [0.714656] pci 0001:03:00.0: BAR 0: assigned [mem 0x3fe080088000-0x3fe080088fff 64bit] [0.714670] pci 0001:03:00.1: BAR 0: assigned [mem 0x3fe080089000-0x3fe080089fff 64bit] [0.714685] pci 0001:03:00.0: BAR 4: no space for [io size 0x0100] [0.714686] pci 0001:03:00.0: BAR 4: failed to assign [io size 0x0100] [0.714688] pci 0001:03:00.1: BAR 4: no space for [io size 0x0100] [0.714690] pci 0001:03:00.1: BAR 4: failed to assign [io size 0x0100] [0.714691] pci 0001:02:01.0: PCI bridge to [bus 03] # lspci :00:00.0 PCI bridge: IBM Device 03dc 0001:00:00.0 PCI bridge: IBM Device 03dc 0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:03:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) 0001:03:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) 0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01) 0002:00:00.0 PCI bridge: IBM Device 03dc 0003:00:00.0 PCI bridge: IBM Device 03dc 0003:01:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0003:02:01.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0003:02:08.0 PCI bridge: PLX Technology, Inc. Device 8