[Kernel-packages] [Bug 1657112] s2lp4 (s390x.LPAR) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp4__4.8.0-36.38__2017-01-20_07-42-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1657112] modoc (ppc64el) - tests ran: 141, failed: 0

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/modoc__4.8.0-36.38__2017-01-20_07-02-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1657994] Status changed to Confirmed

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Regression:  HDMI audio produces no sound (Skylake NUC)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from Xenial 16.04 to Yakkety 16.10, playing audio over HDMI no 
longer produces sound.
  * When booting with old kernel from Xenial (4.4.0-59), HDMI audio works fine
  * Audio from headphone jack works fine
  * Userspace seems to be happily playing to HDMI audio device, but no sound 
produced at HDMI sink (Samsung TV)

  Any of a wide range of pre-built mainline kernels fail to produce HDMI
  audio, but with a different failure mode (HDMI audio does not seem to
  be enumerated in the same way as in the Ubuntu kernels.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  israel 1973 F pulseaudio
   /dev/snd/controlC1:  israel 1973 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jan 20 08:58:35 2017
  HibernationDevice: RESUME=UUID=ca27f739-071f-4c25-974e-0d0f0614b21c
  InstallationDate: Installed on 2016-10-03 (108 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=90c3e094-e890-4c35-a0d2-0a358f5d2430 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-01-13 (6 days ago)
  dmi.bios.date: 06/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-405
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Kernel-packages] [Bug 1657112] kernel02 (s390x.zVM) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/kernel02__4.8.0-36.38__2017-01-20_07-16-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1657994] [NEW] Regression: HDMI audio produces no sound (Skylake NUC)

[Joseph Nuzman]

Public bug reported:

After upgrade from Xenial 16.04 to Yakkety 16.10, playing audio over HDMI no 
longer produces sound.
* When booting with old kernel from Xenial (4.4.0-59), HDMI audio works fine
* Audio from headphone jack works fine
* Userspace seems to be happily playing to HDMI audio device, but no sound 
produced at HDMI sink (Samsung TV)

Any of a wide range of pre-built mainline kernels fail to produce HDMI
audio, but with a different failure mode (HDMI audio does not seem to be
enumerated in the same way as in the Ubuntu kernels.)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-34-generic 4.8.0-34.36
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  israel 1973 F pulseaudio
 /dev/snd/controlC1:  israel 1973 F pulseaudio
CurrentDesktop: Unity
Date: Fri Jan 20 08:58:35 2017
HibernationDevice: RESUME=UUID=ca27f739-071f-4c25-974e-0d0f0614b21c
InstallationDate: Installed on 2016-10-03 (108 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=90c3e094-e890-4c35-a0d2-0a358f5d2430 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-34-generic N/A
 linux-backports-modules-4.8.0-34-generic  N/A
 linux-firmware1.161.1
SourcePackage: linux
UpgradeStatus: Upgraded to yakkety on 2017-01-13 (6 days ago)
dmi.bios.date: 06/03/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
dmi.board.name: NUC6i7KYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H90766-405
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Regression:  HDMI audio produces no sound (Skylake NUC)

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrade from Xenial 16.04 to Yakkety 16.10, playing audio over HDMI no 
longer produces sound.
  * When booting with old kernel from Xenial (4.4.0-59), HDMI audio works fine
  * Audio from headphone jack works fine
  * Userspace seems to be happily playing to HDMI audio device, but no sound 
produced at HDMI sink (Samsung TV)

  Any of a wide range of pre-built mainline kernels fail to produce HDMI
  audio, but with a different failure mode (HDMI audio does not seem to
  be enumerated in the same way as in the Ubuntu kernels.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  israel 1973 F pulseaudio
   /dev/snd/controlC1:  israel 1973 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jan 20 08:58:35 2017
  HibernationDevice: RESUME=UUID=ca27f739-071f-4c25-974e-0d0f0614b21c
  InstallationDate: Installed on 2016-10-03 (108 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed 
root=UUID=90c3e094-e890-4c35-a0d2-0a358f5d2430 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-34-generic N/A
   linux-backports-modules-4.8.0-34-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-01-13 (6 days ago)
  dmi.bios.date: 06/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-405
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0:

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

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

[Kernel-packages] [Bug 1657430] Re: linux: 4.4.0-62.83 -proposed tracker

[Steve Beattie]

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

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1657112] modoc (ppc64el) - tests ran: 16, failed: 3

[Brad Figg]

tests ran:  16, failed: 3;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/modoc__4.8.0-36.38__2017-01-20_06-10-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1657112] modoc (ppc64el) - tests ran: 36, failed: 4

[Brad Figg]

tests ran:  36, failed: 4;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/modoc__4.8.0-36.38__2017-01-20_03-48-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1657430] onza (i386) - tests ran: 4, failed: 0

[Brad Figg]

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-lowlatency/onza__4.4.0-62.83__2017-01-20_04-35-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1657430] onibi (amd64) - tests ran: 33, failed: 0

[Brad Figg]

tests ran:  33, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-lowlatency/onibi__4.4.0-62.83__2017-01-20_03-57-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1657430] onza (amd64) - tests ran: 34, failed: 4

[Brad Figg]

tests ran:  34, failed: 4;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-lowlatency/onza__4.4.0-62.83__2017-01-20_03-02-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1629603] Re: Wifi stops working sporadically

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Wifi stops working sporadically

Status in linux package in Ubuntu:
  Expired

Bug description:
  Since 16.04 I have been having trouble with WIFI stopping working
  daily and requiring a reboot to fix.

  This happens at worst multiple times a day and I dont know what could
  trigger it, the connection just stops working with no apparent reason
  and I cant get it back without a reboot.

  I did not have this problem with 15.10.

  My access point is ASUS RT-N12E_B1. I did not experience this issue
  when I was using a different access point for a few days so I'm not
  sure whether the cause is something specific to this wifi environment.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-generic 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lelux  2188 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Oct  1 22:56:40 2016
  HibernationDevice: RESUME=UUID=f9484e9d-673f-4b04-9e39-52035ccf958b
  InstallationDate: Installed on 2016-09-28 (3 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha i386 (20160921)
  MachineType: LENOVO 7665WM6
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC9WW (2.29 )
  dmi.board.name: 7665WM6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn7665WM6:pvrThinkPadT61:rvnLENOVO:rn7665WM6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7665WM6
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1657430] onibi (i386) - tests ran: 4, failed: 0

[Brad Figg]

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-lowlatency/onibi__4.4.0-62.83__2017-01-20_02-08-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1657112] modoc (ppc64el) - tests ran: 8, failed: 0

[Brad Figg]

tests ran:   8, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/modoc__4.8.0-36.38__2017-01-20_02-33-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1657112] s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/s2lp6g002__4.8.0-36.38__2017-01-20_02-45-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1657430] onza (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-lowlatency/onza__4.4.0-62.83__2017-01-20_02-38-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1657430] onza (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-lowlatency/onza__4.4.0-62.83__2017-01-20_02-10-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1657112] modoc (ppc64el) - tests ran: 10, failed: 0

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/modoc__4.8.0-36.38__2017-01-20_01-00-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1657430] onza (i386) - tests ran: 19, failed: 0

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/onza__4.4.0-62.83__2017-01-20_00-54-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1657430] onibi (amd64) - tests ran: 34, failed: 4

[Brad Figg]

tests ran:  34, failed: 4;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-lowlatency/onibi__4.4.0-62.83__2017-01-20_00-03-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

[Wesley C wamer]

@Konrad

Sorry for not being more specific I'm having the issues for the Bose
QC35 headphones.

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

Title:
  Fails to pair with Bose QC35 headphones

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions

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

[Kernel-packages] [Bug 1657430] onza (amd64) - tests ran: 19, failed: 0

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/onza__4.4.0-62.83__2017-01-19_23-39-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1651602] Re: NVMe driver regression for non-smp/1-cpu systems

[Dan Streetman]

Booted the 4.8.0-36-generic kernel with maxcpus=0 parameter and verified
all NVMe drives were initialized.

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

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

Title:
  NVMe driver regression for non-smp/1-cpu systems

Status in curtin:
  Invalid
Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.10.1)
  Deploying Xenial Nodes

  1) Deploy MAAS 2.1.1 on Yakkety
  2) Associate Juju 2.1 beta3
  3) Juju deploy Kubernetes Core

  Nodes begin to deploy but fail

  Installation failed with exception: Unexpected error while running command.
  Command: ['curtin', 'block-meta', 'custom']
  Exit code: 3
  Reason: -
  Stdout: b"no disk with serial 'CVMD434500BN400AGN' found\n"

  Related bugs:
   * bug 1647485: NVMe symlinks broken by devices with spaces in model or 
serial strings
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives

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

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

[Kernel-packages] [Bug 1648449] Re: NVMe drives in Amazon AWS instance fail to initialize

[Dan Streetman]

Verified with the 4.8.0-36-generic kernel on an AWS i3 instance, all the
NVMe drives initialized successfully.  Checked the git log and verified
the initial commit had been fully reverted (see comment 7).


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

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

Title:
  NVMe drives in Amazon AWS instance fail to initialize

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Invalid

Bug description:
  [Impact]

  On an Amazon AWS instance that has NVMe drives, the NVMe drives fail
  to initialize, and so aren't usable by the system.  If one of the NVMe
  drives contains the root filesystem, the instance won't boot.

  [Test Case]

  Boot an AWS instance with a NVMe drive.  It will fail to initialize
  the NVMe drive(s), and errors will appear in the system log (if the
  system boots at all).  With a patched kernel, all NVMe drives are
  initialized and enumerated and work properly.

  [Regression Potential]

  Patching the NVMe driver may cause problems on other systems using
  NVMe drives.

  [Other Info]

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

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

[Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

[Marcel Krause]

Upgraded my netbook to xenial today, paired my Sennheiser PX210BT,
shows up in "bt-device --list", connects and headphones play their
internal "playback device added" sound. pavucontrol sees them as
well and offers "High Fidelity Playback (A2DP Sink)" as one of the
modes, so I select it, but still its "output devices" tab has just
the "dummy output". :-(

Also I want the bt-audio command back.

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Kernel-packages] [Bug 1656381] Re: Xen MSI setup code incorrectly re-uses cached pirq

[Dan Streetman]

Verified with the 4.8.0-36-generic kernel on an AWS i3 instance, all the
NVMe drives initialized successfully.

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

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

Title:
  Xen MSI setup code incorrectly re-uses cached pirq

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  [Impact]

  This bug fixes the root problem reported in bug 1648449, so its
  description can be mostly reused here:

  On an Amazon AWS instance that has NVMe drives, the NVMe drives fail
  to initialize, and so aren't usable by the system. If one of the NVMe
  drives contains the root filesystem, the instance won't boot.

  [Test Case]

  Boot an AWS instance with multiple NVMe drives. All except the first
  will fail to initialize, and errors will appear in the system log (if
  the system boots at all). With a patched kernel, all NVMe drives are
  initialized and enumerated and work properly.

  [Regression Potential]

  Patching the Xen MSI setup function may cause problems with other PCI
  devices using MSI/MSIX interrupts on a Xen guest.

  Note this patch restores correct behavior for guests running under Xen
  4.5 or later hypervisors - specifically Xen hypervisors with qemu
  2.1.0 or later.  For Xen hypervisors with qemu 2.0.0 or earlier, this
  patch causes a regression.  With an Ubuntu hypervisor, Vivid or later
  qemu is patched, as well as UCA Kilo or later qemu.  Trusty qemu or
  UCA Icehouse qemu are not patched - see bug 1657489.

  [Other Info]

  The patch from bug 1648449 was only a workaround, that changed the
  NVMe driver to not trigger this Xen bug.  However, there have been
  reports of that patch causing non-Xen systems with NVMe drives to stop
  working, in bug 1626894.  So, the best thing to do is revert the
  workaround patch (and its regression fix patch from bug 1651602) back
  to the original NVMe drive code, and apply the real Xen patch to fix
  the problem.  That should restore functionality for non-Xen systems,
  and should allow Xen systems with multiple NVMe controllers to work.

  Upstream discussion:
  https://lists.xen.org/archives/html/xen-devel/2017-01/msg00447.html

  Related: bug 1657489 ("qemu-xen: free all the pirqs for msi/msix when
  driver unload")

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

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

[Kernel-packages] [Bug 1611831] Re: Can't boot from new kernel 4.4.0-34. Old kernel 4.4.0-31 is fine.

[Dan Moore]

I was able to install 4.4.0-43-generic and extras, and it works. Will
test on 4.4.0-59 and 4.8.0 and report back.

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

Title:
  Can't boot from new kernel 4.4.0-34.  Old kernel 4.4.0-31 is fine.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Greetings,

  I recently upgraded from the 4.4.0-31 to 4.4.0-34 kernel in Ubuntu
  16.04.  If I try booting from 4.4.0-34, my system freezes just after I
  enter my password to decrypt my hard-drive.  If I ask it to boot from
  4.4.0-31, everything is fine.

  My boot.log file:

lvmetad is not active yet, using direct activation during sysinit
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes.  This may take a while...
Found volume group "ubuntu-vg" using metadata type lvm2
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
2 logical volume(s) in volume group "ubuntu-vg" now active
  /dev/mapper/ubuntu--vg-root: recovering journal
  /dev/mapper/ubuntu--vg-root: clean, 525872/28426240 files, 91143613/113674240 
blocks

  
  It's unclear to me what is going wrong.  There appears to be no activity on 
the computer.  I let the boot sequence sit for 10 minutes (way longer than an 
average boot time) my laptop's fan is running full-tilt.  But there was no 
hard-drive activity.  

  How can I find out what's going wrong?

  I'm running Ubuntu 16.04 Linux on a Lenovo W530.  I'm not certain what other 
information would be helpful for a bug report.  I would be happy to submit 
whatever is deemed helpful. 
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rybu   4449 F pulseaudio
   /dev/snd/controlC0:  rybu   4449 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=48cdbc4a-e07f-4aa4-bb23-e2904e1cd350
  InstallationDate: Installed on 2016-04-26 (106 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2436CTO
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2436CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2436CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1656381] Re: Xen MSI setup code incorrectly re-uses cached pirq

[Dan Streetman]

Verified with the 4.4.0-62-generic kernel on an AWS i3 instance, all the
NVMe drives initialized successfully.

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

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

Title:
  Xen MSI setup code incorrectly re-uses cached pirq

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress

Bug description:
  [Impact]

  This bug fixes the root problem reported in bug 1648449, so its
  description can be mostly reused here:

  On an Amazon AWS instance that has NVMe drives, the NVMe drives fail
  to initialize, and so aren't usable by the system. If one of the NVMe
  drives contains the root filesystem, the instance won't boot.

  [Test Case]

  Boot an AWS instance with multiple NVMe drives. All except the first
  will fail to initialize, and errors will appear in the system log (if
  the system boots at all). With a patched kernel, all NVMe drives are
  initialized and enumerated and work properly.

  [Regression Potential]

  Patching the Xen MSI setup function may cause problems with other PCI
  devices using MSI/MSIX interrupts on a Xen guest.

  Note this patch restores correct behavior for guests running under Xen
  4.5 or later hypervisors - specifically Xen hypervisors with qemu
  2.1.0 or later.  For Xen hypervisors with qemu 2.0.0 or earlier, this
  patch causes a regression.  With an Ubuntu hypervisor, Vivid or later
  qemu is patched, as well as UCA Kilo or later qemu.  Trusty qemu or
  UCA Icehouse qemu are not patched - see bug 1657489.

  [Other Info]

  The patch from bug 1648449 was only a workaround, that changed the
  NVMe driver to not trigger this Xen bug.  However, there have been
  reports of that patch causing non-Xen systems with NVMe drives to stop
  working, in bug 1626894.  So, the best thing to do is revert the
  workaround patch (and its regression fix patch from bug 1651602) back
  to the original NVMe drive code, and apply the real Xen patch to fix
  the problem.  That should restore functionality for non-Xen systems,
  and should allow Xen systems with multiple NVMe controllers to work.

  Upstream discussion:
  https://lists.xen.org/archives/html/xen-devel/2017-01/msg00447.html

  Related: bug 1657489 ("qemu-xen: free all the pirqs for msi/msix when
  driver unload")

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

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

[Kernel-packages] [Bug 1657112] modoc (ppc64el) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/modoc__4.8.0-36.38__2017-01-20_00-00-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1657112] Re: linux: 4.8.0-36.38 -proposed tracker

[Steve Beattie]

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

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
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:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1611831] Re: Can't boot from new kernel 4.4.0-34. Old kernel 4.4.0-31 is fine.

[Dan Moore]

While I'm not using encryption, I am using LVM and am experincing this
same problem on 4.4.0-59 and 4.8.0, upgrading from 3.19.0-79 which was
previously working.

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

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

Title:
  Can't boot from new kernel 4.4.0-34.  Old kernel 4.4.0-31 is fine.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Greetings,

  I recently upgraded from the 4.4.0-31 to 4.4.0-34 kernel in Ubuntu
  16.04.  If I try booting from 4.4.0-34, my system freezes just after I
  enter my password to decrypt my hard-drive.  If I ask it to boot from
  4.4.0-31, everything is fine.

  My boot.log file:

lvmetad is not active yet, using direct activation during sysinit
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes.  This may take a while...
Found volume group "ubuntu-vg" using metadata type lvm2
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
2 logical volume(s) in volume group "ubuntu-vg" now active
  /dev/mapper/ubuntu--vg-root: recovering journal
  /dev/mapper/ubuntu--vg-root: clean, 525872/28426240 files, 91143613/113674240 
blocks

  
  It's unclear to me what is going wrong.  There appears to be no activity on 
the computer.  I let the boot sequence sit for 10 minutes (way longer than an 
average boot time) my laptop's fan is running full-tilt.  But there was no 
hard-drive activity.  

  How can I find out what's going wrong?

  I'm running Ubuntu 16.04 Linux on a Lenovo W530.  I'm not certain what other 
information would be helpful for a bug report.  I would be happy to submit 
whatever is deemed helpful. 
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rybu   4449 F pulseaudio
   /dev/snd/controlC0:  rybu   4449 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=48cdbc4a-e07f-4aa4-bb23-e2904e1cd350
  InstallationDate: Installed on 2016-04-26 (106 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2436CTO
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2436CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2436CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1657430] modoc (ppc64el) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/modoc__4.4.0-62.83__2017-01-19_23-14-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1657430] onibi (i386) - tests ran: 19, failed: 0

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/onibi__4.4.0-62.83__2017-01-19_22-30-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1657430] onza (i386) - tests ran: 23, failed: 0

[Brad Figg]

tests ran:  23, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/onza__4.4.0-62.83__2017-01-19_21-10-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1657907

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

Title:
  555-BCOE Killer 1535 802.11ac 2x2 WiFi/Bluetooth: firmware crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Every not too often, my wifi adapter/driver/firmware seems to crash.

  Here is the most recent one, entry in `dmesg`:

  [20634.804968] ath10k_pci :3a:00.0: firmware crashed! (uuid 
a373e5e5-e4a9-4391-b091-f6c7b58f9f73)
  [20634.804985] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:1535
  [20634.804989] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [20634.805896] ath10k_pci :3a:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
  [20634.806401] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 
6fc88fe7
  [20634.806415] ath10k_pci :3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [20634.808476] ath10k_pci :3a:00.0: firmware register dump:
  [20634.808486] ath10k_pci :3a:00.0: [00]: 0x0503 0x15B3 
0x009860FA 0x00955B31
  [20634.808492] ath10k_pci :3a:00.0: [04]: 0x009860FA 0x00060730 
0x0004 0x0040E8A0
  [20634.808497] ath10k_pci :3a:00.0: [08]: 0x00498110 0x00955A00 
0x000B 0x0040
  [20634.808502] ath10k_pci :3a:00.0: [12]: 0x0009 0x 
0x00952CD0 0x00952CE6
  [20634.808507] ath10k_pci :3a:00.0: [16]: 0x00952CC4 0x00910712 
0x 0x0091080D
  [20634.808513] ath10k_pci :3a:00.0: [20]: 0x409860FA 0x0040E7E8 
0x 0x0041E0DC
  [20634.808518] ath10k_pci :3a:00.0: [24]: 0x800B5A1D 0x0040E848 
0x000F 0xC09860FA
  [20634.808523] ath10k_pci :3a:00.0: [28]: 0x809B3230 0x0040E948 
0x0018 0x004313B8
  [20634.808528] ath10k_pci :3a:00.0: [32]: 0x809B2992 0x0040E998 
0x0040E9C0 0x00429548
  [20634.808533] ath10k_pci :3a:00.0: [36]: 0x8091D252 0x0040E9B8 
0x 0x0002
  [20634.808538] ath10k_pci :3a:00.0: [40]: 0x809FF05D 0x0040EA68 
0x0043A380 0x00429C10
  [20634.808543] ath10k_pci :3a:00.0: [44]: 0x809FCFDB 0x0040EA88 
0x0043A380 0x0001
  [20634.808548] ath10k_pci :3a:00.0: [48]: 0x80911210 0x0040EAD8 
0x0010 0x004041D0
  [20634.808553] ath10k_pci :3a:00.0: [52]: 0x80911154 0x0040EB28 
0x0040 0x
  [20634.808558] ath10k_pci :3a:00.0: [56]: 0x8091122D 0x0040EB48 
0x 0x00400600
  [20634.911972] ieee80211 phy0: Hardware restart was requested

  The system does recover, at least partially, but system feels laggy.
  Might be subjective.

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

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

[Kernel-packages] [Bug 1657907] [NEW] 555-BCOE Killer 1535 802.11ac 2x2 WiFi/Bluetooth: firmware crashes

[Gerardus]

Public bug reported:

Every not too often, my wifi adapter/driver/firmware seems to crash.

Here is the most recent one, entry in `dmesg`:

[20634.804968] ath10k_pci :3a:00.0: firmware crashed! (uuid 
a373e5e5-e4a9-4391-b091-f6c7b58f9f73)
[20634.804985] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 chip_id 
0x00340aff sub 1a56:1535
[20634.804989] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 
0 testmode 0
[20634.805896] ath10k_pci :3a:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
[20634.806401] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 
6fc88fe7
[20634.806415] ath10k_pci :3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp 
max-sta 32 raw 0 hwcrypto 1
[20634.808476] ath10k_pci :3a:00.0: firmware register dump:
[20634.808486] ath10k_pci :3a:00.0: [00]: 0x0503 0x15B3 0x009860FA 
0x00955B31
[20634.808492] ath10k_pci :3a:00.0: [04]: 0x009860FA 0x00060730 0x0004 
0x0040E8A0
[20634.808497] ath10k_pci :3a:00.0: [08]: 0x00498110 0x00955A00 0x000B 
0x0040
[20634.808502] ath10k_pci :3a:00.0: [12]: 0x0009 0x 0x00952CD0 
0x00952CE6
[20634.808507] ath10k_pci :3a:00.0: [16]: 0x00952CC4 0x00910712 0x 
0x0091080D
[20634.808513] ath10k_pci :3a:00.0: [20]: 0x409860FA 0x0040E7E8 0x 
0x0041E0DC
[20634.808518] ath10k_pci :3a:00.0: [24]: 0x800B5A1D 0x0040E848 0x000F 
0xC09860FA
[20634.808523] ath10k_pci :3a:00.0: [28]: 0x809B3230 0x0040E948 0x0018 
0x004313B8
[20634.808528] ath10k_pci :3a:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9C0 
0x00429548
[20634.808533] ath10k_pci :3a:00.0: [36]: 0x8091D252 0x0040E9B8 0x 
0x0002
[20634.808538] ath10k_pci :3a:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 
0x00429C10
[20634.808543] ath10k_pci :3a:00.0: [44]: 0x809FCFDB 0x0040EA88 0x0043A380 
0x0001
[20634.808548] ath10k_pci :3a:00.0: [48]: 0x80911210 0x0040EAD8 0x0010 
0x004041D0
[20634.808553] ath10k_pci :3a:00.0: [52]: 0x80911154 0x0040EB28 0x0040 
0x
[20634.808558] ath10k_pci :3a:00.0: [56]: 0x8091122D 0x0040EB48 0x 
0x00400600
[20634.911972] ieee80211 phy0: Hardware restart was requested

The system does recover, at least partially, but system feels laggy.
Might be subjective.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1657907

Title:
  555-BCOE Killer 1535 802.11ac 2x2 WiFi/Bluetooth: firmware crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Every not too often, my wifi adapter/driver/firmware seems to crash.

  Here is the most recent one, entry in `dmesg`:

  [20634.804968] ath10k_pci :3a:00.0: firmware crashed! (uuid 
a373e5e5-e4a9-4391-b091-f6c7b58f9f73)
  [20634.804985] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:1535
  [20634.804989] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [20634.805896] ath10k_pci :3a:00.0: firmware ver 
WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad 
crc32 75dee6c5
  [20634.806401] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 
6fc88fe7
  [20634.806415] ath10k_pci :3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [20634.808476] ath10k_pci :3a:00.0: firmware register dump:
  [20634.808486] ath10k_pci :3a:00.0: [00]: 0x0503 0x15B3 
0x009860FA 0x00955B31
  [20634.808492] ath10k_pci :3a:00.0: [04]: 0x009860FA 0x00060730 
0x0004 0x0040E8A0
  [20634.808497] ath10k_pci :3a:00.0: [08]: 0x00498110 0x00955A00 
0x000B 0x0040
  [20634.808502] ath10k_pci :3a:00.0: [12]: 0x0009 0x 
0x00952CD0 0x00952CE6
  [20634.808507] ath10k_pci :3a:00.0: [16]: 0x00952CC4 0x00910712 
0x 0x0091080D
  [20634.808513] ath10k_pci :3a:00.0: [20]: 0x409860FA 0x0040E7E8 
0x 0x0041E0DC
  [20634.808518] ath10k_pci :3a:00.0: [24]: 0x800B5A1D 0x0040E848 
0x000F 0xC09860FA
  [20634.808523] ath10k_pci :3a:00.0: [28]: 0x809B3230 0x0040E948 
0x0018 0x004313B8
  [20634.808528] ath10k_pci :3a:00.0: [32]: 0x809B2992 0x0040E998 
0x0040E9C0 0x00429548
  [20634.808533] ath10k_pci :3a:00.0: [36]: 0x8091D252 0x0040E9B8 
0x 0x0002
  [20634.808538] ath10k_pci :3a:00.0: [40]: 0x809FF05D 0x0040EA68 
0x0043A380 0x00429C10
  [20634.808543] ath10k_pci :3a:00.0: [44]: 0x809FCFDB 0x0040EA88 
0x0043A380 0x0001
  [20634.808548] ath10k_pci :3a:00.0: [48]: 0x80911210 0x0040EAD8 
0x0010 0x004041D0
  [20634.808553] ath10k_pci :3a:00.0: [52]: 0x80911154 0x0040EB28 
0x0040 0x
  [20634.808558] ath10k_pci :3a:00.0: [56]: 0x8091122D 0x0040EB48 
0x 0x00400600
  

[Kernel-packages] [Bug 1657112] dwalin (amd64) - tests ran: 36, failed: 0

[Brad Figg]

tests ran:  36, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/dwalin__4.8.0-36.38__2017-01-19_20-57-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1657430] modoc (ppc64el) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/modoc__4.4.0-62.83__2017-01-19_22-39-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1649905] Re: On boot excessive number of kworker threads are running

[Doug Smythies]

I would not expect to see this issue in 16.04, and don't on my test
16.04 server, with the default,  up to date, kernel. (Linux s15
4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux).

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

Title:
  On boot excessive number of kworker threads are running

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [SRU REQUEST, Yakkety]

  Ubuntu Yakkety 4.8 kernels have an excessive amount of kworker threads
  running, this is especially noticeable on boot, one can easily have >
  1000 kworker threads on a 4 CPU box.

  Bisected this down to:

  commit 81ae6d03952c1bfb96e1a716809bd65e7cd14360
  Author: Vladimir Davydov 
  Date:   Thu May 19 17:10:34 2016 -0700

  mm/slub.c: replace kick_all_cpus_sync() with synchronize_sched() in
  kmem_cache_shrink()

  [FIX]

  The synchronize_sched calls seem to create all these excessive kworker
  threads.  This is fixed with upstream commit:

  commit 89e364db71fb5e7fc8d93228152abfa67daf35fa
  Author: Vladimir Davydov 
  Date:   Mon Dec 12 16:41:32 2016 -0800

  slub: move synchronize_sched out of slab_mutex on shrink
  
  synchronize_sched() is a heavy operation and calling it per each cache
  owned by a memory cgroup being destroyed may take quite some time.  What
  is worse, it's currently called under the slab_mutex, stalling all works
  doing cache creation/destruction.
  
  Actually, there isn't much point in calling synchronize_sched() for each
  cache - it's enough to call it just once - after setting cpu_partial for
  all caches and before shrinking them.  This way, we can also move it out
  of the slab_mutex, which we have to hold for iterating over the slab
  cache list.

  [TEST CASE]

  Without the fix, boot a Yakkety and count the number of kthreads:

  ps -ef | grep kworker | wc -l
  1034

  With the fix, boot count the number kthreads and it will be
  dramatically less:

  ps -ef | grep kworker | wc -l
  32

  Since this touches the slub allocator and cgroups too, I have
  regression tested this against the kernel-team autotest regression
  tests to sanity check this fix. All seems OK.

  Note: this only affects kernels from 4.7-rc1 through to 4.8

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

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

[Kernel-packages] [Bug 1554077] Re: brcmf_add_if: ERROR: netdev:wlp2s0 already exists

[elParaguayo]

I also get this on my XPS 13 laptop running 16.04 "Linux
4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux"

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

Title:
  brcmf_add_if: ERROR: netdev:wlp2s0 already exists

Status in linux package in Ubuntu:
  Expired

Bug description:
  At boot time, on  Wifi interface set up, at boot time, an error is raised. 
  The graphical boot switches to textual boot to display this error.
  Despite this error the Wifi connection mostly works.

  [   47.250309] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
  [   47.289947] brcmf_add_if: ERROR: netdev:wlp2s0 already exists
  [   47.289950] brcmf_add_if: ignore IF event
  [   48.485330] brcmf_add_if: ERROR: netdev:wlp2s0 already exists
  [   48.485333] brcmf_add_if: ignore IF event

  Ubuntu Wily 15.10, Kernel 4.2.0-30-generic,
  Network controller: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC 
(rev 01)
  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gquintana   1413 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=2e069a2b-037f-4058-89b1-6e221da4046d
  InstallationDate: Installed on 2016-01-31 (35 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0a5c:6410 Broadcom Corp.
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0c45:6713 Microdia
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=3ecb2c05-ad6c-4d9d-9356-48c6991f0226 ro quiet splash 
nouveau.modeset=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0X2P13
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0X2P13:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1657430] modoc (ppc64el) - tests ran: 141, failed: 0

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/modoc__4.4.0-62.83__2017-01-19_21-32-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1270676] Re: SD Card Reader broken on UX302LG

[Kamil]

@Bus van den Heuvel: did you found any solution to your issue. I own the
same notebook UX501-VW and also encountered the error with IRQ-17 flag.
Have you tried do modify the code any futher? The card reader would be
very useful for me.

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

Title:
  SD Card Reader broken on UX302LG

Status in linux package in Ubuntu:
  Triaged

Bug description:
  SD card reader (controller Alcor Micro AU6601) is dysfunctional in UX302LG 
laptop. USB readers work without problem. Nothing happens when pluggin 
SD/mSD/SDHC/mSDHC cards in the reader (might as well use a piece of wood).
  Nothing is listed in lsusb -v that could be the reader.
  Nohting is listed in lspci -k -vv -nnn.
  Nothing in acpi_listen.
  Nothing in kern.log etc.

  According to (select "Windows 8" then "Card Reader") :
  
http://support.asus.com/download.aspx?SLanguage=en=3=597=UX302LG==GEZaY8oaj8oSlQ3U

  Reader vendor is :
  Alcor Multi-Card Reader Driver
  http://www.pcidatabase.com/vendor_details.php?id=1672

  There is only one device that is "Unassigned class" 1aea:6601 but
  searching this online only pops up my other bug reports (sigh) and
  vendor is unassigned on pcidatabase.com.

  But...Downloading the 14M Win driver for the reader, vendor id 1aea and 
device id 6601 is present at multiple instances :
  [DeviceList.NTamd64]
  ; For XP and later
  %AMPCIECR% = DriverInstall_6601, PCI\VEN_1aea_6601

  Also there is mention of _Gen instance in the .inf, might point to a 
"Generic" alternative ?
  [DeviceList_Gen.NTamd64]
  ; For XP and later
  %AMPCIECR_GEN% = DriverInstall_Gen, PCI\VEN_105b_0ef6

  This does point to something totally different online 105b:0ef6 points to 
some Realtek HD Audio device...
  ---
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-12-31 (21 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131231)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.13.0-031300-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  ---
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6
  InstallationDate: Installed on 2013-12-31 (21 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131231)
  MachineType: ASUSTeK COMPUTER INC. UX302LG
  Package: linux (not installed)
  ProcFB: 0 simple
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-4-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= nomodeset 
plymouth:debug vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-4-generic N/A
   linux-backports-modules-3.13.0-4-generic  N/A
   linux-firmware1.121
  Tags:  trusty
  Uname: Linux 3.13.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 10/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX302LG.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX302LG
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX302LG
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1657430] onibi (amd64) - tests ran: 19, failed: 0

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/onibi__4.4.0-62.83__2017-01-19_20-58-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1651242] Re: Ubuntu16.04.2KVM: Installing any package on Ubuntu16.04.2 guest having NPIV disk shows traces: blk_update_request: I/O error, dev sda, sector 5006840

[bugproxy]

--- Comment From mauri...@br.ibm.com 2017-01-19 16:34 EDT---
Verification done with yakkety! All good.

# lsb_release -d
Description:Ubuntu 16.10

Previous kernel (fail)
--

# uname -rv
4.8.0-22-generic #24-Ubuntu SMP Sat Oct 8 09:14:41 UTC 2016

# capsh --drop=cap_sys_rawio -- -c \
'sg_write_same --num 1 --xferlen 512 /dev/sdb'
Write same: pass through os error: Operation not permitted
Write same(10): Sense category: -1, try '-v' option for more information

Proposed kernel (pass)
---

# uname -rv
4.8.0-36-generic #38-Ubuntu SMP Tue Jan 17 15:31:08 UTC 2017

# capsh --drop=cap_sys_rawio -- -c \
>   'sg_write_same --num 1 --xferlen 512 /dev/sdb'

# echo $?
0

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

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

Title:
  Ubuntu16.04.2KVM: Installing any package on Ubuntu16.04.2 guest having
  NPIV disk shows traces: blk_update_request: I/O error, dev sda, sector
  5006840

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  == Comment: #35 - Mauricio Faria De Oliveira - 2016-12-19 09:20:41 ==
  Hi Canonical,

  Could you please apply this patch [1] for 16.04.x HWE 4.8 ?

  It has not yet been accepted by the block subsystem maintainer Jens Axboe,
  but good a reviewed-by tag from Christoph Hellwig [2].

  The change is very straightforward and clearly spottable/documented,
  so if at all possible, I think it wouldn't be a problem for it to be SAUCE 
commit for now.

  Thank you,

  [PATCH RESEND] block: allow WRITE_SAME commands with the SG_IO ioctl

  [1] https://lkml.org/lkml/2016/12/15/503
  [2] https://lkml.org/lkml/2016/12/19/132

  == Comment: #36 - Mauricio Faria De Oliveira - 2016-12-19 12:39:24 ==
  (In reply to comment #35)
  > Hi Canonical,
  > 
  > Could you please apply this patch [1] for 16.04.x HWE 4.8 ?
  > 
  > It has not yet been accepted by the block subsystem maintainer Jens Axboe,
  > but good a reviewed-by tag from Christoph Hellwig [2].

  Hey, it just got word from Jens; added to 4.10 [3].

  [3] https://lkml.org/lkml/2016/12/19/318

  == Comment: #37 - Mauricio Faria De Oliveira - 2016-12-19 12:40:51 ==
  (In reply to comment #36)
  > (In reply to comment #35)
  > > Hi Canonical,
  > > 
  > > Could you please apply this patch [1] for 16.04.x HWE 4.8 ?
  > > 
  > > It has not yet been accepted by the block subsystem maintainer Jens Axboe,
  > > but good a reviewed-by tag from Christoph Hellwig [2].
  > 
  > Hey, it just got word from Jens; added to 4.10 [3].

  And here is it in his branch on g.k.o [4]

  [4] http://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-
  linus=25cdb64510644f3e854d502d69c73f21c6df88a9

  Bug History:

  == Comment: #0 - Manjunatha H R - 2016-12-06 01:52:11 ==
  Ubuntu16.04.2 KVM guest having NPIV disks shows following traces upon 
installing any package:

  root@lotg5:~# apt-get install -y python-paramiko
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
python-crypto python-ecdsa python-six
  Suggested packages:
python-crypto-dbg python-crypto-doc
  The following NEW packages will be installed:
python-crypto python-ecdsa python-paramiko python-six
  0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
  Need to get 404 kB of archives.
  After this operation, 3,092 kB of additional disk space will be used.
  Get:1 http://us.ports.ubuntu.com/ubuntu-ports xenial/main ppc64el 
python-crypto ppc64el 2.6.1-6build1 [251 kB]
  Get:2 http://us.ports.ubuntu.com/ubuntu-ports xenial/main ppc64el python-six 
all 1.10.0-3 [10.9 kB]
  Get:3 http://us.ports.ubuntu.com/ubuntu-ports xenial/main ppc64el 
python-ecdsa all 0.13-2 [34.0 kB]
  Get:4 http://us.ports.ubuntu.com/ubuntu-ports xenial/main ppc64el 
python-paramiko all 1.16.0-1 [109 kB]
  Fetched 404 kB in 5s (72.6 kB/s)  
  Selecting previously unselected package python-crypto.
  (Reading database ... 104986 files and directories currently installed.)
  Preparing to unpack .../python-crypto_2.6.1-6build1_ppc64el.deb ...
  Unpacking python-crypto (2.6.1-6build1) ...
  [  529.051285] blk_update_request: I/O error, dev sda, sector 17096824
  [  529.175195] blk_update_request: I/O error, dev sda, sector 5009416
  [  529.239143] blk_update_request: I/O error, dev sda, sector 5009440
  [  529.303689] blk_update_request: I/O error, dev sda, sector 5009480
  [  529.375233] blk_update_request: I/O error, dev sda, sector 5009488
  [  529.455172] blk_update_request: I/O error, dev sda, sector 5009520
  [  529.535189] blk_update_request: I/O error, dev sda, sector 5009544
  [  

[Kernel-packages] [Bug 1655745] Re: linux: 3.19.0-80.88 -proposed tracker

[Steve Beattie]

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

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

Title:
  linux: 3.19.0-80.88 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-80.88 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
  derivative-trackers-created: 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/1655745/+subscriptions

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

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

[Steve Beattie]

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

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

Title:
  linux-lts-trusty: 3.13.0-108.155~precise1 -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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
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 3.13.0-108.155~precise1 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655476
  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/1655480/+subscriptions

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

[Kernel-packages] [Bug 1657430] modoc (ppc64el) - tests ran: 16, failed: 2

[Brad Figg]

tests ran:  16, failed: 2;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/modoc__4.4.0-62.83__2017-01-19_20-35-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1655076] Re: linux-armadaxp: 3.2.0-1682.109 -proposed tracker

[Steve Beattie]

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

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

Title:
  linux-armadaxp: 3.2.0-1682.109 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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-armadaxp package in Ubuntu:
  Invalid
Status in linux-armadaxp source package in Precise:
  In Progress

Bug description:
  This bug is for tracking the 3.2.0-1682.109 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655071
  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/1655076/+subscriptions

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

[Kernel-packages] [Bug 1655476] Re: linux: 3.13.0-108.155 -proposed tracker

[Steve Beattie]

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

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

Title:
  linux: 3.13.0-108.155 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-108.155 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
  derivative-trackers-created: 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/1655476/+subscriptions

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

[Kernel-packages] [Bug 1655075] Re: linux-ti-omap4: 3.2.0-1499.126 -proposed tracker

[Steve Beattie]

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

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

Title:
  linux-ti-omap4: 3.2.0-1499.126 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 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
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655071
  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/1655075/+subscriptions

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

[Kernel-packages] [Bug 1655071] Re: linux: 3.2.0-121.164 -proposed tracker

[Steve Beattie]

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

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

Title:
  linux: 3.2.0-121.164 -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-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the 3.2.0-121.164 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
  derivative-trackers-created: 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/1655071/+subscriptions

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

[Kernel-packages] [Bug 1657430] onibi (i386) - tests ran: 20, failed: 0

[Brad Figg]

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/onibi__4.4.0-62.83__2017-01-19_18-31-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1657112] dwalin (amd64) - tests ran: 38, failed: 6

[Brad Figg]

tests ran:  38, failed: 6;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/dwalin__4.8.0-36.38__2017-01-19_19-20-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1657430] modoc (ppc64el) - tests ran: 36, failed: 4

[Brad Figg]

tests ran:  36, failed: 4;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/modoc__4.4.0-62.83__2017-01-19_18-09-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

-- 
Mailing list: https://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 1650336] Re: NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

[Seth Forshee]

On Thu, Jan 19, 2017 at 06:14:33PM -, Thomas Fili wrote:
> @Seth : Yes, this problem is very confusing

Thanks for the clarifications.

> Unfortunately the kernel 4.4.0-54 is not available any longer from
> offical repos ... so i not able to test this one again ... but maybe
> this kernel had also the problem ?!

Yeah, looks like this build never made it out of our PPA.

> But i will try to find the last working kernel between 4.4.0-34 to
> 4.4.0-53 tomorrow.

Please do. So far we've been working under the assumption that this is a
bug introduced after 4.4.0-54, so if it was introduced before that we
would never have found it. Honestly though if the build at commit
50f208e18014589971583a8495987194724d56e4 is bad then 4.4.0-54 is almost
certainly bad as well.

> And there is also another bug with accessing a nfsv4 subshare

Yes, I haven't forgotten about this one. I'm waiting on the upstream
developers right now, but if they don't come back with something by
early next week I'll pursue a temporary fix in x/y.

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

Title:
  NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

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

Bug description:
  On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel
  crash on boot when in /etc/fstab a nfsv4 entry is active

  When comment the line or set to noauto the kernel boot with no error
  and mounting the nfs shares (after uncomment ) is also possible
  without error

  4.4.0-54 boots without this problem.

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

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

[Kernel-packages] [Bug 1653162] Re: System won't boot after upgrade to 16.04 with 4.4.0 kernel

[Joseph Salisbury]

I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.

Can you test the following kernels and report back? We are looking for
the first kernel version that exhibits this bug:

3.13 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/
3.16 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-utopic/
4.0 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/
4.2 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-wily/
4.4 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/


You don't have to test every kernel, just up until the kernel that first has 
this bug.

Thanks in advance!

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

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Yakkety)
   Status: New => Triaged

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Tags removed: kernel-da-key
** Tags added: kernel-key

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

Title:
  System won't boot after upgrade to 16.04 with 4.4.0 kernel

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged

Bug description:
  I have a Dell PowerEdge 1800 with Dell CERC 1.5/6ch RAID controller in
  it. Everything worked fine under Ubuntu 14.04.1. When I upgraded to
  16.04.1 the system won't boot. It can't find the root filesystem. I
  see errors about host adapter dead on the screen many times. This is
  with kernel 4.4.0-57 and with 4.8.0-32. When I switch back to kernel
  3.13.0-105 the system boots just fine.

  I have mptbios 5.06.04.
  The CERC card says bios version 4.1-0 [Build 7403]

  When booting into the ercovery kernel I'm getting error messages about host 
adapter dead.
  Eventually I get a message:
  "aacraid: aac_fib_send: first asynchronous command timed out.
  Usually a result of a PCI interrupt routing problem
  update moher board BIOS or consider utilizing one of
  the SAFE mode kernel options (acpi, apic etc)"

  
  Using kernel parameter "intel_iommu=on" doesn't help. This was suggested on a 
post that I saw about these errors.

  Booting with "noapic" didn't help.
  Booting with "noapic noacpi" didn't help.

  
  I've also tried the dkms modules from Adaptec and that doesn't seem to help 
either.

  
  I can't figure out how to upgrade the firmware or BIOS on the system from 
Ubuntu either.

  
  This may be related to this bug: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552551?comments=all
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=beec17b5-eac8-4e94-ac99-65b63c428b77
  InstallationDate: Installed on 2014-02-24 (1039 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  IwConfig:
   eth1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Computer Corporation PowerEdge 1800
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-105-generic 
root=UUID=83e1b87e-adb9-4798-a6e0-18d401c91a4a ro nosplash noplymouth
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-105-generic N/A
   

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

[roots]

Maybe some symptoms with my old mainboard will be helpful for general
debugging this issue:

-The drive was *sometimes* recognised fine at boot in first place, showed with 
"lspci" and "nvme list" would give me correct output
-After boot, the drive would go "missing" after a duration of approx. 5 to 1000 
or more seconds for no obvious reason, here's what dmesg | grep nvme gave:

[ 37.805783] nvme :01:00.0: Failed status: 0x, reset controller.
[ 37.825887] nvme :01:00.0: Refused to change power state, currently in D3
[ 37.825934] nvme nvme0: Removing after probe failure status: -19
[ 37.825941] nvme0n1: detected capacity change from 1024209543168 to 0

Furthermore, this could be interesting:

-If I changed from default BIOS settings to overclocked ones, the NVME drive 
would not be seen by the _OS_ anymore
-If my HDD drive was going to sleep in Ubuntu (via hdparm), the NVME drive 
would get disconnected _instantly_, with dmesg showing the same output as above.

The two last effects were reproducible, they occured with kernels
4.4.0-53, 4.4.0-57, 4.4.0-58, 4.9.0. Especially hdparm -Y (or -y)
/dev/myhdd would cause the NVME drive to become lost instantly.

Hope this may be of help.

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

[Joseph Salisbury]

This may be related to bug 1655842 .  Can you test the test kernel for
that bug which can be downloaded here:

http://kernel.ubuntu.com/~jsalisbury/lp1655842/

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
  Jan  9 07:36:53 gorilla kernel: 

[Kernel-packages] [Bug 1630924] Re: Kdump through NMI SMP and single core not working on Ubuntu16.10

[Joseph Salisbury]

I see commit 59107e2f4 in mainline:
59107e2f4883 x86/hyperv: Handle unknown NMIs on one CPU when unknown_nmi_panic

However, I don't see 56ef6718a as of yet.  Do you have a patch
available?

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

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

Title:
  Kdump through NMI SMP and single core not working on Ubuntu16.10

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  During some tests I've encountered an issue with kdump through NMI SMP
  and single core. After kdump configuration, when I trigger the crash
  through an NMI call from the host, the VM will panic, however it will
  not write the vmcore dump files and neither reboot.

  REPRO STEPS:

  1. configure kdump
   - crashkernel=512M-:384M  /boot/grub/grub.cfg
   - USE_KDUMP=1 /etc/default/kdump-tools

  2. after configuration reboot the VM

  3. check kdump status
   - cat /sys/kernel/kexec_*
   - service kdump-tools status

  4. configure NMI
   - sysctl -w kernel.unknown_nmi_panic=1

  5. trigger a crash from host
   - Debug-VM -Name $vmName -InjectNonMaskableInterrupt -ComputerName $hvServer 
-Force

  This case also applies to:
  -Ubuntu 16.10 generation 2(kernel version: 4.8.0-17-generic)
  -Ubuntu 16.04.1(kernel: 4.4.0-38-generic)
  -Ubuntu 14.04.5(kernel: 3.19.0-69-generic)

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

[roots]

Dan,

unfortunately I can't, as the bug won't show up with my new mainboard
anymore, that's why I suspected it to be chipset-specific (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/comments/36).


roots.

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

[Guillaume Mazoyer]

Will do, this testing can be tricky since the issue appears randomly (can take 
minutes, hours, even a day for me).
Can we review the patch for the issue somewhere as well?

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1657733] Re: KVM module handling different per Architecture - s390x

[Tim Gardner]

Building in the KVM drivers for s390x was a direct request from IBM.

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

Title:
  KVM module handling different per Architecture - s390x

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  the Intel KVM module is build as a module, yet OTOH the s390 one is not.
  I asked around and we discussed, quoting the core of the discussion that I'd 
like to be continued here:

   cpaelzer, we want kvm to be available. on x86 there are two modules 
depending on ones cpu features (amd vs intel vs whatever). thus cannot be 
compiled in, as either/or are loaded.
  ...
   infinity, the problem on s390x was that unlike on x86 nothing would 
autoload the module
   xnox: That sounds like a bug to take back to IBM and say "plz fix".
   and it was counter intuitive for millenials like me to do $ sudo 
modprobe kvm; to get libvirt+qemu working
  [...]
   the place to autoload would be /usr/share/qemu/init/qemu-kvm-init 
that is where the others do it
   cpaelzer: Yeah, that's a gross hack because there's no proper 
autoloading.
   true
   cpaelzer: Since that init job only exists if you install qemu, 
modular everywhere would save a tiny bit of boot time on pure guests.  So maybe 
it's worth evaluating
  [...]
   But I'm all for kernel configs being as normalized as possible 
across arches.

  I'm not saying we "should" change anything, but since I wondered about that 
arch difference more people will do so as well.
  So we should consciously evaluate, do we want to:
  1. keep it built-in as it is now
  2. change it to a module and rely on qemu-kvm to load it
  3. change it to a module and let IBM upstream do autoload where it is 
supported

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

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

[Kernel-packages] [Bug 1657734] Re: KVM module handling different per Architecture - ppc64el

[Tim Gardner]

UBUNTU: [Config] powerpc: Add kvm-hv and kvm-pr to the generic inclusion
list

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  KVM module handling different per Architecture - ppc64el

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Hi,
  the Intel KVM module is build as a modules - the core being KVM and then the 
chip vendor specific kvm-intel / kvm-svm.
  On ppc64el the situation is similar there is kvm.ko and then kvm-pr and 
kvm-hv for problem state and hardware virtualization.

  Currently using kvm users can get:
  modprobe: FATAL: Module kvm-hv not found ...

  But when evaluating if I should add a new recommends to qemu-kvm I
  realized this module to kernel package mismatch.

  This is caused by one difference, on intel all is in one package:

  dpkg -S /lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm-amd.ko 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm-intel.ko 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm.ko
  linux-image-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm-amd.ko
  linux-image-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm-intel.ko
  linux-image-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm.ko

  But on ppc64el it is not:

  $ dpkg -S /lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm.ko 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm-hv.ko 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm-pr.ko 
  linux-image-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm.ko
  linux-image-extra-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm-hv.ko
  linux-image-extra-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm-pr.ko

  
  Those should be in just one of these packages.
  At a discussion on #stable-kernel it was suggested that it might just have 
been missed so far:

   smb: I doubt it was a conscious move, but rather that
  kvm.ko is in the module include list (as inherited from x86 builds),
  while the ppc-specific modules are not.

  I don't know, but I wanted to open the bug to get it resolved - and if
  possible all in the base image.

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

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

[Kernel-packages] [Bug 1657734] Re: KVM module handling different per Architecture - ppc64el

[Tim Gardner]

** Also affects: linux (Ubuntu Zesty)
   Importance: Medium
   Status: Confirmed

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  KVM module handling different per Architecture - ppc64el

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  Hi,
  the Intel KVM module is build as a modules - the core being KVM and then the 
chip vendor specific kvm-intel / kvm-svm.
  On ppc64el the situation is similar there is kvm.ko and then kvm-pr and 
kvm-hv for problem state and hardware virtualization.

  Currently using kvm users can get:
  modprobe: FATAL: Module kvm-hv not found ...

  But when evaluating if I should add a new recommends to qemu-kvm I
  realized this module to kernel package mismatch.

  This is caused by one difference, on intel all is in one package:

  dpkg -S /lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm-amd.ko 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm-intel.ko 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm.ko
  linux-image-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm-amd.ko
  linux-image-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm-intel.ko
  linux-image-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm.ko

  But on ppc64el it is not:

  $ dpkg -S /lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm.ko 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm-hv.ko 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm-pr.ko 
  linux-image-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm.ko
  linux-image-extra-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm-hv.ko
  linux-image-extra-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm-pr.ko

  
  Those should be in just one of these packages.
  At a discussion on #stable-kernel it was suggested that it might just have 
been missed so far:

   smb: I doubt it was a conscious move, but rather that
  kvm.ko is in the module include list (as inherited from x86 builds),
  while the ppc-specific modules are not.

  I don't know, but I wanted to open the bug to get it resolved - and if
  possible all in the base image.

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

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

[Kernel-packages] [Bug 1657430] dwalin (amd64) - tests ran: 36, failed: 0

[Brad Figg]

tests ran:  36, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-lowlatency/dwalin__4.4.0-62.83__2017-01-19_16-24-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1650336] Re: NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

[Thomas Fili]

@Seth : Yes, this problem is very confusing

Since posting #8 i used a dedicated test system with a fresh kubuntu 16.04.1 
installation on a well tested system.
During the testing i modify /etc/fstab switching between noauto/auto options of 
nfs shares and later changing server uri to ip address or adding new entries 
from other servers.

And i install the test kernels, of course ;)

Today i install the commit 50f208e18014589971583a8495987194724d56e4
again ... and it crashes as i said before.

Unfortunately the kernel 4.4.0-54 is not available any longer from
offical repos ... so i not able to test this one again ... but maybe
this kernel had also the problem ?!

At the beginning i was very confused because of some kernel crashes ...
not on the first try but on the second or third try.

In fact i found only one old offical kernel that do not have the problem
and this is the 16.04.1 installation kernel 4.0.31

But i will try to find the last working kernel between 4.4.0-34 to
4.4.0-53 tomorrow.

Mainline Kernel 4.10-rc4 and 4.9.4 both work since i modify server uri
to ip address in /etc/stab

> By that I mean you see a crash with nearly identical messages in the
kernel log.

Yes, of cource ... when i wrote the kernel crash this happend allways at
the same place in the log with similar log entries

> If there are multiple different issues going on it's best to try to
focus on one at a time, if possible

That is clear ... for example the resolv the ip from uri problem is secondary.
And there is also another bug with accessing a nfsv4 subshare

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

Title:
  NFS client : kernel 4.4.0-57 crash with nfsv4 enries in /etc/fstab

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

Bug description:
  On (K)ubuntu 16.04.01 (Xenial) Upgrading to kernel 4.4.0-57 the kernel
  crash on boot when in /etc/fstab a nfsv4 entry is active

  When comment the line or set to noauto the kernel boot with no error
  and mounting the nfs shares (after uncomment ) is also possible
  without error

  4.4.0-54 boots without this problem.

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

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

[Kernel-packages] [Bug 1656489] Re: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity

[Mikemecanic]

Live cd in chinese: Kylin 20170119.  Same result

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

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this

[Kernel-packages] [Bug 1656489] PulseList.txt

[Mikemecanic]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1656489/+attachment/4806325/+files/PulseList.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/1656489

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 

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

[Mikemecanic]

apport information

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

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' 

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

[Mikemecanic]

apport information

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

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 

[Kernel-packages] [Bug 1656489] CRDA.txt

[Mikemecanic]

apport information

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

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group 

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

[Mikemecanic]

apport information

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

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' 

[Kernel-packages] [Bug 1656489] ProcCpuinfo.txt

[Mikemecanic]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1656489/+attachment/4806322/+files/ProcCpuinfo.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/1656489

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 

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

[Mikemecanic]

apport information

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

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 

[Kernel-packages] [Bug 1656489] JournalErrors.txt

[Mikemecanic]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1656489/+attachment/4806319/+files/JournalErrors.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/1656489

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 

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

[Mikemecanic]

apport information

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

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 

[Kernel-packages] [Bug 1656489] Re: AMD A10 [Firmware Bug]: APIC id mismatch / All Variants Zesty/Ubiquity

[Mikemecanic]

apport information

** Description changed:

  The following log comes from the installer syslog file.  Since at least
  Dec.16th a message is present in all variants of Ubuntu on startup
  (ubiquity).  Since then, in BIOS mode, all installers have opened in try
  Ubuntu.
  
  There is no incidence on the installation except for xubuntu.  In the Xu
  installer, the skin is light pink.  This bug is not shown in the System
  Log and belongs to ubiquity.
  
  This is a fresh install of 17.04 on an HP desktop. 20170111 build
  
  Visible message on startup in the installer (all of them):
  
  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  
  As seen from Try Ubuntu : /var/log/syslog
  
  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…
  
  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  Package: linux (not installed)
  Tags:  zesty
  Uname: Linux 4.10.0-041000rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: nopasswdlogin
  

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

[Mikemecanic]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1656489/+attachment/4806327/+files/WifiSyslog.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/1656489

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 

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

[Mikemecanic]

apport information

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

Title:
  AMD A10  [Firmware Bug]: APIC id mismatch / All Variants
  Zesty/Ubiquity

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following log comes from the installer syslog file.  Since at
  least Dec.16th a message is present in all variants of Ubuntu on
  startup (ubiquity).  Since then, in BIOS mode, all installers have
  opened in try Ubuntu.

  There is no incidence on the installation except for xubuntu.  In the
  Xu installer, the skin is light pink.  This bug is not shown in the
  System Log and belongs to ubiquity.

  This is a fresh install of 17.04 on an HP desktop. 20170111 build

  Visible message on startup in the installer (all of them):

  [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
  [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3

  As seen from Try Ubuntu : /var/log/syslog

  … [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0
  Jan 13 18:19:25 ubuntu kernel: [0.014913] [Firmware Bug]: CPU0: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.014940] Last level iTLB entries: 4KB 
512, 2MB 1024, 4MB 512
  Jan 13 18:19:25 ubuntu kernel: [0.014941] Last level dTLB entries: 4KB 
1024, 2MB 1024, 4MB 512, 1GB 0
  Jan 13 18:19:25 ubuntu kernel: [0.016004] Freeing SMP alternatives 
memory: 32K (b41ba000 - b41c2000)
  Jan 13 18:19:25 ubuntu kernel: [0.026156] ftrace: allocating 33650 
entries in 132 pages
  Jan 13 18:19:25 ubuntu kernel: [0.039817] smpboot: APIC(10) Converting 
physical 1 to logical package 0
  Jan 13 18:19:25 ubuntu kernel: [0.039819] smpboot: Max logical packages: 2
  Jan 13 18:19:25 ubuntu kernel: [0.040205] ..TIMER: vector=0x30 apic1=0 
pin1=2 apic2=-1 pin2=-1
  Jan 13 18:19:25 ubuntu kernel: [0.184091] smpboot: CPU0: AMD A10-9630P 
RADEON R5, 10 COMPUTE CORES 4C+6G (family: 0x15, model: 0x65, stepping: 0x1)
  Jan 13 18:19:25 ubuntu kernel: [0.184095] Performance Events: Fam15h core 
perfctr, AMD PMU driver.
  Jan 13 18:19:25 ubuntu kernel: [0.184099] ... version:0
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... bit width:  48
  Jan 13 18:19:25 ubuntu kernel: [0.184100] ... generic registers:  6
  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... value mask: 

  Jan 13 18:19:25 ubuntu kernel: [0.184101] ... max period: 
7fff
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... fixed-purpose events:   0
  Jan 13 18:19:25 ubuntu kernel: [0.184102] ... event mask: 
003f
  Jan 13 18:19:25 ubuntu kernel: [0.185039] NMI watchdog: enabled on all 
CPUs, permanently consumes one hw-PMU counter.
  Jan 13 18:19:25 ubuntu kernel: [0.185154] x86: Booting SMP configuration:
  Jan 13 18:19:25 ubuntu kernel: [0.185155]  node  #0, CPUs:  #1
  Jan 13 18:19:25 ubuntu kernel: [0.185290] [Firmware Bug]: CPU1: APIC id 
mismatch. Firmware: 11 CPUID: 1
  Jan 13 18:19:25 ubuntu kernel: [0.185292] [Firmware Bug]: CPU1: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.187463]  #2<3>[0.187735] [Firmware 
Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
  Jan 13 18:19:25 ubuntu kernel: [0.187736] [Firmware Bug]: CPU2: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.190129]  #3<3>[0.190398] [Firmware 
Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
  Jan 13 18:19:25 ubuntu kernel: [0.190399] [Firmware Bug]: CPU3: Using 
firmware package id 1 instead of 0
  Jan 13 18:19:25 ubuntu kernel: [0.192653] x86: Booted up 1 node, 4 CPUs
  Jan 13 18:19:25 ubuntu kernel: [0.192710] smpboot: Total of 4 processors 
activated (20761.91 BogoMIPS)…

  I had never seen this message in Zesty nor in Yakkety before Dec. 16th.  This 
bug is not present in Xenial Xerus.  Will be waiting for a correction in 
Ubiquity.  Thanks in advance!
  Log files of this machine are shown in bug # 1655123 and were given about 2 
hours ago.
  ---
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-11 (2 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' 

[Kernel-packages] [Bug 1657112] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 64, failed: 2

[Brad Figg]

tests ran:  64, failed: 2;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-19_17-21-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Mike Rushton]

KVM was never tested successfully on this particular model. The
virtualization test works fine on all other open power servers we have
in the labs.

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

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  
  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  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: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.959 GHz (cpu 79)
   max: 3.988 GHz (cpu 81)
   avg: 3.974 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1657430] onibi (amd64) - tests ran: 33, failed: 0

[Brad Figg]

tests ran:  33, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/onibi__4.4.0-62.83__2017-01-19_15-52-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument

[Joseph Salisbury]

Thanks for testing, Mike.  Do you know if this is a regression?  Were
there prior kernel versions that did not exhibit 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/1656112

Title:
  Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
  failed: Invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  Upon running the virtualization test from the certification test
  suite, the kvm guest test fails with the following error:

  kvm_init_vcpu failed: Invalid argument

  This same test works on multiple other IBM Power 8 and Openpower
  servers. kvm-ok tells us that kvm virtualization is supported. I have
  tried with SMT enabled and disabled. I have tried the latest cloud
  image as well as previous onces we had saved. I have tried running the
  qemu-system-ppc64 command found below manually with the same error.

  
  The full output from the test is as follows:

  Executing KVM Test
  DEBUG:root:Starting KVM Test
  DEBUG:root:Cloud image location specified: 
http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img.
  DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from 
http://10.1.10.2
  DEBUG:root:Creating cloud user-data
  DEBUG:root:Creating cloud meta-data
  I: -input-charset not specified, using utf-8 (detected in locale settings)
  Total translation table size: 0
  Total rockridge attributes bytes: 331
  Total directory bytes: 0
  Path table size(bytes): 10
  Max brk space used 0
  183 extents written (0 MB)
  DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img
  DEBUG:root:Attaching Cloud config disk
  DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic 
-net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 
-enable-kvm -machine pseries,usb=off -cpu POWER8 -drive 
file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive 
file=seed.iso,if=virtio
  INFO:root:Storing VM console output in 
/home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: ppc64el
  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: Thu Jan 12 22:45:34 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 
Pro
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1
  ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 3709 00:14:665 0 EOF
   2: POSIX  ADVISORY  WRITE 3593 00:14:655 0 EOF
   3: POSIX  ADVISORY  WRITE 1658 00:14:376 0 EOF
   4: FLOCK  ADVISORY  WRITE 3560 00:14:637 0 EOF
   5: POSIX  ADVISORY  WRITE 3571 00:14:640 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri 
Jan 6 17:35:59 UTC 2017
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.959 GHz (cpu 79)
   max: 3.988 GHz (cpu 81)
   avg: 3.974 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=8

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update

[Joseph Salisbury]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc4

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

Title:
  Laptop stick and touchpad problems after linux 4.4 update

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

Bug description:
  Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have 
behaved erratically on my Dell Precision 7510:
  * The trackpoint moves WAY too fast and there don't seem to be any parameters 
I can change in xinput to fix this. It is essentially unusable.
  * The touchpad starts with parameters set incorrectly.
  * Touchpad tap to click is now turned on again and is very sensitive. This I 
can change through xinput but the change is still odd.
  * The two finger scrolling is set incorrectly to be highly sensitive. This I 
can also change through xinput.
  * Two finger scrolling still activates often during normal use of the 
trackpad. To the extent that I had to turn off two finger scrolling to stop 
inadvertent scrolling.

  All of the above behavior is new going from 4.4.0-47 to -53.
  Previously this all worked perfectly on this machine.

  Seems to be symptoms noted by these other users on askubuntu here as
  well: http://askubuntu.com/questions/862527/laptop-stick-mouse-
  problems-after-linux-4-4-update-on-14-04

  The touchpad symptoms I seem to be able to work around my changing
  xinput parameters, but the trackpoint I have not been able to fix at
  all (which is sad since that is my primary mouse device normally).
  Would appreciate any suggestions as to how to revert the old behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpeverill   2813 F pulseaudio
   /dev/snd/controlC0:  jpeverill   2813 F pulseaudio
  Date: Wed Jan 18 10:21:55 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-17 (916 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
  dmi.bios.date: 01/24/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update

[Joseph Salisbury]

Does this bug go away if you boot back into the prior kernel version?


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

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: linux (Ubuntu Xenial)
   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/1657553

Title:
  Laptop stick and touchpad problems after linux 4.4 update

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

Bug description:
  Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have 
behaved erratically on my Dell Precision 7510:
  * The trackpoint moves WAY too fast and there don't seem to be any parameters 
I can change in xinput to fix this. It is essentially unusable.
  * The touchpad starts with parameters set incorrectly.
  * Touchpad tap to click is now turned on again and is very sensitive. This I 
can change through xinput but the change is still odd.
  * The two finger scrolling is set incorrectly to be highly sensitive. This I 
can also change through xinput.
  * Two finger scrolling still activates often during normal use of the 
trackpad. To the extent that I had to turn off two finger scrolling to stop 
inadvertent scrolling.

  All of the above behavior is new going from 4.4.0-47 to -53.
  Previously this all worked perfectly on this machine.

  Seems to be symptoms noted by these other users on askubuntu here as
  well: http://askubuntu.com/questions/862527/laptop-stick-mouse-
  problems-after-linux-4-4-update-on-14-04

  The touchpad symptoms I seem to be able to work around my changing
  xinput parameters, but the trackpoint I have not been able to fix at
  all (which is sad since that is my primary mouse device normally).
  Would appreciate any suggestions as to how to revert the old behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpeverill   2813 F pulseaudio
   /dev/snd/controlC0:  jpeverill   2813 F pulseaudio
  Date: Wed Jan 18 10:21:55 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-17 (916 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 7510
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
  dmi.bios.date: 01/24/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 7510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1657430] modoc (ppc64el) - tests ran: 10, failed: 0

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-62.83-generic/modoc__4.4.0-62.83__2017-01-19_16-21-00/results-index.html

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1657733] Re: KVM module handling different per Architecture - s390x

[Joseph Salisbury]

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

** Tags added: bot-stop-nagging kernel-da-key

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

Title:
  KVM module handling different per Architecture - s390x

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  the Intel KVM module is build as a module, yet OTOH the s390 one is not.
  I asked around and we discussed, quoting the core of the discussion that I'd 
like to be continued here:

   cpaelzer, we want kvm to be available. on x86 there are two modules 
depending on ones cpu features (amd vs intel vs whatever). thus cannot be 
compiled in, as either/or are loaded.
  ...
   infinity, the problem on s390x was that unlike on x86 nothing would 
autoload the module
   xnox: That sounds like a bug to take back to IBM and say "plz fix".
   and it was counter intuitive for millenials like me to do $ sudo 
modprobe kvm; to get libvirt+qemu working
  [...]
   the place to autoload would be /usr/share/qemu/init/qemu-kvm-init 
that is where the others do it
   cpaelzer: Yeah, that's a gross hack because there's no proper 
autoloading.
   true
   cpaelzer: Since that init job only exists if you install qemu, 
modular everywhere would save a tiny bit of boot time on pure guests.  So maybe 
it's worth evaluating
  [...]
   But I'm all for kernel configs being as normalized as possible 
across arches.

  I'm not saying we "should" change anything, but since I wondered about that 
arch difference more people will do so as well.
  So we should consciously evaluate, do we want to:
  1. keep it built-in as it is now
  2. change it to a module and rely on qemu-kvm to load it
  3. change it to a module and let IBM upstream do autoload where it is 
supported

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

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

[Kernel-packages] [Bug 1657606] Re: package linux-image-4.4.0-59-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"


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

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

Title:
  package linux-image-4.4.0-59-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel updates for this 16.04 system keep reporting this error but an
  apt -f install will fix it. Didn't suffer this problem when on 14.04
  previously (upgraded to 16.04 from it)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Thu Jan 19 00:02:25 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=e40cfdf2-c116-4a18-95b6-b0b0c6f6d674
  InstallationDate: Installed on 2014-02-16 (1067 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA69G-S3H
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=46657d9d-c39e-427e-8924-6ea788a4cb78 ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.6
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-59-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to xenial on 2016-10-10 (100 days ago)
  dmi.bios.date: 11/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8e
  dmi.board.name: GA-MA69G-S3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8e:bd11/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA69G-S3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA69G-S3H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA69G-S3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1657734] Re: KVM module handling different per Architecture - ppc64el

[Joseph Salisbury]

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

** Tags added: bot-stop-nagging kernel-da-key

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

Title:
  KVM module handling different per Architecture - ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  the Intel KVM module is build as a modules - the core being KVM and then the 
chip vendor specific kvm-intel / kvm-svm.
  On ppc64el the situation is similar there is kvm.ko and then kvm-pr and 
kvm-hv for problem state and hardware virtualization.

  Currently using kvm users can get:
  modprobe: FATAL: Module kvm-hv not found ...

  But when evaluating if I should add a new recommends to qemu-kvm I
  realized this module to kernel package mismatch.

  This is caused by one difference, on intel all is in one package:

  dpkg -S /lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm-amd.ko 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm-intel.ko 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm.ko
  linux-image-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm-amd.ko
  linux-image-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm-intel.ko
  linux-image-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/x86/kvm/kvm.ko

  But on ppc64el it is not:

  $ dpkg -S /lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm.ko 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm-hv.ko 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm-pr.ko 
  linux-image-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm.ko
  linux-image-extra-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm-hv.ko
  linux-image-extra-4.9.0-11-generic: 
/lib/modules/4.9.0-11-generic/kernel/arch/powerpc/kvm/kvm-pr.ko

  
  Those should be in just one of these packages.
  At a discussion on #stable-kernel it was suggested that it might just have 
been missed so far:

   smb: I doubt it was a conscious move, but rather that
  kvm.ko is in the module include list (as inherited from x86 builds),
  while the ppc-specific modules are not.

  I don't know, but I wanted to open the bug to get it resolved - and if
  possible all in the base image.

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

[Dan Streetman]

Wayne, Guillaume, roots, Stéphane, can any/all of you test with the
-proposed kernel (using directions from comment 39) to verify the bug is
fixed?

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1657281] Re: Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue

[Dragan S.]

Verified:

4.4.0-59-generic
$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync
100+0 records in
100+0 records out
819200 bytes (8.2 GB, 7.6 GiB) copied, 56.7741 s, 144 MB/s

4.4.0-62-generic
$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync
100+0 records in
100+0 records out
819200 bytes (8.2 GB, 7.6 GiB) copied, 31.3783 s, 261 MB/s


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

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

Title:
  Ubuntu xenial - 4.4.0-59-generic i3 I/O performance issue

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  
  [Impact]

   * When running block device I/O on an Amazon i3 system there
 is a performance degradation. A patch with git change id
 87c279e613f848c69b29 that is in Ubuntu-lts-4.8.0 kernel
 series increases I/O performance.

   * Fix should be backported to xenial 4.4 series to avoid more
 support issues being filed.

   * This change gets rid of uneccessary work being performed.

  [Test Case]

   * Steps to reproduce below
 1) partition ephemeral disks 
/sbin/parted -s --align optimal /dev/nvme0n1 mklabel gpt mkpart primary 
0% 100% 
/sbin/parted -s --align optimal /dev/nvme1n1 mklabel gpt mkpart primary 
0% 100% 
/sbin/parted -s --align optimal /dev/nvme2n1 mklabel gpt mkpart primary 
0% 100% 
/sbin/parted -s --align optimal /dev/nvme3n1 mklabel gpt mkpart primary 
0% 100% 

 2) create raid array 
/sbin/mdadm --create /dev/md0 --assume-clean --chunk=2048 --level=10 
--raid-devices=4 /dev/nvme0n1p1 /dev/nvme1n1p1 /dev/nvme2n1p1 /dev/nvme3n1p1 

 3) create pv 
/sbin/pvcreate --force --metadatasize 4092k /dev/md0 

 4) create volume group 
/sbin/vgcreate RDSVG /dev/md0 

 5) create lv 
/sbin/lvcreate -L 2.5T -n RDSRAIDLV RDSVG 

 5) test I/O
sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync

  [Regression Potential]

   * No known regression potential.

  [Original Description]

  When we were doing testing on i3, we noticed that it is taking
  significantly longer to perform operations when using software RAID
  than without, we believe this is resolved in an upstream commit:
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  xenial.git/commit/?id=87c279e613f848c69b29d49de8df3f4f56da

  So stock 4.4.0-59-generic performs ok:
  $ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k count=100 && sync 
  sudo: unable to resolve host ip-10-0-85-167
  100+0 records in
  100+0 records out
  819200 bytes (8.2 GB, 7.6 GiB) copied, 54.3711 s, 151 MB/s

  and the patch you originally providing works a little bit better (as 
expected):
  $ uname -a
  Linux ip-10-0-85-167 4.4.0-57-generic 
#78hf00v20170110b0h3199a6e718db-Ubuntu SMP Tue Jan 10 02:53: x86_64 x86_64 
x86_64 GNU/Linux
  ubuntu@ip-10-0-85-167:~$ sudo dd if=/dev/zero of=/dev/RDSVG/RDSRAIDLV bs=8k 
count=100 && sync 
  sudo: unable to resolve host ip-10-0-85-167
  100+0 records in
  100+0 records out
  819200 bytes (8.2 GB, 7.6 GiB) copied, 31.4108 s, 261 MB/s

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

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

[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

[Rolf Leggewie]

On 07.01.2017 01:38, Luke-Jr wrote:
> On Friday, January 06, 2017 5:22:34 PM Joseph Salisbury wrote:
>> btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in
>> btrfs_ioctl
>>
>> However, this commit introduced a new regression.  With this commit
>> applied, "btrfs fi show" no longer works and the btrfs snapshot
>> functionality breaks.
> I don't see how this is even possibly related. Furthermore,
> "btrfs fi show" as  well as snapshots seem to work just fine
> for me.

Maybe the relation isn't immediately obvious from code inspection alone,
nonetheless it demonstrably is there.  That commit is what introduced
the described regression.  Apparently, it's only present with an amd64
kernel and 32-bit userspace.

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in linux:
  Unknown
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Kernel-packages] [Bug 1654319] Re: kernel BUG at /build/linux-_qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413

[Mikołaj Kowalski]

This is a fresh installation.

I've tested 
Linux version 4.10.0-041000rc4-generic (kernel@gloin) (gcc version 6.2.0 
20161005 (Ubuntu 6.2.0-5ubuntu12) ) #201701152031 SMP Mon Jan 16 01:33:39 UTC 
2017

First of all, I had problem booting this kernel on VMWare. The screen
goes black after few seconds. I've attached dmesg. Appending nomodeset
to kernel commandline helps though. You can file another bug if You want
to.

Second, I this I was able to reproduce the bug on mentioned kernel. I
run test using JMeter and the system hangs and restarts. I am not sure,
because I do not have kernel dump. Where can I find debug symbols for
the kernel you wanted me to test?

sty 19 17:54:25 jenkins kdump-tools[1259]: Starting kdump-tools:  * running 
makedumpfile -c -d 31 /proc/vmcore /var/crash/201701191754/dump-incomplete
sty 19 17:54:25 jenkins kdump-tools[1259]: check_release: Can't get the kernel 
version.
sty 19 17:54:25 jenkins kdump-tools[1259]: The kernel version is not supported.
sty 19 17:54:25 jenkins kdump-tools[1259]: The makedumpfile operation may be 
incomplete.
sty 19 17:54:25 jenkins kdump-tools[1259]: makedumpfile Failed.
sty 19 17:54:25 jenkins kdump-tools[1259]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
sty 19 17:54:25 jenkins kdump-tools[1348]: makedumpfile failed, falling back to 
'cp'
sty 19 17:54:52 jenkins kernel: hpet_rtc_timer_reinit: 37 callbacks suppressed
sty 19 17:54:53 jenkins kernel: hpet1: lost 1725 rtc interrupts
sty 19 17:55:04 jenkins kdump-tools[1259]:  * kdump-tools: saved vmcore in 
/var/crash/201701191754
sty 19 17:55:04 jenkins kernel: hpet1: lost 759 rtc interrupts
sty 19 17:55:04 jenkins kdump-tools[1362]: saved vmcore in 
/var/crash/201701191754
sty 19 17:55:04 jenkins kdump-tools[1259]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701191754/dmesg.201701191754
sty 19 17:55:04 jenkins kernel: hpet1: lost 14 rtc interrupts
sty 19 17:55:04 jenkins kdump-tools[1259]: check_release: Can't get the kernel 
version.
sty 19 17:55:04 jenkins kdump-tools[1259]: The kernel version is not supported.
sty 19 17:55:04 jenkins kdump-tools[1259]: The makedumpfile operation may be 
incomplete.
sty 19 17:55:04 jenkins kdump-tools[1259]: makedumpfile Failed.
sty 19 17:55:04 jenkins kdump-tools[1365]: makedumpfile --dump-dmesg failed. 
dmesg content will be unavailable
sty 19 17:55:04 jenkins kdump-tools[1259]:  * kdump-tools: makedumpfile 
--dump-dmesg failed. dmesg content will be unavailable
sty 19 17:55:04 jenkins kdump-tools[1259]:  * kdump-tools: failed to save dmesg 
content in /var/crash/201701191754
sty 19 17:55:04 jenkins kdump-tools[1366]: failed to save dmesg content in 
/var/crash/201701191754
sty 19 17:55:04 jenkins kdump-tools[1259]: Thu, 19 Jan 2017 17:55:04 +0100


I can provide vmcore if you want me to.

** Attachment added: "kernel 4.10-rc4 fails to boot"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654319/+attachment/4806301/+files/serial%282%29.out

** Tags added: kernel-bug-exists-upstream

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

Title:
  kernel BUG at /build/linux-
  _qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello everyone,

  I have jenkins installed with an apache frontend. Sometimes, after
  making few GET requests whole system crashes and restarts.

  ESXi host version 6.5, virtual hardware version 13.

  I've found similar bug report here
  https://bugzilla.kernel.org/show_bug.cgi?id=191201

  
  [ 6544.559660] [ cut here ]
  [ 6544.559694] kernel BUG at 
/build/linux-_qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413!
  [ 6544.559728] invalid opcode:  [#1] SMP
  [ 6544.559745] Modules linked in: xt_multiport vmw_vsock_vmci_transport vsock 
ppdev vmw_balloon joydev coretemp input_leds serio_raw nfit shpchp i2c_piix4 
vmw_vmci parport_pc parport mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 
nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables 
nf_conntrack_netbios_ns ib_iser rdma_cm nf_conntrack_broadcast iw_cm nf_nat_ftp 
ib_cm nf_nat ib_core nf_conntrack_ftp nf_conntrack iptable_filter configfs 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic
  [ 6544.560172]  usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
vmwgfx ttm aesni_intel aes_x86_64 lrw glue_helper ablk_helper cryptd 
drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops vmxnet3 
ahci libahci mptspi drm mptscsih mptbase scsi_transport_spi pata_acpi fjes
  [ 

[Kernel-packages] [Bug 1650058] Re: [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and image

[Tim Gardner]

Joshua - I looked at mlnx-ofed-kernel-
dkms_3.4-OFED.3.4.2.0.0.1.g30039f7_all.deb in some detail. It appears
that nearly all of the drivers contained therein are replacements for
existing drivers in the linux v4.4 kernel. Even without looking at the
code for these replacement drivers, I can say that a patch series
integrating these changes will certainly _not_ qualify under the Ubuntu
SRU policy. There are a number of consumers of the Mellanox Infiniband
stack for which these changes might cause regression.

We could certainly merge these changes in an Azure specific kernel or
flavor, but not as part of the generic distribution kernel binary.

rtg

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

Title:
  [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel
  and image

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

Bug description:
  In order to have the correct VF driver to support SR-IOV in Azure, the
  Mellanox OFED distribution needs to be included in the kernel and the
  image. Mellanox's drivers are not upstream, but they are available
  from here:

  
https://www.mellanox.com/page/products_dyn?product_family=26=linux_sw_drivers=3nnhohirh5htv6dnp1uk7tf487

  While this configuration is not explicitly listed as supported in the
  release notes, Microsoft and Mellanox engineers are working on the
  corresponding Windows Server 2016 PF driver to support this VF driver
  in operation in Ubuntu guests.

  I file file a corresponding rebase request to pick up the PCI
  passthrough and other SR-IOV work done for the Hyper-V capabilities in
  the upstream 4.9 kernel.

  Only 64-bit support for Ubuntu 16.04's HWE kernel is needed.

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

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

[Kernel-packages] [Bug 1656618] Re: Any key pressed opens shutdown dialog (Asus X205TA)

[harry]

adding i2c_hid.debug=1 as a boot parameter gives the following output:
[4.572059] i2c_hid i2c-PDEC3393:00: Fetching the HID descriptor
[4.572065] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f1 00
[4.575576] i2c_hid i2c-PDEC3393:00: HID Descriptor: 1e 00 00 01 b4 00 f2 00 
f3 00 0e 00 f4 00 04 00 f5 00 f6 00 05 0b 85 85 01 00 00 00 00 00
[4.575685] i2c_hid i2c-PDEC3393:00: entering i2c_hid_parse
[4.575689] i2c_hid i2c-PDEC3393:00: i2c_hid_hwreset
[4.575692] i2c_hid i2c-PDEC3393:00: i2c_hid_set_power
[4.575695] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 00 08
[4.581210] i2c_hid i2c-PDEC3393:00: resetting...
[4.581214] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 00 01
[4.581660] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: waiting...
[9.701087] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: finished.
[9.701099] i2c_hid i2c-PDEC3393:00: failed to reset device.
[9.708842] i2c_hid i2c-PDEC3393:00: i2c_hid_set_power
[9.708854] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 01 08
[   10.714178] i2c_hid i2c-PDEC3393:00: i2c_hid_hwreset
[   10.714190] i2c_hid i2c-PDEC3393:00: i2c_hid_set_power
[   10.714201] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 00 08
[   10.714821] i2c_hid i2c-PDEC3393:00: resetting...
[   10.714833] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: cmd=f5 00 00 01
[   10.718836] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: waiting...
[   15.887586] i2c_hid i2c-PDEC3393:00: __i2c_hid_command: finished.
[   15.887597] i2c_hid i2c-PDEC3393:00: failed to reset device.
..
..
[   29.294255] i2c_hid: probe of i2c-PDEC3393:00 failed with error -61
[   29.465100] i2c_hid i2c-ELAN0100:00: Fetching the HID descriptor
[   29.465104] i2c_hid i2c-ELAN0100:00: __i2c_hid_command: cmd=01 00
[   29.468290] i2c_hid i2c-ELAN0100:00: HID Descriptor: 1e 00 00 01 6a 00 02 00 
03 00 1e 00 04 00 00 00 05 00 06 00 f3 04 01 04 0a 00 00 00 00 00
[   29.596520] i2c_designware 80860F41:04: I2C bus managed by PUNIT
[   29.772290] elan_i2c i2c-ELAN0100:00: Elan Touchpad: Module ID: 0x0026, 
Firmware: 0x000a, Sample: 0x0001, IAP: 0x
[   29.773767] input: Elan Touchpad as 
/devices/platform/80860F41:03/i2c-11/i2c-ELAN0100:00/input/input7
[   31.145688] elan_i2c i2c-ELAN0100:00: Elan Touchpad: Module ID: 0x0026, 
Firmware: 0x000a, Sample: 0x0001, IAP: 0x
[   31.145966] input: Elan Touchpad as 
/devices/platform/80860F41:03/i2c-11/i2c-ELAN0100:00/input/input11

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

Title:
  Any key pressed opens shutdown dialog (Asus X205TA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of 16.10 on my Asus X205TA, any key pressed on
  the built-in keyboard brings up the shutdown dialog. The system works
  fine with a USB keyboard.

  The installed kernel was 4.8.0-34-generic. Booting with
  4.8.0-22-generic, the keyboard works fine.

  Other users have confirmed the bug in Fedora and Tails 
(https://ubuntuforums.org/showthread.php?t=2254322=13594241#post13594241) and 
in 16.10 MATE 
(https://ubuntuforums.org/showthread.php?t=2254322=13594617#post13594617).
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  Lsusb:
   Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 8087:07e6 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X205TA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=05a20fbf-3084-4535-bae3-bed719df662c ro quiet splash 
intel_max.idle_cstate=1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X205TA.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X205TA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Kernel-packages] [Bug 1655065] Re: Regression: Suspend broken on Thinkpad P50 with 4.8.0-32-generic

[Guillaume Martres]

Bug closed upstream since 4.8 is EOL and the bug does not appear in 4.9
and 4.10. I'm willing to do a bisect to find the problematic commit, but
only if I can get some guarantee that this will lead to someone taking
the time to review the result and do what's needed to get a fix in
16.10. Otherwise I'm personally fine running a mainline 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/1655065

Title:
  Regression: Suspend broken on Thinkpad P50 with 4.8.0-32-generic

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

Bug description:
  Suspending to ram and to disk works perfectly fine on the
  4.8.0-30-generic kernel. On 4.8.0-32-generic it works some of the
  time, but most of the time it freezes the machine. When the machine is
  frozen the screen is turned off, the power button light is on, but the
  machine does not respond to any input including the Magic SysRq keys,
  the only thing that can be done is powering off the machine by
  pressing the power button for 10 seconds. This happens both with
  suspend-to-ram and suspend-to-disk.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  smarter1803 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Jan  9 16:42:48 2017
  HibernationDevice: RESUME=UUID=a1a154db-3fbe-43e4-92d1-987022206599
  InstallationDate: Installed on 2012-09-28 (1563 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120928)
  MachineType: LENOVO 20ENCTO1WW
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=bf5c18a6-40c4-4768-82bc-5c47a1324be5 ro ipv6.disable=1 
i915.enable_psr=0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-04-15 (269 days ago)
  dmi.bios.date: 08/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET57W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ENCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET57W(1.30):bd08/03/2016:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20ENCTO1WW
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Allen Wild]

I manage a set of build servers for CPU/IO intensive builds using
Yocto/OpenEmbedded. Ubuntu 14.04.5 with the 4.4 Xenial kernel. After
updating to 4.4.0-59 the builds started failing because of the OOM
killer.

Rolling back to 4.4.0-57 fixed the OOMs for me.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

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

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  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: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1657112] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 141, failed: 0

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-36.38-generic/ms10-34-mcdivittB0-kernel__4.8.0-36.38__2017-01-19_16-06-00/results-index.html

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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

[Kernel-packages] [Bug 1657430] Re: linux: 4.4.0-62.83 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.4.0-62.83 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-62.83 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
  derivative-trackers-created: 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/1657430/+subscriptions

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

[Kernel-packages] [Bug 1657112] Re: linux: 4.8.0-36.38 -proposed tracker

[Steve Beattie]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.8.0-36.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  New

Bug description:
  This bug is for tracking the 4.8.0-35.37 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
  derivative-trackers-created: 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/1657112/+subscriptions

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