[Kernel-packages] [Bug 1802753] Re: linux-kvm: 4.18.0-1005.5 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release - security-signoff: Waiting for signoff -- 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/1802753 Title: linux-kvm: 4.18.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802787] Re: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802750 phase: Promoted to proposed phase-changed: Tuesday, 27. November 2018 17:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress - security-signoff: Waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802787 Title: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802750 phase: Promoted to proposed phase-changed: Tuesday, 27. November 2018 17:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-beta is neither "Fix Released" nor "Invalid" + promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805982] [NEW] Please consider making the zed daemon activated on demand
Public bug reported: Hi, currently if one wants most common FS tools to be able to mount them to e.g. mount them "just in case" or when considering a more capable base image or install CD then there is the problem that installing "zfsutils-linux" pulls in "zfs-zed" as a recommends. Having it on disk would be ok, but IMHO there is no reason this daemon needs to run until the first ZFS element is created. ● zfs-zed.service - ZFS Event Daemon (zed) Loaded: loaded (/lib/systemd/system/zfs-zed.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-11-29 16:09:04 UTC; 3min 26s ago Docs: man:zed(8) Main PID: 2968 (zed) Tasks: 2 (limit: 546) Memory: 436.0K CGroup: /system.slice/zfs-zed.service └─2968 /usr/sbin/zed -F Nov 29 16:09:04 disco-zfstest systemd[1]: Started ZFS Event Daemon (zed). Nov 29 16:09:04 disco-zfstest zed[2968]: ZFS Event Daemon 0.7.9-3ubuntu6 (PID 2968) Nov 29 16:09:04 disco-zfstest zed[2968]: Processing events since eid=0 People in general would want the number of default running services low. Further than the general "not too much default daemons" there are a few issues like [1] which makes this worse if one is affected. There is no related upstream feature yet that I'd know of, nor did I find a trivial way to e.g. match a systemd unit Condition (which also is only evaluated only once, so it would miss later zfs creation) or a socket (what would it wait for). I wanted to ask here if you'd have more/better ideas or if we should directly file this upstream and then link that bug here? [1]: https://github.com/zfsonlinux/zfs/issues/7995 ** Affects: zfs-linux (Ubuntu) Importance: Wishlist Status: New ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1805982 Title: Please consider making the zed daemon activated on demand Status in zfs-linux package in Ubuntu: New Bug description: Hi, currently if one wants most common FS tools to be able to mount them to e.g. mount them "just in case" or when considering a more capable base image or install CD then there is the problem that installing "zfsutils-linux" pulls in "zfs-zed" as a recommends. Having it on disk would be ok, but IMHO there is no reason this daemon needs to run until the first ZFS element is created. ● zfs-zed.service - ZFS Event Daemon (zed) Loaded: loaded (/lib/systemd/system/zfs-zed.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-11-29 16:09:04 UTC; 3min 26s ago Docs: man:zed(8) Main PID: 2968 (zed) Tasks: 2 (limit: 546) Memory: 436.0K CGroup: /system.slice/zfs-zed.service └─2968 /usr/sbin/zed -F Nov 29 16:09:04 disco-zfstest systemd[1]: Started ZFS Event Daemon (zed). Nov 29 16:09:04 disco-zfstest zed[2968]: ZFS Event Daemon 0.7.9-3ubuntu6 (PID 2968) Nov 29 16:09:04 disco-zfstest zed[2968]: Processing events since eid=0 People in general would want the number of default running services low. Further than the general "not too much default daemons" there are a few issues like [1] which makes this worse if one is affected. There is no related upstream feature yet that I'd know of, nor did I find a trivial way to e.g. match a systemd unit Condition (which also is only evaluated only once, so it would miss later zfs creation) or a socket (what would it wait for). I wanted to ask here if you'd have more/better ideas or if we should directly file this upstream and then link that bug here? [1]: https://github.com/zfsonlinux/zfs/issues/7995 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1805982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802750] Re: linux-gcp: 4.18.0-1004.5 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release - security-signoff: Waiting for signoff -- 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/1802750 Title: linux-gcp: 4.18.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802787] Re: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -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/1802787 Title: linux-gcp-edge: 4.18.0-1004.5~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802750 phase: Promoted to proposed phase-changed: Tuesday, 27. November 2018 17:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805244] Re: linux-azure: 4.18.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug is for tracking the 4.18.0-1006.6 upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed phase-changed: Tuesday, 27. November 2018 15:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing in progress + automated-testing: Testing FAILED regression-testing: Testing in progress - security-signoff: Waiting for signoff stakeholder-signoff: Waiting for signoff -- 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/1805244 Title: linux-azure: 4.18.0-1006.6 -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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.18.0-1006.6 upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed phase-changed: Tuesday, 27. November 2018 15:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805465] Re: linux: 4.19.0-7.8 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- phase: Uploaded phase-changed: Thursday, 29. November 2018 22:03 UTC reason: - promote-to-proposed: 'FAILED: Packages no longer available' + promote-to-proposed: Packages copied but not yet published to -proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805465 Title: linux: 4.19.0-7.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- phase: Uploaded phase-changed: Thursday, 29. November 2018 22:03 UTC reason: promote-to-proposed: Packages copied but not yet published to -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805465] Re: linux: 4.19.0-7.8 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed 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/1805465 Title: linux: 4.19.0-7.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- phase: Uploaded phase-changed: Thursday, 29. November 2018 22:03 UTC reason: promote-to-proposed: Packages copied but not yet published to -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802743] Re: linux: 4.18.0-12.13 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1802744 (linux-hwe-edge), bug 1802746 (linux-aws-edge), bug 1802747 (linux-azure-edge), bug 1805606 (linux-aws-edge) derivatives: bug 1802748 (linux-raspi2), bug 1802749 (linux-aws), bug 1802750 (linux-gcp), bug 1802752 (linux-azure), bug 1802753 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Uploaded phase-changed: Wednesday, 28. November 2018 10:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED - security-signoff: Waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802743 Title: linux: 4.18.0-12.13 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1802744 (linux-hwe-edge), bug 1802746 (linux-aws-edge), bug 1802747 (linux-azure-edge), bug 1805606 (linux-aws-edge) derivatives: bug 1802748 (linux-raspi2), bug 1802749 (linux-aws), bug 1802750 (linux-gcp), bug 1802752 (linux-azure), bug 1802753 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Uploaded phase-changed: Wednesday, 28. November 2018 10:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802753] Re: linux-kvm: 4.18.0-1005.5 -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/1802753 Title: linux-kvm: 4.18.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805778] Re: ubuntu_vfat_stress failed again with P8/P9 Bionic
BTW, the vfat stress failure in Bionic 4.18 has gone with retest as
well. (node pepe)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805778
Title:
ubuntu_vfat_stress failed again with P8/P9 Bionic
Status in ubuntu-kernel-tests:
Fix Committed
Status in linux package in Ubuntu:
Triaged
Bug description:
This issue just like bug 1801907, but this time it's passed with P8
"modoc", failed with P8 "entei" and P9 "baltar"
I haven't run them directly, this is the result when testing with the
whole test suite.
06:21:04 INFO | START ubuntu_vfat_stress.vfat-stress
ubuntu_vfat_stress.vfat-stress timestamp=1543472464timeout=18000
localtime=Nov 29 06:21:04
06:21:04 DEBUG| Persistent state client._record_indent now set to 2
06:21:04 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_vfat_stress.vfat-stress', 'ubuntu_vfat_stress.vfat-stress')
06:21:04 DEBUG| Waiting for pid 56149 for 18000 seconds
06:21:04 DEBUG| Running 'LOG=/tmp/vfat-falure.log
STRESS_NG=/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng
DURATION=10s bash -c
/home/ubuntu/autotest/client/tests/ubuntu_vfat_stress/ubuntu_vfat_stress.sh
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src 2>&1'
06:21:04 DEBUG| [stdout] Testing: --verify --times --metrics-brief --syslog
--keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd
--lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order
stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2
--hdd-bytes 4M --fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
06:21:04 DEBUG| [stdout] Mounting tmpfs /mnt/vfat-test-56154
06:21:05 DEBUG| [stdout] Created loop image
/mnt/vfat-test-56154/vfat-loop-data
06:21:05 DEBUG| [stdout] mkfs.fat 4.1 (2017-01-24)
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout] VFAT options: allow_utime=20
06:21:06 DEBUG| [stdout] Stress test:
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng
--verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
06:21:06 DEBUG| [stdout] VFAT_IMAGE path: /mnt/vfat-test-56154
06:21:06 DEBUG| [stdout] Mount point: /mnt/vfat-test-56154
06:21:06 DEBUG| [stdout] Date: Thu Nov 29 06:21:06 UTC 2018
06:21:06 DEBUG| [stdout] Host: baltar
06:21:06 DEBUG| [stdout] Kernel:4.15.0-42-generic #45-Ubuntu SMP Thu
Nov 15 19:29:37 UTC 2018
06:21:06 DEBUG| [stdout] Machine: baltar ppc64le ppc64le
06:21:06 DEBUG| [stdout] CPUs online: 40
06:21:06 DEBUG| [stdout] CPUs total:160
06:21:06 DEBUG| [stdout] Page size: 65536
06:21:06 DEBUG| [stdout] Pages avail: 1935143
06:21:06 DEBUG| [stdout] Pages total: 2089666
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout] Started, PID 56225
06:23:13 DEBUG| [stdout] Timed out waiting for stress-ng to finish
06:23:13 DEBUG| [stdout] Forcefully killing, PID 56225 (after 121 seconds)
06:23:23 DEBUG| [stdout] Found kernel warning and/or call trace:
06:23:23 DEBUG| [stdout]
06:23:23 DEBUG| [stdout] [ 4940.791800] Testing: --verify --times
--metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
06:23:23 DEBUG| [stdout] [ 4941.855398] Created loop image
/mnt/vfat-test-56154/vfat-loop-data
06:23:23 DEBUG| [stdout] [ 4942.232934] ubuntu_vfat_str (56154): drop_caches:
1
06:23:23 DEBUG| [stdout] [ 4942.593708] ubuntu_vfat_str (56154): drop_caches:
2
06:23:23 DEBUG| [stdout] [ 4942.597717] ubuntu_vfat_str (56154): drop_caches:
3
06:23:23 DEBUG| [stdout] [ 4943.125332] VFAT options: allow_utime=20
06:23:23 DEBUG| [stdout] [ 4943.125392] Stress test:
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng
--verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2
--fstat 2 --dentries 100 --lease 2 --open 2
[Kernel-packages] [Bug 1802750] Re: linux-gcp: 4.18.0-1004.5 -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/1802750 Title: linux-gcp: 4.18.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" - (New) + promote-to-updates: snap-release-to-beta is neither "Fix Released" nor "Invalid" + (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-beta is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802743] Re: linux: 4.18.0-12.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 in Ubuntu. https://bugs.launchpad.net/bugs/1802743 Title: linux: 4.18.0-12.13 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1802744 (linux-hwe-edge), bug 1802746 (linux-aws-edge), bug 1802747 (linux-azure-edge), bug 1805606 (linux-aws-edge) derivatives: bug 1802748 (linux-raspi2), bug 1802749 (linux-aws), bug 1802750 (linux-gcp), bug 1802752 (linux-azure), bug 1802753 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Uploaded phase-changed: Wednesday, 28. November 2018 10:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805244] Re: linux-azure: 4.18.0-1006.6 -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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1805244 Title: linux-azure: 4.18.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.18.0-1006.6 upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed phase-changed: Tuesday, 27. November 2018 15:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805778] Re: ubuntu_vfat_stress failed again with P8/P9 Bionic
Retested on both entei and baltar,
passed on entei but still failing on balter (with the whole test suite)
Log for balter:
https://pastebin.ubuntu.com/p/82NXmVYS93/
I will give it another shot on balter.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805778
Title:
ubuntu_vfat_stress failed again with P8/P9 Bionic
Status in ubuntu-kernel-tests:
Fix Committed
Status in linux package in Ubuntu:
Triaged
Bug description:
This issue just like bug 1801907, but this time it's passed with P8
"modoc", failed with P8 "entei" and P9 "baltar"
I haven't run them directly, this is the result when testing with the
whole test suite.
06:21:04 INFO | START ubuntu_vfat_stress.vfat-stress
ubuntu_vfat_stress.vfat-stress timestamp=1543472464timeout=18000
localtime=Nov 29 06:21:04
06:21:04 DEBUG| Persistent state client._record_indent now set to 2
06:21:04 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_vfat_stress.vfat-stress', 'ubuntu_vfat_stress.vfat-stress')
06:21:04 DEBUG| Waiting for pid 56149 for 18000 seconds
06:21:04 DEBUG| Running 'LOG=/tmp/vfat-falure.log
STRESS_NG=/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng
DURATION=10s bash -c
/home/ubuntu/autotest/client/tests/ubuntu_vfat_stress/ubuntu_vfat_stress.sh
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src 2>&1'
06:21:04 DEBUG| [stdout] Testing: --verify --times --metrics-brief --syslog
--keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd
--lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order
stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2
--hdd-bytes 4M --fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
06:21:04 DEBUG| [stdout] Mounting tmpfs /mnt/vfat-test-56154
06:21:05 DEBUG| [stdout] Created loop image
/mnt/vfat-test-56154/vfat-loop-data
06:21:05 DEBUG| [stdout] mkfs.fat 4.1 (2017-01-24)
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout] VFAT options: allow_utime=20
06:21:06 DEBUG| [stdout] Stress test:
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng
--verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
06:21:06 DEBUG| [stdout] VFAT_IMAGE path: /mnt/vfat-test-56154
06:21:06 DEBUG| [stdout] Mount point: /mnt/vfat-test-56154
06:21:06 DEBUG| [stdout] Date: Thu Nov 29 06:21:06 UTC 2018
06:21:06 DEBUG| [stdout] Host: baltar
06:21:06 DEBUG| [stdout] Kernel:4.15.0-42-generic #45-Ubuntu SMP Thu
Nov 15 19:29:37 UTC 2018
06:21:06 DEBUG| [stdout] Machine: baltar ppc64le ppc64le
06:21:06 DEBUG| [stdout] CPUs online: 40
06:21:06 DEBUG| [stdout] CPUs total:160
06:21:06 DEBUG| [stdout] Page size: 65536
06:21:06 DEBUG| [stdout] Pages avail: 1935143
06:21:06 DEBUG| [stdout] Pages total: 2089666
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout] Started, PID 56225
06:23:13 DEBUG| [stdout] Timed out waiting for stress-ng to finish
06:23:13 DEBUG| [stdout] Forcefully killing, PID 56225 (after 121 seconds)
06:23:23 DEBUG| [stdout] Found kernel warning and/or call trace:
06:23:23 DEBUG| [stdout]
06:23:23 DEBUG| [stdout] [ 4940.791800] Testing: --verify --times
--metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
06:23:23 DEBUG| [stdout] [ 4941.855398] Created loop image
/mnt/vfat-test-56154/vfat-loop-data
06:23:23 DEBUG| [stdout] [ 4942.232934] ubuntu_vfat_str (56154): drop_caches:
1
06:23:23 DEBUG| [stdout] [ 4942.593708] ubuntu_vfat_str (56154): drop_caches:
2
06:23:23 DEBUG| [stdout] [ 4942.597717] ubuntu_vfat_str (56154): drop_caches:
3
06:23:23 DEBUG| [stdout] [ 4943.125332] VFAT options: allow_utime=20
06:23:23 DEBUG| [stdout] [ 4943.125392] Stress test:
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng
--verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2
[Kernel-packages] [Bug 1451387] Re: [Fujitsu LIFEBOOK LH532] UEFI firmware becomes locked after installing Ubuntu in UEFI mode
Even I am facing something similar. I have Fujitsu laptop (Model: LH532). It had Windows OS. After installing Ubuntu 18.04.1 from USB drive, on restart, laptop just shows "ubuntu" options in boot menu (not showing original BIOS, some new screen). Original BIOS screen does not appear. On selecting "ubuntu" and hitting enter key, nothing happens, so I am stuck with no options to start laptop. Below are the steps that I took. 1. Created bootable USB stick with https://rufus.akeo.ie/ (as recommended on Ubuntu site). 2. Rebooted the laptop. 3. Entered BIOS to change boot order so that USB is checked before HDD. Saved BIOS settings and restarted the laptop. 4. On re-start, options to try or install ubuntu were shown. Selected "try ..." option. 5. System started with Ubuntu (from USB). 6. Selected "Install Ubuntu" application icon when system started. 7. Went through normal question shown in ubuntu installation wizard. 8 Selected option to customize partitions, as I wanted to remove windows and partition it into two - one for / and another for /home. 9. Deleted the partition on which Windows was installed (C:\) and divided that into two partitions. One to install root (/) filesystem and another to install /home. 10. Ubnutu installation started, but after some time got an error "Installer crashed" as Grub could not be installed. 11. Tried to close the installation window, but nothing happened. 12. Restarted the system and again booted from USB. 13. This time I selected "Install ubuntu" option without booting ubuntu from USB in trial mode. 14. Answered installation questions. 15. This selected default option (showing reinstall Ubuntu 18.04.1) -- It was already showing that 18.04.1 is installed in the partition that I selected in earlier install (that failed). 16. Installation completed without any error. System asked to restart to start using Ubnutu installation. 17. Restarted the system. 18. On restart, I am shown a new screen (not the original BIOS or Boot options). Refer video https://www.youtube.com/watch?v=4ZkhsKc29Zg. This new screen (BIOS kind of screen) have two tabs - "Boot Menu" and "Application Menu". Under Boot Menu tab, only option available is "ubuntu" which is by default selected. On hitting enter, it tries to do something, but within second it comes back to same screen. Problem: I am stuck with this new BIOS kind of screen with "ubuntu" as only option and that option does not boot system. I have no option to start the system or enter the original BIOS (which is not even visible anymore). Its kind of very strange that machine's BIOS got updated on installing Ubnutu. ** Changed in: linux (Ubuntu) Status: Expired => 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/1451387 Title: [Fujitsu LIFEBOOK LH532] UEFI firmware becomes locked after installing Ubuntu in UEFI mode Status in linux package in Ubuntu: Confirmed Bug description: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/comments/74 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 4 16:57:39 2015 InstallationDate: Installed on 2010-01-01 (1949 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rut1480 F pulseaudio rut7079 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=d4bb392e-90ed-41a3-9d30-fa457fefb25b InstallationDate: Installed on 2010-01-01 (1949 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: FUJITSU LIFEBOOK LH532 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=e8258103-326b-4708-b64f-6306d0eb0a01 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" - (Confirmed) + promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" + (New) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (New) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767568] Re: Console DPMS Nonfunctional in Ubuntu Server 18.04
Actually, my apologies, I am not (and I can't figure out how to edit my last comment, if it is possible) ... I was in 18.04 Workstation with GUI disabled when I was adding consoleblank to GRUB_CMDLINE_LINUX_DEFAULT - that wasn't working at all in Server though, so I tried adding it to GRUB_CMDLINE_LINUX and I am AMAZED to see that the display is actually OFF for the first time in 3-4 weeks I've been fighting with all this. No issues here, please disregard my previous comment! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Confirmed Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 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 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
Things are much improved now on cosmic 18.04 ubuntu studio:- /sys/class/power_supply/BAT0/capacity:100 /sys/class/power_supply/hid-34:88:5d:87:92:8c-battery/capacity:85 Linux 4.18.0-11-lowlatency #12-Ubuntu SMP PREEMPT Tue Oct 23 21:12:42 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [The mouse is OK again on 17.10, while the ASUS docking station is still not correct. I will update this bug report with details soon.] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767568] Re: Console DPMS Nonfunctional in Ubuntu Server 18.04
As soon as I hit post on that last comment the display lit up again, so it's "blank" but not "off" - so I AM having the issue, and will stop spamming now, sorry. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Confirmed Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 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 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767568] Re: Console DPMS Nonfunctional in Ubuntu Server 18.04
I'm experiencing this same issue on a Dell 7577 (laptop), it has got a GTX 1060 MaxQ, but I believe the internal display (which is where I am experiencing and trying to resolve this same issue) is running off the Intel HD Graphics 630. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767568 Title: Console DPMS Nonfunctional in Ubuntu Server 18.04 Status in linux package in Ubuntu: Confirmed Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 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 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: X58A-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD5:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD5 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-beta is neither "Fix Released" nor "Invalid" + promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" - (New) + promote-to-updates: snap-release-to-beta is neither "Fix Released" nor "Invalid" + (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-beta is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802750] Re: linux-gcp: 4.18.0-1004.5 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED + promote-to-security: Master bug not ready for release + promote-to-updates: Master bug not ready for release security-signoff: Waiting for signoff -- 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/1802750 Title: linux-gcp: 4.18.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805412] Re: linux-azure: 4.15.0-1034.35 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug is for tracking the 4.15.0-1034.35 upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed phase-changed: Wednesday, 28. November 2018 15:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel stakeholder-signoff: Waiting for signoff -- 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/1805412 Title: linux-azure: 4.15.0-1034.35 -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: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the 4.15.0-1034.35 upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed phase-changed: Wednesday, 28. November 2018 15:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Testing in progress security-signoff: Waiting for signoff snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel stakeholder-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805412/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790753] Re: X1 yoga 3rd generation doesn't go to sleep
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790753 Title: X1 yoga 3rd generation doesn't go to sleep Status in linux package in Ubuntu: Expired Bug description: The laptop doesn't go to sleep. This is probably related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1756105 which seems to be missing logs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: myrti 16389 F pulseaudio CurrentDesktop: KDE Date: Tue Sep 4 20:35:07 2018 HibernationDevice: RESUME=UUID=d105e0f8-28bb-49d5-badc-d2081f559c27 InstallationDate: Installed on 2018-08-30 (5 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20LES49J00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=2b23d1c6-f9bc-4bff-9420-8ab24cce52df ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET35W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LES49J00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET35W(1.21):bd06/08/2018:svnLENOVO:pn20LES49J00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES49J00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LES49J00 dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802560] Re: linux-gcp: 4.15.0-1025.26 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED + promote-to-security: Master bug not ready for release + promote-to-updates: Master bug not ready for release security-signoff: Waiting for signoff -- 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/1802560 Title: linux-gcp: 4.15.0-1025.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" - (Confirmed) + promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" + (New) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (New) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805148] 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 1805148 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805148 Title: [radeon] Lock screen corrupt since upgrade to 18.04.01 Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Bug description: Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this laptop (an HP 6910p) became corrupt. When logged in and using the system, video display is fine, but the lock screen is consistently garbled as in the attached photo. Switching to Wayland made no difference in this behavior. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-01-23 (1038 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic wayland-session Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805148] Re: [radeon] Lock screen corrupt since upgrade to 18.04.01
** Summary changed: - [i945] Lock screen corrupt since upgrade to 18.04.01 + [radeon] Lock screen corrupt since upgrade to 18.04.01 ** Tags added: radeon ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: mesa (Ubuntu) Status: Incomplete => 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/1805148 Title: [radeon] Lock screen corrupt since upgrade to 18.04.01 Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Bug description: Immediately after upgrade to 18.04.01 from 16.04.01, the lock screen of this laptop (an HP 6910p) became corrupt. When logged in and using the system, video display is fine, but the lock screen is consistently garbled as in the attached photo. Switching to Wayland made no difference in this behavior. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-01-23 (1038 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic wayland-session Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-14 (104 days ago) UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805148] Re: [i945] Lock screen corrupt since upgrade to 18.04.01
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c) Subsystem: Hewlett-Packard Company Compaq 6910p 00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c) Kernel driver in use: pcieport Kernel modules: shpchp 00:03.0 Communication controller: Intel Corporation Mobile PM965/GM965 MEI Controller (rev 0c) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: mei_me Kernel modules: mei_me 00:03.2 IDE interface: Intel Corporation Mobile PM965/GM965 PT IDER Controller (rev 0c) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: ata_generic Kernel modules: pata_acpi 00:03.3 Serial controller: Intel Corporation Mobile PM965/GM965 KT Controller (rev 0c) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: serial 00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: uhci_hcd 00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: uhci_hcd 00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: ehci-pci 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: uhci_hcd 00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: uhci_hcd 00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: uhci_hcd 00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: ehci-pci 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) 00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M-E) LPC Interface Controller (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: ata_piix Kernel modules: pata_acpi 00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: ahci Kernel modules: ahci 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV516/M64-S [Mobility Radeon X2300] Subsystem: Hewlett-Packard Company 6910p Kernel driver in use: radeon Kernel modules: radeon 02:06.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b9) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: yenta_cardbus Kernel modules: yenta_socket 02:06.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b9) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: yenta_cardbus Kernel modules: yenta_socket 02:06.3 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 20) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: sdhci-pci Kernel modules: sdhci_pci ** Attachment added: "allpackages.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805148/+attachment/5217565/+files/allpackages.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/1805148 Title: [i945] Lock screen corrupt since upgrade to
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-beta is neither "Fix Released" nor "Invalid" + promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805821] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805821 Title: [amdgpu] GUI performance is poor Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Response is slow, amdgpu driver gives warning in dmesg which is below [0.00] Linux version 4.15.0-36-generic (buildd@lgw01-amd64-031) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 (Ubuntu 4.15.0-36.39-generic 4.15.18) [0.00] random: get_random_u32 called from bsp_init_amd+0x255/0x2a0 with crng_init=0 [0.966765] amd_uncore: AMD NB counters detected [1.165305] pcie_mp2_amd: AMD(R) PCI-E MP2 Communication Driver Version: 1.0 [1.716922] amdkcl: loading out-of-tree module taints kernel. [1.716947] amdkcl: module verification failed: signature and/or required key missing - tainting kernel [1.827886] [drm] amdgpu kernel modesetting enabled. [1.827887] [drm] amdgpu version: 18.30.2.15 [1.833528] fb: switching to amdgpudrmfb from EFI VGA [1.850977] amdgpu :00:01.0: VRAM: 1024M 0x00F4 - 0x00F43FFF (1024M used) [1.850979] amdgpu :00:01.0: GTT: 1024M 0x - 0x3FFF [1.851137] [drm] amdgpu: 1024M of VRAM memory ready [1.851139] [drm] amdgpu: 14975M of GTT memory ready. [1.851291] [drm] amdgpu: dpm initialized [1.853722] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:1! type 0 expected 3 [1.853779] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.853825] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.853872] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [2.064038] fbcon: amdgpudrmfb (fb0) is primary device [2.128334] amdgpu :00:01.0: fb0: amdgpudrmfb frame buffer device [2.145953] [drm] Initialized amdgpu 3.26.0 20150101 for :00:01.0 on minor 0 [5.265031] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [6.277293] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [7.289439] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [8.301565] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [9.313691] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 10.325849] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 11.338007] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 12.350159] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 13.362305] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 14.374463] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 14.394355] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, giving up!!! [ 14.394396] [drm:amdgpu_device_ip_set_powergating_state [amdgpu]] *ERROR* set_powergating_state of IP block failed -110 [ 15.420234] [drm:amdgpu_vce_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test timed out. [ 15.420321] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed testing IB on ring 12 (-110). [ 15.420369] [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring test failed (-110). [ 23.736730] EDAC amd64: Node 0: DRAM ECC disabled. [ 23.736731] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. [ 1566.370793] audit: type=1400 audit(1543500426.678:40): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/usr/share/libdrm/amdgpu.ids" pid=7169 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Takes too for software center to install .deb package where as it happens in a few seconds in terminal via dpkg -i. Problems are after installation of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
[Kernel-packages] [Bug 1805821] Re: GUI performance is poor
It looks the those messages are coming from the kernel. Although you might not encounter the problem till xserver-xorg-video-amdgpu is enabled. ** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Summary changed: - GUI performance is poor + [amdgpu] GUI performance is poor ** Package changed: gnome-shell (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Also affects: linux (Ubuntu) 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/1805821 Title: [amdgpu] GUI performance is poor Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Response is slow, amdgpu driver gives warning in dmesg which is below [0.00] Linux version 4.15.0-36-generic (buildd@lgw01-amd64-031) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 (Ubuntu 4.15.0-36.39-generic 4.15.18) [0.00] random: get_random_u32 called from bsp_init_amd+0x255/0x2a0 with crng_init=0 [0.966765] amd_uncore: AMD NB counters detected [1.165305] pcie_mp2_amd: AMD(R) PCI-E MP2 Communication Driver Version: 1.0 [1.716922] amdkcl: loading out-of-tree module taints kernel. [1.716947] amdkcl: module verification failed: signature and/or required key missing - tainting kernel [1.827886] [drm] amdgpu kernel modesetting enabled. [1.827887] [drm] amdgpu version: 18.30.2.15 [1.833528] fb: switching to amdgpudrmfb from EFI VGA [1.850977] amdgpu :00:01.0: VRAM: 1024M 0x00F4 - 0x00F43FFF (1024M used) [1.850979] amdgpu :00:01.0: GTT: 1024M 0x - 0x3FFF [1.851137] [drm] amdgpu: 1024M of VRAM memory ready [1.851139] [drm] amdgpu: 14975M of GTT memory ready. [1.851291] [drm] amdgpu: dpm initialized [1.853722] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:1! type 0 expected 3 [1.853779] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.853825] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.853872] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [2.064038] fbcon: amdgpudrmfb (fb0) is primary device [2.128334] amdgpu :00:01.0: fb0: amdgpudrmfb frame buffer device [2.145953] [drm] Initialized amdgpu 3.26.0 20150101 for :00:01.0 on minor 0 [5.265031] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [6.277293] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [7.289439] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [8.301565] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [9.313691] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 10.325849] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 11.338007] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 12.350159] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 13.362305] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 14.374463] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, trying to reset the ECPU!!! [ 14.394355] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, giving up!!! [ 14.394396] [drm:amdgpu_device_ip_set_powergating_state [amdgpu]] *ERROR* set_powergating_state of IP block failed -110 [ 15.420234] [drm:amdgpu_vce_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test timed out. [ 15.420321] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed testing IB on ring 12 (-110). [ 15.420369] [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring test failed (-110). [ 23.736730] EDAC amd64: Node 0: DRAM ECC disabled. [ 23.736731] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. [ 1566.370793] audit: type=1400 audit(1543500426.678:40): apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" name="/usr/share/libdrm/amdgpu.ids" pid=7169 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Takes too for software center to install .deb package where as it happens in a few seconds in terminal via dpkg -i. Problems are after installation of amdgpu. ProblemType: Bug
[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
None of my hardware can duplicate this problem. Is the firmware installed? Look at the dmesg output to look for firmware failures. If you do have the correct firmware, there are two options that might help. Try the following: sudo modprobe -rv rtl8192ee sudo modprobe -v rtl8192ee aspm=0 If that does not help, then try sudo modprobe -rv rtl8192ee sudo modprobe -v rtl8192ee msi=0 If any other options show up, then your /etc/modprobe.d/ directory is screwed up. Delete the offending files and try again. If one of those options helps, then create /etc/modprobe.d/50-rtl8192ee.conf (as root), and add the single line containing "options rtl8192ee =0" where is the option you want to set. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Status in linux source package in Utopic: Fix Released Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. This bug is only for the initial support of this WiFi adapter, it's not working 100% well yet, please report new "not working bug" or contact upstream but not keep posting comments, thanks. Status: pull-request for trusty was NAKed because next minor Trusty release will use Utopic LTS kernel, which had already fixed this issue. please wait it or upgrade your whole distro to Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" - (New) + promote-to-updates: snap-release-to-beta is neither "Fix Released" nor "Invalid" + (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-beta is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" - (Confirmed) + promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" + (New) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (New) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805849] Re: apt repository in proposed packages availability issue
** Tags added: kernel-da-key kernel-hyper-v
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805849
Title:
apt repository in proposed packages availability issue
Status in linux package in Ubuntu:
Triaged
Status in linux-azure package in Ubuntu:
Triaged
Bug description:
We have a watcher that does the following:
- verifies if any linux-azure kernels have been published in proposed repo.
- if it detects one, it will install.
The problem we have is that even though we detect a new kernel in proposed,
the installation of it will fail as there are unmet package dependencies not
being available.
This does resolve after several hours, but the way it works is not reliable
that we see the main package being available, but the packages in the repo are
not ready yet.
So it seems to be a timing issue from the time the kernel is released, and
the time the packages actual get on the repo.
Can you please suggest on some methods to better handle the detect &
install for these, or some suggestions to how we do this from below.
How we search for new kernel availability from proposed:
#apt-cache madison linux-azure | grep ${release}-proposed
But doing an install right after that will fail most of the times if the
kernel was just published:
#apt clean all
#apt -y update
#apt install linux-azure/$release
^ this is after we add the proposed repo in sources.list.
Actual error in the end:
linux-azure : Depends: linux-image-azure (= 4.15.0.1034.34) but 4.15.0.1030.30
E: Unable to correct problems, you have held broken packages.
This is observed on all LTS versions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805849/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" - (New) + promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" + (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" - (Confirmed) + promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" + (New) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (New) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" - (New) + promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" + (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" - (Confirmed) + promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" + (New) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (New) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]
Still the same problem on Lenovo T440 on Ubuntu 18.04 AND Ubuntu 18.10. 'Init MAC failed' all the time -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239578 Title: No wireless support for Realtek RTL8192EE [10ec:818b] Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Status in linux source package in Utopic: Fix Released Bug description: Open this bug to trace device driver RTL8192EE. We have seen this wireless card on some laptops, id is [10ec:818b], driver is RTL8192EE. This bug is only for the initial support of this WiFi adapter, it's not working 100% well yet, please report new "not working bug" or contact upstream but not keep posting comments, thanks. Status: pull-request for trusty was NAKed because next minor Trusty release will use Utopic LTS kernel, which had already fixed this issue. please wait it or upgrade your whole distro to Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1239578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" - (New) + promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" + (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764956] Re: Guests using IBRS incur a large performance penalty
** Changed in: linux (Ubuntu Xenial)
Assignee: Guilherme G. Piccoli (gpiccoli) => Gavin Guo (mimi0213kimo)
** Changed in: linux (Ubuntu)
Assignee: Guilherme G. Piccoli (gpiccoli) => Gavin Guo (mimi0213kimo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764956
Title:
Guests using IBRS incur a large performance penalty
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
[Impact]
the IBRS would be mistakenly enabled in the host when the switching
from an IBRS-enabled VM and that causes the performance overhead in
the host. The other condition could also mistakenly disables the IBRS
in VM when context-switching from the host. And this could be
considered a CVE host.
[Fix]
The patch fixes the logic inside the x86_virt_spec_ctrl that it checks
the ibrs_enabled and _or_ the hostval with the SPEC_CTRL_IBRS as the
x86_spec_ctrl_base by default is zero. Because the upstream
implementation is not equal to the Xenial's implementation. Upstream
doesn't use the IBRS as the formal fix. So, by default, it's zero.
On the other hand, after the VM exit, the SPEC_CTRL register also
needs to be saved manually by reading the SPEC_CTRL MSR as the MSR
intercept is disabled by default in the hardware_setup(v4.4) and
vmx_init(v3.13). The access to SPEC_CTRL MSR in VM is direct and
doesn't trigger a trap. So, the vmx_set_msr() function isn't called.
The v3.13 kernel hasn't been tested. However, the patch can be viewed
at:
http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=sf00191076-sru
The v4.4 patch:
http://kernel.ubuntu.com/git/gavinguo/ubuntu-xenial.git/log/?h=sf00191076-spectre-v2-regres-backport-juerg
[Test]
The patch has been tested on the 4.4.0-140.166 and works fine.
The reproducing environment:
Guest kernel version: 4.4.0-138.164
Host kernel version: 4.4.0-140.166
(host IBRS, guest IBRS)
- 1). (0, 1).
The case can be reproduced by the following instructions:
guest$ echo 1 | sudo tee /proc/sys/kernel/ibrs_enabled
1
host$ cat /proc/sys/kernel/ibrs_enabled
0
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
110001001010
Some of the IBRS bit inside the SPEC_CTRL MSR are mistakenly
enabled.
host$ taskset -c 5 stress-ng -c 1 --cpu-ops 2500
stress-ng: info: [11264] defaulting to a 86400 second run per stressor
stress-ng: info: [11264] dispatching hogs: 1 cpu
stress-ng: info: [11264] cache allocate: default cache size: 35840K
stress-ng: info: [11264] successful run completed in 33.48s
The host kernel didn't notice the IBRS bit is enabled. So, the situation
is the same as "echo 2 > /proc/sys/kernel/ibrs_enabled" in the host.
And running the stress-ng is a pure userspace CPU capability
calculation. So, the performance downgrades to about 1/3. Without the
IBRS enabled, it needs about 10s.
- 2). (1, 1) disables IBRS in host -> (0, 1) actually it becomes (0, 0).
The guest IBRS has been mistakenly disabled.
guest$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
host$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
host$ echo 0 | sudo tee /proc/sys/kernel/ibrs_enabled
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764956/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805465] Re: linux: 4.19.0-7.8 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- - phase: Packaging - phase-changed: Thursday, 29. November 2018 21:31 UTC + phase: Uploaded + phase-changed: Thursday, 29. November 2018 22:03 UTC reason: - prepare-package-meta: Package tag not yet published - prepare-package-signed: Package tag not yet published promote-to-proposed: 'FAILED: Packages no longer available' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805465 Title: linux: 4.19.0-7.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- phase: Uploaded phase-changed: Thursday, 29. November 2018 22:03 UTC reason: promote-to-proposed: 'FAILED: Packages no longer available' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" - (Confirmed) + promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" + (New) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-candidate is neither "Fix Released" nor "Invalid" (New) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805465] Re: linux: 4.19.0-7.8 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-disco ** Tags added: block-proposed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- phase: Packaging - phase-changed: Wednesday, 28. November 2018 12:46 UTC + phase-changed: Thursday, 29. November 2018 21:31 UTC reason: - prepare-package: Package not yet uploaded - prepare-package-meta: Package not yet uploaded - prepare-package-signed: Package not yet uploaded + prepare-package-meta: Package tag not yet published + prepare-package-signed: Package tag not yet published + promote-to-proposed: 'FAILED: Packages no longer available' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805465 Title: linux: 4.19.0-7.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released 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: Incomplete Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: -- swm properties -- phase: Packaging phase-changed: Thursday, 29. November 2018 21:31 UTC reason: prepare-package-meta: Package tag not yet published prepare-package-signed: Package tag not yet published promote-to-proposed: 'FAILED: Packages no longer available' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
This bug was fixed in the package mesa - 18.2.6-1ubuntu1 --- mesa (18.2.6-1ubuntu1) disco; urgency=medium * Merge from Debian. - add missing i965 pci-id's (LP: #1789924) -- Timo Aaltonen Wed, 28 Nov 2018 23:14:08 +0200 ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: New Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 - phase: Uploaded - phase-changed: Tuesday, 27. November 2018 16:44 UTC + phase: Promoted to updates + phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Ready to copy - promote-to-updates: Ready to copy + promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" + (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802341] Re: crash in ENA driver on removing an interface
This bug was fixed in the package linux-aws - 4.15.0-1029.30 --- linux-aws (4.15.0-1029.30) bionic; urgency=medium * Miscellaneous Ubuntu changes - [Config] linux-aws: enable arm64 build linux-aws (4.15.0-1028.29) bionic; urgency=medium * linux-aws: 4.15.0-1028.29 -proposed tracker (LP: #1802558) * Improve AWS hibernation performance (LP: #1803613) - SAUCE: [aws] PM / hibernate: Speed up hibernation by batching requests * Restore request-based mode to xen-blkfront for AWS kernels (LP: #1801305) - SAUCE: xen/manage: keep track of the on-going suspend mode - SAUCE: xen/manage: introduce helper function to know the on-going suspend mode - SAUCE: xenbus: add freeze/thaw/restore callbacks support - SAUCE: xen-blkfront: add callbacks for PM suspend and hibernation - SAUCE: xen-blkfront: resurrect request-based mode - SAUCE: xen-blkfront: Fixed blkfront_restore to remove a call to negotiate_mq [ Ubuntu: 4.15.0-42.45 ] * linux: 4.15.0-42.45 -proposed tracker (LP: #1803592) * [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405) - KVM: s390: reset crypto attributes for all vcpus - KVM: s390: vsie: simulate VCPU SIE entry/exit - KVM: s390: introduce and use KVM_REQ_VSIE_RESTART - KVM: s390: refactor crypto initialization - s390: vfio-ap: base implementation of VFIO AP device driver - s390: vfio-ap: register matrix device with VFIO mdev framework - s390: vfio-ap: sysfs interfaces to configure adapters - s390: vfio-ap: sysfs interfaces to configure domains - s390: vfio-ap: sysfs interfaces to configure control domains - s390: vfio-ap: sysfs interface to view matrix mdev matrix - KVM: s390: interface to clear CRYCB masks - s390: vfio-ap: implement mediated device open callback - s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl - s390: vfio-ap: zeroize the AP queues - s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl - KVM: s390: Clear Crypto Control Block when using vSIE - KVM: s390: vsie: Do the CRYCB validation first - KVM: s390: vsie: Make use of CRYCB FORMAT2 clear - KVM: s390: vsie: Allow CRYCB FORMAT-2 - KVM: s390: vsie: allow CRYCB FORMAT-1 - KVM: s390: vsie: allow CRYCB FORMAT-0 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1 - KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2 - KVM: s390: device attrs to enable/disable AP interpretation - KVM: s390: CPU model support for AP virtualization - s390: doc: detailed specifications for AP virtualization - KVM: s390: fix locking for crypto setting error path - KVM: s390: Tracing APCB changes - s390: vfio-ap: setup APCB mask using KVM dedicated function - s390/zcrypt: Add ZAPQ inline function. - s390/zcrypt: Review inline assembler constraints. - s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h. - s390/zcrypt: fix ap_instructions_available() returncodes - s390/zcrypt: remove VLA usage from the AP bus - s390/zcrypt: Remove deprecated ioctls. - s390/zcrypt: Remove deprecated zcrypt proc interface. - s390/zcrypt: Support up to 256 crypto adapters. - [Config:] Enable CONFIG_S390_AP_IOMMU and set CONFIG_VFIO_AP to module. * Bypass of mount visibility through userns + mount propagation (LP: #1789161) - mount: Retest MNT_LOCKED in do_umount - mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts * CVE-2018-18955: nested user namespaces with more than five extents incorrectly grant privileges over inode (LP: #1801924) // CVE-2018-18955 - userns: also map extents in the reverse map to kernel IDs * kdump fail due to an IRQ storm (LP: #1797990) - SAUCE: x86/PCI: Export find_cap() to be used in early PCI code - SAUCE: x86/quirks: Add parameter to clear MSIs early on boot - SAUCE: x86/quirks: Scan all busses for early PCI quirks [ Ubuntu: 4.15.0-40.43 ] * linux: 4.15.0-40.43 -proposed tracker (LP: #1802554) * crash in ENA driver on removing an interface (LP: #1802341) - SAUCE: net: ena: fix crash during ena_remove() * Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding (LP: #1797367) - s390/qeth: don't keep track of MAC address's cast type - s390/qeth: consolidate qeth MAC address helpers - s390/qeth: avoid using is_multicast_ether_addr_64bits on (u8 *)[6] - s390/qeth: remove outdated portname debug msg - s390/qeth: reduce hard-coded access to ccw channels - s390/qeth: sanitize strings in debug messages * [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding (LP: #1799184) - s390/zcrypt: code beautify - s390/zcrypt: AP bus support for alternate driver(s) - s390/zcrypt: hex string mask improvements for apmask and aqmask. - s390/zcrypt: remove unused functions and declarations - s390/zcrypt: Show load of cards
[Kernel-packages] [Bug 1802341] Re: crash in ENA driver on removing an interface
This bug was fixed in the package linux-aws - 4.15.0-1029.30 --- linux-aws (4.15.0-1029.30) bionic; urgency=medium * Miscellaneous Ubuntu changes - [Config] linux-aws: enable arm64 build linux-aws (4.15.0-1028.29) bionic; urgency=medium * linux-aws: 4.15.0-1028.29 -proposed tracker (LP: #1802558) * Improve AWS hibernation performance (LP: #1803613) - SAUCE: [aws] PM / hibernate: Speed up hibernation by batching requests * Restore request-based mode to xen-blkfront for AWS kernels (LP: #1801305) - SAUCE: xen/manage: keep track of the on-going suspend mode - SAUCE: xen/manage: introduce helper function to know the on-going suspend mode - SAUCE: xenbus: add freeze/thaw/restore callbacks support - SAUCE: xen-blkfront: add callbacks for PM suspend and hibernation - SAUCE: xen-blkfront: resurrect request-based mode - SAUCE: xen-blkfront: Fixed blkfront_restore to remove a call to negotiate_mq [ Ubuntu: 4.15.0-42.45 ] * linux: 4.15.0-42.45 -proposed tracker (LP: #1803592) * [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405) - KVM: s390: reset crypto attributes for all vcpus - KVM: s390: vsie: simulate VCPU SIE entry/exit - KVM: s390: introduce and use KVM_REQ_VSIE_RESTART - KVM: s390: refactor crypto initialization - s390: vfio-ap: base implementation of VFIO AP device driver - s390: vfio-ap: register matrix device with VFIO mdev framework - s390: vfio-ap: sysfs interfaces to configure adapters - s390: vfio-ap: sysfs interfaces to configure domains - s390: vfio-ap: sysfs interfaces to configure control domains - s390: vfio-ap: sysfs interface to view matrix mdev matrix - KVM: s390: interface to clear CRYCB masks - s390: vfio-ap: implement mediated device open callback - s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl - s390: vfio-ap: zeroize the AP queues - s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl - KVM: s390: Clear Crypto Control Block when using vSIE - KVM: s390: vsie: Do the CRYCB validation first - KVM: s390: vsie: Make use of CRYCB FORMAT2 clear - KVM: s390: vsie: Allow CRYCB FORMAT-2 - KVM: s390: vsie: allow CRYCB FORMAT-1 - KVM: s390: vsie: allow CRYCB FORMAT-0 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1 - KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2 - KVM: s390: device attrs to enable/disable AP interpretation - KVM: s390: CPU model support for AP virtualization - s390: doc: detailed specifications for AP virtualization - KVM: s390: fix locking for crypto setting error path - KVM: s390: Tracing APCB changes - s390: vfio-ap: setup APCB mask using KVM dedicated function - s390/zcrypt: Add ZAPQ inline function. - s390/zcrypt: Review inline assembler constraints. - s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h. - s390/zcrypt: fix ap_instructions_available() returncodes - s390/zcrypt: remove VLA usage from the AP bus - s390/zcrypt: Remove deprecated ioctls. - s390/zcrypt: Remove deprecated zcrypt proc interface. - s390/zcrypt: Support up to 256 crypto adapters. - [Config:] Enable CONFIG_S390_AP_IOMMU and set CONFIG_VFIO_AP to module. * Bypass of mount visibility through userns + mount propagation (LP: #1789161) - mount: Retest MNT_LOCKED in do_umount - mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts * CVE-2018-18955: nested user namespaces with more than five extents incorrectly grant privileges over inode (LP: #1801924) // CVE-2018-18955 - userns: also map extents in the reverse map to kernel IDs * kdump fail due to an IRQ storm (LP: #1797990) - SAUCE: x86/PCI: Export find_cap() to be used in early PCI code - SAUCE: x86/quirks: Add parameter to clear MSIs early on boot - SAUCE: x86/quirks: Scan all busses for early PCI quirks [ Ubuntu: 4.15.0-40.43 ] * linux: 4.15.0-40.43 -proposed tracker (LP: #1802554) * crash in ENA driver on removing an interface (LP: #1802341) - SAUCE: net: ena: fix crash during ena_remove() * Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding (LP: #1797367) - s390/qeth: don't keep track of MAC address's cast type - s390/qeth: consolidate qeth MAC address helpers - s390/qeth: avoid using is_multicast_ether_addr_64bits on (u8 *)[6] - s390/qeth: remove outdated portname debug msg - s390/qeth: reduce hard-coded access to ccw channels - s390/qeth: sanitize strings in debug messages * [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding (LP: #1799184) - s390/zcrypt: code beautify - s390/zcrypt: AP bus support for alternate driver(s) - s390/zcrypt: hex string mask improvements for apmask and aqmask. - s390/zcrypt: remove unused functions and declarations - s390/zcrypt: Show load of cards
[Kernel-packages] [Bug 1802341] Re: crash in ENA driver on removing an interface
This bug was fixed in the package linux-aws - 4.18.0-1006.7 --- linux-aws (4.18.0-1006.7) cosmic; urgency=medium * Miscellaneous Ubuntu changes - [Config] linux-aws: enable arm64 build linux-aws (4.18.0-1005.6) cosmic; urgency=medium * linux-aws: 4.18.0-1005.6 -proposed tracker (LP: #1802749) * Improve AWS hibernation performance (LP: #1803613) - SAUCE: [aws] PM / hibernate: Speed up hibernation by batching requests * Restore request-based mode to xen-blkfront for AWS kernels (LP: #1801305) - SAUCE: xen/manage: keep track of the on-going suspend mode - SAUCE: xen/manage: introduce helper function to know the on-going suspend mode - SAUCE: xenbus: add freeze/thaw/restore callbacks support - SAUCE: xen-blkfront: add callbacks for PM suspend and hibernation - SAUCE: xen-blkfront: resurrect request-based mode - SAUCE: xen-blkfront: Fixed blkfront_restore to remove a call to negotiate_mq [ Ubuntu: 4.18.0-12.13 ] * linux: 4.18.0-12.13 -proposed tracker (LP: #1802743) * [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405) - s390/zcrypt: Add ZAPQ inline function. - s390/zcrypt: Review inline assembler constraints. - s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h. - s390/zcrypt: fix ap_instructions_available() returncodes - KVM: s390: vsie: simulate VCPU SIE entry/exit - KVM: s390: introduce and use KVM_REQ_VSIE_RESTART - KVM: s390: refactor crypto initialization - s390: vfio-ap: base implementation of VFIO AP device driver - s390: vfio-ap: register matrix device with VFIO mdev framework - s390: vfio-ap: sysfs interfaces to configure adapters - s390: vfio-ap: sysfs interfaces to configure domains - s390: vfio-ap: sysfs interfaces to configure control domains - s390: vfio-ap: sysfs interface to view matrix mdev matrix - KVM: s390: interface to clear CRYCB masks - s390: vfio-ap: implement mediated device open callback - s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl - s390: vfio-ap: zeroize the AP queues - s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl - KVM: s390: Clear Crypto Control Block when using vSIE - KVM: s390: vsie: Do the CRYCB validation first - KVM: s390: vsie: Make use of CRYCB FORMAT2 clear - KVM: s390: vsie: Allow CRYCB FORMAT-2 - KVM: s390: vsie: allow CRYCB FORMAT-1 - KVM: s390: vsie: allow CRYCB FORMAT-0 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1 - KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2 - KVM: s390: device attrs to enable/disable AP interpretation - KVM: s390: CPU model support for AP virtualization - s390: doc: detailed specifications for AP virtualization - KVM: s390: fix locking for crypto setting error path - KVM: s390: Tracing APCB changes - s390: vfio-ap: setup APCB mask using KVM dedicated function - [Config:] Enable CONFIG_S390_AP_IOMMU and set CONFIG_VFIO_AP to module. * Bypass of mount visibility through userns + mount propagation (LP: #1789161) - mount: Retest MNT_LOCKED in do_umount - mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts * CVE-2018-18955: nested user namespaces with more than five extents incorrectly grant privileges over inode (LP: #1801924) // CVE-2018-18955 - userns: also map extents in the reverse map to kernel IDs * kdump fail due to an IRQ storm (LP: #1797990) - SAUCE: x86/PCI: Export find_cap() to be used in early PCI code - SAUCE: x86/quirks: Add parameter to clear MSIs early on boot - SAUCE: x86/quirks: Scan all busses for early PCI quirks * crash in ENA driver on removing an interface (LP: #1802341) - SAUCE: net: ena: fix crash during ena_remove() * Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding (LP: #1797367) - s390/qeth: reduce hard-coded access to ccw channels - s390/qeth: sanitize strings in debug messages * Add checksum offload and TSO support for HiNIC adapters (LP: #1800664) - net-next/hinic: add checksum offload and TSO support * smartpqi updates for ubuntu 18.04.2 (LP: #1798208) - scsi: smartpqi: improve handling for sync requests - scsi: smartpqi: improve error checking for sync requests - scsi: smartpqi: add inspur advantech ids - scsi: smartpqi: fix critical ARM issue reading PQI index registers - scsi: smartpqi: bump driver version to 1.1.4-130 * [GLK/CLX] Enhanced IBRS (LP: #1786139) - x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation - x86/speculation: Support Enhanced IBRS on future CPUs * Enable keyboard wakeup for S2Idle laptops (LP: #1798552) - Input: i8042 - enable keyboard wakeups by default when s2idle is used * Overlayfs in user namespace leaks directory content of inaccessible directories (LP: #1793458) // CVE-2018-6559 - SAUCE: overlayfs: ensure mounter
[Kernel-packages] [Bug 1802341] Re: crash in ENA driver on removing an interface
This bug was fixed in the package linux-aws - 4.18.0-1006.7 --- linux-aws (4.18.0-1006.7) cosmic; urgency=medium * Miscellaneous Ubuntu changes - [Config] linux-aws: enable arm64 build linux-aws (4.18.0-1005.6) cosmic; urgency=medium * linux-aws: 4.18.0-1005.6 -proposed tracker (LP: #1802749) * Improve AWS hibernation performance (LP: #1803613) - SAUCE: [aws] PM / hibernate: Speed up hibernation by batching requests * Restore request-based mode to xen-blkfront for AWS kernels (LP: #1801305) - SAUCE: xen/manage: keep track of the on-going suspend mode - SAUCE: xen/manage: introduce helper function to know the on-going suspend mode - SAUCE: xenbus: add freeze/thaw/restore callbacks support - SAUCE: xen-blkfront: add callbacks for PM suspend and hibernation - SAUCE: xen-blkfront: resurrect request-based mode - SAUCE: xen-blkfront: Fixed blkfront_restore to remove a call to negotiate_mq [ Ubuntu: 4.18.0-12.13 ] * linux: 4.18.0-12.13 -proposed tracker (LP: #1802743) * [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405) - s390/zcrypt: Add ZAPQ inline function. - s390/zcrypt: Review inline assembler constraints. - s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h. - s390/zcrypt: fix ap_instructions_available() returncodes - KVM: s390: vsie: simulate VCPU SIE entry/exit - KVM: s390: introduce and use KVM_REQ_VSIE_RESTART - KVM: s390: refactor crypto initialization - s390: vfio-ap: base implementation of VFIO AP device driver - s390: vfio-ap: register matrix device with VFIO mdev framework - s390: vfio-ap: sysfs interfaces to configure adapters - s390: vfio-ap: sysfs interfaces to configure domains - s390: vfio-ap: sysfs interfaces to configure control domains - s390: vfio-ap: sysfs interface to view matrix mdev matrix - KVM: s390: interface to clear CRYCB masks - s390: vfio-ap: implement mediated device open callback - s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl - s390: vfio-ap: zeroize the AP queues - s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl - KVM: s390: Clear Crypto Control Block when using vSIE - KVM: s390: vsie: Do the CRYCB validation first - KVM: s390: vsie: Make use of CRYCB FORMAT2 clear - KVM: s390: vsie: Allow CRYCB FORMAT-2 - KVM: s390: vsie: allow CRYCB FORMAT-1 - KVM: s390: vsie: allow CRYCB FORMAT-0 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1 - KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2 - KVM: s390: device attrs to enable/disable AP interpretation - KVM: s390: CPU model support for AP virtualization - s390: doc: detailed specifications for AP virtualization - KVM: s390: fix locking for crypto setting error path - KVM: s390: Tracing APCB changes - s390: vfio-ap: setup APCB mask using KVM dedicated function - [Config:] Enable CONFIG_S390_AP_IOMMU and set CONFIG_VFIO_AP to module. * Bypass of mount visibility through userns + mount propagation (LP: #1789161) - mount: Retest MNT_LOCKED in do_umount - mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts * CVE-2018-18955: nested user namespaces with more than five extents incorrectly grant privileges over inode (LP: #1801924) // CVE-2018-18955 - userns: also map extents in the reverse map to kernel IDs * kdump fail due to an IRQ storm (LP: #1797990) - SAUCE: x86/PCI: Export find_cap() to be used in early PCI code - SAUCE: x86/quirks: Add parameter to clear MSIs early on boot - SAUCE: x86/quirks: Scan all busses for early PCI quirks * crash in ENA driver on removing an interface (LP: #1802341) - SAUCE: net: ena: fix crash during ena_remove() * Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding (LP: #1797367) - s390/qeth: reduce hard-coded access to ccw channels - s390/qeth: sanitize strings in debug messages * Add checksum offload and TSO support for HiNIC adapters (LP: #1800664) - net-next/hinic: add checksum offload and TSO support * smartpqi updates for ubuntu 18.04.2 (LP: #1798208) - scsi: smartpqi: improve handling for sync requests - scsi: smartpqi: improve error checking for sync requests - scsi: smartpqi: add inspur advantech ids - scsi: smartpqi: fix critical ARM issue reading PQI index registers - scsi: smartpqi: bump driver version to 1.1.4-130 * [GLK/CLX] Enhanced IBRS (LP: #1786139) - x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation - x86/speculation: Support Enhanced IBRS on future CPUs * Enable keyboard wakeup for S2Idle laptops (LP: #1798552) - Input: i8042 - enable keyboard wakeups by default when s2idle is used * Overlayfs in user namespace leaks directory content of inaccessible directories (LP: #1793458) // CVE-2018-6559 - SAUCE: overlayfs: ensure mounter
[Kernel-packages] [Bug 1802558] Re: linux-aws: 4.15.0-1028.29 -proposed tracker
*** This bug is a duplicate of bug 1805362 *** https://bugs.launchpad.net/bugs/1805362 This bug was fixed in the package linux-aws - 4.15.0-1029.30 --- linux-aws (4.15.0-1029.30) bionic; urgency=medium * Miscellaneous Ubuntu changes - [Config] linux-aws: enable arm64 build linux-aws (4.15.0-1028.29) bionic; urgency=medium * linux-aws: 4.15.0-1028.29 -proposed tracker (LP: #1802558) * Improve AWS hibernation performance (LP: #1803613) - SAUCE: [aws] PM / hibernate: Speed up hibernation by batching requests * Restore request-based mode to xen-blkfront for AWS kernels (LP: #1801305) - SAUCE: xen/manage: keep track of the on-going suspend mode - SAUCE: xen/manage: introduce helper function to know the on-going suspend mode - SAUCE: xenbus: add freeze/thaw/restore callbacks support - SAUCE: xen-blkfront: add callbacks for PM suspend and hibernation - SAUCE: xen-blkfront: resurrect request-based mode - SAUCE: xen-blkfront: Fixed blkfront_restore to remove a call to negotiate_mq [ Ubuntu: 4.15.0-42.45 ] * linux: 4.15.0-42.45 -proposed tracker (LP: #1803592) * [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405) - KVM: s390: reset crypto attributes for all vcpus - KVM: s390: vsie: simulate VCPU SIE entry/exit - KVM: s390: introduce and use KVM_REQ_VSIE_RESTART - KVM: s390: refactor crypto initialization - s390: vfio-ap: base implementation of VFIO AP device driver - s390: vfio-ap: register matrix device with VFIO mdev framework - s390: vfio-ap: sysfs interfaces to configure adapters - s390: vfio-ap: sysfs interfaces to configure domains - s390: vfio-ap: sysfs interfaces to configure control domains - s390: vfio-ap: sysfs interface to view matrix mdev matrix - KVM: s390: interface to clear CRYCB masks - s390: vfio-ap: implement mediated device open callback - s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl - s390: vfio-ap: zeroize the AP queues - s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl - KVM: s390: Clear Crypto Control Block when using vSIE - KVM: s390: vsie: Do the CRYCB validation first - KVM: s390: vsie: Make use of CRYCB FORMAT2 clear - KVM: s390: vsie: Allow CRYCB FORMAT-2 - KVM: s390: vsie: allow CRYCB FORMAT-1 - KVM: s390: vsie: allow CRYCB FORMAT-0 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1 - KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2 - KVM: s390: device attrs to enable/disable AP interpretation - KVM: s390: CPU model support for AP virtualization - s390: doc: detailed specifications for AP virtualization - KVM: s390: fix locking for crypto setting error path - KVM: s390: Tracing APCB changes - s390: vfio-ap: setup APCB mask using KVM dedicated function - s390/zcrypt: Add ZAPQ inline function. - s390/zcrypt: Review inline assembler constraints. - s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h. - s390/zcrypt: fix ap_instructions_available() returncodes - s390/zcrypt: remove VLA usage from the AP bus - s390/zcrypt: Remove deprecated ioctls. - s390/zcrypt: Remove deprecated zcrypt proc interface. - s390/zcrypt: Support up to 256 crypto adapters. - [Config:] Enable CONFIG_S390_AP_IOMMU and set CONFIG_VFIO_AP to module. * Bypass of mount visibility through userns + mount propagation (LP: #1789161) - mount: Retest MNT_LOCKED in do_umount - mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts * CVE-2018-18955: nested user namespaces with more than five extents incorrectly grant privileges over inode (LP: #1801924) // CVE-2018-18955 - userns: also map extents in the reverse map to kernel IDs * kdump fail due to an IRQ storm (LP: #1797990) - SAUCE: x86/PCI: Export find_cap() to be used in early PCI code - SAUCE: x86/quirks: Add parameter to clear MSIs early on boot - SAUCE: x86/quirks: Scan all busses for early PCI quirks [ Ubuntu: 4.15.0-40.43 ] * linux: 4.15.0-40.43 -proposed tracker (LP: #1802554) * crash in ENA driver on removing an interface (LP: #1802341) - SAUCE: net: ena: fix crash during ena_remove() * Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding (LP: #1797367) - s390/qeth: don't keep track of MAC address's cast type - s390/qeth: consolidate qeth MAC address helpers - s390/qeth: avoid using is_multicast_ether_addr_64bits on (u8 *)[6] - s390/qeth: remove outdated portname debug msg - s390/qeth: reduce hard-coded access to ccw channels - s390/qeth: sanitize strings in debug messages * [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding (LP: #1799184) - s390/zcrypt: code beautify - s390/zcrypt: AP bus support for alternate driver(s) - s390/zcrypt: hex string mask improvements for apmask and aqmask. -
[Kernel-packages] [Bug 1803613] Re: Improve AWS hibernation performance
This bug was fixed in the package linux-aws - 4.15.0-1029.30 --- linux-aws (4.15.0-1029.30) bionic; urgency=medium * Miscellaneous Ubuntu changes - [Config] linux-aws: enable arm64 build linux-aws (4.15.0-1028.29) bionic; urgency=medium * linux-aws: 4.15.0-1028.29 -proposed tracker (LP: #1802558) * Improve AWS hibernation performance (LP: #1803613) - SAUCE: [aws] PM / hibernate: Speed up hibernation by batching requests * Restore request-based mode to xen-blkfront for AWS kernels (LP: #1801305) - SAUCE: xen/manage: keep track of the on-going suspend mode - SAUCE: xen/manage: introduce helper function to know the on-going suspend mode - SAUCE: xenbus: add freeze/thaw/restore callbacks support - SAUCE: xen-blkfront: add callbacks for PM suspend and hibernation - SAUCE: xen-blkfront: resurrect request-based mode - SAUCE: xen-blkfront: Fixed blkfront_restore to remove a call to negotiate_mq [ Ubuntu: 4.15.0-42.45 ] * linux: 4.15.0-42.45 -proposed tracker (LP: #1803592) * [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405) - KVM: s390: reset crypto attributes for all vcpus - KVM: s390: vsie: simulate VCPU SIE entry/exit - KVM: s390: introduce and use KVM_REQ_VSIE_RESTART - KVM: s390: refactor crypto initialization - s390: vfio-ap: base implementation of VFIO AP device driver - s390: vfio-ap: register matrix device with VFIO mdev framework - s390: vfio-ap: sysfs interfaces to configure adapters - s390: vfio-ap: sysfs interfaces to configure domains - s390: vfio-ap: sysfs interfaces to configure control domains - s390: vfio-ap: sysfs interface to view matrix mdev matrix - KVM: s390: interface to clear CRYCB masks - s390: vfio-ap: implement mediated device open callback - s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl - s390: vfio-ap: zeroize the AP queues - s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl - KVM: s390: Clear Crypto Control Block when using vSIE - KVM: s390: vsie: Do the CRYCB validation first - KVM: s390: vsie: Make use of CRYCB FORMAT2 clear - KVM: s390: vsie: Allow CRYCB FORMAT-2 - KVM: s390: vsie: allow CRYCB FORMAT-1 - KVM: s390: vsie: allow CRYCB FORMAT-0 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1 - KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2 - KVM: s390: device attrs to enable/disable AP interpretation - KVM: s390: CPU model support for AP virtualization - s390: doc: detailed specifications for AP virtualization - KVM: s390: fix locking for crypto setting error path - KVM: s390: Tracing APCB changes - s390: vfio-ap: setup APCB mask using KVM dedicated function - s390/zcrypt: Add ZAPQ inline function. - s390/zcrypt: Review inline assembler constraints. - s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h. - s390/zcrypt: fix ap_instructions_available() returncodes - s390/zcrypt: remove VLA usage from the AP bus - s390/zcrypt: Remove deprecated ioctls. - s390/zcrypt: Remove deprecated zcrypt proc interface. - s390/zcrypt: Support up to 256 crypto adapters. - [Config:] Enable CONFIG_S390_AP_IOMMU and set CONFIG_VFIO_AP to module. * Bypass of mount visibility through userns + mount propagation (LP: #1789161) - mount: Retest MNT_LOCKED in do_umount - mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts * CVE-2018-18955: nested user namespaces with more than five extents incorrectly grant privileges over inode (LP: #1801924) // CVE-2018-18955 - userns: also map extents in the reverse map to kernel IDs * kdump fail due to an IRQ storm (LP: #1797990) - SAUCE: x86/PCI: Export find_cap() to be used in early PCI code - SAUCE: x86/quirks: Add parameter to clear MSIs early on boot - SAUCE: x86/quirks: Scan all busses for early PCI quirks [ Ubuntu: 4.15.0-40.43 ] * linux: 4.15.0-40.43 -proposed tracker (LP: #1802554) * crash in ENA driver on removing an interface (LP: #1802341) - SAUCE: net: ena: fix crash during ena_remove() * Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding (LP: #1797367) - s390/qeth: don't keep track of MAC address's cast type - s390/qeth: consolidate qeth MAC address helpers - s390/qeth: avoid using is_multicast_ether_addr_64bits on (u8 *)[6] - s390/qeth: remove outdated portname debug msg - s390/qeth: reduce hard-coded access to ccw channels - s390/qeth: sanitize strings in debug messages * [18.04 FEAT] zcrypt DD: introduce APQN tags to support deterministic driver binding (LP: #1799184) - s390/zcrypt: code beautify - s390/zcrypt: AP bus support for alternate driver(s) - s390/zcrypt: hex string mask improvements for apmask and aqmask. - s390/zcrypt: remove unused functions and declarations - s390/zcrypt: Show load of cards
[Kernel-packages] [Bug 1805360] Re: linux-aws: 4.18.0-1006.7 -proposed tracker
The package has been published and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 - phase: Uploaded - phase-changed: Tuesday, 27. November 2018 16:39 UTC + phase: Released + phase-changed: Thursday, 29. November 2018 21:05 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-security: Ready to copy - promote-to-updates: Ready to copy ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1805360 Title: linux-aws: 4.18.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Released phase-changed: Thursday, 29. November 2018 21:05 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803613] Re: Improve AWS hibernation performance
This bug was fixed in the package linux-aws - 4.18.0-1006.7 --- linux-aws (4.18.0-1006.7) cosmic; urgency=medium * Miscellaneous Ubuntu changes - [Config] linux-aws: enable arm64 build linux-aws (4.18.0-1005.6) cosmic; urgency=medium * linux-aws: 4.18.0-1005.6 -proposed tracker (LP: #1802749) * Improve AWS hibernation performance (LP: #1803613) - SAUCE: [aws] PM / hibernate: Speed up hibernation by batching requests * Restore request-based mode to xen-blkfront for AWS kernels (LP: #1801305) - SAUCE: xen/manage: keep track of the on-going suspend mode - SAUCE: xen/manage: introduce helper function to know the on-going suspend mode - SAUCE: xenbus: add freeze/thaw/restore callbacks support - SAUCE: xen-blkfront: add callbacks for PM suspend and hibernation - SAUCE: xen-blkfront: resurrect request-based mode - SAUCE: xen-blkfront: Fixed blkfront_restore to remove a call to negotiate_mq [ Ubuntu: 4.18.0-12.13 ] * linux: 4.18.0-12.13 -proposed tracker (LP: #1802743) * [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405) - s390/zcrypt: Add ZAPQ inline function. - s390/zcrypt: Review inline assembler constraints. - s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h. - s390/zcrypt: fix ap_instructions_available() returncodes - KVM: s390: vsie: simulate VCPU SIE entry/exit - KVM: s390: introduce and use KVM_REQ_VSIE_RESTART - KVM: s390: refactor crypto initialization - s390: vfio-ap: base implementation of VFIO AP device driver - s390: vfio-ap: register matrix device with VFIO mdev framework - s390: vfio-ap: sysfs interfaces to configure adapters - s390: vfio-ap: sysfs interfaces to configure domains - s390: vfio-ap: sysfs interfaces to configure control domains - s390: vfio-ap: sysfs interface to view matrix mdev matrix - KVM: s390: interface to clear CRYCB masks - s390: vfio-ap: implement mediated device open callback - s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl - s390: vfio-ap: zeroize the AP queues - s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl - KVM: s390: Clear Crypto Control Block when using vSIE - KVM: s390: vsie: Do the CRYCB validation first - KVM: s390: vsie: Make use of CRYCB FORMAT2 clear - KVM: s390: vsie: Allow CRYCB FORMAT-2 - KVM: s390: vsie: allow CRYCB FORMAT-1 - KVM: s390: vsie: allow CRYCB FORMAT-0 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1 - KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2 - KVM: s390: device attrs to enable/disable AP interpretation - KVM: s390: CPU model support for AP virtualization - s390: doc: detailed specifications for AP virtualization - KVM: s390: fix locking for crypto setting error path - KVM: s390: Tracing APCB changes - s390: vfio-ap: setup APCB mask using KVM dedicated function - [Config:] Enable CONFIG_S390_AP_IOMMU and set CONFIG_VFIO_AP to module. * Bypass of mount visibility through userns + mount propagation (LP: #1789161) - mount: Retest MNT_LOCKED in do_umount - mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts * CVE-2018-18955: nested user namespaces with more than five extents incorrectly grant privileges over inode (LP: #1801924) // CVE-2018-18955 - userns: also map extents in the reverse map to kernel IDs * kdump fail due to an IRQ storm (LP: #1797990) - SAUCE: x86/PCI: Export find_cap() to be used in early PCI code - SAUCE: x86/quirks: Add parameter to clear MSIs early on boot - SAUCE: x86/quirks: Scan all busses for early PCI quirks * crash in ENA driver on removing an interface (LP: #1802341) - SAUCE: net: ena: fix crash during ena_remove() * Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding (LP: #1797367) - s390/qeth: reduce hard-coded access to ccw channels - s390/qeth: sanitize strings in debug messages * Add checksum offload and TSO support for HiNIC adapters (LP: #1800664) - net-next/hinic: add checksum offload and TSO support * smartpqi updates for ubuntu 18.04.2 (LP: #1798208) - scsi: smartpqi: improve handling for sync requests - scsi: smartpqi: improve error checking for sync requests - scsi: smartpqi: add inspur advantech ids - scsi: smartpqi: fix critical ARM issue reading PQI index registers - scsi: smartpqi: bump driver version to 1.1.4-130 * [GLK/CLX] Enhanced IBRS (LP: #1786139) - x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation - x86/speculation: Support Enhanced IBRS on future CPUs * Enable keyboard wakeup for S2Idle laptops (LP: #1798552) - Input: i8042 - enable keyboard wakeups by default when s2idle is used * Overlayfs in user namespace leaks directory content of inaccessible directories (LP: #1793458) // CVE-2018-6559 - SAUCE: overlayfs: ensure mounter
[Kernel-packages] [Bug 1805360] Re: linux-aws: 4.18.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress -- 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/1805360 Title: linux-aws: 4.18.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Released phase-changed: Thursday, 29. November 2018 21:05 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to updates phase-changed: Thursday, 29. November 2018 21:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: snap-release-to-edge is neither "Fix Released" nor "Invalid" (Confirmed) snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802749] Re: linux-aws: 4.18.0-1005.6 -proposed tracker
*** This bug is a duplicate of bug 1805360 *** https://bugs.launchpad.net/bugs/1805360 This bug was fixed in the package linux-aws - 4.18.0-1006.7 --- linux-aws (4.18.0-1006.7) cosmic; urgency=medium * Miscellaneous Ubuntu changes - [Config] linux-aws: enable arm64 build linux-aws (4.18.0-1005.6) cosmic; urgency=medium * linux-aws: 4.18.0-1005.6 -proposed tracker (LP: #1802749) * Improve AWS hibernation performance (LP: #1803613) - SAUCE: [aws] PM / hibernate: Speed up hibernation by batching requests * Restore request-based mode to xen-blkfront for AWS kernels (LP: #1801305) - SAUCE: xen/manage: keep track of the on-going suspend mode - SAUCE: xen/manage: introduce helper function to know the on-going suspend mode - SAUCE: xenbus: add freeze/thaw/restore callbacks support - SAUCE: xen-blkfront: add callbacks for PM suspend and hibernation - SAUCE: xen-blkfront: resurrect request-based mode - SAUCE: xen-blkfront: Fixed blkfront_restore to remove a call to negotiate_mq [ Ubuntu: 4.18.0-12.13 ] * linux: 4.18.0-12.13 -proposed tracker (LP: #1802743) * [FEAT] Guest-dedicated Crypto Adapters (LP: #1787405) - s390/zcrypt: Add ZAPQ inline function. - s390/zcrypt: Review inline assembler constraints. - s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h. - s390/zcrypt: fix ap_instructions_available() returncodes - KVM: s390: vsie: simulate VCPU SIE entry/exit - KVM: s390: introduce and use KVM_REQ_VSIE_RESTART - KVM: s390: refactor crypto initialization - s390: vfio-ap: base implementation of VFIO AP device driver - s390: vfio-ap: register matrix device with VFIO mdev framework - s390: vfio-ap: sysfs interfaces to configure adapters - s390: vfio-ap: sysfs interfaces to configure domains - s390: vfio-ap: sysfs interfaces to configure control domains - s390: vfio-ap: sysfs interface to view matrix mdev matrix - KVM: s390: interface to clear CRYCB masks - s390: vfio-ap: implement mediated device open callback - s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl - s390: vfio-ap: zeroize the AP queues - s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl - KVM: s390: Clear Crypto Control Block when using vSIE - KVM: s390: vsie: Do the CRYCB validation first - KVM: s390: vsie: Make use of CRYCB FORMAT2 clear - KVM: s390: vsie: Allow CRYCB FORMAT-2 - KVM: s390: vsie: allow CRYCB FORMAT-1 - KVM: s390: vsie: allow CRYCB FORMAT-0 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1 - KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2 - KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2 - KVM: s390: device attrs to enable/disable AP interpretation - KVM: s390: CPU model support for AP virtualization - s390: doc: detailed specifications for AP virtualization - KVM: s390: fix locking for crypto setting error path - KVM: s390: Tracing APCB changes - s390: vfio-ap: setup APCB mask using KVM dedicated function - [Config:] Enable CONFIG_S390_AP_IOMMU and set CONFIG_VFIO_AP to module. * Bypass of mount visibility through userns + mount propagation (LP: #1789161) - mount: Retest MNT_LOCKED in do_umount - mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts * CVE-2018-18955: nested user namespaces with more than five extents incorrectly grant privileges over inode (LP: #1801924) // CVE-2018-18955 - userns: also map extents in the reverse map to kernel IDs * kdump fail due to an IRQ storm (LP: #1797990) - SAUCE: x86/PCI: Export find_cap() to be used in early PCI code - SAUCE: x86/quirks: Add parameter to clear MSIs early on boot - SAUCE: x86/quirks: Scan all busses for early PCI quirks * crash in ENA driver on removing an interface (LP: #1802341) - SAUCE: net: ena: fix crash during ena_remove() * Ubuntu 18.04.1 - [s390x] Kernel panic while stressing network bonding (LP: #1797367) - s390/qeth: reduce hard-coded access to ccw channels - s390/qeth: sanitize strings in debug messages * Add checksum offload and TSO support for HiNIC adapters (LP: #1800664) - net-next/hinic: add checksum offload and TSO support * smartpqi updates for ubuntu 18.04.2 (LP: #1798208) - scsi: smartpqi: improve handling for sync requests - scsi: smartpqi: improve error checking for sync requests - scsi: smartpqi: add inspur advantech ids - scsi: smartpqi: fix critical ARM issue reading PQI index registers - scsi: smartpqi: bump driver version to 1.1.4-130 * [GLK/CLX] Enhanced IBRS (LP: #1786139) - x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation - x86/speculation: Support Enhanced IBRS on future CPUs * Enable keyboard wakeup for S2Idle laptops (LP: #1798552) - Input: i8042 - enable keyboard wakeups by default when s2idle is used * Overlayfs in user namespace leaks directory content of
[Kernel-packages] [Bug 1803173] Re: cloud-init disables user on azure at second reboot
Thanks All. A newer Azure Agent which no longer touches cloud-init data is already in the pipeline. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803173 Title: cloud-init disables user on azure at second reboot Status in cloud-init: Invalid Status in linux package in Ubuntu: Triaged Status in walinuxagent package in Ubuntu: Confirmed Bug description: Hello, Environment: platform: Azure arm image: Canonical UbuntuServer 16.04-DAILY-LTS latest Steps: Deploy VM with user/pass authentication Install latest linux-next-upstream kernel (for example 4.19.0-4db9d11bcbef, where 4db9d11bcbef is the git tag from the linux-next latest tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next/) reboot (all good) reboot again cloud-init disables the username password authentication I checked the cloud-init logs and found: 2018-11-01 16:45:28,566 - init.py[INFO]: User already exists, skipping. 2018-11-01 16:45:28,570 - util.py[DEBUG]: Running command ['passwd', '-l', ''] with allowed return codes [0] (shell=False, capture=True) 2018-11-01 16:45:28,793 - util.py[DEBUG]: Reading from /etc/sudoers (quiet=False) 2018-11-01 16:45:28,795 - util.py[DEBUG]: Read 781 bytes from /etc/sudoers 2018-11-01 16:45:28,796 - util.py[DEBUG]: Writing to /etc/sudoers.d/90-cloud-init-users - ab: [None] 51 bytes 2018-11-01 16:45:28,797 - handlers.py[DEBUG]: finish: init-network/config-users-groups: SUCCESS: config-users-groups ran successfully This issue is very bad one, as it can render your vm inaccessible on Azure. I think this problem is due to the new kernel installation. Initial bug report: https://github.com/Azure/WALinuxAgent/issues/1386 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1803173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Master bug not ready for release - promote-to-updates: Master bug not ready for release + promote-to-security: Ready to copy + promote-to-updates: Ready to copy snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Ready to copy promote-to-updates: Ready to copy snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805360] Re: linux-aws: 4.18.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => New ** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => New ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-security Status: Confirmed => New ** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => New ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Tags removed: block-proposed-cosmic ** Tags removed: block-proposed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Master bug not ready for release - promote-to-updates: Master bug not ready for release + promote-to-security: Ready to copy + promote-to-updates: Ready to copy -- 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/1805360 Title: linux-aws: 4.18.0-1006.7 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Ready to copy promote-to-updates: Ready to copy To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Tags added: kernel-manual-release -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Ready to copy promote-to-updates: Ready to copy snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805360] Re: linux-aws: 4.18.0-1006.7 -proposed tracker
** Tags added: kernel-manual-release -- 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/1805360 Title: linux-aws: 4.18.0-1006.7 -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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1644056] Re: kernel BUG at /build/linux-lts-xenial-gUF4JR/linux-lts-xenial-4.4.0/mm/huge_memory.c:1931!
FYI, a 4.8.0 kernel (not ubuntu) Nov 29 13:34:42 fanny kernel: [2752823.883284] BUG: Bad rss-counter state mm:8d1c56233c00 idx:1 val:5 Nov 29 13:34:42 fanny kernel: [2752823.883292] BUG: non-zero nr_ptes on freeing mm: 2 $ cat /proc/version Linux version 4.8.0-0.bpo.2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.8.15-2~bpo8+2 (2017-01-17) $ cat /proc/meminfo MemTotal: 264141684 kB $ cat /proc/cpuinfo processor : 23 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : AMD Opteron(tm) Processor 6344 stepping: 0 microcode : 0x600081c TLB size: 1536 4K pages clflush size: 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid amd_dcm aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bugs: fxsave_leak sysret_ss_attrs null_seg bogomips: 5200.02 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1644056 Title: kernel BUG at /build/linux-lts-xenial-gUF4JR/linux-lts- xenial-4.4.0/mm/huge_memory.c:1931! Status in linux package in Ubuntu: Confirmed Bug description: Hi, While running IO on the following kernel/Ubuntu version: $ lsb_release -rd Description:Ubuntu 14.04.5 LTS Release:14.04 $ uname -a Linux 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/issue Ubuntu 14.04.5 LTS \n \l [1133672.985186] /build/linux-lts-xenial-gUF4JR/linux-lts-xenial-4.4.0/mm/pgtable-generic.c:33: bad pmd 881fd6790240(80004b8008e7) [1135572.440941] huge_memory: mapcount 0 page_mapcount 1 [1135572.441607] [ cut here ] [1135572.442059] kernel BUG at /build/linux-lts-xenial-gUF4JR/linux-lts-xenial-4.4.0/mm/huge_memory.c:1931! [1135572.442571] invalid opcode: [#1] SMP [1135572.443028] Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm joydev input_leds sb_edac irqbypass crct10dif_pclmul crc32_pclmul aesni_intel edac_core aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd dm_multipath lpc_ich ipmi_ssif ipmi_devintf shpchp 8250_fintek mac_hid acpi_power_meter ipmi_si ipmi_msghandler iTCO_wdt iTCO_vendor_support raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear ses enclosure raid1 ast ttm ixgbe hid_generic igb vxlan drm_kms_helper syscopyarea ip6_udp_tunnel usbhid dca sysfillrect udp_tunnel sysimgblt hid mxm_wmi fb_sys_fops mpt3sas ptp drm ahci raid_class pps_core libahci i2c_algo_bit mdio scsi_transport_sas fjes wmi [1135572.448909] CPU: 15 PID: 2018 Comm: sh Not tainted 4.4.0-31-generic #50~14.04.1-Ubuntu [1135572.450082] Hardware name: Quanta Computer Inc. X-100.Column.01/S2PC-MB(Dual 1G LOM), BIOS S2P_3B04.HGT02 09/21/2016 [1135572.451346] task: 8814923ae040 ti: 882eba658000 task.ti: 882eba658000 [1135572.452494] RIP: 0010:[] [] __split_huge_page+0x691/0x6d0 [1135572.453580] RSP: 0018:882eba65b7e0 EFLAGS: 00010292 [1135572.454589] RAX: 0027 RBX: ea00012e RCX: [1135572.455742] RDX: 0001 RSI: 883fff3cdc78 RDI: 883fff3cdc78 [1135572.457040] RBP: 882eba65b860 R08: R09: 881fe93eaf00 [1135572.458271] R10: 03ff R11: 0ac1 R12: [1135572.459539] R13: 882eba65ba10 R14: ea00012e R15: ea00012e [1135572.460746] FS: 7fcf6b305740() GS:883fff3c() knlGS: [1135572.461972] CS: 0010 DS: ES: CR0: 80050033 [1135572.463237] CR2: 558db9da0bb8 CR3: 0021667eb000 CR4: 003406e0 [1135572.464515] DR0: DR1: DR2: [1135572.465831] DR3: DR6: fffe0ff0 DR7: 0400 [1135572.467177] Stack: [1135572.468502] 882eba65b840 811bdfe9 883fed2e51d0 [1135572.469769] 811c67c8 883fee9bb760 0007f43c9000 882eba65ba10 [1135572.471040] 7b6d 81c72fa0 883ff17340f4 ea00012e [1135572.472277] Call Trace:
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release - security-signoff: Waiting for signoff snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel -- 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/1805362 Title: linux-aws: 4.15.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
4.18 EOL now anyway The only way out is to revert the above commit this patch isn't yet upstream https://patchwork.linuxtv.org/patch/53155/ Also this patch which has made into kernel 4.18 commit 7d95fb746c4eece67308f1642a666ea1ebdbd2cc Revert "media: dvbsky: use just one mutex for serializing device R/W ops" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Confirmed Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805362] Re: linux-aws: 4.15.0-1029.30 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1805362 Title: linux-aws: 4.15.0-1029.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release security-signoff: Waiting for signoff snap-release-to-beta: Snap not in 18/beta channel snap-release-to-edge: Snap not in 18/edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804533] Re: xen hibernation support for linux-aws (bionic)
** Changed in: linux-aws (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu) Status: In Progress => Fix Committed -- 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/1804533 Title: xen hibernation support for linux-aws (bionic) Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Bug description: AWS-specific xen hibernation support (as is already supported in linux-aws Xenial and Trusty) has been ported to linux-aws Bionic by the Amazon team. Patches to be applied to linux-aws-bionic: UBUNTU: SAUCE [aws] x86/xen: Introduce new function to map HYPERVISOR_shared_info on UBUNTU: SAUCE [aws] x86/xen: add system core suspend and resume callbacks UBUNTU: SAUCE [aws] xen-netfront: add callbacks for PM suspend and hibernation support UBUNTU: SAUCE [aws] xen-time-introduce-xen_-save-restore-_steal_clock UBUNTU: SAUCE [aws] x86/xen: save and restore steal clock UBUNTU: SAUCE [aws] xen/events: add xen_shutdown_pirqs helper function UBUNTU: SAUCE [aws] x86/xen: close event channels for PIRQs in system core suspend UBUNTU: SAUCE [aws] PM / hibernate: update the resume offset on SNAPSHOT_SET_SWAP_AREA This patch set passes simple hibernation smoke-testing on an instance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1804533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805360] Re: linux-aws: 4.18.0-1006.7 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release - security-signoff: Waiting for signoff -- 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/1805360 Title: linux-aws: 4.18.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805627] Re: zfs-linux 0.7.12-1ubuntu1 ADT test failure with linux 4.19.0-7.8
This bug was fixed in the package zfs-linux - 0.7.12-1ubuntu2 --- zfs-linux (0.7.12-1ubuntu2) disco; urgency=medium [ Colin Ian King ] * debian/control: remove armhf i386 suggests on zfs-modules and zfs-dkms for zfsutils-linux * debian/tests/control: only run tests for amd64, arm64, ppc64el and s390x (LP: #1805627) -- Colin Ian King Thu, 29 Nov 2018 15:55:12 + ** Changed in: zfs-linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1805627 Title: zfs-linux 0.7.12-1ubuntu1 ADT test failure with linux 4.19.0-7.8 Status in zfs-linux package in Ubuntu: Fix Released Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-bootstrap/disco/i386/z/zfs-linux/20181128_052301_6f831@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1805627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805360] Re: linux-aws: 4.18.0-1006.7 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1805360 Title: linux-aws: 4.18.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724992] Re: [Hyper-V] PCI passthrough no longer works on 4.4.0-97
Fixed by using linux-azure. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724992 Title: [Hyper-V] PCI passthrough no longer works on 4.4.0-97 Status in linux package in Ubuntu: Won't Fix Status in linux source package in Xenial: Won't Fix Bug description: Azure NV class: 4.11.0-1013: jrp@jrpubuntuv:~$ lspci :00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03) :00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01) :00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) :00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) :00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA 983b:00:00.0 VGA compatible controller: NVIDIA Corporation GM204GL [Tesla M60] (rev a1) 4.11 finds it fine, but NVIDIA's GRID driver doesn't support newer kernels like 4.11. 4.4.0-97: jrp@jrpubuntuv:~$ uname -r 4.4.0-97-generic jrp@jrpubuntuv:~$ lspci 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03) 00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01) 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) 00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA 4.4.0-77, 79, 83, 87, 89, 91, 92, 93, and 96 also fail to find the hardware. These used to work, so I am also investigating on the host/hardware side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724992] Re: [Hyper-V] PCI passthrough no longer works on 4.4.0-97
** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724992 Title: [Hyper-V] PCI passthrough no longer works on 4.4.0-97 Status in linux package in Ubuntu: Won't Fix Status in linux source package in Xenial: Won't Fix Bug description: Azure NV class: 4.11.0-1013: jrp@jrpubuntuv:~$ lspci :00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03) :00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01) :00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) :00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) :00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA 983b:00:00.0 VGA compatible controller: NVIDIA Corporation GM204GL [Tesla M60] (rev a1) 4.11 finds it fine, but NVIDIA's GRID driver doesn't support newer kernels like 4.11. 4.4.0-97: jrp@jrpubuntuv:~$ uname -r 4.4.0-97-generic jrp@jrpubuntuv:~$ lspci 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) (rev 03) 00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01) 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) 00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA 4.4.0-77, 79, 83, 87, 89, 91, 92, 93, and 96 also fail to find the hardware. These used to work, so I am also investigating on the host/hardware side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
I checked hwdata output in Unity Settings Displays menu with 2 different devices (vendors: LG and Dell) on LiveCDs for xenial, bionic, cosmic with the proposed patch installed (and with ubuntu-unity-desktop installed from universe in case of bionic and comsmic). Worked as expected (i.e. in the Test Case section of the bug description). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in hwdata source package in Xenial: Fix Committed Status in unity-settings-daemon source package in Xenial: Fix Committed Status in hwdata source package in Bionic: Fix Committed Status in unity-settings-daemon source package in Bionic: Fix Released Status in hwdata source package in Cosmic: Fix Committed Status in unity-settings-daemon source package in Cosmic: Fix Released Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805360] Re: linux-aws: 4.18.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Testing FAILED + promote-to-security: Master bug not ready for release + promote-to-updates: Master bug not ready for release security-signoff: Waiting for signoff -- 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/1805360 Title: linux-aws: 4.18.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1802743 phase: Uploaded phase-changed: Tuesday, 27. November 2018 16:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Master bug not ready for release promote-to-updates: Master bug not ready for release security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1805360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
Run the verifications for: hwdata | 0.267-1ubuntu2 | xenial-proposed hwdata | 0.290-1ubuntu0.18.04.1 | bionic-proposed hwdata | 0.290-1ubuntu0.18.10.1 | cosmic-proposed ** Tags removed: verification-needed-bionic verification-needed-cosmic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-cosmic verification-done-xenial ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in hwdata source package in Xenial: Fix Committed Status in unity-settings-daemon source package in Xenial: Fix Committed Status in hwdata source package in Bionic: Fix Committed Status in unity-settings-daemon source package in Bionic: Fix Released Status in hwdata source package in Cosmic: Fix Committed Status in unity-settings-daemon source package in Cosmic: Fix Released Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1755490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802776] Re: linux: 4.4.0-140.166 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1804491 (linux-aws), bug 1802779 (linux-lts-xenial) derivatives: bug 1802780 (linux-raspi2), bug 1802781 (linux-snapdragon), bug 1802783 (linux-euclid), bug 1802785 (linux-aws), bug 1802786 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED - certification-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802776 Title: linux: 4.4.0-140.166 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-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 snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1804491 (linux-aws), bug 1802779 (linux-lts-xenial) derivatives: bug 1802780 (linux-raspi2), bug 1802781 (linux-snapdragon), bug 1802783 (linux-euclid), bug 1802785 (linux-aws), bug 1802786 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802776] Re: linux: 4.4.0-140.166 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-140.166 /xenial-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing 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/1802776 Title: linux: 4.4.0-140.166 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-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 snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1804491 (linux-aws), bug 1802779 (linux-lts-xenial) derivatives: bug 1802780 (linux-raspi2), bug 1802781 (linux-snapdragon), bug 1802783 (linux-euclid), bug 1802785 (linux-aws), bug 1802786 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED regression-testing: Testing in progress security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797625] Re: Missing the 'Call Trace' with the cases of 'KernelOops'
** Changed in: apport (Ubuntu) Status: New => Incomplete ** Changed in: kerneloops (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/1797625 Title: Missing the 'Call Trace' with the cases of 'KernelOops' Status in apport package in Ubuntu: Incomplete Status in kerneloops package in Ubuntu: Incomplete Bug description: Hello, I am working with these two reports: * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] https://bugs.launchpad.net/bugs/1796385 * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] https://bugs.launchpad.net/bugs/1797538 And the file: 'OopsText.txt' does not appear in the 'Call Trace'. Others: https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 "The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem." Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 Uname: Linux 4.18.13-gnu x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 16:12:58 2018 InstallationDate: Installed on 2017-10-13 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1797625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675949] Re: perf report can't annotate kernel and dbgsym package has wrong addresses
This issue fell off my radar, and I never followed up on it. I'll see if we can get someone to take a look. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1675949 Title: perf report can't annotate kernel and dbgsym package has wrong addresses Status in linux package in Ubuntu: Expired Bug description: Running zesty 4.10.0-13-generic kernel and running: $ perf record followed by $ perf report results in output that can't be annotated (even when run as root). The following message appears: Couldn't annotate do_io_submit: No vmlinux file with build id 81ba79d482fa9e3ea58486de8f119b27fe6db55e was found in the path. Note that annotation using /proc/kcore requires CAP_SYS_RAWIO capability. Please use: perf buildid-cache -vu vmlinux Note this is being run as root and /proc/kcore is accessible with dd from the same shell: $ dd if=/proc/kcore bs=8 count=16 | hexdump 000 457f 464c 0102 0001 010 0004 00b7 0001 020 0040 030 0040 0038 0003 040 0004 00e8 Additionally, installing the linux-image-4.10.0-13-generic-dbgsym actually hurts the situation because the symbol addresses in the dbgsym don't match the kernel addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802743] Re: linux: 4.18.0-12.13 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1802744 (linux-hwe-edge), bug 1802746 (linux-aws-edge), bug 1802747 (linux-azure-edge), bug 1805606 (linux-aws-edge) derivatives: bug 1802748 (linux-raspi2), bug 1802749 (linux-aws), bug 1802750 (linux-gcp), bug 1802752 (linux-azure), bug 1802753 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Uploaded phase-changed: Wednesday, 28. November 2018 10:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED - certification-testing: Testing in progress security-signoff: Waiting for signoff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802743 Title: linux: 4.18.0-12.13 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1802744 (linux-hwe-edge), bug 1802746 (linux-aws-edge), bug 1802747 (linux-azure-edge), bug 1805606 (linux-aws-edge) derivatives: bug 1802748 (linux-raspi2), bug 1802749 (linux-aws), bug 1802750 (linux-gcp), bug 1802752 (linux-azure), bug 1802753 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Uploaded phase-changed: Wednesday, 28. November 2018 10:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805778] Re: ubuntu_vfat_stress failed again with P8/P9 Bionic
Sam, can this be retested, I think we were getting into dirty page write
amplification because of using vfat on a tmpfs backing store file. I've
reworked the test now to use bog standard vfat on a loopbacked file.
Fix committed: http://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=e39a7d03a6dbda3039514096737d72150877017b
** No longer affects: stress-ng
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu)
Status: Fix Committed => Triaged
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: ubuntu-kernel-tests
Importance: Undecided => High
** Changed in: ubuntu-kernel-tests
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805778
Title:
ubuntu_vfat_stress failed again with P8/P9 Bionic
Status in ubuntu-kernel-tests:
Fix Committed
Status in linux package in Ubuntu:
Triaged
Bug description:
This issue just like bug 1801907, but this time it's passed with P8
"modoc", failed with P8 "entei" and P9 "baltar"
I haven't run them directly, this is the result when testing with the
whole test suite.
06:21:04 INFO | START ubuntu_vfat_stress.vfat-stress
ubuntu_vfat_stress.vfat-stress timestamp=1543472464timeout=18000
localtime=Nov 29 06:21:04
06:21:04 DEBUG| Persistent state client._record_indent now set to 2
06:21:04 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_vfat_stress.vfat-stress', 'ubuntu_vfat_stress.vfat-stress')
06:21:04 DEBUG| Waiting for pid 56149 for 18000 seconds
06:21:04 DEBUG| Running 'LOG=/tmp/vfat-falure.log
STRESS_NG=/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng
DURATION=10s bash -c
/home/ubuntu/autotest/client/tests/ubuntu_vfat_stress/ubuntu_vfat_stress.sh
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src 2>&1'
06:21:04 DEBUG| [stdout] Testing: --verify --times --metrics-brief --syslog
--keep-name -t 10s --hdd 2 --hdd-opts sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd
--lockf 2 --seek 2 --aio 2 --aio-requests 32 --dentry 2 --dir 2 --dentry-order
stride --fallocate 2 --fstat 2 --dentries 100 --lease 2 --open 2 --rename 2
--hdd-bytes 4M --fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
06:21:04 DEBUG| [stdout] Mounting tmpfs /mnt/vfat-test-56154
06:21:05 DEBUG| [stdout] Created loop image
/mnt/vfat-test-56154/vfat-loop-data
06:21:05 DEBUG| [stdout] mkfs.fat 4.1 (2017-01-24)
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout] VFAT options: allow_utime=20
06:21:06 DEBUG| [stdout] Stress test:
/home/ubuntu/autotest/client/tmp/ubuntu_vfat_stress/src/stress-ng/stress-ng
--verify --times --metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
06:21:06 DEBUG| [stdout] VFAT_IMAGE path: /mnt/vfat-test-56154
06:21:06 DEBUG| [stdout] Mount point: /mnt/vfat-test-56154
06:21:06 DEBUG| [stdout] Date: Thu Nov 29 06:21:06 UTC 2018
06:21:06 DEBUG| [stdout] Host: baltar
06:21:06 DEBUG| [stdout] Kernel:4.15.0-42-generic #45-Ubuntu SMP Thu
Nov 15 19:29:37 UTC 2018
06:21:06 DEBUG| [stdout] Machine: baltar ppc64le ppc64le
06:21:06 DEBUG| [stdout] CPUs online: 40
06:21:06 DEBUG| [stdout] CPUs total:160
06:21:06 DEBUG| [stdout] Page size: 65536
06:21:06 DEBUG| [stdout] Pages avail: 1935143
06:21:06 DEBUG| [stdout] Pages total: 2089666
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout]
06:21:06 DEBUG| [stdout] Started, PID 56225
06:23:13 DEBUG| [stdout] Timed out waiting for stress-ng to finish
06:23:13 DEBUG| [stdout] Forcefully killing, PID 56225 (after 121 seconds)
06:23:23 DEBUG| [stdout] Found kernel warning and/or call trace:
06:23:23 DEBUG| [stdout]
06:23:23 DEBUG| [stdout] [ 4940.791800] Testing: --verify --times
--metrics-brief --syslog --keep-name -t 10s --hdd 2 --hdd-opts
sync,wr-rnd,rd-rnd,fadv-willneed,fadv-rnd --lockf 2 --seek 2 --aio 2
--aio-requests 32 --dentry 2 --dir 2 --dentry-order stride --fallocate 2
--fstat 2 --dentries 100 --lease 2 --open 2 --rename 2 --hdd-bytes 4M
--fallocate-bytes 4M --chdir 2 --rename 2 --hdd-write-size 512
06:23:23 DEBUG| [stdout] [ 4941.855398] Created loop image
/mnt/vfat-test-56154/vfat-loop-data
06:23:23 DEBUG| [stdout] [ 4942.232934]
[Kernel-packages] [Bug 1802743] Re: linux: 4.18.0-12.13 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/cosmic/4.18.0-12.13 /cosmic-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing 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/1802743 Title: linux: 4.18.0-12.13 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1802744 (linux-hwe-edge), bug 1802746 (linux-aws-edge), bug 1802747 (linux-azure-edge), bug 1805606 (linux-aws-edge) derivatives: bug 1802748 (linux-raspi2), bug 1802749 (linux-aws), bug 1802750 (linux-gcp), bug 1802752 (linux-azure), bug 1802753 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Uploaded phase-changed: Wednesday, 28. November 2018 10:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
Please attach `sudo lspci -vvnn`. I'd like to see if it support MSI-X or maskable MSI. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Confirmed Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension
I wonder what performance penalty "pci=nomsi,noaer" would has? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798921 Title: sky2 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Confirmed Bug description: Bug very similar to #1752772 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but affecting the sky2 driver instead of r8169. After system suspend the ethernet connection stops working. The card is still up and the modem can see it is connected, but the card doesn't get an ip address. Ifconfig down/up and restarting network- manager does not solve the issue. Similarly to the other bug, "sudo modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue. Relevant: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107 Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux *-network description: Ethernet interface product: 88E8040 PCI-E Fast Ethernet Controller vendor: Marvell Technology Group Ltd. physical id: 0 bus info: pci@:09:00.0 logical name: enp9s0 version: 13 serial: size: 100Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805670] Re: 18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues ex. suspend, touchpad
Link to change the package name does not work. It has already been changed to linux. I assume the issues are kernel related. Need I change anything else? ** 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/1805670 Title: 18.04 LTS - ACPI parsing errors in ZBook G5 Mobile Workstation: issues ex. suspend, touchpad Status in linux package in Ubuntu: Confirmed Bug description: Some background information: I have a new Ubuntu 18.04 installation that did not go too well. The Live-USB installation would hang with ACPi related errors. I finally installed (barring a GRUB install error) using the acpi=off kernel flag. I also tested with acpi=force and no acpi settings (only worked after the last kernel update). I report here with - no changes in the kernel parameters - no changes in BIOS except of graphics set to hybrid (Nvidia + Intel) otherwise I could not get it to work I am following the indications here: https://wiki.ubuntu.com/DebuggingACPI So here is the initial information I have (kernel version, kernel parameters, ACPI errors): .. uname -a Linux gandalf 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=82d8b6b9-1f12-4651--3639a6b76683 ro quiet splash vt.handoff=1 dmesg | grep -i acpi | grep -i error [0.00] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210) [0.00] ACPI Error: 1 table load failures, 19 successful (20170831/tbxfload-246) [0.164845] ACPI Error: Field [CAP1] at bit offset/length 64/32 exceeds size of target Buffer (64 bits) (20170831/dsopcode-235) [0.164874] ACPI Error: Method parse/execution failed \_SB._OSC, AE_AML_BUFFER_LIMIT (20170831/psparse-550) [3.528032] ACPI Error: Method parse/execution failed \_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550) [3.528042] ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103) [3.529831] ACPI Error: Method parse/execution failed \_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/psparse-550) [3.529840] ACPI Error: Method execution failed \_SB.PCI0.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20170831/uteval-103) [4.610629] ACPI Error: Method parse/execution failed \_TZ.GETP, AE_AML_PACKAGE_LIMIT (20170831/psparse-550) [4.610635] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, AE_AML_PACKAGE_LIMIT (20170831/psparse-550) [4.611513] ACPI Error: Method parse/execution failed \_TZ.GETP, AE_AML_PACKAGE_LIMIT (20170831/psparse-550) [4.611518] ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, AE_AML_PACKAGE_LIMIT (20170831/psparse-550) [8.206279] ACPI Error: Needed [Buffer/String/Package], found [Integer] 85bce4f4 (20170831/exresop-593) [8.206309] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20170831/psparse-550) [8.206315] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20170831/psparse-550) [8.210629] ACPI Error: Needed [Buffer/String/Package], found [Integer] 352a9487 (20170831/exresop-593) [8.210660] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20170831/psparse-550) [8.210666] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20170831/psparse-550) [8.214527] ACPI Error: Needed [Buffer/String/Package], found [Integer] 88ce12bb (20170831/exresop-593) [8.214555] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20170831/psparse-550) [8.214562] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20170831/psparse-550) [8.231122] ACPI Error: Attempt to CreateField of length zero (20170831/dsopcode-168) [8.231147] ACPI Error: Method parse/execution failed \_SB.WMIV.WVPI, AE_AML_OPERAND_VALUE (20170831/psparse-550) [8.231154] ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_VALUE (20170831/psparse-550) .. I have also added the following outputs: sudo lspci -vvnn >> report.txt sudo dmidecode > dmidecode.txt The kern.log after a suspend and resume. Some weird behavior I have noticed: . The Live-USB pendrive allowed me to use the touchpad when testing and installing Ubuntu . The current kernel does not allow me to use the touchpad . After I resume, the touchpad can be used . I cannot resume with the builtin At keyboard or touchpad . The
[Kernel-packages] [Bug 1756311] Re: fstrim and discard operations take too long to complete
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-aws (Ubuntu) Status: New => Confirmed -- 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/1756311 Title: fstrim and discard operations take too long to complete Status in linux-aws package in Ubuntu: Confirmed Bug description: 1-) Ubuntu Release : Ubuntu 14.04.5 LTS 2-) linux-image-3.13.0-143-generic and linux-image-4.4.0-1014-aws 3-) mkfs.xfs and fstrim -v on a raid0 array using nvme and md should not take more than some seconds to complete. 4-) Formating the raid0 array with xfs took around 2 hours. Running fstrim -v on the mount point mounted on top of the raid array took around 2 hours. How to reproduce the issue: - Launch an i3.4xlarge instance on Amazon AWS using an Ubuntu 14.04.5 AMI ( ami-78d2be01 on EU-WEST-1 ), this will generate an instance with one 8Gb EBS root volume and two 1.9T SSD drives that are presented to the instance using the nvme driver. - Compose a raid0 array with the following command : # mdadm --create --verbose --level=0 /dev/md0 --raid-devices=2 /dev/nvme0n1 /dev/nvme1n1 - When trying to format the raid0 array ( /dev/md0 ) using xfs it takes around 2 hours to complete. I tried other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. root@ip-172-31-30-133:~# time mkfs.xfs /dev/md0 real120m45.725s user0m0.000s sys 0m18.248s - Running fstrim -v on a filesystem mounted on top of /dev/md0 can take around 2 hours to complete. With other AMIs like RHEL7, CentOS7 and Ubuntu 18.04 and the time needed was around 2 seconds. - When I try the same with any of the nvme SSD devices alone, let's say /dev/nvme0n1, the issue doesn't happen. - I tried to replicate this issue using LVM and striping, fstrim and mkfs.xfs, the tasks complete without taking hours : root@ip-172-31-27-69:~# pvcreate /dev/nvme0n1 Physical volume "/dev/nvme0n1" successfully created root@ip-172-31-27-69:~# pvcreate /dev/nvme1n1 Physical volume "/dev/nvme1n1" successfully created root@ip-172-31-27-69:~# vgcreate raid0 /dev/nvme0n1 /dev/nvme1n1 Volume group "raid0" successfully created root@ip-172-31-27-69:~# lvcreate --type striped --stripes 2 --extents 100%FREE raid0 /dev/nvme0n1 /dev/nvme1n1 Using default stripesize 64.00 KiB. Logical volume "lvol0" created. root@ip-172-31-27-69:~# vgchange -ay 1 logical volume(s) in volume group "raid0" now active root@ip-172-31-27-69:~# lvchange -ay /dev/raid0/lvol0 root@ip-172-31-27-69:~# lvs -a /dev/raid0/lvol0 LVVGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol0 raid0 -wi-a- 3.46t htop root@ip-172-31-27-69:~# time mkfs.xfs /dev/raid0/lvol0 meta-data=/dev/raid0/lvol0 isize=512agcount=32, agsize=28991664 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0 data = bsize=4096 blocks=927733248, imaxpct=5 = sunit=16 swidth=32 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=453008, version=2 = sectsz=512 sunit=16 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 real0m2.926s user0m0.180s sys 0m0.000s root@ip-172-31-27-69:~# mount /dev/raid0/lvol0 /mnt root@ip-172-31-27-69:~# time fstrim -v /mnt /mnt: 3.5 TiB (3798138650624 bytes) trimmed real0m1.794s user0m0.000s sys 0m0.000s So the issue only happens when using nvme and md to compose the raid0 array. Bellow follows some information that may be useful: started formating the md array with mkfs.xfs. Process looks hanged. root@ip-172-31-24-66:~# ps aux | grep -i mkfs.xfs root 1693 12.0 0.0 12728 968 pts/1D+ 07:54 0:03 mkfs.xfs /dev/md0 PID 1693 is in uninterruptible sleep ( D ) Looking at /proc/7965/stack root@ip-172-31-24-66:~# cat /proc/1693/stack [] blkdev_issue_discard+0x232/0x2a0 [] blkdev_ioctl+0x61d/0x7d0 [] block_ioctl+0x41/0x50 [] do_vfs_ioctl+0x2e3/0x4d0 [] SyS_ioctl+0x81/0xa0 [] system_call_fastpath+0x1a/0x1f [] 0x Looking at the stack, looks like it's hanged on a discard operation root@ip-172-31-24-66:~# ps -flp 1693 F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 D root 1693 1682 2 80 0 - 3182 blkdev 07:54 pts/100:00:03 mkfs.xfs /dev/md0 root@ip-172-31-24-66:~# cat /proc/1693/wchan blkdev_issue_discard Process stuck with function --> blkdev_issue_discard To manage notifications about this bug go to:
[Kernel-packages] [Bug 1804007] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1804007 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: idk why every time i want install graphic card on 18.04 LTS always being like this ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Nov 19 12:10:24 2018 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 InstallationDate: Installed on 2018-11-17 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1804007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB
** Tags removed: triage-a ** Tags added: triage-r -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788098 Title: Avoid migration issues with aligned 2MB THB Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: FYI: This blocks bug 1781526 - once this one here is resolved we can go on with SRU considerations for 1781526 --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT--- Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802556] Re: linux-oem: 4.15.0-1027.32 -proposed tracker
*** This bug is a duplicate of bug 1805617 *** https://bugs.launchpad.net/bugs/1805617 ** This bug is no longer a duplicate of bug 1803678 linux-oem: 4.15.0-1028.33 -proposed tracker ** This bug has been marked a duplicate of bug 1805617 linux-oem: 4.15.0-1029.34 -proposed tracker -- 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/1802556 Title: linux-oem: 4.15.0-1027.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress regression-testing: Testing in progress security-signoff: Waiting for signoff verification-testing: Testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1802556/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804007] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1804007 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: idk why every time i want install graphic card on 18.04 LTS always being like this ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Nov 19 12:10:24 2018 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 InstallationDate: Installed on 2018-11-17 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1804007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803678] Re: linux-oem: 4.15.0-1028.33 -proposed tracker
*** This bug is a duplicate of bug 1805617 *** https://bugs.launchpad.net/bugs/1805617 ** This bug has been marked a duplicate of bug 1805617 linux-oem: 4.15.0-1029.34 -proposed tracker -- 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/1803678 Title: linux-oem: 4.15.0-1028.33 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1803592 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Testing FAILED certification-testing: Testing in progress security-signoff: Waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1803678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805849] Re: apt repository in proposed packages availability issue
** 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/1805849
Title:
apt repository in proposed packages availability issue
Status in linux package in Ubuntu:
Confirmed
Bug description:
We have a watcher that does the following:
- verifies if any linux-azure kernels have been published in proposed repo.
- if it detects one, it will install.
The problem we have is that even though we detect a new kernel in proposed,
the installation of it will fail as there are unmet package dependencies not
being available.
This does resolve after several hours, but the way it works is not reliable
that we see the main package being available, but the packages in the repo are
not ready yet.
So it seems to be a timing issue from the time the kernel is released, and
the time the packages actual get on the repo.
Can you please suggest on some methods to better handle the detect &
install for these, or some suggestions to how we do this from below.
How we search for new kernel availability from proposed:
#apt-cache madison linux-azure | grep ${release}-proposed
But doing an install right after that will fail most of the times if the
kernel was just published:
#apt clean all
#apt -y update
#apt install linux-azure/$release
^ this is after we add the proposed repo in sources.list.
Actual error in the end:
linux-azure : Depends: linux-image-azure (= 4.15.0.1034.34) but 4.15.0.1030.30
E: Unable to correct problems, you have held broken packages.
This is observed on all LTS versions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805849/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805841] Re: CPI information about kvm usage is lost during apt upgrade
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => s390-tools (Ubuntu) ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805841 Title: CPI information about kvm usage is lost during apt upgrade Status in Ubuntu on IBM z Systems: Triaged Status in s390-tools package in Ubuntu: New Bug description: ---Problem Description--- CPI information about kvm usage is lost during apt upgrade ---uname output--- 4.15.0-42-generic Machine Type = s390x lpar ---Steps to Reproduce--- # cat /sys/firmware/cpi/* cat: /sys/firmware/cpi/set: Permission denied 0x00040f00 LINUX root@m83lp52:~# virsh start guest # starting a guest does set the highest bit in /sys/firmware/cpi/system_leveln root@m83lp52:~# cat /sys/firmware/cpi/* cat: /sys/firmware/cpi/set: Permission denied 0x80040f00 < see the 8 LINUX root@m83lp52:~# apt upgrade [] has to upgrade at least one package, that will trigger some other code. [] Now. some other code seems to have set values in /sys/firmware/cpi as well dropping the kvm information. root@m83lp52:~# cat /sys/firmware/cpi/* cat: /sys/firmware/cpi/set: Permission denied 18 04 1 0x00040f00 UBUNTU LINUX The canonical place to handle /sys/firmware/cpi should be /lib/s390-tools/cpictl and /lib/systemd/system/cpi.service. So can we put the additional features (setting 18 04 1 and UBUNTU things also into /etc/sysconfig/cpi or /lib/s390-tools/cpictl ) and can we disable the other code that also sets /sys/firmware/cpi (I have not found out which code sets these values). This seems to be /lib/systemd/system-generators/s390-cpi-vars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805849] 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 1805849
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805849
Title:
apt repository in proposed packages availability issue
Status in linux package in Ubuntu:
Incomplete
Bug description:
We have a watcher that does the following:
- verifies if any linux-azure kernels have been published in proposed repo.
- if it detects one, it will install.
The problem we have is that even though we detect a new kernel in proposed,
the installation of it will fail as there are unmet package dependencies not
being available.
This does resolve after several hours, but the way it works is not reliable
that we see the main package being available, but the packages in the repo are
not ready yet.
So it seems to be a timing issue from the time the kernel is released, and
the time the packages actual get on the repo.
Can you please suggest on some methods to better handle the detect &
install for these, or some suggestions to how we do this from below.
How we search for new kernel availability from proposed:
#apt-cache madison linux-azure | grep ${release}-proposed
But doing an install right after that will fail most of the times if the
kernel was just published:
#apt clean all
#apt -y update
#apt install linux-azure/$release
^ this is after we add the proposed repo in sources.list.
Actual error in the end:
linux-azure : Depends: linux-image-azure (= 4.15.0.1034.34) but 4.15.0.1030.30
E: Unable to correct problems, you have held broken packages.
This is observed on all LTS versions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805849/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
