[Kernel-packages] [Bug 1626155] Re: linux-armadaxp: 3.2.0-1674.100 -proposed tracker

[Brad Figg]

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

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

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

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

** Description changed:

  This bug is for tracking the 3.2.0-1674.100 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1626151
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Tuesday, 27. September 2016 12:19 UTC

** Description changed:

  This bug is for tracking the 3.2.0-1674.100 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1626151
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Tuesday, 27. September 2016 12:19 UTC
+ 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-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1626155

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1626151
  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/1626155/+subscriptions

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

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

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

Title:
  [Yakkety] enable EDAC_GHES in kernel config

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  EDAC_GHES is essential for ARMv8.0 Server systems, as it enables
  firmware-first error handling of memory and CPU errors. Due to a lack
  of standard RAS architecture (or machine check architecture
  equivalent) on ARMv8.0 systems, APEI/GHES is the only mechanism
  available for reporting hardware errors (e.g. memory and CPU errors).
  This enables reporting of hardware errors, and also helps enable
  memory fault recovery mechanisms to extend the life of the system by
  offlining pages when recoverable uncorrected errors are encountered.
  Note that other ARM vendors will be going in this direction for
  hardware error handling.

  Currently EDAC_MM_EDAC=m is in Ubuntu, but EDAC_GHES requires this to
  be =y therefore it is not selected.

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

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

[Kernel-packages] [Bug 1628124] [NEW] Yakkety - Enable the arm64 arch on Raspberry Pi

[Tim Gardner]

Public bug reported:

Enable arm64 on the raspi2 branch of Yakkety. No functional change to
armhf.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: Fix Committed

** Affects: linux (Ubuntu Yakkety)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: Fix Committed

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

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

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

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

Title:
  Yakkety - Enable the arm64 arch on Raspberry Pi

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

Bug description:
  Enable arm64 on the raspi2 branch of Yakkety. No functional change to
  armhf.

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

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

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

[Brad Figg]

tests ran:  83, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/ms10-35-mcdivittB0-kernel__4.4.0-40.60__2016-09-27_13-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[bugproxy]

--- Comment From bssrika...@in.ibm.com 2016-09-27 09:02 EDT---
(In reply to comment #18)
> 4.8.0-17-generic is based on 4.8-rc7. The next kernel upload will be based
> on 4.8-rc8 (which has the fix commit)

would it be tomorrows daily build?

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

Title:
  Ubuntu 16.10 KVM: kernel 4.8 can not enable SRIOV for power systems

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

Bug description:
  ---Problem Description---
  Using Ubuntu mainline kernel 
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc6/
  if we try to enable SRIOV in Mellanox CX4 card it will fail. 

  # uname -r
  4.8.0-040800rc6-generic
  root@c158f2u09os:~# echo 7 > /sys/class/net/enP5p1s0f0/device/sriov_numvfs
  -bash: echo: write error: Cannot allocate memory

  logs show:
  Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778118] mlx5_core 0005:01:00.0: 
not enough MMIO resources for SR-IOV
  Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778238] mlx5_core 0005:01:00.0: 
enable sriov failed -12
  Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778604] mlx5_core 0005:01:00.0: 
mlx5_core_sriov_enable failed -12

  ---uname output---
  4.8.0-040800rc6-generic
   
  ---Additional Hardware Info---
  To recreate this you need power system and a Mellanox card that can be used 
for SRIOV.  

   
  Machine Type = P8 
   
  ---Steps to Reproduce---
   with a Mellanox card like CX4 with SRIOV enabled.
  just do this echo to the PF interface in this case was enP5p1s0f0.
  echo 1 > /sys/class/net/enP5p1s0f0/device

  If I take kernel 4.8 and I revert the following patch I can get it to
  work again:

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/arch/powerpc/platforms/powernv
  /pci-ioda.c?id=5958d19a143eb229e9ece20bd4c781ad41cb7d24

   From 5958d19a143eb229e9ece20bd4c781ad41cb7d24 Mon Sep 17 00:00:00 2001
   From: Benjamin Herrenschmidt 
   Date: Fri, 8 Jul 2016 15:55:43 +1000
   Subject: powerpc/pnv/pci: Fix incorrect PE reservation attempt on some 
64-bit BARs

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

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

[Kernel-packages] [Bug 1628112] [NEW] Yakkety - armhf: MFD_TPS65217 and REGULATOR_TPS65217 are boot essential

[Tim Gardner]

Public bug reported:

The MFD65217 is a multi-function chip that, among other things,
regulates voltage in the TI AM335x chip (the SOC used in the Beaglebone
board), and as such, it's a boot essential there.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: Fix Committed

** Affects: linux (Ubuntu Yakkety)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: Fix Committed

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

** Description changed:

- The MFD65217 is a multi-function chip that, among other things, regulates
- voltage in the TI AM335x chip (the SOC used in the Beaglebone board), and as
- such, it's a boot essential there.
+ The MFD65217 is a multi-function chip that, among other things,
+ regulates voltage in the TI AM335x chip (the SOC used in the Beaglebone
+ board), and as such, it's a boot essential there.

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

Title:
  Yakkety - armhf: MFD_TPS65217 and REGULATOR_TPS65217 are boot
  essential

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

Bug description:
  The MFD65217 is a multi-function chip that, among other things,
  regulates voltage in the TI AM335x chip (the SOC used in the
  Beaglebone board), and as such, it's a boot essential there.

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

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

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

[bugproxy]

--- Comment From gmgay...@us.ibm.com 2016-09-27 09:42 EDT---
Exposing private comment from Pravithra (tester).

Hi,

Tested with today's build, VDVD installation on LPAR works fine.

root@ubuntu:~# uname -a
Linux ubuntu 4.8.0-17-generic #19-Ubuntu SMP Sun Sep 25 06:35:40 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

Thanks,
Pavithra

--- Comment From gmgay...@us.ibm.com 2016-09-27 09:44 EDT---
Hi Pavrithra or Pooja,
Are you satisfied that we can close this bug?
Thanks, Gary

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

Title:
  Ubuntu16.10 PowerVM VDVD installation fails on LPAR

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Pooja B. Suryanarayana  - 2016-09-22 
11:07:49 ==
  ---Problem Description---
  Ubuntu16.10 PowerVM VDVD installation on LPAR fails with below error message.

  ---Machine Type---
  PowerVM LPAR

  ---Installation type---
  VDVD

  ---Steps to reproduce---
  1.Copy the iso to VIOS
  2.create virtualdvd
  mkvopt -name poo-ubu1610 -file /home/padmin/yakkety-server-ppc64el.iso -ro
  3.Attach the vdvd to the vtopt
  loadopt -f -release -disk poo-ubu1610 -vtd vtopt18
  4.Select the attached disk while installing and continue installation.
  5.Installation fails with below error.

  
 ? [!!] Detect and mount CD-ROM ??
 ?   ?
 ? Your installation CD-ROM couldn't be mounted. This probably means ?
 ? that the CD-ROM was not in the drive. If so you can insert it and try ?
 ? again.?
 ?   ?
 ? Retry mounting the CD-ROM??
 ?   ?
 ?  ?
 ?   ?
 ?



  
   moves;  selects;  activates buttons



  
   ??? [!!] Detect and mount CD-ROM 
   ?   ?
   ? Installation step failed  ?
   ? An installation step failed. You can try to run the failing item  ?
   ? again from the menu, or skip it and choose something else. The?
   ? failing step is: Detect and mount CD-ROM  ?
   ?   ?
   ? ?
   ?   ?
   ?


  
   moves;  selects;  activates buttons


  And Installer this doesnt list the partitioning disk optiona as well

?? [?] Ubuntu installer main menu ??
?  ?
? Choose the next step in the install process: ?
?  ?
?  Choose language ?
?  Access software for a blind person using a braille display  ?
?  Configure the keyboard  ?
?  Detect and mount CD-ROM ?
?  Load installer components from CD   ?
?  Change debconf priority ?
?  Check the CD-ROM(s) integrity   ?
?  Save debug logs ?
?  Execute a shell ?
?  Abort the installation  ?
?  ?



   moves;  selects;  activates buttons

  == Comment: #3 - Pooja B. Suryanarayana  -
  2016-09-23 01:49:04 ==

  (In reply to comment #2)
  > Hi Pooja,
  > Our first step is narrow down whether this is a pVM issue or an Ubuntu 16.10
  > install issue.
  > 
  > --- For pVM I will ask you to perform some extra steps and show the output
  > from the commands.  Per your recreate steps:
  > 
  > ---Steps to reproduce---
  > 1.Copy the iso to VIOS
  > 
  > New 1.5  show the output of ls -al   we want to see if size
  > and permissions are 

[Kernel-packages] [Bug 1628111] [NEW] [Yakkety] enable EDAC_GHES in kernel config

[Manoj Iyer]

Public bug reported:

EDAC_GHES is essential for ARMv8.0 Server systems, as it enables
firmware-first error handling of memory and CPU errors. Due to a lack of
standard RAS architecture (or machine check architecture equivalent) on
ARMv8.0 systems, APEI/GHES is the only mechanism available for reporting
hardware errors (e.g. memory and CPU errors). This enables reporting of
hardware errors, and also helps enable memory fault recovery mechanisms
to extend the life of the system by offlining pages when recoverable
uncorrected errors are encountered. Note that other ARM vendors will be
going in this direction for hardware error handling.

Currently EDAC_MM_EDAC=m is in Ubuntu, but EDAC_GHES requires this to be
=y therefore it is not selected.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Manoj Iyer (manjo)
 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/1628111

Title:
  [Yakkety] enable EDAC_GHES in kernel config

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  EDAC_GHES is essential for ARMv8.0 Server systems, as it enables
  firmware-first error handling of memory and CPU errors. Due to a lack
  of standard RAS architecture (or machine check architecture
  equivalent) on ARMv8.0 systems, APEI/GHES is the only mechanism
  available for reporting hardware errors (e.g. memory and CPU errors).
  This enables reporting of hardware errors, and also helps enable
  memory fault recovery mechanisms to extend the life of the system by
  offlining pages when recoverable uncorrected errors are encountered.
  Note that other ARM vendors will be going in this direction for
  hardware error handling.

  Currently EDAC_MM_EDAC=m is in Ubuntu, but EDAC_GHES requires this to
  be =y therefore it is not selected.

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

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

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

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

Title:
  Yakkety - armhf: MFD_TPS65217 and REGULATOR_TPS65217 are boot
  essential

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

Bug description:
  The MFD65217 is a multi-function chip that, among other things,
  regulates voltage in the TI AM335x chip (the SOC used in the
  Beaglebone board), and as such, it's a boot essential there.

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

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

[Kernel-packages] [Bug 1628112] Re: Yakkety - armhf: MFD_TPS65217 and REGULATOR_TPS65217 are boot essential

[Tim Gardner]

UBUNTU: [Config] armhf: MFD_TPS65217=y && REGULATOR_TPS65217=y

** Changed in: linux (Ubuntu Yakkety)
   Status: Incomplete => Fix Committed

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

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

Title:
  Yakkety - armhf: MFD_TPS65217 and REGULATOR_TPS65217 are boot
  essential

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

Bug description:
  The MFD65217 is a multi-function chip that, among other things,
  regulates voltage in the TI AM335x chip (the SOC used in the
  Beaglebone board), and as such, it's a boot essential there.

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

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

[Kernel-packages] [Bug 1626604] onza (amd64) - tests ran: 65, failed: 24

[Brad Figg]

tests ran:  65, failed: 24;
  
http://kernel.ubuntu.com/testing/3.13.0-97.144/onza__3.13.0-97.144__2016-09-27_05-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/1626604

Title:
  linux: 3.13.0-97.144 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-97.144 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 --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

[Mons ter Wade]

BQ Aquaris E5
Volkswagen Phaeton 2011 (VW Navigation System RNS810)
OTA13

After the OTA13 stable update I'm now able to pair my phone with the in
car bluetooth system for the first time. However the pairing process was
a bit of a hassle until it worked. I was not able to detect why pairing
suddenly worked after 5 unsuccessful tries. Maybe a timing issue,
because I have to enter a 16 digit code and not a 4 digit code.

After pairing I can access contacts, start calls etc. The phone also
reconnects perfectly after entering the car again. Everything seems to
work...

BUT the bluetooth audio is not routed to my car speakers/microphone. I
can browse my contacts, start a call and answer calls, but I can't hear
anyting and my opposite can't hear me.

For me OTA13 was an improvement (pairing now works), but I still can't
make phone calls in the car.

My Ubuntu Phone would be perfect, if hands-free speaking would work.
Please keep up the good work and release a fix as soon as possible!

If I can help, let me know ...

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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

[Kernel-packages] [Bug 1624961] Re: Ubuntu 16.10 KVM: kernel 4.8 can not enable SRIOV for power systems

[Tim Gardner]

It'll get uploaded by Thursday Sept 29 at the latest.

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

Title:
  Ubuntu 16.10 KVM: kernel 4.8 can not enable SRIOV for power systems

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

Bug description:
  ---Problem Description---
  Using Ubuntu mainline kernel 
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc6/
  if we try to enable SRIOV in Mellanox CX4 card it will fail. 

  # uname -r
  4.8.0-040800rc6-generic
  root@c158f2u09os:~# echo 7 > /sys/class/net/enP5p1s0f0/device/sriov_numvfs
  -bash: echo: write error: Cannot allocate memory

  logs show:
  Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778118] mlx5_core 0005:01:00.0: 
not enough MMIO resources for SR-IOV
  Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778238] mlx5_core 0005:01:00.0: 
enable sriov failed -12
  Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778604] mlx5_core 0005:01:00.0: 
mlx5_core_sriov_enable failed -12

  ---uname output---
  4.8.0-040800rc6-generic
   
  ---Additional Hardware Info---
  To recreate this you need power system and a Mellanox card that can be used 
for SRIOV.  

   
  Machine Type = P8 
   
  ---Steps to Reproduce---
   with a Mellanox card like CX4 with SRIOV enabled.
  just do this echo to the PF interface in this case was enP5p1s0f0.
  echo 1 > /sys/class/net/enP5p1s0f0/device

  If I take kernel 4.8 and I revert the following patch I can get it to
  work again:

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/arch/powerpc/platforms/powernv
  /pci-ioda.c?id=5958d19a143eb229e9ece20bd4c781ad41cb7d24

   From 5958d19a143eb229e9ece20bd4c781ad41cb7d24 Mon Sep 17 00:00:00 2001
   From: Benjamin Herrenschmidt 
   Date: Fri, 8 Jul 2016 15:55:43 +1000
   Subject: powerpc/pnv/pci: Fix incorrect PE reservation attempt on some 
64-bit BARs

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

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

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

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/modoc__4.4.0-40.60__2016-09-27_13-13-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1628284] [NEW] yakkety: daily powerpc server ISO fails to find cdrom during install in a VM

[Nish Aravamudan]

Public bug reported:

xenial daily ISO successfully installs using the same method on the same
system, but yakkety reports:

Sep 27 21:13:14 cdrom-detect: Searching for Ubuntu installation media...
Sep 27 21:13:18 cdrom-detect: Devices: ''
Sep 27 21:13:23 cdrom-detect: Devices: ''
Sep 27 21:13:24 kernel: [  154.649279] random: crng init done
Sep 27 21:13:28 cdrom-detect: Devices: ''
Sep 27 21:13:33 cdrom-detect: Devices: ''
Sep 27 21:13:38 cdrom-detect: Devices: ''
Sep 27 21:13:43 cdrom-detect: Devices: ''
Sep 27 21:13:48 cdrom-detect: Devices: ''
Sep 27 21:13:53 cdrom-detect: Devices: ''
Sep 27 21:13:58 cdrom-detect: Devices: ''
Sep 27 21:14:06 cdrom-detect: CDROM-detect failed; unmounting CD just to be sure
Sep 27 21:14:06 main-menu[267]: WARNING **: Configuring 'cdrom-detect' failed 
with error code 1
Sep 27 21:14:06 main-menu[267]: WARNING **: Menu item 'cdrom-detect' failed.

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

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

Title:
  yakkety: daily powerpc server ISO fails to find cdrom during install
  in a VM

Status in linux package in Ubuntu:
  New

Bug description:
  xenial daily ISO successfully installs using the same method on the
  same system, but yakkety reports:

  Sep 27 21:13:14 cdrom-detect: Searching for Ubuntu installation media...
  Sep 27 21:13:18 cdrom-detect: Devices: ''
  Sep 27 21:13:23 cdrom-detect: Devices: ''
  Sep 27 21:13:24 kernel: [  154.649279] random: crng init done
  Sep 27 21:13:28 cdrom-detect: Devices: ''
  Sep 27 21:13:33 cdrom-detect: Devices: ''
  Sep 27 21:13:38 cdrom-detect: Devices: ''
  Sep 27 21:13:43 cdrom-detect: Devices: ''
  Sep 27 21:13:48 cdrom-detect: Devices: ''
  Sep 27 21:13:53 cdrom-detect: Devices: ''
  Sep 27 21:13:58 cdrom-detect: Devices: ''
  Sep 27 21:14:06 cdrom-detect: CDROM-detect failed; unmounting CD just to be 
sure
  Sep 27 21:14:06 main-menu[267]: WARNING **: Configuring 'cdrom-detect' failed 
with error code 1
  Sep 27 21:14:06 main-menu[267]: WARNING **: Menu item 'cdrom-detect' failed.

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

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

[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

[Richard Laager]

I just talked to Brian Behlendorf (since I'm sitting next to him at the
OpenZFS Developer Summit). He doesn't have strong feelings either way,
but is concerned about breaking people who are already relying on those
names.

My thought is we should just fix it in Debian/Ubuntu regardless of
whether it is fixed upstream.

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

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

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

[Kernel-packages] [Bug 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Joseph Salisbury]

I built a Yakkety test kernel with a revert of commit
2deb4be28077638591fe5fc593b7f8aabc140f42.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1627198

Can you see if this kernel resolves this bug?

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

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

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

Title:
  yakkety: daily powerpc server ISO fails to find cdrom during install
  in a VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  xenial daily ISO successfully installs using the same method on the
  same system, but yakkety reports:

  Sep 27 21:13:14 cdrom-detect: Searching for Ubuntu installation media...
  Sep 27 21:13:18 cdrom-detect: Devices: ''
  Sep 27 21:13:23 cdrom-detect: Devices: ''
  Sep 27 21:13:24 kernel: [  154.649279] random: crng init done
  Sep 27 21:13:28 cdrom-detect: Devices: ''
  Sep 27 21:13:33 cdrom-detect: Devices: ''
  Sep 27 21:13:38 cdrom-detect: Devices: ''
  Sep 27 21:13:43 cdrom-detect: Devices: ''
  Sep 27 21:13:48 cdrom-detect: Devices: ''
  Sep 27 21:13:53 cdrom-detect: Devices: ''
  Sep 27 21:13:58 cdrom-detect: Devices: ''
  Sep 27 21:14:06 cdrom-detect: CDROM-detect failed; unmounting CD just to be 
sure
  Sep 27 21:14:06 main-menu[267]: WARNING **: Configuring 'cdrom-detect' failed 
with error code 1
  Sep 27 21:14:06 main-menu[267]: WARNING **: Menu item 'cdrom-detect' failed.

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

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

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

[Brad Figg]

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/onza__4.4.0-40.60__2016-09-27_21-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

-- 
Mailing list: https://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 1627198] Re: 4.8.0 kernels do not complete boot process on VM

[Barry Warsaw]

On Sep 27, 2016, at 09:15 PM, Joseph Salisbury wrote:

>Can you see if this kernel resolves this bug?

Almost!  As mentioned in IRC, it boots but login doesn't give me a
desktop.

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

Title:
  4.8.0 kernels do not complete boot process on VM

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

Bug description:
  On my native amd64 box, 4.8.0-15 works just fine, but on my VMWare
  Fusion 8.5 system, none of the 4.8.0 kernels complete the boot
  process.  I tried 4.8.0-15 from yakkety and 4.8.0-16 from yakkety-
  proposed.

  Currently  I am seeing the last message in my console at boot up as:

  [ OK ] Started Bluetooth service

  and then... it just sits there.

  Through the use of snapshots, restores, and package bisects, I've
  definitively narrowed it to linux-generic linux-image-generic and
  linux-headers-generic.

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

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

[Kernel-packages] [Bug 1626194] Re: Seccomp actions are not audited in the 4.8 kernel

[Tyler Hicks]

It looks like this was first fixed in 4.8.0-15.16 and I've verified that
it is fixed in 4.8.0-17.19.

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

Title:
  Seccomp actions are not audited in the 4.8 kernel

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The following patch, released in v4.5, changed the auditing behavior of
  seccomp:

commit 96368701e1c89057bbf39222e965161c68a85b4b
Author: Paul Moore 
Date:   Wed Jan 13 09:18:55 2016 -0500

audit: force seccomp event logging to honor the audit_enabled
  flag

  In Ubuntu, where the audit subsystem is not enabled by default, it means that
  seccomp actions are not logged unless the user has installed auditd or added
  the audit=1 kernel command line parameter.

  This impacts snap confinement in Yakkety because seccomp actions are no longer
  audited which means that snap authors cannot easily know which restricted
  system calls they're using.

  To test, build the attached program:

   $ sudo apt-get install libseccomp-dev
   ...
   $ gcc -o test test.c -lseccomp

  Run the program. It should be killed when calling open().

   $ ./test
   Bad system call

  Now look in the syslog. In 4.4 kernels, there will be an audit record
  showing that the test program was killed because it called open()
  (syscall 2):

[15.055437] audit: type=1326 audit(1474477027.391:261):
  auid=4294967295 uid=1000 gid=1000 ses=4294967295 pid=12546 comm="test"
  exe="/tmp/seccomp-log/test" sig=31 arch=c03e syscall=2 compat=0
  ip=0x7fde77e45790 code=0x0

  This audit record is not present in 4.8 kernels.

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

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

[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

[Eric Desrochers]

rlaager, yes, this is reasonable.

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

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

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

[Kernel-packages] [Bug 1625794] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 4, failed: 1

[Brad Figg]

tests ran:   4, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/ms10-34-mcdivittB0-kernel__3.19.0-70.78~14.04.1__2016-09-27_10-58-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+subscriptions

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

[Kernel-packages] [Bug 1447909] Re: external mic not detected on machines with alc256 codec

[MIFAS]

sudo: hdajacksensetest: command not found

But I've installed hdajackretask

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

Title:
  external mic not detected on machines with alc256 codec

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  This bug is used for tracking, please do not triage.

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

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

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

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/ms10-35-mcdivittB0-kernel__4.4.0-40.60__2016-09-27_11-50-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1626112] Re: Permission denied in CIFS with kernel 4.4.0-38

[Seth Forshee]

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

Title:
  Permission denied in CIFS with kernel 4.4.0-38

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

Bug description:
  SRU Justification

  Imapct: A regression from upstream stable causes problems with direct
  mounting of DFS submounts in 4.4.0-38.57 and in yakkety 4.8 kernels,
  and memory leaks as well.

  Fix: For xenial backport all patches which are fixes for the stable
  patch. Yakkety already has all the fixes except for the last one.

  Regression Potential: The patches are all pretty straightforward, so
  regression risk is low, and they fix existing regressions.

  ---

  Hello,

  I'm experiencing problem accessing a remote CIFS mounted with kernel
  4.4.0.38.

  The mount succeed but I can't list the content.

  ll /home/nico/mnt/carpetes
  ls: cannot open directory '/home/nico/mnt/carpetes': Permission denied

  The mount command is:
  sudo mount -t cifs //windowsdomain.ad/carpetes/documents 
/home/nico/mnt/carpetes -o 
user=nico,password=mypassword,domain=windowsdomain.ad,sec=ntlm,file_mode=0777,dir_mode=0777

  I can change directory to the mounted CIFS but can't list the content.
  Even with root user the error message is:

  ll /home/nico/mnt/carpetes
  ls: reading directory '/home/nico/mnt/carpetes': Object is remote
  total 0

  Thank you very much for helping.

  Best regards,
  Nico
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nico   2741 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18
  HibernationDevice: RESUME=UUID=62f559ea-4eb1-4b4f-be21-d6a8ae558fe0
  InstallationDate: Installed on 2016-09-13 (8 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=d2e01c93-3645-4d39-8d01-617b7416b761 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-38.57+lp1612135v201609211623-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  RfKill:

  Tags:  sarah
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nico   2748 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18
  HibernationDevice: RESUME=UUID=62f559ea-4eb1-4b4f-be21-d6a8ae558fe0
  InstallationDate: Installed on 2016-09-13 (9 days ago)
  InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628
  IwConfig:
   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=d2e01c93-3645-4d39-8d01-617b7416b761 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157.3
  RfKill:

  Tags:  sarah
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf
  _MarkForUpload: 

[Kernel-packages] [Bug 1624961] Re: Ubuntu 16.10 KVM: kernel 4.8 can not enable SRIOV for power systems

[Tim Gardner]

4.8.0-17-generic is based on 4.8-rc7. The next kernel upload will be
based on 4.8-rc8 (which has the fix commit)

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

Title:
  Ubuntu 16.10 KVM: kernel 4.8 can not enable SRIOV for power systems

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

Bug description:
  ---Problem Description---
  Using Ubuntu mainline kernel 
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc6/
  if we try to enable SRIOV in Mellanox CX4 card it will fail. 

  # uname -r
  4.8.0-040800rc6-generic
  root@c158f2u09os:~# echo 7 > /sys/class/net/enP5p1s0f0/device/sriov_numvfs
  -bash: echo: write error: Cannot allocate memory

  logs show:
  Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778118] mlx5_core 0005:01:00.0: 
not enough MMIO resources for SR-IOV
  Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778238] mlx5_core 0005:01:00.0: 
enable sriov failed -12
  Sep 16 00:52:46 c158f2u09os kernel: [ 1419.778604] mlx5_core 0005:01:00.0: 
mlx5_core_sriov_enable failed -12

  ---uname output---
  4.8.0-040800rc6-generic
   
  ---Additional Hardware Info---
  To recreate this you need power system and a Mellanox card that can be used 
for SRIOV.  

   
  Machine Type = P8 
   
  ---Steps to Reproduce---
   with a Mellanox card like CX4 with SRIOV enabled.
  just do this echo to the PF interface in this case was enP5p1s0f0.
  echo 1 > /sys/class/net/enP5p1s0f0/device

  If I take kernel 4.8 and I revert the following patch I can get it to
  work again:

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/arch/powerpc/platforms/powernv
  /pci-ioda.c?id=5958d19a143eb229e9ece20bd4c781ad41cb7d24

   From 5958d19a143eb229e9ece20bd4c781ad41cb7d24 Mon Sep 17 00:00:00 2001
   From: Benjamin Herrenschmidt 
   Date: Fri, 8 Jul 2016 15:55:43 +1000
   Subject: powerpc/pnv/pci: Fix incorrect PE reservation attempt on some 
64-bit BARs

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

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

[Kernel-packages] [Bug 1625794] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 136, failed: 0

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/ms10-34-mcdivittB0-kernel__3.19.0-70.78~14.04.1__2016-09-27_12-07-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+subscriptions

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

[Kernel-packages] [Bug 1626604] onibi (amd64) - tests ran: 65, failed: 26

[Brad Figg]

tests ran:  65, failed: 26;
  
http://kernel.ubuntu.com/testing/3.13.0-97.144/onibi__3.13.0-97.144__2016-09-27_08-38-00/results-index.html

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

Title:
  linux: 3.13.0-97.144 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-97.144 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 --
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1618550] Re: [HP 15-r085no Notebook PC (ENERGY STAR)] Suspend/resume freezes

[Christopher M. Penalver]

Arto Makkonen, could you please provide the missing information from
https://wiki.ubuntu.com/DebuggingKernelSuspend ?

** Tags removed: kernel-bug-exists-upstream-4.8-rc4
** Tags added: kernel-bug-exists-upstream-4.8-rc8

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

Title:
  [HP 15-r085no Notebook PC (ENERGY STAR)] Suspend/resume freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My HP notebook won't wake from suspend with 16.04 LTS, waited for the
  latest 4.4.0-36 kernel update before reporting this bug. Computer goes
  to suspend, but attempts to wake it up just start the fan (and HDD)
  while the display remains black.

  Also tested this with the mainline upstream kernel
  4.8.0-040800rc3-generic. With this version there was different
  behaviour but still a bug: the display woke up but Ubuntu was very
  unstable, did not connect to Wifi and the GUI froze very soon after
  resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arto   3449 F pulseaudio
   /dev/snd/controlC1:  arto   3449 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 30 19:42:38 2016
  HibernationDevice: RESUME=UUID=8b70a4a1-df29-4f51-9b65-c2a17b4361a2
  InstallationDate: Installed on 2015-09-18 (347 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=c1e1c032-887a-44c8-b4d2-0850b57082e8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-15 (15 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2212
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097610405F0620180
  dmi.sys.vendor: Hewlett-Packard

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

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

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

[bugproxy]

--- Comment From pavsu...@in.ibm.com 2016-09-27 05:49 EDT---
I have now tried with the makedumpfile binary provided in the Ubuntu 16.10 OS.

root@powerkvm3-lp1:~# cd /var/crash/
root@powerkvm3-lp1:/var/crash# ls
201609270334  kexec_cmd
root@powerkvm3-lp1:/var/crash# cd 201609270334/
root@powerkvm3-lp1:/var/crash/201609270334# ls
vmcore.201609270334
root@powerkvm3-lp1:/var/crash/201609270334# which makedumpfile
/usr/bin/makedumpfile

root@powerkvm3-lp1:/var/crash/201609270334# dpkg -S /usr/bin/makedumpfile
makedumpfile: /usr/bin/makedumpfile
root@powerkvm3-lp1:/var/crash/201609270334# dpkg --list | grep makedumpfile
ii  makedumpfile1:1.6.0-2   
 ppc64el  VMcore extraction tool

Now I tried to use the same to extract the vmcore generated earlier.

root@powerkvm3-lp1:/var/crash/201609270334# ls -l vmcore.201609270334
-r 1 root root 270746714112 Sep 27 03:36 vmcore.201609270334
root@powerkvm3-lp1:/var/crash/201609270334# makedumpfile -l -d 31 
vmcore.201609270334 dump1
The kernel version is not supported.
The makedumpfile operation may be incomplete.
get_mem_map: Can't distinguish the memory type.

makedumpfile Failed.

But its still failing with the makedumpfile provided by latest Ubuntu
16.10 OS.

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

Title:
  Machine crashes to (initramfs) after Triggering a crash - missing
  crc32c module

Status in linux package in Ubuntu:
  Triaged
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #6 - PAVAMAN SUBRAMANIYAM - 2016-09-23 01:12:09 ==
  I have installed the latest Ubuntu 16.10 4.8.0-15-generic kernel on the 
machine.

  root@powerkvm3-lp1:~# uname -a
  Linux powerkvm3-lp1 4.8.0-15-generic #16-Ubuntu SMP Wed Sep 21 20:45:56 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
  root@powerkvm3-lp1:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.10 (Yakkety Yak)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.10"
  VERSION_ID="16.10"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="http://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=yakkety
  UBUNTU_CODENAME=yakkety

  Then again triggered the crash on the machine using sysrq-trigger.

  root@powerkvm3-lp1:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-15-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-15-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=85301ac1-2c85-426a-a9f2-fa87254fc9a7 ro quiet splash 
irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@powerkvm3-lp1:~# cat /proc/sys/kernel/sysrq
  176
  root@powerkvm3-lp1:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1
  root@powerkvm3-lp1:~# cat /proc/sys/kernel/sysrq
  1

  But again the machine went to (initramfs) prompt since it could not
  load rootfs.

  Ubuntu Yakkety Yak (development branch) powerkvm3-lp1 hvc0

  powerkvm3-lp1 login: [  655.378861] sysrq: SysRq : Trigger a crash
  [  655.378969] Unable to handle kernel paging request for data at address 
0x
  [  655.379047] Faulting instruction address: 0xc05c28f4
  [  655.379112] Oops: Kernel access of bad area, sig: 11 [#1]
  [  655.379163] SMP NR_CPUS=2048 NUMA PowerNV
  [  655.379216] Modules linked in: btrfs ipmi_msghandler raid6_pq xor sg 
powernv_rng rng_core ghash_generic gf128mul powernv_op_panel vmx_crypto 
ip_tables x_tables autofs4 crc32c_generic ext4 crc16 jbd2 fscrypto mbcache 
sr_mod cdrom sd_mod crc32c_vpmsum xhci_pci xhci_hcd lpfc usbcore tg3 be2net ptp 
usb_common scsi_transport_fc pps_core ipr libphy
  [  655.379757] CPU: 25 PID: 6866 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  655.379832] task: c00fea14af00 task.stack: c00fed1c8000
  [  655.379896] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  655.379971] REGS: c00fed1cb990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  655.380045] MSR: 90009033   CR: 28242422  
XER: 2000
  [  655.380235] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c00fed1cbc10 c0f67b00 0063
  GPR04: c00ff964a9b8 c00ff965f7e0 c03fff80 00029610
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c177e100  2200
  GPR16: 10170dc8 010024567738 

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

[Brad Figg]

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/modoc__4.8.0-18.20__2016-09-27_09-30-00/results-index.html

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

Title:
  linux: 4.8.0-18.20 -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 Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-18.20 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-changed:Tuesday, 27. September 2016 08:45 UTC
  kernel-phase:Packaging

  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging

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

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

[Kernel-packages] [Bug 1627074] s2lp6g001 (s390x.zKVM) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/s2lp6g001__4.4.0-40.60__2016-09-27_10-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1627074] s2lp6g001 (s390x.zKVM) - tests ran: 83, failed: 0

[Brad Figg]

tests ran:  83, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/s2lp6g001__4.4.0-40.60__2016-09-27_09-36-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1584456] Re: apparmor denial using ptmx char device

[Zygmunt Krynicki]

Yann could you please verify that this bug is fixed by the package in
xenial-proposed?

You can find more information about the process at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification

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

Title:
  apparmor denial using ptmx char device

Status in Snappy Launcher:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in snap-confine package in Ubuntu:
  Fix Released
Status in snap-confine source package in Xenial:
  In Progress

Bug description:
  [Impact]

  snap-confine would refuse to work on an older kernel running on an
  Nvidia Tegra X1 board. This was traced to a bug in older version of
  apparmor there that required directory-like syntax for /dev/pts/ptmx
  (with a trailing slash).

  This bug is fixed by adding an apparmor rule, identical to the normal
  rule, with an extra slash. Older kernels will use the new rule while
  current kernels will just ignore it.

  [Test Case]

  On an Nvidia Tegra X1 board, running 3.10.96 snap-confine should no
  longer fail to start. On Ubuntu Xenial (all architectures) there
  should be no perceived change.

  Snap-confine is carefully tested with a battery of spread tests that
  can be found here: https://github.com/snapcore/snap-
  confine/blob/master/spread-tests/

  The test cases are ran automatically for each pull request and for
  each final release.

  All those tests were executed successfully for this release. As a
  simple test case consider running any snap (any at all, including
  hello-world).

  [Regression Potential]

   * Regression potential is minimal as the fix simply adds another
  apparmor rule that grants additional permissions that are only picked
  up by old buggy kernels.

  * The fix was tested on Ubuntu via spread.

  [Other Info]

  * This bug is a part of a major SRU that brings snap-confine in Ubuntu
  16.04 in line with the current upstream release 1.0.41.

  * This bug was included in an earlier SRU and is now fixed in Ubuntu.
  I am updating the template here to ensure that the process is fully
  documented from 1.0.38 all the way up to the current upstream release
  1.0.41.

  * snap-confine is technically an integral part of snapd which has an
  SRU exception and is allowed to introduce new features and take
  advantage of accelerated procedure. For more information see
  https://wiki.ubuntu.com/SnapdUpdates

  == # Pre-SRU bug description follows # ==

  - Finding issues running snaps (hello-world).
  - Same issue even installing with --devmode. Even running the snap binary as 
root
  - Using a custom kernel, this is on an Nvidia Tegra X1 custom board.

  =

  ubuntu@localhost:~$ hello-world.echo plop
  unable to mount '/dev/pts/ptmx'->'/dev/ptmx'. errmsg: Permission denied
  ubuntu@localhost:~$ sudo hello-world.echo plop
  unable to mount '/dev/pts/ptmx'->'/dev/ptmx'. errmsg: Permission denied

  dmesg shows:
  =

  [  302.838046] type=1400 audit(1455208371.989:16): apparmor="DENIED"
  operation="mount" info="failed mntpnt match" error=-13 parent=911
  profile="/usr/bin/ubuntu-core-launcher" name="/dev/ptmx/" pid=912
  comm="ubuntu-core-lau" srcname="/dev/pts/ptmx/" flags="rw, bind"
  [  308.080449] type=1400 audit(1455208377.229:17): apparmor="DENIED"
  operation="mount" info="failed mntpnt match" error=-13 parent=914
  profile="/usr/bin/ubuntu-core-launcher" name="/dev/ptmx/" pid=915
  comm="ubuntu-core-lau" srcname="/dev/pts/ptmx/" flags="rw, bind"

  This is with the "hello-world" snap installed with "snap install"

  Output of an ls over the device file:
  =

  ubuntu@localhost:~$ ls -lR /dev/ptmx /dev/pts
  crw-rw-rw- 1 root tty  5, 2 Feb 11 16:28 /dev/ptmx

  /dev/pts:
  total 0
  c- 1 root root 5, 2 Jan  1  1970 ptmx

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-confine/+bug/1584456/+subscriptions

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

[Kernel-packages] [Bug 1626269] Re: Ubuntu 16.10: kdump is not working in 4.8 kernel.

[bugproxy]

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

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

Title:
  Ubuntu 16.10: kdump is not working in 4.8 kernel.

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Trusty:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Yakkety:
  Confirmed

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-09-21 00:50:22 ==
  ---Problem Description---

  Ubuntu 16.10: kdump is not working in 4.8 kernel.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M"

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show
  6) echo "c" > /proc/sysrq-trigger

  Logs
  

  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  
  root@ubuntu:/home/ubuntu# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.8.0-11-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-11-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinux-4.8.0-11-generic 
root=UUID=7ea3831b-f4c3-4f69-8f77-79aefcda70e3 ro splash quiet irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
  root@ubuntu:/home/ubuntu# cd
  root@ubuntu:~# echo "c" > /proc/sysrq-trigger
  [   50.733424] sysrq: SysRq : Trigger a crash
  [   50.733437] Unable to handle kernel paging request for data at address 
0x
  [   50.733441] Faulting instruction address: 0xc05af3f4
  [   50.733444] Oops: Kernel access of bad area, sig: 11 [#1]
  [   50.733446] SMP NR_CPUS=2048 NUMA pSeries
  [   50.733450] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag pseries_rng sg 
rng_core binfmt_misc ghash_generic gf128mul vmx_crypto ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache sr_mod cdrom sd_mod bnx2x ibmvscsi 
ibmveth scsi_transport_srp ptp pps_core mdio libcrc32c crc32c_generic 
crc32c_vpmsum
  [   50.733477] CPU: 2 PID: 1517 Comm: bash Not tainted 4.8.0-11-generic 
#12-Ubuntu
  [   50.733480] task: c004f7906880 task.stack: c004f7898000
  [   50.733482] NIP: c05af3f4 LR: c05b04d8 CTR: 
c05af3c0
  [   50.733485] REGS: c004f789b990 TRAP: 0300   Not tainted  
(4.8.0-11-generic)
  [   50.733488] MSR: 80009033   CR: 28242422  
XER: 0001
  [   50.733496] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1 
  GPR00: c05b04d8 c004f789bc10 c0f46700 0063 
  GPR04: c005ef78a9b8 c005ef79f7d8 c0063fe82300 5970 
  GPR08: 0007 0001  0001 
  GPR12: c05af3c0 c7b31200  2200 
  GPR16: 10170dc8 0100111c0538 10140f58 100c7570 
  GPR20:  1017dd58 10153618 1017b608 
  GPR24: 310b9624 0001 c0e9fd40 0004 
  GPR28: c0ea0100 0063 c0e528e8  
  [   50.733536] NIP [c05af3f4] sysrq_handle_crash+0x34/0x50
  [   50.733539] LR [c05b04d8] __handle_sysrq+0xe8/0x280
  [   50.733541] Call Trace:
  [   50.733544] [c004f789bc10] [c09ff9e8] 0xc09ff9e8 
(unreliable)
  [   50.733548] [c004f789bc30] [c05b04d8] __handle_sysrq+0xe8/0x280
  [   50.733552] [c004f789bcd0] [c05b0c88] 
write_sysrq_trigger+0x78/0xa0
  [   50.733556] [c004f789bd00] [c03a9a90] proc_reg_write+0xb0/0x110
  [   50.733560] [c004f789bd50] [c030c27c] __vfs_write+0x6c/0xe0
  [   50.733564] [c004f789bd90] [c030d784] vfs_write+0xd4/0x240
  [   50.733567] [c004f789bde0] [c030f49c] SyS_write+0x6c/0x110
  [   50.733571] [c004f789be30] [c00095e0] system_call+0x38/0x108
  [   50.733574] Instruction dump:
  [   50.733576] 38427340 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949cde0 
  [   50.733582] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6 
  [   50.733589] ---[ end trace 

[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

[bhartendu]

Hi, I am facing the same issues.

In my case gnome-shell and gnome-daemon are taking most of the memory.
At one point gnome-shell was using 5.6 GB of RAM.

** Attachment added: "Screenshot from 2016-09-27 14-55-34.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+attachment/4749216/+files/Screenshot%20from%202016-09-27%2014-55-34.png

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

Title:
  Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

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

Bug description:
  Ubuntu 16.04 64bit ISO number 20160420.1
  unity version 7.4.0+16.04.20160415-0ubuntu1
  Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10
  Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB
  Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 21 01:44:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1920x1080+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 
'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 
'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 
'unityshell']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PLUS
  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.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 21 01:37:17 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Kernel-packages] [Bug 1627074] s2lp6g001 (s390x.zKVM) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/s2lp6g001__4.4.0-40.60__2016-09-27_10-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1461738] Re: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms

[Michael Kiermaier]

Christopher M. Penalver (penalvch): ok, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628061

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

Title:
  iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after
  500ms

Status in linux package in Ubuntu:
  Expired

Bug description:
  After using wireless for some period of time, it stops working. dmesg
  report is attached. Rebooting the machine makes the wireless driver
  work again (for a little bit anyway). I haven't checked if it's
  related to suspend/resume, but I use this a lot. I can try bisecting
  for a kernel which doesn't have this problem, although between when I
  started having problems, I upgraded to Vivid (which didn't fix the
  problem.)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-18-generic 3.19.0-18.18
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ezyang 3167 F...m pulseaudio
   /dev/snd/controlC0:  ezyang 3167 F pulseaudio
  Date: Wed Jun  3 20:09:04 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/mapper/sabre-swap
  InstallationDate: Installed on 2013-11-21 (560 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 7762K3U
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-29 (6 days ago)
  dmi.bios.date: 02/21/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7SET25WW (1.11 )
  dmi.board.name: 7762K3U
  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:bvr7SET25WW(1.11):bd02/21/2008:svnLENOVO:pn7762K3U:pvrThinkPadX61Tablet:rvnLENOVO:rn7762K3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7762K3U
  dmi.product.version: ThinkPad X61 Tablet
  dmi.sys.vendor: LENOVO

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

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

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

Title:
  iwl4965 crashes randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo X61s, WLAN randomly stops working, typically after a few hours 
of running time. I don't know any remedy but to reboot.
  This behavior started maybe 2 or 3 months ago. My maching is usually kept up 
to date, so the problem might be caused by some kernel update at that time.

  The relevant part in dmesg (attached) starts with
  [ 5812.412141] iwl4965 :03:00.0: Error sending C_POWER_TBL: time out 
after 500ms.
  [ 5812.412156] iwl4965 :03:00.0: set power fail, ret = -110
  [ 5813.424145] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5813.424162] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 0
  [ 5813.924092] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5813.924107] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 5
  [ 5814.052099] iwl4965 :03:00.0: Queue 4 stuck for 2500 ms.
  [ 5814.052124] iwl4965 :03:00.0: On demand firmware reload
  [ 5814.424142] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5814.424168] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 6
  [ 5814.424421] iwl4965 :03:00.0: Master Disable Timed Out, 100 usec
  [ 5814.424468] ieee80211 phy0: Hardware restart was requested
  [ 5814.448160] iwl4965 :03:00.0: idx 0 not used in uCode key table.
  [ 5814.948182] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5814.948201] wls3: failed to remove key (0, **:**:**:**:**:**) from 
hardware (-110)
  [ 5818.964158] iwl4965 :03:00.0: START_ALIVE timeout after 4000ms.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mki2093 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Sep 27 13:29:36 2016
  HibernationDevice: RESUME=/dev/mapper/vgubuntu-swap
  InstallationDate: Installed on 2016-06-05 (113 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  MachineType: LENOVO 76693JG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/vgubuntu-system ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7NETC2WW (2.22 )
  dmi.board.name: 76693JG
  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:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn76693JG:pvrThinkPadX61s:rvnLENOVO:rn76693JG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 76693JG
  dmi.product.version: ThinkPad X61s
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1617550] Re: Kernel Build Fails for Fuse Module

[Seth Forshee]

Verified that 4.4.0-40.60 builds without error with CONFIG_FUSE_FS=m.

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

Title:
  Kernel Build Fails for Fuse Module

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

Bug description:
  SRU Justification

  Impact: Users attempting to build our xenial kernel tree with fuse as
  a module get an error that current_in_userns in undefined. This is
  because that symbol is not exported to modules.

  Fix: Export the symbol. This is done in the upstream patches, but that
  never got backported to xenial.

  Regression Potential: Virtually zero.

  ---

  ERROR: "current_in_userns" [fs/fuse/fuse.ko] undefined!
  /root/linux-4.4.0/scripts/Makefile.modpost:91: recipe for target '__modpost' 
failed
  make[3]: *** [__modpost] Error 1
  /root/linux-4.4.0/Makefile:1112: recipe for target 'modules' failed
  make[2]: *** [modules] Error 2
  make[2]: Leaving directory '/root/linux-4.4.0/debian/build/build-generic'
  Makefile:146: recipe for target 'sub-make' failed
  make[1]: *** [sub-make] Error 2
  make[1]: Leaving directory '/root/linux-4.4.0'
  debian/rules.d/2-binary-arch.mk:70: recipe for target 
'/root/linux-4.4.0/debian/stamps/stamp-build-generic' failed
  make: *** [/root/linux-4.4.0/debian/stamps/stamp-build-generic] Error 2

  Confirmed working using the following diff:

  https://www.redhat.com/archives/dm-devel/2016-April/msg00388.html

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

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

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

[Brad Figg]

tests ran:   3, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/ms10-35-mcdivittB0-kernel__4.4.0-40.60__2016-09-27_08-44-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1627074] kernel01 (s390x.zVM) - tests ran: 31, failed: 1

[Brad Figg]

tests ran:  31, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/kernel01__4.4.0-40.60__2016-09-27_09-39-00/results-index.html

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

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1625794] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 19, failed: 11

[Brad Figg]

tests ran:  19, failed: 11;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/ms10-34-mcdivittB0-kernel__3.19.0-70.78~14.04.1__2016-09-27_11-23-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/kernel02__4.8.0-18.20__2016-09-27_10-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/1627387

Title:
  linux: 4.8.0-17.19 -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:
  Confirmed
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 Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

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

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

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

[Brad Figg]

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-18.20/s2lp4__4.8.0-18.20__2016-09-27_10-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/1627387

Title:
  linux: 4.8.0-17.19 -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:
  Confirmed
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 Yakkety:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded

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

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

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

[Brad Figg]

tests ran:  31, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/ms10-35-mcdivittB0-kernel__4.4.0-40.60__2016-09-27_10-11-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1627074] kernel01 (s390x.zVM) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/kernel01__4.4.0-40.60__2016-09-27_11-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1627909] Re: zfs-linux should be using python3 for python userspace tools

[Tim Gardner]

** Also affects: zfs-linux (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Colin Ian King (colin-king)
   Status: In Progress

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

Title:
  zfs-linux should be using python3 for python userspace tools

Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Yakkety:
  In Progress

Bug description:
  dbufstat.py arc_summary.py arcstat.py should be using python3 rather
  than the older python2

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

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

[Kernel-packages] [Bug 1616677] Re: [Hyper-V] Rebase Hyper-V to 4.7.2 (stable)

[Chris Valean]

Thanks Brad!
We're doing a test pass on the proposed kernel and update this thread once we 
have the results.

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

Title:
  [Hyper-V] Rebase Hyper-V to 4.7.2 (stable)

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

Bug description:
  Please rebase the Hyper-V drivers and tools in lts-xenial (and
  yakkity) to the final v4.7.2 stable upstream kernel.

  The following files comprise Hyper-V support in the upstream kernel:
  arch/x86/kernel/cpu/mshyperv.c
  arch/x86/include/asm/mshyperv.h
  arch/x86/include/uapi/asm/hyperv.h
  include/linux/hyperv.h
  drivers/hv/channel.c
  drivers/hv/channel_mgmt.c
  drivers/hv/connection.c
  drivers/hv/hv_balloon.c
  drivers/hv/hv.c
  drivers/hv/hv_fcopy.c
  drivers/hv/hv_kvp.c
  drivers/hv/hv_snapshot.c
  drivers/hv/hv_util.c
  drivers/hv/hv_utils_transport.c
  drivers/hv/hv_utils_transport.h
  drivers/hv/hyperv_vmbus.h
  drivers/hv/ring_buffer.c
  drivers/hv/vmbus_drv.c
  tools/hv/hv_fcopy_daemon.c
  tools/hv/hv_get_dhcp_info.sh
  tools/hv/hv_get_dns_info.sh
  tools/hv/hv_kvp_daemon.c
  tools/hv/hv_set_ifconfig.sh
  tools/hv/hv_vss_daemon.c
  tools/hv/lsvmbus
  drivers/input/serio/hyperv-keyboard.c
  drivers/net/hyperv/hyperv_net.h
  drivers/net/hyperv/netvsc.c
  drivers/net/hyperv/netvsc_drv.c
  drivers/net/hyperv/rndis_filter.c
  drivers/scsi/storvsc_drv.c
  drivers/hid/hid-hyperv.c
  drivers/pci/host/pci-hyperv.c
  drivers/video/fbdev/hyperv_fb.c

  While I know a number of post-4.6 commits are already included, I am
  including all of the commits from 4.6 to 4.7.2 for reference:

  channel_mgmt.c : commit cd95aad5579371ac332507fc946008217fc37e6c : 
Drivers: hv: vmbus: handle various crash scenarios
  connection.c : commit 5cc472477f928fb8584eb8e08245c9cf9002d74a : Drivers: 
hv: vmbus: Export the vmbus_set_event() API
  hv_balloon.c : commit 77c0c9735bc0ba5898e637a3a20d6bcb50e3f67d : Drivers: 
hv: balloon: don't crash when memory is added in non-sorted order
  hv_balloon.c : commit d19a55d6ed5bf0ffe553df2d8bf91d054ddf2d76 : Drivers: 
hv: balloon: reset host_specified_ha_region
  hv_kvp.c : commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc : Drivers: hv: 
kvp: fix IP Failover
  hyperv_fb.c : commit 696ca5e82c057a272381ae6064d59eb97a578397 : 
drivers:hv: Use new vmbus_mmio_free() from client drivers.
  hyperv.h : commit 97fb77dc87582300fa3c141b63699f853576cab1 : drivers:hv: 
Make a function to free mmio regions through vmbus
  hyperv.h : commit a6341f24cdf1ec14dc26743a409a17378db5 : Drivers: hv: 
vmbus: Introduce functions for estimating room in the ring buffer
  hyperv.h : commit ab028db41ca9174caab7f9e3fc0a2e7f4a418410 : Drivers: hv: 
vmbus: Implement APIs to support "in place" consumption of vmbus packets
  hyperv_net.h : commit 10082f98878a9dff1563745f9f1dd9d1ff142700 : 
hv_netvsc: Eliminate status from struct hv_netvsc_packet
  hyperv_net.h : commit 3d541ac5a92af708d0085925d136f875f3a58d57 : 
hv_netvsc: untangle the pointer mess
  hyperv_net.h : commit c85e4924452ae8225c8829f3fa8a2f7baa34bc5c : 
hv_netvsc: Fix book keeping of skb during batching process
  hyperv_vmbus.h : commit 4dbfc2e68004c60edab7e8fd26784383dd3ee9bc : 
Drivers: hv: kvp: fix IP Failover
  hyperv_vmbus.h : commit 5cc472477f928fb8584eb8e08245c9cf9002d74a : 
Drivers: hv: vmbus: Export the vmbus_set_event() API
  hyperv_vmbus.h : commit cd95aad5579371ac332507fc946008217fc37e6c : 
Drivers: hv: vmbus: handle various crash scenarios
  lsvmbus : commit 552beb4930ef3889d42a049eb9ba3533b4cbe0f6 : tools: hv: 
lsvmbus: add pci pass-through UUID
  netvsc_drv.c : commit 15cfd40771e18a4e9b788c64c9db2606f958b93d : 
hv_netvsc: Fix the list processing for network change event
  netvsc_drv.c : commit 1bdcec8a5f05445752a0639edd603ac09ae6c553 : 
hv_netvsc: use start_remove flag to protect netvsc_link_change()
  netvsc_drv.c : commit 84bf9cefb162b197da20a0f4388929f4b5ba5db4 : 
hv_netvsc: Implement support for VF drivers on Hyper-V
  pci-hyperv.c : commit 696ca5e82c057a272381ae6064d59eb97a578397 : 
drivers:hv: Use new vmbus_mmio_free() from client drivers.
  pci-hyperv.c : commit bdd74440d9e887b1fa648eefa17421def5f5243c : PCI: hv: 
Add explicit barriers to config space access
  pci-hyperv.c : commit deb22e5c84c884a129d801cf3bfde7411536998d : PCI: hv: 
Report resources release after stopping the bus
  ring_buffer.c : commit a6341f24cdf1ec14dc26743a409a17378db5 : 
Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer
  rndis_filter.c : commit 0a1275ca5128b84c149960969ed351ae00eb : 
hv_netvsc: get rid of struct net_device pointer in struct netvsc_device
  rndis_filter.c : commit 

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Emsi]

No luck with 14.04. After couple of days two test machines restarted 
unexpectedly at the very same moment. I sustepct kernel crash but the virtual 
console is gone and nothing was logged.
On the other hand the xenial machine is working for weeks now without any 
issues.

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1625794] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 3, failed: 1

[Brad Figg]

tests ran:   3, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/ms10-34-mcdivittB0-kernel__3.19.0-70.78~14.04.1__2016-09-27_09-47-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+subscriptions

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

[Kernel-packages] [Bug 1586302] Re: Bluetooth and other issues connecting to Bluetooth speaker

[Dirk-Jan van Leeuwen]

I experience similar behavior on my UE Boom2 (Logitech) Wireless speaker
(http://www.ultimateears.com/en-us/ueboom2/specs).

It pairs, makes a connection and drops it and thus no audio on the
speaker.

According to vendor specs it uses A2DP for audio playback.

Aquaris E4.5 @ OTA-13

Which log files/output is needed for debugging this?

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

Title:
  Bluetooth and other issues connecting to Bluetooth speaker

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Aquaris E4.5 @ OTA 10.1

  Attempting to connect to EasyAcc Bluetooth Speaker

  (https://www.amazon.co.uk/EasyAcc-Portable-Rechargeable-Bluetooth-
  
Microphone/dp/B00JK6MQEI/ref=sr_1_3?ie=UTF8=1464297589=8-3=easyacc)

  Phone finds speaker and connects (no pin required). Audio is heard
  from the speaker for 1 second, then stops.

  The volume control stills says audio is routed to bluetooth speaker,
  but no sound output.

  Bluetooth cannot then be turned off (button appears to function to
  “off” position , but bluetooth remains active and button returns to
  “on” position after exactly 30 seconds)

  Attempting to switch to flight mode – the button “greys out” for 30
  seconds, then appears as “on”. Wifi is disconnected but mobile network
  connections are still active.

  Switching off the bluetooth speaker has no effect, the phone still
  appears to be connected to it.

  Attempting  to restart does not work – The phone switches off and does
  not restart. Hard reset is required to get the phone to boot again.
  Also if the phone is powered off, it will not restart until a hard
  reset is performed.

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

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

[Kernel-packages] [Bug 1627074] kernel01 (s390x.zVM) - tests ran: 19, failed: 7

[Brad Figg]

tests ran:  19, failed: 7;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/kernel01__4.4.0-40.60__2016-09-27_10-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1627074] kernel01 (s390x.zVM) - tests ran: 136, failed: 27

[Brad Figg]

tests ran: 136, failed: 27;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/kernel01__4.4.0-40.60__2016-09-27_10-44-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

[Andrew Smith]

I run LTS releases and ran into this Shutdown failure about the time the 
upgrade notification came through from 14.04, so did not investigate closely as 
I suspected it would go when I upgraded to 16.04. It didn't. Mine is a pretty 
standard i7 desktop with an SSD. I have noticed the following:
*When it fails I can either Suspend it or pop up a terminal and do "shutdown -h 
now". Both work immediately but,
*If Suspend is used, the following time I can do a normal Shutdown and it works 
normally. The normal Shutdown after that fails.
*If the terminal command is used, the following time I do a normal Shutdown it 
fails.
So somehow Suspend circumvents the problem for one time. I am no command line 
guru so I don't know what logs or files I should be looking at. Any suggestions?

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

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

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

[Kernel-packages] [Bug 1627052] Re: 4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus

[Robert C Jennings]

Fixed in cloud-images build 20160927

** Changed in: cloud-images
   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/1627052

Title:
  4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus

Status in cloud-images:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I usually run kvm with '-serial stdio' after adding
  GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0" to /etc/default/grub.  This
  will give me a serial console where I can login and, more important,
  get kernel logs.

  After install 4.8.0-16.17 I'm unable to login in the serial console,
  and I'm getting a lot of messages:

genirq: Flags mismatch irq 4.  (serial) vs. 0080
  (goldfish_pdev_bus)

  System seems to be working fine otherwise.

  4.8.0-15.16 didn't show this behaviour.

  The obvious suspect commits are the "SAUCE: irqchip/gicv3-its:*" in
  -16, although the several config changes may also be involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1627052/+subscriptions

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

[Kernel-packages] [Bug 1627074] kernel01 (s390x.zVM) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/kernel01__4.4.0-40.60__2016-09-27_11-44-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1627074] kernel01 (s390x.zVM) - tests ran: 83, failed: 1

[Brad Figg]

tests ran:  83, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/kernel01__4.4.0-40.60__2016-09-27_11-15-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1628061] [NEW] iwl4965 crashes randomly

[Michael Kiermaier]

Public bug reported:

On my Lenovo X61s, WLAN randomly stops working, typically after a few hours of 
running time. I don't know any remedy but to reboot.
This behavior started maybe 2 or 3 months ago. My maching is usually kept up to 
date, so the problem might be caused by some kernel update at that time.

The relevant part in dmesg (attached) starts with
[ 5812.412141] iwl4965 :03:00.0: Error sending C_POWER_TBL: time out after 
500ms.
[ 5812.412156] iwl4965 :03:00.0: set power fail, ret = -110
[ 5813.424145] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
[ 5813.424162] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 0
[ 5813.924092] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
[ 5813.924107] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 5
[ 5814.052099] iwl4965 :03:00.0: Queue 4 stuck for 2500 ms.
[ 5814.052124] iwl4965 :03:00.0: On demand firmware reload
[ 5814.424142] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
[ 5814.424168] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 6
[ 5814.424421] iwl4965 :03:00.0: Master Disable Timed Out, 100 usec
[ 5814.424468] ieee80211 phy0: Hardware restart was requested
[ 5814.448160] iwl4965 :03:00.0: idx 0 not used in uCode key table.
[ 5814.948182] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
[ 5814.948201] wls3: failed to remove key (0, **:**:**:**:**:**) from hardware 
(-110)
[ 5818.964158] iwl4965 :03:00.0: START_ALIVE timeout after 4000ms.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mki2093 F pulseaudio
CurrentDesktop: XFCE
Date: Tue Sep 27 13:29:36 2016
HibernationDevice: RESUME=/dev/mapper/vgubuntu-swap
InstallationDate: Installed on 2016-06-05 (113 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
MachineType: LENOVO 76693JG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/vgubuntu-system ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-38-generic N/A
 linux-backports-modules-4.4.0-38-generic  N/A
 linux-firmware1.157.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7NETC2WW (2.22 )
dmi.board.name: 76693JG
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:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn76693JG:pvrThinkPadX61s:rvnLENOVO:rn76693JG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 76693JG
dmi.product.version: ThinkPad X61s
dmi.sys.vendor: LENOVO

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

Title:
  iwl4965 crashes randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo X61s, WLAN randomly stops working, typically after a few hours 
of running time. I don't know any remedy but to reboot.
  This behavior started maybe 2 or 3 months ago. My maching is usually kept up 
to date, so the problem might be caused by some kernel update at that time.

  The relevant part in dmesg (attached) starts with
  [ 5812.412141] iwl4965 :03:00.0: Error sending C_POWER_TBL: time out 
after 500ms.
  [ 5812.412156] iwl4965 :03:00.0: set power fail, ret = -110
  [ 5813.424145] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5813.424162] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 0
  [ 5813.924092] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5813.924107] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 5
  [ 5814.052099] iwl4965 :03:00.0: Queue 4 stuck for 2500 ms.
  [ 5814.052124] iwl4965 :03:00.0: On demand firmware reload
  [ 5814.424142] iwl4965 :03:00.0: Error sending C_ADD_STA: time out after 
500ms.
  [ 5814.424168] wls3: HW problem - can not stop rx aggregation for 
**:**:**:**:**:** tid 6
  [ 5814.424421] iwl4965 :03:00.0: Master Disable Timed Out, 100 usec
  [ 5814.424468] ieee80211 phy0: Hardware restart was requested
  [ 5814.448160] iwl4965 :03:00.0: idx 0 not used in uCode 

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

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/modoc__4.4.0-40.60__2016-09-27_12-05-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Brad Figg]

tests ran:  10, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/modoc__3.19.0-70.78~14.04.1__2016-09-27_21-21-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+subscriptions

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

[Kernel-packages] [Bug 1628305] [NEW] ACPI: Dynamic OEM Table Load:

[Cristian Aravena Romero]

Public bug reported:

[0.128304] ACPI: Dynamic OEM Table Load:
[0.128316] ACPI: SSDT 0x886FD09F2800 000784 (v01 PmRef  Cpu0Cst  
3001 INTL 20061109)
[0.129166] ACPI: Dynamic OEM Table Load:
[0.129174] ACPI: SSDT 0x886FD0A2B800 000303 (v01 PmRef  ApIst
3000 INTL 20061109)
[0.129902] ACPI: Dynamic OEM Table Load:
[0.129909] ACPI: SSDT 0x886FD0ABF000 000119 (v01 PmRef  ApCst
3000 INTL 20061109)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
Uname: Linux 4.8.0-17-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2141 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Sep 27 19:29:22 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (429 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.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-lowlatency N/A
 linux-backports-modules-4.8.0-17-lowlatency  N/A
 linux-firmware   1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
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.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  ACPI: Dynamic OEM Table Load:

Status in linux package in Ubuntu:
  New

Bug description:
  [0.128304] ACPI: Dynamic OEM Table Load:
  [0.128316] ACPI: SSDT 0x886FD09F2800 000784 (v01 PmRef  Cpu0Cst  
3001 INTL 20061109)
  [0.129166] ACPI: Dynamic OEM Table Load:
  [0.129174] ACPI: SSDT 0x886FD0A2B800 000303 (v01 PmRef  ApIst
3000 INTL 20061109)
  [0.129902] ACPI: Dynamic OEM Table Load:
  [0.129909] ACPI: SSDT 0x886FD0ABF000 000119 (v01 PmRef  ApCst
3000 INTL 20061109)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:29:22 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 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.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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 

[Kernel-packages] [Bug 1628307] [NEW] ACPI: Executed 1 blocks of module-level executable AML code

[Cristian Aravena Romero]

Public bug reported:

[0.121702] ACPI: Executed 1 blocks of module-level executable AML
code

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
Uname: Linux 4.8.0-17-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2141 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Sep 27 19:32:02 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (429 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.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-lowlatency N/A
 linux-backports-modules-4.8.0-17-lowlatency  N/A
 linux-firmware   1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
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.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  ACPI: Executed 1 blocks of module-level executable AML code

Status in linux package in Ubuntu:
  New

Bug description:
  [0.121702] ACPI: Executed 1 blocks of module-level executable AML
  code

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:32:02 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 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.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1628307/+subscriptions

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

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

Title:
  ACPI: Dynamic OEM Table Load:

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.128304] ACPI: Dynamic OEM Table Load:
  [0.128316] ACPI: SSDT 0x886FD09F2800 000784 (v01 PmRef  Cpu0Cst  
3001 INTL 20061109)
  [0.129166] ACPI: Dynamic OEM Table Load:
  [0.129174] ACPI: SSDT 0x886FD0A2B800 000303 (v01 PmRef  ApIst
3000 INTL 20061109)
  [0.129902] ACPI: Dynamic OEM Table Load:
  [0.129909] ACPI: SSDT 0x886FD0ABF000 000119 (v01 PmRef  ApCst
3000 INTL 20061109)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:29:22 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 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.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1628305/+subscriptions

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

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

Title:
  ACPI: Executed 1 blocks of module-level executable AML code

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.121702] ACPI: Executed 1 blocks of module-level executable AML
  code

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:32:02 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 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.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1628307/+subscriptions

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

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

Title:
  PCCT header not found.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.114784] PCCT header not found.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:34:08 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 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.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1628308/+subscriptions

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

[Kernel-packages] [Bug 1628279] Re: python utilities script suffix (.py) should be removed as per Policy 10.4

[Eric Desrochers]

** Changed in: zfs-linux (Ubuntu)
   Importance: Low => Medium

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

Title:
  python utilities script suffix (.py) should be removed as per Policy
  10.4

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  The zfs utilities scripts shipped with debian and ubuntu such as :

  * arc_summary.py : Provides a summary of the statistics
  https://github.com/zfsonlinux/zfs/blob/master/cmd/arc_summary

  * arcstat.py : Print out ZFS ARC Statistics exported via kstat(1)
  https://github.com/zfsonlinux/zfs/tree/master/cmd/arcstat

  * dbufstat.py : Print out statistics for all cached dmu buffers
  https://github.com/zfsonlinux/zfs/blob/master/cmd/dbufstat

  should be renamed according to Policy 10.4 :

  [https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts]

  "When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as .sh or .pl that
  denotes the scripting language currently used to implement it."

  Ideally, this should be fixed and upstreamed to Debian (or to zfslinux
  upstream) as well.

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

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

[Kernel-packages] [Bug 1626749] Re: autofs set $USER to "root" instead of current user

[Alberto Salvia Novella]

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1626370] Re: Sound problems / slow performance /not responsive

[Alberto Salvia Novella]

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

** Changed in: linux (Ubuntu)
   Importance: High => 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/1626370

Title:
  Sound problems / slow performance /not responsive

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan is always working very hard and system is hot. When I run windows
  8 on the same machine it is ok. New HD and fan too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  peteruser   2757 F pulseaudio
   /dev/snd/controlC0:  peteruser   2757 F pulseaudio
  Date: Thu Sep 22 10:57:12 2016
  HibernationDevice: RESUME=UUID=def99bab-c578-4f83-b26e-3a1168b65b03
  MachineType: LENOVO 20193
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=b6bd5968-eb36-4de2-8e53-6906d540f6b6 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6BCN44WW(V2.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y500
  dmi.modalias: 
dmi:bvnLENOVO:bvr6BCN44WW(V2.04):bd05/21/2013:svnLENOVO:pn20193:pvrLenovoIdeaPadY500:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY500:
  dmi.product.name: 20193
  dmi.product.version: Lenovo IdeaPad Y500
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1625794] modoc (ppc64el) - tests ran: 19, failed: 6

[Brad Figg]

tests ran:  19, failed: 6;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/modoc__3.19.0-70.78~14.04.1__2016-09-27_23-23-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+subscriptions

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

[Kernel-packages] [Bug 1628363] [NEW] VIA VL812 hub stops working with 4.4.0-40.60

[Dave Chiluk]

Public bug reported:

VIA VL812 hub stops working with 4.4.0-40.60.  Works fine with
4.4.0-39.59.

Logs include both boot with 4.4.0-39 *(most recent) and 4.4.0-40
(previous boot).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.40.42
ProcVersionSignature: Ubuntu 4.4.0-39.59-generic 4.4.21
Uname: Linux 4.4.0-39-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep 27 22:48:35 2016
HibernationDevice: RESUME=UUID=1cb62c08-3564-4d8a-846c-6963690d
InstallationDate: Installed on 2016-01-15 (256 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-39-generic 
root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-39-generic N/A
 linux-backports-modules-4.4.0-39-generic  N/A
 linux-firmware1.157.4
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2013
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DX79SI
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG28808-500
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
klp-taint: 12289

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


** Tags: amd64 apport-bug package-from-proposed third-party-packages 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/1628363

Title:
  VIA VL812 hub stops working with 4.4.0-40.60

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  VIA VL812 hub stops working with 4.4.0-40.60.  Works fine with
  4.4.0-39.59.

  Logs include both boot with 4.4.0-39 *(most recent) and 4.4.0-40
  (previous boot).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.40.42
  ProcVersionSignature: Ubuntu 4.4.0-39.59-generic 4.4.21
  Uname: Linux 4.4.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 27 22:48:35 2016
  HibernationDevice: RESUME=UUID=1cb62c08-3564-4d8a-846c-6963690d
  InstallationDate: Installed on 2016-01-15 (256 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-39-generic 
root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-39-generic N/A
   linux-backports-modules-4.4.0-39-generic  N/A
   linux-firmware1.157.4
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DX79SI
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG28808-500
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
  klp-taint: 12289

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

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

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

Title:
  VIA VL812 hub stops working with 4.4.0-40.60

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  VIA VL812 hub stops working with 4.4.0-40.60.  Works fine with
  4.4.0-39.59.

  Logs include both boot with 4.4.0-39 *(most recent) and 4.4.0-40
  (previous boot).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.40.42
  ProcVersionSignature: Ubuntu 4.4.0-39.59-generic 4.4.21
  Uname: Linux 4.4.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 27 22:48:35 2016
  HibernationDevice: RESUME=UUID=1cb62c08-3564-4d8a-846c-6963690d
  InstallationDate: Installed on 2016-01-15 (256 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-39-generic 
root=UUID=029afe58-00c3-4872-9556-b3fd990c5cf1 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
scsi_mod.use_blk_mq=y dm_mod.use_blk_mq=y crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-39-generic N/A
   linux-backports-modules-4.4.0-39-generic  N/A
   linux-firmware1.157.4
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SIX7910J.86A.0594.2013.0806.2241
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DX79SI
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG28808-500
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSIX7910J.86A.0594.2013.0806.2241:bd08/06/2013:svn:pn:pvr:rvnIntelCorporation:rnDX79SI:rvrAAG28808-500:cvn:ct3:cvr:
  klp-taint: 12289

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

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

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

[bugproxy]

--- Comment From nasas...@in.ibm.com 2016-09-28 00:58 EDT---
(In reply to comment #7)
> Could you try upgrading to the newer 4.8.0-17.19 kernel that was promoted to
> the release pocket last night:
>
> https://launchpad.net/ubuntu/+source/linux/4.8.0-17.19
>

Tested with latest kernel i.e. 4.8.0-17.19, not seeing OOPs or any other
error messages.

root@pkvmhab010:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.8.0-17-generic
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast

root@pkvmhab010:~# apt install -y btrfs-progs/yakkety
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '4.7-1' (Ubuntu:16.10/yakkety [ppc64el]) for 'btrfs-progs'
The following NEW packages will be installed:
btrfs-progs
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/562 kB of archives.
After this operation, 5,656 kB of additional disk space will be used.
Selecting previously unselected package btrfs-progs.
(Reading database ... 130815 files and directories currently installed.)
Preparing to unpack .../btrfs-progs_4.7-1_ppc64el.deb ...
Unpacking btrfs-progs (4.7-1) ...
Processing triggers for initramfs-tools (0.125ubuntu3) ...
update-initramfs: Generating /boot/initrd.img-4.8.0-17-generic
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
Processing triggers for libc-bin (2.24-0ubuntu1) ...
Setting up btrfs-progs (4.7-1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for initramfs-tools (0.125ubuntu3) ...
update-initramfs: Generating /boot/initrd.img-4.8.0-17-generic
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
Processing triggers for libc-bin (2.24-0ubuntu1) ...

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

Title:
  [Ubuntu16.10]KV4.8: OOPs while updating initramfs

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - NAGESWARA R. SASTRY  - 2016-09-22 
06:40:59 ==
  ---Problem Description---
  Try installing btrfs-progs using 'apt install -y btrfs-progs'
  At the time of updating initramfs seeing a 'segfault' and kernel OOPs
   
  Contact Information = nasas...@in.ibm.com 
   
  ---uname output---
  Linux pkvmhab010 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8348-21C 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   # apt install -y btrfs-progs/yakkety
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Selected version '4.7-1' (Ubuntu:16.10/yakkety [ppc64el]) for 'btrfs-progs'
  The following package was automatically installed and is no longer required:
libprotobuf-lite9v5
  Use 'apt autoremove' to remove it.
  The following additional packages will be installed:
liblzo2-2
  The following NEW packages will be installed:
btrfs-progs liblzo2-2
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  Need to get 629 kB of archives.
  After this operation, 5,987 kB of additional disk space will be used.
  Get:1 http://us.ports.ubuntu.com/ubuntu-ports yakkety/main ppc64el liblzo2-2 
ppc64el 2.08-1.2 [67.2 kB]
  Get:2 http://us.ports.ubuntu.com/ubuntu-ports yakkety/main ppc64el 
btrfs-progs ppc64el 4.7-1 [562 kB]
  Fetched 629 kB in 0s (2,416 kB/s)
  Selecting previously unselected package liblzo2-2:ppc64el.
  (Reading database ... 129624 files and directories currently installed.)
  Preparing to unpack .../0-liblzo2-2_2.08-1.2_ppc64el.deb ...
  Unpacking liblzo2-2:ppc64el (2.08-1.2) ...
  Selecting previously unselected package btrfs-progs.
  Preparing to unpack .../1-btrfs-progs_4.7-1_ppc64el.deb ...
  Unpacking btrfs-progs (4.7-1) ...
  Processing triggers for initramfs-tools (0.125ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.8.0-11-generic
  Segmentation fault
   
   
  Oops output:
   [  643.673740] Unable to handle kernel paging request for data at address 
0x0020
  [  643.674688] Faulting instruction address: 0xc0185040
  [  643.675418] Oops: Kernel access of bad area, sig: 11 [#1]
  [  643.676115] SMP NR_CPUS=2048 NUMA PowerNV
  [  643.676650] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
tun bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter evdev joydev at24 ghash_generic gf128mul vmx_crypto 
nvmem_core sg powernv_rng rng_core ip_tables x_tables autofs4 ext4 crc16 jbd2 
fscrypto mbcache dm_mod sr_mod cdrom ses enclosure scsi_transport_sas sd_mod 
hid_generic usbhid hid uas usb_storage xhci_pci bnx2x ast xhci_hcd i2c_algo_bit 
ttm 

[Kernel-packages] [Bug 1625794] modoc (ppc64el) - tests ran: 81, failed: 19

[Brad Figg]

tests ran:  81, failed: 19;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/modoc__3.19.0-70.78~14.04.1__2016-09-28_03-10-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+subscriptions

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

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

[Brad Figg]

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/dwalin__4.4.0-40.60__2016-09-28_03-28-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1620317] Re: ISST-LTE:pNV: system ben is hung during ST (nvme)

[bugproxy]

--- Comment From gbert...@br.ibm.com 2016-09-27 23:02 EDT---
Hi Canonical,

Our test teams had problems with booting the Ubuntu-4.4.0-40.60 kernel.
They hit an Oops in the NVMe probe path.

My current understanding is that this is already fixed in your kernel by
the fixup commit: e9820e415895 (" UBUNTU: (fix) NVMe: Don't unmap
controller registers on reset") which will be published in kernel
Ubuntu-4.4.0-41.61.

We will try again with that version.

While we are here, I noticed another issue with the backport of
30d6592fce71 (" NVMe: Don't unmap controller registers on reset").
Looks like you are missing the fixup commit that went later into the
4.4.y tree:

81e9a969c441 ('nvme: Call pci_disable_device on the error path") #4.4.y
tree.

I opened Bug 146899 to track this.  It will be mirrored soon.

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

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

Title:
  ISST-LTE:pNV: system ben is hung during ST (nvme)

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

Bug description:
  On when we are running I/O intensive tasks and CPU addition/removal,
  the block may hang stalling the entire machine.

  The backtrace below is one of the symptoms:

  [12747.49] ---[ end trace b4d8d720952460b5 ]---
  [12747.126885] Trying to free IRQ 357 from IRQ context!
  [12747.146930] [ cut here ]
  [12747.166674] WARNING: at 
/build/linux-iLHNl3/linux-4.4.0/kernel/irq/manage.c:1438
  [12747.184069] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) 
mlx4_ib(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) ib_addr(OE) mlx4_en(OE) 
mlx4_core(OE) binfmt_misc xfs joydev input_leds mac_hid ofpart cmdlinepart 
powernv_flash ipmi_powernv mtd ipmi_msghandler at24 opal_prd powernv_rng 
ibmpowernv uio_pdrv_genirq uio sunrpc knem(OE) autofs4 btrfs xor raid6_pq 
hid_generic usbhid hid uas usb_storage nouveau ast bnx2x i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx5_core(OE) ahci 
drm mdio libcrc32c mlx_compat(OE) libahci vxlan nvme ip6_udp_tunnel udp_tunnel
  [12747.349013] CPU: 80 PID: 0 Comm: swapper/80 Tainted: GW  OEL  
4.4.0-21-generic #37-Ubuntu
  [12747.369046] task: c00f1fab89b0 ti: c00f1fb6c000 task.ti: 
c00f1fb6c000
  [12747.404848] NIP: c0131888 LR: c0131884 CTR: 
300303f0
  [12747.808333] REGS: c00f1fb6e550 TRAP: 0700   Tainted: GW  OEL   
(4.4.0-21-generic)
  [12747.867658] MSR: 900100029033   CR: 2802  
XER: 2000
  [12747.884783] CFAR: c0aea8f4 SOFTE: 1 
  GPR00: c0131884 c00f1fb6e7d0 c15b4200 0028 
  GPR04: c00f2a409c50 c00f2a41b4e0 000f2948 33da 
  GPR08: 0007 c0f8b27c 000f2948 90011003 
  GPR12: 2200 c7b6f800 c00f2a40a938 0100 
  GPR16: c00f1148 3a98   
  GPR20:  d9521008 d95146a0 f000 
  GPR24: c4a19ef0  0003 007d 
  GPR28: 0165 c00eefeb1800 c00eef830600 0165 
  [12748.243270] NIP [c0131888] __free_irq+0x238/0x370
  [12748.254089] LR [c0131884] __free_irq+0x234/0x370
  [12748.269738] Call Trace:
  [12748.286740] [c00f1fb6e7d0] [c0131884] __free_irq+0x234/0x370 
(unreliable)
  [12748.289687] [c00f1fb6e860] [c0131af8] free_irq+0x88/0xb0
  [12748.304594] [c00f1fb6e890] [d9514528] 
nvme_suspend_queue+0xc8/0x150 [nvme]
  [12748.333825] [c00f1fb6e8c0] [d951681c] 
nvme_dev_disable+0x3fc/0x400 [nvme]
  [12748.340913] [c00f1fb6e9a0] [d9516ae4] nvme_timeout+0xe4/0x260 
[nvme]
  [12748.357136] [c00f1fb6ea60] [c0548a34] 
blk_mq_rq_timed_out+0x64/0x110
  [12748.383939] [c00f1fb6ead0] [c054c540] bt_for_each+0x160/0x170
  [12748.399292] [c00f1fb6eb40] [c054d4e8] 
blk_mq_queue_tag_busy_iter+0x78/0x110
  [12748.402665] [c00f1fb6eb90] [c0547358] 
blk_mq_rq_timer+0x48/0x140
  [12748.438649] [c00f1fb6ebd0] [c014a13c] call_timer_fn+0x5c/0x1c0
  [12748.468126] [c00f1fb6ec60] [c014a5fc] 
run_timer_softirq+0x31c/0x3f0
  [12748.483367] [c00f1fb6ed30] [c00beb78] __do_softirq+0x188/0x3e0
  [12748.498378] [c00f1fb6ee20] [c00bf048] irq_exit+0xc8/0x100
  [12748.501048] [c00f1fb6ee40] [c001f954] timer_interrupt+0xa4/0xe0
  [12748.516377] 

[Kernel-packages] [Bug 1628336] Re: mount-image-callback cannot mount partitioned disk image

[Leann Ogasawara]

** Tags added: kernel-4.8

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

Title:
  mount-image-callback cannot mount partitioned disk image

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This fails on 4.8.0-17-generic and passes on

  $ sudo apt-get update
  $ sudo apt-get install -qy cloud-image-utils
  $ wget 
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
  $ cp xenial-server-cloudimg-amd64-disk1.img disk.img
  $ sudo mount-image-callback xenial-server-cloudimg-amd64-disk1.img -v ls 
_MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected xenial-server-cloudimg-amd64-disk1.img (qcow2) to /dev/nbd0. 
waiting for device.
  partitioned disk.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  waiting for /dev/nbd0p1 part=1 to be ready.
  gave up on waiting for /dev/nbd0p1
  $ echo $?
  1

  
  On an identical system other than 'apt-get install linux-virtual' to get the 
new kernel, you see:

  $ uname -r
  4.4.0-9136-generic

  $ sudo mount-image-callback disk.img -v ls _MOUNTPOINT_
  replaced string _MOUNTPOINT_ in arguments arg 1
  waiting on pidfile for /dev/nbd0 in /sys/block/nbd0/pid
  connected disk.img (qcow2) to /dev/nbd0. waiting for device.
  partitioned disk.
  mounted /dev/nbd0p1 via qemu-nbd /dev/nbd0
  invoking: MOUNTPOINT=/tmp/mount-image-callback.Y8D4lk/mp ls 
/tmp/mount-image-callback.Y8D4lk/mp
  bin   etc lib   media  proc  sbin  sys  var
  boot  homelib64   mntroot  snap  tmp  vmlinuz
  dev   initrd.img  lost+found  optrun   srv   usr
  cmd returned 0. unmounting /tmp/mount-image-callback.Y8D4lk/mp

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-generic 4.8.0-17.19
  ProcVersionSignature: User Name 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 27 19:04 seq
   crw-rw 1 root audio 116, 33 Sep 27 19:04 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Sep 28 00:58:49 2016
  Ec2AMI: ami-0438
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=072136f3-5666-4381-83bd-8d7175059be3 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1~cloud0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-vivid
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr12.0.3:cvnQEMU:ct1:cvrpc-i440fx-vivid:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 12.0.3
  dmi.sys.vendor: OpenStack Foundation

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

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

[Kernel-packages] [Bug 1628284] Re: yakkety: daily powerpc server ISO fails to find cdrom during install in a VM

[Leann Ogasawara]

** Tags added: kernel-4.8

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

Title:
  yakkety: daily powerpc server ISO fails to find cdrom during install
  in a VM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  xenial daily ISO successfully installs using the same method on the
  same system, but yakkety reports:

  Sep 27 21:13:14 cdrom-detect: Searching for Ubuntu installation media...
  Sep 27 21:13:18 cdrom-detect: Devices: ''
  Sep 27 21:13:23 cdrom-detect: Devices: ''
  Sep 27 21:13:24 kernel: [  154.649279] random: crng init done
  Sep 27 21:13:28 cdrom-detect: Devices: ''
  Sep 27 21:13:33 cdrom-detect: Devices: ''
  Sep 27 21:13:38 cdrom-detect: Devices: ''
  Sep 27 21:13:43 cdrom-detect: Devices: ''
  Sep 27 21:13:48 cdrom-detect: Devices: ''
  Sep 27 21:13:53 cdrom-detect: Devices: ''
  Sep 27 21:13:58 cdrom-detect: Devices: ''
  Sep 27 21:14:06 cdrom-detect: CDROM-detect failed; unmounting CD just to be 
sure
  Sep 27 21:14:06 main-menu[267]: WARNING **: Configuring 'cdrom-detect' failed 
with error code 1
  Sep 27 21:14:06 main-menu[267]: WARNING **: Menu item 'cdrom-detect' failed.

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

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

[Kernel-packages] [Bug 1606178] Re: Can't suspend to ram, since linux3.11 and more

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

Title:
  Can't suspend to ram, since linux3.11 and more

Status in linux package in Ubuntu:
  Expired

Bug description:
  I can't suspend to ram since linux 3.11, with ubuntu12.04. Older version 
(3.8, 3.5 etc..) suspend perfectly.
  So, I can't suspend with ubuntu 14.04 and 16.04. :(
  Solutions from here (specially test newer kernels) don't work for me: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566302
  ASRock N68C-S UCC, with phenomIIx4 processor.

  ~$ uname -a
  Linux DDX-STUDIO 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux


  ~$ sudo dmidecode -t baseboard
  # dmidecode 2.11
  SMBIOS 2.4 present.

  Handle 0x0002, DMI type 2, 15 bytes
  Base Board Information
Manufacturer: ASRock
Product Name: N68C-S UCC
Version:   
Serial Number:   
Asset Tag:   
Features:
Board is a hosting board
Board is replaceable
Location In Chassis:   
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', 
'/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Mon Jul 25 12:00:17 2016
  HibernationDevice: RESUME=UUID=3d14e312-ebd4-4129-9183-dcb17519893d
  IwConfig:
   lono wireless extensions.
   
   enp0s7no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0810:0001 Personal Communication Systems, Inc. Dual 
PSX Adaptor
   Bus 002 Device 003: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
   Bus 002 Device 002: ID 056a:00b2 Wacom Co., Ltd Intuos3 9x12
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=7411581c-dc6e-4be3-85ba-bf5ae0c61bbc ro splash quiet vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68C-S UCC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1600759] Re: Kernel crashes

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

Title:
  Kernel crashes

Status in linux package in Ubuntu:
  Expired

Bug description:
  Recently, Ubuntu moved to kernel 4.4.x. On my ASUS X751L, this results
  in my LVDS+external VGA displays to regularly go to sleep/energy
  saving mode (even when being actively used) or to "scramble". As a
  consequence, I reverted to kernel 4.2.0-35-generic. This worked very
  well until I dist-upgraded last thursday. Now, the computer crashes
  regularly, notably when it is (xscreensaver-)locked (mostly while
  executing the "molecule" (OpenGL) screensaver).

  I'm not sure if the crash occurs because of kernel, xscreensaver or an
  mplayer script I run with cron to play a beep every hour (don't ask
  why...).

  This is a critical crash, so I assume there is a security issue
  behind...

  Some extracts of my syslog:

  [computer working...]
  Jul  8 17:55:05 user-X751LAB sSMTP[10137]: Sent mail for r...@gmail.com (221 
2.0.0 closing connection c74sm3677627wme.1 - gsmtp) uid=0 username=root 
outbytes=691
  Jul  8 17:56:01 user-X751LAB CRON[15626]: (user) CMD 
(/home/user/Softs/alarm_bat.sh)
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
  [computer rebooted...]
  Jul  8 17:59:44 user-X751LAB rsyslogd: [origin software="rsyslogd" 
swVersion="8.16.0" x-pid="927" x-info="http://www.rsyslog.com;] start
  Jul  8 17:59:44 user-X751LAB rsyslogd-: command 
'KLogPermitNonKernelFacility' is currently not permitted - did you already set 
it via a RainerScript command (v6+ config)? [v8.16.0 try 
http://www.rsyslog.com/e/ ]
  Jul  8 17:59:44 user-X751LAB rsyslogd: rsyslogd's groupid changed to 109

  Jul  8 17:59:44 user-X751LAB sensors[1049]: Adapter: Virtual device
  Jul  8 17:59:44 user-X751LAB sensors[1049]: temp1:+42.0°C  (crit = 
+108.0°C)
  Jul  8 17:59:44 user-X751LAB sensors[1049]: temp2:+27.8°C  (crit = 
+105.0°C)
  Jul  8 17:59:44 user-X751LAB sensors[1049]: temp3:+29.8°C  (crit = 
+105.0°C)
  Jul  8 17:59:44 user-X751LAB sensors[1049]: coretemp-isa-
  Jul  8 17:59:44 user-X751LAB sensors[1049]: Adapter: ISA adapter
  Jul  8 17:59:44 user-X751LAB sensors[1049]: Physical id 0:  +45.0°C  (high = 
+105.0°C, crit = +105.0°C)
  Jul  8 17:59:44 user-X751LAB sensors[1049]: Core 0: +45.0°C  (high = 
+105.0°C, crit = +105.0°C)
  Jul  8 17:59:44 user-X751LAB sensors[1049]: Core 1: +45.0°C  (high = 
+105.0°C, crit = +105.0°C)

  Jul  8 17:59:51 user-X751LAB kernel: [   50.525061] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.526028] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.526578] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.527439] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.527866] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.528311] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.528739] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.529184] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.529588] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.530410] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.530827] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.530965] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.533857] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!
  Jul  8 17:59:51 user-X751LAB kernel: [   50.534398] [drm:gen8_irq_handler 
[i915]] *ERROR* The master control interrupt lied (SDE)!

  Jul  8 18:01:31 user-X751LAB kernel: [  151.296804] [ cut here 
]
  Jul  8 18:01:31 user-X751LAB kernel: [  151.296868] WARNING: CPU: 3 PID: 1095 
at /build/linux-HVWSXI/linux-4.2.0/drivers/gpu/drm/i915/intel_uncore.c:620 
hsw_unclaimed_reg_debug+0x6d/0x90 [i915]()
  Jul  8 18:01:31 user-X751LAB kernel: [  151.296871] 

[Kernel-packages] [Bug 1604310] Re: Plugging DisplayPort in L530 causes WiFi disconnection

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

Title:
  Plugging DisplayPort in L530 causes WiFi disconnection

Status in linux package in Ubuntu:
  Expired

Bug description:
  I connect running laptop to DisplayPort and wifi is going down (its
  not sending any packages, however the status is still connected for
  2-3 mins).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dawid  1918 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jul 19 10:38:28 2016
  HibernationDevice: RESUME=UUID=2d05849f-f06c-4368-88da-7c7e963ee647
  InstallationDate: Installed on 2015-08-10 (343 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 2478CK2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (85 days ago)
  dmi.bios.date: 10/14/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G3ETA2WW(2.62)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2478CK2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG3ETA2WW(2.62):bd10/14/2014:svnLENOVO:pn2478CK2:pvrThinkPadL530:rvnLENOVO:rn2478CK2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2478CK2
  dmi.product.version: ThinkPad L530
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1602238] Re: Boot hangs on 3.19 /4.2 backported kernels on Trusty

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

Title:
  Boot hangs on 3.19 /4.2 backported kernels on Trusty

Status in linux package in Ubuntu:
  Expired

Bug description:
  we have been trying to install 3.19 /4.2 kernels on our DELL machines
  after successful installation on boot the system simply doesn't boot
  to run level (see attachment where its stuck).Some machines of 4.2
  kernel suceed to boot and subsequent reboots fail and drops with the
  same error (See attachment)

  Isolated the issue to be out of grub since grub is able to be detected
  and boot from the mentioned identified device

  Isolated the issue to be out of initramfs since if the modules are
  missing it will not pass to the next stage of boot process

  Issue is seen in a boot stage before the kernel loads completely

  Same issue is not seen in virtual environment (KVM) since the device
  drivers that is needed to boot is completely different compared to the
  baremetals (DELL/HP) suspect something really messy with the ata,ide
  drivers that goes missing but too early to comment

  While booting to recovery mode it just drops to initramfs shell

  Could be possibly related to  #1308264 but i see none assigned to the
  BUG. Too many work arounds suggested in  #1308264 as well in internet
  nothing helped

  VERSION 14.04 (trusty) 
  Kernel Version 3.19 * 4.2 * 
  Works fine with lts-utopic

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

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

[Kernel-packages] [Bug 1603564] Re: USB unplug crashes system - Assuming host is dying, halting host

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

Title:
  USB unplug crashes system - Assuming host is dying, halting host

Status in linux package in Ubuntu:
  Expired

Bug description:
  Occasionally, when I unplug my Android phone (connected over USB), my machine 
crashes.
  At first, I presumed the entire machine had halted since the keyboard and 
mouse stopped working.
  However, I'm still able to SSH in although the screen is completely 
non-responsive. Pressing the power button on the CPU seems to bring up a window 
with Ubuntu's power options.

  My Ubuntu version:
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Codename: trusty

  Kernel version:
  Linux nixentor 3.13.0-91-generic #138-Ubuntu SMP Fri Jun 24 17:00:34 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  I see the following output on dmesg:
  [15563.650717] [ cut here ]
  [15563.650730] WARNING: CPU: 7 PID: 0 at 
/build/linux-3r7mVb/linux-3.13.0/drivers/usb/host/xhci-ring.c:1590 
handle_cmd_completion+0xe56/0xe60()
  [15563.650732] Modules linked in: qcserial usb_wwan usbserial ip6table_filter 
ip6_tables iptable_filter ip_tables x_tables cachefiles cfg80211 rfcomm bnep 
nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache snd_hda_codec_hdmi btusb 
bluetooth usb_storage mxm_wmi x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper cryptd uvcvideo videobuf2_vmalloc videobuf2_memops 
joydev videobuf2_core snd_hda_codec_realtek videodev snd_usb_audio 
snd_usbmidi_lib 8812au(OX) snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_hda_intel snd_hda_codec snd_seq serio_raw snd_hwdep radeon snd_pcm mei_me 
snd_page_alloc mei snd_seq_device snd_timer snd ttm drm_kms_helper soundcore 
drm parport_pc i2c_algo_bit ppdev lp wmi parport video intel_smartconnect 
shpchp acpi_pad mac_hid hid_generic usbhid hid e1000e ahci psmouse ptp libahci 
pps_core
  [15563.650804] CPU: 7 PID: 0 Comm: swapper/7 Tainted: G   OX 
3.13.0-91-generic #138-Ubuntu
  [15563.650807] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./Z97 Extreme4, BIOS P1.30 05/23/2014
  [15563.650809]   88041edc3d90 81729906 

  [15563.650813]  0009 88041edc3dc8 8106987d 
880404062d60
  [15563.650817]  8804040606b0 0010 0004040606b0 
8804041a
  [15563.650822] Call Trace:
  [15563.650824][] dump_stack+0x64/0x82
  [15563.650836]  [] warn_slowpath_common+0x7d/0xa0
  [15563.650840]  [] warn_slowpath_null+0x1a/0x20
  [15563.650845]  [] handle_cmd_completion+0xe56/0xe60
  [15563.650852]  [] ? check_preempt_curr+0x75/0xa0
  [15563.650857]  [] xhci_irq+0x33b/0xa50
  [15563.650861]  [] ? sched_clock_cpu+0xb5/0x100
  [15563.650865]  [] xhci_msi_irq+0x11/0x20
  [15563.650870]  [] handle_irq_event_percpu+0x4e/0x220
  [15563.650874]  [] handle_irq_event+0x3d/0x60
  [15563.650878]  [] handle_edge_irq+0x77/0x130
  [15563.650886]  [] handle_irq+0x1e/0x30
  [15563.650893]  [] do_IRQ+0x4d/0xc0
  [15563.650898]  [] common_interrupt+0x6d/0x6d
  [15563.650900][] ? cpuidle_enter_state+0x52/0xc0
  [15563.650910]  [] ? cpuidle_enter_state+0x48/0xc0
  [15563.650915]  [] cpuidle_idle_call+0xdc/0x220
  [15563.650921]  [] arch_cpu_idle+0xe/0x30
  [15563.650924]  [] cpu_startup_entry+0xc1/0x2b0
  [15563.650931]  [] start_secondary+0x21d/0x2d0
  [15563.650934] ---[ end trace d9b5447d0ddb440a ]---
  [15565.486066] xhci_hcd :00:14.0: xHCI host not responding to stop 
endpoint command.
  [15565.486075] xhci_hcd :00:14.0: Assuming host is dying, halting host.
  [15565.486120] xhci_hcd :00:14.0: HC died; cleaning up
  [15568.853140] xhci_hcd :00:14.0: Timeout while waiting for address 
device command
  [15568.853149] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15569.057055] usb 3-14: device not accepting address 92, error -108
  [15574.055575] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15574.055587] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15579.054167] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15579.054176] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15584.052706] xhci_hcd :00:14.0: Timeout while waiting for a slot
  [15584.052715] xhci_hcd :00:14.0: Abort the command ring, but the xHCI is 
dead.
  [15584.052841] usb 3-3: USB disconnect, device number 2
  [15584.052854] usb 3-3.2: USB disconnect, device number 13
  [15584.085404] usb 3-4: USB disconnect, device number 3
  [15584.108793] usb 3-6: USB disconnect, 

[Kernel-packages] [Bug 1606384] Re: Ubuntu does not boot with systemd

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

Title:
  Ubuntu does not boot with systemd

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu does not boot with systemd, it boots with upstart choice in
  grub.

  Workaround - alt+f1 during start and then start lightdm manually.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', 
'/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', 
'/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/midiC0D3', 
'/dev/snd/midiC0D2', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/midiC0D1', 
'/dev/snd/midiC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Mon Jul 25 23:52:19 2016
  HibernationDevice: RESUME=UUID=7b4a2bc3-8fd2-4684-b322-2c990980a5ac
  InstallationDate: Installed on 2015-12-13 (225 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MSI MS-7693
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=520db00b-7805-4f04-8c0c-31acfe536389 ro iommu=soft quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-03-21 (126 days ago)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970 GAMING (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0:
  dmi.product.name: MS-7693
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1607239] Re: mdadm raid gets frozen

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

Title:
  mdadm raid gets frozen

Status in linux package in Ubuntu:
  Expired

Bug description:
  Servers periodically became unresponsive, and report the following
  problem:

  Jul 28 01:26:36 osd1-05 kernel: [1644406.270794] kworker/12:2D 
88085fcd3180 0 25000  2 0x
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270813] Workqueue: dio/bdev 
dio_aio_complete_work
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270821]  88003694dc10 
0046 8805621b4800 00013180
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270830]  88003694dfd8 
00013180 8805621b4800 88003694dd38
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270836]  88003694dd40 
7fff 8805621b4800 a6fd7000
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270842] Call Trace:
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270857]  [] 
schedule+0x29/0x70
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270870]  [] 
schedule_timeout+0x279/0x310
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270880]  [] ? 
md_make_request+0xd5/0x220
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270889]  [] 
wait_for_completion+0xa6/0x150
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270900]  [] ? 
wake_up_state+0x20/0x20
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270906]  [] 
submit_bio_wait+0x5e/0x70
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270914]  [] 
blkdev_issue_flush+0x5a/0x90
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270919]  [] 
blkdev_fsync+0x35/0x50
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270928]  [] 
generic_write_sync+0x48/0x60
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270934]  [] 
dio_complete+0x103/0x120
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270939]  [] 
dio_aio_complete_work+0x21/0x30
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270948]  [] 
process_one_work+0x178/0x470
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270953]  [] ? 
manage_workers.isra.25+0x1f7/0x2e0
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270959]  [] 
worker_thread+0x121/0x410
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270964]  [] ? 
rescuer_thread+0x430/0x430
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270971]  [] 
kthread+0xc9/0xe0
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270976]  [] ? 
kthread_create_on_node+0x1c0/0x1c0
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270984]  [] 
ret_from_fork+0x58/0x90
  Jul 28 01:26:36 osd1-05 kernel: [1644406.270988]  [] ? 
kthread_create_on_node+0x1c0/0x1c0
  Jul 28 01:28:36 osd1-05 kernel: [1644526.317504] INFO: task 
kworker/12:2:25000 blocked for more than 120 seconds.
  Jul 28 01:28:36 osd1-05 kernel: [1644526.326399]   Not tainted 
3.13.0-87-generic #133-Ubuntu

  The actual raid configurations is:
  Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] 
[raid10]
  md0 : active raid1 sdb1[1] sda1[0]
937123648 blocks super 1.2 [2/2] [UU]

  md1 : active raid1 sdb2[1] sda2[0]
39473024 blocks super 1.2 [2/2] [UU]

  md60 : active raid6 sdw[0] sdz[3] sdaa[4] sdx[1] sdy[2]
585689088 blocks super 1.2 level 6, 512k chunk, algorithm 2 [5/5] 
[U]

  unused devices: 

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-87-generic 3.13.0-87.133
  ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-87-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 28 06:17 seq
   crw-rw 1 root audio 116, 33 Jul 28 06:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg: [   29.441344] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Thu Jul 28 07:33:28 2016
  HibernationDevice: RESUME=UUID=a049dacc-3f5b-4282-b507-24d3a7382389
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Supermicro SSG-6047R-E1R36L
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic 
root=UUID=7052bcbe-dccf-47e4-a7f7-a95a09176541 ro quiet 

[Kernel-packages] [Bug 1607006] Re: [Regression] latest kernel boots to distorted graphics (systemd) or does not boot at all (upstart)

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

Title:
  [Regression] latest kernel boots to distorted graphics (systemd) or
  does not boot at all (upstart)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Latest kernel boots to distorted graphics (systemd) or does not boot at all 
(upstart).
  Doesn't matter whether I use nouveau or nvidia drivers.
  Graphics is distorted even in tty

  Booting to kernel before that workarounds this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.4.0-31 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tomas  3017 F pulseaudio
   /dev/snd/controlC2:  tomas  3017 F pulseaudio
   /dev/snd/controlC0:  tomas  3017 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Jul 27 19:36:14 2016
  HibernationDevice: RESUME=UUID=7b4a2bc3-8fd2-4684-b322-2c990980a5ac
  InstallationDate: Installed on 2016-07-26 (1 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  MachineType: MSI MS-7693
  PackageArchitecture: all
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=2aaf2167-aca2-41be-b11e-930925090f92 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970 GAMING (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.4:bd12/21/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0:
  dmi.product.name: MS-7693
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1628309] [NEW] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

[Cristian Aravena Romero]

Public bug reported:

[0.020580] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[0.020581] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
Uname: Linux 4.8.0-17-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2141 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Sep 27 19:37:12 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (429 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.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-lowlatency N/A
 linux-backports-modules-4.8.0-17-lowlatency  N/A
 linux-firmware   1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
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.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

Status in linux package in Ubuntu:
  New

Bug description:
  [0.020580] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
  [0.020581] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:37:12 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 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.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1628309/+subscriptions

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

[Kernel-packages] [Bug 1628308] [NEW] PCCT header not found.

[Cristian Aravena Romero]

Public bug reported:

[0.114784] PCCT header not found.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
Uname: Linux 4.8.0-17-lowlatency x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caravena   2141 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Sep 27 19:34:08 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (429 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.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-17-lowlatency N/A
 linux-backports-modules-4.8.0-17-lowlatency  N/A
 linux-firmware   1.161
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
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.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  PCCT header not found.

Status in linux package in Ubuntu:
  New

Bug description:
  [0.114784] PCCT header not found.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19
  ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7
  Uname: Linux 4.8.0-17-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2141 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Sep 27 19:34:08 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (429 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.8.0-17-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-lowlatency N/A
   linux-backports-modules-4.8.0-17-lowlatency  N/A
   linux-firmware   1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1628308/+subscriptions

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

[Kernel-packages] [Bug 1626299] Re: ACPI Errors in dmesg, battery monitor shows empty

[Alberto Salvia Novella]

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

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

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

Title:
  ACPI Errors in dmesg, battery monitor shows empty

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Xubuntu, and the power manager show an empty battery at all
  times, regardless of battery level. I essentially have no indicators
  of how much power my laptop has left. Once I run out of power, the
  laptop obviously shuts down causing data corruption.

  my dmesg shows:

  [   10.587295] ACPI Error: No handler for Region [PMRG] (88015a0c0090) 
[GenericSerialBus] (20150930/evregion-163)
  [   10.587303] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20150930/exfldio-297)
  [   10.587309] ACPI Error: Method parse/execution failed [\_SB.TAMB._TMP] 
(Node 88015a0f7208), AE_NOT_EXIST (20150930/psparse-542)
  [   10.587325] thermal thermal_zone0: failed to read out thermal zone (-5)
  [   10.598876] ACPI Error: No handler for Region [PMRG] (88015a0c0090) 
[GenericSerialBus] (20150930/evregion-163)
  [   10.598882] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20150930/exfldio-297)
  [   10.598886] ACPI Error: Method parse/execution failed [\_SB.TEFN._TMP] 
(Node 88015a0f76e0), AE_NOT_EXIST (20150930/psparse-542)
  [   10.598898] thermal thermal_zone1: failed to read out thermal zone (-5)
  [   10.600460] ACPI Error: No handler for Region [PMRG] (88015a0c0090) 
[GenericSerialBus] (20150930/evregion-163)
  [   10.600465] ACPI Error: Region GenericSerialBus (ID=9) has no handler 
(20150930/exfldio-297)
  [   10.600469] ACPI Error: Method parse/execution failed [\_SB.TSKN._TMP] 
(Node 88015a0f94b0), AE_NOT_EXIST (20150930/psparse-542)
  [   10.600479] thermal thermal_zone2: failed to read out thermal zone (-5)

  later it shows:

  [   11.235601] acer_wmi: Enabling Launch Manager failed: 0xe4 - 0x0

  
  It's unfortunate to never know how much power is left, as one might imagine.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  coder  1607 F pulseaudio
   /dev/snd/controlC1:  coder  1607 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Sep 22 00:34:51 2016
  HibernationDevice: RESUME=UUID=c0846449-28bd-4d6a-9ccb-732cf1582f3a
  InstallationDate: Installed on 2016-09-08 (13 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Acer Aspire SW5-173
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Crepe
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd04/11/2016:svnAcer:pnAspireSW5-173:pvrV1.08:rvnAcer:rnCrepe:rvrV1.08:cvnAcer:ct9:cvrV1.08:
  dmi.product.name: Aspire SW5-173
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

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

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

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

[Brad Figg]

tests ran:   4, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-70.78~14.04.1/modoc__3.19.0-70.78~14.04.1__2016-09-27_23-00-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-70.78~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1625788
  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/1625794/+subscriptions

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

[Kernel-packages] [Bug 1624765] Re: wifi broke after 16.04 upgrade

[Alberto Salvia Novella]

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

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

Title:
  wifi broke after 16.04 upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded from ubuntu 14.04 LTS to ubuntu 16.04 LTS. My wifi was working 
fine in previous version. But, after upgrade wifi broke. It won't show any wifi 
networks and I couldn't enable wifi from ubuntu panel on top right corner. 
  I tried almost all suggestions in this page and few other askubuntu pages 
with same problem: 
  
http://askubuntu.com/questions/62166/siocsifflags-operation-not-possible-due-to-rf-kill
  But, nothing worked. 

  Here is my console output: 
  ~$ sudo rfkill list
  0: dell-rbtn: Wireless LAN
Soft blocked: yes
Hard blocked: yes
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  7: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

  Then, I ran "sudo rfkill unblock wifi" but that didn't fix anything.

  Finally, the only thing that worked was: 
  sudo modprobe -r dell-rbtn

  I don't even know if this is the right way to fix it. Please fix the
  16.04 kernel and OS upgrade package so that other users don't face
  this problem that cost me 2 days. Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Sat Sep 17 15:13:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-19 (29 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  parag  3685 F pulseaudio
   /dev/snd/controlC1:  parag  3685 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=bad8d93e-83c4-40c0-aa97-00ac6c4e373e
  InstallationDate: Installed on 2016-08-19 (38 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 3542
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=206733db-103a-4078-847b-0a897121325e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 02RD2H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn02RD2H:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1626283] Re: lenovo t420s very slow wifi after dist upgrade 14-16

[Alberto Salvia Novella]

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

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

Title:
  lenovo t420s very slow wifi after dist upgrade 14-16

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  it is not more than 2 mbit\s for the moment - before upgrade it works well - 
about 40-50 mbit\s.
  it is not ISP issue other devices works fast at my wifi network

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.16
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Sep 22 00:29:18 2016
  InstallationDate: Installed on 2015-12-17 (279 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-08-17 (35 days ago)
  VarLogDistupgradeTermlog:

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

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

[Kernel-packages] [Bug 1626460] Re: usb-devices | awk '/13d3/' RS=

[Alberto Salvia Novella]

Please:

1. Edit the description so it explains the steps to reproduce the bug,
and what are the consequences of it.

2. Set status back to "confirmed".

Thank you.

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

Title:
  usb-devices | awk '/13d3/' RS=

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  usb-devices | awk '/13d3/' RS=

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  studik 1697 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep 22 12:39:12 2016
  HibernationDevice: RESUME=UUID=56c1e43e-2a1f-4066-b572-bb690c40d0cd
  InstallationDate: Installed on 2016-09-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: Matsushita Electric Industrial Co.,Ltd. CF-19CHD07BE
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2007
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V1.00L14
  dmi.board.name: CF19-1
  dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.board.version: 001
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV1.00L14:bd07/12/2007:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-19CHD07BE:pvr001:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF19-1:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
  dmi.product.name: CF-19CHD07BE
  dmi.product.version: 001
  dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

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

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

[Kernel-packages] [Bug 1626517] Re: Access to some folders hangs and in dmesg see kernel BUG report

[Alberto Salvia Novella]

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

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

Title:
  Access to some folders hangs and in dmesg see kernel BUG report

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Probably freeze during access to folder caused by 
  kernel BUG at /build/linux-BvkamA/linux-4.4.0/fs/namei.c:2562!

  Also segfault during collecting information with 'ubuntu-bug linux', but not 
sure it is related:
  [80059.937844] apport-kde[22602]: segfault at 7fdb0f1d4b00 ip 
7fdb44cd40f5 sp 7ffd35400828 error 4 in 
QtCore.cpython-35m-x86_64-linux-gnu.so[7fdb44ae4000+268000]
  [80099.437691] Qt bearer threa[23986]: segfault at 7f23b89942e9 ip 
7f23b3d41ccb sp 7f239fffce50 error 4 in 
libgcc_s.so.1[7f23b3d33000+16000]
  It is looks like separate issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vadim  4045 F pulseaudio
   /dev/snd/controlC0:  vadim  4045 F pulseaudio
  Date: Thu Sep 22 13:52:19 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=4ff5857a-eca8-4968-9e7d-16cb2b146f60
  InstallationDate: Installed on 2015-04-28 (512 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=f0d3e2ee-9f79-431c-9d8a-1079d7638279 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (152 days ago)
  dmi.bios.date: 08/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1002
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1002:bd08/12/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1626679] Re: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!"

[Alberto Salvia Novella]

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

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

Title:
  NVMe triggering kernel panic followed by "bad: scheduling from the
  idle thread!"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger
  off a kernel panic against somepart of the NVMe driver it looks like,
  after which the logs get filled with entries over and over again of:

  "bad: scheduling from the idle thread!"

  Here's the initial stack trace that seems to trigger off the bug:

  Sep 22 15:51:46 ubuntu kernel: [   97.478175] [ cut here 
]
  Sep 22 15:51:46 ubuntu kernel: [   97.478185] WARNING: CPU: 13 PID: 0 at 
/build/linux-dcxD3m/linux-4.4.0/kernel/irq/manage.c:1438 
__free_irq+0x1d2/0x280()
  Sep 22 15:51:46 ubuntu kernel: [   97.478188] Trying to free IRQ 38 from IRQ 
context!
  Sep 22 15:51:46 ubuntu kernel: [   97.478191] Modules linked in: 
nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm irqbypass ioatdma me
  i_me sb_edac shpchp edac_core lpc_ich mei 8250_fintek ipmi_msghandler mac_hid 
ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr autofs4 btrfs 
iscsi_tcp libiscsi_tcp libiscsi
  scsi_transport_iscsi raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
crct10dif_pclmul ixgbe crc32_pclmu
  l dca vxlan aesni_intel ip6_udp_tunnel udp_tunnel aes_x86_64 lrw gf128mul ptp 
glue_helper ahci ablk_helper pps_core cryptd nvme libahci mdio wmi fjes
  Sep 22 15:51:46 ubuntu kernel: [   97.478257] CPU: 13 PID: 0 Comm: swapper/13 
Not tainted 4.4.0-31-generic #50-Ubuntu
  Sep 22 15:51:46 ubuntu kernel: [   97.478260] Hardware name: Oracle 
Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30080100 04/13/2016
  Sep 22 15:51:46 ubuntu kernel: [   97.478263]  0286 
4fea3140a01056a3 883f7f743b10 813f1143
  Sep 22 15:51:46 ubuntu kernel: [   97.478267]  883f7f743b58 
81cb61f8 883f7f743b48 81081102
  Sep 22 15:51:46 ubuntu kernel: [   97.478271]  0026 
883f5b2ea700 0026 
  Sep 22 15:51:46 ubuntu kernel: [   97.478275] Call Trace:
  Sep 22 15:51:46 ubuntu kernel: [   97.478277][] 
dump_stack+0x63/0x90
  Sep 22 15:51:46 ubuntu kernel: [   97.478290]  [] 
warn_slowpath_common+0x82/0xc0
  Sep 22 15:51:46 ubuntu kernel: [   97.478294]  [] 
warn_slowpath_fmt+0x5c/0x80
  Sep 22 15:51:46 ubuntu kernel: [   97.478299]  [] ? 
try_to_grab_pending+0xb3/0x160
  Sep 22 15:51:46 ubuntu kernel: [   97.478302]  [] 
__free_irq+0x1d2/0x280
  Sep 22 15:51:46 ubuntu kernel: [   97.478306]  [] 
free_irq+0x3c/0x90
  Sep 22 15:51:46 ubuntu kernel: [   97.478314]  [] 
nvme_suspend_queue+0x89/0xb0 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478320]  [] 
nvme_disable_admin_queue+0x27/0x90 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478325]  [] 
nvme_dev_disable+0x29e/0x2c0 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478330]  [] ? 
__nvme_process_cq+0x210/0x210 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478334]  [] ? 
dev_warn+0x6c/0x90
  Sep 22 15:51:46 ubuntu kernel: [   97.478340]  [] 
nvme_timeout+0x110/0x1d0 [nvme]
  Sep 22 15:51:46 ubuntu kernel: [   97.478344]  [] ? 
cpumask_next_and+0x2f/0x40
  Sep 22 15:51:46 ubuntu kernel: [   97.478348]  [] ? 
load_balance+0x18c/0x980
  Sep 22 15:51:46 ubuntu kernel: [   97.478354]  [] 
blk_mq_rq_timed_out+0x2f/0x70
  Sep 22 15:51:46 ubuntu kernel: [   97.478358]  [] 
blk_mq_check_expired+0x4e/0x80
  Sep 22 15:51:46 ubuntu kernel: [   97.478363]  [] 
bt_for_each+0xd8/0xe0
  Sep 22 15:51:46 ubuntu kernel: [   97.478367]  [] ? 
blk_mq_rq_timed_out+0x70/0x70
  Sep 22 15:51:46 ubuntu kernel: [   97.478370]  [] ? 
blk_mq_rq_timed_out+0x70/0x70
  Sep 22 15:51:46 ubuntu kernel: [   97.478375]  [] 
blk_mq_queue_tag_busy_iter+0x47/0xc0
  Sep 22 15:51:46 ubuntu kernel: [   97.478379]  [] ? 
blk_mq_attempt_merge+0xb0/0xb0
  Sep 22 15:51:46 ubuntu kernel: [   97.478383]  [] 
blk_mq_rq_timer+0x41/0xf0
  Sep 22 15:51:46 ubuntu kernel: [   97.478389]  [] 
call_timer_fn+0x35/0x120
  Sep 22 15:51:46 ubuntu kernel: [   97.478393]  [] ? 
blk_mq_attempt_merge+0xb0/0xb0
  Sep 22 15:51:46 ubuntu kernel: [   97.478397]  [] 
run_timer_softirq+0x23a/0x2f0
  Sep 22 15:51:46 ubuntu kernel: [   97.478403]  [] 
__do_softirq+0x101/0x290
  Sep 22 15:51:46 ubuntu kernel: [   97.478407]  [] 
irq_exit+0xa3/0xb0
  Sep 22 15:51:46 ubuntu kernel: [   97.478413]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Sep 22 15:51:46 ubuntu kernel: [   97.478417]  [] 
apic_timer_interrupt+0x82/0x90
  Sep 22 15:51:46 ubuntu kernel: [   97.478419][] ? 
cpuidle_enter_state+0x111/0x2b0
  Sep 22 15:51:46 ubuntu kernel: [   97.478428]  [] 

[Kernel-packages] [Bug 1626413] Re: My laptop doesn't resume when lid is opended

[Alberto Salvia Novella]

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

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

Title:
  My laptop doesn't resume when lid is opended

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have HP ProBook 440 G3.

  my cat > /proc/acpi/wakeup

  DeviceS-state   Status   Sysfs node
  PEG1S4*disabled
  PEGPS4*disabled
  PEG2S4*disabled
  PEGPS4*disabled
  PEG0S4*disabled
  PEGPS4*disabled
  GLANS4*disabled
  XHC S3*enabled   pci::00:14.0
  XDCIS4*disabled
  HDASS4*disabled  pci::00:1f.3
  RP01S4*disabled
  PXSXS4*disabled
  RP02S4*disabled
  PXSXS4*disabled
  RP03S4*disabled
  PXSXS4*disabled
  RP04S4*disabled
  PXSXS4*disabled
  RP05S4*disabled  pci::00:1c.0
  PXSXS4*disabled  pci::01:00.0
  RP06S4*disabled  pci::00:1c.5
  PXSXS4*disabled  pci::02:00.0
  RP07S4*disabled
  PXSXS4*disabled
  RP08S4*disabled
  PXSXS4*disabled
  RP09S4*disabled  pci::00:1d.0
  PXSXS4*disabled  pci::03:00.0
*disabled  platform:rtsx_pci_sdmmc.0
*disabled  platform:rtsx_pci_ms.0
  RP10S4*disabled
  PXSXS4*disabled
  RP11S4*disabled
  PXSXS4*disabled
  RP12S4*disabled
  PXSXS4*disabled
  RP13S4*disabled
  PXSXS4*disabled
  RP14S4*disabled
  PXSXS4*disabled
  RP15S4*disabled
  PXSXS4*disabled
  RP16S4*disabled
  PXSXS4*disabled
  RP17S4*disabled
  PXSXS4*disabled
  RP18S4*disabled
  PXSXS4*disabled
  RP19S4*disabled
  PXSXS4*disabled
  RP20S4*disabled
  PXSXS4*disabled

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lyan   3843 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep 22 10:04:32 2016
  HibernationDevice: RESUME=UUID=fea7db5f-a686-450a-954f-0b89f08b946f
  InstallationDate: Installed on 2016-08-25 (28 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP ProBook 440 G3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=eff3796a-2b2f-4f3a-8754-f446ddb32a9e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.09
  dmi.board.name: 8100
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 40.03
  dmi.chassis.asset.tag: 5CD6228X27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.09:bd03/10/2016:svnHP:pnHPProBook440G3:pvr:rvnHP:rn8100:rvrKBCVersion40.03:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 440 G3
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1626689] Re: During boot process, system goes to sleep

[Alberto Salvia Novella]

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

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

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

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

Title:
  During boot process, system goes to sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04, my computer goes to sleep during the boot process, 
shortly after I entered the passphrase to unlock my LVM. When I wake it up, I’m 
at the graphical login prompt. I type my user password, press enter and it goes 
to sleep again. When I wake it up, I’m in my working Lubuntu desktop. This 
happens every time I boot. And it’s quite annoying.
  Please tell me which additional information I can provide to help fix this 
bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steffi 2155 F lxpanel
  CurrentDesktop: LXDE
  Date: Thu Sep 22 20:24:31 2016
  HibernationDevice: RESUME=UUID=9e305c00-cee8-4703-9352-abc5fb755282
  InstallationDate: Installed on 2016-09-21 (1 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  MachineType: Acer Aspire one
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-09-22 (0 days ago)
  dmi.bios.date: 02/20/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire one
  dmi.board.vendor: Acer
  dmi.board.version: V1.05
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd02/20/2009:svnAcer:pnAspireone:pvrV1.05:rvnAcer:rnAspireone:rvrV1.05:cvnAcer:ct1:cvrV1.05:
  dmi.product.name: Aspire one
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

[scotte]

I tested this using my reproduction method in AWS EC2 with a test
package/PPA provided by Eric@Ubuntu (slashd) containing the commit
referenced in comment #6.

All looks good now - systemd units for ZFS no longer fail. Thanks for
moving this along!

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd - 
  sudo systemctl --failed 
  UNIT LOAD ACTIVE SUB DESCRIPTION 
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning 
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems 

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it. 
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   *
   
  [Other Info]
   
   * This can likely be resolved in the systemd init scripts, by modifying 
zfs-linux to depend on /proc/mounts instead, or inclusion of 
/lib/init/mount-functions.sh in initscripts (sysvinit).

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

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

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

[Brad Figg]

*** This bug is a duplicate of bug 1628204 ***
https://bugs.launchpad.net/bugs/1628204

tests ran:  35, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-40.60/dwalin__4.4.0-40.60__2016-09-27_23-36-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/1627074

Title:
  linux: 4.4.0-40.60 -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 verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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