[Kernel-packages] [Bug 1692589] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 9, failed: 0

[Brad Figg]

tests ran:   9, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/ms10-35-mcdivittB0-kernel__4.8.0-54.57__2017-05-27_04-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

[Kernel-packages] [Bug 1501884] Re: linux-image-extra-*-generic postrm script runs install actions

[Jarno Suni]

Still, it might make more sense to run the scripts in
/etc/kernel/postrm.d and program the exceptions for linux-image-extra
there. For example, check in /etc/kernel/postrm.d/zz-update-grub if we
are removing a linux-image-extra package, and only update grub, if not,
right? And in /etc/kernel/postrm.d/initramfs-tools create initrd.img
instead of removing it, if removing  a linux-image-extra package.

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

Title:
  linux-image-extra-*-generic postrm script runs install actions

Status in linux package in Ubuntu:
  Confirmed
Status in linux-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  The postrm maintainer script in the binary packages linux-image-
  extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of
  those in /etc/kernel/postrm.d.

  This can have all sorts of undesirable consequences depending on what
  other packages add to those directories, but I noticed it because it
  caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong
  decisions leaving my servers with only one installed kernel left.

  Cheers,
  Seb

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

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

[Kernel-packages] [Bug 1691146] rizzo (amd64) - tests ran: 21, failed: 0

[Brad Figg]

tests ran:  21, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-22.24-generic/rizzo__4.10.0-22.24__2017-05-27_04-01-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/1691146

Title:
  linux: 4.10.0-22.24 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1691149,1691152
  derivatives: 1691153
  -- swm properties --
  boot-testing-requested: 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/1691146/+subscriptions

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

[Kernel-packages] [Bug 1692589] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 10, failed: 1

[Brad Figg]

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/ms10-35-mcdivittB0-kernel__4.8.0-54.57__2017-05-27_03-34-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

[Kernel-packages] [Bug 1693962] Re: linux: 4.11.0-5.10 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Description changed:

  This bug is for tracking the 4.11.0-5.10 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
  
- kernel-phase:Packaging
- kernel-phase-changed:Saturday, 27. May 2017 02:03 UTC
- 
  -- swm properties --
  phase: Packaging
+ kernel-phase:Uploaded
+ kernel-phase-changed:Saturday, 27. May 2017 04:33 UTC

** Description changed:

  This bug is for tracking the 4.11.0-5.10 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 --
- phase: Packaging
- kernel-phase:Uploaded
- kernel-phase-changed:Saturday, 27. May 2017 04:33 UTC
+ phase: Uploaded

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

Title:
  linux: 4.11.0-5.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.11.0-5.10 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 --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40

[Launchpad Bug Tracker]

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

** Changed in: linux (Ubuntu Xenial)
   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/1614953

Title:
  hw csum failure when IPv6 interfaces configured in
  netdev_rx_csum_fault+0x38/0x40

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

Bug description:
  Since I started using IPv6 I noticed the following kernel error:

  Thu Aug 18 15:05:01 2016] : hw csum failure
  [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P 
  OE   4.4.0-34-generic #53-Ubuntu
  [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
  [Thu Aug 18 15:05:01 2016]  0286 c05989f2 
8807573dfcd0 813f11b3
  [Thu Aug 18 15:05:01 2016]   0008 
8807573dfce8 8171f6e8
  [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 
8171639b fe091360
  [Thu Aug 18 15:05:01 2016] Call Trace:
  [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
  [Thu Aug 18 15:05:01 2016]  [] 
netdev_rx_csum_fault+0x38/0x40
  [Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
  [Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
  [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
  [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
  [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
  [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
  [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
  [Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  It repeats periodically:

  $ dmesg -T | grep 'hw csum failure' | wc -l
  201

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 19 13:47:54 2016
  HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
  InstallationDate: Installed on 2016-04-24 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/rootpool-rootvol ro intel_iommu=on
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40

[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/1614953

Title:
  hw csum failure when IPv6 interfaces configured in
  netdev_rx_csum_fault+0x38/0x40

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

Bug description:
  Since I started using IPv6 I noticed the following kernel error:

  Thu Aug 18 15:05:01 2016] : hw csum failure
  [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P 
  OE   4.4.0-34-generic #53-Ubuntu
  [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
  [Thu Aug 18 15:05:01 2016]  0286 c05989f2 
8807573dfcd0 813f11b3
  [Thu Aug 18 15:05:01 2016]   0008 
8807573dfce8 8171f6e8
  [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 
8171639b fe091360
  [Thu Aug 18 15:05:01 2016] Call Trace:
  [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
  [Thu Aug 18 15:05:01 2016]  [] 
netdev_rx_csum_fault+0x38/0x40
  [Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
  [Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
  [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
  [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
  [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
  [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
  [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
  [Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  It repeats periodically:

  $ dmesg -T | grep 'hw csum failure' | wc -l
  201

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 19 13:47:54 2016
  HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
  InstallationDate: Installed on 2016-04-24 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/rootpool-rootvol ro intel_iommu=on
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40

[Launchpad Bug Tracker]

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

** Changed in: linux (Ubuntu Yakkety)
   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/1614953

Title:
  hw csum failure when IPv6 interfaces configured in
  netdev_rx_csum_fault+0x38/0x40

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

Bug description:
  Since I started using IPv6 I noticed the following kernel error:

  Thu Aug 18 15:05:01 2016] : hw csum failure
  [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P 
  OE   4.4.0-34-generic #53-Ubuntu
  [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be 
filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013
  [Thu Aug 18 15:05:01 2016]  0286 c05989f2 
8807573dfcd0 813f11b3
  [Thu Aug 18 15:05:01 2016]   0008 
8807573dfce8 8171f6e8
  [Thu Aug 18 15:05:01 2016]  0074 8807573dfd30 
8171639b fe091360
  [Thu Aug 18 15:05:01 2016] Call Trace:
  [Thu Aug 18 15:05:01 2016]  [] dump_stack+0x63/0x90
  [Thu Aug 18 15:05:01 2016]  [] 
netdev_rx_csum_fault+0x38/0x40
  [Thu Aug 18 15:05:01 2016]  [] 
skb_copy_and_csum_datagram_msg+0xeb/0x100
  [Thu Aug 18 15:05:01 2016]  [] udpv6_recvmsg+0x233/0x670
  [Thu Aug 18 15:05:01 2016]  [] inet_recvmsg+0x7e/0xb0
  [Thu Aug 18 15:05:01 2016]  [] sock_recvmsg+0x3b/0x50
  [Thu Aug 18 15:05:01 2016]  [] SYSC_recvfrom+0xe1/0x160
  [Thu Aug 18 15:05:01 2016]  [] ? wake_up_q+0x70/0x70
  [Thu Aug 18 15:05:01 2016]  [] SyS_recvfrom+0xe/0x10
  [Thu Aug 18 15:05:01 2016]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

  It repeats periodically:

  $ dmesg -T | grep 'hw csum failure' | wc -l
  201

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 19 13:47:54 2016
  HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2
  InstallationDate: Installed on 2016-04-24 (116 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/rootpool-rootvol ro intel_iommu=on
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd11/14/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1675540] Re: i2c i2c-1: sendbytes: NAK bailout.

[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/1675540

Title:
  i2c i2c-1: sendbytes: NAK bailout.

Status in linux package in Ubuntu:
  Expired

Bug description:
  This bug still exists and looks like it was identified as part of the
  Nouveau video driver, experienced now with Ubuntu 16.10.

  Timed out (original?) bug thread:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1015165

  Trackback on forums with no clear resolution:
  https://ubuntuforums.org/showthread.php?t=2074280

  
  Details:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.10
  Release:16.10
  Codename:   yakkety

  $ lsmod | grep 'i2c'
  i2c_piix4  24576  0
  i2c_algo_bit   16384  1 nouveau
  support@apollo:~$ lsmod | grep 'nouveau'
  nouveau  1572864  1
  mxm_wmi16384  1 nouveau
  video  40960  1 nouveau
  i2c_algo_bit   16384  1 nouveau
  ttm   102400  1 nouveau
  drm_kms_helper167936  1 nouveau
  drm   368640  4 nouveau,ttm,drm_kms_helper
  wmi16384  2 mxm_wmi,nouveau

  $ uname -a
  Linux apollo 4.8.0-40-generic #43-Ubuntu SMP Thu Feb 23 16:01:19 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  
  $ lspci | grep -i 'nvidia'
  01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] 
(rev a2)

  dmesg spam :

  [74243.701317] Raw EDID:
  [74243.702234]  78 ee c1 25 a3 56 4b 99 27 11 50 54 bf ef 80 95
  [74243.703153]  00 71 4f 81 80 95 0f 01 01 01 01 01 01 01 01 9a
  [74243.704050]  29 a0 d0 51 84 22 30 50 98 36 00 98 ff 10 00 00
  [74243.704925]  1c 00 00 00 fd 00 38 4b 1e 53 0e 00 0a 20 20 20
  [74243.705816]  20 20 20 00 00 00 ff 00 37 33 37 33 31 38 33 49
  [74243.706732]  32 38 57 53 01 00 00 00 fc 00 44 45 4c 4c 20 45
  [74243.707617]  31 39 38 57 46 50 0a 00 3a ff ff ff ff ff ff ff
  [74243.708508]  ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
  [74243.65] i2c i2c-1: sendbytes: NAK bailout.
  [74246.557345] i2c i2c-1: sendbytes: NAK bailout.
  [74246.843767] i2c i2c-1: sendbytes: NAK bailout.
  [74247.128195] i2c i2c-1: sendbytes: NAK bailout.
  [74249.366638] i2c i2c-1: sendbytes: NAK bailout.
  [74250.883810] i2c i2c-1: sendbytes: NAK bailout.
  [74251.295261] i2c i2c-1: sendbytes: NAK bailout.
  [74252.939101] i2c i2c-1: sendbytes: NAK bailout.
  [74254.200165] i2c i2c-1: sendbytes: NAK bailout.
  [74254.885717] i2c i2c-1: readbytes: ack/nak timeout
  [74255.169703] i2c i2c-1: readbytes: ack/nak timeout
  [74255.737676] i2c i2c-1: readbytes: ack/nak timeout
  [74257.450821] i2c i2c-1: sendbytes: NAK bailout.

  No packages :
  $ dpkg --list | grep  -i 'nvidia'
  $ dpkg --list | grep  -i 'nouveau'
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.8.0-41-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', 
'/dev/snd/midiC1D0', '/dev/snd/pcmC1D3c', '/dev/snd/pcmC1D3p', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  Card1.Amixer.info: Error: [Errno 2] No such file or directory
  Card1.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=/dev/mapper/mike--ubuntu--vg-swap_1
  InstallationDate: Installed on 2017-03-01 (24 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: ECS A780GM-A Ultra
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic 
root=/dev/mapper/mike--ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-41-generic N/A
   linux-backports-modules-4.8.0-41-generic  N/A
   linux-firmware1.161.1
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  yakkety
  Uname: Linux 4.8.0-41-generic 

[Kernel-packages] [Bug 1675204] Re: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP)

[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/1675204

Title:
  Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP)

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

Bug description:
  I have a very strange issue related to Intel graphics drivers (i915)
  with 3 connected on-board displays.

  I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop
  computer running on a i7-6700K processor and on-board graphics (Mobo:
  AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG
  display (via onboard DP port), a 1920x1200 Dell display (via on-board
  HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter).

  If I just connect my desktop to the first two displays (not the TV),
  everything works fine (except some minor issues). However, if I
  connect the 4k TV, even the TV is not on, my graphics starts to
  flicker every 5 min-ish (window theme turns off and then turns quickly
  back on); after a few flickering, the window theme will disappear, and
  the screen becomes weird - my chrome window will not fresh, or show
  blank boxes etc.

  If I disconnect the DVI connector to the TV (just use the LG+Dell
  dual-display), flickering and crash will not appear.

  I want to mention that, when I connect the computer to all 3 displays,
  I was actually able to get video output to all displays (I used arandr
  to configure them). I can even get 4k output to the 4k TV at 30Hz.

  I can't find a useful log entry when the flicking or graphics crash
  happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F
  (log attached at the end), but I can see many similar errors in my log
  and the appearance is not correlated to the flickering/crash. The
  "pipe A FIFO underrun" issue was previously reported in Bug#1550779.

  I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my
  Xorg.0.log file constantly, I also do not see an consistent mapping
  between the log entry and the flickering.

  Can anyone tell me how to properly debug this? what can I do to get a
  log for what was wrong?

  ---

  [  145.033055] WARNING: CPU: 2 PID: 1804 at 
/build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675
 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]()
  [  145.033058] WARN_ON(!wm_changed)
  [  145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev 
input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main 
v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) 
uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi 
coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) 
nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw 
gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi 
cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo 
auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc 
intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel 
btintel intel_lpss_ac
 pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops 
syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi 
kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp 
pps_core ahci nvme libahci fjes
  [  145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW  OE   
4.4.0-66-generic #87~14.04.1-Ubuntu
  [  145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016
  [  145.033290]   88086e5879a0 813dc80c 
88086e5879e8
  [  145.033295]  c0556700 88086e5879d8 8107e9d6 
88086d898000
  [  145.033300]  88086d89b000 0004 880871924b78 
88086e587a64
  [  145.033305] Call Trace:
  [  145.033311]  [] dump_stack+0x63/0x87
  [  145.033317]  [] warn_slowpath_common+0x86/0xc0
  [  145.033323]  [] warn_slowpath_fmt+0x4c/0x50
  [  145.033358]  [] ? ironlake_irq_handler+0x660/0xba0 
[i915_bpo]
  [  145.033393]  [] skl_update_other_pipe_wm+0x191/0x1a0 
[i915_bpo]
  [  145.033435]  [] skl_update_wm+0x19a/0x6f0 [i915_bpo]
  [  145.033491]  [] ? chv_write8+0x390/0x390 [i915_bpo]
  [  145.033551]  [] ? skl_ddi_pll_disable+0x70/0x80 
[i915_bpo]
  [  145.033590]  [] intel_update_watermarks+0x1e/0x30 
[i915_bpo]
  [  145.033649]  [] 

[Kernel-packages] [Bug 1675204] Re: Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP)

[Launchpad Bug Tracker]

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

** Changed in: linux (Ubuntu Xenial)
   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/1675204

Title:
  Intel HD graphics crashes when connecting to 3 outputs (DVI+HDMI+DP)

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

Bug description:
  I have a very strange issue related to Intel graphics drivers (i915)
  with 3 connected on-board displays.

  I have a Xubuntu (14.04 LTS with HWE on 4.4.0-66 kernel) desktop
  computer running on a i7-6700K processor and on-board graphics (Mobo:
  AsRock z170 extreme4). I connect it to 3 displays - a 3440x1400 LG
  display (via onboard DP port), a 1920x1200 Dell display (via on-board
  HDMI), and a Sony 4k TV (via onboard DVI and a DVI-to-HDMI adapter).

  If I just connect my desktop to the first two displays (not the TV),
  everything works fine (except some minor issues). However, if I
  connect the 4k TV, even the TV is not on, my graphics starts to
  flicker every 5 min-ish (window theme turns off and then turns quickly
  back on); after a few flickering, the window theme will disappear, and
  the screen becomes weird - my chrome window will not fresh, or show
  blank boxes etc.

  If I disconnect the DVI connector to the TV (just use the LG+Dell
  dual-display), flickering and crash will not appear.

  I want to mention that, when I connect the computer to all 3 displays,
  I was actually able to get video output to all displays (I used arandr
  to configure them). I can even get 4k output to the 4k TV at 30Hz.

  I can't find a useful log entry when the flicking or graphics crash
  happens. I can only see a "CPU pipe A FIFO underrun" for pipe A/B/F
  (log attached at the end), but I can see many similar errors in my log
  and the appearance is not correlated to the flickering/crash. The
  "pipe A FIFO underrun" issue was previously reported in Bug#1550779.

  I also see "intel(0): HDMI max TMDS frequency 30KHz" entry in my
  Xorg.0.log file constantly, I also do not see an consistent mapping
  between the log entry and the flickering.

  Can anyone tell me how to properly debug this? what can I do to get a
  log for what was wrong?

  ---

  [  145.033055] WARNING: CPU: 2 PID: 1804 at 
/build/linux-lts-xenial-drAJVo/linux-lts-xenial-4.4.0/ubuntu/i915/intel_pm.c:3675
 skl_update_other_pipe_wm+0x191/0x1a0 [i915_bpo]()
  [  145.033058] WARN_ON(!wm_changed)
  [  145.033060] Modules linked in: nfsv3 pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) autofs4 rpcsec_gss_krb5 nfsv4 usblp joydev 
input_leds ti_usb_3410_5052 usbserial hid_generic gspca_ov534 gspca_main 
v4l2_common videodev media snd_usb_audio snd_usbmidi_lib usbhid 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nvidia_uvm(POE) 
uas usb_storage intel_rapl x86_pkg_temp_thermal intel_powerclamp mxm_wmi 
coretemp kvm_intel bnep kvm rfcomm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_hda_intel snd_hda_codec snd_hda_core nvidia_drm(POE) 
nvidia_modeset(POE) snd_hwdep aesni_intel snd_pcm aes_x86_64 nvidia(POE) lrw 
gf128mul snd_seq_midi snd_seq_midi_event glue_helper ablk_helper snd_rawmidi 
cryptd snd_seq snd_seq_device snd_timer serio_raw snd soundcore nfsd i915_bpo 
auth_rpcgss nfs_acl nfs binfmt_misc lockd grace 8250_fintek hci_uart sunrpc 
intel_ips drm_kms_helper btbcm pinctrl_sunrisepoint btqca fscache pinctrl_intel 
btintel intel_lpss_ac
 pi bluetooth i2c_hid intel_lpss drm hid video i2c_algo_bit fb_sys_fops 
syscopyarea sysfillrect sysimgblt shpchp mei_me mei mac_hid acpi_als wmi 
kfifo_buf industrialio acpi_pad parport_pc ppdev lp parport e1000e psmouse ptp 
pps_core ahci nvme libahci fjes
  [  145.033284] CPU: 2 PID: 1804 Comm: Xorg Tainted: PW  OE   
4.4.0-66-generic #87~14.04.1-Ubuntu
  [  145.033287] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./Z170 Extreme4, BIOS P7.00 09/09/2016
  [  145.033290]   88086e5879a0 813dc80c 
88086e5879e8
  [  145.033295]  c0556700 88086e5879d8 8107e9d6 
88086d898000
  [  145.033300]  88086d89b000 0004 880871924b78 
88086e587a64
  [  145.033305] Call Trace:
  [  145.033311]  [] dump_stack+0x63/0x87
  [  145.033317]  [] warn_slowpath_common+0x86/0xc0
  [  145.033323]  [] warn_slowpath_fmt+0x4c/0x50
  [  145.033358]  [] ? ironlake_irq_handler+0x660/0xba0 
[i915_bpo]
  [  145.033393]  [] skl_update_other_pipe_wm+0x191/0x1a0 
[i915_bpo]
  [  145.033435]  [] skl_update_wm+0x19a/0x6f0 [i915_bpo]
  [  145.033491]  [] ? chv_write8+0x390/0x390 [i915_bpo]
  [  145.033551]  [] ? skl_ddi_pll_disable+0x70/0x80 
[i915_bpo]
  [  145.033590]  [] intel_update_watermarks+0x1e/0x30 
[i915_bpo]
  [  145.033649]  [] 

[Kernel-packages] [Bug 1669758] Re: Centrino Wireless-N 1000 not working on 16.10

[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/1669758

Title:
  Centrino Wireless-N 1000 not working on 16.10

Status in linux package in Ubuntu:
  Expired

Bug description:
  Summary
  Wifi is not working on Centrino Wireless-N 1000 not working on 16.10, but 
does work on windows.

  Please see following

  http://paste.ubuntu.com/24101344/
  
http://askubuntu.com/questions/887257/device-not-ready-wifi-not-working-on-ubuntu-16-10
  https://ubuntuforums.org/showthread.php?t=2354116=13615105#post13615105
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  anton  2691 F pulseaudio
   /dev/snd/controlC0:  anton  2691 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=4f9bb031-cd71-4106-8408-bc6b09dc34aa
  InstallationDate: Installed on 2017-02-25 (29 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 4384WHB
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-41-generic N/A
   linux-backports-modules-4.8.0-41-generic  N/A
   linux-firmware1.161.1
  Tags:  yakkety
  Uname: Linux 4.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET55WW (1.18 )
  dmi.board.name: 4384WHB
  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:bvr6MET55WW(1.18):bd04/21/2010:svnLENOVO:pn4384WHB:pvrThinkPadT510:rvnLENOVO:rn4384WHB:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4384WHB
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1675983] Re: package linux-image-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[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/1675983

Title:
  package linux-image-4.4.0-66-generic 4.4.0-66.87 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Expired

Bug description:
  system displayed unexpected error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karthikeyan   1706 F pulseaudio
  Date: Sat Mar 25 09:17:35 2017
  Df:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=/dev/sda1
  InstallationDate: Installed on 2017-03-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   ens34 no wireless extensions.
   
   lono wireless extensions.
   
   enp0s29f7u7  no wireless extensions.
  MachineType: Intel DL-G41MX3-LT
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=a23a1244-f351-40a6-9c7b-27f2d56416f8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L1.01
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: DL-G41MX3-LT
  dmi.board.vendor: Intel
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL1.01:bd10/24/2011:svnIntel:pnDL-G41MX3-LT:pvr1.0:rvnIntel:rnDL-G41MX3-LT:rvr1.0:cvnIntel:ct3:cvr1.0:
  dmi.product.name: DL-G41MX3-LT
  dmi.product.version: 1.0
  dmi.sys.vendor: Intel

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

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

[Kernel-packages] [Bug 1675949] Re: perf report can't annotate kernel and dbgsym package has wrong addresses

[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/1675949

Title:
  perf report can't annotate kernel and dbgsym package has wrong
  addresses

Status in linux package in Ubuntu:
  Expired

Bug description:
  Running zesty 4.10.0-13-generic kernel and running:
  $ perf record 

  followed by

  $ perf report

  results in output that can't be annotated (even when run as root). The 
following message appears:
  Couldn't annotate do_io_submit:
  No vmlinux file with build id 81ba79d482fa9e3ea58486de8f119b27fe6db55e
  was found in the path.

  Note that annotation using /proc/kcore requires CAP_SYS_RAWIO
  capability.

  Please use:

  perf buildid-cache -vu vmlinux

  Note this is being run as root and /proc/kcore is accessible with dd from the 
same shell:
  $ dd if=/proc/kcore bs=8 count=16 | hexdump
  000 457f 464c 0102 0001    
  010 0004 00b7 0001     
  020 0040       
  030   0040 0038 0003   
  040 0004    00e8   

  Additionally, installing the linux-image-4.10.0-13-generic-dbgsym
  actually hurts the situation because the symbol addresses in the
  dbgsym don't match the kernel addresses.

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

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

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

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/fozzie__4.8.0-54.57__2017-05-27_02-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

[Kernel-packages] [Bug 1692589] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 19, failed: 0

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/ms10-35-mcdivittB0-kernel__4.8.0-54.57__2017-05-27_02-26-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

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

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/fozzie__4.8.0-54.57__2017-05-27_01-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

[Kernel-packages] [Bug 1692589] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/ms10-35-mcdivittB0-kernel__4.8.0-54.57__2017-05-27_02-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

[Kernel-packages] [Bug 1693962] Re: linux: 4.11.0-5.10 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/prepare-package
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.11.0-5.10 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
+ 
+ kernel-phase:Packaging
+ kernel-phase-changed:Saturday, 27. May 2017 02:03 UTC

** Description changed:

  This bug is for tracking the 4.11.0-5.10 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
  
  kernel-phase:Packaging
  kernel-phase-changed:Saturday, 27. May 2017 02:03 UTC
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux: 4.11.0-5.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  Confirmed
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the 4.11.0-5.10 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

  kernel-phase:Packaging
  kernel-phase-changed:Saturday, 27. May 2017 02:03 UTC

  -- swm properties --
  phase: Packaging

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

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

[Kernel-packages] [Bug 1693962] [NEW] linux: 4.11.0-5.10 -proposed tracker

[Seth Forshee]

Public bug reported:

This bug is for tracking the 4.11.0-5.10 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

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-development-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux (Ubuntu Artful)
 Importance: Medium
 Status: Confirmed


** Tags: artful block-proposed kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed

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

** Tags added: artful

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

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-development-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

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

Title:
  linux: 4.11.0-5.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow 

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/fozzie__4.8.0-54.57__2017-05-27_01-23-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

[Kernel-packages] [Bug 1692589] amaura (amd64) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/amaura__4.8.0-54.57__2017-05-27_01-04-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/fozzie__4.8.0-54.57__2017-05-27_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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-22.24-generic/rizzo__4.10.0-22.24__2017-05-27_00-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/1691146

Title:
  linux: 4.10.0-22.24 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1691149,1691152
  derivatives: 1691153
  -- swm properties --
  boot-testing-requested: 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/1691146/+subscriptions

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

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

[Brad Figg]

tests ran:  34, failed: 4;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/amaura__4.8.0-54.57__2017-05-26_21-47-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

[Kernel-packages] [Bug 1692589] Re: linux: 4.8.0-54.57 -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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

[Kernel-packages] [Bug 1693932] Re: Artful update to v4.11.3 stable release

[Seth Forshee]

** Changed in: linux (Ubuntu Artful)
   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/1693932

Title:
  Artful update to v4.11.3 stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The v4.11.3 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the v4.11.3 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1693932] [NEW] Artful update to v4.11.3 stable release

[Seth Forshee]

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The v4.11.3 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the v4.11.3 stable release shall be
applied:

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: linux (Ubuntu Artful)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Artful update to v4.11.3 stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The v4.11.3 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the v4.11.3 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1691752] Re: iptables/ip6tables regressions in deleting rules

[Seth Forshee]

** Changed in: linux (Ubuntu)
   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/1691752

Title:
  iptables/ip6tables regressions in deleting rules

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful-canonical-kernel-team-
  ppa/artful/amd64/s/snapd/20170517_171222_5c77c@/log.gz

  2017-05-17 17:11:40 Error restoring 
autopkgtest:ubuntu-17.10-amd64:tests/main/econnreset : 
  -
  + echo 'Remove the firewall rule again'
  Remove the firewall rule again
  ++ id -u test
  + iptables -D OUTPUT -m owner --uid-owner 12345 -j REJECT -p tcp 
--reject-with tcp-reset
  iptables: No chain/target/match by that name.
  -

  Can be easily reproduced by hand:

  $ sudo iptables -I OUTPUT -m owner --uid-owner $(id -u) -j REJECT  -p tcp 
--reject-with tcp-reset
  $ sudo iptables -D OUTPUT -m owner --uid-owner $(id -u) -j REJECT  -p tcp 
--reject-with tcp-reset
  iptables: No chain/target/match by that name.

  The rule is successfully deleted in xenial/zesty.

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

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

[Kernel-packages] [Bug 1691752] Re: iptables/ip6tables regressions in deleting rules

[Seth Forshee]

Similar failures observed with lxd and ip6tables, reverting a similar
patch fixes the problem. I've narrowed this down to one change each in
these patches which is causing some data for rules to not be copied to
userspace, so iptables/ip6tables cannot find a match. A partial revert
fixes the issues.

** Summary changed:

- iptables regression causing snapd ADT failure
+ iptables/ip6tables regressions in deleting rules

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

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

Title:
  iptables/ip6tables regressions in deleting rules

Status in linux package in Ubuntu:
  In Progress

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful-canonical-kernel-team-
  ppa/artful/amd64/s/snapd/20170517_171222_5c77c@/log.gz

  2017-05-17 17:11:40 Error restoring 
autopkgtest:ubuntu-17.10-amd64:tests/main/econnreset : 
  -
  + echo 'Remove the firewall rule again'
  Remove the firewall rule again
  ++ id -u test
  + iptables -D OUTPUT -m owner --uid-owner 12345 -j REJECT -p tcp 
--reject-with tcp-reset
  iptables: No chain/target/match by that name.
  -

  Can be easily reproduced by hand:

  $ sudo iptables -I OUTPUT -m owner --uid-owner $(id -u) -j REJECT  -p tcp 
--reject-with tcp-reset
  $ sudo iptables -D OUTPUT -m owner --uid-owner $(id -u) -j REJECT  -p tcp 
--reject-with tcp-reset
  iptables: No chain/target/match by that name.

  The rule is successfully deleted in xenial/zesty.

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

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

[Kernel-packages] [Bug 1687273] Re: Shared folder randomly not mounted

[Patrick Tenhaken]

Hello,
i today i upgraded all my Systems and i was affected by this problem. 
Filesystem is a Windows Server 2016 Datacenter. All my Ubuntu releases have 
problems (16.04 LTS, 16.10 and 17.04). 

The version solution solve the problem for me - but overall it isn't
really funny because when the problem occure there is from time to time
a full system freeze so i was not able to change my frozen tty session.

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

Title:
  Shared folder randomly not mounted

Status in cifs-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello Everybody,

  since last update from ubuntu 16.04.2, last night, my servers are
  randomly not able to read and write from shared folders. I got this
  message:

  lsof: WARNING: can't stat() cifs file system /mnt/record
    Output information may be incomplete.
  lsof: WARNING: can't stat() cifs file system /mnt/record
    Output information may be incomplete.
  lsof: WARNING: can't stat() cifs file system /mnt/record
    Output information may be incomplete.
  ...
  rsync: ERROR: cannot stat destination "/mnt/record/": Host is down (112)
  rsync error: errors selecting input/output files, dirs (code 3) at 
main.c(652) [Receiver=3.1.1]

  This comes from my cron script.

  When I type df -h it takes sometimes very long to get the list. And it
  also can be that the mounted share is disconnected and I have to mount
  -a (what also takes long) again.

  My fstab have this command:

  //address /mnt/storage cifs
  
auto,nofail,iocharset=utf8,rw,credentials=/path/.smb,uid=1000,gid=1000,file_mode=0660,dir_mode=0770
  0 0

  My update list from last night was this:

  linux-image-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic)
  linux-image-extra-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic)
  linux-headers-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic)
  linux-headers-4.4.0-75:amd64 (4.4.0-75.96, automatic)
  Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 
1:9.10.3.dfsg.P4-8ubuntu1.6)
  linux-headers-generic:amd64 (4.4.0.72.78, 4.4.0.75.81)
  linux-libc-dev:amd64 (4.4.0-72.93, 4.4.0-75.96)
  mysql-client-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  libapt-inst2.0:amd64 (1.2.19, 1.2.20)
  mysql-server-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  libsystemd0:amd64 (229-4ubuntu16, 229-4ubuntu17)
  linux-image-generic:amd64 (4.4.0.72.78, 4.4.0.75.81)
  apt:amd64 (1.2.19, 1.2.20)
  mysql-server:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  udev:amd64 (229-4ubuntu16, 229-4ubuntu17)
  libapt-pkg5.0:amd64 (1.2.19, 1.2.20)
  libudev1:amd64 (229-4ubuntu16, 229-4ubuntu17)
  cifs-utils:amd64 (2:6.4-1ubuntu1, 2:6.4-1ubuntu1.1)
  dpkg:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2)
  mysql-client-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 
1:9.10.3.dfsg.P4-8ubuntu1.6)
  linux-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81)
  systemd-sysv:amd64 (229-4ubuntu16, 229-4ubuntu17)
  distro-info-data:amd64 (0.28ubuntu0.2, 0.28ubuntu0.3)
  systemd:amd64 (229-4ubuntu16, 229-4ubuntu17)
  mysql-common:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  apt-utils:amd64 (1.2.19, 1.2.20)
  libmysqlclient20:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  linux-headers-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81)
  linux-image-extra-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81)
  thermald:amd64 (1.5-2ubuntu3, 1.5-2ubuntu4)
  qemu-guest-agent:amd64 (1:2.5+dfsg-5ubuntu10.10, 1:2.5+dfsg-5ubuntu10.11)
  libfreetype6:amd64 (2.6.1-0.1ubuntu2.1, 2.6.1-0.1ubuntu2.2)
  linux-image-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81)
  libdpkg-perl:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2)
  mysql-server-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  libxslt1.1:amd64 (1.1.28-2.1, 1.1.28-2.1ubuntu0.1)
  dpkg-dev:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2)

  I saw that somebody else has the same problem:

  https://askubuntu.com/questions/910058/updates-broke-cifs-smb-mounts-
  in-16-04

  I had to remove the latest kernel update, after that it works.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1687273/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/amaura__4.8.0-54.57__2017-05-26_21-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

[Kernel-packages] [Bug 1687512] Re: Kernel panics on Xenial when using cgroups and strict CFS limits

[Jay Vosburgh]

Customer has verified that 4.4.0-79-generic resolves the issue in their
environment that would previously panic.


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

Title:
  Kernel panics on Xenial when using cgroups and strict CFS limits

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification
  -

  [Impact]
  Apache Mesos and Kubernetes workloads on Xenial cause a panic
  (NULL pointer dereference) in the completely fair scheduler.

  These panics are in pick_next_entity and include pick_next_task_fair
  in the call stack.

  [Fix]
  Cherry-picking both
  754bd598be9bbc953bc709a9e8ed7f3188bfb9d7
  (http://lkml.kernel.org/r/146608183552.21905.15924473394414832071.stgit@buzz)
  and
  094f469172e00d6ab0a3130b0e01c83b3cf3a98d
  (http://lkml.kernel.org/r/146608182119.21870.8439834428248129633.stgit@buzz)
  fix the crash.
  They appear to be intended as a series - they were posted to LKML at
  the same time.

  [Testcase]
  The fix has been validated by the user who reported the bug

  Bug description
  ---

  We see a number of kernel panics on servers running Apache Mesos using
  cgroups with small (0.1-0.2) cpu limits.

  These all appear as NULL pointer dereferences in and around
  pick_next_entity and pick_next_task_fair, for example:

  [24334.493331] BUG: unable to handle kernel NULL pointer dereference at 
0050
  [24334.501611] IP: [] pick_next_entity+0x7f/0x160
  [24334.507868] PGD 3eacfa067 PUD 3eacfb067 PMD 0
  [24334.512806] Oops:  [#1] SMP
  [24334.516420] Modules linked in: ipvlan xt_nat xt_tcpudp veth ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs tcp_diag 
inet_diag nfsd auth_rpcgss nfs_acl nfs lockd grace sunrpc fscache dm_crypt 
ppdev input_leds mac_hid i2c_piix4 8250_fintek parport_pc pvpanic parport 
serio_raw crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse virtio_scsi
  [24334.576359] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.4.0-66-generic 
#87~14.04.1-Ubuntu
  [24334.584748] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [24334.594188] task: 8803ee671c00 ti: 8803ee67c000 task.ti: 
8803ee67c000
  [24334.601799] RIP: 0010:[] [] 
pick_next_entity+0x7f/0x160
  [24334.610490] RSP: 0018:8803ee67fdd8 EFLAGS: 00010086
  [24334.615924] RAX: 8803ebed4c00 RBX: 880036529800 RCX: 

  [24334.623190] RDX: 0225341f RSI:  RDI: 

  [24334.630479] RBP: 8803ee67fe00 R08: 0004 R09: 

  [24334.637758] R10: 8803e7ed7600 R11: 0001 R12: 

  [24334.645153] R13:  R14: 0009067729c4 R15: 
8803ee672178
  [24334.652512] FS: () GS:8803ffd0() 
knlGS:
  [24334.660721] CS: 0010 DS:  ES:  CR0: 80050033
  [24334.666587] CR2: 0050 CR3: 0003eacf9000 CR4: 
001406e0
  [24334.673851] Stack:
  [24334.675980] 8803ffd16e00 8803ffd16e00 8803e855a200 
880036529800
  [24334.683995] 0002 8803ee67fe68 810b98a6 
8803ffd16e70
  [24334.692024] 00016e00 8803e7ed7600 8803ee671c00 

  [24334.700172] Call Trace:
  [24334.702750] [] pick_next_task_fair+0x66/0x4b0
  [24334.708886] [] __schedule+0x7f4/0x980
  [24334.714349] [] schedule+0x35/0x80
  [24334.719445] [] schedule_preempt_disabled+0xe/0x10
  [24334.725962] [] cpu_startup_entry+0x18a/0x350
  [24334.732012] [] start_secondary+0x149/0x170
  [24334.737895] Code: 8b 70 50 4d 2b 74 24 50 4d 85 f6 7e 59 4c 89 e7 e8 67 ff 
ff ff 49 39 c6 7f 04 4c 8b 6b 48 48 8b 43 40 48 85 c0 74 1f 4c 8b 70 50 <4d> 2b 
74 24 50 4d 85 f6 7e 2c 4c 89 e7 e8 3f ff ff ff 49 39 c6
  [24334.765124] RIP [] pick_next_entity+0x7f/0x160
  [24334.771473] RSP 
  [24334.775077] CR2: 0050
  [24334.779121] ---[ end trace 05d941efb97b7bae ]---

  and

  [155852.028575] BUG: unable to handle kernel NULL pointer dereference at 
0050
  [155852.036931] IP: [] pick_next_entity+0x7f/0x160
  [155852.043491] PGD 3ebae8067 PUD 3ebae9067 PMD 0
  [155852.048550] Oops:  [#1] SMP
  [155852.052437] Modules linked in: ipvlan veth xt_nat xt_tcpudp 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter 
ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge 

[Kernel-packages] [Bug 1689980] Re: AACRAID for power9 platform

[bugproxy]

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin16043

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

Title:
  AACRAID for power9 platform

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  Hello team,
  It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

  Hi Narinder,

  We have submitted a handful of critical fixes for the AACRAID driver
  on to the kernel.org, targeting 4.11. These patches are bug fixes and
  our customer IBM is expecting these patches to go into the 16.04.3
  release, for to use with the Power9 platforms.

  Can you please let me know if these patches will be backported by your
  kernel team on to the upcoming 16.04.3? Do you also have a schedule in
  place for 16.04.3 release?

  Thanks,
  Gana

  Below are the patch details.

  Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
  fixes

  This patchset primarily focuses on tweaking and hardening the
  controller reset support for both ARC and HBA1000 devices. Now the
  driver can only reset the controller thru eh reset. Included a srb
  memory fix and pci dma allocation fix.

  Changes in V2:
   - Corrected heading and description for srb memory patch and removed stray
 comment.
   - Removed incorrect up function call and cleared fib wait flag after call
 to down interruptible in the ioctl return on ctrl reset patch.
   - Added review acknowledgements by David Carroll thank you Dave for
 finding the above issues in the above 2 patches.

  Raghava Aditya Renukunta (19):
  [SCSI] aacraid: Remove __GFP_DMA for raw srb memory  
  [SCSI] aacraid: Fix DMAR issues with  iommu=pt  
  [SCSI] aacraid: Added 32 and 64 queue depth for arc natives  
  [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks  
  [SCSI] aacraid: Remove reset support from check_health  
  [SCSI] aacraid: Change wait time for fib completion  
  [SCSI] aacraid: Log count info of scsi cmds before reset  
  [SCSI] aacraid: Print ctrl status before eh reset  
  [SCSI] aacraid: Using single reset mask for IOP reset  
  [SCSI] aacraid: Rework IOP reset  
  [SCSI] aacraid: Add periodic checks to see IOP reset status  
  [SCSI] aacraid: Rework SOFT reset code  
  [SCSI] aacraid: Rework aac_src_restart  
  [SCSI] aacraid: Use correct function to get ctrl health  
  [SCSI] aacraid: Make sure ioctl returns on controller reset  
  [SCSI] aacraid: Enable ctrl reset for both hba and arc  
  [SCSI] aacraid: Add reset debugging statements  
  [SCSI] aacraid: Remove reference to Series-9  
  [SCSI] aacraid: Update driver version to 50834

  drivers/scsi/aacraid/aachba.c   |  17 ++-
  drivers/scsi/aacraid/aacraid.h  |  22 +++-  
  drivers/scsi/aacraid/commctrl.c |  15 ++-  
  drivers/scsi/aacraid/comminit.c |  18 +---  
  drivers/scsi/aacraid/commsup.c  |  78 +++---
  drivers/scsi/aacraid/linit.c| 232 
  drivers/scsi/aacraid/src.c  | 136 +--

   7 files changed, 298 insertions(+), 220 deletions(-)

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

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

[Kernel-packages] [Bug 1689980] Re: AACRAID for power9 platform

[bugproxy]

--- Comment From ru...@us.ibm.com 2017-05-26 16:42 EDT---
Reverse mirror for LP1689980: AACRAID for power9 platform

** Tags added: architecture-ppc64le bugnameltc-155096 severity-high
targetmilestone-inin---

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

Title:
  AACRAID for power9 platform

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Zesty:
  Triaged

Bug description:
  Hello team,
  It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

  Hi Narinder,

  We have submitted a handful of critical fixes for the AACRAID driver
  on to the kernel.org, targeting 4.11. These patches are bug fixes and
  our customer IBM is expecting these patches to go into the 16.04.3
  release, for to use with the Power9 platforms.

  Can you please let me know if these patches will be backported by your
  kernel team on to the upcoming 16.04.3? Do you also have a schedule in
  place for 16.04.3 release?

  Thanks,
  Gana

  Below are the patch details.

  Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
  fixes

  This patchset primarily focuses on tweaking and hardening the
  controller reset support for both ARC and HBA1000 devices. Now the
  driver can only reset the controller thru eh reset. Included a srb
  memory fix and pci dma allocation fix.

  Changes in V2:
   - Corrected heading and description for srb memory patch and removed stray
 comment.
   - Removed incorrect up function call and cleared fib wait flag after call
 to down interruptible in the ioctl return on ctrl reset patch.
   - Added review acknowledgements by David Carroll thank you Dave for
 finding the above issues in the above 2 patches.

  Raghava Aditya Renukunta (19):
  [SCSI] aacraid: Remove __GFP_DMA for raw srb memory  
  [SCSI] aacraid: Fix DMAR issues with  iommu=pt  
  [SCSI] aacraid: Added 32 and 64 queue depth for arc natives  
  [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks  
  [SCSI] aacraid: Remove reset support from check_health  
  [SCSI] aacraid: Change wait time for fib completion  
  [SCSI] aacraid: Log count info of scsi cmds before reset  
  [SCSI] aacraid: Print ctrl status before eh reset  
  [SCSI] aacraid: Using single reset mask for IOP reset  
  [SCSI] aacraid: Rework IOP reset  
  [SCSI] aacraid: Add periodic checks to see IOP reset status  
  [SCSI] aacraid: Rework SOFT reset code  
  [SCSI] aacraid: Rework aac_src_restart  
  [SCSI] aacraid: Use correct function to get ctrl health  
  [SCSI] aacraid: Make sure ioctl returns on controller reset  
  [SCSI] aacraid: Enable ctrl reset for both hba and arc  
  [SCSI] aacraid: Add reset debugging statements  
  [SCSI] aacraid: Remove reference to Series-9  
  [SCSI] aacraid: Update driver version to 50834

  drivers/scsi/aacraid/aachba.c   |  17 ++-
  drivers/scsi/aacraid/aacraid.h  |  22 +++-  
  drivers/scsi/aacraid/commctrl.c |  15 ++-  
  drivers/scsi/aacraid/comminit.c |  18 +---  
  drivers/scsi/aacraid/commsup.c  |  78 +++---
  drivers/scsi/aacraid/linit.c| 232 
  drivers/scsi/aacraid/src.c  | 136 +--

   7 files changed, 298 insertions(+), 220 deletions(-)

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

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

[Kernel-packages] [Bug 1688132] Re: Support IPMI system interface on Cavium ThunderX

[dann frazier]

ubuntu@grotian:~$ cat /proc/version
Linux version 4.10.0-22-generic (buildd@bos01-arm64-038) (gcc version 6.3.0 
20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2) ) #24-Ubuntu SMP Mon May 22 17:43:39 
UTC 2017
ubuntu@grotian:~$ sudo modprobe ipmi_ssif
ubuntu@grotian:~$ sudo modprobe ipmi_devintf
ubuntu@grotian:~$ sudo ipmitool lan print
Set in Progress : Set Complete
Auth Type Support   : MD5 
Auth Type Enable: Callback : MD5 
: User : MD5 
: Operator : MD5 
: Admin: MD5 
: OEM  : MD5 
IP Address Source   : Static Address
IP Address  : 
Subnet Mask : 
MAC Address : 
SNMP Community String   : AMI
IP Header   : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled
Gratituous ARP Intrvl   : 0.0 seconds
Default Gateway IP  : 
Default Gateway MAC : 
Backup Gateway IP   : 0.0.0.0
Backup Gateway MAC  : 00:00:00:00:00:00
802.1q VLAN ID  : Disabled
802.1q VLAN Priority: 0
RMCP+ Cipher Suites : 0,1,2,3,6,7,8,11,12,15,16,17
Cipher Suite Priv Max   : caaaXXX
: X=Cipher Suite Unused
: c=CALLBACK
: u=USER
: o=OPERATOR
: a=ADMIN
: O=OEM
Bad Password Threshold  : 0
Invalid password disable: no
Attempt Count Reset Int.: 0
User Lockout Interval   : 0

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

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

Title:
  Support IPMI system interface on Cavium ThunderX

Status in linux package in Ubuntu:
  Fix Committed
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:
  Fix Committed

Bug description:
  [Impact]
  The IPMI system interface (/dev/ipmi0) is unavailable on Cavium 
ThunderX-based systems. This prevents various in-band management tasks, 
including auto-enlistment using MAAS.

  [Test Case]
  sudo modprobe ipmi_ssif
  sudo modprobe ipmi_devintf

  Do you have a working /dev/ipmi0?
  sudo ipmitool lan print

  [Regression Risk]
  For hwe-z, this is a small fix to a driver that is only used on 
ThunderX-based systems, and is currently not usable w/o magic manual steps.

  For hwe-x and hwe-y, this also impacts the i2c-octeon driver. After
  hwe-y, upstream split that driver into 2 pieces to factor out code
  that could be shared with i2c-thunderx, and then i2c-thunderx was
  added. i2c-octeon is a driver for Cavium OCTEON systems, which are
  MIPS64 - an architecture unsupported by Ubuntu, so regression risk is
  negligible. i2c-thunderx is a new driver that is only loaded on
  ThunderX-based systems, so the testing we've performed on ThunderX
  should mitigate that regression risk.

  Note: there are issues with older firmware (version varies depending
  on platform) where the IPMI device can vanish between reboots,
  requiring a BMC reset to recover. This doesn't cause any other problem
  - drivers don't load, and it's as if this driver was never added.
  However, it is worth noting here in case people google it. Please
  upgrade your firmware if you run into this.

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

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

[Kernel-packages] [Bug 1693912] [NEW] linux-joule update to release_1704

[Thadeu Lima de Souza Cascardo]

Public bug reported:

This is really a linux-joule bug, not a linux one. It involves the
update to latest release.

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

Title:
  linux-joule update to release_1704

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is really a linux-joule bug, not a linux one. It involves the
  update to latest release.

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

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

[Kernel-packages] [Bug 1693912] 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 1693912

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

Title:
  linux-joule update to release_1704

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is really a linux-joule bug, not a linux one. It involves the
  update to latest release.

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

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

[Kernel-packages] [Bug 1693914] 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 1693914

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

Title:
  linux-joule xr-usb-serial build failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the joule rebase that included a backport of upstream commit
  58383c78425e4ee1c077253cf297b641c861c02e ("gpio: change member .dev to
  .parent"), xr-usb-serial fails to build as it uses struct gpio_chip.

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

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

[Kernel-packages] [Bug 1693914] [NEW] linux-joule xr-usb-serial build failure

[Thadeu Lima de Souza Cascardo]

Public bug reported:

After the joule rebase that included a backport of upstream commit
58383c78425e4ee1c077253cf297b641c861c02e ("gpio: change member .dev to
.parent"), xr-usb-serial fails to build as it uses struct gpio_chip.

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

Title:
  linux-joule xr-usb-serial build failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the joule rebase that included a backport of upstream commit
  58383c78425e4ee1c077253cf297b641c861c02e ("gpio: change member .dev to
  .parent"), xr-usb-serial fails to build as it uses struct gpio_chip.

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

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

[Kernel-packages] [Bug 1693369] Re: 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2 5u84

[Joseph Salisbury]

I built a ppc64el package.  It can be downloaded from the same link:

http://kernel.ubuntu.com/~jsalisbury/lp1693369/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/1693369

Title:
  5U84 - ses driver isn't binding right - cannot blink lights on 1 of
  the 2 5u84

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  This is a request to add the following upstream commit to both Ubuntu
  16.04.1 and 16.04.2:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=9373eba6cfae48911b977d14323032cd5d161aae

  Without this patch, the symlink in sysfs which binds a SAS device to
  an enclosure slot does not get created. This makes disk hotplug near
  impossible on large JBOD disk drawers.

  You should be able to do:

  ls /sys/block/sdb/device/ | grep enclosure

  and see something like:

  enclosure_device:1

  If you cd to this directory, you can then access the SES controls for
  that slot to flash the LED to assist in locating the disk to replace a
  failed disk.

  Currently with 16.04.1 and 16.04.2, these symlinks are not getting
  created.

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

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

[Kernel-packages] [Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

[Joseph Salisbury]

** Changed in: linux (Ubuntu)
   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/1686099

Title:
  connection flood to port 445 on mounting cifs volume under kernel

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  This is identical to the bug reported on the Debian kernel list, only
  I'm running 4.4.0, not 4.[89].0

  After about 15 mintues, the cifsd daemon starts flooding echo requests
  on port 445 to the windows server causing a constant 1MB/s load
  (around 10,000 packets per second) that eventually leads to system
  instability that forces a reboot to correct.  This is repeatable and
  as far as I know started about a week ago (possibly with the
  installation of 4.4.0-75).

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856843

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

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

[Kernel-packages] [Bug 1664312] Re: Update ENA driver to 1.1.2 from net-next

[Kamal Mostafa]

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

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

Title:
  Update ENA driver to 1.1.2 from net-next

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-aws source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  "net/ena 1.1.2 changeset" recently merged into linux/net-next:
  http://marc.info/?l=linux-netdev=148664692122357=2

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

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

[Kernel-packages] [Bug 1693337] Re: Enable Matrox driver for Ubuntu 16.04.3

[Seth Forshee]

** Changed in: linux (Ubuntu)
   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/1693337

Title:
  Enable Matrox driver for Ubuntu 16.04.3

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

Bug description:
  This request is to enable Matrox driver and backport the enablement
  paatch from 4.11 kernel to 4.10 kernel for Ubuntu 16.04.3.

  This will get tested on HPE platform after the modification.

  Following config and patch changes are needed.

  CONFIG_DRM_MGAG200=m

  commit f0493e653f9679114d1dfd54ab88b54ce95576e1
  Author: Mathieu Larouche 
  Date:   Fri Oct 21 12:47:07 2016 -0400

  drm/mgag200: Added support for the new device G200eH3

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

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

[Kernel-packages] [Bug 1687273] Re: Shared folder randomly not mounted

[DanielW]

This problem hit me on a xenial install with HWE and linux-generic-
hwe-16.04 with generic kernels 4.8.0-52 and 4.8.0-53. Problem is
alleviated by using the mainline kernel 4.12-rc2.

Please note: I cannot use the vers=3.0 workaround as described above
because one of my servers is running Windows Server 2003 which, as I
understand, still uses the older SMB1 protocol.

This problem happened on a users workstation and due to the freezing
problem with the desktop and file manager, her system was unusable for
about 2-3 days.

It took me a little while to pin-point the problem to a complete cifs
freeze which was occurring within 5-45 minutes of logging on.

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

Title:
  Shared folder randomly not mounted

Status in cifs-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello Everybody,

  since last update from ubuntu 16.04.2, last night, my servers are
  randomly not able to read and write from shared folders. I got this
  message:

  lsof: WARNING: can't stat() cifs file system /mnt/record
    Output information may be incomplete.
  lsof: WARNING: can't stat() cifs file system /mnt/record
    Output information may be incomplete.
  lsof: WARNING: can't stat() cifs file system /mnt/record
    Output information may be incomplete.
  ...
  rsync: ERROR: cannot stat destination "/mnt/record/": Host is down (112)
  rsync error: errors selecting input/output files, dirs (code 3) at 
main.c(652) [Receiver=3.1.1]

  This comes from my cron script.

  When I type df -h it takes sometimes very long to get the list. And it
  also can be that the mounted share is disconnected and I have to mount
  -a (what also takes long) again.

  My fstab have this command:

  //address /mnt/storage cifs
  
auto,nofail,iocharset=utf8,rw,credentials=/path/.smb,uid=1000,gid=1000,file_mode=0660,dir_mode=0770
  0 0

  My update list from last night was this:

  linux-image-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic)
  linux-image-extra-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic)
  linux-headers-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic)
  linux-headers-4.4.0-75:amd64 (4.4.0-75.96, automatic)
  Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 
1:9.10.3.dfsg.P4-8ubuntu1.6)
  linux-headers-generic:amd64 (4.4.0.72.78, 4.4.0.75.81)
  linux-libc-dev:amd64 (4.4.0-72.93, 4.4.0-75.96)
  mysql-client-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  libapt-inst2.0:amd64 (1.2.19, 1.2.20)
  mysql-server-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  libsystemd0:amd64 (229-4ubuntu16, 229-4ubuntu17)
  linux-image-generic:amd64 (4.4.0.72.78, 4.4.0.75.81)
  apt:amd64 (1.2.19, 1.2.20)
  mysql-server:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  udev:amd64 (229-4ubuntu16, 229-4ubuntu17)
  libapt-pkg5.0:amd64 (1.2.19, 1.2.20)
  libudev1:amd64 (229-4ubuntu16, 229-4ubuntu17)
  cifs-utils:amd64 (2:6.4-1ubuntu1, 2:6.4-1ubuntu1.1)
  dpkg:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2)
  mysql-client-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 
1:9.10.3.dfsg.P4-8ubuntu1.6)
  linux-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81)
  systemd-sysv:amd64 (229-4ubuntu16, 229-4ubuntu17)
  distro-info-data:amd64 (0.28ubuntu0.2, 0.28ubuntu0.3)
  systemd:amd64 (229-4ubuntu16, 229-4ubuntu17)
  mysql-common:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  apt-utils:amd64 (1.2.19, 1.2.20)
  libmysqlclient20:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  linux-headers-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81)
  linux-image-extra-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81)
  thermald:amd64 (1.5-2ubuntu3, 1.5-2ubuntu4)
  qemu-guest-agent:amd64 (1:2.5+dfsg-5ubuntu10.10, 1:2.5+dfsg-5ubuntu10.11)
  libfreetype6:amd64 (2.6.1-0.1ubuntu2.1, 2.6.1-0.1ubuntu2.2)
  linux-image-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81)
  libdpkg-perl:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2)
  mysql-server-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  libxslt1.1:amd64 (1.1.28-2.1, 1.1.28-2.1ubuntu0.1)
  dpkg-dev:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2)

  I saw that somebody else has the same problem:

  https://askubuntu.com/questions/910058/updates-broke-cifs-smb-mounts-
  in-16-04

  I had to remove the latest kernel update, after that it works.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1687273/+subscriptions

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

[Kernel-packages] [Bug 1692589] Re: linux: 4.8.0-54.57 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1692590
  derivatives: 1692592
- kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
- kernel-stable-phase:Uploaded
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Friday, 26. May 2017 18:33 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Friday, 26. May 2017 18:33 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.8.0-54.57 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
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  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  -- swm properties --
  boot-testing-requested: 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/1692589/+subscriptions

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

[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

[Joseph Salisbury]

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions

-- 
Mailing list: https://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 1693337] Re: Enable Matrox driver for Ubuntu 16.04.3

[Narinder Gupta]

I tested both the kernels on HPE gen8 and Gen10 platform and it seems to
loading fine and i can confirm that driver is in use with Matrox grpahics
controller for both Gen8 and Gen10 platform. Below is the syslog from the
server tested for this bug.

gen10 http://paste.ubuntu.com/24668361/
gen8  http://paste.ubuntu.com/24668369


Thanks and Regards,
Narinder Gupta (PMP)   narinder.gu...@canonical.com
Canonical, Ltd.narindergupta [irc.freenode.net]
+1.281.736.5150narindergupta2007[skype]

Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com


On Thu, May 25, 2017 at 11:30 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> I built a Zesty test kernel with CONFIG_DRM_MGAG200 set to m and a pick
> of commit f0493e653f9679114d1dfd54ab88b54ce95576e1.  The test kernel can
> be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1693337/
>
> Can you give this kernel a test?
>
> Thanks in advance!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1693337
>
> Title:
>   Enable Matrox driver for Ubuntu 16.04.3
>
> Status in linux package in Ubuntu:
>   In Progress
> Status in linux source package in Zesty:
>   In Progress
>
> Bug description:
>   This request is to enable Matrox driver and backport the enablement
>   paatch from 4.11 kernel to 4.10 kernel for Ubuntu 16.04.3.
>
>   This will get tested on HPE platform after the modification.
>
>   Following config and patch changes are needed.
>
>   CONFIG_DRM_MGAG200=m
>
>   commit f0493e653f9679114d1dfd54ab88b54ce95576e1
>   Author: Mathieu Larouche 
>   Date:   Fri Oct 21 12:47:07 2016 -0400
>
>   drm/mgag200: Added support for the new device G200eH3
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1693337/+subscriptions
>

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

Title:
  Enable Matrox driver for Ubuntu 16.04.3

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

Bug description:
  This request is to enable Matrox driver and backport the enablement
  paatch from 4.11 kernel to 4.10 kernel for Ubuntu 16.04.3.

  This will get tested on HPE platform after the modification.

  Following config and patch changes are needed.

  CONFIG_DRM_MGAG200=m

  commit f0493e653f9679114d1dfd54ab88b54ce95576e1
  Author: Mathieu Larouche 
  Date:   Fri Oct 21 12:47:07 2016 -0400

  drm/mgag200: Added support for the new device G200eH3

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

-- 
Mailing list: https://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 1242321] Re: USB 3.0 Harddrive not recognised

[tomdean]

On 05/26/2017 01:42 AM, Kai-Heng Feng wrote:
> @tomdean
> 
> Let's not hijack the original bug.
> Can you file a new bug?
> 
> $ ubuntu-bug linux
> 

Sorry, typo in the bug number.

I created bug 1693842.

Tom Dean

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

Title:
  USB 3.0 Harddrive not recognised

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is not recognising any device plugged into any USB 3.0 ports.
  Sometimes Ubuntu will freeze for a few seconds when you plug something
  into a USB 3.0 port; when Ubuntu comes out of the freeze, the device
  is still NOT recognised.

  No problems with USB 2.0 ports and devices.

  The USB 3.0 on this computer only works in Windows 7 (I'm dual booting
  Ubuntu 13.10 and Windows 7, both are 64-bit).

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

-- 
Mailing list: https://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 1242321] Re: USB 3.0 Harddrive not recognised

[tomdean]

On 05/26/2017 01:42 AM, Kai-Heng Feng wrote:
> @tomdean
> 
> Let's not hijack the original bug.
> Can you file a new bug?
> 
> $ ubuntu-bug linux
> 

I created bug 1603842.

Tom Dean

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

Title:
  USB 3.0 Harddrive not recognised

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is not recognising any device plugged into any USB 3.0 ports.
  Sometimes Ubuntu will freeze for a few seconds when you plug something
  into a USB 3.0 port; when Ubuntu comes out of the freeze, the device
  is still NOT recognised.

  No problems with USB 2.0 ports and devices.

  The USB 3.0 on this computer only works in Windows 7 (I'm dual booting
  Ubuntu 13.10 and Windows 7, both are 64-bit).

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

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

[Kernel-packages] [Bug 1693842] 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/1693842

Title:
  USB 3.0 Disk Drive Not Recognized.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  WD My Passport 2T USB 3.0 Disk Drive.
  External Plugable 7 port USB 3.0 hub.

  When I connect the WD drive to the external USB 3.0 hub it is not recognized.
  The drive led blinks one time and it is not in dmesg or in the output of 
lsusb.

  > sudo lsusb -v causes the drive led to blink several times and it is
  recognized.

  With Autosuspend good for this device, long access applications like dump 
fail.
  After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes 
and then dump asks for operator intervention.  Looking at dmesg the drive 
(initially sdf) was disconnected and reconnected as sdg.

Bad  Autosuspend for USB device xHCI Host Controller [usb6]

  seems to correct this behavior but not the initial connection problem.

  Some discussion and testing in bug 1242321.

  If I connect the drive to a USB 3.0 port on the motherboard, it is
  recognized.

  There is no problem with an Plugable 7-port USB 2.0 hub.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tomdean3698 F pulseaudio
   /dev/snd/controlC0:  tomdean3698 F pulseaudio
  Date: Fri May 26 09:05:20 2017
  HibernationDevice: RESUME=UUID=8c377624-f972-4b2b-9364-832f70b2a67a
  InstallationDate: Installed on 2016-05-15 (375 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=47d8903b-afb2-4432-bc92-b1f4e30209ef ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.8
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4801:bd07/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1693842] [NEW] USB 3.0 Disk Drive Not Recognized.

[tomdean]

Public bug reported:

WD My Passport 2T USB 3.0 Disk Drive.
External Plugable 7 port USB 3.0 hub.

When I connect the WD drive to the external USB 3.0 hub it is not recognized.
The drive led blinks one time and it is not in dmesg or in the output of lsusb.

> sudo lsusb -v causes the drive led to blink several times and it is
recognized.

With Autosuspend good for this device, long access applications like dump fail.
After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes 
and then dump asks for operator intervention.  Looking at dmesg the drive 
(initially sdf) was disconnected and reconnected as sdg.

  Bad  Autosuspend for USB device xHCI Host Controller [usb6]

seems to correct this behavior but not the initial connection problem.

Some discussion and testing in bug 1242321.

If I connect the drive to a USB 3.0 port on the motherboard, it is
recognized.

There is no problem with an Plugable 7-port USB 2.0 hub.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-78-generic 4.4.0-78.99
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  tomdean3698 F pulseaudio
 /dev/snd/controlC0:  tomdean3698 F pulseaudio
Date: Fri May 26 09:05:20 2017
HibernationDevice: RESUME=UUID=8c377624-f972-4b2b-9364-832f70b2a67a
InstallationDate: Installed on 2016-05-15 (375 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 lono wireless extensions.
 
 eno1  no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=47d8903b-afb2-4432-bc92-b1f4e30209ef ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-78-generic N/A
 linux-backports-modules-4.4.0-78-generic  N/A
 linux-firmware1.157.8
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P9X79 PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4801:bd07/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug 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/1693842

Title:
  USB 3.0 Disk Drive Not Recognized.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  WD My Passport 2T USB 3.0 Disk Drive.
  External Plugable 7 port USB 3.0 hub.

  When I connect the WD drive to the external USB 3.0 hub it is not recognized.
  The drive led blinks one time and it is not in dmesg or in the output of 
lsusb.

  > sudo lsusb -v causes the drive led to blink several times and it is
  recognized.

  With Autosuspend good for this device, long access applications like dump 
fail.
  After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes 
and then dump asks for operator intervention.  Looking at dmesg the drive 
(initially sdf) was disconnected and reconnected as sdg.

Bad  Autosuspend for USB device xHCI Host Controller [usb6]

  seems to correct this behavior but not the initial connection problem.

  Some discussion and testing in bug 1242321.

  If I connect the drive to a USB 3.0 port on the motherboard, it is
  recognized.

  There is no problem with an Plugable 7-port USB 2.0 hub.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tomdean3698 F pulseaudio
   /dev/snd/controlC0:  tomdean3698 F pulseaudio
  Date: Fri May 26 09:05:20 2017
  HibernationDevice: RESUME=UUID=8c377624-f972-4b2b-9364-832f70b2a67a
  InstallationDate: Installed on 2016-05-15 (375 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  

[Kernel-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Kai-Heng Feng]

Great, Kailiang has Launchpad account =)

@Kailiang
I personally cannot reproduce the issue on my $10 Logitech headphone, maybe 
this bug can only be reproduced on more beefy headphone.

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

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

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

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[Kai-Heng Feng]

My bad, didn't notice it's XPS 9560...
To disable the deepest power state, you can add this to your kernel parameter:
"nvme_core.default_ps_max_latency_us=6000".

Please report back if this works, thanks!

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

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

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV: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/1678184/+subscriptions

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

[Kernel-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Kai-Heng Feng]

Sorry, my bad, ALC256 doesn't have aaloop at first place, so my kernel
does nothing =(

I'll ask Realtek codec guy about this issue.

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

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

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

[Kernel-packages] [Bug 1691045] Re: PowerPC: Pstore dump for powerpc is broken

[Joseph Salisbury]

Yes, the 16.04.03 kernel is based off the 4.10 Zesty kernel, so it will
get the patch.  Did you happen to have a chance to test the kernel
posted in comment #2?

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

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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

[Kernel-packages] [Bug 1693673] Re: Ubuntu 16.04 IOB Error when the Mustang board rebooted

[Joseph Salisbury]

It doesn't appear the commit mentioned in comment #4 has landed in
mailine or linux-next yet.  Can you post a comment when It does land,
and we can submit and SRU for the Ubuntu kernel.

** Tags added: 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/1693673

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

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

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 26 12:21 seq
   crw-rw 1 root audio 116, 33 May 26 12:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f8faea1d-17bf-4c48-9b44-ca04875978b9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Mustang Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-53-generic N/A
   linux-backports-modules-4.8.0-53-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-53-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: Feb 28 2017
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.07.09
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Mustang Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Mustang Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro

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

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

[Kernel-packages] [Bug 1691184] Re: linux-aws: 4.4.0-1018.27 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-aws: 4.4.0-1018.27 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1691180
  phase: Promoted to proposed
  proposed-announcement-sent: true

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

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

[Kernel-packages] [Bug 1688164] Re: arm64: Add CNTFRQ_EL0 handler

[dann frazier]

On a HiSilicon D05 system:

ubuntu@ubuntu:~$ cat /proc/version
Linux version 4.10.0-22-generic (buildd@bos01-arm64-038) (gcc version 6.3.0 
20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2) ) #24-Ubuntu SMP Mon May 22 17:43:39 
UTC 2017
ubuntu@ubuntu:~$ ./test
freq 5000

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

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

Title:
  arm64: Add CNTFRQ_EL0 handler

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

Bug description:
  [Impact]
  Userspace reads of CNTVCT_EL0 are broken on HiSilicon D05 systems, which 
breaks some applications such as OpenMPI.

  [Test Case]
  #include 
  #include 

  int main(int argc, char *argv[])
  {
     unsigned int freq;
     __asm__ __volatile__ ("mrs %0, CNTFRQ_EL0" : "=r" (freq));
     printf("freq %d\n",freq);
  return (int)freq;
  }

  ==
  gcc test.c test
  ./test

  This will report an illegal instruction, but should print a frequency
  value.

  [Regression Risk]
  The best way we can minimize risk is to verify on both a system that has an 
errata handler for the timer (D05) and a system that doesn't. We should then be 
exercising both code paths.

  I have regression tested this, using the above test case, on the HP
  m400, the QDT Centriq 2400, and a Cavium ThunderX CRB.

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

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

[Kernel-packages] [Bug 1689661] Re: No PMU support for ACPI-based arm64 systems

[dann frazier]

ubuntu@ubuntu:~$ cat /proc/version
Linux version 4.10.0-22-generic (buildd@bos01-arm64-038) (gcc version 6.3.0 
20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2) ) #24-Ubuntu SMP Mon May 22 17:43:39 
UTC 2017
ubuntu@ubuntu:~$ sudo perf list pmu | wc -l
24
ubuntu@ubuntu:~$ sudo perf list hw | wc -l
6


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

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

Title:
  No PMU support for ACPI-based arm64 systems

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

Bug description:
  [Impact]
  ACPI-based arm64 systems, such as the Qualcomm QDF2400 and the Hisilicon D05, 
do not currently have PMU support. This means that tools like perf are unable 
to use the built-in hardware event counters.

  [Test Case]
  On an ACPI-based arm64 system, run the following commands:

  sudo perf list pmu
  sudo perf list hw

  Without ACPI PMU support, these will be empty.

  [Regression Risk]
  The changes are restricted to ARM-specific code, other than an added enum 
value in linux/cpuhotplug.h. This reduces the non-negligible regression risk to 
the ARM architecture.

  For ACPI-based ARM platforms, regression risk is limited because they
  did not have PMU support previously. However, if this code is buggy,
  previously working commands that just made use of non-PMU events (e.g.
  perf top) might start causing problems. To mitigate this, I did a
  perf_fuzzer run on a QDF2400 (ACPI-based) and confirmed it survived
  (Note: this included a workaround for LP: #1689855, which will need to
  be fixed separately once upstreamed).

  For non-ACPI-based (i.e. devicetree) ARM platforms, there is a chance
  that the changes have broken PMU support. To mitigate that, I also did
  a perf_fuzzer run on a Cavium ThunderX system booted in DT mode, which
  it survived.

  Finally, the non-perf related changes in this series are restricted to
  a change in arch/arm64/kernel/smp.c that saves off pointers to each
  CPU's MADT GICC tables. The code is populating a static array with
  existing data - so pretty low risk (no pointer dereferences, etc).

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

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

[Kernel-packages] [Bug 1693820] 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/1693820

Title:
  Ubuntu boots to black screen when using kernel 4.10.0-21

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu Gnome 17.04.

  What I expected: When booting with kernel 4.10.0-21 I should see the
  GDM login page.

  What actually happens: When booting ubuntu gnome with kernel
  4.10.0-21, GDM doesn't start (or crashes) and I am stuck on a black
  screen or (if booting in verbose mode) the usual boot text (no
  particular error displayed). I can boot using kernel 4.10.0-20 with no
  problem.

  I have reproduced this issue on two computers, both with Nvidia
  graphics cards and nvidia proprietary graphics driver.

  linux-image-4.10.0-21-generic:
Installed: 4.10.0-21.23
Candidate: 4.10.0-21.23
Version table:
   *** 4.10.0-21.23 500
  500 http://fr.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  I can provide more information if needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zaf2783 F pulseaudio
   /dev/snd/pcmC0D0p:   zaf2783 F...m pulseaudio
   /dev/snd/controlC0:  zaf2783 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri May 26 16:29:28 2017
  HibernationDevice: RESUME=UUID=b990ea96-5baf-49e4-9e7b-e6c1ae0aa99c
  InstallationDate: Installed on 2015-06-23 (702 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: Acer Predator G3-605
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=da125261-3dd9-44ae-b88b-15634f861769 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-05-10 (16 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-C0
  dmi.board.name: Predator G3-605
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-C0:bd04/01/2014:svnAcer:pnPredatorG3-605:pvr:rvnAcer:rnPredatorG3-605:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G3-605
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1677319] Re: Support low-pin-count devices on Hisilicon SoCs

[dann frazier]

ubuntu@ubuntu:~$ cat /proc/version
Linux version 4.10.0-22-generic (buildd@bos01-arm64-038) (gcc version 6.3.0 
20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2) ) #24-Ubuntu SMP Mon May 22 17:43:39 
UTC 2017
ubuntu@ubuntu:~$ sudo ipmitool lan print
Set in Progress : Set Complete
IP Address Source   : Static Address
IP Address  : 
Subnet Mask : 
MAC Address : 
SNMP Community String   : TrapAdmin12#$
IP Header   : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
Default Gateway IP  : 10.228.68.1
802.1q VLAN ID  : Disabled
RMCP+ Cipher Suites : 0,1,2,3,17
Cipher Suite Priv Max   : XuuaXXX
: X=Cipher Suite Unused
: c=CALLBACK
: u=USER
: o=OPERATOR
: a=ADMIN
: O=OEM


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

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

Title:
  Support low-pin-count devices on Hisilicon SoCs

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

Bug description:
  [Impact]
  The HiSilicon Hip06/Hip07 SoCs include a low-pin-count (LPC) host controller. 
The Linux kernel needs support for this interface to use attached devices, such 
as a UART and the IPMI system interface.

  [Test Case]
  Boot up a HiSilicon D05 system, confirm that the following command returns 
w/o error:

  $ sudo ipmitool lan print

  [Regression Risk]
  The proposed patchset only enables LIBIO for arm64, so the greatest 
regression risk is to other arm64 systems. We have mitigated that by testing on 
a wide range of hardware (all certified arm64 servers + some in-devel systems). 
There remains some arch-independent changes to the generic PCI code. The patch 
"PCI: Restore codepath for !CONFIG_LIBIO" was added to mitigate the risk to 
other architectures by restoring the previous code for those architectures.

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

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

[Kernel-packages] [Bug 1693647] Re: Ubuntu just stops booting with recent kernels

[Joseph Salisbury]

Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.10 stable 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'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-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.17/


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

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

Title:
  Ubuntu just stops booting with recent kernels

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I happened after kernel 4.10.0-19 or 4.10.0-20
  With 4.10.0-19 it boots perfectly always. With older (and 4.10.0-21) it is 
booting... and just stops doing that. Nothing, no errors, no nothing. It leaves 
the screen the way it was(it may be some booting logs, or just black screen).
  But. If you load system with  4.10.0-19, than right after that you will 
probably be able to do that with 4.10.0-21 too, but only 1 time. 
  At this point I think that xanmod kernel has similar problems.
  Maybe the problem is because i have patch every kernel with 
  https://github.com/neurobin/MT7630E/
  in order to make wifi+bluetooth work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   leonid 9234 F...m pulseaudio
   /dev/snd/controlC1:  leonid 9234 F pulseaudio
   /dev/snd/controlC0:  leonid 9234 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri May 26 03:00:22 2017
  HibernationDevice: RESUME=UUID=361f24cb-c22f-4e7a-8167-fbf71e6deb9b
  InstallationDate: Installed on 2017-05-21 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=86435144-a418-4dfa-a7be-35d977907c9e ro quiet intel_pstate=passive 
zswap.enabled=1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-generic N/A
   linux-backports-modules-4.10.0-21-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.71
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2164
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.71:bd03/13/2017:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08971030410610100:rvnHewlett-Packard:rn2164:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 08971030410610100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1692836] Re: Dell XPS 9360 wifi 5G performance is poor

[Mario Limonciello]

@acelan,
I'm unsure on where this patch first came from and also don't understand the 
impact from calling this.  I know it was discussed on some forums as a solution 
to performance problems.  The reason that the vendor hasn't submitted upstream 
is they said there was discussion that this should be fixed in TCP driver and 
it's cross vendor impact.  I don't think that is true because this is not seen 
on Intel, only on QCA.

Given that and assuming it still has the large performance improvement
on newer kernel I think it's worth an attempt to submit upstream along
with the test data.  The data is irrefutable and if the maintainers
think it would be better to put the patch somewhere else, they can
recommend where it should go.

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

Title:
  Dell XPS 9360 wifi 5G performance is poor

Status in HWE Next:
  Fix Committed
Status in HWE Next xenial series:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  TX throughput is not good in Ubuntu in IEEE 802.11ac mode.

  Measured Rx 60Mbit/s and Tx 12Mbit/s with Ubuntu
  Windows 10 (1607) performs much better with on transmit side Rx 73MBit/s and 
Tx 62MBit/s using the same hardware setup.
  Same result with WPA2 disabled in unencrypted mode.

  Steps to Reproduce:
  1. connect to Wifi
  2. copy a large file from XPS 13 to a share on a 2nd system

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

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

[Kernel-packages] [Bug 1693673] Re: Ubuntu 16.04 IOB Error when the Mustang board rebooted

[Joseph Salisbury]

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

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

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

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

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

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

Title:
  Ubuntu 16.04 IOB Error when the Mustang board rebooted

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

Bug description:
  When rebooting the Mustang board (ARM64 based) running Tianocore 3.06.25 or 
3.07.09, the following warning messages are displayed:
  [   38.192057] xgene-edac 7880.edac: IOB bridge agent (BA) transaction 
error
  [   38.199164] xgene-edac 7880.edac: IOB BA write response error
  [   38.205230] xgene-edac 7880.edac: IOB BA write access at 0x00. 
(0x)
  [   38.213198] xgene-edac 7880.edac: IOB BA requestor ID 0x2722
  This happens on all Ubuntu Xenial, Ubuntu Yakkety and Ubuntu Zesty.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 26 12:21 seq
   crw-rw 1 root audio 116, 33 May 26 12:21 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f8faea1d-17bf-4c48-9b44-ca04875978b9
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Mustang Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-53-generic 
root=UUID=3d627b17-4ab5-4501-b673-46f3beeaf5a2 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-53-generic N/A
   linux-backports-modules-4.8.0-53-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-53-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: Feb 28 2017
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.07.09
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Mustang Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.07.09:bdFeb282017:svnAppliedMicro:pnX-GeneMustangBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMustangBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Mustang Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro

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

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

[Kernel-packages] [Bug 1693677] Re: Bluetooth and wifi not working

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 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.12-rc2


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

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

Title:
  Bluetooth and wifi not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Am unable to connect my laptop with any other devices using bluetooth
  and wifi. It does not show any device list eventhough it is turned on.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  siddharth   1573 F pulseaudio
   /dev/snd/controlC0:  siddharth   1573 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May 26 10:13:59 2017
  InstallationDate: Installed on 2017-04-12 (43 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
   
   ppp0  no wireless extensions.
  MachineType: Dell Inc. Inspiron 3543
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=718e2720-e3ad-4111-9b51-861762095f1c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 04XW3R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3543:pvrA07:rvnDellInc.:rn04XW3R:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3543
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1693820] [NEW] Ubuntu boots to black screen when using kernel 4.10.0-21

[zaf]

Public bug reported:

Using Ubuntu Gnome 17.04.

What I expected: When booting with kernel 4.10.0-21 I should see the GDM
login page.

What actually happens: When booting ubuntu gnome with kernel 4.10.0-21,
GDM doesn't start (or crashes) and I am stuck on a black screen or (if
booting in verbose mode) the usual boot text (no particular error
displayed). I can boot using kernel 4.10.0-20 with no problem.

I have reproduced this issue on two computers, both with Nvidia graphics
cards and nvidia proprietary graphics driver.

linux-image-4.10.0-21-generic:
  Installed: 4.10.0-21.23
  Candidate: 4.10.0-21.23
  Version table:
 *** 4.10.0-21.23 500
500 http://fr.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages
100 /var/lib/dpkg/status

I can provide more information if needed.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-20-generic 4.10.0-20.22
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  zaf2783 F pulseaudio
 /dev/snd/pcmC0D0p:   zaf2783 F...m pulseaudio
 /dev/snd/controlC0:  zaf2783 F pulseaudio
CurrentDesktop: GNOME
Date: Fri May 26 16:29:28 2017
HibernationDevice: RESUME=UUID=b990ea96-5baf-49e4-9e7b-e6c1ae0aa99c
InstallationDate: Installed on 2015-06-23 (702 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Acer Predator G3-605
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=da125261-3dd9-44ae-b88b-15634f861769 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-20-generic N/A
 linux-backports-modules-4.10.0-20-generic  N/A
 linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-05-10 (16 days ago)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P11-C0
dmi.board.name: Predator G3-605
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-C0:bd04/01/2014:svnAcer:pnPredatorG3-605:pvr:rvnAcer:rnPredatorG3-605:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Predator G3-605
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug zesty

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

Title:
  Ubuntu boots to black screen when using kernel 4.10.0-21

Status in linux package in Ubuntu:
  New

Bug description:
  Using Ubuntu Gnome 17.04.

  What I expected: When booting with kernel 4.10.0-21 I should see the
  GDM login page.

  What actually happens: When booting ubuntu gnome with kernel
  4.10.0-21, GDM doesn't start (or crashes) and I am stuck on a black
  screen or (if booting in verbose mode) the usual boot text (no
  particular error displayed). I can boot using kernel 4.10.0-20 with no
  problem.

  I have reproduced this issue on two computers, both with Nvidia
  graphics cards and nvidia proprietary graphics driver.

  linux-image-4.10.0-21-generic:
Installed: 4.10.0-21.23
Candidate: 4.10.0-21.23
Version table:
   *** 4.10.0-21.23 500
  500 http://fr.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  I can provide more information if needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zaf2783 F pulseaudio
   /dev/snd/pcmC0D0p:   zaf2783 F...m pulseaudio
   /dev/snd/controlC0:  zaf2783 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri May 26 16:29:28 2017
  HibernationDevice: RESUME=UUID=b990ea96-5baf-49e4-9e7b-e6c1ae0aa99c
  InstallationDate: Installed on 2015-06-23 (702 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: Acer Predator G3-605
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=da125261-3dd9-44ae-b88b-15634f861769 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164.1
  

[Kernel-packages] [Bug 1693597] Re: vhba: loading out-of-tree module taints kernel.

[Joseph Salisbury]

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

Title:
  vhba: loading out-of-tree module taints kernel.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dmesg:
  [4.815849] vhba: loading out-of-tree module taints kernel.
  [4.815884] vhba: module verification failed: signature and/or required 
key missing - tainting kernel
  [4.816249] scsi host6: vhba

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2098 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2098 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 25 15:18:53 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (669 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-generic N/A
   linux-backports-modules-4.10.0-21-generic  N/A
   linux-firmware 1.165
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-05-15 (9 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1693566] Re: Ubuntu 16.04.03: "NMI watchdog: BUG: soft lockup" occurs while running stress-ng on PowerNV machine.

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 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.12-rc2


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

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

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

Title:
  Ubuntu 16.04.03: "NMI watchdog: BUG: soft lockup" occurs while running
  stress-ng on PowerNV machine.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-05-17 
05:55:38 ==
  --- Problem description 

  Ubuntu 16.04.03: "NMI watchdog: BUG: soft lockup" occurs while running
  stress-ng on NV machine.

  --- Steps to recreate--

  1. Install ubuntu16.04.03.
  2. Run "stress-ng -a 0".

  Logs:
  

  [ 2660.437087] INFO: rcu_sched self-detected stall on CPU
  [ 2660.437111]22-...: (5247 ticks this GP) idle=e19/141/0 
softirq=905/905 fqs=2380 
  [ 2660.437114] (t=5251 jiffies g=95606 c=95605 q=2545946)
  [ 2660.437750]24-...: (5250 ticks this GP) idle=0b7/141/0 
softirq=5805/5805 fqs=2380 
  [ 2660.437859]
  [ 2664.172796] NMI watchdog: BUG: soft lockup - CPU#22 stuck for 23s! 
[stress-ng-mmap:3509]
  [ 2664.172808] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 23s! 
[stress-ng-mrema:3536]
  [ 2674.848037] NMI watchdog: BUG: soft lockup - CPU#5 stuck for 33s! 
[stress-ng-fork:3381]
  [ 2676.172894] NMI watchdog: BUG: soft lockup - CPU#30 stuck for 22s! 
[kswapd0:992]
  [ 2680.336844] NMI watchdog: BUG: soft lockup - CPU#98 stuck for 23s! 
[stress-ng-clock:5099]
  [ 2686.140931] NMI watchdog: BUG: soft lockup - CPU#16 stuck for 39s! 
[stress-ng-clone:3366]
  [ 2686.987192] xhci_hcd 0003:09:00.0: HC died; cleaning up
  [ 2686.987212] usb 1-3-port3: cannot reset (err = -108)

  After few hours machine will become completely unresponsive

  [pavithra@localhost ~]$ ping 9.47.69.255
  PING 9.47.69.255 (9.47.69.255) 56(84) bytes of data.
  ^C
  --- 9.47.69.255 ping statistics ---
  12 packets transmitted, 0 received, 100% packet loss, time 11000ms

  
  Thanks,
  Pavithra

  == Comment: #6 - VIPIN K. PARASHAR  - 2017-05-25 
03:32:26 ==
  ubuntu@ltc-firep2:~$ hostname -i
  9.47.69.255
  ubuntu@ltc-firep2:~$ uname -a
  Linux ltc-firep2 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
  ubuntu@ltc-firep2:~$ cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.04.2 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.2 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  ubuntu@ltc-firep2:~$ tail /proc/cpuinfo
  processor : 159
  cpu   : POWER8 (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.0 (pvr 004d 0200)

  timebase  : 51200
  platform  : PowerNV
  model : 8335-GTA
  machine   : PowerNV 8335-GTA
  firmware  : OPAL
  ubuntu@ltc-firep2:~$

  
  == Comment: #11 - VIPIN K. PARASHAR  - 2017-05-25 
06:27:12 ==
  System Memory stats
  ==
  ubuntu@ltc-firep2:~$ numactl -H
  available: 2 nodes (0,8)
  node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 
25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 
51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 
77 78 79
  node 0 size: 61321 MB
  node 0 free: 60297 MB
  node 8 cpus: 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 
101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 
121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 
141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159
  node 8 size: 65303 MB
  node 8 free: 64923 MB
  node distances:
  node   0   8 
0:  10  40 
8:  40  10 
  ubuntu@ltc-firep2:~$ free -h 
totalusedfree  shared  buff/cache   
available
  Mem:   123G534M122G 20M868M
121G
  Swap:   37G  0B 

[Kernel-packages] [Bug 1692589] Re: linux: 4.8.0-54.57 -proposed tracker

[Łukasz Zemczak]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1693618] Re: Microcode SW error detected.

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 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.12-rc2


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

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

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

Title:
  Microcode SW error detected.

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  In dmesg logs I see

  [81251.363118] iwlwifi :04:00.0: regular scan timed out
  [81251.363235] iwlwifi :04:00.0: Microcode SW error detected.  Restarting 
0x200.
  [81251.363241] iwlwifi :04:00.0: CSR values:
  [81251.363244] iwlwifi :04:00.0: (2nd byte of CSR_INT_COALESCING is 
CSR_INT_PERIODIC_REG)
  [81251.363250] iwlwifi :04:00.0:CSR_HW_IF_CONFIG_REG: 0X00c89008
  [81251.363256] iwlwifi :04:00.0:  CSR_INT_COALESCING: 0X0040
  [81251.363261] iwlwifi :04:00.0: CSR_INT: 0X
  [81251.363266] iwlwifi :04:00.0:CSR_INT_MASK: 0X
  [81251.363271] iwlwifi :04:00.0:   CSR_FH_INT_STATUS: 0X
  [81251.363276] iwlwifi :04:00.0: CSR_GPIO_IN: 0X0019
  [81251.363281] iwlwifi :04:00.0:   CSR_RESET: 0X
  [81251.363286] iwlwifi :04:00.0:CSR_GP_CNTRL: 0X08040005
  [81251.363292] iwlwifi :04:00.0:  CSR_HW_REV: 0X0201
  [81251.363296] iwlwifi :04:00.0:  CSR_EEPROM_REG: 0Xd5d5
  [81251.363302] iwlwifi :04:00.0:   CSR_EEPROM_GP: 0Xd5d5
  [81251.363306] iwlwifi :04:00.0:  CSR_OTP_GP_REG: 0Xd5d5
  [81251.363311] iwlwifi :04:00.0: CSR_GIO_REG: 0X001f0044
  [81251.363316] iwlwifi :04:00.0:CSR_GP_UCODE_REG: 0X
  [81251.363321] iwlwifi :04:00.0:   CSR_GP_DRIVER_REG: 0X
  [81251.363326] iwlwifi :04:00.0:   CSR_UCODE_DRV_GP1: 0X
  [81251.363331] iwlwifi :04:00.0:   CSR_UCODE_DRV_GP2: 0X
  [81251.363336] iwlwifi :04:00.0: CSR_LED_REG: 0X0060
  [81251.363341] iwlwifi :04:00.0:CSR_DRAM_INT_TBL_REG: 0X8884993d
  [81251.363346] iwlwifi :04:00.0:CSR_GIO_CHICKEN_BITS: 0X07800200
  [81251.363351] iwlwifi :04:00.0: CSR_ANA_PLL_CFG: 0Xd5d5
  [81251.363356] iwlwifi :04:00.0:  CSR_MONITOR_STATUS_REG: 0Xc03803c0
  [81251.363361] iwlwifi :04:00.0:   CSR_HW_REV_WA_REG: 0X0001001a
  [81251.363366] iwlwifi :04:00.0:CSR_DBG_HPET_MEM_REG: 0X0010
  [81251.363369] iwlwifi :04:00.0: FH register values:
  [81251.363384] iwlwifi :04:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 
0X848c7800
  [81251.363398] iwlwifi :04:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 
0X0848c080
  [81251.363413] iwlwifi :04:00.0:  FH_RSCSR_CHNL0_WPTR: 
0X00f0
  [81251.363427] iwlwifi :04:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 
0X00801054
  [81251.363442] iwlwifi :04:00.0:  FH_MEM_RSSR_SHARED_CTRL_REG: 
0X00fc
  [81251.363456] iwlwifi :04:00.0:FH_MEM_RSSR_RX_STATUS_REG: 
0X0303
  [81251.363471] iwlwifi :04:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 
0X
  [81251.363486] iwlwifi :04:00.0:FH_TSSR_TX_STATUS_REG: 
0X07ff
  [81251.363500] iwlwifi :04:00.0: FH_TSSR_TX_ERROR_REG: 
0X
  [81251.363612] iwlwifi :04:00.0: Start IWL Error Log Dump:
  [81251.363615] iwlwifi :04:00.0: Status: 0x, count: 6
  [81251.363618] iwlwifi :04:00.0: Loaded firmware version: 21.302800.0
  [81251.363622] iwlwifi :04:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN
  [81251.363624] iwlwifi :04:00.0: 0x06F4 | trm_hw_status0
  [81251.363627] iwlwifi :04:00.0: 0x | trm_hw_status1
  [81251.363630] iwlwifi :04:00.0: 0x0BD8 | branchlink2
  [81251.363632] iwlwifi :04:00.0: 0x00026AC4 | interruptlink1
  [81251.363635] iwlwifi :04:00.0: 0x00026AC4 | interruptlink2
  [81251.363637] iwlwifi :04:00.0: 0x | data1
  [81251.363640] iwlwifi :04:00.0: 0x0080 | data2
  [81251.363642] iwlwifi :04:00.0: 0x0783 | data3
  [81251.363645] 

[Kernel-packages] [Bug 1693685] Re: Blutooth is not working

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 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.12-rc2


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

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

Title:
  Blutooth is not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ usb-devices | awk '/13d3/' RS=
  gives no result

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-52-generic 4.8.0-52.55
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ranjeet2387 F pulseaudio
   /dev/snd/controlC0:  ranjeet2387 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May 26 11:09:22 2017
  HibernationDevice: RESUME=UUID=8823c2c4-8af3-45e4-bd2d-2ab5eee8f42c
  InstallationDate: Installed on 2017-05-03 (22 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   lono wireless extensions.
   
   enxfcde56ff0106  no wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: LENOVO 80K4
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic.efi.signed 
root=UUID=0e2cebd8-df99-45be-9d45-5940a9660d39 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-52-generic N/A
   linux-backports-modules-4.8.0-52-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2017-05-17 (8 days ago)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CACN31WW(V2.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad 500-15ACZ
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 500-15ACZ
  dmi.modalias: 
dmi:bvnLENOVO:bvrCACN31WW(V2.04):bd09/13/2016:svnLENOVO:pn80K4:pvrLenovoideapad500-15ACZ:rvnLENOVO:rnLenovoideapad500-15ACZ:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoideapad500-15ACZ:
  dmi.product.name: 80K4
  dmi.product.version: Lenovo ideapad 500-15ACZ
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[François]

@kaihengfeng: could you please expand on your comment in #73? is it
something that can be done with kernel options? does the kernel in
proposed mentioned in #74 also fixing the issue you are mentioning? also
note that I have an XPS 9560 (not 9550).

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

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

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV: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/1678184/+subscriptions

-- 
Mailing list: https://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 1686268] Re: Backlight brightness level not restored after reboot

[Kai-Heng Feng]

On Fri, May 26, 2017 at 19:55 Mario Limonciello 
wrote:

> But so we're talking about the slider in the bios that adjusts keyboard
> backlight right? That's not tied to display backlight.


> No, the "Video" tab in BIOS has two sliders, one is for AC and another one
is for battery. Both of them are for display brightness.


> On Fri, May 26, 2017, 00:31 Kai-Heng Feng 
> wrote:
>
> > It can't be reproduced once you changed the brightness via slider in
> > BIOS.
> >
> > It should be reproduceable if the brightness was *never* touched in
> > BIOS.
> >
> > Once the brightness is changed in BIOS, the issue can no longer be
> > reproduced regardless the brightness value.
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1686268
> >
> > Title:
> >   Backlight brightness level not restored after reboot
> >
> > To manage notifications about this bug go to:
> >
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+subscriptions
> >
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1686268
>
> Title:
>   Backlight brightness level not restored after reboot
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I am not sure if this is the right place to report this, so feel free
>   to move it elsewhere.
>
>   It looks like the systemd-backlight service (/lib/systemd/system
>   /systemd-backlight@.service) does not restore the brightness level
>   (although it saves it before shut-down).
>
>   However the following command does restore the saved brightness:
>
>   sudo /lib/systemd/systemd-backlight load backlight:intel_backlight
>
>   As a temporary solution to automate it at boot I am using the
>   following line added to the root cron:
>
>   @reboot /lib/systemd/systemd-backlight load backlight:intel_backlight
>
>   - Ubuntu 4.10.0-20.22-generic 4.10.8
>   - Gnome 3.24
>
>   Please, let me know if you need more info. Thanks.
>   ---
>   ApportVersion: 2.20.4-0ubuntu4
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  dd 1540 F pulseaudio
>   CurrentDesktop: GNOME
>   DistroRelease: Ubuntu 17.04
>   InstallationDate: Installed on 2017-04-12 (13 days ago)
>   InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64
> (20170411)
>   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 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: Dell Inc. Precision 5520
>   Package: linux (not installed)
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed
> root=/dev/mapper/nvme-ubuntu_gnome ro systemd.restore_state=1 quiet splash
> vt.handoff=7
>   ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
>   RelatedPackageVersions:
>linux-restricted-modules-4.10.0-20-generic N/A
>linux-backports-modules-4.10.0-20-generic  N/A
>linux-firmware 1.164
>   Tags:  zesty
>   Uname: Linux 4.10.0-20-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 03/29/2017
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.2.4
>   dmi.board.name: 06X96V
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.name: Precision 5520
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+subscriptions
>

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

Title:
  Backlight brightness level not restored after reboot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am not sure if this is the right place to report this, so feel free
  to move it elsewhere.

  It looks like the systemd-backlight service (/lib/systemd/system
  /systemd-backlight@.service) does not restore the brightness level
  (although it saves it before shut-down).

  However the following command does restore the saved brightness:

  sudo /lib/systemd/systemd-backlight load backlight:intel_backlight

  As a temporary solution to automate it at boot I am using the
  following line added to the root cron:

  @reboot /lib/systemd/systemd-backlight load backlight:intel_backlight

  - Ubuntu 4.10.0-20.22-generic 4.10.8
  - Gnome 3.24

  Please, let 

[Kernel-packages] [Bug 1693345] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [khugepaged:38]

[Nabeel Omer]

One of these appear every time I resume from suspend.

[ 9387.911475] [ cut here ]
[ 9387.911519] WARNING: CPU: 2 PID: 0 at 
/home/kernel/COD/linux/net/mac80211/rx.c:630 ieee80211_rx_napi+0x905/0xa20 
[mac80211]
[ 9387.911520] Modules linked in: rtsx_usb_ms memstick rtsx_usb_sdmmc rtsx_usb 
ccm rfcomm bnep nls_iso8859_1 hid_rmi cmdlinepart rmi_core joydev 
intel_spi_platform intel_spi spi_nor intel_rapl mtd x86_pkg_temp_thermal 
intel_powerclamp kvm_intel dell_wmi sparse_keymap kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel arc4 pcbc dell_laptop 
dell_smbios ath9k dcdbas ath9k_common dell_smm_hwmon snd_hda_codec_hdmi 
snd_hda_codec_realtek aesni_intel snd_soc_rt5640 snd_hda_codec_generic 
aes_x86_64 snd_soc_rl6231 crypto_simd glue_helper ath9k_hw snd_hda_intel 
snd_soc_core uvcvideo snd_hda_codec cryptd ath snd_hda_core intel_cstate 
videobuf2_vmalloc snd_hwdep videobuf2_memops videobuf2_v4l2 snd_compress 
intel_rapl_perf ac97_bus snd_seq_midi mac80211 videobuf2_core snd_pcm_dmaengine 
snd_seq_midi_event
[ 9387.911566]  snd_rawmidi input_leds videodev ath3k hid_multitouch serio_raw 
cfg80211 btusb snd_pcm media snd_seq btrtl btbcm btintel snd_seq_device 
elan_i2c bluetooth snd_timer snd ecdh_generic soundcore mei_me shpchp lpc_ich 
mei snd_soc_sst_acpi i2c_designware_platform dw_dmac snd_soc_sst_match 
i2c_designware_core dw_dmac_core spi_pxa2xx_platform 8250_dw dell_rbtn 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 nf_conntrack_broadcast 
nf_nat_ftp nf_nat nf_conntrack_ftp coretemp nf_conntrack parport_pc libcrc32c 
ppdev iptable_filter lp parport ip_tables x_tables autofs4
[ 9387.911617]  usbhid i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 ahci drm libahci mii wmi video sdhci_acpi sdhci 
i2c_hid hid
[ 9387.911634] CPU: 2 PID: 0 Comm: swapper/2 Tainted: GW   
4.12.0-041200rc2-generic #201705212331
[ 9387.911635] Hardware name: Dell Inc. Inspiron 3542/0KHNVP, BIOS A03 
05/27/2014
[ 9387.911637] task: 97edd6294380 task.stack: b2ba80cd
[ 9387.911662] RIP: 0010:ieee80211_rx_napi+0x905/0xa20 [mac80211]
[ 9387.911664] RSP: 0018:97eddfb03d18 EFLAGS: 00010246
[ 9387.911666] RAX: 0001 RBX: 97ed0209b200 RCX: 97edd03fc1a8
[ 9387.911667] RDX: 0004 RSI: c09c8000 RDI: 97edcfac0780
[ 9387.911669] RBP: 97eddfb03de8 R08:  R09: 97eddfda5000
[ 9387.911670] R10:  R11:  R12: 
[ 9387.911671] R13:  R14: 97edd12c9ab8 R15: 97edcfac0780
[ 9387.911673] FS:  () GS:97eddfb0() 
knlGS:
[ 9387.911674] CS:  0010 DS:  ES:  CR0: 80050033
[ 9387.911676] CR2: 7f573ab25000 CR3: 0001b6a09000 CR4: 001406e0
[ 9387.911677] Call Trace:
[ 9387.911679]  
[ 9387.911687]  ? map_single+0x32/0x80
[ 9387.911691]  ? __netdev_alloc_skb+0xc8/0x120
[ 9387.911695]  ? ath9k_cmn_rx_skb_postprocess+0x4c/0x130 [ath9k_common]
[ 9387.911698]  ? swiotlb_tbl_unmap_single+0xf4/0x120
[ 9387.911707]  ath_rx_tasklet+0xacc/0xff0 [ath9k]
[ 9387.911714]  ath9k_tasklet+0x1e4/0x250 [ath9k]
[ 9387.911718]  tasklet_action+0x5e/0x110
[ 9387.911723]  __do_softirq+0x104/0x28f
[ 9387.911726]  irq_exit+0xb6/0xc0
[ 9387.911729]  do_IRQ+0x4f/0xd0
[ 9387.911732]  common_interrupt+0x89/0x89
[ 9387.911737] RIP: 0010:cpuidle_enter_state+0x121/0x2c0
[ 9387.911738] RSP: 0018:b2ba80cd3e60 EFLAGS: 0246 ORIG_RAX: 
ff5e
[ 9387.911741] RAX:  RBX: 0006 RCX: 001f
[ 9387.911742] RDX: 0889cb1fc036 RSI: 97eddfb19718 RDI: 
[ 9387.911743] RBP: b2ba80cd3e98 R08: 02b2 R09: 0018
[ 9387.911744] R10: b2ba80cd3e30 R11: 0139 R12: 97eddfb24900
[ 9387.911746] R13: 8c387b58 R14: 0889cb1fc036 R15: 8c387b40
[ 9387.911747]  
[ 9387.911751]  cpuidle_enter+0x17/0x20
[ 9387.911755]  call_cpuidle+0x23/0x40
[ 9387.911758]  do_idle+0x194/0x200
[ 9387.911761]  cpu_startup_entry+0x71/0x80
[ 9387.911767]  start_secondary+0x154/0x190
[ 9387.911770]  secondary_startup_64+0x9f/0x9f
[ 9387.911772] Code: ff 48 8b 95 70 ff ff ff 4c 8b ab d8 00 00 00 4c 8b b2 d8 
00 00 00 e9 8c f9 ff ff 48 89 de 4c 89 ff e8 50 1d fe ff e9 d0 f9 ff ff <0f> ff 
48 89 df e8 71 2f 45 cb e9 d5 f7 ff ff 0f ff e9 c6 f7 ff 
[ 9387.911814] ---[ end trace affb4b11847df9d2 ]---

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [khugepaged:38]

Status in linux package in 

[Kernel-packages] [Bug 1686519] Re: POWER9: CAPI2 enablement

[bugproxy]

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

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

Title:
  POWER9: CAPI2 enablement

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

Bug description:
  == Comment: #0 - Breno Henrique Leitao  - 2017-04-26 
15:08:18 ==
  Hello,

  We would like to include CAPI2  support on the CXL device driver on
  Zesty kernel.

   The coherent accelerator interface is designed to allow the coherent
  connection of accelerators (FPGAs and other devices) to a  POWER
  system. These devices need to adhere to the Coherent Accelerator
  Interface Architecture (CAIA).

  
This PSL Version 9 provides new features such as:
  * Interaction with the nest MMU on the P9 chip.
  * Native DMA support.
  * Supports sending ASB_Notify messages for host thread wakeup.
  * Supports Atomic operations.

  == Comment: #3 - Breno Henrique Leitao  - 2017-04-26 
15:21:25 ==
  These are the patches we need:

  f24be42aab37c6d07c05126673138e06223a6399 cxl: Add psl9 specific code
  d7b1946c7925a270062b2e0718aa57b42ba619c0 cxl: Force psl data-cache flush 
during device shutdown
  abd1d99bb3da42d6c7341c14986f5b8f4dcc6bd5 cxl: Isolate few psl8 specific calls
  64663f372c72cedeba1b1dc86df9cc159ae5a93d cxl: Rename some psl8 specific 
functions
  bdd2e7150644fee4de7167a3e08294ef32eeda11 cxl: Update implementation service 
layer
  6dd2d23403396d8e6d153a6c9db56e1a1012bad8 cxl: Keep track of mm struct 
associated with a context
  66ef20c7834b7df18168b12a57ef01c6ae0d1a81 cxl: Remove unused values in 
bare-metal environment.
  aba81433b50350fde68bf80fe9f75d671e15b5ae cxl: Read vsec perst load image
  39d40871526627fd0e2cfc1e2fb88500a5049c4c cxl: Fix build when CONFIG_DEBUG_FS=n

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

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

[Kernel-packages] [Bug 1690155] Re: Fix NVLINK2 TCE route

[bugproxy]

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

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

Title:
  Fix NVLINK2 TCE route

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  == Comment: #0 - Breno Henrique Leitao  -
  2017-05-11 09:14:17 ==

  Commit 616badd2fb49 ("powerpc/powernv: Use OPAL call for TCE kill on
  NVLink2") forced all TCE kills to go via the OPAL call for
  NVLink2. However the PHB3 implementation of TCE kill was still being
  called directly from some functions which in some circumstances caused
  a machine check

  The following commit was added into zesty using LP#1667081

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

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

[Kernel-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Esokrates]

Confirming Daniel van Vugt: The kernel
http://people.canonical.com/~khfeng/lp1654448/ does not improve the
situation.

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

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

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

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

[bugproxy]

--- Comment From pavra...@in.ibm.com 2017-05-26 05:50 EDT---
Issue is observed even on Ubuntu 16.04.03.

root@ltc-firep2:/sys/fs/pstore# ls -lrt
total 0
-r--r--r-- 1 root root  3909 May  5 04:21 dmesg-nvram-1
-r--r--r-- 1 root root  4080 May 26 02:59 powerpc-opal-nvram-8
-r--r--r-- 1 root root 65520 May 26 02:59 powerpc-common-nvram-6

root@ltc-firep2:/sys/fs/pstore# ls -lrt
total 0
-r--r--r-- 1 root root  3909 May  5 04:21 dmesg-nvram-1
-r--r--r-- 1 root root  4080 May 26 02:59 powerpc-opal-nvram-8
-r--r--r-- 1 root root 65520 May 26 02:59 powerpc-common-nvram-6
root@ltc-firep2:/sys/fs/pstore# tail dmesg-nvram-1
<4>[  351.724539] LR [c05dd79c] write_sysrq_trigger+0x10c/0x230
<4>[  351.724583] Call Trace:
<4>[  351.724603] [c00fd79b7cf0] [c05dd77c] 
write_sysrq_trigger+0xec/0x230 (unreliable)
<4>[  351.724677] [c00fd79b7d90] [c03dabd4] 
proc_reg_write+0x84/0x120
<4>[  351.724733] [c00fd79b7dd0] [c0327520] SyS_write+0x150/0x400
<4>[  351.724789] [c00fd79b7e30] [c000a17c] system_call+0x38/0xb4
<4>[  351.724843] Instruction dump:
<4>[  351.724870] 409effb8 7fc3f378 4bfff381 4bac 3c4c00c1 384205c0 
3d42fff2 394ac530
<4>[  351.724963] 3921 912a 7c0004ac 3940 <992a> 4e800020 
6000 6042
<4>[  351.725055] ---[ end trace 9de875846d84dfcd ]---

root@ltc-firep2:/sys/fs/pstore# ls -lrt
total 0
-r--r--r-- 1 root root  3909 May  5 04:21 dmesg-nvram-1
-r--r--r-- 1 root root  4080 May 26 05:31 powerpc-opal-nvram-8
-r--r--r-- 1 root root 65520 May 26 05:31 powerpc-common-nvram-6
root@ltc-firep2:/sys/fs/pstore# tail dmesg-nvram-1
<4>[  351.724539] LR [c05dd79c] write_sysrq_trigger+0x10c/0x230
<4>[  351.724583] Call Trace:
<4>[  351.724603] [c00fd79b7cf0] [c05dd77c] 
write_sysrq_trigger+0xec/0x230 (unreliable)
<4>[  351.724677] [c00fd79b7d90] [c03dabd4] 
proc_reg_write+0x84/0x120
<4>[  351.724733] [c00fd79b7dd0] [c0327520] SyS_write+0x150/0x400
<4>[  351.724789] [c00fd79b7e30] [c000a17c] system_call+0x38/0xb4
<4>[  351.724843] Instruction dump:
<4>[  351.724870] 409effb8 7fc3f378 4bfff381 4bac 3c4c00c1 384205c0 
3d42fff2 394ac530
<4>[  351.724963] 3921 912a 7c0004ac 3940 <992a> 4e800020 
6000 6042
<4>[  351.725055] ---[ end trace 9de875846d84dfcd ]---
root@ltc-firep2:/sys/fs/pstore#

Thanks,
Pavithra

--- Comment From hegdevas...@in.ibm.com 2017-05-26 07:55 EDT---
... based on previous comment .. can you please backport patch to 16.04.03 as 
well?

-Vasant

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

Title:
  PowerPC: Pstore dump for powerpc is broken

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

Bug description:
  ---Problem Description---
  Pstore write is broken for PowerPC. On panic, kernel doesn't write mesg to 
/fs/pstore/dmesg*
  (Entry doesn't gets created at all)
   
  Contact Information = Ankit Kumar/kumar.ankit...@in.ibm.com 
   
  ---uname output---
  Linux seedlp2 4.10.0-15-generic #17-Ubuntu SMP Fri Mar 24 17:50:37 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  Write to nvram failed
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Checked kdump kernel is loaded.
  2. Triggered system crash
  # echo c > /proc/sysrq-trigger

  3. /sys/fs/pstore/dmesg* doesn't gets created

  This issue can be reproduced after commit c950fd6f201

  c950fd6f201 - pstore: Split pstore fragile flags

  It introduces  PSTORE_FLAGS_DMESG, which is not set for PowerPC.

  
  Please include below commit 041939c1ec5 as this fixes this issue.

  commit 041939c1ec54208b42f5cd819209173d52a29d34
  Author: Ankit Kumar 
  Date:   Thu Apr 27 17:03:13 2017 +0530

  pstore: Fix flags to enable dumps on powerpc
  
  After commit c950fd6f201a kernel registers pstore write based on flag set.
  Pstore write for powerpc is broken as flags(PSTORE_FLAGS_DMESG) is not 
set for
  powerpc architecture. On panic, kernel doesn't write message to
  /fs/pstore/dmesg*(Entry doesn't gets created at all).
  
  This patch enables pstore write for powerpc architecture by setting
  PSTORE_FLAGS_DMESG flag.
  
  Fixes: c950fd6f201a ("pstore: Split pstore fragile flags")
  Cc: sta...@vger.kernel.org # v4.9+
  Signed-off-by: Ankit Kumar 
  Signed-off-by: Kees Cook 

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

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

Re: [Kernel-packages] [Bug 1686268] Re: Backlight brightness level not restored after reboot

[Mario Limonciello]

But so we're talking about the slider in the bios that adjusts keyboard
backlight right? That's not tied to display backlight.

On Fri, May 26, 2017, 00:31 Kai-Heng Feng 
wrote:

> It can't be reproduced once you changed the brightness via slider in
> BIOS.
>
> It should be reproduceable if the brightness was *never* touched in
> BIOS.
>
> Once the brightness is changed in BIOS, the issue can no longer be
> reproduced regardless the brightness value.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1686268
>
> Title:
>   Backlight brightness level not restored after reboot
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+subscriptions
>

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

Title:
  Backlight brightness level not restored after reboot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am not sure if this is the right place to report this, so feel free
  to move it elsewhere.

  It looks like the systemd-backlight service (/lib/systemd/system
  /systemd-backlight@.service) does not restore the brightness level
  (although it saves it before shut-down).

  However the following command does restore the saved brightness:

  sudo /lib/systemd/systemd-backlight load backlight:intel_backlight

  As a temporary solution to automate it at boot I am using the
  following line added to the root cron:

  @reboot /lib/systemd/systemd-backlight load backlight:intel_backlight

  - Ubuntu 4.10.0-20.22-generic 4.10.8
  - Gnome 3.24

  Please, let me know if you need more info. Thanks.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dd 1540 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-04-12 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170411)
  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 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=/dev/mapper/nvme-ubuntu_gnome ro systemd.restore_state=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/29/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 06X96V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1693492] Re: constant machine crashes

[Mathieu Marquer]

*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838

** This bug has been marked a duplicate of bug 1674838
   kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

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

Title:
  constant machine crashes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since I upgraded to Zesty, I have experienced constant soft crashes on
  my machine. Symptoms are that I can still move the mouse cursor around
  on my X display, but none of the windows respond to button or key
  presses. The mouse cursor will even trigger edge-flips when bumping up
  against the edge of the screen, but the key bindings to do the same do
  not work. Sometimes (more often not) I can ssh into the machine to
  reboot, but most attempts just time out after the "connection
  establised" message. If I attempt to switch to a text console (eg.
  ctrl-alt-F1), the machine appears to lock up completely (even the
  mouse stops responding).

  Obviously, I can't collect a log during the problem. I have to reboot
  by holding down the power button! But after that, this is what I
  typically find in the kern.log:


  May 25 01:59:41 inanna kernel: [33992.896206] [ cut here 
]
  May 25 01:59:41 inanna kernel: [33992.896231] kernel BUG at 
/build/linux-lz1RHE/linux-4.10.0/include/linux/swapops.h:129!
  May 25 01:59:41 inanna kernel: [33992.896255] invalid opcode:  [#1] SMP
  May 25 01:59:41 inanna kernel: [33992.896268] Modules linked in: xfrm_user 
xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo ccm 
bbswitch(OE) msr bluetooth binfmt_misc uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media hp_wmi 
sparse_keymap mxm_wmi snd_hda_codec_hdmi snd_hda_codec_idt 
snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm intel_rapl x86_pkg_temp_thermal snd_seq_midi snd_seq_midi_event 
snd_rawmidi arc4 snd_seq kvm irqbypass rt2800pci rt2800mmio rt2800lib 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel rt2x00pci rt2x00mmio pcbc 
aesni_intel snd_seq_device snd_timer snd aes_x86_64 nvidia_uvm(POE) soundcore 
rt2x00lib mac80211 cfg80211 crypto_simd glue_helper mei_me eeprom_93cx6 cryptd 
rtsx_pci_ms intel_cstate memstick intel_rapl_perf mei
  May 25 01:59:41 inanna kernel: [33992.896477]  shpchp lpc_ich hp_accel 
input_leds joydev intel_smartconnect lis3lv02d input_polldev mac_hid wmi 
serio_raw coretemp ppdev lp parport ip_tables x_tables autofs4 hid_generic 
usbhid hid i915 nvidia_drm(POE) nvidia_modeset(POE) rtsx_pci_sdmmc nvidia(POE) 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
psmouse ahci r8169 drm libahci rtsx_pci mii fjes video [last unloaded: 
parport_pc]
  May 25 01:59:41 inanna kernel: [33992.896591] CPU: 3 PID: 11909 Comm: JS 
Helper Tainted: P   OE   4.10.0-21-generic #23-Ubuntu
  May 25 01:59:41 inanna kernel: [33992.896617] Hardware name: Hewlett-Packard 
HP Pavilion dv7 Notebook PC/181D, BIOS F.0A 05/02/2012
  May 25 01:59:41 inanna kernel: [33992.896643] task: 8e2861381680 
task.stack: a68a429d4000
  May 25 01:59:41 inanna kernel: [33992.896663] RIP: 
0010:__migration_entry_wait+0x16a/0x180
  May 25 01:59:41 inanna kernel: [33992.896680] RSP: :a68a429d7d68 
EFLAGS: 00010246
  May 25 01:59:41 inanna kernel: [33992.896697] RAX: 000fc0048078 RBX: 
d36204acf8f0 RCX: d36204acf8f0
  May 25 01:59:41 inanna kernel: [33992.896718] RDX: 0001 RSI: 
8e282b3e3800 RDI: d36200324000
  May 25 01:59:41 inanna kernel: [33992.896739] RBP: a68a429d7d80 R08: 
8e29515dc5c0 R09: 8e29515dc5c0
  May 25 01:59:41 inanna kernel: [33992.896760] R10: 7f63fd3000c8 R11: 
0206 R12: d36200324000
  May 25 01:59:41 inanna kernel: [33992.896781] R13: 3e00c900 R14: 
a68a429d7e30 R15: 8e28e4b25960
  May 25 01:59:41 inanna kernel: [33992.896802] FS:  7f63e36f8700() 
GS:8e295f2c() knlGS:
  May 25 01:59:41 inanna kernel: [33992.896826] CS:  0010 DS:  ES:  
CR0: 80050033
  May 25 01:59:41 inanna kernel: [33992.896843] CR2: 7f63d5f00018 CR3: 
000111f6c000 CR4: 001406e0
  May 25 01:59:41 inanna kernel: [33992.896864] Call Trace:
  May 25 01:59:41 inanna kernel: [33992.896875]  migration_entry_wait+0x74/0x80
  May 25 01:59:41 inanna kernel: [33992.896890]  do_swap_page+0x5b3/0x770
  May 25 01:59:41 inanna kernel: [33992.896903]  handle_mm_fault+0x873/0x1360
  May 25 01:59:41 inanna kernel: [33992.896918]  __do_page_fault+0x23e/0x4e0
  May 25 01:59:41 inanna kernel: [33992.896932]  do_page_fault+0x22/0x30
  May 25 01:59:41 inanna kernel: [33992.896945]  page_fault+0x28/0x30
  May 25 01:59:41 inanna kernel: [33992.896956] RIP: 0033:0x55e96320f2b4
  May 

[Kernel-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Daniel van Vugt]

** Also affects: dell-sputnik
   Importance: Undecided
   Status: New

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

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

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

[Kernel-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Esokrates]

@vanvugt: The earphones I tested (Bose Soundtrue Ultra) are Android
ones. I have also tested headphones with no microphone (Sennheiser
HD202).

@kaihengfeng: I will install Ubuntu from scratch in order to test your
kernelsl

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

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

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

[Kernel-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

[Ben]

Just a few updates which may be of use to anyone else having the same
issues...

1). As this issue persists without a truly good solution, it may be a
good idea to simply replace the wifi card with, say, an Atheros one
which works better. You can find them relatively cheaply on ebay.

2). One of the major issues that I was having was that my main Wifi
would crash internally, then whenever I tried to plug in a USB Wifi
adapter they wouldn't work either, leaving me literally without any
method of getting (wireless) internet. I assumed these two issues were
connected, however, further research has led me to believe otherwise.

I tried entirely removing the internal wifi card to see if that would
make a difference on the USB wifi cards, yet still neither of mine
worked. Further looking revealed one or two strange oddities...

phy#1
Interface wlx000f6001cb1f
ifindex 3
wdev 0x10001
addr 00:0f:60:01:cb:1f
type managed
txpower 20.00 dBm

The interface is WAY out of convention. As explained here
(https://superuser.com/questions/1086632/wlan1-showing-as-weird-
characters#1086705), interface names are limited to 16 bytes. My theory
is that when network-manager tries to connect with this interface, it
breaks that limit. The solution suggested in that thread works, append
net.ifnames=0 to the kernel parameters in grub and suddenly all of my
USB wifi adapters work fantastically.

I have a feeling this itself may warrant a separate bug report, I'll do
some looking and see if anyone else is having the same issue/if
someone's already reported it.

TL;DR: If your USB wifi doesn't work and you get weird/long interface
names from "iw dev", use "net.ifnames=0" to fix the interface name and
take back your wifi.

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/rumford__4.8.0-54.57__2017-05-26_10-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Daniel van Vugt]

^^^
Confirmed on an XPS 13 9350 too. And the 'Headphone Mic Boost' workaround 
works. Although like others, I find that concerning since it should in theory 
make the problem worse or make no difference.

Also confirmed the problem persists with:
 * 3-contact earphones (Sony)
 * 4-contact Apple Earpods
 * 4-contact Bose AE2 headphones (Apple-compatible cable)

All of these experience the hiss, but the Bose almost none (much harder
to notice). I think the most interesting test should be to try some
proper Android/Samsung/Nokia wired headphones/earphones  in future.

If it turns out there's nothing wrong with the physical connection then
this sounds like a kernel problem still.

kaihengfeng: I have just tested your kernel on zesty and it made no
difference. The problem remains and the same old amixer workaround is
required.

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

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/fozzie__4.8.0-54.57__2017-05-26_09-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/gonzo__4.8.0-54.57__2017-05-26_09-49-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/pepe__4.8.0-54.57__2017-05-26_09-46-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1636486] Re: External screen flickers (esp. in terminals) with xorg modesetting driver on Intel Broadwell

[Bug Watch Updater]

** Changed in: linux
   Status: Incomplete => 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/1636486

Title:
  External screen flickers (esp. in terminals) with xorg modesetting
  driver on Intel Broadwell

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I'm using a Dell XPS 13 (9343 // i7-5600U broadwell, 3200x1800 panel)
  laptop, directly attached to an external Dell P2715Q 4K (3840x2160
  @60Hz) via DP.

  The 4K external screen is flickering when doing light activity --
  easily reproduced when using an X terminal.

  Steps to reproduce:
  - open side by side Firefox (or Chrome) + a terminal and/or a gvim window on 
the external 4K screen
  - do some light web browsing
  - give focus to the X terminal or gvim
// at this point, display is still perfectly steady
  - press a key to enter a single character
// as soon as the key is pressed, external screen goes black for a few 
seconds. Laptop screen is not affected.
  - Wait for the screen to come back, then continue typing
// screen generally stays ON, but sometimes continues to flicker a few 
times in next minute.

  This happens almost every time I switch to the terminal window and
  start typing.

  OS specs:
  - Ubuntu 16.10 running Unity, modesetting Xorg driver
  - kernel 4.8.0. Issue is still present with 4.9.0rc1.

  The intel driver (cp /usr/share/doc/xserver-xorg-video-intel/xorg.conf
  /etc/X11) doesn't exhibit this issue.

  
  Also reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=97264

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

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

[Kernel-packages] [Bug 1692589] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/ms10-35-mcdivittB0-kernel__4.8.0-54.57__2017-05-26_09-26-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/hainzel__4.8.0-54.57__2017-05-26_09-26-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/gonzo__4.8.0-54.57__2017-05-26_09-25-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/pepe__4.8.0-54.57__2017-05-26_09-23-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/amaura__4.8.0-54.57__2017-05-26_09-18-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/secchi__4.8.0-54.57__2017-05-26_09-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-54.57-generic/fozzie__4.8.0-54.57__2017-05-26_09-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/1692589

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Daniel van Vugt]

** Summary changed:

- XPS 13 9360, Realtek ALC3246, Headphone audio hiss
+ XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

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

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions

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

[Kernel-packages] [Bug 1692589] Re: linux: 4.8.0-54.57 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1692589] Re: linux: 4.8.0-54.57 -proposed tracker

[Kleber Sacilotto de Souza]

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => New

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Andy Whitcroft (apw) => Ubuntu Stable Release Updates Team 
(ubuntu-sru)

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

Title:
  linux: 4.8.0-54.57 -proposed tracker

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

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1692590
  derivatives: 1692592
  kernel-stable-phase-changed:Wednesday, 24. May 2017 10:30 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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