[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[Eduardo Montes de Oca Sanchez]

I have de same issue. I Have an HP Star Wars Special Edition 15-an050nr:

edrendar@outrider-HP-Pavilion-Notebook:~$ tail -f /var/log/syslog 
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778017] pcieport 
:00:1c.5: AER: Corrected error received: id=00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778028] pcieport 
:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, 
id=00e5(Receiver ID)
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778032] pcieport 
:00:1c.5:   device [8086:9d15] error status/mask=0001/2000
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778035] pcieport 
:00:1c.5:[ 0] Receiver Error (First)
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778041] pcieport 
:00:1c.5: AER: Corrected error received: id=00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778151] pcieport 
:00:1c.5: can't find device of ID00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778296] pcieport 
:00:1c.5: AER: Corrected error received: id=00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778307] pcieport 
:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, 
id=00e5(Receiver ID)
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778310] pcieport 
:00:1c.5:   device [8086:9d15] error status/mask=0001/2000
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.778313] pcieport 
:00:1c.5:[ 0] Receiver Error (First)
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.877828] pcieport 
:00:1c.5: AER: Corrected error received: id=00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.877853] pcieport 
:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, 
id=00e5(Receiver ID)
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.877864] pcieport 
:00:1c.5:   device [8086:9d15] error status/mask=0001/2000
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.877872] pcieport 
:00:1c.5:[ 0] Receiver Error
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.877885] pcieport 
:00:1c.5: AER: Corrected error received: id=00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.878542] pcieport 
:00:1c.5: can't find device of ID00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.878562] pcieport 
:00:1c.5: AER: Corrected error received: id=00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.878587] pcieport 
:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, 
id=00e5(Receiver ID)
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.878594] pcieport 
:00:1c.5:   device [8086:9d15] error status/mask=0001/2000
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.878600] pcieport 
:00:1c.5:[ 0] Receiver Error
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.878611] pcieport 
:00:1c.5: AER: Corrected error received: id=00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.879259] pcieport 
:00:1c.5: can't find device of ID00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.879283] pcieport 
:00:1c.5: AER: Corrected error received: id=00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.879307] pcieport 
:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, 
id=00e5(Receiver ID)
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.879314] pcieport 
:00:1c.5:   device [8086:9d15] error status/mask=0001/2000
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.879319] pcieport 
:00:1c.5:[ 0] Receiver Error
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.879331] pcieport 
:00:1c.5: AER: Corrected error received: id=00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.880003] pcieport 
:00:1c.5: can't find device of ID00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.880009] pcieport 
:00:1c.5: AER: Corrected error received: id=00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.880032] pcieport 
:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, 
id=00e5(Receiver ID)
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.880039] pcieport 
:00:1c.5:   device [8086:9d15] error status/mask=0001/2000
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.880044] pcieport 
:00:1c.5:[ 0] Receiver Error
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.880056] pcieport 
:00:1c.5: AER: Corrected error received: id=00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.880709] pcieport 
:00:1c.5: can't find device of ID00e5
Nov  8 23:43:47 outrider-HP-Pavilion-Notebook kernel: [ 7275.880823] pcieport 
:00:1c.5: AER: Corrected 

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

[Hui Wang]

Then please dump coefficient as #29, I will send it to realtek's
engineer and let them have a look.

thx.

-- 
You 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 1621474] Re: VLAN creation fails with VF multi queueuing

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

Title:
  VLAN creation fails with VF multi queueuing

Status in linux package in Ubuntu:
  Expired

Bug description:
  Description
  

  It can be read in SR-IOV companion guide that 82599 chipsets :

  * The 82599 has 128 Transmit and 128 Receive queues. They are generally 
referred to/thought of as queue pairs (1 Transmit and 1 Receive queue). This 
gives the 82599 128 queue pairs.
  * The 82599 has up to 64 pools, with each pool having two queue pairs in 
it. That is two Transmit and Receive queue assigned to each VF.
  * The 82599 allows for a variable configuration for the number of pools. 
In SR-IOV mode, there can be 16, 32 or 64 pools.

  The last line suggest using combined queues of 2, 4 and 8.

  The only way, for now we found, is using tc on the host especially as the 
ethtool command is not supported (ethtool -L eth10 combined 8 for example).
  And, with following command "tc qdisc add dev eth10 root mqprio num_tc 8", we 
will be able to use up to 8 combined queues on the host PF and guests which are 
using VFs.
  Yet, with 8 combined queues with tc commnad, VLAN creation was not permitted.

  Following driver versions have been used on host and guest to enable this 
multiqueue option:
* 4.3.15 ixgbe in the host
* 3.1.2  ixgbevf in the guest

  To reproduce
  -

  On the host side
  

  root@ubuntu1404:~# rmmod ixgbe
  root@ubuntu1404:~# modprobe ixgbe
  [ 4817.027637] ixgbe :05:00.0: failed to load because an unsupported SFP+ 
or QSFP module type was detected.
  [ 4817.038630] ixgbe :05:00.0: Reload the driver after installing a 
supported module.
  [ 4817.418360] ixgbe :41:00.1: failed to load because an unsupported SFP+ 
or QSFP module type was detected.
  [ 4817.429354] ixgbe :41:00.1: Reload the driver after installing a 
supported module.
  [ 4817.838086] ixgbe :43:00.0: failed to load because an unsupported SFP+ 
or QSFP module type was detected.
  [ 4817.849091] ixgbe :43:00.0: Reload the driver after installing a 
supported module.
  [ 4817.889189] ixgbe :43:00.1: failed to load because an unsupported SFP+ 
or QSFP module type was detected.
  [ 4817.900178] ixgbe :43:00.1: Reload the driver after installing a 
supported module.
  [ 4817.940318] ixgbe :44:00.0: failed to load because an unsupported SFP+ 
or QSFP module type was detected.
  [ 4817.951357] ixgbe :44:00.0: Reload the driver after installing a 
supported module.
  root@ubuntu1404:~# modinfo ixgbe
  filename:   
/lib/modules/3.13.0-91-generic/updates/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.3.15
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver
  author: Intel Corporation, 
  srcversion: 7AED484083B2C5B86424A3A
  alias:  pci:v8086d15ADsv*sd*bc*sc*i*
  alias:  pci:v8086d15ACsv*sd*bc*sc*i*
  alias:  pci:v8086d15ABsv*sd*bc*sc*i*
  alias:  pci:v8086d15AAsv*sd*bc*sc*i*
  alias:  pci:v8086d15D1sv*sd*bc*sc*i*
  alias:  pci:v8086d1563sv*sd*bc*sc*i*
  alias:  pci:v8086d1560sv*sd*bc*sc*i*
  alias:  pci:v8086d1558sv*sd*bc*sc*i*
  alias:  pci:v8086d154Asv*sd*bc*sc*i*
  alias:  pci:v8086d1557sv*sd*bc*sc*i*
  alias:  pci:v8086d154Fsv*sd*bc*sc*i*
  alias:  pci:v8086d154Dsv*sd*bc*sc*i*
  alias:  pci:v8086d1528sv*sd*bc*sc*i*
  alias:  pci:v8086d10F8sv*sd*bc*sc*i*
  alias:  pci:v8086d151Csv*sd*bc*sc*i*
  alias:  pci:v8086d1529sv*sd*bc*sc*i*
  alias:  pci:v8086d152Asv*sd*bc*sc*i*
  alias:  pci:v8086d10F9sv*sd*bc*sc*i*
  alias:  pci:v8086d1514sv*sd*bc*sc*i*
  alias:  pci:v8086d1507sv*sd*bc*sc*i*
  alias:  pci:v8086d10FBsv*sd*bc*sc*i*
  alias:  pci:v8086d1517sv*sd*bc*sc*i*
  alias:  pci:v8086d10FCsv*sd*bc*sc*i*
  alias:  pci:v8086d10F7sv*sd*bc*sc*i*
  alias:  pci:v8086d1508sv*sd*bc*sc*i*
  alias:  pci:v8086d10DBsv*sd*bc*sc*i*
  alias:  pci:v8086d10F4sv*sd*bc*sc*i*
  alias:  pci:v8086d10E1sv*sd*bc*sc*i*
  alias:  pci:v8086d10F1sv*sd*bc*sc*i*
  alias:  pci:v8086d10ECsv*sd*bc*sc*i*
  alias:  pci:v8086d10DDsv*sd*bc*sc*i*
  alias:  pci:v8086d150Bsv*sd*bc*sc*i*
  alias:  pci:v8086d10C8sv*sd*bc*sc*i*
  alias:  

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

[MIFAS]

Windows is detecting audio jack, so why ubuntu can't detect?. BTW
Sometimes In ubuntu, audio jack is detecting. Don't say this is laptop
issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1447909] Re: external mic not detected on machines with alc256 codec

[Hui Wang]

They are different, on Dell laptop, the audio jack can detect the
headphone plug/unplug, this is the pre-condition for fixing the headset-
mic problem.

But on your Asus laptop, the audio jack can't detect any plug/unplug, so
even apply the same fix to this machine it will not work.

-- 
You 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 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled

[James Agnew]

I am seeing the same issue with Kernel 4.8.0-26-generic #28-Ubuntu SMP
Tue Oct 18 14:39:52 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Workaround as reported in the orinal description also clears it for me

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

Title:
  Seagate external drive causes SCSI bus resets when UAS enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes
  continuous SCSI bus resets by default. As a workaround, disabling UAS
  causes the device to work fine.

  To disable UAS, I created a file in /etc/modprobe.d with the following 
contents:
  options usb-storage quirks=0bc2:02322:u

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sun May 22 22:02:26 2016
  InstallationDate: Installed on 2012-10-07 (1323 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago)

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

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

[Kernel-packages] [Bug 1632527] Re: [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid close/open

[AceLan Kao]

The patch has CC'ed stable, so it won't affect the release with kernel
newer than 4.6

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: hwe-next
   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/1632527

Title:
  [Dell][XPS]Touchscreen fails to function after resume from s3 by Lid
  close/open

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Touchscreen fails to function after resume from s3 by Lid close/open

  Suspend from power menu/ power button cannot reproduce this issue

  Steps:
  1. Install ubuntu 16.04 and boot to OS
  2. suspend the system by Lid close action
  3. resume the session by Lid open
  4. check if touchscreen function works

  Expected results: Touchscreen should still works after Lid open

  Actual results: Touchscreen fails to work after lid open

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

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

[Kernel-packages] [Bug 1640200] Re: 16.10 hangs on shutdown

[David]

please see attached screen shot. not sure if related. please advise.
Thanks,

David


** Attachment added: "Bug photo: screenshot  I get while booting! not sure if 
related"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640200/+attachment/4774681/+files/20161108_191726.jpg

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

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

[David]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1640200/+attachment/4774675/+files/ProcModules.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

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

[David]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1640200/+attachment/4774676/+files/PulseList.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

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

[David]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1640200/+attachment/4774677/+files/UdevDb.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

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

[David]

apport information

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

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

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

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

[David]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1640200/+attachment/4774669/+files/JournalErrors.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1640200] IwConfig.txt

[David]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1640200/+attachment/4774668/+files/IwConfig.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1640200] ProcEnviron.txt

[David]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1640200/+attachment/4774673/+files/ProcEnviron.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

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

[David]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1640200/+attachment/4774667/+files/CurrentDmesg.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

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

[David]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1640200/+attachment/4774671/+files/Lsusb.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

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

[David]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1640200/+attachment/4774674/+files/ProcInterrupts.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

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

[David]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1640200/+attachment/4774672/+files/ProcCpuinfo.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

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

[David]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1640200/+attachment/4774670/+files/Lspci.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

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

[David]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1640200/+attachment/4774666/+files/CRDA.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: Rev.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
  dmi.product.name: M-1629
  dmi.product.version: 3409925R
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1640200] Re: 16.10 hangs on shutdown

[David]

apport information

** Tags added: apport-collected yakkety

** Description changed:

  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
+ --- 
+ ApportVersion: 2.20.3-0ubuntu8
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
+  /dev/snd/controlC1:  david 22172 F pulseaudio
+  /dev/snd/controlC0:  david 22172 F pulseaudio
+  /dev/snd/controlC2:  david 22172 F pulseaudio
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 16.10
+ HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
+ InstallationDate: Installed on 2016-11-03 (5 days ago)
+ InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
+ MachineType: Gateway M-1629
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
+ ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
+ RelatedPackageVersions:
+  linux-restricted-modules-4.8.0-26-lowlatency N/A
+  linux-backports-modules-4.8.0-26-lowlatency  N/A
+  linux-firmware   1.161
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  yakkety
+ Uname: Linux 4.8.0-26-lowlatency x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/23/2008
+ dmi.bios.vendor: Phoenix Technologies LTD
+ dmi.bios.version: 9D.05
+ dmi.board.vendor: Gateway
+ dmi.board.version: 9D.05
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Gateway
+ dmi.chassis.version: Rev.1
+ dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr9D.05:bd05/23/2008:svnGateway:pnM-1629:pvr3409925R:rvnGateway:rn:rvr9D.05:cvnGateway:ct8:cvrRev.1:
+ dmi.product.name: M-1629
+ dmi.product.version: 3409925R
+ dmi.sys.vendor: Gateway

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1640200/+attachment/4774665/+files/AlsaInfo.txt

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   david 22172 F...m pulseaudio
   /dev/snd/controlC1:  david 22172 F pulseaudio
   /dev/snd/controlC0:  david 22172 F pulseaudio
   /dev/snd/controlC2:  david 22172 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=7ede9358-a634-4d7a-ba7f-6f3ef9e433bb
  InstallationDate: Installed on 2016-11-03 (5 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Gateway M-1629
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-lowlatency 
root=UUID=60158545-3519-4bb6-8178-79f862ba7f87 ro recovery nomodeset
  ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-lowlatency N/A
   linux-backports-modules-4.8.0-26-lowlatency  N/A
   linux-firmware   1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-26-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 9D.05
  dmi.board.vendor: Gateway
  dmi.board.version: 9D.05
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 8
  

[Kernel-packages] [Bug 1639506] Re: panic in i915

[Mike Brookes]

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

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

Title:
  panic in i915

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux myhost 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:05 UTC
  2016 i686 i686 i686 GNU/Linux

  syslog:
  Nov  5 21:15:45 myhost kernel: [   53.532149] [ cut here 
]
  Nov  5 21:15:45 myhost kernel: [   53.532252] WARNING: CPU: 0 PID: 369 at 
/build/linux-LfgES4/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12744 
intel_modeset_check_state+0x556/0x910 [i915]()
  Nov  5 21:15:45 myhost kernel: [   53.532257] encoder's enabled state 
mismatch (expected 0, found 1)
  Nov  5 21:15:45 myhost kernel: [   53.532261] Modules linked in: xt_tcpudp 
xt_conntrack iptable_filter ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables 
x_tables gpio_ich snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
ppdev snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event coretemp snd_rawmidi ax88179_178a lpc_ich serio_raw snd_seq 
usbnet snd_seq_device snd_timer snd shpchp soundcore parport_pc 8250_fintek 
mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi lp parport autofs4 btrfs raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear i915 ahci psmouse r8169 libahci 
i2c_algo_bit drm_kms_helper pata_acpi syscopyarea sysfillrect sysimgblt 
fb_sys_fops drm mii fjes video
  Nov  5 21:15:45 myhost kernel: [   53.532402] CPU: 0 PID: 369 Comm: 
kworker/0:2 Tainted: GW   4.4.0-45-generic #66-Ubuntu
  Nov  5 21:15:45 myhost kernel: [   53.532406] Hardware name:  
/D945GSEJT , BIOS JT94510H.86A.0025.2009.0306.1639 03/06/2009
  Nov  5 21:15:45 myhost kernel: [   53.532432] Workqueue: events 
output_poll_execute [drm_kms_helper]
  Nov  5 21:15:45 myhost kernel: [   53.532438]  c1acf967 c1e2b340 0286 
f15d1d20 c13a745f f15d1d60 f89d68b8 f15d1d50
  Nov  5 21:15:45 myhost kernel: [   53.532451]  c1070307 f89d89c8 f15d1d80 
0171 f89d68b8 31c8 f896b696 f896b696
  Nov  5 21:15:45 myhost kernel: [   53.532463]  f58bc5d8 f5b6ea80 f58bc5e4 
f15d1d6c c107037e 0009 f15d1d60 f89d89c8
  Nov  5 21:15:45 myhost kernel: [   53.532475] Call Trace:
  Nov  5 21:15:45 myhost kernel: [   53.532488]  [] 
dump_stack+0x58/0x79
  Nov  5 21:15:45 myhost kernel: [   53.532498]  [] 
warn_slowpath_common+0x87/0xc0
  Nov  5 21:15:45 myhost kernel: [   53.532585]  [] ? 
intel_modeset_check_state+0x556/0x910 [i915]
  Nov  5 21:15:45 myhost kernel: [   53.532667]  [] ? 
intel_modeset_check_state+0x556/0x910 [i915]
  Nov  5 21:15:45 myhost kernel: [   53.532674]  [] 
warn_slowpath_fmt+0x3e/0x60
  Nov  5 21:15:45 myhost kernel: [   53.532757]  [] 
intel_modeset_check_state+0x556/0x910 [i915]
  Nov  5 21:15:45 myhost kernel: [   53.532841]  [] 
intel_atomic_commit+0x4cd/0x6a0 [i915]
  Nov  5 21:15:45 myhost kernel: [   53.532894]  [] ? 
drm_atomic_check_only+0x1ae/0x600 [drm]
  Nov  5 21:15:45 myhost kernel: [   53.532943]  [] ? 
drm_modeset_lock+0x49/0xd0 [drm]
  Nov  5 21:15:45 myhost kernel: [   53.532994]  [] 
drm_atomic_commit+0x32/0x60 [drm]
  Nov  5 21:15:45 myhost kernel: [   53.533020]  [] 
restore_fbdev_mode+0x253/0x290 [drm_kms_helper]
  Nov  5 21:15:45 myhost kernel: [   53.533070]  [] ? 
drm_modeset_lock_all_ctx+0x94/0xb0 [drm]
  Nov  5 21:15:45 myhost kernel: [   53.533096]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x27/0x70 [drm_kms_helper]
  Nov  5 21:15:45 myhost kernel: [   53.533121]  [] 
drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper]
  Nov  5 21:15:45 myhost kernel: [   53.533146]  [] 
drm_fb_helper_hotplug_event+0xcc/0x120 [drm_kms_helper]
  Nov  5 21:15:45 myhost kernel: [   53.533229]  [] 
intel_fbdev_output_poll_changed+0x1a/0x20 [i915]
  Nov  5 21:15:45 myhost kernel: [   53.533252]  [] 
drm_kms_helper_hotplug_event+0x21/0x30 [drm_kms_helper]
  Nov  5 21:15:45 myhost kernel: [   53.533276]  [] 
output_poll_execute+0x188/0x1c0 [drm_kms_helper]
  Nov  5 21:15:45 myhost kernel: [   53.533285]  [] 
process_one_work+0x121/0x3f0
  Nov  5 21:15:45 myhost kernel: [   53.533292]  [] 
worker_thread+0x20a/0x490
  Nov  5 21:15:45 myhost kernel: [   53.533300]  [] ? 
process_one_work+0x3f0/0x3f0
  Nov  5 21:15:45 myhost kernel: [   53.533306]  [] kthread+0xa6/0xc0
  Nov  5 21:15:45 myhost kernel: [   53.533315]  [] 
ret_from_kernel_thread+0x21/0x38
  Nov  5 21:15:45 myhost kernel: [   53.533321]  [] ? 
kthread_create_on_node+0x170/0x170
  Nov  5 21:15:45 myhost kernel: [   53.533327] ---[ end trace 361aeae89ccf24ea 
]---

To manage notifications about this bug go to:

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

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

Title:
  16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab.
  Boots fine in 4.4.0-42-generic and older

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System hangs during boot with 4.4.0-45-generic if /etc/crypptab
  contains a valid entry. Passphrase prompt never seen. Black screen
  with blinking underscore in upper left corner. Repeated attempts to
  type passphrase have no effect.

  There are two workarounds:
  1) Comment out line referring the encrypted partition in /etc/crypttab and 
/etc/fstab. Mount the partition manually after boot completes
  2) Boot in 4.4.0-42-generic which works as do earlier versions. i.e. the user 
provides passphrase at the prompt during boot and the system finishes booting

  robert@kalymnos:~$ cat /etc/crypttab
  spare2 UUID=498b08bb-5e6b-4ddf-8b37-e059665a34e6 none luks
  robert@kalymnos:~$ grep mapper /etc/fstab
  /dev/mapper/spare2/spare2 ext4 defaults 0 2

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

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

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

[bugproxy]

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

--- Comment From cdead...@us.ibm.com 2016-11-08 16:37 EDT---
 State: Working by: carp on 08 November 2016 14:49:01 

#=#=# 2016-11-08 14:48:59 (CST) #=#=#
New Fix_Potential = [F860.20W]
#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#

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

Title:
  STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
  ubuntu 16.04 guest.

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Application Cdeadmin  -
  2016-07-26 11:20:20 ==

  
  == Comment: #1 - Application Cdeadmin  - 2016-07-26 
11:20:22 ==
   State: Open by: panico on 25 July 2016 18:02:09 

  Contact Information:
  
  Defect Originator:  Michael Panico
  Defect Originator   pan...@us.ibm.com

  Backup: Deepti Umarani
  Backup ST ID: Deepti S Umarani/India/IBM

  System Info:
  
  Machine Type:8284-22A
  Card Type:...FSP2_P8LE
  Current Boot Side:...T
  Next Boot Side:..T
  PT_Swap:.1
  Current Side Driver:.fips860/b0713a_1630.860 

  Ubuntu KVM Host:
  root@iaos1:/tmp# uname -a
  Linux iaos1 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  root@iaos1:/tmp# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

  Ubuntu Guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m uname -a
  Linux iap03 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:05:18 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  HTX level on ubuntu 16.04 guest:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m dpkg -l | grep htxubuntu
  ii  htxubuntu  402 ppc64el

  Problem Description:
  
  Running networks (via bridging) on three different guests (other linux, 
ubuntu 16.10 and ubuntu 16.04) the ubuntu 16.04 guest logged a miscompare on 
the austin adapter and the shinerT adapter.  The shinerT ran for 24 hours and 
the austin for 72 hours before logging miscompares.

  From /tmp/htxerr:
  [htx@iap03]  [1m/usr/lpp/htx/bin# [0m cat /tmp/htxerr

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00e3 sev=4 hxecom
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  Miscompare with packet 0, data size = 51062. miscompare_count=0 pakLen = 
51082 
  Miscompare at displacement (decimal) = 23876 
  wbuf = 
  rbuf = 

  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads= 70739865,  good bytes read= 2868570843930

  /dev/enp0s6   Jul 23 14:29:00 2016 err=00d8 sev=4 hxecom
  Shutting down testing due to error flag - 1
  R(102.1.2.20.50854) connected to W(102.1.1.20.39073)
  For stanza 0, TCP connection, bufmin=3, bufmax=65000, bufinc=10531
  Consecutive prior good reads=0,  good bytes read= 0

  /dev/enp0s7   Jul 23 14:29:00 2016 err=00fb0068 sev=1 hxecom
  W(102.1.1.20.39073) connected to R(102.1.2.20.50854)
  Wrote 878 characters, expected 963
  Write failed - Connection reset by peer.
  For stanza 1, TCP connection,  bufmin=3, bufmax=2869, bufinc=94
  Consecutive prior good writes= 25459432,  good bytes written=   
35283290616

  htx_messages  Jul 23 14:29:01 2016 err= sev=1 hxssup
  hxecom HE program for enp0s6 terminated by exit(0) call.

  htx_messages  Jul 23 16:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 7206 seconds.

  htx_messages  Jul 23 18:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 14406 seconds.

  htx_messages  Jul 23 20:29:07 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 21606 seconds.

  htx_messages  Jul 23 22:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 28807 seconds.

  htx_messages  Jul 24 00:29:08 2016 err= sev=4 hang_monitor  
  hxecom for enp0s7 is HUNG!
  Max run time (set in mdt) = 7200 seconds.
  Current elasped time = 36007 seconds.

  /dev/enp0s4   Jul 25 04:56:13 2016 err=00e3 sev=4 

[Kernel-packages] [Bug 1640297] Re: 16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab. Boots fine in 4.4.0-42-generic and older

[normandrobert]

** Summary changed:

- Hang during boot 4.4.0-45-generic with /etc/crypttab. Boots fine in 
4.4.0-42-generic and older
+ 16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab. Boots fine 
in 4.4.0-42-generic and older

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

Title:
  16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab.
  Boots fine in 4.4.0-42-generic and older

Status in linux package in Ubuntu:
  New

Bug description:
  System hangs during boot with 4.4.0-45-generic if /etc/crypptab
  contains a valid entry. Passphrase prompt never seen. Black screen
  with blinking underscore in upper left corner. Repeated attempts to
  type passphrase have no effect.

  There are two workarounds:
  1) Comment out line referring the encrypted partition in /etc/crypttab and 
/etc/fstab. Mount the partition manually after boot completes
  2) Boot in 4.4.0-42-generic which works as do earlier versions. i.e. the user 
provides passphrase at the prompt during boot and the system finishes booting

  robert@kalymnos:~$ cat /etc/crypttab
  spare2 UUID=498b08bb-5e6b-4ddf-8b37-e059665a34e6 none luks
  robert@kalymnos:~$ grep mapper /etc/fstab
  /dev/mapper/spare2/spare2 ext4 defaults 0 2

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

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

[Kernel-packages] [Bug 1640297] Re: Hang during boot 4.4.0-45-generic with /etc/crypttab. Boots fine in 4.4.0-42-generic and older

[Paul White]

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

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

Title:
  16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab.
  Boots fine in 4.4.0-42-generic and older

Status in linux package in Ubuntu:
  New

Bug description:
  System hangs during boot with 4.4.0-45-generic if /etc/crypptab
  contains a valid entry. Passphrase prompt never seen. Black screen
  with blinking underscore in upper left corner. Repeated attempts to
  type passphrase have no effect.

  There are two workarounds:
  1) Comment out line referring the encrypted partition in /etc/crypttab and 
/etc/fstab. Mount the partition manually after boot completes
  2) Boot in 4.4.0-42-generic which works as do earlier versions. i.e. the user 
provides passphrase at the prompt during boot and the system finishes booting

  robert@kalymnos:~$ cat /etc/crypttab
  spare2 UUID=498b08bb-5e6b-4ddf-8b37-e059665a34e6 none luks
  robert@kalymnos:~$ grep mapper /etc/fstab
  /dev/mapper/spare2/spare2 ext4 defaults 0 2

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

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

[Kernel-packages] [Bug 1250476] Re: 8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to ram

[Valentas]

Also affects me on Ubuntu 16.04 LTS, 4.4.0-45-generic, ThinkPad-T430.

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

Title:
  8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents
  suspend to ram

Status in linux package in Ubuntu:
  Expired

Bug description:
  Sometimes, usually towards the end of the day, I find my e100e module
  does not allow the system to suspend.

  WORKAROUND: "rmmod e100e" and I can suspend again. I do use the
  ethernet adapter, and it only has occurred after having been connected
  to ethernet.

  The following is seen in dmsg:
  Nov 12 12:08:38 pk0k4dr kernel: [33964.643792] PM: Syncing filesystems ... 
done.
  Nov 12 12:08:38 pk0k4dr kernel: [33965.021021] PM: Preparing system for mem 
sleep
  Nov 12 12:08:42 pk0k4dr kernel: [33965.134863] Freezing user space processes 
... (elapsed 0.001 seconds) done.
  Nov 12 12:08:42 pk0k4dr kernel: [33965.136441] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Nov 12 12:08:42 pk0k4dr kernel: [33965.137766] PM: Entering mem sleep
  Nov 12 12:08:42 pk0k4dr kernel: [33965.137838] Suspending console(s) (use 
no_console_suspend to debug)
  Nov 12 12:08:42 pk0k4dr kernel: [33965.137889] xhci_hcd :00:14.0: power 
state changed by ACPI to D0
  Nov 12 12:08:42 pk0k4dr kernel: [33965.238268] xhci_hcd :00:14.0: setting 
latency timer to 64
  Nov 12 12:08:42 pk0k4dr kernel: [33965.238338] ehci-pci :00:1a.0: power 
state changed by ACPI to D0
  Nov 12 12:08:42 pk0k4dr kernel: [33965.342280] ehci-pci :00:1a.0: setting 
latency timer to 64
  Nov 12 12:08:42 pk0k4dr kernel: [33965.342306] ehci-pci :00:1d.0: power 
state changed by ACPI to D0
  Nov 12 12:08:42 pk0k4dr kernel: [33965.446254] ehci-pci :00:1d.0: setting 
latency timer to 64
  Nov 12 12:08:42 pk0k4dr kernel: [33965.578114] sd 0:0:0:0: [sda] 
Synchronizing SCSI cache
  Nov 12 12:08:42 pk0k4dr kernel: [33965.578476] sd 0:0:0:0: [sda] Stopping disk
  Nov 12 12:08:42 pk0k4dr kernel: [33965.802057] nouveau [ DRM] suspending 
fbcon...
  Nov 12 12:08:42 pk0k4dr kernel: [33965.802061] nouveau [ DRM] suspending 
display...
  Nov 12 12:08:42 pk0k4dr kernel: [33965.802087] nouveau [ DRM] unpinning 
framebuffer(s)...
  Nov 12 12:08:42 pk0k4dr kernel: [33965.802480] mei_me :00:16.0: suspend
  Nov 12 12:08:42 pk0k4dr kernel: [33965.803108] nouveau [ DRM] evicting 
buffers...
  Nov 12 12:08:42 pk0k4dr kernel: [33965.827282] nouveau [ DRM] waiting for 
kernel channels to go idle...
  Nov 12 12:08:42 pk0k4dr kernel: [33965.827309] nouveau [ DRM] suspending 
client object trees...
  Nov 12 12:08:42 pk0k4dr kernel: [33965.835924] nouveau [ DRM] suspending 
kernel object tree...
  Nov 12 12:08:42 pk0k4dr kernel: [33966.209804] i915 :00:02.0: power state 
changed by ACPI to D3cold
  Nov 12 12:08:42 pk0k4dr kernel: [33966.429324] pci_pm_suspend(): 
e1000_suspend+0x0/0x20 [e1000e] returns -2
  Nov 12 12:08:42 pk0k4dr kernel: [33966.429328] dpm_run_callback(): 
pci_pm_suspend+0x0/0x150 returns -2
  Nov 12 12:08:42 pk0k4dr kernel: [33966.429330] PM: Device :00:19.0 failed 
to suspend async: error -2
  Nov 12 12:08:42 pk0k4dr kernel: [33967.221549] nouveau :01:00.0: power 
state changed by ACPI to D3cold
  Nov 12 12:08:42 pk0k4dr kernel: [33967.221613] PM: Some devices failed to 
suspend, or early wake event detected
  Nov 12 12:08:42 pk0k4dr kernel: [33967.221661] i915 :00:02.0: power state 
changed by ACPI to D0
  Nov 12 12:08:42 pk0k4dr kernel: [33967.221684] xhci_hcd :00:14.0: setting 
latency timer to 64
  Nov 12 12:08:42 pk0k4dr kernel: [33967.221737] mei_me :00:16.0: irq 45 
for MSI/MSI-X

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-13-generic 3.11.0-13.20
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jammy  3673 F pulseaudio
  Date: Tue Nov 12 13:42:10 2013
  HibernationDevice: RESUME=UUID=36cdf9ac-9cc9-4649-9be0-ed0a81c29b26
  InstallationDate: Installed on 2013-10-16 (26 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MachineType: LENOVO 24491D1
  MarkForUpload: True
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-13-generic N/A
   linux-backports-modules-3.11.0-13-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  

[Kernel-packages] [Bug 1640297] [NEW] Hang during boot 4.4.0-45-generic with /etc/crypttab. Boots fine in 4.4.0-42-generic and older

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

System hangs during boot with 4.4.0-45-generic if /etc/crypptab contains
a valid entry. Passphrase prompt never seen. Black screen with blinking
underscore in upper left corner. Repeated attempts to type passphrase
have no effect.

There are two workarounds:
1) Comment out line referring the encrypted partition in /etc/crypttab and 
/etc/fstab. Mount the partition manually after boot completes
2) Boot in 4.4.0-42-generic which works as do earlier versions. i.e. the user 
provides passphrase at the prompt during boot and the system finishes booting

robert@kalymnos:~$ cat /etc/crypttab
spare2 UUID=498b08bb-5e6b-4ddf-8b37-e059665a34e6 none luks
robert@kalymnos:~$ grep mapper /etc/fstab
/dev/mapper/spare2/spare2 ext4 defaults 0 2

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

-- 
Hang during boot 4.4.0-45-generic with /etc/crypttab. Boots fine in 
4.4.0-42-generic and older
https://bugs.launchpad.net/bugs/1640297
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1640275] Re: move nvme driver to linux-image

[Dan Streetman]

> lib/modules/4.4.0-46-generic/kernel/drivers/nvme/host/nvme.ko

Sorry, this is for trusty.

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

Title:
  move nvme driver to linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The nvme driver is in the -extra package but should be in the linux-
  image package, to avoid the overhead of having to install the -extra
  package just to get the nvme driver.

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

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

[Kernel-packages] [Bug 1640275] Re: move nvme driver to linux-image

[Tim Gardner]

There must be something else going on 'cause I think the nvme driver is
in linux-image:

lib/modules/4.4.0-46-generic/kernel/drivers/nvme/host/nvme.ko

It is also explicitly mentioned in the inclusion file:

debian.master/control.d/generic.inclusion-list:drivers/nvme/host/nvme.ko

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

Title:
  move nvme driver to linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The nvme driver is in the -extra package but should be in the linux-
  image package, to avoid the overhead of having to install the -extra
  package just to get the nvme driver.

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

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

[Kernel-packages] [Bug 1612006] Re: I2C touchpad does not work on AMD platform

[Alex Hung]

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

** Changed in: hwe-next
   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/1612006

Title:
  I2C touchpad does not work on AMD platform

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Recent AMD platform has problems with I2C touchpads because its GPIO
  controller is not configured correctly.

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

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

[Kernel-packages] [Bug 1634607] Re: kernel generates ACPI Exception: AE_NOT_FOUND, Evaluating _DOD incorrectly

[Alex Hung]

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

Title:
  kernel generates ACPI Exception: AE_NOT_FOUND, Evaluating _DOD
  incorrectly

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Many system supports hybrid graphics and its discrete VGA does not
  have any connectors and therefore has no _DOD method.  However, kernel
  assumes the control method, _DOD, is required.  As a result, an
  exception is thrown incorrectly.

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

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

[Kernel-packages] [Bug 1637528] Re: [Feature] Add Knights Mill to Intel processors family list

[Tim Gardner]

ba2f81575eba8dcf128354169c20ae23f810f652 perf/x86/intel/uncore: Add Knights 
Mill CPUID
36c4b6c14d20b37fda79cbcd3e8ef7d11f5ef9dc perf/x86/intel/rapl: Add Knights Mill 
CPUID
608284bf0def3ca5e6936920fcd84294101ef12d perf/x86/intel: Add Knights Mill CPUID
0047f59834e5947d45f34f5f12eb330d158f700b x86/cpu/intel: Add Knights Mill to 
Intel family


** Information type changed from Proprietary to Public

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

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

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

** Changed in: linux (Ubuntu Zesty)
   Status: New => 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/1637528

Title:
  [Feature] Add Knights Mill to Intel processors family list

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

Bug description:
  The patch that introduces KNM CPUID was merged in upstream kernel
  (avail 4.9-rc2).

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0047f59834e5947d45f34f5f12eb330d158f700b

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

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

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

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

Title:
  remote no longer works on wily

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  since upgrading to wily, my tivo slide pro no longer has many of its
  keys recognized by the kernel. xev shows that many keys no longer
  register.

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

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

[Kernel-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

[Rolf Leggewie]

I apologize for the delayed response, I was travelling.

Yes, the error message is the same as for the original report.  Then it
was triggered by a call to lsattr, now by calling btrfs to create a
snapshot.  The released kernels do not have the originally reported
problem with lsattr but regressed with the call to create a snapshot.  I
originally found a regression when calling "btrfs fi show" which one
only emit a one-liner with the program version but not the requested
version with information about the btrfs partitions.

I have not yet had the chance to test the xenial or yakkety kernels.

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

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

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Kernel-packages] [Bug 1454843] Re: 10ec:b723 Realtek RTL8723BE wireless card drops connection

[Sebastian]

I wrote 2 short scripts for replacing the drivers after new installation or 
kernel upgrades:
The first rtl8723be_install.sh is for download and installation of an 
alternative driver after a new installation, the second rtl8723be_reinstall.sh 
for re-installation after a kernel upgrade.

"rtl8723be_install.sh":

sudo apt-get install build-essential git
git clone https://github.com/lwfinger/rtlwifi_new/
cd rtlwifi_new
make
install
sudo make install
echo "options rtl8723be swenc=1 fwlps=0 ips=0" | sudo tee 
/etc/modprobe.d/rtl8723be.conf
sudo modprobe -r rtl8723be
sudo modprobe rtl8723be


"rtl8723be_reinstall.sh":

cd rtlwifi_new
make clean
git pull
make clean && make
sudo make install
sudo modprobe -rv rtl8723be
sudo modprobe -v rtl8723be

This is for me the best solution so far.

** Attachment added: "rtl8723be_scripts.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454843/+attachment/4774509/+files/rtl8723be_scripts.tar.gz

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

Title:
  10ec:b723 Realtek RTL8723BE wireless card drops connection

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  I am using Lenovo M30-70.

  I tried many workarounds from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320070 but no
  change, the connection is lost after a while.

  Finally I tried the rtlwifi_new driver from 
https://bugzilla.kernel.org/show_bug.cgi?id=83641#c1.
  I first thought it works stable but after a while it also loses the 
connection (see my comment there). After reconnect it works for a while again.
  I uninstalled the rtlwifi_new driver for this bug report.


  (Bluetooth does not work at all, it doesn't find any devices)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-17-generic 3.19.0-17.17
  ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6
  Uname: Linux 3.19.0-17-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sledzik2179 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May 13 22:51:38 2015
  HibernationDevice: RESUME=UUID=d61164da-04eb-444a-a976-6a1f91fc4ffb
  InstallationDate: Installed on 2015-03-11 (63 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO ZIUS6
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-17-generic.efi.signed 
root=UUID=40721d88-7203-4dfa-ac65-1a2b204fea34 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-17-generic N/A
   linux-backports-modules-3.19.0-17-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-06 (36 days ago)
  dmi.bios.date: 10/15/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8BCN45WW(V3.08)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: INVALID
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: INVALID
  dmi.modalias: 
dmi:bvnLENOVO:bvr8BCN45WW(V3.08):bd10/15/2014:svnLENOVO:pnZIUS6:pvrINVALID:rvnLENOVO:rnINVALID:rvrINVALID:cvnLENOVO:ct10:cvrINVALID:
  dmi.product.name: ZIUS6
  dmi.product.version: INVALID
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1515087] Re: remote no longer works on wily

[Paul White]

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

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

Title:
  remote no longer works on wily

Status in linux package in Ubuntu:
  New

Bug description:
  since upgrading to wily, my tivo slide pro no longer has many of its
  keys recognized by the kernel. xev shows that many keys no longer
  register.

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

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

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

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

Title:
  move nvme driver to linux-image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The nvme driver is in the -extra package but should be in the linux-
  image package, to avoid the overhead of having to install the -extra
  package just to get the nvme driver.

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

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

[Kernel-packages] [Bug 1515087] [NEW] remote no longer works on wily

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

since upgrading to wily, my tivo slide pro no longer has many of its
keys recognized by the kernel. xev shows that many keys no longer
register.

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


** Tags: bot-comment wily
-- 
remote no longer works on wily
https://bugs.launchpad.net/bugs/1515087
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1640275] [NEW] move nvme driver to linux-image

[Dan Streetman]

Public bug reported:

The nvme driver is in the -extra package but should be in the linux-
image package, to avoid the overhead of having to install the -extra
package just to get the nvme driver.

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


** Tags: sts-sru

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

Title:
  move nvme driver to linux-image

Status in linux package in Ubuntu:
  New

Bug description:
  The nvme driver is in the -extra package but should be in the linux-
  image package, to avoid the overhead of having to install the -extra
  package just to get the nvme driver.

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

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

[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

[Alexandre]

I was running 4.4.0-46 (not sure if different than the latest .67?) on
October 27th and yesterday had to reboot for the "... count = 1"
problem.

Was there previous 4.4.0-46 releases? If not, the bug is still
present...

Otherwise, I'll confirm if it happens again, or if it doesn't within a
few weeks.

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

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

  processor : 7
  vendor_id : GenuineIntel
  cpu family: 6
  model : 77
  model name: Intel(R) Atom(TM) CPU  C2758  @ 2.40GHz
  stepping  : 8
  microcode : 0x11d
  cpu MHz   : 2400.000
  cache size: 1024 KB
  physical id   : 0
  siblings  : 8
  core id   : 7
  cpu cores : 8
  apicid: 14
  initial apicid: 14
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 11
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm 
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch 
arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
  bogomips  : 4799.48
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 36 bits physical, 48 bits virtual
  power management:

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

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

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

[Kernel-packages] [Bug 1612006] Re: I2C touchpad does not work on AMD platform

[Luis Henriques]

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

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

Title:
  I2C touchpad does not work on AMD platform

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  Recent AMD platform has problems with I2C touchpads because its GPIO
  controller is not configured correctly.

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

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

[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel

[Luis Henriques]

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

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

Title:
  zfs: importing zpool with vdev on zvol hangs kernel

Status in linux package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in zfs-linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Triaged
Status in zfs-linux source package in Zesty:
  Fix Released

Bug description:
  [SRU Request][Xenial][Yakkety]

  if a zvol of an existing, already imported zpool is a vdev of another
  zpool, a call to "zpool import" will everything zfs related. the stack
  trace is as follows:

  [] taskq_wait+0x74/0xe0 [spl]
  [] taskq_destroy+0x4b/0x100 [spl]
  [] vdev_open_children+0x12d/0x180 [zfs]
  [] vdev_root_open+0x3c/0xc0 [zfs]
  [] vdev_open+0xf5/0x4d0 [zfs]
  [] spa_load+0x39e/0x1c60 [zfs]
  [] spa_tryimport+0xad/0x450 [zfs]
  [] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
  [] zfsdev_ioctl+0x44b/0x4e0 [zfs]
  [] do_vfs_ioctl+0x29f/0x490
  [] SyS_ioctl+0x79/0x90
  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [] 0x

  [Fix]
  zfsutils-linux:

  Zesty: https://launchpadlibrarian.net/290907232/zfs-
  linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz

  Yakkety, likewise
  Xenial, likewise

  Sync'd fixes into kernel repos, patches in:
  http://kernel.ubuntu.com/~cking/zfs-lp-1636517

  [Regression Potential]

  Minimal. This just touched one line in the zfs module
  module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h

  Tested and passes with the ubuntu kernel team autotest client zfs
  regression tests.

  =

  I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged
  in 4.4.0-6.21), which added a second parameter to lookup_bdev without
  patching the zfs module (which needs to special case the vdev-on-zvol
  case, and uses this exact method only in this special casing code
  path).

  attached you can find the output of "zfs send -R" ing such a zvol
  ("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
  by "zpool import" should reproduce the hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 25 15:46 seq
   crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct 25 15:49:51 2016
  HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
  InstallationDate: Installed on 2016-10-25 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  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: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.7
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.7
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1637303] Re: Move some device drivers build from kernel built-in to modules

[Luis Henriques]

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

Title:
  Move some device drivers build from kernel built-in to modules

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

Bug description:
  Some drivers in Ubuntu are built as kernel built-in components, not
  allowing some module interesting features like blacklist on boot
  command-line or module removal/replacement. Also, modules has debug
  advantages compared to built-in kernel components, like the
  possibility to easy build custom-debug modules against kernel tree and
  replace them using modprobe on running system.

  This feature is a request to Canonical move some currently built-in
  drivers to module build system on Power platform, by changing the
  kernel config file.

  The drivers in question are: tg3, virtio-blk and virtio-net.
  The kernel config file parameters related to those 3 drivers are:

  CONFIG_TIGON3, CONFIG_VIRTIO_BLK and CONFIG_VIRTIO_NET.
  They all are currently set as "=y"; we're requesting a change to "=m".

  Thanks in advance,


  Guilherme

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

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

[Kernel-packages] [Bug 1636330] Re: guest experiencing Transmit Timeouts on CX4

[Luis Henriques]

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

Title:
  guest experiencing Transmit Timeouts on CX4

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

Bug description:
  This patch fixes a race condition that was reintroduced in the 4.8
  kernel, as part of the P9 changes, after having been originally fixed
  in 3.19. The effect of the race condition is that a secondary thread
  can start trying to execute code from the guest while the thread is
  still in hypervisor mode, so it can cause many different symptoms, one
  of which seems to be the timebase corruption that leads to the lockup
  in ktime_get_ts64. It could cause other problems such as CPU cores
  locking up hard or memory corruption.

  This patch is only needed on the host. It should be applied to any 4.8
  kernel being used as a host, including the Ubuntu 16.10 kernel.

  Hi Paul
  I built a kernel with your patch and put at the host and in the guest. I can 
still see some ktime_get_ts64 at the host. The guest dmesg is clean.

  This patch fixes another race condition I found in the fastsleep code.
  Please apply this patch as well and test.

  Sure will do and provide feedback.

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

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

[Kernel-packages] [Bug 1637526] Re: [Feature] AVX-512 new instruction sets (avx512_4vnniw, avx512_4fmaps)

[Luis Henriques]

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

Title:
  [Feature] AVX-512 new instruction sets (avx512_4vnniw, avx512_4fmaps)

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  The following instruction set are extension to AVX512 on Intel's Xeon and 
Xoen Phi processors:
  • avx512_4vnniw - Vector instructions for deep learning enhanced word 
variable precision.
  • avx512_4fmaps - Vector instructions for deep learning floating-point single 
precision.

  We will detect the features in CPUID:eax=7:ecx=0->edx[2:3].

  Patch merged in 4.9rc-2
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8214899342981dbd49ae24aadbbd19e9e7830684

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

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

[Kernel-packages] [Bug 1640245] Re: Ubuntu Server 16.04 install errors on linux-generic (dependency problem)

[Luke Olson]

When trying to run the "apport-collect 1640245" command from a terminal
it says the command is not found. This is probably because it's during
the system install rather than a running system. Per the previous
comment I'm changing the status to confirmed.

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

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

Title:
  Ubuntu Server 16.04 install errors on linux-generic (dependency
  problem)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've tried several times to install Ubuntu Server 16.04.1 (and 16.04)
  and both error out and stop when installing linux-generic package
  during the "Install Base System" step of the install. The error
  message suggests running an apt-get command to fix a dependency
  problem but there's no apt-get available since this is during the
  system install.

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

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

[Kernel-packages] [Bug 1617686] Re: Kernel 4.4.0-34 caused Redshift/Flux/brightness-controller etc. to stop working

[JI Xiang]

Well no. I reported that it doesn't work on both Nvidia card and the
integrated Intel card. While on another kernel it works on both Nvidia
and Intel cards. I currently have Nvidia 364 driver and I have redshift
working totally fine. So I don't believe it's induced by NVIDIA driver.
Maybe you're having another 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/1617686

Title:
  Kernel 4.4.0-34 caused Redshift/Flux/brightness-controller etc. to
  stop working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As per reported by several users, such as in
  https://ubuntuforums.org/showthread.php?t=298, apps that control
  screen gamma, such as Redshift/Flux/brightness-controller, stopped
  working under the newest kernel 4.4.0-34 in Ubuntu 16.04 LTS, and
  we're not sure what caused the issue.

  Those apps are still working well on external monitors. It's just the
  internal monitor that is not responsive. Any setting just simply has
  no effect.

  It seems that all the users are using Skylake-based laptop.

  In my case, my laptop is on Skylake and GTX980M.

  Links for the individual apps mentioned above:
  - Redshift http://jonls.dk/redshift/
  - Flux https://justgetflux.com/linux.html
  - brightness-controller 
https://apps.ubuntu.com/cat/applications/brightness-controller/

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jx 4045 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=66785c85-3633-4f60-b15d-718b7b14873e
  InstallationDate: Installed on 2016-04-25 (125 days ago)
  InstallationMedia: It
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 046d:c07e Logitech, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hasee Computer CP65R
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d940d1fe-4c2c-4de3-b82d-108083812e0e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd09/18/2015:svnHaseeComputer:pnCP65R:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: CP65R
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Hasee Computer

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

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

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

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

Title:
  Ubuntu Server 16.04 install errors on linux-generic (dependency
  problem)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've tried several times to install Ubuntu Server 16.04.1 (and 16.04)
  and both error out and stop when installing linux-generic package
  during the "Install Base System" step of the install. The error
  message suggests running an apt-get command to fix a dependency
  problem but there's no apt-get available since this is during the
  system install.

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

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

[Kernel-packages] [Bug 1617686] Re: Kernel 4.4.0-34 caused Redshift/Flux/brightness-controller etc. to stop working

[JI Xiang]

@thorsten-munsch Maybe you should actually file another bug report
instead.

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

Title:
  Kernel 4.4.0-34 caused Redshift/Flux/brightness-controller etc. to
  stop working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As per reported by several users, such as in
  https://ubuntuforums.org/showthread.php?t=298, apps that control
  screen gamma, such as Redshift/Flux/brightness-controller, stopped
  working under the newest kernel 4.4.0-34 in Ubuntu 16.04 LTS, and
  we're not sure what caused the issue.

  Those apps are still working well on external monitors. It's just the
  internal monitor that is not responsive. Any setting just simply has
  no effect.

  It seems that all the users are using Skylake-based laptop.

  In my case, my laptop is on Skylake and GTX980M.

  Links for the individual apps mentioned above:
  - Redshift http://jonls.dk/redshift/
  - Flux https://justgetflux.com/linux.html
  - brightness-controller 
https://apps.ubuntu.com/cat/applications/brightness-controller/

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jx 4045 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=66785c85-3633-4f60-b15d-718b7b14873e
  InstallationDate: Installed on 2016-04-25 (125 days ago)
  InstallationMedia: It
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 046d:c07e Logitech, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hasee Computer CP65R
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d940d1fe-4c2c-4de3-b82d-108083812e0e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd09/18/2015:svnHaseeComputer:pnCP65R:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: CP65R
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Hasee Computer

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

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

[Kernel-packages] [Bug 1612006] Re: I2C touchpad does not work on AMD platform

[Luis Henriques]

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

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

Title:
  I2C touchpad does not work on AMD platform

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  New

Bug description:
  Recent AMD platform has problems with I2C touchpads because its GPIO
  controller is not configured correctly.

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

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

[Kernel-packages] [Bug 1636517] Re: zfs: importing zpool with vdev on zvol hangs kernel

[Luis Henriques]

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

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

Title:
  zfs: importing zpool with vdev on zvol hangs kernel

Status in linux package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  New
Status in zfs-linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Triaged
Status in zfs-linux source package in Zesty:
  Fix Released

Bug description:
  [SRU Request][Xenial][Yakkety]

  if a zvol of an existing, already imported zpool is a vdev of another
  zpool, a call to "zpool import" will everything zfs related. the stack
  trace is as follows:

  [] taskq_wait+0x74/0xe0 [spl]
  [] taskq_destroy+0x4b/0x100 [spl]
  [] vdev_open_children+0x12d/0x180 [zfs]
  [] vdev_root_open+0x3c/0xc0 [zfs]
  [] vdev_open+0xf5/0x4d0 [zfs]
  [] spa_load+0x39e/0x1c60 [zfs]
  [] spa_tryimport+0xad/0x450 [zfs]
  [] zfs_ioc_pool_tryimport+0x64/0xa0 [zfs]
  [] zfsdev_ioctl+0x44b/0x4e0 [zfs]
  [] do_vfs_ioctl+0x29f/0x490
  [] SyS_ioctl+0x79/0x90
  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [] 0x

  [Fix]
  zfsutils-linux:

  Zesty: https://launchpadlibrarian.net/290907232/zfs-
  linux_0.6.5.8-0ubuntu4_0.6.5.8-0ubuntu5.diff.gz

  Yakkety, likewise
  Xenial, likewise

  Sync'd fixes into kernel repos, patches in:
  http://kernel.ubuntu.com/~cking/zfs-lp-1636517

  [Regression Potential]

  Minimal. This just touched one line in the zfs module
  module/zfs/zvol.cand a shim wrapper in include/linux/blkdev_compat.h

  Tested and passes with the ubuntu kernel team autotest client zfs
  regression tests.

  =

  I traced this back to 193fb6a2c94fab8eb8ce70a5da4d21c7d4023bee (erged
  in 4.4.0-6.21), which added a second parameter to lookup_bdev without
  patching the zfs module (which needs to special case the vdev-on-zvol
  case, and uses this exact method only in this special casing code
  path).

  attached you can find the output of "zfs send -R" ing such a zvol
  ("brokenvol.raw"), running "zfs receive POOL/TARGET < FILE" followed
  by "zpool import" should reproduce the hang.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 25 15:46 seq
   crw-rw 1 root audio 116, 33 Oct 25 15:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct 25 15:49:51 2016
  HibernationDevice: RESUME=/dev/mapper/xenial--vg-swap_1
  InstallationDate: Installed on 2016-10-25 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  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: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.7
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.7
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1636733] Re: [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default

[Luis Henriques]

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

Title:
  [LTCTest] vfio_pci not loaded on Ubuntu 16.10 by default

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

Bug description:
  == Comment: #0 - SRIKANTH B. AITHAL  - 2016-10-26 
01:40:39 ==
  ---Problem Description---
  vfio_pci is not loaded by default on Ubuntu 16.10 host boot. All VFIO related 
tasks would fail without that module. For instance I was trying to boot guest 
with QEMU directly and it was failing complaining 
"/sys/bus/pci/drivers/vfio-pci/new_id" not present.

  root@c158f2u09os:~# lsmod | grep -i vfio
  root@c158f2u09os:~# modprobe vfio_pci <-- need to load explicitly
  root@c158f2u09os:~# lsmod | grep -i vfio
  vfio_pci   51735  0
  irqbypass   5567  1 vfio_pci
  vfio_iommu_spapr_tce14567  0
  vfio_virqfd 4859  1 vfio_pci
  vfio   31351  2 vfio_iommu_spapr_tce,vfio_pci
  vfio_spapr_eeh  3441  2 vfio_iommu_spapr_tce,vfio_pci

  Either 
  > we need to have these modules loaded by kernel by default 
  or 
  > we need to update https://wiki.ubuntu.com/ppc64el/CommonQuestions telling 
customers to load vfio_pci module explicitly before attempting any vfio tasks.
   
  Contact Information = Srikanth/bssrika...@in.ibm.com 
   
  ---uname output---
  Linux c158f2u09os 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:41:40 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. After booting into Ubuntu 16.10, see if vfio_pci modules are loaded:
  root@c158f2u09os:~# lsmod | grep -i vfio
  2. After that we need to manually load vfio_pci
  root@c158f2u09os:~# modprobe vfio_pci
  root@c158f2u09os:~#

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

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

[Kernel-packages] [Bug 1640245] Re: Ubuntu Server 16.04 install errors on linux-generic (dependency problem)

[Luke Olson]

Photo of tty4 during the install when the error showed up (more
detailed).

** Attachment added: "tty4.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640245/+attachment/4774497/+files/tty4.jpg

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

Title:
  Ubuntu Server 16.04 install errors on linux-generic (dependency
  problem)

Status in linux package in Ubuntu:
  New

Bug description:
  I've tried several times to install Ubuntu Server 16.04.1 (and 16.04)
  and both error out and stop when installing linux-generic package
  during the "Install Base System" step of the install. The error
  message suggests running an apt-get command to fix a dependency
  problem but there's no apt-get available since this is during the
  system install.

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

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

[Kernel-packages] [Bug 1640245] Re: Ubuntu Server 16.04 install errors on linux-generic (dependency problem)

[Luke Olson]

Photo of tty1 during the install when the error showed up.

** Attachment added: "tty1.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640245/+attachment/4774496/+files/tty1.jpg

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

Title:
  Ubuntu Server 16.04 install errors on linux-generic (dependency
  problem)

Status in linux package in Ubuntu:
  New

Bug description:
  I've tried several times to install Ubuntu Server 16.04.1 (and 16.04)
  and both error out and stop when installing linux-generic package
  during the "Install Base System" step of the install. The error
  message suggests running an apt-get command to fix a dependency
  problem but there's no apt-get available since this is during the
  system install.

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

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

[Kernel-packages] [Bug 1640245] Re: Ubuntu Server 16.04 install errors on linux-generic (dependency problem)

[Brad Figg]

** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

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

Title:
  Ubuntu Server 16.04 install errors on linux-generic (dependency
  problem)

Status in linux package in Ubuntu:
  New

Bug description:
  I've tried several times to install Ubuntu Server 16.04.1 (and 16.04)
  and both error out and stop when installing linux-generic package
  during the "Install Base System" step of the install. The error
  message suggests running an apt-get command to fix a dependency
  problem but there's no apt-get available since this is during the
  system install.

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

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

[Kernel-packages] [Bug 1640245] [NEW] Ubuntu Server 16.04 install errors on linux-generic (dependency problem)

[Luke Olson]

Public bug reported:

I've tried several times to install Ubuntu Server 16.04.1 (and 16.04)
and both error out and stop when installing linux-generic package during
the "Install Base System" step of the install. The error message
suggests running an apt-get command to fix a dependency problem but
there's no apt-get available since this is during the system install.

** 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-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1640245

Title:
  Ubuntu Server 16.04 install errors on linux-generic (dependency
  problem)

Status in linux package in Ubuntu:
  New

Bug description:
  I've tried several times to install Ubuntu Server 16.04.1 (and 16.04)
  and both error out and stop when installing linux-generic package
  during the "Install Base System" step of the install. The error
  message suggests running an apt-get command to fix a dependency
  problem but there's no apt-get available since this is during the
  system install.

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

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

[Kernel-packages] [Bug 1617686] Re: Kernel 4.4.0-34 caused Redshift/Flux/brightness-controller etc. to stop working

[Thorsten Munsch]

Actually, this doesn't seem to be an error in the kernel itself.

It affects 16.04 and 14.04.5 with kernel 4.4.0-45 and is related to the
propritary Nvidia driver later than 361.42.

Solution: go back to 361.42 which let's flux change the color
immedieately after restarting lightdm.

See: https://github.com/xflux-gui/xflux-gui/issues/27

Can be closed here, or?

** Bug watch added: github.com/xflux-gui/xflux-gui/issues #27
   https://github.com/xflux-gui/xflux-gui/issues/27

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

Title:
  Kernel 4.4.0-34 caused Redshift/Flux/brightness-controller etc. to
  stop working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As per reported by several users, such as in
  https://ubuntuforums.org/showthread.php?t=298, apps that control
  screen gamma, such as Redshift/Flux/brightness-controller, stopped
  working under the newest kernel 4.4.0-34 in Ubuntu 16.04 LTS, and
  we're not sure what caused the issue.

  Those apps are still working well on external monitors. It's just the
  internal monitor that is not responsive. Any setting just simply has
  no effect.

  It seems that all the users are using Skylake-based laptop.

  In my case, my laptop is on Skylake and GTX980M.

  Links for the individual apps mentioned above:
  - Redshift http://jonls.dk/redshift/
  - Flux https://justgetflux.com/linux.html
  - brightness-controller 
https://apps.ubuntu.com/cat/applications/brightness-controller/

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jx 4045 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=66785c85-3633-4f60-b15d-718b7b14873e
  InstallationDate: Installed on 2016-04-25 (125 days ago)
  InstallationMedia: It
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 046d:c07e Logitech, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hasee Computer CP65R
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=d940d1fe-4c2c-4de3-b82d-108083812e0e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd09/18/2015:svnHaseeComputer:pnCP65R:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: CP65R
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Hasee Computer

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

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

[Kernel-packages] [Bug 1636330] Re: guest experiencing Transmit Timeouts on CX4

[Tim Gardner]

Re-submitted upstream cherry-picks: https://lists.ubuntu.com/archives
/kernel-team/2016-November/080767.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/1636330

Title:
  guest experiencing Transmit Timeouts on CX4

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

Bug description:
  This patch fixes a race condition that was reintroduced in the 4.8
  kernel, as part of the P9 changes, after having been originally fixed
  in 3.19. The effect of the race condition is that a secondary thread
  can start trying to execute code from the guest while the thread is
  still in hypervisor mode, so it can cause many different symptoms, one
  of which seems to be the timebase corruption that leads to the lockup
  in ktime_get_ts64. It could cause other problems such as CPU cores
  locking up hard or memory corruption.

  This patch is only needed on the host. It should be applied to any 4.8
  kernel being used as a host, including the Ubuntu 16.10 kernel.

  Hi Paul
  I built a kernel with your patch and put at the host and in the guest. I can 
still see some ktime_get_ts64 at the host. The guest dmesg is clean.

  This patch fixes another race condition I found in the fastsleep code.
  Please apply this patch as well and test.

  Sure will do and provide feedback.

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

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

[Kernel-packages] [Bug 1639961] Re: NMI watchdog: BUG: soft lockup during KVM guest migration test suite

[Tim Gardner]

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

This bug is a duplicate of http://bugs.launchpad.net/bugs/1636330

** This bug has been marked a duplicate of bug 1636330
   guest experiencing Transmit Timeouts on CX4

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

Title:
  NMI watchdog: BUG: soft lockup during KVM guest migration test suite

Status in linux package in Ubuntu:
  New

Bug description:
  Hello Canonical.

  We would like the changes in Commit 8117ac6a6c2f pulled into the
  Ubuntu 16.10 stream to address the following issue:

  == Comment: #0 - Balamuruhan S - 2016-09-23 08:48:52 ==
  ---Problem Description---

  Softlock up and call trace observed from libvirtd during guest migration test 
suite
   
  ---uname output---

  # uname -a Linux ltc-hab1 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  ---System Hang---
   NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [libvirtd:50800]
   message is continuous and recovered the machine with reboot

  84050.059159] INFO: rcu_sched self-detected stall on CPU
  [84050.059339]24-...: (5659 ticks this GP) idle=fa5/141/0 
softirq=549845/07 fqs=2176 
  [84050.059453] (t=5250 jiffies g=690268 c=690267 q=484)
  [84055.126993] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! 
[libvirtd:50800]
  [84104.509395] INFO: rcu_sched self-detected stall on CPU
  [84104.509591]24-...: (5659 ticks this GP) idle=5df/141/0 
softirq=562249/562249 fqs=2364 
  [84104.509820] (t=5250 jiffies g=690387 c=690386 q=351)
  [84107.125310] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! 
[virsh:56627]
  [84163.387536] INFO: rcu_sched self-detected stall on CPU
  [84163.387716]24-...: (5250 ticks this GP) idle=f69/142/0 
softirq=562274/562274 fqs=2354 
  [84163.387960] (t=5251 jiffies g=690488 c=690487 q=297)
  [84167.123420] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! 
[virsh:56633]
  [84226.401597] INFO: rcu_sched self-detected stall on CPU
  [84226.401769]24-...: (21004 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=9697 
  [84226.402012] (t=21005 jiffies g=690488 c=690487 q=1145)
  [84289.415706] INFO: rcu_sched self-detected stall on CPU
  [84289.415879]24-...: (36758 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=16889 
  [84289.416137] (t=36759 jiffies g=690488 c=690487 q=15499)
  [84352.429857] INFO: rcu_sched self-detected stall on CPU
  [84352.430038]24-...: (52512 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=23975 
  [84352.430269] (t=52513 jiffies g=690488 c=690487 q=16027)
  [84415.444044] INFO: rcu_sched self-detected stall on CPU
  [84415.444222]24-...: (68266 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=31005 
  [84415.34] (t=68267 jiffies g=690488 c=690487 q=16554)
  [84478.458262] INFO: rcu_sched self-detected stall on CPU
  [84478.458421]24-...: (84020 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=38023 
  [84478.458677] (t=84021 jiffies g=690488 c=690487 q=17030)
  [84541.472510] INFO: rcu_sched self-detected stall on CPU
  [84541.472680]24-...: (99774 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=45068 
  [84541.472939] (t=99775 jiffies g=690488 c=690487 q=17512)
  [84604.486783] INFO: rcu_sched self-detected stall on CPU

  
  Thanks.

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

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

[Kernel-packages] [Bug 1636847] Re: unexpectedly large memory usage of mounted snaps

[Seth Forshee]

Adding some notes and ideas based on looking more at the squashfs
implementation.

One idea I had was to reduce the data cache (or maybe even eliminate it)
by making squashfs decompress directly into the page cache. It turns out
that squashfs already does this if CONFIG_SQUASHFS_FILE_DIRECT=y, which
is the case in our kernel. Rather it tries to read into the page cache
directly first, and if that fails it falls back to using the cache, so
we can't eliminate the cache entirely. But it does mean that squashfs
can probably get by with much less data cache than it currently
allocates for SQUASHFS_DECOMP_MULTI and SQUASHFS_DECOMP_MULTI_PERCPU
when that option is set. We can't reduce the data cache for
CONFIG_SQUASHFS_DECOMP_SINGLE since it always needs enough cache for at
least one uncompressed data block.

Also important to note is that although the squashfs data cache size is
determined by which decompressor implementation is selected, the cache
and decompressor states are managed independently, therefore there's no
requirement that they are so tightly coupled. The coupling makes sense
if SQUASHFS_FILE_DIRECT is disabled but seems less sensible if it's
enabled.

The decompressor implementations come with their own tradeoffs:

- CONFIG_SQUASHFS_DECOMP_SINGLE: Uses less memory. However decompression
is serialized, i.e. for a given superblock only one block can be
decompressed at a time.

- SQUASHFS_DECOMP_MULTI: Allows for (num_online_cpus() * 2) parallel
decompressions, which means the number of parallel decompressions could
vary depending on how many CPUs were online when the filesystem was
mounted. Also allocates the same number of blocks for the data cache.
This implementation has more overhead associated with managing
decompressor state memory than the others.

- SQUASHFS_DECOMP_MULTI_PERCPU: This maintains per-cpu decompressor
state, therefore it is lockless and there is no overhead for managing
the decompressor state memory. That means it uses more RAM though, both
for decompressor state memory and for data cache. You also can have as
many parallel decompressions going on as there are CPU cores.

Based on this, here are a couple of ideas we could try to strike a good
balance between performance and RAM usage:

1. Add a config option for the maximum number of data cache blocks. This
would allow us to use one of the implementations which allows for
parallel decompression without the data cache size exploding. As long as
most blocks get decompressed directly into the page cache (which we'll
need to verify) having only one or two blocks in the data cache should
not be detrimental to performance.

2. Make a new decompressor implementation which allows for full
customization of the number of parallel decompressions and number of
blocks in the data cache. In my opinion SQUASHFS_DECOMP_SINGLE is too
little parallelization but the others are too much on systems with large
numbers of CPUs. Instead we could specify both the maximum number of
parallel decompressions in the kernel config (possibly capped at the
number of possible CPU cores) and the number of data blocks to cache to
suit our needs.

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

Title:
  unexpectedly large memory usage of mounted snaps

Status in Snappy:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  This is a tracking bug for what might be kernel bugs or kernel
  configuration changes.

  As described [1], memory used by simply mounting a squashfs file (even
  an empty one) is ranging from almost nothing (on certain
  distributions) to 131MB on Ubuntu 16.04 and 16.10 on a single-core
  machine or VM.

  The amount is excessive and should be investigated by the kernel team.
  We may need to change the kernel or at least the configuration we ship
  in our packages and kernel snaps.

  [1] https://github.com/zyga/mounted-fs-memory-checker

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

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

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

[bugproxy]

--- Comment From ru...@us.ibm.com 2016-11-08 10:54 EDT---
(In reply to comment #14)
> I am confused. Commit 8117ac6a6c2fa0f847ff6a21a1f32c8d2c8501d0
> ('powerpc/powernv: Switch off MMU before entering nap/sleep/rvwinkle mode')
> has been in the kernel for awhile.
>
> git describe --contains 8117ac6a6c2f
> v3.19-rc1~22^2~6

Sorry.  My error in grabbing the wrong commit for my query.  It's the
update fix for that earlier commit that we are looking for.

https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
stable.git/commit/?id=56c46222af0d09149fadec2a3ce9d4889de01cc6

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

Title:
  NMI watchdog: BUG: soft lockup during KVM guest migration test suite

Status in linux package in Ubuntu:
  New

Bug description:
  Hello Canonical.

  We would like the changes in Commit 8117ac6a6c2f pulled into the
  Ubuntu 16.10 stream to address the following issue:

  == Comment: #0 - Balamuruhan S - 2016-09-23 08:48:52 ==
  ---Problem Description---

  Softlock up and call trace observed from libvirtd during guest migration test 
suite
   
  ---uname output---

  # uname -a Linux ltc-hab1 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  ---System Hang---
   NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [libvirtd:50800]
   message is continuous and recovered the machine with reboot

  84050.059159] INFO: rcu_sched self-detected stall on CPU
  [84050.059339]24-...: (5659 ticks this GP) idle=fa5/141/0 
softirq=549845/07 fqs=2176 
  [84050.059453] (t=5250 jiffies g=690268 c=690267 q=484)
  [84055.126993] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! 
[libvirtd:50800]
  [84104.509395] INFO: rcu_sched self-detected stall on CPU
  [84104.509591]24-...: (5659 ticks this GP) idle=5df/141/0 
softirq=562249/562249 fqs=2364 
  [84104.509820] (t=5250 jiffies g=690387 c=690386 q=351)
  [84107.125310] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! 
[virsh:56627]
  [84163.387536] INFO: rcu_sched self-detected stall on CPU
  [84163.387716]24-...: (5250 ticks this GP) idle=f69/142/0 
softirq=562274/562274 fqs=2354 
  [84163.387960] (t=5251 jiffies g=690488 c=690487 q=297)
  [84167.123420] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! 
[virsh:56633]
  [84226.401597] INFO: rcu_sched self-detected stall on CPU
  [84226.401769]24-...: (21004 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=9697 
  [84226.402012] (t=21005 jiffies g=690488 c=690487 q=1145)
  [84289.415706] INFO: rcu_sched self-detected stall on CPU
  [84289.415879]24-...: (36758 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=16889 
  [84289.416137] (t=36759 jiffies g=690488 c=690487 q=15499)
  [84352.429857] INFO: rcu_sched self-detected stall on CPU
  [84352.430038]24-...: (52512 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=23975 
  [84352.430269] (t=52513 jiffies g=690488 c=690487 q=16027)
  [84415.444044] INFO: rcu_sched self-detected stall on CPU
  [84415.444222]24-...: (68266 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=31005 
  [84415.34] (t=68267 jiffies g=690488 c=690487 q=16554)
  [84478.458262] INFO: rcu_sched self-detected stall on CPU
  [84478.458421]24-...: (84020 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=38023 
  [84478.458677] (t=84021 jiffies g=690488 c=690487 q=17030)
  [84541.472510] INFO: rcu_sched self-detected stall on CPU
  [84541.472680]24-...: (99774 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=45068 
  [84541.472939] (t=99775 jiffies g=690488 c=690487 q=17512)
  [84604.486783] INFO: rcu_sched self-detected stall on CPU

  
  Thanks.

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

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

[Kernel-packages] [Bug 1636647] Re: perf stat interval display broken on 4.4.x

[Luis Henriques]

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

Title:
  perf stat interval display broken on 4.4.x

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

Bug description:
  perf stat with interval display (-I flag) gives incorrect results
  because the following perf/urgent patch has not been applied.  (It's
  not in upstream longterm 4.4 either.)

  https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
  
stable.git/commit/tools/perf/util/stat.c?id=51fd2df1e882a3c2a3f4b6c9ff243a93c9046dba

  # cat /proc/version_signature
  Ubuntu 4.4.0-34.53-generic 4.4.15

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

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

[Kernel-packages] [Bug 1630554] Re: QEMU throws failure msg while booting guest with SRIOV VF

[Luis Henriques]

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

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

Title:
  QEMU throws failure msg while booting guest with SRIOV VF

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 Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  == Comment: #10 - VIPIN K. PARASHAR  - 2016-10-04 
02:39:30 ==
  (In reply to comment #9)
  > I took a quick look to this one and also noticed these 2 links:
  > https://bugzilla.redhat.com/show_bug.cgi?id=1237034
  > http://marc.info/?l=linux-kernel=143737274332400=2
  > and it looks like to avoid these message maybe just need to have this in
  > config file:
  > CONFIG_KVM_VFIO=y
  > I think we have that in powerkvm but not in Ubuntu KVM.

  On x86 running Ubuntu 16.04
  ==
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial
  $ head /proc/cpuinfo 
  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 61
  model name: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
  stepping  : 4
  microcode : 0x22
  cpu MHz   : 2300.179
  cache size: 3072 KB
  physical id   : 0
  $ uname -a
  Linux Workstation 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  $ grep CONFIG_KVM_VFIO /boot/config-4.4.0-38-generic 
  CONFIG_KVM_VFIO=y
  $

  On PowerPC
   
  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety
  # head /proc/cpuinfo
  processor : 0
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)

  processor : 1
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)

  # uname -a
  Linux c158f2u09os 4.8.0-17-generic #19 SMP Thu Sep 29 12:03:21 CDT 2016 
ppc64le ppc64le ppc64le GNU/Linux
  # grep CONFIG_KVM_VFIO /boot/config-4.8.0-17-generic 
  #

  I see that CONFIG_KVM_VFIO is enabled on x86 running Ubuntu 16.04
  while ppc64 running 16.10 doesn't have it enabled.

  == Comment: #9 - Carol L. Soto  - 2016-09-30 16:25:32 ==
  I took a quick look to this one and also noticed these 2 links:
  https://bugzilla.redhat.com/show_bug.cgi?id=1237034
  http://marc.info/?l=linux-kernel=143737274332400=2
  and it looks like to avoid these message maybe just need to have this in 
config file:
  CONFIG_KVM_VFIO=y
  I think we have that in powerkvm but not in Ubuntu KVM.

  == Comment: #6 - VIPIN K. PARASHAR  - 2016-09-23 
06:50:22 ==
  $ git log 178a787502123b0 -1
  commit 178a787502123b01499c5a4617b94bb69ad49dd5
  Author: David Gibson 
  Date:   Mon Feb 1 11:14:15 2016 +1100

  vfio: Enable VFIO device for powerpc
  
  ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is
  used to handle any necessary interactions between KVM and VFIO.
  
  Currently that device is built on x86 and ARM, but not powerpc, although
  powerpc does support both KVM and VFIO.  This makes things awkward in
  userspace
  
  Currently qemu prints an alarming error message if you attempt to use VFIO
  and it can't initialize the KVM VFIO device.  We don't want to remove the
  warning, because lack of the KVM VFIO device could mean coherency problems
  on x86.  On powerpc, however, the error is harmless but looks disturbing,
  and a test based on host architecture in qemu would be ugly, and break if
  we do need the KVM VFIO device for something important in future.
  
  There's nothing preventing the KVM VFIO device from being built for
  powerpc, so this patch turns it on.  It won't actually do anything, since
  we don't define any of the arch_*() hooks, but it will make qemu happy and
  we can extend it in future if we need to.
  
  Signed-off-by: David Gibson 
  Reviewed-by: Eric Auger 
  Signed-off-by: Paul Mackerras 
  $ 

  $ git describe --contains 178a787502123b
  v4.6-rc1~141^2~49^2~20
  $ 

  
  Commit (178a7875) seems to have enabled VFIO devices for powerpc.
  But this commit should already be available since 4.6 kernel and ubuntu is
  using 4.7 kernel here, so this should be already in.

  
  == Comment: #0 - SRIKANTH B. AITHAL 

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

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David

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

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

[Kernel-packages] [Bug 1639560] Re: linux-image-4.8.0-26-generic causes complete system freeze

[Vianney Stroebel]

Reverting to linux-image-4.8.0-22-generic doesn't fix the issue for me.

I still have random crashes.

Can anyone help?

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

Title:
  linux-image-4.8.0-26-generic causes complete system freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  When using kernel linux-image-4.8.0-26-generic 4.8.0-26.28 and after
  applying latest available updates, the system randomly freezes/hangs
  and a forced shutdown is required. It can be easily reproduced by
  trying to press the "logout" button. The system would immediately
  hang.

  Reverting to previous kernel, 4.8.0-22.24 fixes the issue.

  My hardware is a Dell XPS 13 laptop, model 9343. It has the Intel HD
  graphics card, using i915 module.

  Description:  Ubuntu 16.10
  Release:  16.10

  Thanks!

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

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

[Kernel-packages] [Bug 1640200] [NEW] 16.10 hangs on shutdown

[David]

Public bug reported:

This bug is about my Gateway M1629 not shutting down screen stops at reached . 
I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
Thanks,
David

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

Title:
  16.10 hangs on shutdown

Status in linux package in Ubuntu:
  New

Bug description:
  This bug is about my Gateway M1629 not shutting down screen stops at reached 
. I can reproduce it every time. I also have a problem with booting up ( may be 
related) that has to do with the timing. If I click on ubunto LTS in grub 
screen it boots to a black screen. But if I make it wait by clicking on boot 
options and then back to ubuntu  it boots fine!
  The bug about hanging was reported so many times. I am not sure if is the 
kernel or the bios? too many answers but never one fix! can someone help please?
  Thanks,
  David

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

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

[Kernel-packages] [Bug 1634964] Re: Allow fuse user namespace mounts by default in xenial

[Luis Henriques]

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

Title:
  Allow fuse user namespace mounts by default in xenial

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

Bug description:
  This is a requirement for supporting snaps within lxd containers in
  xenial. It is already allowed in yakkety, so enablement in xenial
  consists of backporting some changes and changing the fuse
  userns_mounts parameter to be enabled by default.

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

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

[Kernel-packages] [Bug 1639961] Re: NMI watchdog: BUG: soft lockup during KVM guest migration test suite

[bugproxy]

** Tags added: bugnameltc-146681 severity-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/1639961

Title:
  NMI watchdog: BUG: soft lockup during KVM guest migration test suite

Status in linux package in Ubuntu:
  New

Bug description:
  Hello Canonical.

  We would like the changes in Commit 8117ac6a6c2f pulled into the
  Ubuntu 16.10 stream to address the following issue:

  == Comment: #0 - Balamuruhan S - 2016-09-23 08:48:52 ==
  ---Problem Description---

  Softlock up and call trace observed from libvirtd during guest migration test 
suite
   
  ---uname output---

  # uname -a Linux ltc-hab1 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  ---System Hang---
   NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [libvirtd:50800]
   message is continuous and recovered the machine with reboot

  84050.059159] INFO: rcu_sched self-detected stall on CPU
  [84050.059339]24-...: (5659 ticks this GP) idle=fa5/141/0 
softirq=549845/07 fqs=2176 
  [84050.059453] (t=5250 jiffies g=690268 c=690267 q=484)
  [84055.126993] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! 
[libvirtd:50800]
  [84104.509395] INFO: rcu_sched self-detected stall on CPU
  [84104.509591]24-...: (5659 ticks this GP) idle=5df/141/0 
softirq=562249/562249 fqs=2364 
  [84104.509820] (t=5250 jiffies g=690387 c=690386 q=351)
  [84107.125310] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! 
[virsh:56627]
  [84163.387536] INFO: rcu_sched self-detected stall on CPU
  [84163.387716]24-...: (5250 ticks this GP) idle=f69/142/0 
softirq=562274/562274 fqs=2354 
  [84163.387960] (t=5251 jiffies g=690488 c=690487 q=297)
  [84167.123420] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! 
[virsh:56633]
  [84226.401597] INFO: rcu_sched self-detected stall on CPU
  [84226.401769]24-...: (21004 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=9697 
  [84226.402012] (t=21005 jiffies g=690488 c=690487 q=1145)
  [84289.415706] INFO: rcu_sched self-detected stall on CPU
  [84289.415879]24-...: (36758 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=16889 
  [84289.416137] (t=36759 jiffies g=690488 c=690487 q=15499)
  [84352.429857] INFO: rcu_sched self-detected stall on CPU
  [84352.430038]24-...: (52512 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=23975 
  [84352.430269] (t=52513 jiffies g=690488 c=690487 q=16027)
  [84415.444044] INFO: rcu_sched self-detected stall on CPU
  [84415.444222]24-...: (68266 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=31005 
  [84415.34] (t=68267 jiffies g=690488 c=690487 q=16554)
  [84478.458262] INFO: rcu_sched self-detected stall on CPU
  [84478.458421]24-...: (84020 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=38023 
  [84478.458677] (t=84021 jiffies g=690488 c=690487 q=17030)
  [84541.472510] INFO: rcu_sched self-detected stall on CPU
  [84541.472680]24-...: (99774 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=45068 
  [84541.472939] (t=99775 jiffies g=690488 c=690487 q=17512)
  [84604.486783] INFO: rcu_sched self-detected stall on CPU

  
  Thanks.

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

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

[Kernel-packages] [Bug 1640194] Re: My LENOVO ideapad 310 WIFI device (Qualcomm) is not showing up in lspci

[Sela Lerer]

** Attachment added: "lspci -vvvx output when the wifi device work properly."
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1640194/+attachment/4774472/+files/lspci_vvvx_when_wifi_works.txt

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

Title:
  My LENOVO ideapad 310 WIFI device (Qualcomm) is not showing up in
  lspci

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I bought a new LENOVO ideapad 310 and installed Ubuntu 16 on it.

  Most of the time, when I turn it on, the WIFI doesn't work. It doesn't
  show up in lspci output. Sometimes it does work, then it does show up
  in lspci output.

  When it does work, it is identified as:

  02:00.0 Network controller: Qualcomm Atheros Device 0042 (rev 30)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.4
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  8 16:31:20 2016
  Dependencies:
   
  InstallationDate: Installed on 2016-10-27 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1640194] [NEW] My LENOVO ideapad 310 WIFI device (Qualcomm) is not showing up in lspci

[Sela Lerer]

Public bug reported:

I bought a new LENOVO ideapad 310 and installed Ubuntu 16 on it.

Most of the time, when I turn it on, the WIFI doesn't work. It doesn't
show up in lspci output. Sometimes it does work, then it does show up in
lspci output.

When it does work, it is identified as:

02:00.0 Network controller: Qualcomm Atheros Device 0042 (rev 30)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.4
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Nov  8 16:31:20 2016
Dependencies:
 
InstallationDate: Installed on 2016-10-27 (11 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "lspci -vvvx output when the wifi device doesn't work."
   
https://bugs.launchpad.net/bugs/1640194/+attachment/4774469/+files/lspci_vvvx_when_wifi_broken.txt

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

Title:
  My LENOVO ideapad 310 WIFI device (Qualcomm) is not showing up in
  lspci

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I bought a new LENOVO ideapad 310 and installed Ubuntu 16 on it.

  Most of the time, when I turn it on, the WIFI doesn't work. It doesn't
  show up in lspci output. Sometimes it does work, then it does show up
  in lspci output.

  When it does work, it is identified as:

  02:00.0 Network controller: Qualcomm Atheros Device 0042 (rev 30)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.4
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  8 16:31:20 2016
  Dependencies:
   
  InstallationDate: Installed on 2016-10-27 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1591618] Re: [Feature] KBL - New device ID for Kabypoint(KbP)

[Luis Henriques]

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

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

Title:
  [Feature] KBL - New device ID for Kabypoint(KbP)

Status in intel:
  In Progress
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 Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  identify what new device IDs are required for Kabypoint (KBP): HS-
  UART,SPI, I2C, SMBUS,SPI-NOR,NPK,xHCI,usb device, SD

  Platform: Kabylake-S with Kabypoint PCH

  upstream schedule: 4.9

  X-HWE-Bug: Bug #1622469

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

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

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

Title:
  Need a patched 4.9 kernel to compile nvidia drivers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As the unstable kernel ppa now has 4.9 kernel, i've installed it on a
  system using a nvidia-370/375 driver, but both fails at compile dkms
  time.

  This is an identified problem and a proposed patch is already ready:
  
https://devtalk.nvidia.com/default/topic/972761/linux/linux-4-9-git-rc1-375-10-build-errors/

  Could the kernel team include that patch as there is no workable
  nvidia driver yet ?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1777 F pulseaudio
   /dev/snd/controlC0:  oem1777 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Nov  8 15:01:20 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth1  no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Kernel-packages] [Bug 1637565] Re: nvme: improve performance for virtual Google NVMe devices

[Tim Gardner]

Yakkety patch submitted - 
https://lists.ubuntu.com/archives/kernel-team/2016-November/080751.html
Test image results were, "That image looks good, IOPs goes up, up, up, and 
nothing blows up.".

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

Title:
  nvme: improve performance for virtual Google NVMe devices

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

Bug description:
  This change provides a mechanism to reduce the number of MMIO doorbell writes 
for the NVMe driver. When running in a virtualized environment like QEMU, the 
cost of an MMIO is quite hefy here. The main idea for the patch is provide the 
device two memory location locations:
   1) to store the doorbell values so they can be lookup without the 
doorbell
  MMIO write
   2) to store an event index.
  I believe the doorbell value is obvious, the event index not so much. Similar 
to the virtio specificaiton, the virtual device can tell the driver (guest OS) 
not to write MMIO unless you are writing past this value.
  
  FYI: doorbell values are written by the nvme driver (guest OS) and the event 
index is written by the virtual device (host OS).
  
  The patch implements a new admin command that will communicate where these 
two memory locations reside. If the command fails, the nvme driver will work as 
before without any optimizations.

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

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

[Kernel-packages] [Bug 1640181] [NEW] Need a patched 4.9 kernel to compile nvidia drivers

[dino99]

Public bug reported:

As the unstable kernel ppa now has 4.9 kernel, i've installed it on a
system using a nvidia-370/375 driver, but both fails at compile dkms
time.

This is an identified problem and a proposed patch is already ready:
https://devtalk.nvidia.com/default/topic/972761/linux/linux-4-9-git-rc1-375-10-build-errors/

Could the kernel team include that patch as there is no workable nvidia
driver yet ?

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.8.0-27-generic 4.8.0-27.29
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  oem1777 F pulseaudio
 /dev/snd/controlC0:  oem1777 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Nov  8 15:01:20 2016
HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
IwConfig:
 eth1  no wireless extensions.
 
 lono wireless extensions.
 
 eth0  no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-27-generic N/A
 linux-backports-modules-4.8.0-27-generic  N/A
 linux-firmware1.161
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

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


** Tags: amd64 apport-bug package-from-proposed zesty

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

Title:
  Need a patched 4.9 kernel to compile nvidia drivers

Status in linux package in Ubuntu:
  New

Bug description:
  As the unstable kernel ppa now has 4.9 kernel, i've installed it on a
  system using a nvidia-370/375 driver, but both fails at compile dkms
  time.

  This is an identified problem and a proposed patch is already ready:
  
https://devtalk.nvidia.com/default/topic/972761/linux/linux-4-9-git-rc1-375-10-build-errors/

  Could the kernel team include that patch as there is no workable
  nvidia driver yet ?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.8.0-27-generic 4.8.0-27.29
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1777 F pulseaudio
   /dev/snd/controlC0:  oem1777 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Nov  8 15:01:20 2016
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth1  no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-27-generic N/A
   linux-backports-modules-4.8.0-27-generic  N/A
   linux-firmware1.161
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  

[Kernel-packages] [Bug 1639961] Re: NMI watchdog: BUG: soft lockup during KVM guest migration test suite

[Tim Gardner]

I am confused. Commit 8117ac6a6c2fa0f847ff6a21a1f32c8d2c8501d0
('powerpc/powernv: Switch off MMU before entering nap/sleep/rvwinkle
mode') has been in the kernel for awhile.

git describe --contains 8117ac6a6c2f
v3.19-rc1~22^2~6

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

Title:
  NMI watchdog: BUG: soft lockup during KVM guest migration test suite

Status in linux package in Ubuntu:
  New

Bug description:
  Hello Canonical.

  We would like the changes in Commit 8117ac6a6c2f pulled into the
  Ubuntu 16.10 stream to address the following issue:

  == Comment: #0 - Balamuruhan S - 2016-09-23 08:48:52 ==
  ---Problem Description---

  Softlock up and call trace observed from libvirtd during guest migration test 
suite
   
  ---uname output---

  # uname -a Linux ltc-hab1 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:58:16 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  ---System Hang---
   NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! [libvirtd:50800]
   message is continuous and recovered the machine with reboot

  84050.059159] INFO: rcu_sched self-detected stall on CPU
  [84050.059339]24-...: (5659 ticks this GP) idle=fa5/141/0 
softirq=549845/07 fqs=2176 
  [84050.059453] (t=5250 jiffies g=690268 c=690267 q=484)
  [84055.126993] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! 
[libvirtd:50800]
  [84104.509395] INFO: rcu_sched self-detected stall on CPU
  [84104.509591]24-...: (5659 ticks this GP) idle=5df/141/0 
softirq=562249/562249 fqs=2364 
  [84104.509820] (t=5250 jiffies g=690387 c=690386 q=351)
  [84107.125310] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! 
[virsh:56627]
  [84163.387536] INFO: rcu_sched self-detected stall on CPU
  [84163.387716]24-...: (5250 ticks this GP) idle=f69/142/0 
softirq=562274/562274 fqs=2354 
  [84163.387960] (t=5251 jiffies g=690488 c=690487 q=297)
  [84167.123420] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 22s! 
[virsh:56633]
  [84226.401597] INFO: rcu_sched self-detected stall on CPU
  [84226.401769]24-...: (21004 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=9697 
  [84226.402012] (t=21005 jiffies g=690488 c=690487 q=1145)
  [84289.415706] INFO: rcu_sched self-detected stall on CPU
  [84289.415879]24-...: (36758 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=16889 
  [84289.416137] (t=36759 jiffies g=690488 c=690487 q=15499)
  [84352.429857] INFO: rcu_sched self-detected stall on CPU
  [84352.430038]24-...: (52512 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=23975 
  [84352.430269] (t=52513 jiffies g=690488 c=690487 q=16027)
  [84415.444044] INFO: rcu_sched self-detected stall on CPU
  [84415.444222]24-...: (68266 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=31005 
  [84415.34] (t=68267 jiffies g=690488 c=690487 q=16554)
  [84478.458262] INFO: rcu_sched self-detected stall on CPU
  [84478.458421]24-...: (84020 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=38023 
  [84478.458677] (t=84021 jiffies g=690488 c=690487 q=17030)
  [84541.472510] INFO: rcu_sched self-detected stall on CPU
  [84541.472680]24-...: (99774 ticks this GP) 
idle=f69/142/0 softirq=562274/562274 fqs=45068 
  [84541.472939] (t=99775 jiffies g=690488 c=690487 q=17512)
  [84604.486783] INFO: rcu_sched self-detected stall on CPU

  
  Thanks.

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

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

[Kernel-packages] [Bug 1636941] Re: linux: 4.4.0-47.68 -proposed tracker

[Brad Figg]

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

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

** Changed in: kernel-sru-workflow/promote-to-updates
   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/1636941

Title:
  linux: 4.4.0-47.68 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-47.68 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-sru-workflow/+bug/1636941/+subscriptions

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

[Kernel-packages] [Bug 1635242] Re: linux: 4.4.0-46.67 -proposed tracker

[Luis Henriques]

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

** This bug has been marked a duplicate of bug 1636941
   linux: 4.4.0-47.68 -proposed tracker

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

Title:
  linux: 4.4.0-46.67 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-46.67 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/1635242/+subscriptions

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

[Kernel-packages] [Bug 1633414] Re: linux: 4.4.0-44.64 -proposed tracker

[Luis Henriques]

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

** This bug is no longer a duplicate of bug 1635242
   linux: 4.4.0-46.67 -proposed tracker
** This bug has been marked a duplicate of bug 1636941
   linux: 4.4.0-47.68 -proposed tracker

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

Title:
  linux: 4.4.0-44.64 -proposed tracker

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

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

[Kernel-packages] [Bug 1636941] Re: linux: 4.4.0-47.68 -proposed tracker

[Luis Henriques]

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

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

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => 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/1636941

Title:
  linux: 4.4.0-47.68 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-47.68 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-sru-workflow/+bug/1636941/+subscriptions

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

[Kernel-packages] [Bug 1563229] Re: Touchpad recognised as mouse FTE1000

[Onur Ozan Yüksel]

Hello have an update; 
I can now use scroll on touch screen and pinch zoom also works but only in 
chrome not other applications. Probably chrome uses a different approach. It 
can be a lead. Also there is no advance on touch pad still acts as mouse.

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

Title:
  Touchpad recognised as mouse FTE1000

Status in linux package in Ubuntu:
  Triaged
Status in xinput package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Triaged
Status in xinput source package in Trusty:
  Confirmed
Status in linux source package in Wily:
  Triaged
Status in xinput source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Triaged
Status in xinput source package in Xenial:
  Confirmed

Bug description:
  In my Asus e200ha touchpad is recognized as mouse, only one click, no
  two finger click and scrolling

  Xinput say:
  FTE1000:00 0B05:0101   id=12[slave pointer (2)]

  i've tried:
  - ubuntu 14.04 with stock kernel
  - ubuntu 14.04 with 4.6rc1 kernel
  - Linux mint 17.3 with stock kernel
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: xinput 1.6.1-1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1638788] Re: [MacBookAir5, 2] Resumes immediately after suspend

[Ketil]

Sad news since the XHC1 fixes it for me... Must be two bugs then...
Ketil

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

Title:
  [MacBookAir5,2] Resumes immediately after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  with default settings the laptop will immediately resume after sending
  to sleep (regardless of by closing the LID or though the menu option
  "suspend")

  the workaround is disabling the LID ACPI action by running:

  echo LID0 >/proc/acpi/wakeup

  this will fix the problem. obviously however just simply opening the
  lid won't wake the laptop anymore. so one has to manually press the
  power button.

  (I used ubuntu-bug linux, so hopefully all info should be attached)
  I'm running out of the box, up2date yakkety. without any external
  repos or custom compiled applications

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-26-generic 4.8.0-26.28
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  toby   2327 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov  2 21:49:50 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ba2577eb-f563-46c3-adb9-47967c8c5851
  InstallationDate: Installed on 2016-10-17 (16 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Apple Inc. MacBookAir5,2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic.efi.signed 
root=UUID=add8c949-ae19-4310-aede-4a9007ea7514 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-generic N/A
   linux-backports-modules-4.8.0-26-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B04.1509111654
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B04.1509111654:bd09/11/2015:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.name: MacBookAir5,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1640109] Re: hv_set_ifconfig script parsing fails for certain configuration

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  hv_set_ifconfig script parsing fails for certain configuration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to configure a virtual NIC to DHCP with no IPv6 addresses using 
Hyper-V's integration services, a configuration file similar to the following 
is generated:
  HWADDR=XX:YY:ZZ
  DEVICE=eth0
  BOOTPROTO=dhcp

  When running the hv_set_ifconfig script with this script as an argument 
(executed by IS, most likely the KVP daemon; I ran it manually in order to 
debug), it fails with the following stderr (stderr is muted, the script must be 
edited to retrieve this information, so the line number is offset):
    File "hv_set_ifconfig", line 171, in 
  output = ["auto "+" ".join(autolist)] + output
  NameError: name 'autolist' is not defined

  Editing the script so that autolist is defined in all flows resolves
  the issue and the script successfully sets the interface to use DHCP

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-cloud-tools-virtual 4.4.0.45.48
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Nov  7 16:50 seq
   crw-rw+ 1 root audio 116, 33 Nov  7 16:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  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: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Nov  7 17:21:05 2016
  HibernationDevice: RESUME=UUID=c9cdd190-7007-4e48-9833-1790d9a80017
  InstallationDate: Installed on 2016-10-13 (25 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PciMultimedia:

  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=fa675999-88b8-495e-9153-3621a2b3dce1 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 1923-5120-7734-2680-0264-8714-27
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1634449] Re: Black flicker when leaving monitor

[MisterZ]

Same problem here. Using triple screen (laptop + 2 external monitors) on
a Lenovo ThinkPad t460s.

Monitor on display port is turning black for 2-5 seconds on cursor
movement or focus changes with alt+tab.

OS: Ubuntu 16.10 amd64
Kernel: 4.8.0-26
CPU: Intel Core i7-6600U 
GPU: Intel HD Graphics 520 (Skylake GT2) 

Totally related to the fact that Intel didn't make available the latest drivers 
for yakkety. You can't even get them with the updater because it's not 
mentioned in here:
https://download.01.org/gfx/ilg-config.cfg

There is simply no 16.10 repo:
https://download.01.org/gfx/repos/ubuntu/

Two possible fix I found for now:

- Use the kernel 4.6.7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6.7/
- Use the drm-intel-nightly kernel 4.9.0-994: 
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/
==> there is no amd64 successful build available anymore, last was 201610192310

Drawback: I don't have the linux-image-extra for those kernels so I
don't have aufs for docker.

I had no issues whatsoever on Ubuntu 16.04 LTS with kernel 4.4.x

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

Title:
  Black flicker when leaving monitor

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Sometimes, when moving cursor from one monitor to the other, the
  external monitor turns black and gets back on again.

  The hardware is Dell Latitude E5470 with Docking Station and monitor
  connected via DisplayPort (checked both ports and happens on both of
  them).

  Everything worked correctly on Ubuntu 16.04, but it happens on Ubuntu
  16.10. Kernel 4.8.0-25-generic.

  The bug isn't related to cursor only, if focus changes by alt+tab it
  sometimes happens as well.

  
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553503 This is the same 
bug as this one, but closed.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   vessel 5602 F...m pulseaudio
   /dev/snd/controlC0:  vessel 5602 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=56fab9c8-7226-47b9-91cb-a2c865f81bc0
  InstallationDate: Installed on 2016-08-31 (47 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5470
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-25-generic N/A
   linux-backports-modules-4.8.0-25-generic  N/A
   linux-firmware1.161
  Tags:  yakkety
  Uname: Linux 4.8.0-25-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.3
  dmi.board.name: 0P88J9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0P88J9:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5470
  dmi.sys.vendor: Dell Inc.

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

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

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

Title:
  hv_set_ifconfig script parsing fails for certain configuration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to configure a virtual NIC to DHCP with no IPv6 addresses using 
Hyper-V's integration services, a configuration file similar to the following 
is generated:
  HWADDR=XX:YY:ZZ
  DEVICE=eth0
  BOOTPROTO=dhcp

  When running the hv_set_ifconfig script with this script as an argument 
(executed by IS, most likely the KVP daemon; I ran it manually in order to 
debug), it fails with the following stderr (stderr is muted, the script must be 
edited to retrieve this information, so the line number is offset):
    File "hv_set_ifconfig", line 171, in 
  output = ["auto "+" ".join(autolist)] + output
  NameError: name 'autolist' is not defined

  Editing the script so that autolist is defined in all flows resolves
  the issue and the script successfully sets the interface to use DHCP

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-cloud-tools-virtual 4.4.0.45.48
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Nov  7 16:50 seq
   crw-rw+ 1 root audio 116, 33 Nov  7 16:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  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: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Nov  7 17:21:05 2016
  HibernationDevice: RESUME=UUID=c9cdd190-7007-4e48-9833-1790d9a80017
  InstallationDate: Installed on 2016-10-13 (25 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PciMultimedia:

  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=fa675999-88b8-495e-9153-3621a2b3dce1 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 1923-5120-7734-2680-0264-8714-27
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1640109] Re: hv_set_ifconfig script parsing fails for certain configuration

[Yonatan Amir]

** Description changed:

- When trying to configure DHCP with no IPv6 addresses, a configuration file 
similar to the following is generated:
+ When trying to configure a virtual NIC to DHCP with no IPv6 addresses using 
Hyper-V's integration services, a configuration file similar to the following 
is generated:
  HWADDR=XX:YY:ZZ
  DEVICE=eth0
  BOOTPROTO=dhcp
  
- When running the hv_set_ifconfig script with this script as an argument, it 
fails with the following stderr (stderr is muted, the script must be edited to 
retrieve this information, so the line number is offset):
-   File "hv_set_ifconfig", line 171, in 
- output = ["auto "+" ".join(autolist)] + output
+ When running the hv_set_ifconfig script with this script as an argument 
(executed by IS, most likely the KVP daemon; I ran it manually in order to 
debug), it fails with the following stderr (stderr is muted, the script must be 
edited to retrieve this information, so the line number is offset):
+   File "hv_set_ifconfig", line 171, in 
+ output = ["auto "+" ".join(autolist)] + output
  NameError: name 'autolist' is not defined
  
- 
- Editing the script so that autolist is defined in all flows resolves the 
issue and the script successfully sets the interface to use DHCP
+ Editing the script so that autolist is defined in all flows resolves the
+ issue and the script successfully sets the interface to use DHCP
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-cloud-tools-virtual 4.4.0.45.48
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  AlsaDevices:
-  total 0
-  crw-rw+ 1 root audio 116,  1 Nov  7 16:50 seq
-  crw-rw+ 1 root audio 116, 33 Nov  7 16:50 timer
+  total 0
+  crw-rw+ 1 root audio 116,  1 Nov  7 16:50 seq
+  crw-rw+ 1 root audio 116, 33 Nov  7 16:50 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  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: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon Nov  7 17:21:05 2016
  HibernationDevice: RESUME=UUID=c9cdd190-7007-4e48-9833-1790d9a80017
  InstallationDate: Installed on 2016-10-13 (25 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  PciMultimedia:
-  
+ 
  ProcEnviron:
-  TERM=linux
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  LANGUAGE=en_US:en
-  SHELL=/bin/bash
+  TERM=linux
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  LANGUAGE=en_US:en
+  SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=fa675999-88b8-495e-9153-3621a2b3dce1 ro
  RelatedPackageVersions:
-  linux-restricted-modules-4.4.0-45-generic N/A
-  linux-backports-modules-4.4.0-45-generic  N/A
-  linux-firmware1.157.4
+  linux-restricted-modules-4.4.0-45-generic N/A
+  linux-backports-modules-4.4.0-45-generic  N/A
+  linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 1923-5120-7734-2680-0264-8714-27
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

** Tags added: hyperv

** Tags added: hyper-v

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

Title:
  hv_set_ifconfig script parsing fails for certain configuration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to configure a virtual NIC to DHCP with no IPv6 addresses using 
Hyper-V's integration services, a configuration file similar to the following 
is generated:
  HWADDR=XX:YY:ZZ
  DEVICE=eth0
  BOOTPROTO=dhcp

  When running the hv_set_ifconfig script with this script as an argument 
(executed by IS, most likely the KVP daemon; I ran it manually in order to 
debug), it fails with the following stderr (stderr is muted, the script must be 

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

[muzzol]

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

I just hit this bug and it's really a stopper for me.

I'll downgrade kernel until is resolved.

-- 
You 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:
  Incomplete

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