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

2017-06-16 Thread Joseph Salisbury
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/1698508

Title:
  package linux-image-4.10.0-22-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i am also getting issue with "suspend"
  when i click on suspend 
  it doest start back when i turn it on , it desnt even show a console mode 
besides a blank black screen
  i was also getting this issue in 16.04 and now in 17.04 too
  my specs
  lenovo ideapad  z50
  intel i5 4th gen 2 cores
  8gb ram
  2gb nvidia geforce 820m 
  1 tb hdd
  1080p display

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mubix  1783 F pulseaudio
   /dev/snd/controlC1:  mubix  1783 F pulseaudio
  Date: Sat Jun 17 10:19:46 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-14 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20354
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=ed70addc-4319-4c31-9bdf-3c12bddf4af8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  SourcePackage: linux
  Title: package linux-image-4.10.0-22-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1698508] Re: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-06-16 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.10.0-22-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  i am also getting issue with "suspend"
  when i click on suspend 
  it doest start back when i turn it on , it desnt even show a console mode 
besides a blank black screen
  i was also getting this issue in 16.04 and now in 17.04 too
  my specs
  lenovo ideapad  z50
  intel i5 4th gen 2 cores
  8gb ram
  2gb nvidia geforce 820m 
  1 tb hdd
  1080p display

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mubix  1783 F pulseaudio
   /dev/snd/controlC1:  mubix  1783 F pulseaudio
  Date: Sat Jun 17 10:19:46 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-14 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20354
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=ed70addc-4319-4c31-9bdf-3c12bddf4af8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  SourcePackage: linux
  Title: package linux-image-4.10.0-22-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1698508] [NEW] package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-06-16 Thread Govind Thakre
Public bug reported:

i am also getting issue with "suspend"
when i click on suspend 
it doest start back when i turn it on , it desnt even show a console mode 
besides a blank black screen
i was also getting this issue in 16.04 and now in 17.04 too
my specs
lenovo ideapad  z50
intel i5 4th gen 2 cores
8gb ram
2gb nvidia geforce 820m 
1 tb hdd
1080p display

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-22-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mubix  1783 F pulseaudio
 /dev/snd/controlC1:  mubix  1783 F pulseaudio
Date: Sat Jun 17 10:19:46 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
InstallationDate: Installed on 2017-06-14 (2 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 20354
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=ed70addc-4319-4c31-9bdf-3c12bddf4af8 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
SourcePackage: linux
Title: package linux-image-4.10.0-22-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 9BCN29WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 5A5
dmi.board.vendor: LENOVO
dmi.board.version: NANANANANO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Z50-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoZ50-70:
dmi.product.name: 20354
dmi.product.version: Lenovo Z50-70
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package 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/1698508

Title:
  package linux-image-4.10.0-22-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  i am also getting issue with "suspend"
  when i click on suspend 
  it doest start back when i turn it on , it desnt even show a console mode 
besides a blank black screen
  i was also getting this issue in 16.04 and now in 17.04 too
  my specs
  lenovo ideapad  z50
  intel i5 4th gen 2 cores
  8gb ram
  2gb nvidia geforce 820m 
  1 tb hdd
  1080p display

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mubix  1783 F pulseaudio
   /dev/snd/controlC1:  mubix  1783 F pulseaudio
  Date: Sat Jun 17 10:19:46 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-14 (2 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20354
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=ed70addc-4319-4c31-9bdf-3c12bddf4af8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  SourcePackage: linux
  Title: package linux-image-4.10.0-22-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

To manage notifications about this 

[Kernel-packages] [Bug 1661292] Re: VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-block(0, 0): error -6

2017-06-16 Thread 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/1661292

Title:
  VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-
  block(0,0): error -6

Status in OpenStack Compute (nova):
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  Description
  ===
  An kvm instance failed to boot with a kernel panic after hitting this error:

  VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-
  block(0,0): error -6

  Steps to reproduce
  ==
  This doesn't reproduce reliably, it seems to be a race condition.

  * I started an instance through the API.  It had not attached storage,
  and was attached to a single network. It used an Ubuntu Xenial cloud
  image which booted successfully on a different instance on a different
  compute node.

  Expected Result
  ===
  * I expected the instance to boot successfully

  Actual Result
  =
  * The instance failed to boot with a kernel panic:
  http://pastebin.ubuntu.com/23911493/

  * I used virsh destroy to stop that instance, then started it again
  through the API, and it worked.

  Environment
  ===
  xenial/newtown/kvm/openvswitch, no attached storage.

  ii  nova-common  2:14.0.1-0ubuntu1~cloud0
all  OpenStack Compute - common files
  ii  nova-compute 2:14.0.1-0ubuntu1~cloud0
all  OpenStack Compute - compute node base
  ii  nova-compute-kvm 2:14.0.1-0ubuntu1~cloud0
all  OpenStack Compute - compute node (KVM)
  ii  nova-compute-libvirt 2:14.0.1-0ubuntu1~cloud0
all  OpenStack Compute - compute node libvirt support
  ii  python-nova  2:14.0.1-0ubuntu1~cloud0
all  OpenStack Compute Python libraries
  ii  python-novaclient2:6.0.0-0ubuntu1~cloud0 
all  client library for OpenStack Compute API - Python 2.7
  ii  libvirt-bin  1.3.1-1ubuntu10.6   
amd64programs for the libvirt library
  ii  libvirt0:amd64   1.3.1-1ubuntu10.6   
amd64library for interfacing with different virtualization systems
  ii  nova-compute-libvirt 2:14.0.1-0ubuntu1~cloud0
all  OpenStack Compute - compute node libvirt support
  ii  python-libvirt   1.3.1-1ubuntu1  
amd64libvirt Python bindings

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

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


[Kernel-packages] [Bug 1682339] Re: package linux-headers-3.13.0-116 3.13.0-116.163 failed to install/upgrade: package linux-headers-3.13.0-116 is not ready for configuration cannot configure (current

2017-06-16 Thread 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/1682339

Title:
  package linux-headers-3.13.0-116 3.13.0-116.163 failed to
  install/upgrade: package linux-headers-3.13.0-116 is not ready for
  configuration  cannot configure (current status `half-installed')

Status in linux package in Ubuntu:
  Expired

Bug description:
  Screen gets crashed repeatedly

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-headers-3.13.0-116 3.13.0-116.163
  ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-116-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  AptOrdering:
   neovim: Install
   linux-headers-3.13.0-116: Configure
   neovim: Configure
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  varun  3367 F pulseaudio
   /dev/snd/controlC1:  varun  3367 F pulseaudio
  CRDA:
   country IN:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5735 - 5835 @ 40), (N/A, 20)
  Date: Thu Apr 13 10:36:14 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DuplicateSignature: package:linux-headers-3.13.0-116:3.13.0-116.163:package 
linux-headers-3.13.0-116 is not ready for configuration  cannot configure 
(current status `half-installed')
  ErrorMessage: package linux-headers-3.13.0-116 is not ready for configuration 
 cannot configure (current status `half-installed')
  HibernationDevice: RESUME=UUID=577af156-943f-4d6d-8660-b018d4fb0c00
  InstallationDate: Installed on 2016-03-21 (387 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Inspiron 3543
  PackageArchitecture: all
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-116-generic 
root=UUID=2bb534c3-dee8-4ab2-9aa7-cc79e16e202d ro quiet splash 
video.use_native_backlight=1 vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12
  SourcePackage: linux
  StagingDrivers: rts5139
  Title: package linux-headers-3.13.0-116 3.13.0-116.163 failed to 
install/upgrade: package linux-headers-3.13.0-116 is not ready for 
configuration  cannot configure (current status `half-installed')
  UpgradeStatus: Upgraded to trusty on 2016-03-21 (387 days ago)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd10/16/2015:svnDellInc.:pnInspiron3543:pvrA07:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3543
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1661292] Re: VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-block(0, 0): error -6

2017-06-16 Thread Launchpad Bug Tracker
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
   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/1661292

Title:
  VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-
  block(0,0): error -6

Status in OpenStack Compute (nova):
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  Description
  ===
  An kvm instance failed to boot with a kernel panic after hitting this error:

  VFS: Cannot open root device "LABEL=cloudimg-rootfs" or unknown-
  block(0,0): error -6

  Steps to reproduce
  ==
  This doesn't reproduce reliably, it seems to be a race condition.

  * I started an instance through the API.  It had not attached storage,
  and was attached to a single network. It used an Ubuntu Xenial cloud
  image which booted successfully on a different instance on a different
  compute node.

  Expected Result
  ===
  * I expected the instance to boot successfully

  Actual Result
  =
  * The instance failed to boot with a kernel panic:
  http://pastebin.ubuntu.com/23911493/

  * I used virsh destroy to stop that instance, then started it again
  through the API, and it worked.

  Environment
  ===
  xenial/newtown/kvm/openvswitch, no attached storage.

  ii  nova-common  2:14.0.1-0ubuntu1~cloud0
all  OpenStack Compute - common files
  ii  nova-compute 2:14.0.1-0ubuntu1~cloud0
all  OpenStack Compute - compute node base
  ii  nova-compute-kvm 2:14.0.1-0ubuntu1~cloud0
all  OpenStack Compute - compute node (KVM)
  ii  nova-compute-libvirt 2:14.0.1-0ubuntu1~cloud0
all  OpenStack Compute - compute node libvirt support
  ii  python-nova  2:14.0.1-0ubuntu1~cloud0
all  OpenStack Compute Python libraries
  ii  python-novaclient2:6.0.0-0ubuntu1~cloud0 
all  client library for OpenStack Compute API - Python 2.7
  ii  libvirt-bin  1.3.1-1ubuntu10.6   
amd64programs for the libvirt library
  ii  libvirt0:amd64   1.3.1-1ubuntu10.6   
amd64library for interfacing with different virtualization systems
  ii  nova-compute-libvirt 2:14.0.1-0ubuntu1~cloud0
all  OpenStack Compute - compute node libvirt support
  ii  python-libvirt   1.3.1-1ubuntu1  
amd64libvirt Python bindings

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

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


[Kernel-packages] [Bug 1682230] Re: Wifi usb stick and cordless keyboard and mouse freeze system

2017-06-16 Thread 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/1682230

Title:
  Wifi usb stick and cordless keyboard and mouse freeze system

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,
  For kernels 4.4, using a usb wifi dongle (0bda:8178 Realtek Semiconductor 
Corp. RTL8192CU 802.11n WLAN Adapter) and a cordless mouse/keyboard (1d57:fa20 
Xenta ) freeze the system.
  With 4.8.0-36 kernel, all is fine. 
  With update 4.8.0-46, the system freeze.

  lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alain  1671 F pulseaudio
   /dev/snd/controlC0:  alain  1671 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8185182f-9ef4-421b-afca-6589e86759dc
  InstallationDate: Installed on 2017-04-09 (3 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=4d6d30b5-6ba4-4b58-b88f-62b2ea234e34 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 01/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A78M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/19/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1682826] Re: package linux-image-4.10.0-19-generic (not installed) failed to install/upgrade: il sottoprocesso nuovo script pre-installation ha restituito lo stato di errore 1

2017-06-16 Thread 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/1682826

Title:
  package linux-image-4.10.0-19-generic (not installed) failed to
  install/upgrade: il sottoprocesso nuovo script pre-installation ha
  restituito lo stato di errore 1

Status in linux package in Ubuntu:
  Expired

Bug description:
  applicazione package_hook si è chiusa inaspettatamente

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic i686
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  franco 1668 F pulseaudio
  Date: Fri Apr 14 12:10:14 2017
  ErrorMessage: il sottoprocesso nuovo script pre-installation ha restituito lo 
stato di errore 1
  HibernationDevice: RESUME=UUID=d3610d43-b5ee-4802-9e06-32dfd1ff02ae
  MachineType: FUJITSU SIEMENS Amilo M1425
  PccardctlIdent:
   Socket 0:
 no product info available
   Socket 1:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
   Socket 1:
 no card
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=1eab16de-2aa9-4775-96ab-65c3d483067a ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-19-generic (not installed) failed to 
install/upgrade: il sottoprocesso nuovo script pre-installation ha restituito 
lo stato di errore 1
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)
  dmi.bios.date: 12/29/2004
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080010
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080010:bd12/29/2004:svnFUJITSUSIEMENS:pnAmiloM1425:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Amilo M1425
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: FUJITSU SIEMENS

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

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


[Kernel-packages] [Bug 1682660] Re: Portait mode rotation on 2-in-1 is upside down

2017-06-16 Thread 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/1682660

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Expired

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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


[Kernel-packages] [Bug 1682916] Re: WARNING: CPU: 3 PID: 429 at /build/linux-Fk60NP/linux-4.10.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1891 iwl_trans_pcie_grab_nic_access+0xeb/0xf0 [iwlwifi]

2017-06-16 Thread 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/1682916

Title:
  WARNING: CPU: 3 PID: 429 at /build/linux-
  Fk60NP/linux-4.10.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1891
  iwl_trans_pcie_grab_nic_access+0xeb/0xf0 [iwlwifi]

Status in linux package in Ubuntu:
  Expired

Bug description:
  [ 1371.109885] [ cut here ]
  [ 1371.109913] WARNING: CPU: 3 PID: 429 at 
/build/linux-Fk60NP/linux-4.10.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1891
 iwl_trans_pcie_grab_nic_access+0xeb/0xf0 [iwlwifi]
  [ 1371.109915] Timeout waiting for hardware access (CSR_GP_CNTRL 0x080003d8)
  [ 1371.109917] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter bnep binfmt_misc uvcvideo videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_core videodev samsung_laptop btusb 
btrtl intel_rapl btbcm btintel x86_pkg_temp_thermal intel_powerclamp bluetooth 
media coretemp snd_hda_codec_hdmi kvm_intel snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_intel kvm snd_hda_codec irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel usblp snd_hda_core cryptd 
snd_hwdep intel_cstate intel_rapl_perf input_leds joydev snd_pcm arc4 serio_raw 
snd_seq_midi
  [ 1371.109995]  snd_seq_midi_event iwldvm mac80211 snd_rawmidi snd_seq 
iwlwifi lpc_ich snd_seq_device snd_timer cfg80211 snd shpchp mei_me mei 
soundcore dell_smo8800 mac_hid parport_pc ppdev lp parport ip_tables x_tables 
autofs4 btrfs xor raid6_pq hid_generic usbhid hid i915 i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm ahci 
r8169 libahci mii wmi fjes video
  [ 1371.110055] CPU: 3 PID: 429 Comm: irq/29-iwlwifi Not tainted 
4.10.0-19-generic #21-Ubuntu
  [ 1371.110057] Hardware name: SAMSUNG ELECTRONICS CO., LTD. 
530U3C/530U4C/SAMSUNG_NP1234567890, BIOS P14AAJ 04/15/2013
  [ 1371.110059] Call Trace:
  [ 1371.110070]  dump_stack+0x63/0x81
  [ 1371.110075]  __warn+0xcb/0xf0
  [ 1371.110079]  warn_slowpath_fmt+0x5f/0x80
  [ 1371.110092]  ? iwl_read32+0x1f/0x80 [iwlwifi]
  [ 1371.110107]  iwl_trans_pcie_grab_nic_access+0xeb/0xf0 [iwlwifi]
  [ 1371.110119]  iwl_read_direct32+0x32/0x80 [iwlwifi]
  [ 1371.110132]  iwl_dump_fh+0x268/0x390 [iwlwifi]
  [ 1371.110147]  iwl_pcie_irq_handle_error+0x39/0x160 [iwlwifi]
  [ 1371.110160]  iwl_pcie_irq_handler+0x3ae/0xa90 [iwlwifi]
  [ 1371.110167]  ? irq_finalize_oneshot.part.35+0xf0/0xf0
  [ 1371.110171]  irq_thread_fn+0x20/0x50
  [ 1371.110175]  irq_thread+0x12f/0x1c0
  [ 1371.110180]  ? __schedule+0x23b/0x6f0
  [ 1371.110185]  ? irq_forced_thread_fn+0x70/0x70
  [ 1371.110193]  kthread+0x101/0x140
  [ 1371.110197]  ? irq_affinity_notify+0x130/0x130
  [ 1371.110202]  ? kthread_create_on_node+0x60/0x60
  [ 1371.110208]  ? SyS_exit_group+0x14/0x20
  [ 1371.110213]  ret_from_fork+0x2c/0x40
  [ 1371.110218] ---[ end trace 5b7698dd06ffed08 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2009 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Apr 14 16:54:41 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (628 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 

[Kernel-packages] [Bug 1682440] Re: package linux-image-4.4.0-72-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 2

2017-06-16 Thread 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/1682440

Title:
  package linux-image-4.4.0-72-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 2

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm enable to download something!! please help me!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-72-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brice  1726 F pulseaudio
  Date: Thu Apr 13 13:42:33 2017
  DpkgHistoryLog:
   Start-Date: 2017-04-13  13:42:32
   Commandline: apt install -f
   Requested-By: brice (1000)
   Install: linux-headers-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic), 
linux-headers-4.4.0-72:amd64 (4.4.0-72.93, automatic), 
linux-image-4.4.0-66-generic:amd64 (4.4.0-66.87, automatic), 
linux-image-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic), 
linux-image-extra-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.66.70, 4.4.0.72.78), 
linux-image-generic:amd64 (4.4.0.66.70, 4.4.0.72.78), linux-generic:amd64 
(4.4.0.66.70, 4.4.0.72.78)
  DpkgTerminalLog:
   Preparing to unpack .../linux-image-4.4.0-72-generic_4.4.0-72.93_amd64.deb 
...
   Can't locate Debconf/Client/ConfModule.pm in @INC (@INC contains: 
/opt/lampp/lib/perl5/site_perl/5.16.3/x86_64-linux-thread-multi 
/opt/lampp/lib/perl5/site_perl/5.16.3 
/opt/lampp/lib/perl5/5.16.3/x86_64-linux-thread-multi 
/opt/lampp/lib/perl5/5.16.3 .) at /var/lib/dpkg/tmp.ci/preinst line 20.
   BEGIN failed--compilation aborted at /var/lib/dpkg/tmp.ci/preinst line 20.
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-72-generic_4.4.0-72.93_amd64.deb 
(--unpack):
subprocess new pre-installation script returned error exit status 2
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  InstallationDate: Installed on 2016-12-28 (105 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 004: ID 10f1:1a34 Importek 
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA Satellite C655
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=40b59826-0bd4-49a9-89a6-5bbd8231d3fe ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-72-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.90
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.90:bd03/16/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC12U-04001W:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite C655
  dmi.product.version: PSC12U-04001W
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1683165] Re: suspend/resume yields blank screen on NVIDIA desktop

2017-06-16 Thread 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/1683165

Title:
  suspend/resume yields blank screen on NVIDIA desktop

Status in linux package in Ubuntu:
  Expired

Bug description:
  On my desktop when I set "System settings > Power > Suspend when
  inactive for" to any time (5 minutes, say), and wait, Ubuntu suspends.
  When I power my desktop back on, it boots without the usual chatter on
  the screen and the screen stays entirely blank (the monitor is in
  power-save mode). At that point the only workaround is to force a
  reboot by holding down the power button for 4 seconds, and go through
  the ordinary boot process.

  This appears to be the same symptoms as Bug#1283938, the last comment
  of which says "file a bug by running 'ubuntu-bug linux'", which is
  what I've done here. I have had the problem for years but have not
  reported it until today.

  My desktop has an Asus M4N78 Pro motherboard, which uses an NVIDIA
  GeForce 8300 chipset. lspci reports the graphics controller as "NVIDIA
  Corporation C77 [GeForce 8300] (rev a2)". "Software & Updates" says I
  am using "NVIDIA legacy binary driver - version 304.135 from
  nvidia-304 (proprietary)". As discussed in Bug#1639180 comment#65, I
  cannot use the latest NVIDIA driver as it has so many artifacts on the
  screen that it is unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eggert 1825 F pulseaudio
   /dev/snd/controlC1:  eggert 1825 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 16 09:38:00 2017
  HibernationDevice: RESUME=UUID=433ca071-21cd-44b7-9b81-2b73c0463790
  InstallationDate: Installed on 2014-04-27 (1084 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=0d7c67e2-db5b-493a-890b-90121ad2ee20 ro quiet splash 
acpi_enforce_resources=lax
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.157.8
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (358 days ago)
  dmi.bios.date: 07/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1004
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N78 PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1004:bd07/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1682649] Re: cheese error

2017-06-16 Thread 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/1682649

Title:
  cheese error

Status in linux package in Ubuntu:
  Expired

Bug description:
  camera was working, but changed effects and now it comes up with error :
  There was an error playing video from the webcam

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: cheese 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Apr 14 00:17:12 2017
  InstallationDate: Installed on 2017-04-13 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: VMware, Inc. VMware Virtual Platform
  RelatedPackageVersions:
   cheese3.24.0-0ubuntu1
   cheese-common 3.24.0-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 008: ID 046d:092f Logitech, Inc. QuickCam Express Plus
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

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

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


[Kernel-packages] [Bug 1683441] Re: systemd-resolved doesn't work after suspend

2017-06-16 Thread 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/1683441

Title:
  systemd-resolved doesn't work after suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  After suspend/resume DNS name resolution stop working.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob1644 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-04-17 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 008: ID 0489:e095 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 04f2:b47f Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-331
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=38e254ee-3d77-4144-90a6-a06087eba953 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-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/30/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.17
  dmi.board.name: Aspire ES1-331
  dmi.board.vendor: Acer
  dmi.board.version: V1.17
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.17
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireES1-331:pvrV1.17:rvnAcer:rnAspireES1-331:rvrV1.17:cvnAcer:ct10:cvrV1.17:
  dmi.product.name: Aspire ES1-331
  dmi.product.version: V1.17
  dmi.sys.vendor: Acer

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

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


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

2017-06-16 Thread Brad Figg
tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-55.58-generic/gonzo__4.8.0-55.58__2017-06-17_01-14-00/results-index.html

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

Title:
  linux: 4.8.0-55.58 -proposed tracker

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

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

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

  backports: 1696366
  derivatives: 1696367
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1698264] Re: Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker

2017-06-16 Thread Thiago Alves Silva
Seth, I was able to try the Kernel provided by you (4.4.0-1019-aws) and
it worked fine.

Do you believe we will be able to have it in a supported Ubuntu kernel
on release 16.04.3?

Thank you so much!

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/16/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


[Kernel-packages] [Bug 1514363] Re: kernel crash in ipv4_dst_destroy

2017-06-16 Thread csmcd5
On our product we have recently seen kernel crashes showing the same
call chain as above. It happened on two different hosts only 26 minutes
apart.

We have a Python program using scapy/sniff. Its effect is to repeatedly
put all interfaces into promiscuous mode and then take them out. There
are about 10 interfaces, mostly vlan, and it does not create/delete
interfaces. This has been running on 7 hosts every 1-3 minutes for days.

Linux ir6 3.16.0-44-iridium #59~14.04.1 SMP PREEMPT Tue May 23 01:10:24
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I've seen other Google results for crashes in ipv4_dst_destroy that are
preceded by "promiscuous mode" notices in the kernel log.

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

Title:
  kernel crash in ipv4_dst_destroy

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

Bug description:
  Hi,

  we have seen a GPF resulting in ipv4_dst_destroy:

  messages-2015-11-08:Nov  8 20:23:05 bbk130129 kernel: [205505.064821] device 
tap406dbc6f-a8 left promiscuous mode
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205505.534610] general 
protection fault:  [#1] SMP
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205505.578139] Modules 
linked in: kvm_intel kvm vport_vxlan vport_gre gre openvswitch dm_multipath 
scsi_dh nbd sch_fq_codel xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat bridge ebtable_filter 
ebtables ipmi_devintf btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs xfs libcrc32c vhost_net vhost macvtap macvlan ip6t_REJECT nf_reject_ipv6 
nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT 
nf_reject_ipv4 xt_limit xt_multiport xt_CT iptable_raw xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter 
ip_tables x_tables mlx4_en(OE) mlx4_core(OE) mlx_compat(OE) isofs ipmi_ssif 
intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd sb_edac edac_core lpc_ich hpilo ioatdma 
ipmi_si 8250_fintek ipmi_msghandl
 er wmi acpi_power_meter mac_hid shpchp bonding 8021q garp mrp stp llc lp 
parport nls_iso8859_1 ixgbe dca vxlan ip6_udp_tunnel tg3 udp_tunnel mpt3sas(OE) 
raid_class ptp configfs pps_core mdio scsi_transport_sas
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.275481] CPU: 42 
PID: 258 Comm: rcuos/35 Tainted: G   OE  3.19.0-32-generic 
#37~14.04.1-Ubuntu
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.349044] 
Hardware name: HP ProLiant DL380 Gen9, BIOS P89 07/20/2015
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.404252] task: 
882fa5823110 ti: 882fa5848000 task.ti: 882fa5848000
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.463760] RIP: 
0010:[]  [] ipv4_dst_destroy+0x42/0x80
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.527658] RSP: 
0018:882fa584bde8  EFLAGS: 00010246
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.578843] RAX: 
dead00200200 RBX: 882f1e961200 RCX: 0060
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.636886] RDX: 
dead00100100 RSI: fe01 RDI: 81fc5d84
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.696883] RBP: 
882fa584bdf8 R08: 882f1e961200 R09: 0001802a000b
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.756193] R10: 
816b30f5 R11: ea00bc7a5800 R12: 
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.814938] R13: 
0001 R14: 882f1e961080 R15: 882fa5823110
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.878741] FS:  
() GS:885fbf44() knlGS:
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.943046] CS:  
0010 DS:  ES:  CR0: 80050033
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205506.997859] CR2: 
7ffd99ac3640 CR3: 02c16000 CR4: 001427e0
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205507.057616] Stack:
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205507.093614]  
 882f1e961200 882fa584be18 816b30d2
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205507.155762]  
882f1e961200 882fbfcf4bc0 882fa584be28 816b33ae
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205507.217537]  
882fa584beb8 810d542f 882fa5823110 882fa584be78
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205507.281530] Call 
Trace:
  messages-2015-11-08:Nov  8 20:23:08 bbk130129 kernel: [205507.321761]  
[] dst_destroy+0x32/0xe0
  messages-2015-11-08:Nov  8 20:23:08 

[Kernel-packages] [Bug 1696365] gonzo (amd64) - tests ran: 2, failed: 0

2017-06-16 Thread Brad Figg
tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-55.58-generic/gonzo__4.8.0-55.58__2017-06-17_00-22-00/results-index.html

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

Title:
  linux: 4.8.0-55.58 -proposed tracker

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

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

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

  backports: 1696366
  derivatives: 1696367
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04

2017-06-16 Thread John Manecke
tompotts-

looking at your output, it looks like wheel emulation is still set to
false:

Evdev Wheel Emulation (286): 0

I don't know what your trying to get it to do, but for me, my trackball
works the way I want it to when I turn on the wheel emulation (set it to
1).

Based on the output you posted, you could try:

xinput --set-prop 11 286 1

which would turn on the wheel emulation

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

Title:
  Middle mouse (wheel-click) button stopped working after upgrade to
  16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 16.04 clicking the middle mouse button (scroll
  wheel) on my Logitech M185 stopped working.

  xev does not even show the event for clicking the wheel, while it
  shows other button clicks and scroll wheel up/down events.

  xinput list shows the USB receiver 2 times:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=9[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ HID 046a:0023   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=16   [slave  pointer 
 (2)]
  ⎜   ↳ TPPS/2 IBM TrackPoint   id=17   [slave  pointer 
 (2)]

  Listing the capabilities looks like this:

  $ xinput list 9
  Logitech USB Receiver id=9[slave  pointer  (2)]
   Reporting 7 classes:
    Class originated from: 9. Type: XIButtonClass
    Buttons supported: 24
    Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel 
Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" 
"Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" 
"Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button 
Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" 
"Button Unknown" "Button Unknown" "Button Unknown"
    Button state:
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIValuatorClass
    Detail for Valuator 3:
  Label: Rel Vert Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 9. Type: XIScrollClass
    Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0
    Class originated from: 9. Type: XIScrollClass
    Scroll info for Valuator 3
  type: 1 (vertical)
  increment: -1.00
  flags: 0x2 ( preferred )

  $ xinput list 10
  Logitech USB Receiver id=10   [slave  pointer  (2)]
   Reporting 6 classes:
    Class originated from: 10. Type: XIButtonClass
    Buttons supported: 7
    Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel 
Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right"
    Button state:
    Class originated from: 10. Type: XIKeyClass
    Keycodes supported: 248
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 0:
  Label: Rel X
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 1:
  Label: Rel Y
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIValuatorClass
    Detail for Valuator 2:
  Label: Rel Horiz Wheel
  Range: -1.00 - -1.00
  Resolution: 1 units/m
  Mode: relative
    Class originated from: 10. Type: XIScrollClass
    Scroll info for Valuator 2
  type: 2 (horizontal)
  increment: 1.00
  flags: 0x0

  Does anyone have an idea how I can attempt to further debug that issue? Or 
maybe even a solution? Should I consider this issue a bug? Can I provide more 
info?
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  toby  11625 F pulseaudio
   /dev/snd/controlC0:  toby  11625 F pulseaudio
   /dev/snd/pcmC1D0p:   toby  11625 F...m pulseaudio
   /dev/snd/controlC1:  toby  

[Kernel-packages] [Bug 1696365] gonzo (i386) - tests ran: 141, failed: 0

2017-06-16 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-55.58-generic/gonzo__4.8.0-55.58__2017-06-16_23-15-00/results-index.html

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

Title:
  linux: 4.8.0-55.58 -proposed tracker

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

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

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

  backports: 1696366
  derivatives: 1696367
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1454903] Re: Btrfs Fails to Mount Drive - btrfs-transaction blocked for more than 120 seconds.

2017-06-16 Thread AlexanderYT
Linux g6-1 4.4.0-67-generic #88-Ubuntu SMP Wed Mar 8 16:34:45 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Btrfs Fails to Mount Drive - btrfs-transaction blocked for more than
  120 seconds.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Call Trace:
  kernel:  880408609800 8803e9cba200 8803d06f7398 8803bc89fe00
  kernel:  00014200 88040ce9f5c0 880407f9d850 8803bc89fdd8
  kernel:  8803bc89fdc8 880407f9d850 00014200 8803bc89ffd8
  kernel: btrfs-transacti D 8803bc89fdc8 0  4187  2 0x
  kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
  kernel:   Not tainted 3.19.0-16-generic #16-Ubuntu
  kernel: INFO: task btrfs-transacti:4187 blocked for more than 120 seconds.
  kernel:  [] system_call_fastpath+0x16/0x1b
  kernel:  [] SyS_mount+0x8b/0xd0
  kernel:  [] do_mount+0x204/0xb20
  kernel:  [] vfs_kern_mount+0x6b/0x120
  kernel:  [] ? __alloc_percpu+0x15/0x20
  kernel:  [] mount_fs+0x38/0x1c0
  kernel:  [] btrfs_mount+0x850/0x920 [btrfs]
  kernel:  [] open_ctree+0x1813/0x2090 [btrfs]
  kernel:  [] ? replay_one_extent+0x6b0/0x6b0 [btrfs]
  kernel:  [] btrfs_recover_log_trees+0x1d4/0x470 [btrfs]
  kernel:  [] walk_log_tree+0xbb/0x1a0 [btrfs]
  kernel:  [] walk_down_log_tree+0x1d9/0x420 [btrfs]
  kernel:  [] ? alloc_extent_buffer+0x34/0x350 [btrfs]
  kernel:  [] insert_orphan_item+0x5e/0x90 [btrfs]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-16-generic 3.19.0-16.16
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jdfalk 3444 F pulseaudio
  Date: Wed May 13 19:03:10 2015
  HibernationDevice: RESUME=/dev/mapper/sda5_crypt
  InstallationDate: Installed on 2015-05-10 (4 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic.efi.signed 
root=UUID=51a981ad-aeb0-4bd7-91c6-2d493155c812 ro rootflags=subvol=@ 
crashkernel=384M-:128M
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F18i
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF18i:bd01/06/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-05-10 (5 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  vivid
  Uname: Linux 4.1.0-040100rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1454903] Re: Btrfs Fails to Mount Drive - btrfs-transaction blocked for more than 120 seconds.

2017-06-16 Thread AlexanderYT
I can confirm

# lsb_release -a
   
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename:   xenial


# uptime
   g6-1
 02:13:43 up 17 days,  6:40,  1 user,  load average: 404.83, 402.10, 397.12

[Thu Jun 15 19:30:38 2017] device eth1 left promiscuous mode
[Thu Jun 15 19:31:12 2017] device eth1 entered promiscuous mode
[Thu Jun 15 19:34:04 2017] device eth1 left promiscuous mode
[Thu Jun 15 19:35:59 2017] device eth1 entered promiscuous mode
[Thu Jun 15 19:38:44 2017] device eth1 left promiscuous mode
[Thu Jun 15 21:32:25 2017] device eth2 entered promiscuous mode
[Thu Jun 15 22:04:15 2017] device eth2 left promiscuous mode
[Thu Jun 15 22:04:46 2017] device eth2 entered promiscuous mode
[Thu Jun 15 22:04:52 2017] device eth2 left promiscuous mode
[Fri Jun 16 16:23:36 2017] device eth1 entered promiscuous mode
[Fri Jun 16 20:02:57 2017] device eth1 left promiscuous mode
[Fri Jun 16 22:39:54 2017] INFO: task btrfs-transacti:1604 blocked for more 
than 120 seconds.
[Fri Jun 16 22:39:54 2017]   Tainted: G  I 4.4.0-67-generic 
#88-Ubuntu
[Fri Jun 16 22:39:54 2017] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
[Fri Jun 16 22:39:54 2017] btrfs-transacti D 8817e65e7b38 0  1604  
2 0x
[Fri Jun 16 22:39:54 2017]  8817e65e7b38 c03dbf65 880be8c3f2c0 
8817e51472c0
[Fri Jun 16 22:39:54 2017]  8817e65e8000 ff00 8817e51472c0 
8817e51472c0
[Fri Jun 16 22:39:54 2017]  88137fc714c8 8817e65e7b50 81838545 
88137fc71530
[Fri Jun 16 22:39:54 2017] Call Trace:
[Fri Jun 16 22:39:54 2017]  [] ? 
btrfs_submit_bio_hook+0xe5/0x1b0 [btrfs]
[Fri Jun 16 22:39:54 2017]  [] schedule+0x35/0x80
[Fri Jun 16 22:39:54 2017]  [] 
btrfs_tree_read_lock+0xe6/0x140 [btrfs]
[Fri Jun 16 22:39:54 2017]  [] ? 
wake_atomic_t_function+0x60/0x60
[Fri Jun 16 22:39:54 2017]  [] 
btrfs_read_lock_root_node+0x34/0x50 [btrfs]
[Fri Jun 16 22:39:54 2017]  [] btrfs_search_slot+0x74b/0xa00 
[btrfs]
[Fri Jun 16 22:39:54 2017]  [] ? ktime_get+0x3c/0xb0
[Fri Jun 16 22:39:54 2017]  [] btrfs_lookup_inode+0x3e/0xc0 
[btrfs]
[Fri Jun 16 22:39:54 2017]  [] 
__btrfs_update_delayed_inode+0x69/0x210 [btrfs]
[Fri Jun 16 22:39:54 2017]  [] ? btrfs_alloc_path+0x1a/0x20 
[btrfs]
[Fri Jun 16 22:39:54 2017]  [] 
__btrfs_run_delayed_items+0x571/0x620 [btrfs]
[Fri Jun 16 22:39:54 2017]  [] ? btrfs_free_path+0x26/0x30 
[btrfs]
[Fri Jun 16 22:39:54 2017]  [] 
btrfs_run_delayed_items+0x13/0x20 [btrfs]
[Fri Jun 16 22:39:54 2017]  [] 
btrfs_commit_transaction+0x28b/0xa90 [btrfs]
[Fri Jun 16 22:39:54 2017]  [] 
transaction_kthread+0x229/0x240 [btrfs]
[Fri Jun 16 22:39:54 2017]  [] ? 
btrfs_cleanup_transaction+0x570/0x570 [btrfs]
[Fri Jun 16 22:39:54 2017]  [] kthread+0xd8/0xf0
[Fri Jun 16 22:39:54 2017]  [] ? 
kthread_create_on_node+0x1e0/0x1e0
[Fri Jun 16 22:39:54 2017]  [] ret_from_fork+0x3f/0x70
[Fri Jun 16 22:39:54 2017]  [] ? 
kthread_create_on_node+0x1e0/0x1e0
[Fri Jun 16 22:39:54 2017] INFO: task cmahostd:3707 blocked for more than 120 
seconds.
[Fri Jun 16 22:39:54 2017]   Tainted: G  I 4.4.0-67-generic 
#88-Ubuntu
[Fri Jun 16 22:39:54 2017] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
[Fri Jun 16 22:39:54 2017] cmahostdD 8817e813fd48 0  3707  
1 0x
[Fri Jun 16 22:39:54 2017]  8817e813fd48 8817e47b8000 8817e9702640 
8817e47b8000
[Fri Jun 16 22:39:54 2017]  8817e814 8816d038b068 8816d038b080 
8813f8582000
[Fri Jun 16 22:39:54 2017]  8816d038b000 8817e813fd60 81838545 
8817e47b8000
[Fri Jun 16 22:39:54 2017] Call Trace:
[Fri Jun 16 22:39:54 2017]  [] schedule+0x35/0x80
[Fri Jun 16 22:39:54 2017]  [] 
rwsem_down_read_failed+0xe0/0x140
[Fri Jun 16 22:39:54 2017]  [] 
call_rwsem_down_read_failed+0x14/0x30
[Fri Jun 16 22:39:54 2017]  [] ? down_read+0x20/0x30
[Fri Jun 16 22:39:54 2017]  [] 
proc_pid_cmdline_read+0xae/0x530
[Fri Jun 16 22:39:54 2017]  [] ? 
security_file_permission+0xa0/0xc0
[Fri Jun 16 22:39:54 2017]  [] __vfs_read+0x18/0x40
[Fri Jun 16 22:39:54 2017]  [] vfs_read+0x86/0x130
[Fri Jun 16 22:39:54 2017]  [] SyS_read+0x55/0xc0
[Fri Jun 16 22:39:54 2017]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
[Fri Jun 16 22:39:54 2017] INFO: task rs:main Q:Reg:16960 blocked for more than 
120 seconds.
[Fri Jun 16 22:39:54 2017]   Tainted: G  I 4.4.0-67-generic 
#88-Ubuntu
[Fri Jun 16 22:39:54 2017] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" 
disables this message.
[Fri Jun 16 22:39:54 2017] rs:main Q:Reg   D 88004ad6fba8 0 16960  
16795 0x
[Fri Jun 16 22:39:54 

[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

2017-06-16 Thread Pete Cheslock
@nicholas-hatch - what file system are your disks formatted as?  I was
able to stop the OOM's on my ES hosts by moving from XFS to EXT4.  My
belief is that there was a memory fragmentation issue with ES and many
small files on XFS formatted volumes.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

Status in linux package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Released
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


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

2017-06-16 Thread Joseph Salisbury
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/1698472

Title:
  package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running under Virtual Box under Windows 10

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jim2083 F pulseaudio
  Date: Mon Jun 12 21:51:53 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-04-13 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=cbb0d41e-8a7c-4cef-a662-25e5bbb78052 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1696365] gonzo (amd64) - tests ran: 141, failed: 0

2017-06-16 Thread Brad Figg
tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-55.58-generic/gonzo__4.8.0-55.58__2017-06-16_22-04-00/results-index.html

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

Title:
  linux: 4.8.0-55.58 -proposed tracker

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

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

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

  backports: 1696366
  derivatives: 1696367
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

2017-06-16 Thread Nick Hatch
We're still having issues with higher-order allocations failing and
triggering an OOM kill for unexplainable reasons. (on 4.4.0-78-generic).

I've attached the relevant OOM killer logs. It may be relevant to note
that the server these logs are from is an Elasticsearch instance with a
large (~32GB) mlock'ed heap.


** Attachment added: "kthreadd triggered order=2 allocation failure"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4897378/+files/kern.log

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

Status in linux package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Released
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


[Kernel-packages] [Bug 1698472] Re: package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-06-16 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Running under Virtual Box under Windows 10

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jim2083 F pulseaudio
  Date: Mon Jun 12 21:51:53 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-04-13 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=cbb0d41e-8a7c-4cef-a662-25e5bbb78052 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1698363] Re: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build

2017-06-16 Thread Raymond Meyer
Here is log (not much there)

/var/lib/dkms/zfs$ cat */build/make*
DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-79-generic (x86_64)
Fri Jun 16 07:19:28 CDT 2017
make: *** No targets specified and no makefile found.  Stop.

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Performing system updates, not a user of zfs (at this point). Packages
  just failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-79-generic (x86_64)
   Fri Jun 16 07:19:28 CDT 2017
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-79-generic
  Date: Fri Jun 16 07:19:32 2017
  InstallationDate: Installed on 2014-10-19 (971 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  PackageVersion: 0.6.5.6-0ubuntu17
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (420 days ago)

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

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


[Kernel-packages] [Bug 1698470] Re: [Zesty][Yakkerty] rtl8192e bug fixes

2017-06-16 Thread cheltspy
** Summary changed:

- rtl8192e bug fixes
+ [Zesty][Yakkerty] rtl8192e bug fixes

** Summary changed:

- [Zesty][Yakkerty] rtl8192e bug fixes
+ [Zesty][Yakkety] rtl8192e bug fixes

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

Title:
  [Zesty][Yakkety] rtl8192e bug fixes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following commits needed to be added to 4.10 and 4.8 kernels for
  stable operation of r8192e_pci driver. They are already in 4.11 and in
  4.4.

  commit baabd567f87be05330faa5140f72a91960e7405a upstream
  staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.

  commit 867510bde14e7b7fc6dd0f50b48f6753cfbd227a upstream.
  staging: rtl8192e: fix 2 byte alignment of register BSSIDR.

  commit 90be652c9f157d44b9c2803f902a8839796c090d upstream.
  staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of EPROM_CMD.

  commit 95d93e271d920dfda369d4740b1cc1061d41fe7f upstream.
  staging: rtl8192e: GetTs Fix invalid TID 7 warning.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  canaries-64   2006 F pulseaudio
   /dev/snd/controlC0:  canaries-64   2006 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Jun 16 23:11:13 2017
  HibernationDevice: RESUME=UUID=f23ec6f5-7e6a-4559-a7f1-af640124e970
  InstallationDate: Installed on 2015-10-31 (594 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=48898cca-fae3-4cdc-9785-fc0b97f4cbd9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: rtllib r8192e_pci
  UpgradeStatus: Upgraded to zesty on 2016-10-23 (236 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: N3700-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd04/18/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Kernel-packages] [Bug 1698472] [NEW] package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-06-16 Thread Jim Millard
Public bug reported:

Running under Virtual Box under Windows 10

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-22-generic 4.10.0-22.24
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jim2083 F pulseaudio
Date: Mon Jun 12 21:51:53 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
InstallationDate: Installed on 2017-04-13 (64 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IwConfig:
 lono wireless extensions.
 
 enp0s3no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=cbb0d41e-8a7c-4cef-a662-25e5bbb78052 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
RfKill:
 
SourcePackage: linux
Title: package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-package 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/1698472

Title:
  package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Running under Virtual Box under Windows 10

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jim2083 F pulseaudio
  Date: Mon Jun 12 21:51:53 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-04-13 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=cbb0d41e-8a7c-4cef-a662-25e5bbb78052 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.10.0-22-generic 4.10.0-22.24 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


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

2017-06-16 Thread Joseph Salisbury
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/1698468

Title:
  fwupd taking 100% CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After I boot into Ubuntu, top shows me a fwupd process taking 100%
  CPU. The log file /var/log/syslog has several highlighted messages
  like

  Jun 13 18:11:23 opal gnome-session[1487]: (gnome-software:1660): Gs-
  WARNING **:  failed to call gs_plugin_add_updates_historical on fwupd:
  failed to start fwupd: Error calling StartServiceByName for
  org.freedesktop.fwupd:
  GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate
  service 'org.freedesktop.fwupd': timed out

  Jun 13 18:11:26 opal gnome-session[1487]: (gnome-software:1660): Gs-
  WARNING **:  failed to call gs_plugin_refine on appstream: Error
  opening file: Permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  greg   1620 F pulseaudio
   /dev/snd/controlC1:  greg   1620 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun 16 19:00:37 2017
  HibernationDevice: RESUME=UUID=c05e0556-350a-4c17-8558-c475f250ccbf
  InstallationDate: Installed on 2016-04-28 (414 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA Satellite S50-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=9200f944-2d22-4f9b-8c44-e1498370470d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd05/05/2014:svnTOSHIBA:pnSatelliteS50-B:pvrPSPQ6C-020001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite S50-B
  dmi.product.version: PSPQ6C-020001
  dmi.sys.vendor: TOSHIBA

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

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


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

2017-06-16 Thread Joseph Salisbury
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/1698470

Title:
  [Zesty][Yakkety] rtl8192e bug fixes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following commits needed to be added to 4.10 and 4.8 kernels for
  stable operation of r8192e_pci driver. They are already in 4.11 and in
  4.4.

  commit baabd567f87be05330faa5140f72a91960e7405a upstream
  staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.

  commit 867510bde14e7b7fc6dd0f50b48f6753cfbd227a upstream.
  staging: rtl8192e: fix 2 byte alignment of register BSSIDR.

  commit 90be652c9f157d44b9c2803f902a8839796c090d upstream.
  staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of EPROM_CMD.

  commit 95d93e271d920dfda369d4740b1cc1061d41fe7f upstream.
  staging: rtl8192e: GetTs Fix invalid TID 7 warning.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  canaries-64   2006 F pulseaudio
   /dev/snd/controlC0:  canaries-64   2006 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Jun 16 23:11:13 2017
  HibernationDevice: RESUME=UUID=f23ec6f5-7e6a-4559-a7f1-af640124e970
  InstallationDate: Installed on 2015-10-31 (594 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=48898cca-fae3-4cdc-9785-fc0b97f4cbd9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: rtllib r8192e_pci
  UpgradeStatus: Upgraded to zesty on 2016-10-23 (236 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: N3700-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd04/18/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Kernel-packages] [Bug 1698470] [NEW] [Zesty][Yakkety] rtl8192e bug fixes

2017-06-16 Thread cheltspy
Public bug reported:

The following commits needed to be added to 4.10 and 4.8 kernels for
stable operation of r8192e_pci driver. They are already in 4.11 and in
4.4.

commit baabd567f87be05330faa5140f72a91960e7405a upstream
staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.

commit 867510bde14e7b7fc6dd0f50b48f6753cfbd227a upstream.
staging: rtl8192e: fix 2 byte alignment of register BSSIDR.

commit 90be652c9f157d44b9c2803f902a8839796c090d upstream.
staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of EPROM_CMD.

commit 95d93e271d920dfda369d4740b1cc1061d41fe7f upstream.
staging: rtl8192e: GetTs Fix invalid TID 7 warning.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-22-generic 4.10.0-22.24
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  canaries-64   2006 F pulseaudio
 /dev/snd/controlC0:  canaries-64   2006 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Fri Jun 16 23:11:13 2017
HibernationDevice: RESUME=UUID=f23ec6f5-7e6a-4559-a7f1-af640124e970
InstallationDate: Installed on 2015-10-31 (594 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=48898cca-fae3-4cdc-9785-fc0b97f4cbd9 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-22-generic N/A
 linux-backports-modules-4.10.0-22-generic  N/A
 linux-firmware 1.164.1
RfKill:
 0: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: rtllib r8192e_pci
UpgradeStatus: Upgraded to zesty on 2016-10-23 (236 days ago)
dmi.bios.date: 04/18/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.70
dmi.board.name: N3700-ITX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd04/18/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


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

Title:
  [Zesty][Yakkety] rtl8192e bug fixes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following commits needed to be added to 4.10 and 4.8 kernels for
  stable operation of r8192e_pci driver. They are already in 4.11 and in
  4.4.

  commit baabd567f87be05330faa5140f72a91960e7405a upstream
  staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.

  commit 867510bde14e7b7fc6dd0f50b48f6753cfbd227a upstream.
  staging: rtl8192e: fix 2 byte alignment of register BSSIDR.

  commit 90be652c9f157d44b9c2803f902a8839796c090d upstream.
  staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of EPROM_CMD.

  commit 95d93e271d920dfda369d4740b1cc1061d41fe7f upstream.
  staging: rtl8192e: GetTs Fix invalid TID 7 warning.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-22-generic 4.10.0-22.24
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  canaries-64   2006 F pulseaudio
   /dev/snd/controlC0:  canaries-64   2006 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Jun 16 23:11:13 2017
  HibernationDevice: RESUME=UUID=f23ec6f5-7e6a-4559-a7f1-af640124e970
  InstallationDate: Installed on 2015-10-31 (594 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=48898cca-fae3-4cdc-9785-fc0b97f4cbd9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-22-generic N/A
   linux-backports-modules-4.10.0-22-generic  N/A
   linux-firmware 1.164.1
  RfKill:
   0: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: rtllib r8192e_pci
  UpgradeStatus: Upgraded to zesty on 2016-10-23 (236 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  

[Kernel-packages] [Bug 1698468] [NEW] fwupd taking 100% CPU

2017-06-16 Thread Greg d'Eon
Public bug reported:

After I boot into Ubuntu, top shows me a fwupd process taking 100% CPU.
The log file /var/log/syslog has several highlighted messages like

Jun 13 18:11:23 opal gnome-session[1487]: (gnome-software:1660): Gs-
WARNING **:  failed to call gs_plugin_add_updates_historical on fwupd:
failed to start fwupd: Error calling StartServiceByName for
org.freedesktop.fwupd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut:
Failed to activate service 'org.freedesktop.fwupd': timed out

Jun 13 18:11:26 opal gnome-session[1487]: (gnome-software:1660): Gs-
WARNING **:  failed to call gs_plugin_refine on appstream: Error opening
file: Permission denied

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-78-generic 4.4.0-78.99
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  greg   1620 F pulseaudio
 /dev/snd/controlC1:  greg   1620 F pulseaudio
CurrentDesktop: Unity
Date: Fri Jun 16 19:00:37 2017
HibernationDevice: RESUME=UUID=c05e0556-350a-4c17-8558-c475f250ccbf
InstallationDate: Installed on 2016-04-28 (414 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: TOSHIBA Satellite S50-B
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=9200f944-2d22-4f9b-8c44-e1498370470d ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-78-generic N/A
 linux-backports-modules-4.4.0-78-generic  N/A
 linux-firmware1.157.11
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/05/2014
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.40
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis ManuFacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd05/05/2014:svnTOSHIBA:pnSatelliteS50-B:pvrPSPQ6C-020001:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite S50-B
dmi.product.version: PSPQ6C-020001
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug xenial

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

Title:
  fwupd taking 100% CPU

Status in linux package in Ubuntu:
  New

Bug description:
  After I boot into Ubuntu, top shows me a fwupd process taking 100%
  CPU. The log file /var/log/syslog has several highlighted messages
  like

  Jun 13 18:11:23 opal gnome-session[1487]: (gnome-software:1660): Gs-
  WARNING **:  failed to call gs_plugin_add_updates_historical on fwupd:
  failed to start fwupd: Error calling StartServiceByName for
  org.freedesktop.fwupd:
  GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate
  service 'org.freedesktop.fwupd': timed out

  Jun 13 18:11:26 opal gnome-session[1487]: (gnome-software:1660): Gs-
  WARNING **:  failed to call gs_plugin_refine on appstream: Error
  opening file: Permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  greg   1620 F pulseaudio
   /dev/snd/controlC1:  greg   1620 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun 16 19:00:37 2017
  HibernationDevice: RESUME=UUID=c05e0556-350a-4c17-8558-c475f250ccbf
  InstallationDate: Installed on 2016-04-28 (414 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA Satellite S50-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=9200f944-2d22-4f9b-8c44-e1498370470d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  

[Kernel-packages] [Bug 1696365] gonzo (i386) - tests ran: 6, failed: 0

2017-06-16 Thread Brad Figg
tests ran:   6, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-55.58-generic/gonzo__4.8.0-55.58__2017-06-16_20-56-00/results-index.html

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

Title:
  linux: 4.8.0-55.58 -proposed tracker

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

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

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

  backports: 1696366
  derivatives: 1696367
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

2017-06-16 Thread Hagen Kuehn
In answer to your qeustion
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/3

* Yes, the problem is NOT encountered when using Kernel linux-
image-4.10.0-21-generic 4.10.0-21.23.

* The problem is encountered when using 4.10.0-22-generic

In response to your request
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697556/comments/4

I have tested with upstream kernel 4.10.17

linux-headers-4.10.17-041017_4.10.17-041017.201705201051_all.deb
linux-headers-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb
linux-image-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb

and equally encountered the problem. I therefore added the tag: 'kernel-
bug-exists-upstream'.


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

Title:
  Computer freezes after login - 4.10.0-22-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
  Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
  ago. Login worked fine too.

  A couple of days later I installed the suggested kernel update
  "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer
  freezes right after login (i.e. after pressing enter, the background
  image with the mouse is shown, no responses to any key strokes).

  Syslog excerpt:

  Jun 12 22:12:48 computername kernel: [   47.603358] NMI watchdog: BUG: soft 
lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
  Jun 12 22:12:48 computername kernel: [   47.603360] Modules linked in: ccm 
msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 
i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi 
dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath 
x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp 
snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel 
memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq 
ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore 
idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf 
intel_lpss_pci intel_pch_thermal
  Jun 12 22:12:48 computername kernel: [   47.603422]  hci_uart btbcm btqca 
btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap 
intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als 
int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid 
pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc 
ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm 
i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt 
fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid 
pinctrl_sunrisepoint video wmi pinctrl_intel fjes
  Jun 12 22:12:48 computername kernel: [   47.603453] CPU: 1 PID: 1672 Comm: 
Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
  Jun 12 22:12:48 computername kernel: [   47.603453] Hardware name: Dell Inc. 
XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017

  
  Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not 
observed with 4.10.0-21-generic. As I was not able to login to my computer I am 
writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore 
the information attached through the "ubuntu-bug linux" command here, are 
referring to the kernel that is actually working. I decided to nonetheless 
include that information as it might contain other kernel unrelated information 
that would help you troubleshooting.

  Please see attached file "syslog-4.10.0-22-generic-freeze-after-
  login.log" for the full syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hkuehn 1796 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun 12 23:17:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-30 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 

[Kernel-packages] [Bug 1673344] Re: Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely (intel 7260) even when I try to restart network manager

2017-06-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Ubuntu 16.04 doesn't recongnize wifi card after loosing signal
  completely (intel 7260) even when I try to restart network manager

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  My wireless connection completely disappears and isn't recognized
  along with my NIC card and doesn't come back until I reboot even if I
  restart network manager.

  
  I've attached the required files showing what my wifi information looks like 
connected and what it looks like when the problem occurs hopefully a fix or 
workaround can be found this happens several times a day.

  Steps:

  1) I boot up type in sudo iwconfig wlp3s0 power off (turn off power 
management)
   
  2) 
  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.
  
  wlp3s0IEEE 802.11  ESSID:"2.4ghz"  
Mode:Managed  Frequency:2.437 GHz  Access Point: 
E0:3F:29:93:3F:20   
Bit Rate=144.4 Mb/s   Tx-Power=22 dBm   
Retry short limit:7   RTS thr:off   Fragment thr:off
Power Management:off
Link Quality=60/70  Signal level=-50 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:55   Missed beacon:0
  
  3) I loose wifi using 5ghz or 2.4ghz after a certain amount of time
  
  4) sudo rmmod iwlmvm iwlwifi && sudo modprobe iwlmvm iwlwifi
  5) sudo systemctl restart network-manager.service

  I do a **iwconfig** and **I'm missing wlp3s0IEEE 802.11
  ESSID:"2.4ghz"**

  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.

  I have to reboot to get my wifi back and for ubunutu to recognize my
  wifi card back how can I prevent this.

  $ uname -a
  Linux sys76 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  $ dmesg | grep iwlwifi
  876.891600] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  876.891602] iwlwifi :03:00.0: Scan failed! ret -5
  [  877.909370] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  877.909397] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  877.909409] iwlwifi :03:00.0: Scan failed! ret -5
  [  878.928277] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  878.928364] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  878.928366] iwlwifi :03:00.0: Scan failed! ret -5
  [  879.947120] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  879.947170] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  879.947172] iwlwifi :03:00.0: Scan failed! ret -5

  
  $ sudo lshw -C network
  [sudo] password for rt: 
*-network   
 description: Wireless interface
 product: Wireless 7260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 73
 serial: 0c:8b:fd:2e:64:8e
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=4.8.0-41-generic firmware=17.352738.0 ip=192.168.1.8 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:31 memory:f7d0-f7d01fff
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0.2
 bus info: pci@:04:00.2
 logical name: enp4s0f2
 version: 0a
 serial: 00:90:f5:f9:d4:f8
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list 
ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8411-1_0.0.3 06/18/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
 resources: irq:27 ioport:e000(size=256) memory:f0004000-f0004fff 
memory:f000-f0003fff
  $ 

  ethtool -i wlp3s0 | grep driver
  driver: 

[Kernel-packages] [Bug 1673344] Re: Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely (intel 7260) even when I try to restart network manager

2017-06-16 Thread Joseph Chereshnovsky
My wifi info script output information


** Attachment added: "wifi-info.zip"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1673344/+attachment/4897314/+files/wifi-info.zip

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

Title:
  Ubuntu 16.04 doesn't recongnize wifi card after loosing signal
  completely (intel 7260) even when I try to restart network manager

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  My wireless connection completely disappears and isn't recognized
  along with my NIC card and doesn't come back until I reboot even if I
  restart network manager.

  
  I've attached the required files showing what my wifi information looks like 
connected and what it looks like when the problem occurs hopefully a fix or 
workaround can be found this happens several times a day.

  Steps:

  1) I boot up type in sudo iwconfig wlp3s0 power off (turn off power 
management)
   
  2) 
  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.
  
  wlp3s0IEEE 802.11  ESSID:"2.4ghz"  
Mode:Managed  Frequency:2.437 GHz  Access Point: 
E0:3F:29:93:3F:20   
Bit Rate=144.4 Mb/s   Tx-Power=22 dBm   
Retry short limit:7   RTS thr:off   Fragment thr:off
Power Management:off
Link Quality=60/70  Signal level=-50 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:55   Missed beacon:0
  
  3) I loose wifi using 5ghz or 2.4ghz after a certain amount of time
  
  4) sudo rmmod iwlmvm iwlwifi && sudo modprobe iwlmvm iwlwifi
  5) sudo systemctl restart network-manager.service

  I do a **iwconfig** and **I'm missing wlp3s0IEEE 802.11
  ESSID:"2.4ghz"**

  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.

  I have to reboot to get my wifi back and for ubunutu to recognize my
  wifi card back how can I prevent this.

  $ uname -a
  Linux sys76 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  $ dmesg | grep iwlwifi
  876.891600] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  876.891602] iwlwifi :03:00.0: Scan failed! ret -5
  [  877.909370] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  877.909397] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  877.909409] iwlwifi :03:00.0: Scan failed! ret -5
  [  878.928277] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  878.928364] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  878.928366] iwlwifi :03:00.0: Scan failed! ret -5
  [  879.947120] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  879.947170] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  879.947172] iwlwifi :03:00.0: Scan failed! ret -5

  
  $ sudo lshw -C network
  [sudo] password for rt: 
*-network   
 description: Wireless interface
 product: Wireless 7260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 73
 serial: 0c:8b:fd:2e:64:8e
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=4.8.0-41-generic firmware=17.352738.0 ip=192.168.1.8 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:31 memory:f7d0-f7d01fff
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0.2
 bus info: pci@:04:00.2
 logical name: enp4s0f2
 version: 0a
 serial: 00:90:f5:f9:d4:f8
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list 
ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8411-1_0.0.3 06/18/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
 resources: irq:27 ioport:e000(size=256) memory:f0004000-f0004fff 
memory:f000-f0003fff
  $ 

 

[Kernel-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

2017-06-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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


[Kernel-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

2017-06-16 Thread Joseph Chereshnovsky
This one looks like the same bug:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1673344

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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


[Kernel-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

2017-06-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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


[Kernel-packages] [Bug 1673344] Re: Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely (intel 7260) even when I try to restart network manager

2017-06-16 Thread Joseph Chereshnovsky
My wifi info script output information


** Attachment added: "wifi-info.zip"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1673344/+attachment/4897313/+files/wifi-info.zip

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

Title:
  Ubuntu 16.04 doesn't recongnize wifi card after loosing signal
  completely (intel 7260) even when I try to restart network manager

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  My wireless connection completely disappears and isn't recognized
  along with my NIC card and doesn't come back until I reboot even if I
  restart network manager.

  
  I've attached the required files showing what my wifi information looks like 
connected and what it looks like when the problem occurs hopefully a fix or 
workaround can be found this happens several times a day.

  Steps:

  1) I boot up type in sudo iwconfig wlp3s0 power off (turn off power 
management)
   
  2) 
  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.
  
  wlp3s0IEEE 802.11  ESSID:"2.4ghz"  
Mode:Managed  Frequency:2.437 GHz  Access Point: 
E0:3F:29:93:3F:20   
Bit Rate=144.4 Mb/s   Tx-Power=22 dBm   
Retry short limit:7   RTS thr:off   Fragment thr:off
Power Management:off
Link Quality=60/70  Signal level=-50 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:55   Missed beacon:0
  
  3) I loose wifi using 5ghz or 2.4ghz after a certain amount of time
  
  4) sudo rmmod iwlmvm iwlwifi && sudo modprobe iwlmvm iwlwifi
  5) sudo systemctl restart network-manager.service

  I do a **iwconfig** and **I'm missing wlp3s0IEEE 802.11
  ESSID:"2.4ghz"**

  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.

  I have to reboot to get my wifi back and for ubunutu to recognize my
  wifi card back how can I prevent this.

  $ uname -a
  Linux sys76 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  $ dmesg | grep iwlwifi
  876.891600] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  876.891602] iwlwifi :03:00.0: Scan failed! ret -5
  [  877.909370] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  877.909397] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  877.909409] iwlwifi :03:00.0: Scan failed! ret -5
  [  878.928277] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  878.928364] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  878.928366] iwlwifi :03:00.0: Scan failed! ret -5
  [  879.947120] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  879.947170] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  879.947172] iwlwifi :03:00.0: Scan failed! ret -5

  
  $ sudo lshw -C network
  [sudo] password for rt: 
*-network   
 description: Wireless interface
 product: Wireless 7260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 73
 serial: 0c:8b:fd:2e:64:8e
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=4.8.0-41-generic firmware=17.352738.0 ip=192.168.1.8 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:31 memory:f7d0-f7d01fff
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0.2
 bus info: pci@:04:00.2
 logical name: enp4s0f2
 version: 0a
 serial: 00:90:f5:f9:d4:f8
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list 
ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8411-1_0.0.3 06/18/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
 resources: irq:27 ioport:e000(size=256) memory:f0004000-f0004fff 
memory:f000-f0003fff
  $ 

 

[Kernel-packages] [Bug 1697556] Re: Computer freezes after login - 4.10.0-22-generic

2017-06-16 Thread Hagen Kuehn
** Tags added: kernel-bug-exists-upstream

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

Title:
  Computer freezes after login - 4.10.0-22-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have got a new Ubuntu 17.04 install on a Dell XPS 15 (Intel(R)
  Core(TM) i7-7700HQ CPU @ 2.80GHz) that was installed a couple of days
  ago. Login worked fine too.

  A couple of days later I installed the suggested kernel update
  "4.10.0-22-generic". With kernel 4.10.0-22-generic, the computer
  freezes right after login (i.e. after pressing enter, the background
  image with the mouse is shown, no responses to any key strokes).

  Syslog excerpt:

  Jun 12 22:12:48 computername kernel: [   47.603358] NMI watchdog: BUG: soft 
lockup - CPU#1 stuck for 23s! [Xorg.wrap:1672]
  Jun 12 22:12:48 computername kernel: [   47.603360] Modules linked in: ccm 
msr arc4 cmac rfcomm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl bnep hid_multitouch nls_iso8859_1 
i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi dell_wmi 
dell_led dell_smbios snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
dcdbas ath10k_pci snd_hda_codec ath10k_core intel_rapl snd_hda_core ath 
x86_pkg_temp_thermal snd_hwdep intel_powerclamp mac80211 snd_pcm coretemp 
snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi rtsx_pci_ms kvm_intel 
memstick kvm irqbypass crct10dif_pclmul joydev crc32_pclmul snd_seq 
ghash_clmulni_intel snd_seq_device input_leds snd_timer serio_raw snd soundcore 
idma64 virt_dma mei_me mei shpchp processor_thermal_device intel_soc_dts_iosf 
intel_lpss_pci intel_pch_thermal
  Jun 12 22:12:48 computername kernel: [   47.603422]  hci_uart btbcm btqca 
btintel bluetooth dell_smo8800 intel_hid intel_lpss_acpi sparse_keymap 
intel_lpss tpm_crb int3403_thermal int3400_thermal acpi_als 
int340x_thermal_zone acpi_thermal_rel acpi_pad kfifo_buf industrialio mac_hid 
pcbc aesni_intel crypto_simd glue_helper cryptd aes_x86_64 dm_crypt parport_pc 
ppdev lp parport ip_tables x_tables autofs4 nouveau rtsx_pci_sdmmc i915 ttm 
i2c_algo_bit drm_kms_helper syscopyarea mxm_wmi sysfillrect psmouse sysimgblt 
fb_sys_fops nvme drm nvme_core rtsx_pci ahci libahci i2c_hid hid 
pinctrl_sunrisepoint video wmi pinctrl_intel fjes
  Jun 12 22:12:48 computername kernel: [   47.603453] CPU: 1 PID: 1672 Comm: 
Xorg.wrap Not tainted 4.10.0-22-generic #24-Ubuntu
  Jun 12 22:12:48 computername kernel: [   47.603453] Hardware name: Dell Inc. 
XPS 15 9560/05FFDN, BIOS 1.3.3 05/08/2017

  
  Note, this problem is observed with kernel 4.10.0-22-generic whereas it's not 
observed with 4.10.0-21-generic. As I was not able to login to my computer I am 
writing this bug report while it runs on kernel 4.10.0-21-generic. Therefore 
the information attached through the "ubuntu-bug linux" command here, are 
referring to the kernel that is actually working. I decided to nonetheless 
include that information as it might contain other kernel unrelated information 
that would help you troubleshooting.

  Please see attached file "syslog-4.10.0-22-generic-freeze-after-
  login.log" for the full syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hkuehn 1796 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun 12 23:17:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-05-30 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=e0800d30-3eff-46ac-a6af-38e3bcf99b58 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-generic N/A
   linux-backports-modules-4.10.0-21-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

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

2017-06-16 Thread Brad Figg
tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-55.58-generic/gonzo__4.8.0-55.58__2017-06-16_19-44-00/results-index.html

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

Title:
  linux: 4.8.0-55.58 -proposed tracker

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

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

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

  backports: 1696366
  derivatives: 1696367
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1673344] Re: Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely (intel 7260) even when I try to restart network manager

2017-06-16 Thread Joseph Chereshnovsky
Also this looks like the same problem:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1684213

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

Title:
  Ubuntu 16.04 doesn't recongnize wifi card after loosing signal
  completely (intel 7260) even when I try to restart network manager

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  My wireless connection completely disappears and isn't recognized
  along with my NIC card and doesn't come back until I reboot even if I
  restart network manager.

  
  I've attached the required files showing what my wifi information looks like 
connected and what it looks like when the problem occurs hopefully a fix or 
workaround can be found this happens several times a day.

  Steps:

  1) I boot up type in sudo iwconfig wlp3s0 power off (turn off power 
management)
   
  2) 
  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.
  
  wlp3s0IEEE 802.11  ESSID:"2.4ghz"  
Mode:Managed  Frequency:2.437 GHz  Access Point: 
E0:3F:29:93:3F:20   
Bit Rate=144.4 Mb/s   Tx-Power=22 dBm   
Retry short limit:7   RTS thr:off   Fragment thr:off
Power Management:off
Link Quality=60/70  Signal level=-50 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:55   Missed beacon:0
  
  3) I loose wifi using 5ghz or 2.4ghz after a certain amount of time
  
  4) sudo rmmod iwlmvm iwlwifi && sudo modprobe iwlmvm iwlwifi
  5) sudo systemctl restart network-manager.service

  I do a **iwconfig** and **I'm missing wlp3s0IEEE 802.11
  ESSID:"2.4ghz"**

  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.

  I have to reboot to get my wifi back and for ubunutu to recognize my
  wifi card back how can I prevent this.

  $ uname -a
  Linux sys76 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  $ dmesg | grep iwlwifi
  876.891600] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  876.891602] iwlwifi :03:00.0: Scan failed! ret -5
  [  877.909370] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  877.909397] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  877.909409] iwlwifi :03:00.0: Scan failed! ret -5
  [  878.928277] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  878.928364] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  878.928366] iwlwifi :03:00.0: Scan failed! ret -5
  [  879.947120] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  879.947170] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  879.947172] iwlwifi :03:00.0: Scan failed! ret -5

  
  $ sudo lshw -C network
  [sudo] password for rt: 
*-network   
 description: Wireless interface
 product: Wireless 7260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 73
 serial: 0c:8b:fd:2e:64:8e
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=4.8.0-41-generic firmware=17.352738.0 ip=192.168.1.8 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:31 memory:f7d0-f7d01fff
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0.2
 bus info: pci@:04:00.2
 logical name: enp4s0f2
 version: 0a
 serial: 00:90:f5:f9:d4:f8
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list 
ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8411-1_0.0.3 06/18/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
 resources: irq:27 ioport:e000(size=256) memory:f0004000-f0004fff 
memory:f000-f0003fff
  $ 

  ethtool -i wlp3s0 | grep driver
  driver: iwlwifi

  
  $ dmesg | grep iwlwifi

[Kernel-packages] [Bug 1673344] Re: Ubuntu 16.04 doesn't recongnize wifi card after loosing signal completely (intel 7260) even when I try to restart network manager

2017-06-16 Thread Joseph Chereshnovsky
Have the same issue, so subscribing for updates.

More details can be found here:
https://ubuntuforums.org/showthread.php?t=2359202

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

Title:
  Ubuntu 16.04 doesn't recongnize wifi card after loosing signal
  completely (intel 7260) even when I try to restart network manager

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My wireless connection completely disappears and isn't recognized
  along with my NIC card and doesn't come back until I reboot even if I
  restart network manager.

  
  I've attached the required files showing what my wifi information looks like 
connected and what it looks like when the problem occurs hopefully a fix or 
workaround can be found this happens several times a day.

  Steps:

  1) I boot up type in sudo iwconfig wlp3s0 power off (turn off power 
management)
   
  2) 
  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.
  
  wlp3s0IEEE 802.11  ESSID:"2.4ghz"  
Mode:Managed  Frequency:2.437 GHz  Access Point: 
E0:3F:29:93:3F:20   
Bit Rate=144.4 Mb/s   Tx-Power=22 dBm   
Retry short limit:7   RTS thr:off   Fragment thr:off
Power Management:off
Link Quality=60/70  Signal level=-50 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:55   Missed beacon:0
  
  3) I loose wifi using 5ghz or 2.4ghz after a certain amount of time
  
  4) sudo rmmod iwlmvm iwlwifi && sudo modprobe iwlmvm iwlwifi
  5) sudo systemctl restart network-manager.service

  I do a **iwconfig** and **I'm missing wlp3s0IEEE 802.11
  ESSID:"2.4ghz"**

  $ iwconfig
  enp4s0f2  no wireless extensions.
  
  lono wireless extensions.

  I have to reboot to get my wifi back and for ubunutu to recognize my
  wifi card back how can I prevent this.

  $ uname -a
  Linux sys76 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  $ dmesg | grep iwlwifi
  876.891600] iwlwifi :03:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  876.891602] iwlwifi :03:00.0: Scan failed! ret -5
  [  877.909370] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  877.909397] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  877.909409] iwlwifi :03:00.0: Scan failed! ret -5
  [  878.928277] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  878.928364] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  878.928366] iwlwifi :03:00.0: Scan failed! ret -5
  [  879.947120] iwlwifi :03:00.0: Failed to wake NIC for hcmd
  [  879.947170] iwlwifi :03:00.0: Error sending 
SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5
  [  879.947172] iwlwifi :03:00.0: Scan failed! ret -5

  
  $ sudo lshw -C network
  [sudo] password for rt: 
*-network   
 description: Wireless interface
 product: Wireless 7260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 73
 serial: 0c:8b:fd:2e:64:8e
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=4.8.0-41-generic firmware=17.352738.0 ip=192.168.1.8 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:31 memory:f7d0-f7d01fff
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0.2
 bus info: pci@:04:00.2
 logical name: enp4s0f2
 version: 0a
 serial: 00:90:f5:f9:d4:f8
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list 
ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8411-1_0.0.3 06/18/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
 resources: irq:27 ioport:e000(size=256) memory:f0004000-f0004fff 
memory:f000-f0003fff
  $ 

  ethtool -i wlp3s0 | grep driver
  driver: iwlwifi

  
  $ 

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

2017-06-16 Thread Joseph Salisbury
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1698448

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

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

Title:
  [SRU][Zesty] acpi: apei: check for pending errors when probing GHES
  entries

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  In addition to the RAS patches for which SRU were submitted under bug 
https://launchpad.net/bugs/1696570. We also require the following patch:
  f561618d9b80 acpi: apei: check for pending errors when probing GHES entries

  Without this patch pending RAS error at boot may not be handled
  correctly on the QDF2400 platforms, and could cause platform to
  reboot, or prevent future RAS issues from being reported.

  [Test]
  Run mce-tests suite.

  [Fix]
  Fix is available in the linux ARM64 git repo maintained by Will Deacon:
  f561618d9b80 acpi: apei: check for pending errors when probing GHES entries. 
This patch needs to be applied on top of the RAS patches that were already 
submitted for SRU

  [Regression Potential]
  Small fix to handle pending errors right away. Low risk of regression.

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

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


[Kernel-packages] [Bug 1698448] [NEW] [SRU][Zesty] acpi: apei: check for pending errors when probing GHES entries

2017-06-16 Thread Manoj Iyer
Public bug reported:

[Impact]
In addition to the RAS patches for which SRU were submitted under bug 
https://launchpad.net/bugs/1696570. We also require the following patch:
f561618d9b80 acpi: apei: check for pending errors when probing GHES entries

Without this patch pending RAS error at boot may not be handled
correctly on the QDF2400 platforms, and could cause platform to reboot,
or prevent future RAS issues from being reported.

[Test]
Run mce-tests suite.

[Fix]
Fix is available in the linux ARM64 git repo maintained by Will Deacon:
f561618d9b80 acpi: apei: check for pending errors when probing GHES entries. 
This patch needs to be applied on top of the RAS patches that were already 
submitted for SRU

[Regression Potential]
Small fix to handle pending errors right away. Low risk of regression.

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Manoj Iyer (manjo)
 Status: New


** Tags: qdf2400

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

Title:
  [SRU][Zesty] acpi: apei: check for pending errors when probing GHES
  entries

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]
  In addition to the RAS patches for which SRU were submitted under bug 
https://launchpad.net/bugs/1696570. We also require the following patch:
  f561618d9b80 acpi: apei: check for pending errors when probing GHES entries

  Without this patch pending RAS error at boot may not be handled
  correctly on the QDF2400 platforms, and could cause platform to
  reboot, or prevent future RAS issues from being reported.

  [Test]
  Run mce-tests suite.

  [Fix]
  Fix is available in the linux ARM64 git repo maintained by Will Deacon:
  f561618d9b80 acpi: apei: check for pending errors when probing GHES entries. 
This patch needs to be applied on top of the RAS patches that were already 
submitted for SRU

  [Regression Potential]
  Small fix to handle pending errors right away. Low risk of regression.

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

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


[Kernel-packages] [Bug 474653] ☁nice

2017-06-16 Thread shanta
Yo!

Just take  a look what I've just read, it's something extremely
interesting, check it out  http://bit.do/dwDAY


Sincerely, shanta


Sent from Mail for Windows 10

** Attachment added: "477DBEE399535FF68A186CC2DE4AA003.jpg"
   
https://bugs.launchpad.net/bugs/474653/+attachment/4897275/+files/477DBEE399535FF68A186CC2DE4AA003.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/474653

Title:
  nvidia sound card test failure

Status in linux package in Ubuntu:
  Fix Released
Status in linux-backports-modules-2.6.31 package in Ubuntu:
  Fix Released

Bug description:
  Upgrading to Karmic Using update manager. I lost the sound card.

  ProblemType: Bug
  Architecture: amd64
  CheckboxCommand: gst_pipeline_test -t 2 'audiotestsrc wave=sine freq=512 ! 
audioconvert ! audioresample ! gconfaudiosink'
  CheckboxDescription:
   Click the Test button to play a sound on the automatically detected playback 
device.
   
   Do you hear a sound?
  CheckboxTest: playback_auto
  Date: Wed Nov  4 11:55:29 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: python-gst0.10 0.10.17-1
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_CA.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: gst0.10-python
  Tags: checkbox-bug
  Uname: Linux 2.6.31-14-generic x86_64

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

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


[Kernel-packages] [Bug 479752] ❣just take a look

2017-06-16 Thread shanta
Hi,

Just  take a look  at that amazing and wonderful stuff, you're going to
love it I'm sure!  Check it out  http://bit.do/dwDA3

Looking forward, shanta


From: Bug 479752 [mailto:479...@bugs.launchpad.net]
Sent: Friday, June 16, 2017 2:17 PM
To: sha...@computersystemconsulting.ca
Subject: ACC MANIFEST DESTINY!

Hearthstone can  improve in the  easy to understand category. What I
hate is just looking at the card doesn't always explain what  it does.
For example Dr. Boom  says it summons two bombs, but you have no idea
what a  bomb does until you  summon it.  It's  not the only one the
same is true for Wild Growth drawing a card at 10 mana, and we  can
continue.


Sent from Mail for Windows 10

** Attachment added: "5D280419A94D6BB20E54BB73344832F2.jpg"
   
https://bugs.launchpad.net/bugs/479752/+attachment/4897276/+files/5D280419A94D6BB20E54BB73344832F2.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/479752

Title:
  wireless lan 'not ready' since upgrade to Karmic

Status in linux package in Ubuntu:
  Expired

Bug description:
  wireless lan shows 'device not ready' when enabled.

  I have tried some of the tips in other bugs but can't seem to get to
  the bottom of the problem.

  What tools do I need to install to even see the card to test and set
  it up?

  none of the defalut install tools see it.

  divice manager only sees that it is pressent but gives no data about
  it other than a ?

  Prior to the upgrade it worked fine.

  Thanks 
  Shanta

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC883 Analog [ALC883 Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shanta 2458 F pulseaudio
   /dev/snd/pcmC0D0p:   shanta 2458 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfebd8000 irq 25'
 Mixer name : 'Realtek ALC883'
 Components : 'HDA:10ec0883,1462373d,0012 
HDA:11c11040,11c10001,00100200'
 Controls  : 23
 Simple ctrls  : 14
  Date: Mon Nov  9 20:00:51 2009
  DistroRelease: Ubuntu 9.10
  HibernationDevice: RESUME=UUID=0bd33231-0e8b-47e2-8e5e-ad02a58e9fe1
  Lsusb:
   Bus 002 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 003: ID 0db0:6877 Micro Star International RT2573
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International MEGA BOOK S430
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.31-15-generic 2.6.31-15.49
  ProcCmdLine: root=UUID=6d73a21e-f9e0-4fb2-90a5-11e025b16cbf ro quiet splash
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-15.49-generic
  RelatedPackageVersions:
   linux-backports-modules-2.6.31-15-generic N/A
   linux-firmware 1.24
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  Uname: Linux 2.6.31-15-generic x86_64
  WpaSupplicantLog:
   
  dmi.bios.date: 10/09/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A1414NMS V7.09
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-1414X
  dmi.board.vendor: MSI
  dmi.board.version: Ver 1.000
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA1414NMSV7.09:bd10/09/2007:svnMicro-StarInternational:pnMEGABOOKS430:pvrMS-1414X:rvnMSI:rnMS-1414X:rvrVer1.000:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: MEGA BOOK S430
  dmi.product.version: MS-1414X
  dmi.sys.vendor: Micro-Star International

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

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


[Kernel-packages] [Bug 1630285] Re: mwifiex_pcie crashes after several bind/unbind

2017-06-16 Thread Mathieu Trudel-Lapierre
Somehow this appears to have possibly landed in xenial without
undergoing the verification expected (which might explain why it was
still in New, rather than Fix Committed).

I have set this back to Fix Committed for xenial, and re-did the
verification. As above, verification was limited to making sure the
workaround was present, since there is no hardware available to me to
run the test with.

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

** Tags added: verification-done-xenial

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

Title:
  mwifiex_pcie crashes after several bind/unbind

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in nplan package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in nplan source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  New
Status in nplan source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  netplan-configured systems with mwifiex interfaces crash if netplan attempts 
to unbind/bind the interface.

  [Test case]
  1) Run 'netplan apply' on a system with mwifiex_pci driver.

  The system should not crash, and the mwifiex interface should remain
  untouched.

  [Regression potential]
  Interfaces other than those affected by unbind/bind crashes or failures 
should still be unbound when 'netplan apply' is run. This affects most wireless 
interfaces, with the notable exception of mwifiex and brcmfmac. Failure to 
apply netplan configuration for a legitimate mwifiex device (wireless 
connection driven by NetworkManager renderer using netplan) would also 
constitute a regression.

  [Original bug report]
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bind

  Keep doing the bind/unbind actions, it would crash very soon.

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

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


[Kernel-packages] [Bug 1630285] Re: mwifiex_pcie crashes after several bind/unbind

2017-06-16 Thread Mathieu Trudel-Lapierre
Closing the nplan xenial task as Fix Released since it already have
nplan 0.14~16.04; which contains the fix for mwifiex -- this was
released in 0.13; backported as 0.13~16.04 (which was landed prior, but
also included in 0.14~16.04 in xenial-updates).

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

Title:
  mwifiex_pcie crashes after several bind/unbind

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in nplan package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in nplan source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  New
Status in nplan source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  netplan-configured systems with mwifiex interfaces crash if netplan attempts 
to unbind/bind the interface.

  [Test case]
  1) Run 'netplan apply' on a system with mwifiex_pci driver.

  The system should not crash, and the mwifiex interface should remain
  untouched.

  [Regression potential]
  Interfaces other than those affected by unbind/bind crashes or failures 
should still be unbound when 'netplan apply' is run. This affects most wireless 
interfaces, with the notable exception of mwifiex and brcmfmac. Failure to 
apply netplan configuration for a legitimate mwifiex device (wireless 
connection driven by NetworkManager renderer using netplan) would also 
constitute a regression.

  [Original bug report]
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bind

  Keep doing the bind/unbind actions, it would crash very soon.

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

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


[Kernel-packages] [Bug 1630285] Re: mwifiex_pcie crashes after several bind/unbind

2017-06-16 Thread Mathieu Trudel-Lapierre
Verification done for yakkety:

I have verified that the workaround for mwifiex is present in nplan
0.23~16.10. No further testing can be done due to the fact that I don't
have any hardware that uses the mwifiex driver.

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

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

Title:
  mwifiex_pcie crashes after several bind/unbind

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Triaged
Status in nplan package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in nplan source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  New
Status in nplan source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  netplan-configured systems with mwifiex interfaces crash if netplan attempts 
to unbind/bind the interface.

  [Test case]
  1) Run 'netplan apply' on a system with mwifiex_pci driver.

  The system should not crash, and the mwifiex interface should remain
  untouched.

  [Regression potential]
  Interfaces other than those affected by unbind/bind crashes or failures 
should still be unbound when 'netplan apply' is run. This affects most wireless 
interfaces, with the notable exception of mwifiex and brcmfmac. Failure to 
apply netplan configuration for a legitimate mwifiex device (wireless 
connection driven by NetworkManager renderer using netplan) would also 
constitute a regression.

  [Original bug report]
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/unbind
  # echo :03:00.0 > /sys/bus/pci/drivers/mwifiex_pcie/bind

  Keep doing the bind/unbind actions, it would crash very soon.

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

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


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

2017-06-16 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-55.58-generic/gonzo__4.8.0-55.58__2017-06-16_19-20-00/results-index.html

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

Title:
  linux: 4.8.0-55.58 -proposed tracker

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

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

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

  backports: 1696366
  derivatives: 1696367
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


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

2017-06-16 Thread Brad Figg
tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-55.58-generic/gonzo__4.8.0-55.58__2017-06-16_18-55-00/results-index.html

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

Title:
  linux: 4.8.0-55.58 -proposed tracker

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

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

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

  backports: 1696366
  derivatives: 1696367
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1696352] Re: linux: 3.13.0-120.167 -proposed tracker

2017-06-16 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux: 3.13.0-120.167 -proposed tracker

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

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

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

  backports: 1696354
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1660587] Re: Dracut cannot be used to generate kernel initramfs image

2017-06-16 Thread AsciiWolf
** Tags added: artful

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

Title:
  Dracut cannot be used to generate kernel initramfs image

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Unlike Debian, the Ubuntu kernel packages have hardcoded "update-initramfs" 
in the postinst script, making it impossible to use Dracut to generate 
initramfs image for the package.
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asciiwolf   2319 F pulseaudio
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=7aaa5193-1c44-4e73-8fe0-6e25a5d5b95a
  InstallationDate: Installed on 2016-05-05 (270 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=cs
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-12-generic 
root=UUID=5eb355dc-59d2-40c7-b52a-7cf31cd6dc3b ro quiet splash
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-12-generic N/A
   linux-backports-modules-4.9.0-12-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.9.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


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

2017-06-16 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

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

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

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

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

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

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


[Kernel-packages] [Bug 1696352] Re: linux: 3.13.0-120.167 -proposed tracker

2017-06-16 Thread Kleber Sacilotto de Souza
No regular bug fixes on this release, only CVEs. Setting verification-
testing to 'Fix Released'.

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

Title:
  linux: 3.13.0-120.167 -proposed tracker

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

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

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

  backports: 1696354
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1688158] Please help test zesty-proposed kernel for SMMU passthough.

2017-06-16 Thread Manoj Iyer
Jeff,

Could someone from QTI please help test 
http://launchpad.net/bugs/1688158 zesty-proposed kernel for SMMU 
passthough? We won't have an NVME drive (yet) installed in time for 
this SRU verification. I have boot tested this kernel and it boots fine 
on the QDF2400.

To enable proposed add the following line to your /etc/apt/sources.list

deb http://us.ports.ubuntu.com/ubuntu-ports/ zesty-proposed main 
restricted

Then install the kernel and fio tool.
$ sudo apt update

$ sudo apt install linux-image-4.10.0-23-generic 
linux-image-extra-4.10.0-23-generic

$ sudo apt install fio

For kernel parameter cases 0/1 run the tests.
iommu.passthough=0/1

$ sudo fio --name=global --readonly --group_reporting --direct=1 
--ioengine=libaio --rw=read --eta-newline=1s --size=1T --blocksize=512k 
--iodepth=32 --numjobs=1 --runtime=10s --name=nvme_0 
--filename=/dev/nvme0n1

After you are done posting the results to the bug. Please update the 
tag "verification-needed-zesty" to "verification-done-zesty"

Thanks
Manoj Iyer

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

Title:
  [SRU][Zesty] Support SMMU passthrough using the default domain

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

Bug description:
  [Impact]
  Have the SMMU come up in a passthrough configuration, and then allow 
subsequent translation for things such as VFIO. Rather than do this in each 
SMMU driver, it's much cleaner to allow the default domain to be configured to 
be something other than DMA.

  This patch series implements a command-line option to configure the
  default domain type. Currently, it supports "dma" and "identity" which
  is sufficient for the passthrough use-case.

  [Fix]
  The following patch series in linux-next adds this support to the kernel.
  4a8d8a14c0d0 arm64: dma-mapping: Only swizzle DMA ops for IOMMU_DOMAIN_DMA
  fccb4e3b8ab0 iommu: Allow default domain type to be set on the kernel command 
line
  beb3c6a066bf iommu/arm-smmu-v3: Install bypass STEs for IOMMU_DOMAIN_IDENTITY 
domains
  67560edcd8e5 iommu/arm-smmu-v3: Make arm_smmu_install_ste_for_dev return void
  61bc671179f1 iommu/arm-smmu: Install bypass S2CRs for IOMMU_DOMAIN_IDENTITY 
domains
  0834cc28fa56 iommu/arm-smmu: Restrict domain attributes to UNMANAGED domains

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

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


[Kernel-packages] [Bug 1691973] Re: Ubuntu16.04.03: POWER9 XIVE: msgsnd/doorbell IPI support (backport)

2017-06-16 Thread bugproxy
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

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

Title:
  Ubuntu16.04.03: POWER9 XIVE: msgsnd/doorbell IPI support (backport)

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

Bug description:
  == Comment: #0 - Mauricio Faria De Oliveira  - 
2017-05-17 09:22:57 ==
  Backport request for 16.04.3 HWE (via 17.04).

  Commit list:

  6b3edefefa67  powerpc/powernv: POWER9 support for msgsnd/doorbell IPI 
  a5adf282461f  powerpc/64s: Avoid a branch for ppc_msgsnd 
  b87ac0218355  powerpc: Introduce msgsnd/doorbell barrier primitives 
  b866cc2199d6  powerpc: Change the doorbell IPI calling convention 
  9b7ff0c6586b  powerpc/64s: Add SCV FSCR bit for ISA v3.0 
  794464f4dea0  powerpc/64s: Add msgp facility unavailable log string  

  Contacts (in CC list):
  - Breno Leitao 

  == Comment: #1 - Mauricio Faria De Oliveira  - 
2017-05-17 09:25:16 ==
  Gustavo has been working on this request, and has identified other commits 
required.

  He has a working patched kernel and is performing stress test for
  validating it before submission.

  == Comment: #2 - Gustavo Luiz Ferreira Walbon  - 
2017-05-18 15:48:52 ==
  I will submit a patch set in the kernel-team mailing list.

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

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


[Kernel-packages] [Bug 1696365] Re: linux: 4.8.0-55.58 -proposed tracker

2017-06-16 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

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

Title:
  linux: 4.8.0-55.58 -proposed tracker

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

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

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

  backports: 1696366
  derivatives: 1696367
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1698264] Re: Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker

2017-06-16 Thread Seth Forshee
I've tried reproducing this but haven't had luck. Something about my
test environment must make it difficult to hit the issue.

As I indicated on github, the xenial kernel currently in -proposed
(4.4.0-80.101) contains the patch which you indicated fixes the issue.
Could you test this kernel to confirm it is fixed there?

https://wiki.ubuntu.com/Testing/EnableProposed

I'll work on getting the fix into the yakkety/zesty kernels as well.
Thanks!

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

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/16/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


[Kernel-packages] [Bug 1680549] Re: [Zesty] QDF2400 ARM64 server - NMI watchdog: BUG: soft lockup - CPU#8 stuck for 22s!

2017-06-16 Thread Manoj Iyer
The proposed kernel in Zesty boots fine on the AW SDP at Canonical, and
does not report any NMI softlockups.

ubuntu@ubuntu:~$ uname -a 
Linux ubuntu 4.10.0-23-generic #25-Ubuntu SMP Fri Jun 9 09:36:27 UTC 2017 
aarch64 aarch64 aarch64 GNU/Linux

ubuntu@ubuntu:~$ apt-cache policy linux-image-4.10.0-23-generic
linux-image-4.10.0-23-generic:
  Installed: 4.10.0-23.25
  Candidate: 4.10.0-23.25
  Version table:
 *** 4.10.0-23.25 500
500 http://us.ports.ubuntu.com/ubuntu-ports zesty-proposed/main arm64 
Packages
100 /var/lib/dpkg/status


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

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

Title:
  [Zesty] QDF2400 ARM64 server - NMI watchdog: BUG: soft lockup - CPU#8
  stuck for 22s!

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

Bug description:
  [IMPACT]
  Booting Zesty 4.10 kernel on Qualcomm Centriq 2400 ARM64 servers causes soft 
lockups on multiple CPUs.

  [  104.205397] Modules linked in: nls_iso8859_1 cdc_acm bridge stp llc
  ipmi_ssif ipmi_devintf ipmi_msghandler shpchp hdma hdma_mgmt i2c_qup
  cppc_cpufreq ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp
  libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10
  raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
  raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage at803x
  aes_ce_blk aes_ce_cipher crc32_ce crct10dif_ce ghash_ce sha2_ce
  sha1_ce mlx5_core devlink ptp pps_core ahci_platform libahci_platform
  libahci qcom_emac sdhci_acpi sdhci xhci_plat_hcd pinctrl_qdf2xxx fjes
  aes_neon_blk crypto_simd cryptd

  [  104.205442] CPU: 47 PID: 0 Comm: swapper/47 Tainted: G L  
4.10.0-16-generic #18ubuntuRC03+.1
  [  104.205443] Hardware name: Qualcomm QDF2400 DP/ABW|SYS|CVR,1DPC|V3 
  , BIOS XBL.DF.2.0.R3-00153 QDF2400_REL CRM 02/ 8/2017
  [  104.205444] task: 9fa30ed49c00 task.stack: 9fa30ed5c000
  [  104.205447] PC is at _raw_spin_unlock_irqrestore+0x2c/0x38
  [  104.205450] LR is at alloc_iova+0x1cc/0x2a0
  [  104.205451] pc : [] lr : [] pstate: 
20400145
  [  104.205452] sp : 9fa31fbecc00
  [  104.205453] x29: 9fa31fbecc00 x28: 000efe46
  [  104.205455] x27: 0040 x26: 000f
  [  104.205458] x25: 3f06251f8000 x24: 0001
  [  104.205460] x23: 9fa30da06008 x22: 
  [  104.205462] x21: 9fa2e2af8740 x20: 9fa30da06008
  [  104.205464] x19: 0140 x18: a5e112c1
  [  104.205466] x17: 4d48a1ed x16: b0f9c455
  [  104.205468] x15: aa4269e9 x14: 85094ac4
  [  104.205471] x13: 9b3b00da x12: 8aae8d9c
  [  104.205473] x11: 9fa31fbf90b0 x10: 3f0624eb70eb
  [  104.205475] x9 :  x8 : 0004
  [  104.205477] x7 : 9fa2e2875400 x6 : 
  [  104.205479] x5 : 9fa2e2875401 x4 : 
  [  104.205481] x3 : 9fa2e2a27b00 x2 : 9fa2e2875400
  [  104.205483] x1 : 0140 x0 : f7c2

  [  111.198062] INFO: rcu_sched self-detected stall on CPU
  [  111.198971] INFO: rcu_sched detected stalls on CPUs/tasks:
  [  111.198977]31-...: (1 GPs behind) idle=1b3/2/0 softirq=432/433 
fqs=6805
  [  111.198979]32-...: (1 GPs behind) idle=291/1/0 softirq=469/470 
fqs=6805
  [  111.198980](detected by 2, t=15002 jiffies, g=143, c=142, q=6968)
  [  111.199000] Task dump for CPU 31:
  [  111.199002] swapper/31  R  running task0 0  1 
0x0002
  [  111.199006] Call trace:
  [  111.199012] [] __switch_to+0x98/0xb0
  [  111.199014] [<000b7160dcd2>] 0xb7160dcd2
  [  111.199015] Task dump for CPU 32:
  [  111.199016] swapper/32  R  running task0 0  1 
0x0002
  [  111.199018] Call trace:
  [  111.199019] [] __switch_to+0x98/0xb0
  [  111.199020] [<000bcde2fa4e>] 0xbcde2fa4e
  [  111.227703]31-...: (1 GPs behind) idle=1b3/2/0 softirq=432/433 
fqs=6809
  [  111.234558] (t=15010 jiffies g=143 c=142 q=6968)
  [  111.239334] Task dump for CPU 31:
  [  111.239335] swapper/31  R  running task0 0  1 
0x0002
  [  111.239338] Call trace:
  [  111.239344] [] dump_backtrace+0x0/0x2b0
  [  111.239346] [] show_stack+0x24/0x30
  [  111.239350] [] sched_show_task+0x128/0x178
  [  111.239352] [] dump_cpu_task+0x48/0x58
  [  111.239356] [] rcu_dump_cpu_stacks+0xbc/0xf0
  [  111.239359] [] rcu_check_callbacks+0x7a8/0x968
  [  111.239362] [] update_process_times+0x34/0x60
  [  111.239365] [] tick_sched_handle.isra.7+0x38/0x70
  [  111.239367] [] tick_sched_timer+0x4c/0x98
  [  111.239369] [] __hrtimer_run_queues+0xe8/0x2e8
  [  111.239371] [] hrtimer_interrupt+0xa8/0x228
  [  111.239376] [] 

[Kernel-packages] [Bug 1698028] Re: package linux-image-4.4.0-80-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-06-16 Thread Ubuntu Foundations Team Bug Bot
*** This bug is a duplicate of bug 1698027 ***
https://bugs.launchpad.net/bugs/1698027

** Attachment removed: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1698028/+attachment/4896129/+files/DuplicateSignature.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/1698028

Title:
  package linux-image-4.4.0-80-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  sto usando da parecchio tempo ubuntu 16.04 lts. recentemente mi sono
  scomparsi il launcer, che era a sinistra del descktop, la barra dei
  menu e la barra degli strumenti. all'avvio mi si presenta solo il
  descktop con le icone dei file e delle cartelle, l'open office,
  l'icona firefox non sono presenti.quindi il mio computer è
  inutilizzabile. non sono molto esperto di compèuter. sono solo uno
  smanettone. grazie a tutti.rommascia

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-80-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  remo   2043 F pulseaudio
   /dev/snd/controlC0:  remo   2043 F pulseaudio
  Date: Thu Jun 15 01:46:38 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=21cc7b49-c3b6-4915-830c-1e8c12b9da96
  InstallationDate: Installed on 2016-09-01 (286 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Packard Bell imedia S3800
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=153f300f-7cb1-4d60-8791-1157f7e4d1e5 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-80-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-B1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: FIH57
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/03/2010:svnPackardBell:pnimediaS3800:pvr:rvnAcer:rnFIH57:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: imedia S3800
  dmi.sys.vendor: Packard Bell

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

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


[Kernel-packages] [Bug 1698028] DuplicateSignature.txt

2017-06-16 Thread Brian Murray
*** This bug is a duplicate of bug 1698027 ***
https://bugs.launchpad.net/bugs/1698027

Due to a bug in apport's method for creating a duplicate signature, the
DuplicateSignature in this report was incorrect. We are fixing that now,
sorry for the noise!

** Attachment added: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1698028/+attachment/4897187/+files/DuplicateSignature.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/1698028

Title:
  package linux-image-4.4.0-80-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  sto usando da parecchio tempo ubuntu 16.04 lts. recentemente mi sono
  scomparsi il launcer, che era a sinistra del descktop, la barra dei
  menu e la barra degli strumenti. all'avvio mi si presenta solo il
  descktop con le icone dei file e delle cartelle, l'open office,
  l'icona firefox non sono presenti.quindi il mio computer è
  inutilizzabile. non sono molto esperto di compèuter. sono solo uno
  smanettone. grazie a tutti.rommascia

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-80-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  remo   2043 F pulseaudio
   /dev/snd/controlC0:  remo   2043 F pulseaudio
  Date: Thu Jun 15 01:46:38 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=21cc7b49-c3b6-4915-830c-1e8c12b9da96
  InstallationDate: Installed on 2016-09-01 (286 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Packard Bell imedia S3800
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=153f300f-7cb1-4d60-8791-1157f7e4d1e5 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-80-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-B1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: FIH57
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/03/2010:svnPackardBell:pnimediaS3800:pvr:rvnAcer:rnFIH57:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: imedia S3800
  dmi.sys.vendor: Packard Bell

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

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


[Kernel-packages] [Bug 1698169] DuplicateSignature.txt

2017-06-16 Thread Brian Murray
*** This bug is a duplicate of bug 1696440 ***
https://bugs.launchpad.net/bugs/1696440

Due to a bug in apport's method for creating a duplicate signature, the
DuplicateSignature in this report was incorrect. We are fixing that now,
sorry for the noise!

** Attachment added: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1698169/+attachment/4897183/+files/DuplicateSignature.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/1698169

Title:
  package linux-image-4.4.0-79-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  message at startup...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-79-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  linux  1469 F pulseaudio
  Date: Thu Jun 15 12:52:20 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=d933e772-dbb2-4f4b-a93e-9d3d2a1806a7
  InstallationDate: Installed on 2017-04-08 (68 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Compaq 6910p (GC022ET#ABF)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=528b9359-82b2-4c9e-9d44-394d03845cd8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.9
  SourcePackage: linux
  Title: package linux-image-4.4.0-79-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MCD Ver. F.0A
  dmi.board.name: 30C1
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 68.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MCDVer.F.0A:bd09/13/2007:svnHewlett-Packard:pnHPCompaq6910p(GC022ET#ABF):pvrF.0A:rvnHewlett-Packard:rn30C1:rvrKBCVersion68.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6910p (GC022ET#ABF)
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1698169] Re: package linux-image-4.4.0-79-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2017-06-16 Thread Ubuntu Foundations Team Bug Bot
*** This bug is a duplicate of bug 1696440 ***
https://bugs.launchpad.net/bugs/1696440

** Attachment removed: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1698169/+attachment/4896643/+files/DuplicateSignature.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/1698169

Title:
  package linux-image-4.4.0-79-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  message at startup...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-79-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  linux  1469 F pulseaudio
  Date: Thu Jun 15 12:52:20 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=d933e772-dbb2-4f4b-a93e-9d3d2a1806a7
  InstallationDate: Installed on 2017-04-08 (68 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Compaq 6910p (GC022ET#ABF)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=528b9359-82b2-4c9e-9d44-394d03845cd8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.9
  SourcePackage: linux
  Title: package linux-image-4.4.0-79-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MCD Ver. F.0A
  dmi.board.name: 30C1
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 68.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MCDVer.F.0A:bd09/13/2007:svnHewlett-Packard:pnHPCompaq6910p(GC022ET#ABF):pvrF.0A:rvnHewlett-Packard:rn30C1:rvrKBCVersion68.32:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6910p (GC022ET#ABF)
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard

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

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


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

2017-06-16 Thread Vladiszavlyev Gergo
Follow-up: Errors disappeared only for a few reboots. First only a
subset of errors, today all of the previously observed error messages
appeared again during boot 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/1521173

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1696693] Re: Mousepad/trackpad not working

2017-06-16 Thread paddotk
Hi guys,

Please bear with me but I'm not very technical with Ubuntu stuff. I've
been looking for a solution for over a day, tried solutions I've found
here and there, but I can't figure it out.

As for kernel versions; I honestly don't understand what a kernel is,
nor how to boot an older one.

@jsalisbury
Ubuntu's software updater did install some updates, and I figure the issue is 
related to an updated driver that doesn't work.
The link you provided me contains many download links, I'm not sure which file 
to download from here?

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

Title:
  Mousepad/trackpad not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I booted my pc this morning and found that the trackpad is no longer
  responding. Moving it or clicking, there is no response.

  I did nothing special yesterday nor manually installed anything, the
  only thing that was installed was some new Ubuntu updates through the
  software updater.

  My laptop is an Asus ROG GL553VD with Ubuntu 16.04.2 LTS.

  Looking in the list of hardware to see if the trackpad is recognized,
  I found 'ITE Tech. Inc. ITE Device(8910)' which seems to be the name
  for my trackpad.

  I tried 'sudo apt-get install xserver-xorg-input-synaptics' but it
  said it was already up-to-date (version 1.8.2-1ubuntu3)

  I can't include the package name in this report as 'apt-cache policy
  pkgname' doesn't work ("N: Unable to locate package pkgname")

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jun  8 11:11:14 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
  InstallationDate: Installed on 2017-05-28 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic.efi.signed 
root=UUID=958dbae2-1028-43ae-af29-6fa03c950ee3 ro acpi_backlight=vendor quiet 
splash acpi_osi= vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.301:bd12/30/2016:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: GL553VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jun  8 10:44:13 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1631 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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


[Kernel-packages] [Bug 1698363] Re: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build

2017-06-16 Thread Colin Ian King
** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Performing system updates, not a user of zfs (at this point). Packages
  just failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-79-generic (x86_64)
   Fri Jun 16 07:19:28 CDT 2017
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-79-generic
  Date: Fri Jun 16 07:19:32 2017
  InstallationDate: Installed on 2014-10-19 (971 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  PackageVersion: 0.6.5.6-0ubuntu17
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (420 days ago)

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

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


[Kernel-packages] [Bug 1543788] Re: Fails to resume from suspend

2017-06-16 Thread Kai-Heng Feng
@Igor

File a new bug, because everything machine has vastly different
components.

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

Title:
  Fails to resume from suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  Resuming from suspend used to work previously in 16.04.

  On resume I see a blank screen and nothing seems to respond. I've
  tried Ctrl+Alt+F1 and then Ctrl+Alt+Delete. Also tried the power
  button. No response.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shahar 2292 F pulseaudio
   /dev/snd/controlC0:  shahar 2292 F pulseaudio
   /dev/snd/controlC2:  shahar 2292 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Feb  9 22:51:40 2016
  HibernationDevice: RESUME=UUID=f2bd5594-8447-422c-a345-492ede4de1d9
  InstallationDate: Installed on 2010-10-12 (1946 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X10SRA
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-2-generic root=/dev/mapper/root 
ro nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2015-11-13 (88 days ago)
  dmi.bios.date: 11/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0a:bd11/27/2014:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X10SRA
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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


[Kernel-packages] [Bug 1697892] Re: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds

2017-06-16 Thread Joseph Salisbury
Great, Thanks!

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

Title:
  linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link
  speeds

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
Status in linux source package in Artful:
  In Progress

Bug description:
  These upstream patches are needed to correctly handle 5G, 25G and 50G
  speeds in 802.3ad:

  19ddde1eeca1 bonding: add 802.3ad support for 25G speeds
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e

  c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af

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

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


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

2017-06-16 Thread Brad Figg
tests ran:   4, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-80.101-generic/onza__4.4.0-80.101__2017-06-16_13-16-00/results-index.html

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

Title:
  linux: 4.4.0-80.101 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

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

  backports: 1696358
  derivatives: 1696359,1696360,1696362,1696363,1696364
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


[Kernel-packages] [Bug 1697892] Re: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds

2017-06-16 Thread Nicolas Dichtel
Thibaut will test the xenial kernel next week. Is it ok?

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

Title:
  linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link
  speeds

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
Status in linux source package in Artful:
  In Progress

Bug description:
  These upstream patches are needed to correctly handle 5G, 25G and 50G
  speeds in 802.3ad:

  19ddde1eeca1 bonding: add 802.3ad support for 25G speeds
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e

  c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af

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

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


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

2017-06-16 Thread bugproxy
--- Comment From cdead...@us.ibm.com 2017-06-16 09:35 EDT---
This CMVC defect is being cancelled by the CDE Bridge because the corresponding 
CQ Defect [SW383941] was transferred out of the bridge domain.
Here are the additional details:
New Subsystem = ppc_triage
New Release = unspecified
New Component = ubuntu_linux
New OwnerInfo = Chavez, Luciano (cha...@us.ibm.com)
To continue tracking this issue, please follow CQ defect [SW383941].

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

Title:
  Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with
  split op

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

Bug description:
   State: Open by: mdate on 19 March 2017 12:33:34 

  On a Bolt adapter in a system with Ubuntu 16.04, I've formatted the
  Bolt for T10 and am using it to do a dd with a 2M block size.

  Here are the commands:
  nvme format /dev/nvme0n1 --lbaf=1 --pil=0 --ms=0 --pi=2

  dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct count=1

  I get an error on the dd.
root@x1623bp1:~# dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct 
count=1
dd: error writing '/dev/nvme0n1': Input/output error
1+0 records in
0+0 records out
0 bytes copied, 0.0525061 s, 0.0 kB/s

  dmesg shows:
  [589997.985151] blk_update_request: I/O error, dev nvme0n1, sector 0

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

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


[Kernel-packages] [Bug 1698241] Re: WARNING: CPU: 13 PID: 0 at /build/linux-0XAgc4/linux-4.4.0/net/ipv4/tcp_output.c:1145

2017-06-16 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc5

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

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

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

Title:
  WARNING: CPU: 13 PID: 0 at /build/linux-
  0XAgc4/linux-4.4.0/net/ipv4/tcp_output.c:1145

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [ cut here ]
  WARNING: CPU: 13 PID: 0 at 
/build/linux-0XAgc4/linux-4.4.0/net/ipv4/tcp_output.c:1145 
tcp_fragment+0x34d/0x370()
  Modules linked in: ip6table_filter ipip tunnel4 ip_tunnel cpuid 8021q garp 
mrp stp llc ip6_tables binfmt_misc xt_comment nf_log_ipv4 nf_log_common xt_LOG 
xt_limit xt_tcpudp xt_addrtype iptable_filt
   iptable_raw ip_tables x_tables intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel ipmi_ssif aes_x86_64 
  _helper ablk_helper hpilo cryptd serio_raw sb_edac edac_core ioatdma lpc_ich 
shpchp 8250_fintek mac_hid acpi_power_meter ipmi_si ipmi_devintf 
ipmi_msghandler autofs4 raid10 raid456 async_raid6_reco
  ync_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
ixgbe dca vxlan ip6_udp_tunnel udp_tunnel ptp ahci pps_core psmouse libahci
   mdio wmi fjes [last unloaded: nf_conntrack]
  CPU: 13 PID: 0 Comm: swapper/13 Not tainted 4.4.0-78-generic #99-Ubuntu
   0286 24b314fc942cf971 88105f3439a8 813f8dd3
    81d71d78 88105f3439e0 81081302
   88088a1c5000 880cc988f800 004b 
  Call Trace:
 [] dump_stack+0x63/0x90
   [] warn_slowpath_common+0x82/0xc0
   [] warn_slowpath_null+0x1a/0x20
   [] tcp_fragment+0x34d/0x370
   [] tcp_mark_head_lost+0x14f/0x240
   [] tcp_update_scoreboard+0x4c/0x70
   [] tcp_fastretrans_alert+0x6f2/0xaa0
   [] tcp_ack+0x46b/0x800
   [] tcp_rcv_established+0x1d9/0x780
   [] ? sk_filter_trim_cap+0x42/0x160
   [] tcp_v4_do_rcv+0x145/0x200
   [] tcp_v4_rcv+0x872/0xa20
   [] ? iptable_filter_hook+0x27/0x56 [iptable_filter]
   [] ? nf_iterate+0x62/0x80
   [] ip_local_deliver_finish+0x94/0x1e0
   [] ip_local_deliver+0x6f/0xe0
   [] ? ip_rcv_finish+0x320/0x320
   [] ip_rcv_finish+0x92/0x320
   [] ip_rcv+0x291/0x3a0
   [] ? inet_del_offload+0x40/0x40
   [] __netif_receive_skb_core+0x704/0xa60
   [] ? tcp4_gro_receive+0x130/0x1d0
   [] __netif_receive_skb+0x18/0x60
   [] netif_receive_skb_internal+0x32/0xa0
   [] napi_gro_receive+0xc3/0x120
   [] gro_cell_poll+0x5a/0x90 [ip_tunnel]
   [] net_rx_action+0x21e/0x360
   [] __do_softirq+0x101/0x290
   [] irq_exit+0xa3/0xb0
   [] smp_call_function_single_interrupt+0x33/0x40
   [] call_function_single_interrupt+0x82/0x90
 [] ? cpuidle_enter_state+0x111/0x2b0
   [] cpuidle_enter+0x17/0x20
   [] call_cpuidle+0x32/0x60
   [] ? cpuidle_select+0x13/0x20
   [] cpu_startup_entry+0x290/0x350
   [] start_secondary+0x154/0x190
  ---[ end trace f0d076c2d7e8bb40 ]---

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

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


[Kernel-packages] [Bug 739746] ☂Re: Re: useful info

2017-06-16 Thread gimmigio
Hey friend,


This info may  be very  useful for  you, you won't regret,  just take a look at 
http://bit.do/dwB9Q

Warmest regards, Gianluca Martuscelli


From: Bug 739746 [mailto:739...@bugs.launchpad.net]
Sent: Friday, June 16, 2017 8:15 AM
To: gmartusce...@libero.it
Subject: Encourage

Thanks  for saying sorry,  seriously...   
 I'm  just sick of people  talking shit to people just for working at Comcast. 
I  don't get  paid  to write on this  sub, i  do it to help people,  and help 
people a lot and have  gotten  MANY thanks.  
  
And if you didn't "mean to  offend me" then  i feel REALY bad for anyone 
you DO mean to  offend, because that was rude  as hell.


Sent from Mail for Windows 10

** Attachment added: "483059F3B558E744E091A749012C1928.jpg"
   
https://bugs.launchpad.net/bugs/739746/+attachment/4897165/+files/483059F3B558E744E091A749012C1928.jpg

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

Title:
  bluetoothd crashed with SIGSEGV in g_main_context_dispatch()

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: bluez

  Don't know what I did but latest keys I pressed were  Super+6
  (activate Totem from Unity panel) and then I saw this crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: bluez 4.89-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-7.36-generic 2.6.38
  Uname: Linux 2.6.38-7-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Mon Mar 21 22:42:22 2011
  ExecutablePath: /usr/sbin/bluetoothd
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110320)
  InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
  MachineType: Hewlett-Packard Compaq 615
  ProcCmdline: /usr/sbin/bluetoothd --udev
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic 
root=UUID=6e5309ba-d57c-44a5-a02a-0ba7ab026458 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x548ff8:  mov0x4(%edi),%eax
   PC (0x00548ff8) ok
   source "0x4(%edi)" (0x0004) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? () from /lib/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/libglib-2.0.so.0
  Title: bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/17/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68GVV Ver. F.04
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 308C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 27.07
  dmi.chassis.asset.tag: CNU9326ML2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68GVVVer.F.04:bd07/17/2009:svnHewlett-Packard:pnCompaq615:pvrF.04:rvnHewlett-Packard:rn308C:rvrKBCVersion27.07:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: Compaq 615
  dmi.product.version: F.04
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:24:7E:7E:99:A1  ACL MTU: 1017:8  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:657 acl:0 sco:0 events:21 errors:0
TX bytes:340 acl:0 sco:0 commands:21 errors:0

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

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


[Kernel-packages] [Bug 1698299] Re: package linux-image-4.2.0-42-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2017-06-16 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  package linux-image-4.2.0-42-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  non-PAE kernel not supported

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-42-generic (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhyry  1172 F pulseaudio
  Date: Thu Jun 15 23:38:38 2017
  DpkgTerminalLog:
   Preparing to unpack .../linux-image-4.2.0-42-generic_4.2.0-42.49_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.2.0-42-generic_4.2.0-42.49_i386.deb 
(--unpack):
subprocess new pre-installation script returned error exit status 1
  DuplicateSignature: package:linux-image-4.2.0-42-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=dca97c1f-7ca0-4fe7-af28-2d9535205a92
  InstallationDate: Installed on 2015-04-28 (779 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  MachineType: Hewlett-Packard hp pavilion ze4900 (PR301UA#ABA)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic 
root=/dev/mapper/lubuntu--vg-root ro priority=low quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-29ubuntu0.3
  RfKill:
   0: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.2.0-42-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to wily on 2016-02-29 (472 days ago)
  dmi.bios.date: 11/09/2004
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.name: 3084
  dmi.board.vendor: Quanta
  dmi.board.version: 41.0B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd11/09/2004:svnHewlett-Packard:pnhppavilionze4900(PR301UA#ABA):pvrRev1:rvnQuanta:rn3084:rvr41.0B:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: hp pavilion ze4900 (PR301UA#ABA)
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1698348] Re: Bluetooth is not Working

2017-06-16 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc5

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

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

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

Title:
  Bluetooth is not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Devices are not being searched .Ubuntu 16.04 is the version

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   prashant   1833 F...m pulseaudio
   /dev/snd/controlC1:  prashant   1833 F pulseaudio
   /dev/snd/controlC0:  prashant   1833 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun 16 16:19:31 2017
  HibernationDevice: RESUME=UUID=0a483b1a-6963-4fde-acc5-1a072e0114c7
  InstallationDate: Installed on 2016-08-13 (306 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 3542
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=d0ba25a6-8a79-4837-9d88-62c640108868 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 066KRV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/20/2015:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn066KRV:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1697892] Re: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds

2017-06-16 Thread Joseph Salisbury
Will you not be able to test at all to see if these three patches work
as expected?  It is usually a requirement to submit an 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/1697892

Title:
  linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link
  speeds

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
Status in linux source package in Artful:
  In Progress

Bug description:
  These upstream patches are needed to correctly handle 5G, 25G and 50G
  speeds in 802.3ad:

  19ddde1eeca1 bonding: add 802.3ad support for 25G speeds
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e

  c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af

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

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


[Kernel-packages] [Bug 1543788] Re: Fails to resume from suspend

2017-06-16 Thread Igor Zinovyev
I seem to be affected by the same bug, here are the latest syslog
entries before the new boot. I'd be glad to use ubuntu-bug, but it only
reports current dmesg, which have nothing related to the previous boot.


-- There is a lot of these kind of messages about resume errors, I have to hold 
page down for a while to get past them --
Jun 16 15:36:37 precision kernel: [21082.801684] ehci-pci :0d:00.2: port 3 
resume error -19
Jun 16 15:36:37 precision systemd-sleep[1653]: Selected interface 
'p2p-dev-wlp2s0'
Jun 16 15:36:37 precision systemd-sleep[1653]: 'SUSPEND' command timed out.
Jun 16 15:36:37 precision systemd-sleep[1656]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
Jun 16 15:36:37 precision systemd-sleep[1653]: Suspending system...
Jun 16 15:36:37 precision kernel: [21082.832609] PM: Syncing filesystems ... 
Jun 16 15:36:37 precision kernel: [21082.837789] ehci-pci :0d:00.2: port 3 
resume error -19

Please let me know how I can help. I can run custom builds if necessary.

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

Title:
  Fails to resume from suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  Resuming from suspend used to work previously in 16.04.

  On resume I see a blank screen and nothing seems to respond. I've
  tried Ctrl+Alt+F1 and then Ctrl+Alt+Delete. Also tried the power
  button. No response.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shahar 2292 F pulseaudio
   /dev/snd/controlC0:  shahar 2292 F pulseaudio
   /dev/snd/controlC2:  shahar 2292 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Feb  9 22:51:40 2016
  HibernationDevice: RESUME=UUID=f2bd5594-8447-422c-a345-492ede4de1d9
  InstallationDate: Installed on 2010-10-12 (1946 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X10SRA
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-2-generic root=/dev/mapper/root 
ro nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2015-11-13 (88 days ago)
  dmi.bios.date: 11/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0a
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0a:bd11/27/2014:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X10SRA
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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

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


[Kernel-packages] [Bug 1689946] Re: Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with split op

2017-06-16 Thread Joseph Salisbury
I'd like to submit an SRU request to have commit f36ea50ca004 included
in Xenial.  However, I wanted to check an see if it is also needed in
the newer Ubuntu releases as well.

Commit f36ea50ca004 was included in mainline as of v4.12-rc1.  It
changes the location of blk_queue_split in blk_mq_make_request, which
was originally added by commit 54efd50bfd87 in v4.3-rc1.  That would
suggested that commit f36ea50ca004 is also needed in Yakkety, Zesty and
Artful.  Can you confirm this bug also exists in those releases and
require commit f36ea50ca004?

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

Title:
  Ubuntu16.04: NVMe 4K+T10 DIF/DIX format returns I/O error on dd with
  split op

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

Bug description:
   State: Open by: mdate on 19 March 2017 12:33:34 

  On a Bolt adapter in a system with Ubuntu 16.04, I've formatted the
  Bolt for T10 and am using it to do a dd with a 2M block size.

  Here are the commands:
  nvme format /dev/nvme0n1 --lbaf=1 --pil=0 --ms=0 --pi=2

  dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct count=1

  I get an error on the dd.
root@x1623bp1:~# dd if=/dev/urandom of=/dev/nvme0n1 bs=2M oflag=direct 
count=1
dd: error writing '/dev/nvme0n1': Input/output error
1+0 records in
0+0 records out
0 bytes copied, 0.0525061 s, 0.0 kB/s

  dmesg shows:
  [589997.985151] blk_update_request: I/O error, dev nvme0n1, sector 0

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

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


[Kernel-packages] [Bug 1698363] Re: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build

2017-06-16 Thread Colin Ian King
Hi Raymond,

Can there should be a log /var/lib/dkms/zfs*/*/build/make.log   - can
you add that to the bug report?

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

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

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  Performing system updates, not a user of zfs (at this point). Packages
  just failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-79-generic (x86_64)
   Fri Jun 16 07:19:28 CDT 2017
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-79-generic
  Date: Fri Jun 16 07:19:32 2017
  InstallationDate: Installed on 2014-10-19 (971 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  PackageVersion: 0.6.5.6-0ubuntu17
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (420 days ago)

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

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


[Kernel-packages] [Bug 1698363] [NEW] zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build

2017-06-16 Thread Raymond Meyer
Public bug reported:

Performing system updates, not a user of zfs (at this point). Packages
just failed to install.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: zfs-dkms 0.6.5.6-0ubuntu17
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
DKMSBuildLog:
 DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-79-generic (x86_64)
 Fri Jun 16 07:19:28 CDT 2017
 make: *** No targets specified and no makefile found.  Stop.
DKMSKernelVersion: 4.4.0-79-generic
Date: Fri Jun 16 07:19:32 2017
InstallationDate: Installed on 2014-10-19 (971 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723)
PackageVersion: 0.6.5.6-0ubuntu17
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: zfs-linux
Title: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build
UpgradeStatus: Upgraded to xenial on 2016-04-22 (420 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Performing system updates, not a user of zfs (at this point). Packages
  just failed to install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-79-generic (x86_64)
   Fri Jun 16 07:19:28 CDT 2017
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-79-generic
  Date: Fri Jun 16 07:19:32 2017
  InstallationDate: Installed on 2014-10-19 (971 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  PackageVersion: 0.6.5.6-0ubuntu17
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu17: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (420 days ago)

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

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


[Kernel-packages] [Bug 1698264] Re: Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker

2017-06-16 Thread Seth Forshee
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/16/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


[Kernel-packages] [Bug 1696357] s2lp6g001 (s390x.zKVM) - tests ran: 20, failed: 1

2017-06-16 Thread Brad Figg
tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-80.101-generic/s2lp6g001__4.4.0-80.101__2017-06-16_11-40-00/results-index.html

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

Title:
  linux: 4.4.0-80.101 -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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

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

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

  backports: 1696358
  derivatives: 1696359,1696360,1696362,1696363,1696364
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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


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

2017-06-16 Thread Thiago Alves Silva
apport information

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/16/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


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

2017-06-16 Thread Thiago Alves Silva
apport information

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/16/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


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

2017-06-16 Thread Thiago Alves Silva
apport information

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/16/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


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

2017-06-16 Thread Thiago Alves Silva
apport information

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/16/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


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

2017-06-16 Thread Thiago Alves Silva
apport information

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/16/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


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

2017-06-16 Thread Thiago Alves Silva
apport information

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/16/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


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

2017-06-16 Thread Thiago Alves Silva
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1698264/+attachment/4897095/+files/ProcCpuinfoMinimal.txt

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/16/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


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

2017-06-16 Thread Thiago Alves Silva
apport information

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/16/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


[Kernel-packages] [Bug 1698264] Re: Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker

2017-06-16 Thread Thiago Alves Silva
apport information

** Tags added: apport-collected ec2-images xenial

** Description changed:

  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)
  
  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)
  
  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot
  
  Expected behavior:
  - All containers should be terminated without any dangling process
  
  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.
  
  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the supported
  kernel.
  
  Thanks in advance
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 May 29 16:54 seq
+  crw-rw 1 root audio 116, 33 May 29 16:54 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.6
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse:
+  Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
+  Cannot stat file /proc/11652/fd/5: Stale file handle
+  Cannot stat file /proc/11652/fd/6: Stale file handle
+  Cannot stat file /proc/11652/fd/7: Stale file handle
+  Cannot stat file /proc/11652/fd/11: Stale file handle
+ DistroRelease: Ubuntu 16.04
+ Ec2AMI: ami-45b69e52
+ Ec2AMIManifest: (unknown)
+ Ec2AvailabilityZone: us-east-1c
+ Ec2InstanceType: t2.large
+ Ec2Kernel: unavailable
+ Ec2Ramdisk: unavailable
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ MachineType: Xen HVM domU
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 cirrusdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
+ ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-78-generic N/A
+  linux-backports-modules-4.4.0-78-generic  N/A
+  linux-firmware1.157.10
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial ec2-images
+ Uname: Linux 4.4.0-78-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 02/16/2017
+ dmi.bios.vendor: Xen
+ dmi.bios.version: 4.2.amazon
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Xen
+ dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
+ dmi.product.name: HVM domU
+ dmi.product.version: 4.2.amazon
+ dmi.sys.vendor: Xen

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 

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

2017-06-16 Thread Thiago Alves Silva
apport information

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

Title:
  Processes in "D" state due to zap_pid_ns_processes kernel call with
  Ubuntu + Docker

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (please refer to
  https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
  context)

  Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)

  Steps to reproduce:
  - Install latest Docker
  - Run 300 containers with health check (for i in {1..300}; do docker run -d 
-it --restart=always --name poc_$i talves/health_poc; done)
  - Send termination signal to the containers (docker kill -s TERM $(docker ps 
-q)
  - A few processes are going to be stuck in "uninterruptible sleep" ("D" 
state). The only know way to recover from this is host reboot

  Expected behavior:
  - All containers should be terminated without any dangling process

  Actual behavior:
  - Some processes are left in "D" state. In our production environment this 
leads over time to performance degradation and maintenance issues due to 
containers that cannot be stopped / removed.

  A fix is provided on kernel 4.12 - it would be nice if it could be
  backported and included in the next Ubuntu release within the
  supported kernel.

  Thanks in advance
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 29 16:54 seq
   crw-rw 1 root audio 116, 33 May 29 16:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse:
   Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with 
exit code 1: Cannot stat file /proc/11652/fd/4: Stale file handle
   Cannot stat file /proc/11652/fd/5: Stale file handle
   Cannot stat file /proc/11652/fd/6: Stale file handle
   Cannot stat file /proc/11652/fd/7: Stale file handle
   Cannot stat file /proc/11652/fd/11: Stale file handle
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-45b69e52
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1c
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.10
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-78-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/16/2017
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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


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

2017-06-16 Thread Joseph Salisbury
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/1698348

Title:
  Bluetooth is not Working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Devices are not being searched .Ubuntu 16.04 is the version

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   prashant   1833 F...m pulseaudio
   /dev/snd/controlC1:  prashant   1833 F pulseaudio
   /dev/snd/controlC0:  prashant   1833 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun 16 16:19:31 2017
  HibernationDevice: RESUME=UUID=0a483b1a-6963-4fde-acc5-1a072e0114c7
  InstallationDate: Installed on 2016-08-13 (306 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 3542
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=d0ba25a6-8a79-4837-9d88-62c640108868 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 066KRV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/20/2015:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn066KRV:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1698348] [NEW] Bluetooth is not Working

2017-06-16 Thread Prashant Chaurasia
Public bug reported:

Devices are not being searched .Ubuntu 16.04 is the version

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-78-generic 4.4.0-78.99
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   prashant   1833 F...m pulseaudio
 /dev/snd/controlC1:  prashant   1833 F pulseaudio
 /dev/snd/controlC0:  prashant   1833 F pulseaudio
CurrentDesktop: Unity
Date: Fri Jun 16 16:19:31 2017
HibernationDevice: RESUME=UUID=0a483b1a-6963-4fde-acc5-1a072e0114c7
InstallationDate: Installed on 2016-08-13 (306 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. Inspiron 3542
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=d0ba25a6-8a79-4837-9d88-62c640108868 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-78-generic N/A
 linux-backports-modules-4.4.0-78-generic  N/A
 linux-firmware1.157.8
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 066KRV
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/20/2015:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn066KRV:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3542
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Bluetooth is not Working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Devices are not being searched .Ubuntu 16.04 is the version

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   prashant   1833 F...m pulseaudio
   /dev/snd/controlC1:  prashant   1833 F pulseaudio
   /dev/snd/controlC0:  prashant   1833 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun 16 16:19:31 2017
  HibernationDevice: RESUME=UUID=0a483b1a-6963-4fde-acc5-1a072e0114c7
  InstallationDate: Installed on 2016-08-13 (306 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 3542
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=d0ba25a6-8a79-4837-9d88-62c640108868 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 066KRV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/20/2015:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn066KRV:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

2017-06-16 Thread Richard
I can confirm that 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 9 10:45:17 
UTC 2017 works
with a Gigabyte GA-AX370-Gaming 5 and UEFI version F5. (Ubuntu 16.04)

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Gigabyte AM4 boards users cannot boot Ubuntu successfully.
  Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf 
"pinctrl/amd: Use regular interrupt instead of chained" can fix the issue. 

  [Test Case]
  All Gigabyte AM4 boards can reproduce the issue.
  With the patch, the issue is resolved, per comment #170.

  [Regression Potential] 
  Regression Potential is low. It limits to rather new AMD platform which has 
pinctrl-amd. 
  As the commit log says, use chained interrupt is not a good idea. Use regular 
interrupt is the correct way.

  I also test the patch on an AMD laptop, where its touchpad depends on
  pinctrl-amd. No regression found.

  Original bug report:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  Following advice from various places, I've tried:disable cpu freq
  governor and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090,
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090,
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20,
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090,
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20,
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:

  _MarkForUpload: True

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

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


  1   2   >