date:20180522

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1770294

Title:
  linux-azure: 4.15.0-1011.11 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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:
  Fix Released

Bug description:
  This bug is for tracking the 4.15.0-1011.11 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
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770294/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1770019] Re: linux-kvm: 4.4.0-1024.29 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: Fix Released => Invalid

-- 
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/1770019

Title:
  linux-kvm: 4.4.0-1024.29 -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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 Xenial:
  Fix Released

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: 1770011
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770019/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1767400] Re: linux-gcp: 4.15.0-1007.7 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1767400

Title:
  linux-gcp: 4.15.0-1007.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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Fix Released

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: 1767397
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767400/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1767409] Re: linux-kvm: 4.15.0-1009.9 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1767409

Title:
  linux-kvm: 4.15.0-1009.9 -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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 Bionic:
  Fix Released

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: 1767397
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767409/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1770011] Re: linux: 4.4.0-125.150 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: Fix Released => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770011

Title:
  linux: 4.4.0-125.150 -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:
  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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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:
  Invalid
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:
  Fix Released

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 1770013 (linux-aws), bug 1770015 (linux-lts-xenial)
  derivatives: bug 1770016 (linux-aws), bug 1770018 (linux-euclid), bug 1770019 
(linux-kvm), bug 1770020 (linux-raspi2), bug 1770023 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770011/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1767397] Re: linux: 4.15.0-21.22 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1767397

Title:
  linux: 4.15.0-21.22 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 Bionic:
  Fix Released

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 1767410 (linux-hwe-edge)
  derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 
(linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767397/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1767403] Re: linux-aws: 4.15.0-1008.8 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1767403

Title:
  linux-aws: 4.15.0-1008.8 -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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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:
  Fix Released

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: 1767397
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767403/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1770013] Re: linux-aws: 4.4.0-1020.20 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: Fix Released => Invalid

-- 
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/1770013

Title:
  linux-aws: 4.4.0-1020.20 -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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 Trusty:
  Fix Released

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: 1770011
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770013/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1770294] Re: linux-azure: 4.15.0-1011.11 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1770294

Title:
  linux-azure: 4.15.0-1011.11 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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:
  Fix Released

Bug description:
  This bug is for tracking the 4.15.0-1011.11 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
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1770294/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1767397] Re: linux: 4.15.0-21.22 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1767397

Title:
  linux: 4.15.0-21.22 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 Bionic:
  Fix Released

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 1767410 (linux-hwe-edge)
  derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 
(linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767397/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1767398] Re: linux-oem: 4.15.0-1005.8 -proposed tracker

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

-- 
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/1767398

Title:
  linux-oem: 4.15.0-1005.8 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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:
  Fix Released

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: 1767397
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767398/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1767398] Re: linux-oem: 4.15.0-1005.8 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1767398

Title:
  linux-oem: 4.15.0-1005.8 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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:
  Fix Released

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: 1767397
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767398/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1769993] Re: linux: 4.13.0-42.47 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: Fix Released => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1769993

Title:
  linux: 4.13.0-42.47 -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:
  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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 Artful:
  Fix Released

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 1769996 (linux-oem), bug 1769997 (linux-azure), bug 1766595 
(linux-azure-edge), bug 1770001 (linux-hwe), bug 1770002 (linux-gcp)
  derivatives: bug 1769995 (linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769993/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772626] Re: [Redpine] HCI command timeout after resume from S4

2018-05-22 Thread Timo Aaltonen

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
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/1772626

Title:
  [Redpine] HCI command timeout after resume from S4

Status in HWE Next:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux-oem source package in Bionic:
  New

Bug description:
  Redpine BT stops working after resume from S4.

  Symptoms:
  - The device list is increasing after resume. 
  - Error after command "hciconfig -a" which as:
  Can't read local name on hci0: Connection timed out (110)

  The reproduce steps:
  1) Go to hibernate mode
  $ sudo systemctl hibernate

  2) Wakeup system by power recycle

  3) Check the bluetooth list
  $ hciconfig -a
  hci1: Type: Primary Bus: SDIO
   BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
   DOWN
   RX bytes:574 acl:0 sco:0 events:30 errors:0
   TX bytes:0 acl:0 sco:0 commands:30 errors:0
   Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
   Link policy: RSWITCH
   Link mode: SLAVE ACCEPT

  hci0: Type: Primary Bus: SDIO
   BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
   UP RUNNING
   RX bytes:1238 acl:0 sco:0 events:75 errors:0
   TX bytes:0 acl:0 sco:0 commands:75 errors:0
   Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
   Link policy: RSWITCH
   Link mode: SLAVE ACCEPT
  Can't read local name on hci0: Connection timed out (110)

  4) Go to hibernate and wake again(as step 1-2)

  5) Try ifconfig command to check wifi device
  Result: command no response

  This bug is for tracking purposes only, please don't triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1772626/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1769993] Re: linux: 4.13.0-42.47 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1769993

Title:
  linux: 4.13.0-42.47 -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:
  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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 Artful:
  Fix Released

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 1769996 (linux-oem), bug 1769997 (linux-azure), bug 1766595 
(linux-azure-edge), bug 1770001 (linux-hwe), bug 1770002 (linux-gcp)
  derivatives: bug 1769995 (linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769993/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772641] Re: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package post-installation script subprocess re

2018-05-22 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1772641

Title:
  package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to
  install/upgrade: installed linux-image-4.15.0-22-generic package post-
  installation script subprocess returned error exit status 1

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Installed PyCharm from jetbrains > get this error when starting the 
application.
  Thx for your help!
  Pom

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue May 22 08:29:45 2018
  ErrorMessage: installed linux-image-4.15.0-22-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-08 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: linux-signed
  Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to 
install/upgrade: installed linux-image-4.15.0-22-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1772641/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1578141] Re: Predictable interface names partially broken with igb driver

2018-05-22 Thread Wladimir Mutel

I observe the same effect on Asus P10S-M WS motherboard with Ubuntu
18.04, kernel 4.15.0-22-generic

(from lshw :)
product: P10S-M WS Series
vendor: ASUSTeK COMPUTER INC.
version: Rev 1.xx

description: BIOS
vendor: American Megatrends Inc.
version: 4401
date: 03/05/2018

'biosdevname -d' prints both (2) onboard interfaces with BIOS device:
em1

BIOS device: em1
Kernel name: eno1
Permanent MAC: 2C:FD:A1:C6:F3:FA
Assigned MAC : 2C:FD:A1:C6:F3:FA
ifIndex: 2
Driver: igb
Driver version: 5.4.0-k
Firmware version: 3.16, 0x84d7
Bus Info: :01:00.0
PCI name  : :01:00.0
PCI Slot  : embedded
SMBIOS Device Type: Ethernet
SMBIOS Instance: 1
SMBIOS Label:  Onboard LAN
sysfs Index: 1
sysfs Label:  Onboard LAN
Embedded Index: 1

Duplicate: True
BIOS device: em1
Kernel name: rename3
Permanent MAC: 2C:FD:A1:C6:F3:FB
Assigned MAC : 2C:FD:A1:C6:F3:FB
ifIndex: 3
Driver: igb
Driver version: 5.4.0-k
Firmware version: 3.16, 0x8513
Bus Info: :02:00.0
PCI name  : :02:00.0
PCI Slot  : embedded
SMBIOS Device Type: Other
SMBIOS Instance: 1
SMBIOS Label:  Onboard 1394
sysfs Index: 1
sysfs Label:  Onboard 1394
Embedded Index: 2

Duplicate: True


so, this is not limited to SUpermicro boards only

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1578141

Title:
  Predictable interface names partially broken with igb driver

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Note: I'm not sure whether this is really a kernel bug or something
  within systemd/udev, please advise how to further debug.

  On a system with two GE ports, instead of getting named eno1 and eno2,
  I am getting eno1 and renameN. Where N starts at 3 and increases by 2
  on every iteration of doing "rmmod igb;modprobe igb". The
  corresponding lines in dmesg look like this:

  [2.748429] igb :07:00.0: added PHC on eth0
  [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection
  [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8e
  [2.748505] igb :07:00.0: eth0: PBA No: 106100-000
  [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.802555] igb :07:00.1: added PHC on eth1
  [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection
  [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8f
  [2.802631] igb :07:00.1: eth1: PBA No: 106100-000
  [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.803618] igb :07:00.0 eno1: renamed from eth0
  [2.833208] igb :07:00.1 rename3: renamed from eth1

  What is even worse: Sometimes the naming changes and the second
  interface ends up as eno1 while the first interface is named renameN
  with an even N. The bad thing about this version is that when it
  happens while the installer is running, the installer will setup
  "rename2" as the primary network interface, which works fine for the
  installation itself, but after installation is finished and the first
  boot of the installed system happens, that interface will be gone,
  leaving the system without network connectivity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  4 09:48 seq
   crw-rw 1 root audio 116, 33 May  4 09:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed May  4 10:00:39 2016
  HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro X9DRT-HF+
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1772641] [NEW] package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package post-installation script subprocess

2018-05-22 Thread Pom2terre

Public bug reported:

Installed PyCharm from jetbrains > get this error when starting the application.
Thx for your help!
Pom

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-22-generic 4.15.0-22.24
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Tue May 22 08:29:45 2018
ErrorMessage: installed linux-image-4.15.0-22-generic package post-installation 
script subprocess returned error exit status 1
InstallationDate: Installed on 2018-05-08 (14 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: linux-signed
Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to 
install/upgrade: installed linux-image-4.15.0-22-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic need-duplicate-check

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1772641

Title:
  package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to
  install/upgrade: installed linux-image-4.15.0-22-generic package post-
  installation script subprocess returned error exit status 1

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Installed PyCharm from jetbrains > get this error when starting the 
application.
  Thx for your help!
  Pom

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue May 22 08:29:45 2018
  ErrorMessage: installed linux-image-4.15.0-22-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2018-05-08 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: linux-signed
  Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to 
install/upgrade: installed linux-image-4.15.0-22-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1772641/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1769077] Re: linux: 3.13.0-148.197 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1769077

Title:
  linux: 3.13.0-148.197 -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:
  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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 Trusty:
  Fix Released

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 1769080 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769077/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1769080] Re: linux-lts-trusty: 3.13.0-148.197~precise1 -proposed tracker

All tasks have been completed and the bug is being set to Fix Released


** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Tags removed: kernel-release-tracking-bug-live

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1769080

Title:
  linux-lts-trusty: 3.13.0-148.197~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1769077
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769080/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1766067] Re: Dell XPS 9370 freezes at login screen/shortly after login with kernels after 4.15.0-13

2018-05-22 Thread Maximilian Federle

I reinstalled Bionic to a fresh/clean state (for unrelated reasons) and
can't reproduce the freezing with the current kernel. A bit mysterious.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: linux (Ubuntu)
   Status: Opinion => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1766067

Title:
  Dell XPS 9370 freezes at login screen/shortly after login with kernels
  after 4.15.0-13

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu freezes at the login screen or, if one is quick enough, shortly after 
typing a few chars of the password.
  Sometimes nothing except the power button works, at times I could reboot via 
endless massaging of sysrq + b.

  Last good kernel: 4.15.0-13
  Mainline 4.16.3 is also affected.
  Mainline 4.17rc1 is good again.

  ---

  lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  --- 
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mfederle  14667 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-15 (37 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair rfcomm 
thunderbolt uhid bnep snd_hda_codec_hdmi snd_hda_codec_realtek 
snd_hda_codec_generic uvcvideo videobuf2_vmalloc btusb videobuf2_memops btrtl 
videobuf2_v4l2 btbcm videobuf2_core btintel videodev bluetooth media 
hid_multitouch dell_laptop dell_smbios_smm dcdbas intel_rapl 
x86_pkg_temp_thermal intel_powerclamp snd_soc_skl coretemp snd_soc_skl_ipc 
snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core 
ac97_bus intel_cstate intel_rapl_perf dell_smbios_wmi dell_wmi snd_hda_intel 
dell_smbios snd_hda_codec snd_hda_core dell_wmi_descriptor wmi_bmof 
intel_wmi_thunderbolt ath10k_pci ath10k_core ath mac80211 cfg80211 rtsx_pci_ms 
idma64 virt_dma memstick mei_me intel_lpss_pci processor_thermal_device mei 
intel_soc_dts_iosf shpchp intel_lpss intel_pch_thermal intel_hid 
int3403_thermal sparse_keymap int3400_thermal mac_hid int340x_thermal_zone 
acpi_thermal_rel rtsx_pci_sdmmc i915 rtsx_pci wmi i2c_hid pinctrl_sunrisepoint 
pinctrl_intel
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=eb600459-616e-4745-bd8d-f28a5cc5578e ro quiet splash 
mem_sleep_default=deep crashkernel=384M-:128M vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766067/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

Here is another observation, when I run virtualbox on 17.10, and then
create a guest OS with 18.04 it runs fine, no kernel crashes. Thus this
evidence seems to point to the fact that 18.04 is not playing nicely
with the HP BIOS, but 17.10 does play nicely. 18.04 seems to have no
problems with the virtual BIOS provided by VirtualBox.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772038

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772038/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1769080] Re: linux-lts-trusty: 3.13.0-148.197~precise1 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: Fix Released => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1769080

Title:
  linux-lts-trusty: 3.13.0-148.197~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  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: 1769077
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769080/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1769077] Re: linux: 3.13.0-148.197 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-security
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: Fix Released => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1769077

Title:
  linux: 3.13.0-148.197 -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:
  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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow 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 Trusty:
  Fix Released

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 1769080 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769077/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772626] Re: [Redpine] HCI command timeout after resume from S4

2018-05-22 Thread Shrirang Bagul

** Tags added: originate-from-1771268 plano

** Changed in: hwe-next
   Status: New => Confirmed

** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
   Importance: Critical => High

** Changed in: hwe-next
 Assignee: (unassigned) => Shrirang Bagul (shrirang-bagul)

-- 
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/1772626

Title:
  [Redpine] HCI command timeout after resume from S4

Status in HWE Next:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  Redpine BT stops working after resume from S4.

  Symptoms:
  - The device list is increasing after resume. 
  - Error after command "hciconfig -a" which as:
  Can't read local name on hci0: Connection timed out (110)

  The reproduce steps:
  1) Go to hibernate mode
  $ sudo systemctl hibernate

  2) Wakeup system by power recycle

  3) Check the bluetooth list
  $ hciconfig -a
  hci1: Type: Primary Bus: SDIO
   BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
   DOWN
   RX bytes:574 acl:0 sco:0 events:30 errors:0
   TX bytes:0 acl:0 sco:0 commands:30 errors:0
   Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
   Link policy: RSWITCH
   Link mode: SLAVE ACCEPT

  hci0: Type: Primary Bus: SDIO
   BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
   UP RUNNING
   RX bytes:1238 acl:0 sco:0 events:75 errors:0
   TX bytes:0 acl:0 sco:0 commands:75 errors:0
   Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
   Link policy: RSWITCH
   Link mode: SLAVE ACCEPT
  Can't read local name on hci0: Connection timed out (110)

  4) Go to hibernate and wake again(as step 1-2)

  5) Try ifconfig command to check wifi device
  Result: command no response

  This bug is for tracking purposes only, please don't triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1772626/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1743541] Comment bridged from LTC Bugzilla

--- Comment From vipar...@in.ibm.com 2018-05-22 06:45 EDT---
(In reply to comment #15)
> IBM, could you please re-test with the latest bionic and report back here if
> the bug is still valid?

Hello Canonical,

This bug is still being seen with latest kernels.
4.15.0-22-generic is the most recent one seeing it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1743541

Title:
  Ubuntu18.04: PowerNV - cpupower monitor will not work when cpu0 is
  offline

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-16 
04:58:48 ==
  Problem Description :
  =

  cpupower monitor fails to show stop states when cpu 0 is made offline.

  Testing :
  =
  root@ltc-wspoon12:~# echo 0 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
  WARNING: at least one cpu is offline
  No HW Cstate monitors found
  root@ltc-wspoon12:~# 

  root@ltc-wspoon12:~# echo 1 > /sys/devices/system/cpu/cpu0/online 
  root@ltc-wspoon12:~# cpupower -c 12 monitor 
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop | stop | stop 
 0|  12|  12|  0.00|  0.00|  0.00|  0.00|  0.01

  Details :
  
  uname -a : Linux ltc-wspoon12 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 
21:15:55 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  OS : Ubuntu 18.04
  Machine : Witherspoon ( DD2.1) and Boston (DD.01)

  Patch :
  
  Patch that fixes the issue : 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  == Comment: #1 - VIPIN K. PARASHAR  - 2018-01-16 
05:09:40 ==
  (In reply to comment #0)

  > Patch :
  > 
  > Patch that fixes the issue :
  > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
  > ?id=dbdc468f35ee827cab2753caa1c660bdb832243a

  $ git log dbdc468f35ee827 -1
  commit dbdc468f35ee827cab2753caa1c660bdb832243a
  Author: Abhishek Goel 
  Date:   Wed Nov 15 14:10:02 2017 +0530

  cpupower : Fix cpupower working when cpu0 is offline
  
  cpuidle_monitor used to assume that cpu0 is always online which is not
  a valid assumption on POWER machines. This patch fixes this by getting
  the cpu on which the current thread is running, instead of always using
  cpu0 for monitoring which may not be online.
  
  Signed-off-by: Abhishek Goel 
  Signed-off-by: Shuah Khan 
  $

  Commit dbdc468f3 is available with 4.15-rc2 onwards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1743541/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1743541] Comment bridged from LTC Bugzilla

--- Comment From shriy...@in.ibm.com 2018-05-22 06:39 EDT---
This issue is still reproducible with latest kernel : 4.15.0-22-generic

root@ltc-wspoon12:~# cpupower monitor sleep 60
sleep took 60.03991 seconds and exited with status 0
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop | stop | stop | stop | stop | stop | stop
0|   0|   0|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 81.49|  6.52| 10.87
0|   0|   1|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 57.06|  1.50| 40.91
0|   0|   2|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.06|  0.00| 99.94
0|   0|   3|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.06|  0.00| 99.94
0|   4|   4|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 42.93|  0.00| 56.99
0|   4|   5|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  4.25|  0.00| 95.74
0|   4|   6|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.05|  0.00| 99.95
0|   4|   7|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.05|  0.00| 99.95
0|   8|   8|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.71
0|   8|   9|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.03|  0.00| 99.96
0|   8|  10|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  2.52|  0.00| 97.83
0|   8|  11|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.03|  0.00| 99.96
0|  12|  12|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  1.62|  0.00| 98.48
0|  12|  13|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  12|  14|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  12|  15|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  24|  16|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  4.65|  0.00| 95.08
0|  24|  17|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.05|  0.00| 99.95
0|  24|  18|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  24|  19|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  28|  20|  0.18|  8.47|  0.00|  0.00|  0.00|  0.00| 90.43|  0.00|  0.63
0|  28|  21|  0.00|  0.00|  0.00|  0.00|  3.91|  0.00|  0.07|  0.00| 96.02
0|  28|  22|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.11|  0.00| 99.89
0|  28|  23|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.07|  0.00| 99.93
0|  40|  24|  0.21| 65.05|  0.00|  0.00|  0.00|  0.00|  2.77|  0.00| 31.63
0|  40|  25|  0.27| 11.39|  0.00|  0.00|  0.00|  0.00|  2.74|  0.15| 85.13
0|  40|  26|  0.02| 19.97| 66.05|  0.00|  0.00|  0.00|  0.00|  0.00| 13.62
0|  40|  27|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.06|  0.00| 99.94
0|  44|  28|  0.01| 12.42| 67.47|  0.00|  0.74|  0.00|  3.22|  0.81| 14.88
0|  44|  29|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.08|  0.00| 99.92
0|  44|  30|  0.47| 14.39|  0.00|  0.00|  0.00|  0.00| 84.32|  0.00|  0.50
0|  44|  31|  0.00|  2.38|  0.00|  0.00|  0.00|  0.00|  0.06|  0.00| 97.56
0|  56|  32|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.02|  0.00| 99.74
0|  56|  33|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  56|  34|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  56|  35|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  2.15|  0.00| 97.59
0|  60|  36|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.31|  4.89| 94.56
0|  60|  37|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  8.11|  0.00| 91.88
0|  60|  38|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  60|  39|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  64|  40|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  7.20|  0.00| 92.76
0|  64|  41|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.07|  0.00| 99.93
0|  64|  42|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 94.04|  0.00|  6.04
0|  64|  43|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.07|  0.00| 99.93
0|  68|  44|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 10.25|  0.00| 89.51
0|  68|  45|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  68|  46|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  68|  47|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  72|  48|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 10.25|  0.00| 89.51
0|  72|  49|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  1.48|  0.00| 98.51
0|  72|  50|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  72|  51|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  76|  52|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 13.13|  0.00| 86.63
0|  76|  53|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  76|  54|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  76|  55|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.03|  0.00| 99.96
0|  80|  56|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00| 13.13|  0.00| 86.63
0|  80|  57|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  80|  58|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  80|  59|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.96
0|  84|  60|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.04|  0.00| 99.79
0|  84|  61|  0.00|  0.00|  0.00|  0.00|  0.00|  0.00|  0.05|  0.00| 99.95
0|  84|  62|

Re: [Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

Downloading the desktop image now, will report back later!

On 5/21/2018 12:09 PM, Joseph Salisbury wrote:
> Also, it would be good to know if this bug also happens with the current 
> daily iso:
> Desktop:
> http://cdimage.ubuntu.com/daily-live/current/
> Server:
> http://cdimage.ubuntu.com/ubuntu-server/daily/current/
>
>
> ** Tags added: kernel-key
>
> ** Also affects: linux (Ubuntu Bionic)
> Importance: Undecided
> Status: New
>
> ** Changed in: linux (Ubuntu Bionic)
> Importance: Undecided => High
>
> ** Changed in: linux (Ubuntu Bionic)
> Status: New => Incomplete
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772038

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772038/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772617] Re: fix inverted boolean flag in arch_add_memory, reverts back to original behaviour

2018-05-22 Thread Colin Ian King

Test kernel packages have been uploaded ready for testing:

http://kernel.ubuntu.com/~cking/lp1772617/

Please test these and report if this fixes the issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772617

Title:
  fix inverted boolean flag in arch_add_memory, reverts back to original
  behaviour

Status in linux package in Ubuntu:
  In Progress

Bug description:
  == SRU Justification, ARTFUL ==

  Bug fix #1761104 incorrectly inverted the flag in the call to 
arch_add_memory, it should be true instead of false.
  == Fix ==

  Fix partial backport from bug #1747069, remove can_online_high_movable
  and fix the incorrectly set boolean argument to arch_add_memory().
  NVIDIA are reported that this is was incorrectly flipped in the last
  SRU to fix their driver support on powerpc.

  == Testing ==

  run ADT memory hotplug test, should not regress this. Without the fix,
  the nvidia driver on powerpc will not work. With the fix it loads and
  works.

  == Regression Potential ==

  This fixes a regression in the original fix and hence the regression
  potential is the same as the previously SRU'd bug fix for #1747069,
  namely:

  "Reverting this commit does remove some functionality, however this
  does not regress the kernel compared to previous releases and having a
  working reliable memory hotplug is the preferred option. This fix does
  touch some memory hotplug, so there is a risk that this may break this
  functionality that is not covered by the kernel regression testing."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772617/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

These are older machines and boot with a BIOS. If I get free time, I'll 
remove the graphics card and see what happens, but I agree with 
jsailsbury I think it will still crash.

On 5/21/2018 12:14 PM, Penn Mackintosh wrote:
> Does your device boot UEFI or BIOS? The small bit of crash we can see
> looks like some kind of talk with the bootrom. If you can remove the
> video card that may also be the issue, they have been known to cause
> problems with just about everything. To debug without graphics (if your
> cpu/motherboard doesn't have intergrated) is to connect a serial
> console.
>
> jsailsbury - I think the crash will still occur, as it is a kernel
> crash, and it looks like it is in a hardware method.
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772038

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772038/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772626] [NEW] [Redpine] HCI command timeout after resume from S4

2018-05-22 Thread Shrirang Bagul

Public bug reported:

Redpine BT stops working after resume from S4.

Symptoms:
- The device list is increasing after resume. 
- Error after command "hciconfig -a" which as:
Can't read local name on hci0: Connection timed out (110)

The reproduce steps:
1) Go to hibernate mode
$ sudo systemctl hibernate

2) Wakeup system by power recycle

3) Check the bluetooth list
$ hciconfig -a
hci1: Type: Primary Bus: SDIO
 BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
 DOWN
 RX bytes:574 acl:0 sco:0 events:30 errors:0
 TX bytes:0 acl:0 sco:0 commands:30 errors:0
 Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
 Link policy: RSWITCH
 Link mode: SLAVE ACCEPT

hci0: Type: Primary Bus: SDIO
 BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
 UP RUNNING
 RX bytes:1238 acl:0 sco:0 events:75 errors:0
 TX bytes:0 acl:0 sco:0 commands:75 errors:0
 Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
 Link policy: RSWITCH
 Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)

4) Go to hibernate and wake again(as step 1-2)

5) Try ifconfig command to check wifi device
Result: command no response

This bug is for tracking purposes only, please don't triage.

** Affects: linux-oem (Ubuntu)
 Importance: Critical
 Status: Confirmed

** Changed in: linux-oem (Ubuntu)
   Status: New => Confirmed

** Changed in: linux-oem (Ubuntu)
   Importance: Undecided => Critical

-- 
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/1772626

Title:
  [Redpine] HCI command timeout after resume from S4

Status in linux-oem package in Ubuntu:
  Confirmed

Bug description:
  Redpine BT stops working after resume from S4.

  Symptoms:
  - The device list is increasing after resume. 
  - Error after command "hciconfig -a" which as:
  Can't read local name on hci0: Connection timed out (110)

  The reproduce steps:
  1) Go to hibernate mode
  $ sudo systemctl hibernate

  2) Wakeup system by power recycle

  3) Check the bluetooth list
  $ hciconfig -a
  hci1: Type: Primary Bus: SDIO
   BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
   DOWN
   RX bytes:574 acl:0 sco:0 events:30 errors:0
   TX bytes:0 acl:0 sco:0 commands:30 errors:0
   Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
   Link policy: RSWITCH
   Link mode: SLAVE ACCEPT

  hci0: Type: Primary Bus: SDIO
   BD Address: 00:23:A7:BF:34:F8 ACL MTU: 540:2 SCO MTU: 30:1
   UP RUNNING
   RX bytes:1238 acl:0 sco:0 events:75 errors:0
   TX bytes:0 acl:0 sco:0 commands:75 errors:0
   Features: 0x3f 0x02 0x04 0x4e 0xc8 0x0d 0x5b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1
   Link policy: RSWITCH
   Link mode: SLAVE ACCEPT
  Can't read local name on hci0: Connection timed out (110)

  4) Go to hibernate and wake again(as step 1-2)

  5) Try ifconfig command to check wifi device
  Result: command no response

  This bug is for tracking purposes only, please don't triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1772626/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

I have 2 of these computers, the 2nd computer has 8GB of memory and 1TB
HDD, same video card, but this second computer has a WiFi card
installed. I've tried several of the DVD's that I burned and I get the
same results the only difference is the time stamps shown on the screen
is different. On this second computer the crash happens quicker (ie the
timestamps are lower).

I'm currently downloading the 18.10 kernel and I'll report when I know
more about this daily build kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772038

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772038/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772624] [NEW] Broadcom BCM4356 wifi chipset firmware is not working

2018-05-22 Thread Jean-Pierre Thomasset

Public bug reported:

Hello,

After upgrading to Ubuntu 18.04 I got an issue with the wifi chipset
(Broadcom BCM4356) not initializing properly.

Here is the error I got when loading the driver brcmfmac:

```
[ 8189.092819] brcmfmac: brcmf_fw_map_chip_to_name: using 
brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x02
[ 8189.093100] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.txt failed with error -2
[ 8191.568544] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for query 
command
[ 8191.568562] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr 
failed, -5
[ 8191.568570] brcmfmac: brcmf_bus_started: failed: -5
[ 8191.568588] brcmfmac: brcmf_pcie_attach_bus: dongle is not responding
```

As seen here https://answers.launchpad.net/ubuntu/+question/668329, I
reverted to the previous linux-firmware version and then the wifi
chipset is working:

Previous firmware package: https://packages.ubuntu.com/artful-updates
/linux-firmware

```
[10087.698214] brcmfmac: brcmf_fw_map_chip_to_name: using 
brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x02
[10087.698634] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.txt failed with error -2
[10088.104176] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.clm_blob failed with error -2
[10088.104186] brcmfmac: brcmf_c_process_clm_blob: no clm_blob 
available(err=-2), device may have limited channels available
[10088.105170] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 22 
2015 06:16:41 version 7.35.180.119 (r594535) FWID 01-1a5c4016
[10088.179872] brcmfmac :04:00.0 wlp4s0: renamed from wlan0
```

The problem seems to have been reported to the linux-wireless mailing
list but no fix has been committed apparently :
https://www.spinics.net/lists/linux-wireless/msg168687.html

System information:
Description:Ubuntu 18.04 LTS
Release:18.04

linux-image-4.15.0-20-generic:
  Installé : 4.15.0-20.21
  Candidat : 4.15.0-20.21
 Table de version :
 *** 4.15.0-20.21 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

linux-firmware:
  Installé : 1.173
  Candidat : 1.173
 Table de version :
 *** 1.173 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://fr.archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status


Regards,
Jean Pierre.

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1772624

Title:
  Broadcom BCM4356 wifi chipset firmware is not working

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hello,

  After upgrading to Ubuntu 18.04 I got an issue with the wifi chipset
  (Broadcom BCM4356) not initializing properly.

  Here is the error I got when loading the driver brcmfmac:

  ```
  [ 8189.092819] brcmfmac: brcmf_fw_map_chip_to_name: using 
brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x02
  [ 8189.093100] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.txt failed with error -2
  [ 8191.568544] brcmfmac: brcmf_msgbuf_query_dcmd: Timeout on response for 
query command
  [ 8191.568562] brcmfmac: brcmf_c_preinit_dcmds: Retreiving cur_etheraddr 
failed, -5
  [ 8191.568570] brcmfmac: brcmf_bus_started: failed: -5
  [ 8191.568588] brcmfmac: brcmf_pcie_attach_bus: dongle is not responding
  ```

  As seen here https://answers.launchpad.net/ubuntu/+question/668329, I
  reverted to the previous linux-firmware version and then the wifi
  chipset is working:

  Previous firmware package: https://packages.ubuntu.com/artful-updates
  /linux-firmware

  ```
  [10087.698214] brcmfmac: brcmf_fw_map_chip_to_name: using 
brcm/brcmfmac4356-pcie.bin for chip 0x004356(17238) rev 0x02
  [10087.698634] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.txt failed with error -2
  [10088.104176] brcmfmac :04:00.0: Direct firmware load for 
brcm/brcmfmac4356-pcie.clm_blob failed with error -2
  [10088.104186] brcmfmac: brcmf_c_process_clm_blob: no clm_blob 
available(err=-2), device may have limited channels available
  [10088.105170] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Oct 
22 2015 06:16:41 version 7.35.180.119 (r594535) FWID 01-1a5c4016
  [10088.179872] brcmfmac :04:00.0 wlp4s0: renamed from wlan0
  ```

  The problem seems to have been reported to the linux-wireless mailing
  list but no fix has been committed apparently :
  https://www.spinics.net/lists/linux-wireless/msg168687.html

  System information:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  linux-image-4.15.0-20-generic:
Installé : 4.15.0-20.21
Candidat : 4.15.0-20.21
   Table de version :
   *** 4.15.0-20.21 500
  500

Re: [Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

I'm looking for the modules on the web page given and I'm not seeing 
where to download them. I'm not familiar with how launchpad works, so if 
there is another way to do this pls let me know.

On 5/21/2018 12:08 PM, Joseph Salisbury wrote:
> Can you install and see if installing a 18.04(Bionic) kernel will boot
> on 17.10?  The kernel can be downloaded from:
>
> https://launchpad.net/~canonical-kernel-
> team/+archive/ubuntu/ppa/+build/14810997
>
>
> You need to install the linux-modules, linux-modules-extra and 
> linux-image-unsigned .deb packages.
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => High
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772038

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772038/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1689240] Re: scrashme failed to build on s390x

2018-05-22 Thread Po-Hsu Lin

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1689240

Title:
  scrashme failed to build on s390x

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This test case failed to build on LPAR Ubuntu (s2lp4)
  Maybe we should disable it from the test suite.

  cc -Wall -W -Wshadow -g -O2 -o scrashme.o -c scrashme.c
  Makefile:13: recipe for target 'scrashme.o' failed
  stderr:
  scrashme.c: In function 'mkcall':
  scrashme.c:150:13: error: 'NR_SYSCALLS' undeclared (first use in this 
function)
  if (call > NR_SYSCALLS)
  ^~~
  scrashme.c:150:13: note: each undeclared identifier is reported only once for 
each function it appears in
  scrashme.c: In function 'do_syscall':
  scrashme.c:258:27: error: 'NR_SYSCALLS' undeclared (first use in this 
function)
  cl = rand() / (RAND_MAX/NR_SYSCALLS);
  ^~~
  scrashme.c: In function 'syscall_list':
  scrashme.c:293:15: error: 'NR_SYSCALLS' undeclared (first use in this 
function)
  for (i=0; i<=NR_SYSCALLS; i++) {
  ^~~
  scrashme.c: In function 'parse_args':
  scrashme.c:337:18: error: 'NR_SYSCALLS' undeclared (first use in this 
function)
  for (i=0; i<=NR_SYSCALLS; i++) {
  ^~~
  scrashme.c:371:13: error: 'KERNEL_ADDR' undeclared (first use in this 
function)
  regval = KERNEL_ADDR;
  ^~~
  scrashme.c: In function 'run_mode':
  scrashme.c:522:15: error: 'NR_SYSCALLS' undeclared (first use in this 
function)
   if (rep > NR_SYSCALLS) {
  ^~~
  scrashme.c: In function 'main':
  scrashme.c:588:13: error: 'syscalls_i386' undeclared (first use in this 
function)
  syscalls = syscalls_i386;
  ^
  scrashme.c: In function 'run_setup':
  scrashme.c:467:2: warning: ignoring return value of 'seteuid', declared with 
attribute warn_unused_result [-Wunused-result]
  seteuid(65536);
  ^~
  scrashme.c:468:2: warning: ignoring return value of 'seteuid', declared with 
attribute warn_unused_result [-Wunused-result]
  seteuid(65536);
  ^~
  scrashme.c:469:2: warning: ignoring return value of 'setgid', declared with 
attribute warn_unused_result [-Wunused-result]
  (void)setgid(65536);
  ^~~
  scrashme.c:470:2: warning: ignoring return value of 'seteuid', declared with 
attribute warn_unused_result [-Wunused-result]
  seteuid(65536);
  ^~
  scrashme.c:486:2: warning: ignoring return value of 'chroot', declared with 
attribute warn_unused_result [-Wunused-result]
  chroot("tmp");
  ^
  make: *** [scrashme.o] Error 1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-52-generic 4.8.0-52.55
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon May  8 03:25:31 2017
  HibernationDevice: RESUME=UUID=46fcf640-03e2-4fd5-b7d6-321d6a11ff8d
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=4a1de891-d624-42df-be09-50199aec3d11 
crashkernel=196M debug BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-52-generic N/A
   linux-backports-modules-4.8.0-52-generic  N/A
   linux-firmware1.161.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689240/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772617] [NEW] fix inverted boolean flag in arch_add_memory, reverts back to original behaviour

2018-05-22 Thread Colin Ian King

Public bug reported:

== SRU Justification, ARTFUL ==

Bug fix #1761104 incorrectly inverted the flag in the call to arch_add_memory, 
it should be true instead of false.
== Fix ==

Fix partial backport from bug #1747069, remove can_online_high_movable
and fix the incorrectly set boolean argument to arch_add_memory().
NVIDIA are reported that this is was incorrectly flipped in the last SRU
to fix their driver support on powerpc.

== Testing ==

run ADT memory hotplug test, should not regress this. Without the fix,
the nvidia driver on powerpc will not work. With the fix it loads and
works.

== Regression Potential ==

This fixes a regression in the original fix and hence the regression
potential is the same as the previously SRU'd bug fix for #1747069,
namely:

"Reverting this commit does remove some functionality, however this does
not regress the kernel compared to previous releases and having a
working reliable memory hotplug is the preferred option. This fix does
touch some memory hotplug, so there is a risk that this may break this
functionality that is not covered by the kernel regression testing."

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Colin Ian King (colin-king)
 Status: In Progress

** Changed in: linux (Ubuntu)
   Status: New => In Progress

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772617

Title:
  fix inverted boolean flag in arch_add_memory, reverts back to original
  behaviour

Status in linux package in Ubuntu:
  In Progress

Bug description:
  == SRU Justification, ARTFUL ==

  Bug fix #1761104 incorrectly inverted the flag in the call to 
arch_add_memory, it should be true instead of false.
  == Fix ==

  Fix partial backport from bug #1747069, remove can_online_high_movable
  and fix the incorrectly set boolean argument to arch_add_memory().
  NVIDIA are reported that this is was incorrectly flipped in the last
  SRU to fix their driver support on powerpc.

  == Testing ==

  run ADT memory hotplug test, should not regress this. Without the fix,
  the nvidia driver on powerpc will not work. With the fix it loads and
  works.

  == Regression Potential ==

  This fixes a regression in the original fix and hence the regression
  potential is the same as the previously SRU'd bug fix for #1747069,
  namely:

  "Reverting this commit does remove some functionality, however this
  does not regress the kernel compared to previous releases and having a
  working reliable memory hotplug is the preferred option. This fix does
  touch some memory hotplug, so there is a risk that this may break this
  functionality that is not covered by the kernel regression testing."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772617/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772610] Re: Adding back alx WoL feature

2018-05-22 Thread AceLan Kao

** Description changed:

  [Impact]
  The WoL feature is a must to pass Energy Star 6.1 and above,
  the power consumption will be measured during S3 with WoL is enabled.
  
  [Test case]
  Verified pass on new Dell machines without the wake up issue.
  
  [Regression potential]
  No regression.
  We disable this feature by default, so the driver behavior will be the same. 
We'll leave this feature disabled by default before we can fix the 
unintentional wake up issue.
+ 
+ [Misc]
+ Upstream maintainer insists to fix the wake up issue before we can add this 
feature back to the driver, so make the patch in Ubuntu only.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772610

Title:
  Adding back alx WoL feature

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  The WoL feature is a must to pass Energy Star 6.1 and above,
  the power consumption will be measured during S3 with WoL is enabled.

  [Test case]
  Verified pass on new Dell machines without the wake up issue.

  [Regression potential]
  No regression.
  We disable this feature by default, so the driver behavior will be the same. 
We'll leave this feature disabled by default before we can fix the 
unintentional wake up issue.

  [Misc]
  Upstream maintainer insists to fix the wake up issue before we can add this 
feature back to the driver, so make the patch in Ubuntu only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772610/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

2018-05-22 Thread Antoine Pitrou

According at least to http://blog.programster.org/stabilizing-
ubuntu-16-04-on-ryzen, 18.04 is supposed to be ok.  I haven't upgraded
yet myself.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1772610] [NEW] Adding back alx WoL feature

2018-05-22 Thread AceLan Kao

Public bug reported:

[Impact]
The WoL feature is a must to pass Energy Star 6.1 and above,
the power consumption will be measured during S3 with WoL is enabled.

[Test case]
Verified pass on new Dell machines without the wake up issue.

[Regression potential]
No regression.
We disable this feature by default, so the driver behavior will be the same. 
We'll leave this feature disabled by default before we can fix the 
unintentional wake up issue.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772610

Title:
  Adding back alx WoL feature

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  The WoL feature is a must to pass Energy Star 6.1 and above,
  the power consumption will be measured during S3 with WoL is enabled.

  [Test case]
  Verified pass on new Dell machines without the wake up issue.

  [Regression potential]
  No regression.
  We disable this feature by default, so the driver behavior will be the same. 
We'll leave this feature disabled by default before we can fix the 
unintentional wake up issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772610/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

2018-05-22 Thread Mario Emmenlauer

Is it known if 18.04 has the patches active to support ryzen out of the
box? I have upgraded to 18.04 recently and the system has just hung for
the first time in many months. I wonder if this is by chance or if other
people experienced the same?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)

[Kernel-packages] [Bug 1742658] Re: linux-generic-hwe-16.04 OOPS in nouveau after security update

2018-05-22 Thread Daniel Axtens

Hi,

I have a report from another user reporting this. I will submit it to
the kernel team.

Regards,
Daniel

** 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/1742658

Title:
  linux-generic-hwe-16.04 OOPS in nouveau after security update

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-hwe-edge package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  After upgrading linux-generic-hwe-16.04 to 4.13.0.26.46 I get a black screen 
with nouveau.
  Previously I was running 4.10.0-42-generic, and that kernel still works fine.

  Here is the OOPS:

  an 11 09:39:18 edvin-tower kernel: [3.079986] [drm] Initialized nouveau 
1.3.1 20120801 for :02:00.0 on minor 0
  Jan 11 09:39:18 edvin-tower kernel: [3.100591] BUG: unable to handle 
kernel NULL pointer dereference at   (null)
  Jan 11 09:39:18 edvin-tower kernel: [3.100606] IP:   (null)
  Jan 11 09:39:18 edvin-tower kernel: [3.100610] PGD 0 
  Jan 11 09:39:18 edvin-tower kernel: [3.100611] P4D 0 
  Jan 11 09:39:18 edvin-tower kernel: [3.100615] 
  Jan 11 09:39:18 edvin-tower kernel: [3.100620] Oops: 0010 [#1] SMP PTI
  Jan 11 09:39:18 edvin-tower kernel: [3.100623] Modules linked in: 
hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect e1000e sysimgblt fb_sys_fops drm ptp ahci pps_core 
pata_acpi libahci wmi
  Jan 11 09:39:18 edvin-tower kernel: [3.100643] CPU: 4 PID: 238 Comm: 
kworker/u16:7 Not tainted 4.13.0-26-generic #29~16.04.2-Ubuntu
  Jan 11 09:39:18 edvin-tower kernel: [3.100649] Hardware name: Dell Inc. 
Precision Tower 5810/0K240Y, BIOS A05 12/16/2014
  Jan 11 09:39:18 edvin-tower kernel: [3.100688] Workqueue: nvkm-disp 
gf119_disp_super [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100694] task: 9d8982d25d00 
task.stack: ac9ec2134000
  Jan 11 09:39:18 edvin-tower kernel: [3.100698] RIP: 0010:  (null)
  Jan 11 09:39:18 edvin-tower kernel: [3.100701] RSP: 0018:ac9ec2137bd8 
EFLAGS: 00010206
  Jan 11 09:39:18 edvin-tower kernel: [3.100706] RAX: c0416f20 RBX: 
 RCX: 0016
  Jan 11 09:39:18 edvin-tower kernel: [3.100710] RDX:  RSI: 
 RDI: 9d898140d180
  Jan 11 09:39:18 edvin-tower kernel: [3.100715] RBP: ac9ec2137c70 R08: 
 R09: 
  Jan 11 09:39:18 edvin-tower kernel: [3.100719] R10: 1000 R11: 
 R12: 
  Jan 11 09:39:18 edvin-tower kernel: [3.100724] R13:  R14: 
ac9ec2137d00 R15: 9d898c542600
  Jan 11 09:39:18 edvin-tower kernel: [3.100728] FS:  
() GS:9d899fd0() knlGS:
  Jan 11 09:39:18 edvin-tower kernel: [3.100733] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan 11 09:39:18 edvin-tower kernel: [3.100737] CR2:  CR3: 
00029ac0a006 CR4: 001606e0
  Jan 11 09:39:18 edvin-tower kernel: [3.100742] Call Trace:
  Jan 11 09:39:18 edvin-tower kernel: [3.100771]  ? 
nvkm_dp_train_drive+0x214/0x300 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100798]  nvkm_dp_train+0x582/0x970 
[nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100824]  
nvkm_dp_acquire+0xd4/0x390 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100850]  
nv50_disp_super_2_2+0x6d/0x430 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100872]  ? 
nvkm_devinit_pll_set+0xf/0x20 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100897]  
gf119_disp_super+0x1b7/0x300 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100904]  ? __schedule+0x3ca/0x890
  Jan 11 09:39:18 edvin-tower kernel: [3.100911]  
process_one_work+0x156/0x410
  Jan 11 09:39:18 edvin-tower kernel: [3.100915]  worker_thread+0x4b/0x460
  Jan 11 09:39:18 edvin-tower kernel: [3.100920]  kthread+0x109/0x140
  Jan 11 09:39:18 edvin-tower kernel: [3.100924]  ? 
process_one_work+0x410/0x410
  Jan 11 09:39:18 edvin-tower kernel: [3.100928]  ? 
kthread_create_on_node+0x70/0x70
  Jan 11 09:39:18 edvin-tower kernel: [3.100934]  ret_from_fork+0x1f/0x30
  Jan 11 09:39:18 edvin-tower kernel: [3.100938] Code:  Bad RIP value.
  Jan 11 09:39:18 edvin-tower kernel: [3.100944] RIP:   (null) RSP: 
ac9ec2137bd8
  Jan 11 09:39:18 edvin-tower kernel: [3.100948] CR2: 
  Jan 11 09:39:18 edvin-tower kernel: [3.100952] ---[ end trace 
93a79dae0d3ec749 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic-hwe-16.04

[Kernel-packages] [Bug 1742658] Missing required logs.

2018-05-22 Thread Ubuntu Kernel Bot

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 1742658

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/1742658

Title:
  linux-generic-hwe-16.04 OOPS in nouveau after security update

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-hwe-edge package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  After upgrading linux-generic-hwe-16.04 to 4.13.0.26.46 I get a black screen 
with nouveau.
  Previously I was running 4.10.0-42-generic, and that kernel still works fine.

  Here is the OOPS:

  an 11 09:39:18 edvin-tower kernel: [3.079986] [drm] Initialized nouveau 
1.3.1 20120801 for :02:00.0 on minor 0
  Jan 11 09:39:18 edvin-tower kernel: [3.100591] BUG: unable to handle 
kernel NULL pointer dereference at   (null)
  Jan 11 09:39:18 edvin-tower kernel: [3.100606] IP:   (null)
  Jan 11 09:39:18 edvin-tower kernel: [3.100610] PGD 0 
  Jan 11 09:39:18 edvin-tower kernel: [3.100611] P4D 0 
  Jan 11 09:39:18 edvin-tower kernel: [3.100615] 
  Jan 11 09:39:18 edvin-tower kernel: [3.100620] Oops: 0010 [#1] SMP PTI
  Jan 11 09:39:18 edvin-tower kernel: [3.100623] Modules linked in: 
hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect e1000e sysimgblt fb_sys_fops drm ptp ahci pps_core 
pata_acpi libahci wmi
  Jan 11 09:39:18 edvin-tower kernel: [3.100643] CPU: 4 PID: 238 Comm: 
kworker/u16:7 Not tainted 4.13.0-26-generic #29~16.04.2-Ubuntu
  Jan 11 09:39:18 edvin-tower kernel: [3.100649] Hardware name: Dell Inc. 
Precision Tower 5810/0K240Y, BIOS A05 12/16/2014
  Jan 11 09:39:18 edvin-tower kernel: [3.100688] Workqueue: nvkm-disp 
gf119_disp_super [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100694] task: 9d8982d25d00 
task.stack: ac9ec2134000
  Jan 11 09:39:18 edvin-tower kernel: [3.100698] RIP: 0010:  (null)
  Jan 11 09:39:18 edvin-tower kernel: [3.100701] RSP: 0018:ac9ec2137bd8 
EFLAGS: 00010206
  Jan 11 09:39:18 edvin-tower kernel: [3.100706] RAX: c0416f20 RBX: 
 RCX: 0016
  Jan 11 09:39:18 edvin-tower kernel: [3.100710] RDX:  RSI: 
 RDI: 9d898140d180
  Jan 11 09:39:18 edvin-tower kernel: [3.100715] RBP: ac9ec2137c70 R08: 
 R09: 
  Jan 11 09:39:18 edvin-tower kernel: [3.100719] R10: 1000 R11: 
 R12: 
  Jan 11 09:39:18 edvin-tower kernel: [3.100724] R13:  R14: 
ac9ec2137d00 R15: 9d898c542600
  Jan 11 09:39:18 edvin-tower kernel: [3.100728] FS:  
() GS:9d899fd0() knlGS:
  Jan 11 09:39:18 edvin-tower kernel: [3.100733] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan 11 09:39:18 edvin-tower kernel: [3.100737] CR2:  CR3: 
00029ac0a006 CR4: 001606e0
  Jan 11 09:39:18 edvin-tower kernel: [3.100742] Call Trace:
  Jan 11 09:39:18 edvin-tower kernel: [3.100771]  ? 
nvkm_dp_train_drive+0x214/0x300 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100798]  nvkm_dp_train+0x582/0x970 
[nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100824]  
nvkm_dp_acquire+0xd4/0x390 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100850]  
nv50_disp_super_2_2+0x6d/0x430 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100872]  ? 
nvkm_devinit_pll_set+0xf/0x20 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100897]  
gf119_disp_super+0x1b7/0x300 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100904]  ? __schedule+0x3ca/0x890
  Jan 11 09:39:18 edvin-tower kernel: [3.100911]  
process_one_work+0x156/0x410
  Jan 11 09:39:18 edvin-tower kernel: [3.100915]  worker_thread+0x4b/0x460
  Jan 11 09:39:18 edvin-tower kernel: [3.100920]  kthread+0x109/0x140
  Jan 11 09:39:18 edvin-tower kernel: [3.100924]  ? 
process_one_work+0x410/0x410
  Jan 11 09:39:18 edvin-tower kernel: [3.100928]  ? 
kthread_create_on_node+0x70/0x70
  Jan 11 09:39:18 edvin-tower kernel: [3.100934]  ret_from_fork+0x1f/0x30

[Kernel-packages] [Bug 1742658] Re: linux-generic-hwe-16.04 OOPS in nouveau after security update

2018-05-22 Thread Daniel Axtens

** 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/1742658

Title:
  linux-generic-hwe-16.04 OOPS in nouveau after security update

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-hwe-edge package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  After upgrading linux-generic-hwe-16.04 to 4.13.0.26.46 I get a black screen 
with nouveau.
  Previously I was running 4.10.0-42-generic, and that kernel still works fine.

  Here is the OOPS:

  an 11 09:39:18 edvin-tower kernel: [3.079986] [drm] Initialized nouveau 
1.3.1 20120801 for :02:00.0 on minor 0
  Jan 11 09:39:18 edvin-tower kernel: [3.100591] BUG: unable to handle 
kernel NULL pointer dereference at   (null)
  Jan 11 09:39:18 edvin-tower kernel: [3.100606] IP:   (null)
  Jan 11 09:39:18 edvin-tower kernel: [3.100610] PGD 0 
  Jan 11 09:39:18 edvin-tower kernel: [3.100611] P4D 0 
  Jan 11 09:39:18 edvin-tower kernel: [3.100615] 
  Jan 11 09:39:18 edvin-tower kernel: [3.100620] Oops: 0010 [#1] SMP PTI
  Jan 11 09:39:18 edvin-tower kernel: [3.100623] Modules linked in: 
hid_generic usbhid hid nouveau mxm_wmi video i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect e1000e sysimgblt fb_sys_fops drm ptp ahci pps_core 
pata_acpi libahci wmi
  Jan 11 09:39:18 edvin-tower kernel: [3.100643] CPU: 4 PID: 238 Comm: 
kworker/u16:7 Not tainted 4.13.0-26-generic #29~16.04.2-Ubuntu
  Jan 11 09:39:18 edvin-tower kernel: [3.100649] Hardware name: Dell Inc. 
Precision Tower 5810/0K240Y, BIOS A05 12/16/2014
  Jan 11 09:39:18 edvin-tower kernel: [3.100688] Workqueue: nvkm-disp 
gf119_disp_super [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100694] task: 9d8982d25d00 
task.stack: ac9ec2134000
  Jan 11 09:39:18 edvin-tower kernel: [3.100698] RIP: 0010:  (null)
  Jan 11 09:39:18 edvin-tower kernel: [3.100701] RSP: 0018:ac9ec2137bd8 
EFLAGS: 00010206
  Jan 11 09:39:18 edvin-tower kernel: [3.100706] RAX: c0416f20 RBX: 
 RCX: 0016
  Jan 11 09:39:18 edvin-tower kernel: [3.100710] RDX:  RSI: 
 RDI: 9d898140d180
  Jan 11 09:39:18 edvin-tower kernel: [3.100715] RBP: ac9ec2137c70 R08: 
 R09: 
  Jan 11 09:39:18 edvin-tower kernel: [3.100719] R10: 1000 R11: 
 R12: 
  Jan 11 09:39:18 edvin-tower kernel: [3.100724] R13:  R14: 
ac9ec2137d00 R15: 9d898c542600
  Jan 11 09:39:18 edvin-tower kernel: [3.100728] FS:  
() GS:9d899fd0() knlGS:
  Jan 11 09:39:18 edvin-tower kernel: [3.100733] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan 11 09:39:18 edvin-tower kernel: [3.100737] CR2:  CR3: 
00029ac0a006 CR4: 001606e0
  Jan 11 09:39:18 edvin-tower kernel: [3.100742] Call Trace:
  Jan 11 09:39:18 edvin-tower kernel: [3.100771]  ? 
nvkm_dp_train_drive+0x214/0x300 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100798]  nvkm_dp_train+0x582/0x970 
[nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100824]  
nvkm_dp_acquire+0xd4/0x390 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100850]  
nv50_disp_super_2_2+0x6d/0x430 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100872]  ? 
nvkm_devinit_pll_set+0xf/0x20 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100897]  
gf119_disp_super+0x1b7/0x300 [nouveau]
  Jan 11 09:39:18 edvin-tower kernel: [3.100904]  ? __schedule+0x3ca/0x890
  Jan 11 09:39:18 edvin-tower kernel: [3.100911]  
process_one_work+0x156/0x410
  Jan 11 09:39:18 edvin-tower kernel: [3.100915]  worker_thread+0x4b/0x460
  Jan 11 09:39:18 edvin-tower kernel: [3.100920]  kthread+0x109/0x140
  Jan 11 09:39:18 edvin-tower kernel: [3.100924]  ? 
process_one_work+0x410/0x410
  Jan 11 09:39:18 edvin-tower kernel: [3.100928]  ? 
kthread_create_on_node+0x70/0x70
  Jan 11 09:39:18 edvin-tower kernel: [3.100934]  ret_from_fork+0x1f/0x30
  Jan 11 09:39:18 edvin-tower kernel: [3.100938] Code:  Bad RIP value.
  Jan 11 09:39:18 edvin-tower kernel: [3.100944] RIP:   (null) RSP: 
ac9ec2137bd8
  Jan 11 09:39:18 edvin-tower kernel: [3.100948] CR2: 
  Jan 11 09:39:18 edvin-tower kernel: [3.100952] ---[ end trace 
93a79dae0d3ec749 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic-hwe-16.04 4.13.0.26.46
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux

[Kernel-packages] [Bug 1734691] Comment bridged from LTC Bugzilla

--- Comment From heinz-werner_se...@de.ibm.com 2018-05-22 04:11 EDT---
@Qi Ye: by any chance retest possible?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734691

Title:
  Got disk i/o failure when vary cpu offline via chcpu command (Ubuntu
  running on LPAR)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Got disk i/o failure when offline CPU via chcpu command
   
  ---uname output---
  4.4.0-45-generic #66-Ubuntu
   
  Machine Type = z13 - 2964 
   
  ---Debugger---
  A debugger is not configured
   
  Contact Information = y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  -Attach sysctl -a output output to the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1734691/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1754580] Comment bridged from LTC Bugzilla

--- Comment From heinz-werner_se...@de.ibm.com 2018-05-22 04:01 EDT---
IBM Bugzilla status closed; Further updates will be provide via kernel-stable 
releases

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1754580

Title:
  [CVE] Spectre: System Z {kernel} UBUNTU18.04

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Comment will follow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1754580/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772593] Re: cpum_sf: ensure sample freq is non-zero

2018-05-22 Thread Andrew Cloke

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772593

Title:
  cpum_sf: ensure sample freq is non-zero

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Description:  cpum_sf: ensure sample freq is non-zero
  Symptom:  A kernel crash might occur.
  Problem:  An FP divide exception during the sample rate
initialization for the hardware sampling facility.
  Solution: Ensure that the sample frequency of the perf
event attribute is non-zero.
  Reproduction: Run trinity against the perf_event_open() syscall.
  Upstream-ID:  4bbaf2584b86b0772413edeac22ff448f36351b1
  Component: kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772593/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1769077] Re: linux: 3.13.0-148.197 -proposed tracker

** Tags removed: kernel-block-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/1769077

Title:
  linux: 3.13.0-148.197 -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:
  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:
  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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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 1769080 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769077/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1757443] Re: Redpine: BLE radio lost issue

2018-05-22 Thread Shrirang Bagul

After installing 1.173.1 from bionic-proposed:

$ apt list linux-firmware
Listing...
linux-firmware/bionic-proposed,now 1.173.1 all [installed,automatic]
linux-firmware/bionic 1.173 all


Redpine driver reports correct FW revision (1.6.1):

May 22 07:24:36 caracalla kernel: rsi_91x: 

May 22 07:24:36 caracalla kernel: rsi_91x: Firmware file: 
rsi/rs9113_wlan_bt_dual_mode.rps
May 22 07:24:36 caracalla kernel: rsi_91x: Operating mode: 13 [Wi-Fi 
STA + BT DUAL]
May 22 07:24:36 caracalla kernel: rsi_91x: FW Version: 1.6.1
May 22 07:24:36 caracalla kernel: rsi_91x: 

May 22 07:24:36 caracalla kernel: rsi_91x:  RSI Version Info 
==
May 22 07:24:36 caracalla kernel: rsi_91x: 



** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1757443

Title:
  Redpine: BLE radio lost issue

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Triaged
Status in linux-firmware source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Radio stops capturing advertisements after several hours.

  Fix: Updated firmware.

  Test Case: See below.

  Regression Potential: Limited to specific hardware.

  ---

  Below are the steps to replicate the issue

  We are doing continuous BLE scanning and monitoring the advertisements
  from reference device. After long periods of capture (several hours),
  the radio stops capturing advertisements and won't start again until
  we power cycle the box or manually unload/load the module via modprobe

  This bug is for tracking purposes only, please don't triage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757443/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1769077] Re: linux: 3.13.0-148.197 -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-trusty

** Tags removed: block-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/1769077

Title:
  linux: 3.13.0-148.197 -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:
  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:
  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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

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 1769080 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1769077/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772593] [NEW] cpum_sf: ensure sample freq is non-zero

Public bug reported:

Description:  cpum_sf: ensure sample freq is non-zero
Symptom:  A kernel crash might occur.
Problem:  An FP divide exception during the sample rate
  initialization for the hardware sampling facility.
Solution: Ensure that the sample frequency of the perf
  event attribute is non-zero.
Reproduction: Run trinity against the perf_event_open() syscall.
Upstream-ID:  4bbaf2584b86b0772413edeac22ff448f36351b1
Component: kernel

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-168084 severity-high 
targetmilestone-inin16041

** Tags added: architecture-s39064 bugnameltc-168084 severity-high
targetmilestone-inin16041

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772593

Title:
  cpum_sf: ensure sample freq is non-zero

Status in linux package in Ubuntu:
  New

Bug description:
  Description:  cpum_sf: ensure sample freq is non-zero
  Symptom:  A kernel crash might occur.
  Problem:  An FP divide exception during the sample rate
initialization for the hardware sampling facility.
  Solution: Ensure that the sample frequency of the perf
event attribute is non-zero.
  Reproduction: Run trinity against the perf_event_open() syscall.
  Upstream-ID:  4bbaf2584b86b0772413edeac22ff448f36351b1
  Component: kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772593/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772593] [NEW] cpum_sf: ensure sample freq is non-zero

2018-05-22 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Description:  cpum_sf: ensure sample freq is non-zero
Symptom:  A kernel crash might occur.
Problem:  An FP divide exception during the sample rate
  initialization for the hardware sampling facility.
Solution: Ensure that the sample frequency of the perf
  event attribute is non-zero.
Reproduction: Run trinity against the perf_event_open() syscall.
Upstream-ID:  4bbaf2584b86b0772413edeac22ff448f36351b1
Component: kernel

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-168084 severity-high 
targetmilestone-inin16041
-- 
cpum_sf: ensure sample freq is non-zero
https://bugs.launchpad.net/bugs/1772593
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU

2018-05-22 Thread Marcel Schrijvers

Just upgraded from kernel 4.15.0-20-generic => 4.15.0-22-generic - still
the same problem

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1759836

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460

2018-05-22 Thread semreh

Problem still exists in 4.16.10 kernel from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.10/
(#uname -r output is 4.16.10-041610-generic )

dmesg output gives same error output as before when amdgpu.dc=1

 [1.866312] [drm] amdgpu: 1024M of VRAM memory ready
 [1.866316] [drm] amdgpu: 3072M of GTT memory ready.
 [1.866332] [drm] GART: num cpu pages 262144, num gpu pages 262144
 [1.866382] [drm] PCIE GART of 1024M enabled (table at 0x00F40004).
 [1.866500] [drm] Internal thermal controller without fan control
 [1.866504] [drm] amdgpu: dpm initialized
 [1.867685] [drm] Found UVD firmware Version: 1.55 Family ID: 9
 [1.868113] [drm] Found VCE firmware Version: 50.10 Binary ID: 2
 [1.870125] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:3! type 0 expected 3
 [1.870214] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:4! type 0 expected 3
 [1.870337] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:5! type 0 expected 3
 [1.870445] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:6! type 0 expected 3
 [1.880211] [drm] Display Core initialized with v3.1.27!
 [1.887329] [drm] SADs count is: -2, don't need to read it
 [1.887755] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [1.887761] [drm] Driver supports precise vblank timestamp query.
 [1.906232] [drm] UVD initialized successfully.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1761751

Title:
  Black screen on 18.04 + AMD RX460

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1768898] Comment bridged from LTC Bugzilla

--- Comment From mainam...@in.ibm.com 2018-05-22 03:06 EDT---
*** Bug 167467 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1768898

Title:
  smp_call_function_single/many core hangs with stop4 alone

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == SRU Justification ==
  IBM reports that this bug occurs with stop4 which results in soft lockups/rcu 
stalls.
  This is a kernel synchronization issue leading to a dead lock.

  This bug was introduced by commit 7bc54b652f13 in v4.8-rc1.  This
  regression is fixed by mainline commit c0f7f5b6c6910.

  == Fix ==
  c0f7f5b6c6910 ("cpufreq: powernv: Fix hardlockup due to synchronous smp_call 
in timer interrupt")

  == Regression Potential ==
  Low. Fixes current regression.  Cc'd to upstream stable, so it has had
  additon upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  Recently we discovered this bug occurs just alone with stop4 which
  results in soft lockups/rcu stalls.

  ```
  root@ltc-boston125:~# [15523.619395] systemd[1]: systemd-journald.service: 
Processes still around after final SIGKILL. Entering failed mode.
  [15523.619508] systemd[1]: systemd-journald.service: Failed with result 
'timeout'.
  [15523.619769] systemd[1]: Failed to start Journal Service.
  [15523.620618] systemd[1]: systemd-journald.service: Service has no hold-off 
time, scheduling restart.
  [15523.620774] systemd[1]: systemd-journald.service: Scheduled restart job, 
restart counter is at 21.
  [15523.621462] systemd[1]: Stopped Journal Service.
  [15523.621635] systemd[1]: systemd-journald.service: Found left-over process 
1561 (systemd-journal) in control group while starting unit. Ignoring.
  [15523.621756] systemd[1]: This usually indicates unclean termination of a 
previous run, or service implementation deficiencies.
  [15523.621888] systemd[1]: systemd-journald.service: Found left-over process 
69060 (systemd-journal) in control group while starting unit. Ignoring.
  [15523.622029] systemd[1]: This usually indica[15541.629904] INFO: rcu_sched 
self-detected stall on CPU
  [15541.629958]60-: (2 GPs behind) idle=146/142/0 
softirq=300022/300022 fqs=999069
  [15541.630046] (t=2415546 jiffies g=184827 c=184826 q=57111)
  [15541.630101] NMI backtrace for cpu 60
  [15541.630135] CPU: 60 PID: 4810 Comm: tlbie_test Tainted: G L   
4.15.0-15-generic #16-Ubuntu
  [15541.630207] Call Trace:
  [15541.630232] [c000201a1da96b00] [c0ceb35c] dump_stack+0xb0/0xf4 
(unreliable)
  [15541.630298] [c000201a1da96b40] [c0cf4d48] 
nmi_cpu_backtrace+0x1f8/0x200
  [15541.630363] [c000201a1da96bd0] [c0cf4ee8] 
nmi_trigger_cpumask_backtrace+0x198/0x1f0
  [15541.630429] [c000201a1da96c60] [c002f2d8] 
arch_trigger_cpumask_backtrace+0x28/0x40
  [15541.630495] [c000201a1da96c80] [c01a913c] 
rcu_dump_cpu_stacks+0xf4/0x158
  [15541.630560] [c000201a1da96cd0] [c01a81e8] 
rcu_check_callbacks+0x8e8/0xb40
  [15541.630625] [c000201a1da96e00] [c01b64a8] 
update_process_times+0x48/0x90
  [15541.630689] [c000201a1da96e30] [c01ce1f4] 
tick_sched_handle.isra.5+0x34/0xd0
  [15541.630753] [c000201a1da96e60] [c01ce2f0] 
tick_sched_timer+0x60/0xe0
  [15541.630818] [c000201a1da96ea0] [c01b7054] 
__hrtimer_run_queues+0x144/0x370
  [15541.630883] [c000201a1da96f20] [c01b7fac] 
hrtimer_interrupt+0xfc/0x350
  [15541.630948] [c000201a1da96ff0] [c00248f0] 
__timer_interrupt+0x90/0x260
  [15541.631013] [c000201a1da97040] [c0024d08] timer_interrupt+0x98/0xe0
  [15541.631069] [c000201a1da97070] [c0009014] 
decrementer_common+0x114/0x120
  [15541.631135] --- interrupt: 901 at smp_call_function_single+0x134/0x180
  [15541.631135] LR = smp_call_function_single+0x110/0x180
  [15541.631230] [c000201a1da973d0] [c01d55e0] 
smp_call_function_any+0x180/0x250
  [15541.631294] [c000201a1da97430] [c0acd3e8] 
gpstate_timer_handler+0x1e8/0x580
  [15541.631359] [c000201a1da974e0] [c01b46b0] call_timer_fn+0x50/0x1c0
  [15541.631433] [c000201a1da97560] [c01b4958] expire_timers+0x138/0x1f0
  [15541.631488] [c000201a1da975d0] [c01b4bf8] 
run_timer_softirq+0x1e8/0x270
  [15541.631553] [c000201a1da97670] [c0d0d6c8] __do_softirq+0x158/0x3e4
  [15541.631608] [c000201a1da97750] [c0114be8] irq_exit+0xe8/0x120
  [15541.631663] [c000201a1da97770] [c0024d0c] timer_interrupt+0x9c/0xe0
  [15541.631718] [c000201a1da977a0] [c0009014] 
decrementer_common+0x114/0x120
  [15541.631784] --- interrupt: 901 at

[Kernel-packages] [Bug 1510570] Re: Bluetooth LE pairing fail

2018-05-22 Thread Yuan-Chen Cheng

** Changed in: oem-priority
Importance: High => Medium

--
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/1510570

Title:
Bluetooth LE pairing fail

Status in OEM Priority Project:
Confirmed
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Xenial:
Fix Committed

Bug description:
[Impact]

When the Bluetooth adapter is not powered on it is not possible to use
it in normal way. We used to have a hack to force powering on by using
an udev rule but this doe snot work anymore. Luckily the BlueZ has
introduced "AutoEnable" option that makes the stack power on adapters by
itself.

Backporting this to xenial will improve life of the desktop users and
will not require them to hack the solution on their own. The fix itself
uses the well known solution to this problem that is floating around
there for a while.

The upload fixes the bug by enabling the 'AutoEnable' option in the
bluetoothd config file.

[Original Report]

. 15.10 we now have bluez 5 so we can pair BLE devices like the
Microsoft Arc Touch Bluetooth Mouse.

But this pairing doesn't work very well. Mouse is seen but pairing fail.
More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

This is due to udev rule that use "hcitool" to power on device.
Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
instead of udev rules.

here is a commit with this parameter:
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

[Test Case]

On xenial install from ppa:
https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

Now reboot the machine. The BT adapter shall be
powered on.

[Regression Potential]

If things go wrong the adapter will not be powered on after the system
boots up. Therefore while testing please focus on the adapter state,
i.e. powered on or off.

[Other Info]

This fix is included in the development release, see:
http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

[What to upload]

For xenial as in:

) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
)
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772575] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1772575/+attachment/5142718/+files/UdevDb.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/1772575

Title:
  Kernel 4.4 NBD size overflow with image size exceeding 1TB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release 16.04, kernel 4.4.0-124-generic

  There's an issue in kernel's NBD module which prevents some larger images to 
be
  correctly "connected" , largely described here:
  https://github.com/NetworkBlockDevice/nbd/issues/44

  There is a small patch here that was accepted into mainline 4.10:
  https://www.spinics.net/lists/linux-block/msg07060.html

  This is a regression from the previous LTS 3.13 kernel.

  

  Here is a small example of the faulty behaviour:

  # qemu-img create -f qcow2 test.img 1100G
  Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 
lazy_refcounts=off refcount_bits=16
  # qemu-nbd -c /dev/nbd0 test.img
  # blockdev --getsize64 /dev/nbd0
  18446743055802302464

  The correct response would be 1181116006400; this breaks most tools
  and makes the image unusable, e.g.

  # fdisk -l /dev/nbd0
  fdisk: cannot open /dev/nbd0: Invalid argument
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 12:51 seq
   crw-rw 1 root audio 116, 33 May 21 12:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro SYS-1028R-WTR
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_AU:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic 
root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 
net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-backports-modules-4.4.0-124-generic  N/A
   linux-firmware 1.157.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-124-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRW-i
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.10
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: SYS-1028R-WTR
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume

2018-05-22 Thread Woodrow Shen

Ok, thanks. Do I need to remove linux-oem? or you can help me to do it
:)

-- 
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/1771542

Title:
  Suspend to idle: Open lid didn't resume

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and 
then they can't resume the system from opening the lid.

  [Test Case]
  1. echo s2idle | sudo tee /sys/power/mem_sleep
  2. Close the lid
  3. Open the lid

  [Fix]
  According a patch sent to 4.17-rc1, which was not be included before 4.15 
EOL, so we cherry pick the patch to Ubuntu 4.15 kernel.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953

  [Regression Potential]
  Per commit, this change also allows Dells XPS13 9360 blacklisted by commit 
71630b7a832f to use the power button for waking up from suspend-to-idle, no 
regression could be happened

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1771542/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1685442] Re: Errors: flip_done timed out during boot-up; slow boot

2018-05-22 Thread Kai Kasurinen

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=93782
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1685442

Title:
  Errors:  flip_done timed out  during boot-up; slow boot

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had been running Ubuntu 16.04 LTS on many laptop computers
  (especially Dell D620, D630, E6400) with no problem.

  I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell
  D630.  It was very slow to boot up (about 90 seconds) as opposed to
  the 30-45 seconds it usually takes. For a few seconds there were error
  messages that included the phrase "flip_done timed out".

  When the Ubuntu desktop appeared, the mouse cursor hung for a while,
  but then came back to life. I didn't do much testing from there.  I
  did a Live session with the 16.04.2 LTS  on a different D630 laptop,
  and the same problem occureed.

  I Googled the problem, and found several hits.
  -
  On an Arch forum, someone reported the problem on a Dell D630, like mine. It 
also occured on other laptops:
  https://bbs.archlinux.org/viewtopic.php?id=218581

  The suggestion was that the bug was related to kernel version 4.8.x
  and the 965GM chipset, which is what the D630 has.

  So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the 
problem DID NOT occur.
  ---
  For a similar boot-up problem, Ubuntu Forum suggested going back to an 
earlier version of Ubuntu.
  https://ubuntuforums.org/showthread.php?t=2348892

  I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and
  the problem did NOT occur.

  So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather 
than 16.04.2.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  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-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  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-4.8.0-36-generic N/A

[Kernel-packages] [Bug 1772575] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1772575/+attachment/5142717/+files/ProcModules.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/1772575

Title:
  Kernel 4.4 NBD size overflow with image size exceeding 1TB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release 16.04, kernel 4.4.0-124-generic

  There's an issue in kernel's NBD module which prevents some larger images to 
be
  correctly "connected" , largely described here:
  https://github.com/NetworkBlockDevice/nbd/issues/44

  There is a small patch here that was accepted into mainline 4.10:
  https://www.spinics.net/lists/linux-block/msg07060.html

  This is a regression from the previous LTS 3.13 kernel.

  

  Here is a small example of the faulty behaviour:

  # qemu-img create -f qcow2 test.img 1100G
  Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 
lazy_refcounts=off refcount_bits=16
  # qemu-nbd -c /dev/nbd0 test.img
  # blockdev --getsize64 /dev/nbd0
  18446743055802302464

  The correct response would be 1181116006400; this breaks most tools
  and makes the image unusable, e.g.

  # fdisk -l /dev/nbd0
  fdisk: cannot open /dev/nbd0: Invalid argument
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 12:51 seq
   crw-rw 1 root audio 116, 33 May 21 12:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro SYS-1028R-WTR
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_AU:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic 
root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 
net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-backports-modules-4.4.0-124-generic  N/A
   linux-firmware 1.157.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-124-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRW-i
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.10
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: SYS-1028R-WTR
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772575] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1772575/+attachment/5142716/+files/ProcInterrupts.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/1772575

Title:
  Kernel 4.4 NBD size overflow with image size exceeding 1TB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release 16.04, kernel 4.4.0-124-generic

  There's an issue in kernel's NBD module which prevents some larger images to 
be
  correctly "connected" , largely described here:
  https://github.com/NetworkBlockDevice/nbd/issues/44

  There is a small patch here that was accepted into mainline 4.10:
  https://www.spinics.net/lists/linux-block/msg07060.html

  This is a regression from the previous LTS 3.13 kernel.

  

  Here is a small example of the faulty behaviour:

  # qemu-img create -f qcow2 test.img 1100G
  Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 
lazy_refcounts=off refcount_bits=16
  # qemu-nbd -c /dev/nbd0 test.img
  # blockdev --getsize64 /dev/nbd0
  18446743055802302464

  The correct response would be 1181116006400; this breaks most tools
  and makes the image unusable, e.g.

  # fdisk -l /dev/nbd0
  fdisk: cannot open /dev/nbd0: Invalid argument
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 12:51 seq
   crw-rw 1 root audio 116, 33 May 21 12:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro SYS-1028R-WTR
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_AU:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic 
root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 
net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-backports-modules-4.4.0-124-generic  N/A
   linux-firmware 1.157.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-124-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRW-i
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.10
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: SYS-1028R-WTR
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772575] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1772575/+attachment/5142713/+files/Lspci.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/1772575

Title:
  Kernel 4.4 NBD size overflow with image size exceeding 1TB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release 16.04, kernel 4.4.0-124-generic

  There's an issue in kernel's NBD module which prevents some larger images to 
be
  correctly "connected" , largely described here:
  https://github.com/NetworkBlockDevice/nbd/issues/44

  There is a small patch here that was accepted into mainline 4.10:
  https://www.spinics.net/lists/linux-block/msg07060.html

  This is a regression from the previous LTS 3.13 kernel.

  

  Here is a small example of the faulty behaviour:

  # qemu-img create -f qcow2 test.img 1100G
  Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 
lazy_refcounts=off refcount_bits=16
  # qemu-nbd -c /dev/nbd0 test.img
  # blockdev --getsize64 /dev/nbd0
  18446743055802302464

  The correct response would be 1181116006400; this breaks most tools
  and makes the image unusable, e.g.

  # fdisk -l /dev/nbd0
  fdisk: cannot open /dev/nbd0: Invalid argument
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 12:51 seq
   crw-rw 1 root audio 116, 33 May 21 12:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro SYS-1028R-WTR
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_AU:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic 
root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 
net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-backports-modules-4.4.0-124-generic  N/A
   linux-firmware 1.157.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-124-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRW-i
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.10
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: SYS-1028R-WTR
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772575] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1772575/+attachment/5142711/+files/CurrentDmesg.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/1772575

Title:
  Kernel 4.4 NBD size overflow with image size exceeding 1TB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release 16.04, kernel 4.4.0-124-generic

  There's an issue in kernel's NBD module which prevents some larger images to 
be
  correctly "connected" , largely described here:
  https://github.com/NetworkBlockDevice/nbd/issues/44

  There is a small patch here that was accepted into mainline 4.10:
  https://www.spinics.net/lists/linux-block/msg07060.html

  This is a regression from the previous LTS 3.13 kernel.

  

  Here is a small example of the faulty behaviour:

  # qemu-img create -f qcow2 test.img 1100G
  Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 
lazy_refcounts=off refcount_bits=16
  # qemu-nbd -c /dev/nbd0 test.img
  # blockdev --getsize64 /dev/nbd0
  18446743055802302464

  The correct response would be 1181116006400; this breaks most tools
  and makes the image unusable, e.g.

  # fdisk -l /dev/nbd0
  fdisk: cannot open /dev/nbd0: Invalid argument
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 12:51 seq
   crw-rw 1 root audio 116, 33 May 21 12:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro SYS-1028R-WTR
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_AU:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic 
root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 
net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-backports-modules-4.4.0-124-generic  N/A
   linux-firmware 1.157.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-124-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRW-i
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.10
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: SYS-1028R-WTR
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772575] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1772575/+attachment/5142714/+files/Lsusb.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/1772575

Title:
  Kernel 4.4 NBD size overflow with image size exceeding 1TB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release 16.04, kernel 4.4.0-124-generic

  There's an issue in kernel's NBD module which prevents some larger images to 
be
  correctly "connected" , largely described here:
  https://github.com/NetworkBlockDevice/nbd/issues/44

  There is a small patch here that was accepted into mainline 4.10:
  https://www.spinics.net/lists/linux-block/msg07060.html

  This is a regression from the previous LTS 3.13 kernel.

  

  Here is a small example of the faulty behaviour:

  # qemu-img create -f qcow2 test.img 1100G
  Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 
lazy_refcounts=off refcount_bits=16
  # qemu-nbd -c /dev/nbd0 test.img
  # blockdev --getsize64 /dev/nbd0
  18446743055802302464

  The correct response would be 1181116006400; this breaks most tools
  and makes the image unusable, e.g.

  # fdisk -l /dev/nbd0
  fdisk: cannot open /dev/nbd0: Invalid argument
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 12:51 seq
   crw-rw 1 root audio 116, 33 May 21 12:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro SYS-1028R-WTR
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_AU:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic 
root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 
net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-backports-modules-4.4.0-124-generic  N/A
   linux-firmware 1.157.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-124-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRW-i
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.10
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: SYS-1028R-WTR
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772467] Re: Driver iwlwifi for Intel Wireless-AC 9560 is slow and unreliable in kernel 4.15.0-20-generic

2018-05-22 Thread David Bogner

apport information

** Description changed:

  This is a hardware specific issue with Ubuntu 18.04 and kernel
  4.15.0-20-generic. The driver for the Intel AC 9560 wireless chip causes
  the problem. Driver location:
  https://www.intel.com/content/www/us/en/support/articles/05511
  /network-and-i-o/wireless-networking.html
  
  The wifi connection is very slow (1MB instead of 100MB possible download
  speed, upload speed is normal) and is also very unreliable.
  
  When installing the 4.16 kernel from mainline kernel
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/ the described
  problem is solved.
  
  Sytem data:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Package:
  4.15.0-20-generic
  driver=iwlwifi driverversion=4.15.0-20-generic firmware=34.0.0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1729 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-19 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer Swift SF114-32
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=39ea17c1-4c91-45ac-81a7-401583763b21 ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/02/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.name: Sapporo_GL
  dmi.board.vendor: GLK
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd05/02/2018:svnAcer:pnSwiftSF114-32:pvrV1.03:rvnGLK:rnSapporo_GL:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.family: Swift 1
  dmi.product.name: Swift SF114-32
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-05-19 (2 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_AT.UTF-8
+  SHELL=/bin/bash
+ Tags:  bionic
+ Uname: Linux 4.15.18-041518-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1772467/+attachment/5142709/+files/ProcCpuinfoMinimal.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/1772467

Title:
  Driver iwlwifi for Intel Wireless-AC 9560 is slow and unreliable in
  kernel 4.15.0-20-generic

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  This is a hardware specific issue with Ubuntu 18.04 and kernel
  4.15.0-20-generic. The driver for the Intel AC 9560 wireless chip
  causes the problem. Driver location:
  https://www.intel.com/content/www/us/en/support/articles/05511
  /network-and-i-o/wireless-networking.html

  The wifi connection is very slow (1MB instead of 100MB possible
  download speed, upload speed is normal) and is also very unreliable.

  When installing the 4.16 kernel from mainline kernel
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/ the described
  problem is solved.

  Sytem data:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Package:
  4.15.0-20-generic
  driver=iwlwifi driverversion=4.15.0-20-generic firmware=34.0.0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1729 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-19 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer Swift SF114-32
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0

[Kernel-packages] [Bug 1772575] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1772575/+attachment/5142715/+files/ProcCpuinfoMinimal.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/1772575

Title:
  Kernel 4.4 NBD size overflow with image size exceeding 1TB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release 16.04, kernel 4.4.0-124-generic

  There's an issue in kernel's NBD module which prevents some larger images to 
be
  correctly "connected" , largely described here:
  https://github.com/NetworkBlockDevice/nbd/issues/44

  There is a small patch here that was accepted into mainline 4.10:
  https://www.spinics.net/lists/linux-block/msg07060.html

  This is a regression from the previous LTS 3.13 kernel.

  

  Here is a small example of the faulty behaviour:

  # qemu-img create -f qcow2 test.img 1100G
  Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 
lazy_refcounts=off refcount_bits=16
  # qemu-nbd -c /dev/nbd0 test.img
  # blockdev --getsize64 /dev/nbd0
  18446743055802302464

  The correct response would be 1181116006400; this breaks most tools
  and makes the image unusable, e.g.

  # fdisk -l /dev/nbd0
  fdisk: cannot open /dev/nbd0: Invalid argument
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 12:51 seq
   crw-rw 1 root audio 116, 33 May 21 12:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro SYS-1028R-WTR
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_AU:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic 
root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 
net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-backports-modules-4.4.0-124-generic  N/A
   linux-firmware 1.157.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-124-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRW-i
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.10
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: SYS-1028R-WTR
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772575] HookError_generic.txt

apport information

** Attachment added: "HookError_generic.txt"
   
https://bugs.launchpad.net/bugs/1772575/+attachment/5142712/+files/HookError_generic.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/1772575

Title:
  Kernel 4.4 NBD size overflow with image size exceeding 1TB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release 16.04, kernel 4.4.0-124-generic

  There's an issue in kernel's NBD module which prevents some larger images to 
be
  correctly "connected" , largely described here:
  https://github.com/NetworkBlockDevice/nbd/issues/44

  There is a small patch here that was accepted into mainline 4.10:
  https://www.spinics.net/lists/linux-block/msg07060.html

  This is a regression from the previous LTS 3.13 kernel.

  

  Here is a small example of the faulty behaviour:

  # qemu-img create -f qcow2 test.img 1100G
  Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 
lazy_refcounts=off refcount_bits=16
  # qemu-nbd -c /dev/nbd0 test.img
  # blockdev --getsize64 /dev/nbd0
  18446743055802302464

  The correct response would be 1181116006400; this breaks most tools
  and makes the image unusable, e.g.

  # fdisk -l /dev/nbd0
  fdisk: cannot open /dev/nbd0: Invalid argument
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 12:51 seq
   crw-rw 1 root audio 116, 33 May 21 12:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro SYS-1028R-WTR
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_AU:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic 
root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 
net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-backports-modules-4.4.0-124-generic  N/A
   linux-firmware 1.157.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-124-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRW-i
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.10
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: SYS-1028R-WTR
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772467] Re: Driver iwlwifi for Intel Wireless-AC 9560 is slow and unreliable in kernel 4.15.0-20-generic

2018-05-22 Thread David Bogner

The latest upstream 4.15.18 kernel solves stability. I can now finish
downloads with git fetch. But download speed still is very slow.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772467

Title:
  Driver iwlwifi for Intel Wireless-AC 9560 is slow and unreliable in
  kernel 4.15.0-20-generic

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  This is a hardware specific issue with Ubuntu 18.04 and kernel
  4.15.0-20-generic. The driver for the Intel AC 9560 wireless chip
  causes the problem. Driver location:
  https://www.intel.com/content/www/us/en/support/articles/05511
  /network-and-i-o/wireless-networking.html

  The wifi connection is very slow (1MB instead of 100MB possible
  download speed, upload speed is normal) and is also very unreliable.

  When installing the 4.16 kernel from mainline kernel
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/ the described
  problem is solved.

  Sytem data:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Package:
  4.15.0-20-generic
  driver=iwlwifi driverversion=4.15.0-20-generic firmware=34.0.0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1729 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-19 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer Swift SF114-32
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=39ea17c1-4c91-45ac-81a7-401583763b21 ro quiet splash vt.handoff=1
  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
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/02/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.name: Sapporo_GL
  dmi.board.vendor: GLK
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd05/02/2018:svnAcer:pnSwiftSF114-32:pvrV1.03:rvnGLK:rnSapporo_GL:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.family: Swift 1
  dmi.product.name: Swift SF114-32
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-19 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.15.18-041518-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772467/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772575] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1772575/+attachment/5142719/+files/WifiSyslog.txt

** 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/1772575

Title:
  Kernel 4.4 NBD size overflow with image size exceeding 1TB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release 16.04, kernel 4.4.0-124-generic

  There's an issue in kernel's NBD module which prevents some larger images to 
be
  correctly "connected" , largely described here:
  https://github.com/NetworkBlockDevice/nbd/issues/44

  There is a small patch here that was accepted into mainline 4.10:
  https://www.spinics.net/lists/linux-block/msg07060.html

  This is a regression from the previous LTS 3.13 kernel.

  

  Here is a small example of the faulty behaviour:

  # qemu-img create -f qcow2 test.img 1100G
  Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 
lazy_refcounts=off refcount_bits=16
  # qemu-nbd -c /dev/nbd0 test.img
  # blockdev --getsize64 /dev/nbd0
  18446743055802302464

  The correct response would be 1181116006400; this breaks most tools
  and makes the image unusable, e.g.

  # fdisk -l /dev/nbd0
  fdisk: cannot open /dev/nbd0: Invalid argument
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 12:51 seq
   crw-rw 1 root audio 116, 33 May 21 12:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro SYS-1028R-WTR
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_AU:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic 
root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 
net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-124-generic N/A
   linux-backports-modules-4.4.0-124-generic  N/A
   linux-firmware 1.157.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-124-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10DRW-i
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.10
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: SYS-1028R-WTR
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772575/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1772575] Re: Kernel 4.4 NBD size overflow with image size exceeding 1TB

apport information

** Tags added: apport-collected xenial

** Description changed:

  Release 16.04, kernel 4.4.0-124-generic
  
  There's an issue in kernel's NBD module which prevents some larger images to 
be
  correctly "connected" , largely described here:
  https://github.com/NetworkBlockDevice/nbd/issues/44
  
  There is a small patch here that was accepted into mainline 4.10:
  https://www.spinics.net/lists/linux-block/msg07060.html
  
  This is a regression from the previous LTS 3.13 kernel.
  
  
  
  Here is a small example of the faulty behaviour:
  
  # qemu-img create -f qcow2 test.img 1100G
  Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 
lazy_refcounts=off refcount_bits=16
  # qemu-nbd -c /dev/nbd0 test.img
  # blockdev --getsize64 /dev/nbd0
  18446743055802302464
  
  The correct response would be 1181116006400; this breaks most tools and
  makes the image unusable, e.g.
  
  # fdisk -l /dev/nbd0
  fdisk: cannot open /dev/nbd0: Invalid argument
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 May 21 12:51 seq
+  crw-rw 1 root audio 116, 33 May 21 12:51 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.17
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=/dev/mapper/VolGroup00-swap_1
+ IwConfig: Error: [Errno 2] No such file or directory
+ MachineType: Supermicro SYS-1028R-WTR
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  LANGUAGE=en_AU:
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_AU
+  SHELL=/bin/bash
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-124-generic 
root=/dev/mapper/VolGroup00-root ro nomodeset elevator=noop consoleblank=0 
net.ifnames=0 biosdevname=0 modprobe.blacklist=igb nosplash quiet
+ ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-124-generic N/A
+  linux-backports-modules-4.4.0-124-generic  N/A
+  linux-firmware 1.157.18
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial xenial
+ Uname: Linux 4.4.0-124-generic x86_64
+ UnreportableReason: The report belongs to a package that is not installed.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: False
+ dmi.bios.date: 02/08/2018
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 3.0a
+ dmi.board.asset.tag: Default string
+ dmi.board.name: X10DRW-i
+ dmi.board.vendor: Supermicro
+ dmi.board.version: 1.10
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Supermicro
+ dmi.chassis.version: 0123456789
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd02/08/2018:svnSupermicro:pnSYS-1028R-WTR:pvr0123456789:rvnSupermicro:rnX10DRW-i:rvr1.10:cvnSupermicro:ct1:cvr0123456789:
+ dmi.product.name: SYS-1028R-WTR
+ dmi.product.version: 0123456789
+ dmi.sys.vendor: Supermicro

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1772575/+attachment/5142710/+files/CRDA.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/1772575

Title:
  Kernel 4.4 NBD size overflow with image size exceeding 1TB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release 16.04, kernel 4.4.0-124-generic

  There's an issue in kernel's NBD module which prevents some larger images to 
be
  correctly "connected" , largely described here:
  https://github.com/NetworkBlockDevice/nbd/issues/44

  There is a small patch here that was accepted into mainline 4.10:
  https://www.spinics.net/lists/linux-block/msg07060.html

  This is a regression from the previous LTS 3.13 kernel.

  

  Here is a small example of the faulty behaviour:

  # qemu-img create -f qcow2 test.img 1100G
  Formatting 'test.img', fmt=qcow2 size=1181116006400 cluster_size=65536 
lazy_refcounts=off refcount_bits=16
  # qemu-nbd -c /dev/nbd0 test.img
  # blockdev --getsize64 /dev/nbd0
  18446743055802302464

  The correct response would be 1181116006400; this breaks most tools
  and makes the image unusable, e.g.

  # fdisk -l /dev/nbd0
  fdisk: cannot open /dev/nbd0: Invalid argument
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 21 12:51 seq
   crw-rw 1 root audio 116, 33 May 21 12:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice:

[Kernel-packages] [Bug 1771780] Comment bridged from LTC Bugzilla