[Kernel-packages] [Bug 1681313] Re: "port does not support device sleep" on Dell Precision 5520

[TomaszChmielewski]

It's still showing up with pcie_aspm=off (and ppa kernel):

$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.11.0-041100rc6-generic 
root=UUID=e38db0de-7f52-4cab-839b-6bfb046d4665 ro acpi_rev_override quiet 
splash vt.handoff=7 pcie_aspm=off


$ dmesg
(...)
[  352.877941] ata2.00: exception Emask 0x10 SAct 0x100 SErr 0x405 
action 0xe frozen
[  352.877946] ata2.00: irq_stat 0x0040, connection status changed
[  352.877948] ata2: SError: { PHYRdyChg CommWake DevExch }
[  352.877952] ata2.00: failed command: READ FPDMA QUEUED
[  352.877957] ata2.00: cmd 60/08:c0:18:f6:f0/00:00:11:00:00/40 tag 24 ncq dma 
4096 in
res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA 
bus error)
[  352.877959] ata2.00: status: { DRDY }
[  352.877963] ata2: hard resetting link
[  353.590145] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  353.591464] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[  353.591466] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
[  353.591468] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
[  353.591564] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device 
(Stat=0x51 Err=0x04)
[  353.594283] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[  353.594285] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
[  353.594286] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
[  353.594354] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device 
(Stat=0x51 Err=0x04)
[  353.595861] ata2.00: configured for UDMA/133
[  353.595865] ahci :00:17.0: port does not support device sleep
[  353.595921] ata2: EH complete
[  358.035306] ata2.00: exception Emask 0x10 SAct 0x800 SErr 0x405 action 
0xe frozen
[  358.035309] ata2.00: irq_stat 0x0040, connection status changed
[  358.035310] ata2: SError: { PHYRdyChg CommWake DevExch }
[  358.035311] ata2.00: failed command: READ FPDMA QUEUED
[  358.035314] ata2.00: cmd 60/08:58:90:f8:f0/00:00:11:00:00/40 tag 11 ncq dma 
4096 in
res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA 
bus error)
[  358.035315] ata2.00: status: { DRDY }
[  358.035317] ata2: hard resetting link
[  358.747460] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  358.748472] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[  358.748474] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
[  358.748475] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
[  358.748507] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device 
(Stat=0x51 Err=0x04)
[  358.750983] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[  358.750985] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
[  358.750985] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
[  358.751030] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device 
(Stat=0x51 Err=0x04)
[  358.752636] ata2.00: configured for UDMA/133
[  358.752640] ahci :00:17.0: port does not support device sleep
[  358.752680] ata2: EH complete

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

Title:
  "port does not support device sleep" on Dell Precision 5520

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm seeing messages like below on Dell Precision 5520, which is on an
  Ubuntu certified hardware list:

  https://certification.ubuntu.com/hardware/201610-25144/

  BIOS is updated to the latest version available: 1.1.3

  The system has this SATA controller:

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA
  controller [AHCI mode] (rev 31)

  And this 256 GB SSD disk:

  Model Number:   SanDisk X400 2.5 7MM 256GB
  Firmware Revision:  X4130012

  There is a firmware upgrade available for SSD storage on Dell website,
  but unfortunately, the installer is Windows only (a weird thing for a
  Ubuntu certified hardware IMO) - therefore, I was no able to apply it.

  dmesg entries which show up follow below:

  [35713.825698] ata2.00: exception Emask 0x10 SAct 0x4 SErr 0x405 action 
0xe frozen
  [35713.825701] ata2.00: irq_stat 0x0040, connection status changed
  [35713.825703] ata2: SError: { PHYRdyChg CommWake DevExch }
  [35713.825704] ata2.00: failed command: WRITE FPDMA QUEUED
  [35713.825707] ata2.00: cmd 61/18:10:e0:8d:0a/00:00:12:00:00/40 tag 2 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [35713.825709] ata2.00: status: { DRDY }
  [35713.825711] ata2: hard resetting link
  [35714.549641] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [35714.550813] ata2.00: ACPI cmd 

[Kernel-packages] [Bug 1680733] Re: linux: 3.13.0-117.164 -proposed tracker

[Steve Beattie]

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

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

Title:
  linux: 3.13.0-117.164 -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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[NancyHsu]

On official kernel 4.4.0-31, we use below command upgrade to 4.4.0-72.93. The 
bug still exist.
sudo apt-get update
sudo apt-get dist-upgrade

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1681313] Re: "port does not support device sleep" on Dell Precision 5520

[Francisco Cribari]

Try booting with the following kernel parameter: pcie_aspm=off

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

Title:
  "port does not support device sleep" on Dell Precision 5520

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm seeing messages like below on Dell Precision 5520, which is on an
  Ubuntu certified hardware list:

  https://certification.ubuntu.com/hardware/201610-25144/

  BIOS is updated to the latest version available: 1.1.3

  The system has this SATA controller:

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA
  controller [AHCI mode] (rev 31)

  And this 256 GB SSD disk:

  Model Number:   SanDisk X400 2.5 7MM 256GB
  Firmware Revision:  X4130012

  There is a firmware upgrade available for SSD storage on Dell website,
  but unfortunately, the installer is Windows only (a weird thing for a
  Ubuntu certified hardware IMO) - therefore, I was no able to apply it.

  dmesg entries which show up follow below:

  [35713.825698] ata2.00: exception Emask 0x10 SAct 0x4 SErr 0x405 action 
0xe frozen
  [35713.825701] ata2.00: irq_stat 0x0040, connection status changed
  [35713.825703] ata2: SError: { PHYRdyChg CommWake DevExch }
  [35713.825704] ata2.00: failed command: WRITE FPDMA QUEUED
  [35713.825707] ata2.00: cmd 61/18:10:e0:8d:0a/00:00:12:00:00/40 tag 2 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [35713.825709] ata2.00: status: { DRDY }
  [35713.825711] ata2: hard resetting link
  [35714.549641] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [35714.550813] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.550816] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.550818] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.550975] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.553832] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.553835] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.553837] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.553886] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.555383] ata2.00: configured for UDMA/133
  [35714.555399] ahci :00:17.0: port does not support device sleep
  [35714.555493] ata2: EH complete
  [36324.490477] ata2.00: exception Emask 0x10 SAct 0x4000 SErr 0x405 
action 0xe frozen
  [36324.490480] ata2.00: irq_stat 0x0040, connection status changed
  [36324.490482] ata2: SError: { PHYRdyChg CommWake DevExch }
  [36324.490484] ata2.00: failed command: WRITE FPDMA QUEUED
  [36324.490487] ata2.00: cmd 61/18:f0:68:08:85/00:00:07:00:00/40 tag 30 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [36324.490488] ata2.00: status: { DRDY }
  [36324.490490] ata2: hard resetting link
  [36325.214543] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [36325.215658] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [36325.215660] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [36325.215662] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [36325.215731] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [36325.218240] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [36325.218242] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [36325.218243] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [36325.218293] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [36325.219965] ata2.00: configured for UDMA/133
  [36325.219982] ahci :00:17.0: port does not support device sleep
  [36325.220079] ata2: EH complete
  [38355.555685] ata2.00: exception Emask 0x10 SAct 0x800 SErr 0x405 
action 0xe frozen
  [38355.555688] ata2.00: irq_stat 0x0040, connection status changed
  [38355.555690] ata2: SError: { PHYRdyChg CommWake DevExch }
  [38355.555693] ata2.00: failed command: READ FPDMA QUEUED
  [38355.555695] ata2.00: cmd 60/20:d8:78:b4:3a/00:00:12:00:00/40 tag 27 ncq 
16384 in
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [38355.555697] ata2.00: status: { DRDY }
  [38355.555699] ata2: hard resetting link
  [38356.282999] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [38356.284112] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [38356.284114] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 

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

[Travisgevans]

I also haven't personally encountered any further OOM issues on my home
desktop (used daily) with 4.4.0.63.

-- 
You 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 source package in Xenial:
  Fix Released

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 1680416] Re: linux: 4.4.0-73.94 -proposed tracker

[Steve Beattie]

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

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

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

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1680416/+subscriptions

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

[Kernel-packages] [Bug 1681602] [NEW] Please remove linux-goldfish from the archive

[Steve Beattie]

Public bug reported:

The linux-goldfish (android derived linux kernel for Android touch
emulation on i386/armhf) package has not been regularly updated ands
contain a large number of unfixed security issues:

  http://people.canonical.com/~ubuntu-security/cve/pkg/linux-
goldfish.html

The Ubuntu kernel team is not maintaining this kernel. Please remove.

Thanks!

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

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

Title:
  Please remove linux-goldfish from the archive

Status in linux-goldfish package in Ubuntu:
  New

Bug description:
  The linux-goldfish (android derived linux kernel for Android touch
  emulation on i386/armhf) package has not been regularly updated ands
  contain a large number of unfixed security issues:

http://people.canonical.com/~ubuntu-security/cve/pkg/linux-
  goldfish.html

  The Ubuntu kernel team is not maintaining this kernel. Please remove.

  Thanks!

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

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

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

[bugproxy]

--- Comment From cha...@us.ibm.com 2017-04-10 19:38 EDT---
Since we don't have an XFS developer in-house, does Canonical have any 
suggestions on what kernel config options or debug facilities we can use in the 
event this is reproducible?

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

Title:
  Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Lata Kuntal  - 2017-03-30 09:44:23 ==
  Ubuntu 17.04 KVM guest gusg8 was having ubuntu 16.04.2 and was running stress 
test IO, Base,TCP and NFS.The guest is having XFS as rootFS and after running 
few hours of regression test it dropped at xmon.

  Console logs :
  
  root@guskvm:~# virsh console gusg8 --force
  Connected to domain gusg8
  Escape character is ^]

  
  1:mon> r
  R00 = d288edf4   R16 = 024200ca
  R01 = c000378cb1f0   R17 = 
  R02 = d2936080   R18 = 0020
  R03 = 0001   R19 = c002734d1800
  R04 = c000378cb190   R20 = 
  R05 =    R21 = 
  R06 = 3c00d03fe056   R22 = c0027e26ccf0
  R07 =    R23 = 
  R08 = c48492d0   R24 = 
  R09 = 3c00d03fe056   R25 = 
  R10 = 3c00d03fe062   R26 = 00024df4cd49
  R11 = d28fa360   R27 = 
  R12 =    R28 = d28ac7b0
  R13 = cfb80900   R29 = c4849000
  R14 =    R30 = 
  R15 = c137ad08   R31 = 
  pc  = d288ee0c xfs_perag_get_tag+0x6c/0x170 [xfs]
  cfar= c096a494 perf_trace_mmc_request_start+0x104/0x440
  lr  = d288edf4 xfs_perag_get_tag+0x54/0x170 [xfs]
  msr = 80010280b033   cr  = 82428424
  ctr = c05e4950   xer = 2000   trap =  300
  dar = 3c00d03fe062   dsisr = 4000
  1:mon> t
  [c000378cb250] d28ac7b0 xfs_reclaim_inodes_count+0x70/0xa0 [xfs]
  [c000378cb290] d28c0ea8 xfs_fs_nr_cached_objects+0x28/0x40 [xfs]
  [c000378cb2b0] c03292d8 super_cache_count+0x68/0x120
  [c000378cb2f0] c0271530 shrink_slab.part.14+0x150/0x4f0
  [c000378cb430] c0276db8 shrink_node+0x158/0x3f0
  [c000378cb4f0] c0277178 do_try_to_free_pages+0x128/0x460
  [c000378cb590] c02775ac try_to_free_pages+0xfc/0x280
  [c000378cb620] c0260158 __alloc_pages_nodemask+0x758/0xe30
  [c000378cb7e0] c02dbb98 alloc_pages_vma+0x108/0x360
  [c000378cb880] c029d080 wp_page_copy+0xf0/0x9d0
  [c000378cb920] c02a0770 do_wp_page+0x210/0xb20
  [c000378cb9b0] c02a656c handle_mm_fault+0x9cc/0x14c0
  [c000378cba60] c0b511a0 do_page_fault+0x260/0x7d0
  [c000378cbb10] c0008948 handle_page_fault+0x10/0x30
  --- Exception: 301 (Data Access) at c010aec4 schedule_tail+0x84/0xb0
  [c000378cbe30] c0009844 ret_from_fork+0x4/0x54
  --- Exception: c00 (System Call) at 3fffa2b5bf44
  1:mon> d
      ||
  1:mon> c
  cpus stopped: 0x0-0x3
  1:mon>

  Kernel host build
  =
  root@guskvm:~# uname -r
  4.10.0-13-generic
  root@guskvm:~#

  
  == Comment: #1 - Luciano Chavez  - 2017-03-30 10:42:15 ==
  At first glance, based on the following assembly from around the failure 
point:

  d288edd4  38c1  li  r6,1
  d288edd8  7f8802a6  mflrr28
  d288eddc  78a70020  clrldi  r7,r5,32
  d288ede0  7c7d1b78  mr  r29,r3
  d288ede4  7c852378  mr  r5,r4
  d288ede8  386302c8  addir3,r3,712
  d288edec  38810020  addir4,r1,32
  d288edf0  4806b571  bl  d28fa360# 
exit_xfs_fs+0x180c/0xfd44 [xfs]
  d288edf4  e8410018  ld  r2,24(r1)
  d288edf8  2f83  cmpwi   cr7,r3,0
  d288edfc  409d0104  ble cr7,d288ef00# 
xfs_perag_get_tag+0x160/0x170 [xfs]
  d288ee00  7c0004ac  sync
  d288ee04  e9210020  ld  r9,32(r1)
  d288ee08  3949000c  addir10,r9,12
  d288ee0c  7fc05028  lwarx   r30,0,r10
  d288ee10  33de0001  addic   r30,r30,1
  d288ee14  7fc0512d  stwcx.  r30,0,r10

  I believe the crash in fs_perag_get_tag() is after we come back from
  the radix_tree_gang_lookup_tag() call and are attempting the
  atomic_inc_return() and struct xfs_perag*pag is R09 =
  3c00d03fe056 which is invalid.

   85 rcu_read_lock();  
 
   86 

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

[Anton]

Yes, 4.4.0.63 solved our OOM issues (and we had plenty after 4.4.0.59).
Ours were all headless server (bare metal and VMs) related though - no
desktop usage.

But I never experienced this issue with my home laptop either, but that
had lots of RAM and was only lightly used during that period - not
really a good data point.

-- 
You 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 source package in Xenial:
  Fix Released

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 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails

[Joshua Powers]

** Changed in: cloud-init
   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/1499869

Title:
  maas wily deployment to HP Proliant m400 arm64 server cartridge fails

Status in cloud-init:
  Fix Released
Status in curtin:
  Invalid
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in cloud-init source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  This is the error seen on the console:

  [   64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: 
Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin
  [  124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - 
url_helper.py[WARNING]: Calling 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
[2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', 
port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id 
(Caused by 
ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect 
timeout=50.0)'))]
  [  124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - 
DataSourceEc2.py[CRITICAL]: Giving up on md from 
['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds
  [  124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - 
url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404]

  This times out eventually and the node is left at the login prompt. I
  can install wily via netboot without issue and some time back, wily
  was deployable to this node from MAAS.

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

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

[Kernel-packages] [Bug 1679678] Re: linux: 4.8.0-47.50 -proposed tracker

[Steve Beattie]

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

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

Title:
  linux: 4.8.0-47.50 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux 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: 1679679,1679682
  derivatives: 1679684
  -- 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/1679678/+subscriptions

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

[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference

[Greg Lutostanski]

Only time I have been able to cause it was high load with lxcs and
graphics load (via unity). The mainline does not seem to let my lxd
instance load.

Unfortunately my lxd setup does not work with the mainline, [due to
snaps/lxd/zfs, one of the above probably](so it will make repro much
harder, and stop me from actual work) so I don't think I'll be able to
hit it again...

If I can get the above to repro at some later date I will let you know.

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

Title:
  zesty unable to handle kernel NULL pointer dereference

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to zesty about a week ago. Ran into this on latest kernel.
  (during high load, nothing in particular seems to cause it to happen).

  Did not happen with previous (4.10.0.14.16) kernel. Only after update
  to 4.10.0.15.17, has happened about 3 times since then (or other
  crashes), this is the one I could capture.

  kern.log entries below. Let me know if you need anything else from me.

  Thanks!

  
  Apr  7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL 
pointer dereference at 0018
  Apr  7 11:20:28 doe kernel: [26003.796375] IP: 
gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.796404] PGD 0
  Apr  7 11:20:28 doe kernel: [26003.796405]
  Apr  7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP
  Apr  7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT 
nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep 
zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 
hid_multitouch joydev i2c_designware_platform i2c_designware_core 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp 
snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core asus_nb_wmi
  Apr  7 11:20:28 doe kernel: [26003.796722]  snd_hwdep asus_wmi sparse_keymap 
snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp 
uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops 
irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 
videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm 
elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf 
industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad 
int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi 
acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb 
int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless 
parport_pc ppdev lp parport ip_tables
  Apr  7 11:20:28 doe kernel: [26003.797026]  x_tables autofs4 algif_skcipher 
af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm 
wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
  Apr  7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: 
chromium-browse Tainted: P   O4.10.0-15-generic #17-Ubuntu
  Apr  7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER 
INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015
  Apr  7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: 
c25b5ea8c000
  Apr  7 11:20:28 doe kernel: [26003.797250] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 
00010246
  Apr  7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 
0003 RCX: 0003
  Apr  7 11:20:28 doe kernel: [26003.797325] RDX:  RSI: 
9bbae7c0a000 RDI: 9bbba0418000
  Apr  7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: 
 R09: 
  Apr  7 11:20:28 doe kernel: [26003.797378] R10:  R11: 
0041 R12: 9bbb5f00a000
  Apr  7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: 
fff97000 R15: 8000
  Apr  7 11:20:28 doe kernel: [26003.797440] FS:  7f70bd1df6c0() 
GS:93c0() knlGS:
  Apr  7 11:20:28 doe kernel: [26003.797470] CS:  0010 DS:  ES:  CR0: 
80050033
  Apr  7 

[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference

[Greg Lutostanski]

Speak of the devil... happened again on, will try with upstream kernel.

Linux doe 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680904/+attachment/4859878/+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/1680904

Title:
  zesty unable to handle kernel NULL pointer dereference

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to zesty about a week ago. Ran into this on latest kernel.
  (during high load, nothing in particular seems to cause it to happen).

  Did not happen with previous (4.10.0.14.16) kernel. Only after update
  to 4.10.0.15.17, has happened about 3 times since then (or other
  crashes), this is the one I could capture.

  kern.log entries below. Let me know if you need anything else from me.

  Thanks!

  
  Apr  7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL 
pointer dereference at 0018
  Apr  7 11:20:28 doe kernel: [26003.796375] IP: 
gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.796404] PGD 0
  Apr  7 11:20:28 doe kernel: [26003.796405]
  Apr  7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP
  Apr  7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT 
nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep 
zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 
hid_multitouch joydev i2c_designware_platform i2c_designware_core 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp 
snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core asus_nb_wmi
  Apr  7 11:20:28 doe kernel: [26003.796722]  snd_hwdep asus_wmi sparse_keymap 
snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp 
uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops 
irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 
videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm 
elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf 
industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad 
int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi 
acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb 
int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless 
parport_pc ppdev lp parport ip_tables
  Apr  7 11:20:28 doe kernel: [26003.797026]  x_tables autofs4 algif_skcipher 
af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm 
wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
  Apr  7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: 
chromium-browse Tainted: P   O4.10.0-15-generic #17-Ubuntu
  Apr  7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER 
INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015
  Apr  7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: 
c25b5ea8c000
  Apr  7 11:20:28 doe kernel: [26003.797250] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 
00010246
  Apr  7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 
0003 RCX: 0003
  Apr  7 11:20:28 doe kernel: [26003.797325] RDX:  RSI: 
9bbae7c0a000 RDI: 9bbba0418000
  Apr  7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: 
 R09: 
  Apr  7 11:20:28 doe kernel: [26003.797378] R10:  R11: 
0041 R12: 9bbb5f00a000
  Apr  7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: 
fff97000 R15: 8000
  Apr  7 11:20:28 doe kernel: [26003.797440] FS:  7f70bd1df6c0() 
GS:93c0() knlGS:
  Apr  7 11:20:28 doe kernel: [26003.797470] CS:  0010 DS:  ES:  CR0: 
80050033
  Apr  7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 
00016942 CR4: 003406f0
  Apr  7 11:20:28 doe kernel: 

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

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/onza__3.13.0-117.164__2017-04-10_19-26-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1637550] Re: [Feature] R3 mwait support for Knights Mill

[Robert Hooker]

** Changed in: intel
   Status: Fix Committed => 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/1637550

Title:
  [Feature] R3 mwait support for Knights Mill

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Enable r3 mwait for  Knights Mill.

  Schedule:
  upstream: 4.11 kernel

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

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

[Kernel-packages] [Bug 1645963] Re: [Feature] GLK Northpeak Enabling

[Robert Hooker]

** Changed in: intel
   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/1645963

Title:
  [Feature] GLK Northpeak Enabling

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

Bug description:
  The NPK(North Peak) solution is composed of four major components.Hardware to 
connect the debug target to the host. DAL (DFX Abstraction Layer) to manage the 
target to host connection. NPKSDK connects to DAL and processes trace data 
using a decoder network.
  GUI and command line tools provide access to NPKSDK to configure and start / 
stop tracing.
  In GLK we have also Core side tracing that is new enabling.

  HW: Gemini Lake

  Upstream schedule:
  kernel: 4.11

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

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

[Kernel-packages] [Bug 1677057] Re: kernel hung, bug in swapops.h,

[Gilles Seguin]

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

** This bug has been marked a duplicate of bug 1674838
   kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

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

Title:
  kernel hung, bug in swapops.h,

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

Bug description:
  Machine locked up while reading mail with thunderbird.  I was able to
  catch the following error before the machine finally locked up:

  [ 3652.739499] [ cut here ]
  [ 3652.739543] kernel BUG at 
/build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129!
  [ 3652.739569] invalid opcode:  [#1] SMP
  [ 3652.739582] Modules linked in: xt_conntrack ipt_REJECT nf_reject_ipv4 
ebtable_filter ebtables ip6table_filter ip6_tables xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c xt_tcpudp bridge stp 
llc iptable_filter binfmt_misc zfs(PO) dm_crypt zunicode(PO) zavl(PO) 
zcommon(PO) znvpair(PO) spl(O) intel_rapl x86_pkg_temp_thermal intel_powerclamp 
arc4 coretemp rtl8192ce kvm_intel kvm rtl_pci irqbypass crct10dif_pclmul 
snd_hda_codec_hdmi rtl8192c_common crc32_pclmul ghash_clmulni_intel rtlwifi 
snd_hda_codec_realtek pcbc aesni_intel mac80211 aes_x86_64 crypto_simd 
glue_helper snd_hda_codec_generic cryptd intel_cstate intel_rapl_perf cfg80211 
snd_hda_intel uvcvideo snd_hda_codec snd_hda_core videobuf2_vmalloc
  [ 3652.739797]  videobuf2_memops snd_hwdep videobuf2_v4l2 videobuf2_core 
videodev media shpchp snd_seq_midi snd_pcm snd_seq_midi_event input_leds joydev 
serio_raw thinkpad_acpi snd_rawmidi nvram lpc_ich mei_me mei snd_seq 
snd_seq_device snd_timer snd soundcore mac_hid parport_pc ppdev lp parport 
ip_tables x_tables autofs4 btrfs xor raid6_pq hid_generic usbhid hid i915 
psmouse ahci i2c_algo_bit drm_kms_helper sdhci_pci libahci e1000e sdhci 
syscopyarea sysfillrect sysimgblt ptp fb_sys_fops pps_core drm wmi fjes video
  [ 3652.739941] CPU: 0 PID: 7826 Comm: thunderbird Tainted: P   O
4.10.0-14-generic #16-Ubuntu
  [ 3652.739968] Hardware name: LENOVO 2320CTO/2320CTO, BIOS G2ET31WW (1.11 ) 
05/24/2012
  [ 3652.739992] task: 8d420b004380 task.stack: a277cca0c000
  [ 3652.740014] RIP: 0010:__migration_entry_wait+0x16a/0x180
  [ 3652.740030] RSP: :a277cca0fd68 EFLAGS: 00010246
  [ 3652.740047] RAX: 0017c0048078 RBX: f1044ed42370 RCX: 
f1044ed42370
  [ 3652.740069] RDX: 0001 RSI: 8d41f508d800 RDI: 
f1044c8dc000
  [ 3652.740090] RBP: a277cca0fd80 R08: 8d41e378ec80 R09: 
8d41e378ec80
  [ 3652.740112] R10: 7fc2f1d000c8 R11: 0206 R12: 
f1044c8dc000
  [ 3652.740134] R13: 3e323700 R14: a277cca0fe30 R15: 
8d417b8d1e10
  [ 3652.740156] FS:  7fc2f3161740() GS:8d425e20() 
knlGS:
  [ 3652.740180] CS:  0010 DS:  ES:  CR0: 80050033
  [ 3652.740198] CR2: 7fc2b9500018 CR3: 00039ac5e000 CR4: 
001406f0
  [ 3652.740219] Call Trace:
  [ 3652.740231]  migration_entry_wait+0x74/0x80
  [ 3652.740247]  do_swap_page+0x5b3/0x770
  [ 3652.740261]  handle_mm_fault+0x873/0x1360
  [ 3652.740276]  __do_page_fault+0x23e/0x4e0
  [ 3652.740290]  do_page_fault+0x22/0x30
  [ 3652.740304]  page_fault+0x28/0x30
  [ 3652.740316] RIP: 0033:0x565503cc606c
  [ 3652.740328] RSP: 002b:7fff81758970 EFLAGS: 00010207
  [ 3652.740345] RAX:  RBX: 7fc2f1d00040 RCX: 
7fc2f1fd60b7
  [ 3652.740366] RDX: 0008 RSI: 2000 RDI: 
7fc2b95cb000
  [ 3652.740388] RBP: 7fc2b950 R08: 7fc2f1d000c8 R09: 

  [ 3652.740409] R10: 7fc2f1d000c8 R11: 0206 R12: 
0200
  [ 3652.740431] R13: 7fc2f1d000c8 R14: 00ca R15: 
0002
  [ 3652.740453] Code: ff ff ff 4c 89 e7 e8 86 a2 f8 ff e9 3c ff ff ff 85 d2 0f 
84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 
4c 89 e7 e8 1c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 1b eb 
  [ 3652.740525] RIP: __migration_entry_wait+0x16a/0x180 RSP: a277cca0fd68
  [ 3652.744504] ---[ end trace 0f3e466d2ae6c0fb ]---

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

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

[Kernel-packages] [Bug 1677057] Re: kernel hung, bug in swapops.h,

[Gilles Seguin]

Also ran into this bug on XUbuntu 17.04 beta 2 while browsing on Firefox
Computer is AMD R7 1700 / Asus Prime B350 / NVidia GTX 560 Ti

Apr 10 20:48:38 R7-1700 kernel: [ 1914.026456] [ cut here 
]
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026459] kernel BUG at 
/build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129!
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026461] invalid opcode:  [#1] SMP
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026462] Modules linked in: 
snd_hda_codec_hdmi nvidia_uvm(POE) nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) snd_hda_intel snd_hda_codec snd_oxygen snd_hda_core snd_oxygen_lib 
snd_hwdep snd_mpu401_uart snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer snd joydev input_leds soundcore drm_kms_helper 
drm eeepc_wmi asus_wmi fb_sys_fops syscopyarea sparse_keymap sysfillrect 
sysimgblt eeprom video ccp shpchp i2c_piix4 edac_mce_amd edac_core kvm wmi 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
aes_x86_64 crypto_simd glue_helper cryptd mac_hid 8250_dw 
i2c_designware_platform i2c_designware_core it87(OE) hwmon_vid parport_pc ppdev 
lp parport ip_tables x_tables autofs4 hid_generic usbhid hid r8169 ahci mii 
libahci fjes gpio_amdpt gpio_generic
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026482] CPU: 2 PID: 2069 Comm: JS Helper 
Tainted: P   OE   4.10.0-14-generic #16-Ubuntu
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026483] Hardware name: System 
manufacturer System Product Name/PRIME B350-PLUS, BIOS 0513 03/20/2017
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026484] task: 9422136c 
task.stack: a7bbc903c000
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026488] RIP: 
0010:__migration_entry_wait+0x16a/0x180
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026489] RSP: :a7bbc903fd68 
EFLAGS: 00010246
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026490] RAX: 0017c0048078 RBX: 
d7055f58d0f0 RCX: d7055f58d0f0
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026490] RDX: 0001 RSI: 
942216343800 RDI: d7055c804000
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026491] RBP: a7bbc903fd80 R08: 
942236c79f00 R09: 942236c79f00
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026492] R10: 7f4f4d5000c8 R11: 
0206 R12: d7055c804000
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026492] R13: 3e720100 R14: 
a7bbc903fe30 R15: 942213e35130
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026494] FS:  7f4f367ef700() 
GS:94225ec8() knlGS:
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026494] CS:  0010 DS:  ES:  CR0: 
80050033
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026495] CR2: 7f4f19700018 CR3: 
0007f3318000 CR4: 003406e0
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026496] Call Trace:
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026499]  migration_entry_wait+0x74/0x80
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026500]  do_swap_page+0x5b3/0x770
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026502]  handle_mm_fault+0x873/0x1360
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026504]  __do_page_fault+0x23e/0x4e0
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026505]  do_page_fault+0x22/0x30
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026507]  page_fault+0x28/0x30
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026508] RIP: 0033:0x555d1c6593b4
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026509] RSP: 002b:7f4f367eec30 
EFLAGS: 00010203
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026509] RAX:  RBX: 
7f4f4d500040 RCX: 7f4f4d73c137
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026510] RDX: 0008 RSI: 
2000 RDI: 7f4f19799000
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026511] RBP: 7f4f1970 R08: 
7f4f4d5000c8 R09: 
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026511] R10: 7f4f4d5000c8 R11: 
0206 R12: 0080
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026512] R13: 7f4f4d5000c8 R14: 
0098 R15: 0002
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026513] Code: ff ff ff 4c 89 e7 e8 86 a2 
f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 
39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 1c fb f9 ff eb b8 4c 8d 60 ff 4c 8d 
68 1b eb 
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026527] RIP: 
__migration_entry_wait+0x16a/0x180 RSP: a7bbc903fd68
Apr 10 20:48:38 R7-1700 kernel: [ 1914.026529] ---[ end trace b2b4260353f2375f 
]---

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

Title:
  kernel hung, bug in swapops.h,

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

Bug description:
  Machine locked up while reading mail with thunderbird.  I was able to
  catch the following error before the machine finally locked up:

  [ 3652.739499] [ cut here ]
  [ 3652.739543] kernel BUG at 

[Kernel-packages] [Bug 1672850] Re: [MIR] linux-aws

[Steve Langasek]

promoting to main for xenial-updates and xenial-security.

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

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

Title:
  [MIR] linux-aws

Status in linux-aws package in Ubuntu:
  Fix Released

Bug description:
  We would like to request the linux-aws kernel package be promoted to
  Main for 16.04.

  [Availability]

  The linux-aws kernel package is currently available in Universe for
  16.04.  It successfully builds against amd64 which is the target arch
  to be supported.

  [Rationale]

  The plan is to switch the Ubuntu AMI’s to default to the linux-aws
  kernel, which will have widespread impact for all newly deployed
  instances in AWS.  We, the Canonical Kernel Team, will stand behind
  and fully support this kernel.  It makes sense for this to be promoted
  to Main.

  [Security]

  The linux-aws kernel is based on the stock linux v4.4 based GA Ubuntu
  kernel available in 16.04.  Linux-aws will naturally inherit all
  existing security support and maintenance provided for the stock linux
  v4.4 based GA Ubuntu kernel in 16.04.  The linux kernel package is
  already in Main.

  [Quality assurance]

  The linux-aws kernel will undergo the same 3 week kernel SRU process
  and follow the same SRU requirements for proposed changes.  This
  include bug verification and Kernel SRU testing.

  [Dependencies]

  None

  [Standards compliance]

  The linux-aws kernel adheres to the same level of standards presented
  for the existing linux Ubuntu kernel.

  [Maintenance]

  The Canonical Kernel Team (~canonical-kernel-team) will commit to full
  security maintenance and support of linux-aws for the duration of the
  16.04 LTS release.

  [Background information]

  See above.

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

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

[Kernel-packages] [Bug 1413440] Re: USB stops working after a while (xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command)

[Max Rumpf]

I also have this issue on my Asus M5A99X EVO motherboard with a AMD
FX-4100 CPU; Ubuntu 16.10 and kernel version 4.8.0-46-generic.

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

Title:
  USB stops working after a while (xhci_hcd :00:14.0: Timeout while
  waiting for setup device command)

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On my laptop the kernel will sometimes drop the USB hub. After this,
  the laptop doesn't recognise any device plugged in to the USB ports -
  plugging and unplugging any device I've tried into any of the USB
  ports produces no response, not even dmesg entries.

  Strangely this also applies to bluetooth - it no longer works once USB
  has dropped (possibly the module is hung of the bus internally).

  Once this has happened only a reboot fixes it; I've not managed to
  find any combination of module unload/reload or suspend cycles to
  reinitialise things correctly.

  Relevant snippet of dmesg:
  [48830.625057] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079718] xhci_hcd :00:14.0: Stopped the command ring failed, maybe 
the host is dead
  [48838.079742] xhci_hcd :00:14.0: Abort command ring failed
  [48838.079746] xhci_hcd :00:14.0: HC died; cleaning up
  [48838.079770] xhci_hcd :00:14.0: Timeout while waiting for setup device 
command
  [48838.079806] sched: RT throttling activated
  [48838.079981] usb 1-1: USB disconnect, device number 16
  [48838.079985] usb 1-1.2: USB disconnect, device number 18
  [48838.079987] usb 1-1.2.3: USB disconnect, device number 19
  [48838.080285] usb 1-1.2.4: USB disconnect, device number 20
  [48838.111892] usb 1-1.4: USB disconnect, device number 17
  [48838.191292] usb 1-4: USB disconnect, device number 6
  [48838.267550] usb 1-10: USB disconnect, device number 8
  [48838.282968] usb 2-1: device not accepting address 8, error -62
  [48838.282983] usb 2-1: USB disconnect, device number 8
  [48838.282986] usb 2-1.2: USB disconnect, device number 9

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.18.0-9-generic 3.18.0-9.10
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  4255 F pulseaudio
   /dev/snd/controlC0:  chris  4255 F pulseaudio
  CRDA:
   country AU: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (3, 23), (N/A)
(5250 - 5330 @ 40), (3, 23), (0 ms), DFS
(5735 - 5835 @ 40), (3, 30), (N/A)
  CurrentDesktop: Unity
  Date: Thu Jan 22 12:59:27 2015
  InstallationDate: Installed on 2013-08-06 (533 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System76, Inc. Galago UltraPro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic.efi.signed 
root=UUID=92c2fa03-f29c-4bcc-87ab-f0fe28c134f2 ro quiet splash vt.handoff=7 
init=/lib/systemd/systemd break=mount
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.141
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-08-06 (533 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

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

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

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

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/onza__3.13.0-117.164__2017-04-10_18-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/1680733

Title:
  linux: 3.13.0-117.164 -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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/onza__3.13.0-117.164__2017-04-10_17-02-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1680733] pepe (i386) - tests ran: 3, failed: 0

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/pepe__3.13.0-117.164__2017-04-10_17-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/1680733

Title:
  linux: 3.13.0-117.164 -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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1681517] [NEW] /usr/lib/bluetooth/bluetoothd:11:avdtp_open:endpoint_open_cb:endpoint_reply:complete_pending_call_and_unlock:dbus_connection_dispatch

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.41-0ubuntu3, 
the problem page at 
https://errors.ubuntu.com/problem/8a866d2144eff926b451cc11c9018d9c402eceda 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: wily xenial yakkety

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

Title:
  
/usr/lib/bluetooth/bluetoothd:11:avdtp_open:endpoint_open_cb:endpoint_reply:complete_pending_call_and_unlock:dbus_connection_dispatch

Status in bluez package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.41-0ubuntu3, 
the problem page at 
https://errors.ubuntu.com/problem/8a866d2144eff926b451cc11c9018d9c402eceda 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

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

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/ms10-34-mcdivittB0-kernel__3.13.0-117.164__2017-04-10_16-28-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/ms10-35-mcdivittB0-kernel__3.13.0-117.164__2017-04-10_16-28-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1680888] Re: Disable CONFIG_HVC_UDBG on ppc64el

[Seth Forshee]

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

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
   Status: New

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

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

** Changed in: linux (Ubuntu Zesty)
 Assignee: Taco Screen team (taco-screen-team) => 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/1680888

Title:
  Disable CONFIG_HVC_UDBG on ppc64el

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

Bug description:
  Canonical,

  Could you please disable CONFIG_HVC_UDBG on ppc64el config?

  This is not required, and it is causing some extra timing on the TTY
  device that is causing some racing condition that is still being
  debugged

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

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

[Kernel-packages] [Bug 1680733] pepe (amd64) - tests ran: 33, failed: 6

[Brad Figg]

tests ran:  33, failed: 6;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/pepe__3.13.0-117.164__2017-04-10_16-34-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference

[Greg Lutostanski]

Unable to reproduce unfortunately. In fact it has not reoccurred, since
I filed this bug. Will reopen if it happens again, but I am moving to
the more recent released kernel... 4.10.0-15 -> 4.10.0-19.

Not sure what status to mark this bug as until I can get a repro of it.

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

Title:
  zesty unable to handle kernel NULL pointer dereference

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to zesty about a week ago. Ran into this on latest kernel.
  (during high load, nothing in particular seems to cause it to happen).

  Did not happen with previous (4.10.0.14.16) kernel. Only after update
  to 4.10.0.15.17, has happened about 3 times since then (or other
  crashes), this is the one I could capture.

  kern.log entries below. Let me know if you need anything else from me.

  Thanks!

  
  Apr  7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL 
pointer dereference at 0018
  Apr  7 11:20:28 doe kernel: [26003.796375] IP: 
gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.796404] PGD 0
  Apr  7 11:20:28 doe kernel: [26003.796405]
  Apr  7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP
  Apr  7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT 
nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep 
zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 
hid_multitouch joydev i2c_designware_platform i2c_designware_core 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp 
snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core asus_nb_wmi
  Apr  7 11:20:28 doe kernel: [26003.796722]  snd_hwdep asus_wmi sparse_keymap 
snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp 
uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops 
irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 
videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm 
elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf 
industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad 
int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi 
acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb 
int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless 
parport_pc ppdev lp parport ip_tables
  Apr  7 11:20:28 doe kernel: [26003.797026]  x_tables autofs4 algif_skcipher 
af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm 
wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
  Apr  7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: 
chromium-browse Tainted: P   O4.10.0-15-generic #17-Ubuntu
  Apr  7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER 
INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015
  Apr  7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: 
c25b5ea8c000
  Apr  7 11:20:28 doe kernel: [26003.797250] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 
00010246
  Apr  7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 
0003 RCX: 0003
  Apr  7 11:20:28 doe kernel: [26003.797325] RDX:  RSI: 
9bbae7c0a000 RDI: 9bbba0418000
  Apr  7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: 
 R09: 
  Apr  7 11:20:28 doe kernel: [26003.797378] R10:  R11: 
0041 R12: 9bbb5f00a000
  Apr  7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: 
fff97000 R15: 8000
  Apr  7 11:20:28 doe kernel: [26003.797440] FS:  7f70bd1df6c0() 
GS:93c0() knlGS:
  Apr  7 11:20:28 doe kernel: [26003.797470] CS:  0010 DS:  ES:  CR0: 
80050033
  Apr  7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 
00016942 CR4: 003406f0
  Apr  7 11:20:28 doe kernel: [26003.797523] Call Trace:
  Apr  7 

[Kernel-packages] [Bug 1681313] Re: "port does not support device sleep" on Dell Precision 5520

[TomaszChmielewski]

I think it was happening from the very beginning.


I'm still seeing this with ppa kernel 4.11.0-041100rc6-generic #201704091331:

[ 1889.428907] ata2.00: exception Emask 0x10 SAct 0x3c00 SErr 0x405 action 
0xe frozen
[ 1889.428915] ata2.00: irq_stat 0x0040, connection status changed
[ 1889.428921] ata2: SError: { PHYRdyChg CommWake DevExch }
[ 1889.428926] ata2.00: failed command: WRITE FPDMA QUEUED
[ 1889.428936] ata2.00: cmd 61/e8:50:d8:e9:0c/01:00:12:00:00/40 tag 10 ncq dma 
249856 out
res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA 
bus error)
[ 1889.428941] ata2.00: status: { DRDY }
[ 1889.428945] ata2.00: failed command: WRITE FPDMA QUEUED
[ 1889.428954] ata2.00: cmd 61/08:58:40:a8:6f/00:00:00:00:00/40 tag 11 ncq dma 
4096 out
res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA 
bus error)
[ 1889.428958] ata2.00: status: { DRDY }
[ 1889.428962] ata2.00: failed command: WRITE FPDMA QUEUED
[ 1889.428970] ata2.00: cmd 61/08:60:08:a8:6f/00:00:0e:00:00/40 tag 12 ncq dma 
4096 out
res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA 
bus error)
[ 1889.428973] ata2.00: status: { DRDY }
[ 1889.428977] ata2.00: failed command: WRITE FPDMA QUEUED
[ 1889.428984] ata2.00: cmd 61/08:68:c0:f2:93/00:00:11:00:00/40 tag 13 ncq dma 
4096 out
res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA 
bus error)
[ 1889.428988] ata2.00: status: { DRDY }
[ 1889.428995] ata2: hard resetting link
[ 1890.148893] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1890.151697] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 1890.151703] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
[ 1890.151707] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
[ 1890.151829] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device 
(Stat=0x51 Err=0x04)
[ 1890.158322] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 1890.158326] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
[ 1890.158328] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
[ 1890.158488] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device 
(Stat=0x51 Err=0x04)
[ 1890.160149] ata2.00: configured for UDMA/133
[ 1890.160162] ahci :00:17.0: port does not support device sleep
[ 1890.160237] ata2: EH complete

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

Title:
  "port does not support device sleep" on Dell Precision 5520

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm seeing messages like below on Dell Precision 5520, which is on an
  Ubuntu certified hardware list:

  https://certification.ubuntu.com/hardware/201610-25144/

  BIOS is updated to the latest version available: 1.1.3

  The system has this SATA controller:

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA
  controller [AHCI mode] (rev 31)

  And this 256 GB SSD disk:

  Model Number:   SanDisk X400 2.5 7MM 256GB
  Firmware Revision:  X4130012

  There is a firmware upgrade available for SSD storage on Dell website,
  but unfortunately, the installer is Windows only (a weird thing for a
  Ubuntu certified hardware IMO) - therefore, I was no able to apply it.

  dmesg entries which show up follow below:

  [35713.825698] ata2.00: exception Emask 0x10 SAct 0x4 SErr 0x405 action 
0xe frozen
  [35713.825701] ata2.00: irq_stat 0x0040, connection status changed
  [35713.825703] ata2: SError: { PHYRdyChg CommWake DevExch }
  [35713.825704] ata2.00: failed command: WRITE FPDMA QUEUED
  [35713.825707] ata2.00: cmd 61/18:10:e0:8d:0a/00:00:12:00:00/40 tag 2 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [35713.825709] ata2.00: status: { DRDY }
  [35713.825711] ata2: hard resetting link
  [35714.549641] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [35714.550813] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.550816] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.550818] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.550975] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.553832] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.553835] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.553837] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.553886] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.555383] ata2.00: configured for UDMA/133
  [35714.555399] ahci 

[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath
  root device

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory associated with per-CPU stuff is less in total).

  Per the bug description, the memory reserved for the crashkernel is
  512MB:

  (In reply to comment #23)
  > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to
  > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg

  That seems low for Power guests/systems. 
  I think it theory is doesn't seem so, but the reality is that _for some 
reason(s)_ we require just too much memory to load and boot a kernel/initramfs 
(either on boot or kdump).

  When working w/ kdump and Ubuntu, I usually set the crashkernel
  allocated size right away to 4GB to avoid problems.

  Since this is a smaller sized guest, obviously we'd want to use less
  than that, but more than 512 MB given the evidence observed.

  Hope this helps

  == Comment: 

[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device

[Mauro S M Rodrigues]

Hi Canonical,
Is there any news related to this bug and the patch attached? Is it already 
accepted?

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath
  root device

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory associated with per-CPU stuff is less in total).

  Per the bug description, the memory reserved for the crashkernel is
  512MB:

  (In reply to comment #23)
  > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to
  > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg

  That seems low for Power guests/systems. 
  I think it theory is doesn't seem so, but the reality is that _for some 
reason(s)_ we require just too much memory to load and boot a kernel/initramfs 
(either on boot or kdump).

  When working w/ kdump and Ubuntu, I usually set the crashkernel
  allocated size right away to 4GB to avoid problems.

  Since this is a smaller sized guest, obviously we'd want to use less
  than that, but more than 512 MB given the evidence observed.

  Hope this helps

  == Comment: #28 - Mauro Sergio Martins Rodrigues - 

[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath root device

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: kexec-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system on multipath
  root device

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in makedumpfile package in Ubuntu:
  Confirmed

Bug description:
  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel fails 
to mount the root file system.  This error does not occur in a similar guest 
installed to a single path device.
   
  Full console output of the kdump failure is attached.  These messages from 
the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.
   
  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest 
   
   
  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  > 
  > Could you please recreate the guest for further debug? 

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  > KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see
  > http://pastebin.hursley.ibm.com/8239
  > 
  > I'm still investigating to figure out what is the reason behind this
  > behavior.
  > 
  > Thanks,
  > 
  > --
  > maurosr

  That would smell like an out of memory condition that is alleviated
  with a smaller number of CPUs allowed for the kernel (so the amount of
  memory associated with per-CPU stuff is less in total).

  Per the bug description, the memory reserved for the crashkernel is
  512MB:

  (In reply to comment #23)
  > - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to
  > load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg

  That seems low for Power guests/systems. 
  I think it theory is doesn't seem so, but the reality is that _for some 
reason(s)_ we require just too much memory to load and boot a kernel/initramfs 
(either on boot or kdump).

  When working w/ kdump and Ubuntu, I usually set the crashkernel
  allocated size right away to 4GB to avoid problems.

  Since this is a smaller sized guest, obviously we'd want to use less
  than that, but more than 512 MB given the evidence observed.

  Hope this helps

  == Comment: #28 

[Kernel-packages] [Bug 1680733] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 14, failed: 2

[Brad Figg]

tests ran:  14, failed: 2;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/ms10-35-mcdivittB0-kernel__3.13.0-117.164__2017-04-10_15-50-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran:  14, failed: 2;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/ms10-34-mcdivittB0-kernel__3.13.0-117.164__2017-04-10_15-49-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1680735
  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/1680733/+subscriptions

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

Re: [Kernel-packages] [Bug 1681429] [NEW] POWER9: Improve performance on memory management

[Michael Hohnbaum]

Leann,

Please add to the Kernel Team's queue.

 Michael


On 04/10/2017 05:59 AM, Launchpad Bug Tracker wrote:
> bugproxy (bugproxy) has assigned this bug to you for Ubuntu:
>
> Please include this two patches for POWER9. They are performance patches
> and can improve up to 10x some workloads. These patches are limited to
> arch/powerpc only:
>
> https://patchwork.ozlabs.org/patch/746016/
> https://patchwork.ozlabs.org/patch/746020/
>
> ** Affects: ubuntu
>  Importance: Undecided
>  Assignee: Taco Screen team (taco-screen-team)
>  Status: New
>
>
> ** Tags: architecture-ppc64le bugnameltc-153287 severity-high 
> targetmilestone-inin1704

-- 
Michael Hohnbaum
OIL Program Manager
Power (ppc64el) Development Project Manager
Canonical, Ltd.

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

Title:
  POWER9: Improve performance on memory management

Status in linux package in Ubuntu:
  New

Bug description:
  Please include this two patches for POWER9. They are performance
  patches and can improve up to 10x some workloads. These patches are
  limited to arch/powerpc only:

  https://patchwork.ozlabs.org/patch/746016/
  https://patchwork.ozlabs.org/patch/746020/

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

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

Re: [Kernel-packages] [Bug 1681469] [NEW] Potential memory corruption with capi adapters

[Michael Hohnbaum]

Leann,

Critical bug to add to the Kernel Team's queue.

   Michael


On 04/10/2017 07:49 AM, Launchpad Bug Tracker wrote:
> bugproxy (bugproxy) has assigned this bug to you for Ubuntu:
>
> == Comment: #0 - Frederic Barrat  -
> 2017-04-10 04:44:01 ==
>
> ---Problem Description---
> Memory corruption can be seen when using a capi adapter. It can happen if the 
> host process allocates/frees/reallocates memory areas used by the the capi 
> adapter.
> Some TLB invalidations may not be propagated to the capi adapter, causing the 
> corruption.
>  
> Contact Information = frederic.bar...@fr.ibm.com 
>  
> ---uname output---
> Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
> ppc64le ppc64le ppc64le GNU/Linux
>  
> ---Additional Hardware Info---
> capi card needed, with the AFU image used by libdonut development  
>
>  
> Machine Type = Tuleta 
>  
> ---Debugger---
> A debugger is not configured
>  
> ---Steps to Reproduce---
>  Run libdonut in a loop, until corruption is seen. Host process will dump core
>  
>  
> Stack trace output:
>  no
>  
> Oops output:
>  no
>  
> System Dump Info:
>   The system is not configured to capture a system dump.
>  
> *Additional Instructions for frederic.bar...@fr.ibm.com: 
> -Attach sysctl -a output output to the bug.
>
> == Comment: #1 - Frederic Barrat  - 2017-04-10 
> 04:45:19 ==
> Fix is already upstream:
>
> commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
> Author: Frederic Barrat 
> Date:   Wed Mar 29 19:19:42 2017 +0200
>
> powerpc/mm: Add missing global TLB invalidate if cxl is active
>
>
> Could it be backported to the 16.04 LTS release, as well as 17.04?
> Thanks
>
> ** Affects: ubuntu
>  Importance: Undecided
>  Assignee: Taco Screen team (taco-screen-team)
>  Status: New
>
>
> ** Tags: architecture-ppc64le bugnameltc-153279 severity-high 
> targetmilestone-inin16045

-- 
Michael Hohnbaum
OIL Program Manager
Power (ppc64el) Development Project Manager
Canonical, Ltd.

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

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

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

-- 
Mailing list: https://launchpad.net/~kernel-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!

[Manoj Iyer]

** Description changed:

  [IMPACT]
- On QDF2400 ARM64 servers, booting Zesty 4.10 kernel causes soft lockups on 
multiple CPUs. 
+ On QDF2400 ARM64 servers, booting Zesty 4.10 kernel 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+bandera.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 
+ [  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.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.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] [] 

[Kernel-packages] [Bug 1680733] Re: linux: 3.13.0-117.164 -proposed tracker

[Steve Beattie]

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 3.13.0-117.164 -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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1391476] Re: [MacBookPro11, 1] Laptop wakes up while lid closed

[Erlenmayr]

In Ubuntu 17.04, this stopped happening.

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

Title:
  [MacBookPro11,1] Laptop wakes up while lid closed

Status in linux package in Ubuntu:
  Confirmed
Status in Debian:
  New

Bug description:
  Same behavior when using pm-suspend. It is hard to notice whether the
  laptop wakes up, especially because that does not always happen
  immediately. Getting to sleep takes up to 30 seconds. Hardware damage
  may be a result of waking up while lid is closed, for example if
  laptop is transported in a bag. I suspect that the problem comes from
  the Intel video driver. See extract from kern.log.

  WORKAROUND: Disable XHC1 in /proc/acpi/wakeup.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stephan2266 F pulseaudio
   /dev/snd/controlC1:  stephan2266 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Tue Nov 11 12:11:02 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-08 (33 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0259 Apple, Inc.
   Bus 001 Device 006: ID 05ac:8289 Apple, Inc.
   Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago)
  WifiSyslog:

  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B07.1402121134
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  ---
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   stephan2266 F...m pulseaudio
   /dev/snd/controlC0:  stephan2266 F pulseaudio
   /dev/snd/controlC1:  stephan2266 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-08 (34 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=d3ef8cca-2c30-46c5-88cc-a5f523abf8ac ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Tags:  utopic
  Uname: Linux 3.16.0-24-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago)
  UserGroups: sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP111.88Z.0138.B07.1402121134
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.name: MacBookPro11,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages

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

[Brad Figg]

tests ran:   4, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/ms10-34-mcdivittB0-kernel__3.13.0-117.164__2017-04-10_15-29-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/1680733

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran:   4, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/ms10-35-mcdivittB0-kernel__3.13.0-117.164__2017-04-10_15-29-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/1680733

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/ms10-35-mcdivittB0-kernel__3.13.0-117.164__2017-04-10_14-45-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran:   3, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/ms10-34-mcdivittB0-kernel__3.13.0-117.164__2017-04-10_14-45-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1680733
+ kernel-stable-phase-changed:Monday, 10. April 2017 15:03 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1680733
- kernel-stable-phase-changed:Monday, 10. April 2017 15:03 UTC
- kernel-stable-phase:Packaging
+ phase: Packaging

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1680733
  phase: Packaging

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

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

[Kernel-packages] [Bug 1681469] Re: Potential memory corruption with capi adapters

[bugproxy]

** Tags removed: severity-high
** Tags added: severity-critical

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

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

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

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

[Kernel-packages] [Bug 1681469] [NEW] Potential memory corruption with capi adapters

[bugproxy]

Public bug reported:

== Comment: #0 - Frederic Barrat  -
2017-04-10 04:44:01 ==

---Problem Description---
Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
 
Contact Information = frederic.bar...@fr.ibm.com 
 
---uname output---
Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
 
---Additional Hardware Info---
capi card needed, with the AFU image used by libdonut development  

 
Machine Type = Tuleta 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 Run libdonut in a loop, until corruption is seen. Host process will dump core
 
 
Stack trace output:
 no
 
Oops output:
 no
 
System Dump Info:
  The system is not configured to capture a system dump.
 
*Additional Instructions for frederic.bar...@fr.ibm.com: 
-Attach sysctl -a output output to the bug.

== Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
Fix is already upstream:

commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
Author: Frederic Barrat 
Date:   Wed Mar 29 19:19:42 2017 +0200

powerpc/mm: Add missing global TLB invalidate if cxl is active


Could it be backported to the 16.04 LTS release, as well as 17.04?
Thanks

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-153279 severity-high 
targetmilestone-inin16045

** Tags added: architecture-ppc64le bugnameltc-153279 severity-high
targetmilestone-inin16045

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

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

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[kulwinder singh]

Anybody having successfully tested 4.4.0.63 for OOM-kill issue...

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

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

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

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 1680733] gonzo (i386) - tests ran: 141, failed: 0

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/gonzo__3.13.0-117.164__2017-04-10_13-52-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1681469] [NEW] Potential memory corruption with capi adapters

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Frederic Barrat  -
2017-04-10 04:44:01 ==

---Problem Description---
Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
 
Contact Information = frederic.bar...@fr.ibm.com 
 
---uname output---
Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
 
---Additional Hardware Info---
capi card needed, with the AFU image used by libdonut development  

 
Machine Type = Tuleta 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 Run libdonut in a loop, until corruption is seen. Host process will dump core
 
 
Stack trace output:
 no
 
Oops output:
 no
 
System Dump Info:
  The system is not configured to capture a system dump.
 
*Additional Instructions for frederic.bar...@fr.ibm.com: 
-Attach sysctl -a output output to the bug.

== Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
Fix is already upstream:

commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
Author: Frederic Barrat 
Date:   Wed Mar 29 19:19:42 2017 +0200

powerpc/mm: Add missing global TLB invalidate if cxl is active


Could it be backported to the 16.04 LTS release, as well as 17.04?
Thanks

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-153279 severity-high 
targetmilestone-inin16045
-- 
Potential memory corruption with capi adapters
https://bugs.launchpad.net/bugs/1681469
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

[Stefan Bader]

** Summary changed:

- linux-lts-trusty:  -proposed tracker
+ linux-lts-trusty: 3.13.0-117.164~precise1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
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 --
  kernel-stable-master-bug: 1680733

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

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

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

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/fozzie__3.13.0-117.164__2017-04-10_13-09-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran: 141, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/gonzo__3.13.0-117.164__2017-04-10_12-45-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1681429] Re: POWER9: Improve performance on memory management

[Breno Leitão]

Send to the mailing list:

https://lists.ubuntu.com/archives/kernel-team/2017-April/083554.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/1681429

Title:
  POWER9: Improve performance on memory management

Status in linux package in Ubuntu:
  New

Bug description:
  Please include this two patches for POWER9. They are performance
  patches and can improve up to 10x some workloads. These patches are
  limited to arch/powerpc only:

  https://patchwork.ozlabs.org/patch/746016/
  https://patchwork.ozlabs.org/patch/746020/

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

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

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-67 or later

[Joseph Salisbury]

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

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-67 or later

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command 

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-67 or later

[Dave]

** Changed in: linux (Ubuntu Xenial)
   Status: Fix Committed => 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/1679898

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-67 or later

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command 

[Kernel-packages] [Bug 1681183] Re: Ubuntu mainline git repo not updated for v4.10 kernels

[Andy Whitcroft]

That repository is a mirror of the actual repository used for builds so
it should be in there.  However, it seems the mirror processing is sick.
Will investigate.

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

Title:
  Ubuntu mainline git repo not updated for v4.10 kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey lovely Ubuntu maintainers!

  I've been compiling my own mainline kernels for a while now due to
  running with a few additional hardware specific patches for my system.
  I've been using the mainline kernel instructions from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/ .

  However starting with Kernel v4.10, the Ubuntu git repo doesn't seem
  to contain the needed branches for this to work any more. For example,
  trying to get v4.10.9 fails:

  $ git clone --branch v4.10.9 
git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack
  Cloning into 'mainline-crack'...
  fatal: Remote branch v4.10.9 not found in upstream origin

  but cloning anything from the v4.9.x series works fine:

  $ git clone --branch v4.9.10 
git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack
  Cloning into 'mainline-crack'...
  remote: Counting objects: ...

  The particular instructions for building v4.10.9 are at
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.9/ , and don't
  seem to be any different from any earlier releases, so I'm guessing
  that branches are not hitting the ubuntu mainline-crack repository at
  all.

  This may be the entirely wrong place to report this bug, in which case
  I would *love* your advice on where I should be fielding this.

  Many, many thanks!

  ~ Paul

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

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

[Kernel-packages] [Bug 1681434] Re: package linux-headers-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

[Joseph Salisbury]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

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

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

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

Title:
  package linux-headers-4.4.0-66-generic 4.4.0-66.87 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happens on boot up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tim2017 F pulseaudio
   /dev/snd/controlC0:  tim2017 F pulseaudio
  Date: Fri Apr  7 21:16:40 2017
  DpkgHistoryLog:
   Start-Date: 2017-04-07  21:16:11
   Commandline: /usr/bin/unattended-upgrade
   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-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.71.77, 4.4.0.72.78), 
linux-libc-dev:amd64 (4.4.0-71.92, 4.4.0-72.93), linux-image-generic:amd64 
(4.4.0.71.77, 4.4.0.72.78), linux-generic:amd64 (4.4.0.71.77, 4.4.0.72.78), 
lightdm:amd64 (1.18.3-0ubuntu1, 1.18.3-0ubuntu1.1), 
liblightdm-gobject-1-0:amd64 (1.18.3-0ubuntu1, 1.18.3-0ubuntu1.1)
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=13756ac8-2730-4c73-9a30-4ffbf49eccb8
  InstallationDate: Installed on 2016-10-08 (183 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   tun0  no wireless extensions.
   
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=0174b67e-8087-4a08-a594-a5166cecd313 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.7
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0908
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0908:bd11/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x: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/1681434/+subscriptions

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

[Kernel-packages] [Bug 1680276] Re: DRM for Via GPUs is missing

[Seth Forshee]

The changes to disable the modules happened in zesty. These are the ones
that are no longer enabled:

DRM_TDFX: 3dfx Banshee/Voodoo3+
DRM_R128: ATI Rage 128
DRM_I810: ATI Rage 128
DRM_MGA: Matrox g200/g400
DRM_SIS: SiS video cards
DRM_VIA: Via unichrome video cards
DRM_SAVAGE: Savage video cards

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

Title:
  DRM for Via GPUs is missing

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

Bug description:
  17.04 Beta 2 (Zesty Zapus) amd64

  Via PM800 chipset (S3 UniChrome Pro)

  Xorg.0.log:
  [25.194] (EE) CHROME(0): [drm] Failed to open DRM device for 
pci::01:00.0: No such file or directory
  …
  [25.469] (EE) AIGLX: reverting to software rendering

  ls /dev/dri/card0
  ls: cannot access '/dev/dri/card0': No such file or directory

  ls /lib/modules/4.10.0-15-generic/kernel/drivers/gpu/drm/via/via.ko
  ls: cannot access 
'/lib/modules/4.10.0-15-generic/kernel/drivers/gpu/drm/via/via.ko': No such 
file or directory

  No DRM so no acceleration with Openchrome.  This will make me and
  other Ubuntu 17.04 users with Via hardware sad (I'm guessing there's
  at least five of us).  Makes for an annoying Ubuntu experience when
  browsing the web at nearly slide-show speeds while trying to find the
  correct drivers for our Nvidia and AMD cards.

  https://cgit.freedesktop.org/openchrome/drm-openchrome/

  Not sure if it matters for the DRM module but Openchrome 0.6 has been
  released:  https://lists.freedesktop.org/archives/openchrome-
  devel/2017-March/003232.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-15-generic 4.10.0-15.17
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrator   1313 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr  5 19:02:03 2017
  HibernationDevice: RESUME=UUID=34091ce2-a8c1-4a9f-9003-e91bf39fc4ae
  InstallationDate: Installed on 2017-04-05 (0 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  IwConfig:
   enp0s18   no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VIA Technologies, Inc. PM800-8237
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-15-generic 
root=UUID=f8e980c3-f382-4ec2-82b1-0b7c00b69932 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-15-generic N/A
   linux-backports-modules-4.10.0-15-generic  N/A
   linux-firmware 1.164
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2005
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: PM800-8237
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/21/2005:svnVIATechnologies,Inc.:pnPM800-8237:pvr:rvn:rnPM800-8237:rvr:cvn:ct3:cvr:
  dmi.product.name: PM800-8237
  dmi.sys.vendor: VIA Technologies, Inc.

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

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

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

[bugproxy]

--- Comment From danie...@br.ibm.com 2017-04-10 09:03 EDT---
> Hi,
> thank you a lot Daniel to identify the potentially missing two patches.
> I wonder thou if we really need all 7 then, or maybe just the two new ones.
> While the extra 5 are valid fixes in general I'm not sure they are 100%
> needed as Xenial seems to be fine without and at least according to Mike he
> was good with 2.6.1 from Yakkety which does not have them.

The 5 patches from 2.7.0 are performance boosts/fixes. Given that the 8335-GTB
is a high performance system they are quite interesting to have. But they
are not need in a sense of QEMU does not work without them.  In fact, I've 
tested
2.5.0 with only the 2 patches from 2.6.1 and the sanity tests worked just fine.

> 2. I'd be happy on an IBM statement on the extra 5 patches from qemu 2.7 if
> they are really required especially since this is in the sense of an SRU I
> want to keep the scope minimal to the fix that is needed.

You don't need the 5 patches from 2.7.0 to make QEMU work in 8335-GTB.

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Confirmed
Status in qemu source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * Some newer Power8 derivates fail to work correctly e.g. Power S822LC 
(8335-GTB) 

   * This is a toleration change (no exploitation) for those HW releases 
 following the SRU policy of "For Long Term Support releases we 
 regularly want to enable new hardware. Such changes are appropriate 
 provided that we can ensure not to affect upgrades on existing 
 hardware."

   * Without the Fix that hardware won't run Xenial guests under current 
 Xenials Qemu version

   * The fix lets processors that support it run in PowerISA 2.07 
 compatibility mode (plus a few no-op changes as backport 
 dependencies)

  
  [Test Case]

   * Run a Xenial Guest in KVM on one of the specific HW revisions being 
 affected.

  [Regression Potential]

   * Changes are PPC only, so fallout should be contained to that
   * Patches were created by IBM and in Upstream qemu since 2.7
   * The effective change is rather small, only allow different compat 
 level on this other cpu class
   * There are a few refactoring changes needed to get the backport done, 
 while they should be a no-op that is a regression potential (still 
 limited to ppc64el)

  [Other Info]
   
   * Needed for certifying this Hardware for Ubuntu


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

  kvm_init_vcpu failed: Invalid argument

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

  The full output from the test is as follows:

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 22:18 seq
   crw-rw 1 root audio 116, 33 Jan 12 22:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: 

[Kernel-packages] [Bug 1681434] Re: package linux-headers-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

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

Title:
  package linux-headers-4.4.0-66-generic 4.4.0-66.87 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in linux package in Ubuntu:
  New

Bug description:
  Happens on boot up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tim2017 F pulseaudio
   /dev/snd/controlC0:  tim2017 F pulseaudio
  Date: Fri Apr  7 21:16:40 2017
  DpkgHistoryLog:
   Start-Date: 2017-04-07  21:16:11
   Commandline: /usr/bin/unattended-upgrade
   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-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.71.77, 4.4.0.72.78), 
linux-libc-dev:amd64 (4.4.0-71.92, 4.4.0-72.93), linux-image-generic:amd64 
(4.4.0.71.77, 4.4.0.72.78), linux-generic:amd64 (4.4.0.71.77, 4.4.0.72.78), 
lightdm:amd64 (1.18.3-0ubuntu1, 1.18.3-0ubuntu1.1), 
liblightdm-gobject-1-0:amd64 (1.18.3-0ubuntu1, 1.18.3-0ubuntu1.1)
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: RESUME=UUID=13756ac8-2730-4c73-9a30-4ffbf49eccb8
  InstallationDate: Installed on 2016-10-08 (183 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   tun0  no wireless extensions.
   
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=0174b67e-8087-4a08-a594-a5166cecd313 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.7
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0908
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0908:bd11/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x: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/1681434/+subscriptions

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

[Kernel-packages] [Bug 1681434] [NEW] package linux-headers-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt

[Tim]

Public bug reported:

Happens on boot up

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-headers-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
Uname: Linux 4.4.0-71-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  tim2017 F pulseaudio
 /dev/snd/controlC0:  tim2017 F pulseaudio
Date: Fri Apr  7 21:16:40 2017
DpkgHistoryLog:
 Start-Date: 2017-04-07  21:16:11
 Commandline: /usr/bin/unattended-upgrade
 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-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.71.77, 4.4.0.72.78), 
linux-libc-dev:amd64 (4.4.0-71.92, 4.4.0-72.93), linux-image-generic:amd64 
(4.4.0.71.77, 4.4.0.72.78), linux-generic:amd64 (4.4.0.71.77, 4.4.0.72.78), 
lightdm:amd64 (1.18.3-0ubuntu1, 1.18.3-0ubuntu1.1), 
liblightdm-gobject-1-0:amd64 (1.18.3-0ubuntu1, 1.18.3-0ubuntu1.1)
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
HibernationDevice: RESUME=UUID=13756ac8-2730-4c73-9a30-4ffbf49eccb8
InstallationDate: Installed on 2016-10-08 (183 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
 tun0  no wireless extensions.
 
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=0174b67e-8087-4a08-a594-a5166cecd313 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.7
RfKill:
 
SourcePackage: linux
Title: package linux-headers-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0908
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V LK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0908:bd11/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


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

Title:
  package linux-headers-4.4.0-66-generic 4.4.0-66.87 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in linux package in Ubuntu:
  New

Bug description:
  Happens on boot up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tim2017 F pulseaudio
   /dev/snd/controlC0:  tim2017 F pulseaudio
  Date: Fri Apr  7 21:16:40 2017
  DpkgHistoryLog:
   Start-Date: 2017-04-07  21:16:11
   Commandline: /usr/bin/unattended-upgrade
   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-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.71.77, 4.4.0.72.78), 
linux-libc-dev:amd64 (4.4.0-71.92, 4.4.0-72.93), linux-image-generic:amd64 
(4.4.0.71.77, 4.4.0.72.78), linux-generic:amd64 (4.4.0.71.77, 4.4.0.72.78), 
lightdm:amd64 (1.18.3-0ubuntu1, 1.18.3-0ubuntu1.1), 
liblightdm-gobject-1-0:amd64 (1.18.3-0ubuntu1, 1.18.3-0ubuntu1.1)
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  HibernationDevice: 

[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference

[Joseph Salisbury]

Do you have a way to reproduce this bug?

If so, would it be possible for you to test the latest upstream kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.11 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.11-rc6

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

Title:
  zesty unable to handle kernel NULL pointer dereference

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to zesty about a week ago. Ran into this on latest kernel.
  (during high load, nothing in particular seems to cause it to happen).

  Did not happen with previous (4.10.0.14.16) kernel. Only after update
  to 4.10.0.15.17, has happened about 3 times since then (or other
  crashes), this is the one I could capture.

  kern.log entries below. Let me know if you need anything else from me.

  Thanks!

  
  Apr  7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL 
pointer dereference at 0018
  Apr  7 11:20:28 doe kernel: [26003.796375] IP: 
gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.796404] PGD 0
  Apr  7 11:20:28 doe kernel: [26003.796405]
  Apr  7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP
  Apr  7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT 
nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack 
libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep 
zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 
hid_multitouch joydev i2c_designware_platform i2c_designware_core 
snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp 
snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic 
snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel 
snd_hda_codec snd_hda_core asus_nb_wmi
  Apr  7 11:20:28 doe kernel: [26003.796722]  snd_hwdep asus_wmi sparse_keymap 
snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 
iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp 
uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops 
irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 
videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm 
elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf 
industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad 
int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi 
acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb 
int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless 
parport_pc ppdev lp parport ip_tables
  Apr  7 11:20:28 doe kernel: [26003.797026]  x_tables autofs4 algif_skcipher 
af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm 
wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes
  Apr  7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: 
chromium-browse Tainted: P   O4.10.0-15-generic #17-Ubuntu
  Apr  7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER 
INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015
  Apr  7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: 
c25b5ea8c000
  Apr  7 11:20:28 doe kernel: [26003.797250] RIP: 
0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
  Apr  7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 
00010246
  Apr  7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 
0003 RCX: 0003
  Apr  7 11:20:28 doe kernel: [26003.797325] RDX:  RSI: 
9bbae7c0a000 RDI: 9bbba0418000
  Apr  7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: 
 R09: 
  Apr  7 11:20:28 doe kernel: [26003.797378] R10:  R11: 
0041 R12: 9bbb5f00a000
  Apr  7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: 
fff97000 R15: 8000
  Apr  7 11:20:28 doe kernel: [26003.797440] FS:  7f70bd1df6c0() 
GS:93c0() 

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-67 or later

[Dave]

In what version of the kernel can we expect the fix?

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-67 or later

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit 

[Kernel-packages] [Bug 1680973] Re: Suspend does not work when booting with 'nomodeset' option

[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.11 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.11-rc6


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

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

Title:
  Suspend does not work when booting with 'nomodeset' option

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 16.04.2 with kernel version 4.10.8 on an original
  MacBook Air. No matter how I try to suspend, the screen stays black
  when I try to wake my computer again. I know that it is on because I
  hear sounds if I tap the volume buttons and I am able to connect over
  ssh, but the screen stays black.

  I have tried switching TTYs et.c. but the screen stays black. The
  Apple logo on the lid isn't lit either. I don't know if this is a bug
  or just lack of support but I find it really sad because my computer
  gets way faster when I boot with the 'nomodeset' option.

  Another problem I have with 'nomodeset' is that I am unable to control
  screen brightness. I don't know if this is related or not, but I guess
  it is.

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

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

[Kernel-packages] [Bug 1681429] [NEW] POWER9: Improve performance on memory management

[bugproxy]

Public bug reported:

Please include this two patches for POWER9. They are performance patches
and can improve up to 10x some workloads. These patches are limited to
arch/powerpc only:

https://patchwork.ozlabs.org/patch/746016/
https://patchwork.ozlabs.org/patch/746020/

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-153287 severity-high 
targetmilestone-inin1704

** Tags added: architecture-ppc64le bugnameltc-153287 severity-high
targetmilestone-inin1704

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

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

Title:
  POWER9: Improve performance on memory management

Status in linux package in Ubuntu:
  New

Bug description:
  Please include this two patches for POWER9. They are performance
  patches and can improve up to 10x some workloads. These patches are
  limited to arch/powerpc only:

  https://patchwork.ozlabs.org/patch/746016/
  https://patchwork.ozlabs.org/patch/746020/

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

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

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

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/fozzie__3.13.0-117.164__2017-04-10_12-03-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1681150] Re: Has anyone noticed zesty linux-image-generic_4.10.0.19.21_amd64 has no initrd.img AND can't see Root=UUID= AND read any partitions?

[Joseph Salisbury]

So your system will boot if you select 4.10.0-13 from the GRUB menu but
not any kernel version newer than -14?

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

** Tags added: kernel-da-key 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/1681150

Title:
  Has anyone noticed zesty linux-image-generic_4.10.0.19.21_amd64 has no
  initrd.img AND can't see Root=UUID= AND read any partitions?

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm running Zesty 17.04 linux-image.4.10.0.13
  I can log in but compiz has to be --replaced.

  Then I update-grub. kernel .14 downloads yesterday
  and .19 today. Both don't have a initrd.img-4.10.0-1[49]-generic.

  Most would stop here. 
  In grub.cfg I tried adding a initrd /initrd.img with is linked
  to /boot/initrd.img-4.10.0-13-generic to both
  linux vmlinuz-4.10.0-14-generic and linux vmlinuz-4.10.0-19-generic

  What does it mean when it boots until a kernel panic "can't find root."
  This also happens if there is no initrd line (as intended.)

  ubuntu-bug linux reports "not a real package. please remove third party packs"
  $cat /proc/version_signature |tee version.log
  Ubuntu 4.10.0-13.15-generic 4.10.1
  #install new crash kernels:   zesty 
  echo deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates  \
  main restricted universe multiverse > /etc/apt/sources.list.d/ddebs.list
  $ sudo apt-get install linux-image-$(uname -r)-dbgsym
  E: Unable to locate package linux-image-4.10.0-13-generic-dbgsym
  E: Unable to locate package linux-image-4.10.0-14-generic-dbgsym
  E: Unable to locate package linux-image-4.10.0-19-generic-dbgsym

  oh well. I'm learning so much.

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

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

[Kernel-packages] [Bug 1681429] [NEW] POWER9: Improve performance on memory management

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Please include this two patches for POWER9. They are performance patches
and can improve up to 10x some workloads. These patches are limited to
arch/powerpc only:

https://patchwork.ozlabs.org/patch/746016/
https://patchwork.ozlabs.org/patch/746020/

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-153287 severity-high 
targetmilestone-inin1704
-- 
POWER9: Improve performance on memory management
https://bugs.launchpad.net/bugs/1681429
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1681183] Re: Ubuntu mainline git repo not updated for v4.10 kernels

[Joseph Salisbury]

** Tags added: kernel-da-key

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

Title:
  Ubuntu mainline git repo not updated for v4.10 kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey lovely Ubuntu maintainers!

  I've been compiling my own mainline kernels for a while now due to
  running with a few additional hardware specific patches for my system.
  I've been using the mainline kernel instructions from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/ .

  However starting with Kernel v4.10, the Ubuntu git repo doesn't seem
  to contain the needed branches for this to work any more. For example,
  trying to get v4.10.9 fails:

  $ git clone --branch v4.10.9 
git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack
  Cloning into 'mainline-crack'...
  fatal: Remote branch v4.10.9 not found in upstream origin

  but cloning anything from the v4.9.x series works fine:

  $ git clone --branch v4.9.10 
git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack
  Cloning into 'mainline-crack'...
  remote: Counting objects: ...

  The particular instructions for building v4.10.9 are at
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.9/ , and don't
  seem to be any different from any earlier releases, so I'm guessing
  that branches are not hitting the ubuntu mainline-crack repository at
  all.

  This may be the entirely wrong place to report this bug, in which case
  I would *love* your advice on where I should be fielding this.

  Many, many thanks!

  ~ Paul

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

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

[Kernel-packages] [Bug 1680416] Re: linux: 4.4.0-73.94 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   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/1680416

Title:
  linux: 4.4.0-73.94 -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:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  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/1680416/+subscriptions

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

[Kernel-packages] [Bug 1679678] Re: linux: 4.8.0-47.50 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   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/1679678

Title:
  linux: 4.8.0-47.50 -proposed tracker

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

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

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

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/gonzo__3.13.0-117.164__2017-04-10_12-23-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1681183] Re: Ubuntu mainline git repo not updated for v4.10 kernels

[Joseph Salisbury]

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

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

Title:
  Ubuntu mainline git repo not updated for v4.10 kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey lovely Ubuntu maintainers!

  I've been compiling my own mainline kernels for a while now due to
  running with a few additional hardware specific patches for my system.
  I've been using the mainline kernel instructions from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/ .

  However starting with Kernel v4.10, the Ubuntu git repo doesn't seem
  to contain the needed branches for this to work any more. For example,
  trying to get v4.10.9 fails:

  $ git clone --branch v4.10.9 
git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack
  Cloning into 'mainline-crack'...
  fatal: Remote branch v4.10.9 not found in upstream origin

  but cloning anything from the v4.9.x series works fine:

  $ git clone --branch v4.9.10 
git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack
  Cloning into 'mainline-crack'...
  remote: Counting objects: ...

  The particular instructions for building v4.10.9 are at
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.9/ , and don't
  seem to be any different from any earlier releases, so I'm guessing
  that branches are not hitting the ubuntu mainline-crack repository at
  all.

  This may be the entirely wrong place to report this bug, in which case
  I would *love* your advice on where I should be fielding this.

  Many, many thanks!

  ~ Paul

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

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

[Kernel-packages] [Bug 1681313] Re: "port does not support device sleep" on Dell Precision 5520

[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.11 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.11-rc6

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

Title:
  "port does not support device sleep" on Dell Precision 5520

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm seeing messages like below on Dell Precision 5520, which is on an
  Ubuntu certified hardware list:

  https://certification.ubuntu.com/hardware/201610-25144/

  BIOS is updated to the latest version available: 1.1.3

  The system has this SATA controller:

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA
  controller [AHCI mode] (rev 31)

  And this 256 GB SSD disk:

  Model Number:   SanDisk X400 2.5 7MM 256GB
  Firmware Revision:  X4130012

  There is a firmware upgrade available for SSD storage on Dell website,
  but unfortunately, the installer is Windows only (a weird thing for a
  Ubuntu certified hardware IMO) - therefore, I was no able to apply it.

  dmesg entries which show up follow below:

  [35713.825698] ata2.00: exception Emask 0x10 SAct 0x4 SErr 0x405 action 
0xe frozen
  [35713.825701] ata2.00: irq_stat 0x0040, connection status changed
  [35713.825703] ata2: SError: { PHYRdyChg CommWake DevExch }
  [35713.825704] ata2.00: failed command: WRITE FPDMA QUEUED
  [35713.825707] ata2.00: cmd 61/18:10:e0:8d:0a/00:00:12:00:00/40 tag 2 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [35713.825709] ata2.00: status: { DRDY }
  [35713.825711] ata2: hard resetting link
  [35714.549641] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [35714.550813] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.550816] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.550818] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.550975] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.553832] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.553835] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.553837] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.553886] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.555383] ata2.00: configured for UDMA/133
  [35714.555399] ahci :00:17.0: port does not support device sleep
  [35714.555493] ata2: EH complete
  [36324.490477] ata2.00: exception Emask 0x10 SAct 0x4000 SErr 0x405 
action 0xe frozen
  [36324.490480] ata2.00: irq_stat 0x0040, connection status changed
  [36324.490482] ata2: SError: { PHYRdyChg CommWake DevExch }
  [36324.490484] ata2.00: failed command: WRITE FPDMA QUEUED
  [36324.490487] ata2.00: cmd 61/18:f0:68:08:85/00:00:07:00:00/40 tag 30 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [36324.490488] ata2.00: status: { DRDY }
  [36324.490490] ata2: hard resetting link
  [36325.214543] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [36325.215658] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [36325.215660] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [36325.215662] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [36325.215731] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [36325.218240] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [36325.218242] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [36325.218243] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [36325.218293] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [36325.219965] ata2.00: configured for UDMA/133
  [36325.219982] ahci :00:17.0: port does not support device sleep
  [36325.220079] ata2: EH complete
  [38355.555685] ata2.00: exception Emask 0x10 SAct 

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

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/gonzo__3.13.0-117.164__2017-04-10_12-02-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard

[Ubiratan Pires Alberton]

s/"Complete"/"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/1678477

Title:
  Kernel has troule recognizing Corsair Strafe RGB keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently bought a Corsair Strafe RGB keyboard, and while it works
  well when successfully recognized by Ubuntu at boot, that doesn't
  always happen.

  I see messages like this when booting my desktop up:

  [6.619510] usb 3-10: unable to read config index 0 descriptor/all
  [6.619543] usb 3-10: can't read configurations, error -110

  They sometimes repeat at 5-second intervals, culminating on a "can't
  set config #1" message or even "unable to enumerate USB device". This
  happens on the logic that deals with a new USB device being connected,
  so when it doesn't work it never gets to the HID drivers part of the
  code. When it does, hid-generic is quite able to control the keyboard,
  though this message appears on dmesg:

  [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt
  endpoint

  
  From what I have been able to determine, the Corsair Strafe RGB has three 
inputs, with the last one being used as input/output and having something to do 
with the LEDs. It only has a single USB configuration, though I don't know why 
it times out.

  Searching on Google has a lot of people recommending this userspace
  drive to me: https://github.com/mattanger/ckb-next , and I've tried
  it, but it seems to be more about programming lighting effects into
  the keyboard than in controlling its basic operation, which is all I'm
  interested in. Its daemon was supposed to handle that part too, but it
  didn't fix those connection errors on boot.

  I have the following boot parameter set in my kernel, following advice
  from ckb-next's README, but it doesn't see to have an appreciable
  effect on my success rate:

  usbhid.quirks=0x1B1C:0x1B20:0x2448

  ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT
  as well in an attempt to improve things, without success.

  GRUB is always able to correctly identify the keyboard and get it to
  work, too, which makes the fact that the full kernel can't always do
  it a little more frustrating.

  I would be happy to provide any extra information you require on this
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-45-generic 4.8.0-45.48
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bira   2322 F pulseaudio
   /dev/snd/controlC0:  bira   2322 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Apr  1 10:23:52 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-24 (767 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic 
root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash 
usbhid.quirks=0x1B1C:0x1B20:0x2448
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-45-generic N/A
   linux-backports-modules-4.8.0-45-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-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.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97M-D3H
  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/1678477/+subscriptions

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

[Kernel-packages] [Bug 1678477] Re: Kernel has troule recognizing Corsair Strafe RGB keyboard

[Ubiratan Pires Alberton]

I tested it a few days ago but forgot to mark it as "Complete", sorry
about that. To further add information to my previous comment here, the
bug I described occurs both when the keyboard is plugged into a USB 3.0
port and when it's plugged into 2 USB 2.0 ports.

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

Title:
  Kernel has troule recognizing Corsair Strafe RGB keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently bought a Corsair Strafe RGB keyboard, and while it works
  well when successfully recognized by Ubuntu at boot, that doesn't
  always happen.

  I see messages like this when booting my desktop up:

  [6.619510] usb 3-10: unable to read config index 0 descriptor/all
  [6.619543] usb 3-10: can't read configurations, error -110

  They sometimes repeat at 5-second intervals, culminating on a "can't
  set config #1" message or even "unable to enumerate USB device". This
  happens on the logic that deals with a new USB device being connected,
  so when it doesn't work it never gets to the HID drivers part of the
  code. When it does, hid-generic is quite able to control the keyboard,
  though this message appears on dmesg:

  [6.883811] usbhid 3-10:1.2: couldn't find an input interrupt
  endpoint

  
  From what I have been able to determine, the Corsair Strafe RGB has three 
inputs, with the last one being used as input/output and having something to do 
with the LEDs. It only has a single USB configuration, though I don't know why 
it times out.

  Searching on Google has a lot of people recommending this userspace
  drive to me: https://github.com/mattanger/ckb-next , and I've tried
  it, but it seems to be more about programming lighting effects into
  the keyboard than in controlling its basic operation, which is all I'm
  interested in. Its daemon was supposed to handle that part too, but it
  didn't fix those connection errors on boot.

  I have the following boot parameter set in my kernel, following advice
  from ckb-next's README, but it doesn't see to have an appreciable
  effect on my success rate:

  usbhid.quirks=0x1B1C:0x1B20:0x2448

  ckb-next recommended 0x2408, but I added the HID_QUIRK_MULTI_INPUT
  as well in an attempt to improve things, without success.

  GRUB is always able to correctly identify the keyboard and get it to
  work, too, which makes the fact that the full kernel can't always do
  it a little more frustrating.

  I would be happy to provide any extra information you require on this
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-45-generic 4.8.0-45.48
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bira   2322 F pulseaudio
   /dev/snd/controlC0:  bira   2322 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Apr  1 10:23:52 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-24 (767 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97M-D3H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic 
root=UUID=d1db423d-2a50-49ac-b4e7-fd50d73afaff ro quiet splash 
usbhid.quirks=0x1B1C:0x1B20:0x2448
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-45-generic N/A
   linux-backports-modules-4.8.0-45-generic  N/A
   linux-firmware1.161.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97M-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.:bvrF5:bd05/30/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97M-D3H
  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/1678477/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

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

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/ms10-34-mcdivittB0-kernel__3.13.0-117.164__2017-04-10_11-44-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/fozzie__3.13.0-117.164__2017-04-10_11-45-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1680733] amaura (amd64) - tests ran: 33, failed: 5

[Brad Figg]

tests ran:  33, failed: 5;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/amaura__3.13.0-117.164__2017-04-10_11-29-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/1680733

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/ms10-35-mcdivittB0-kernel__3.13.0-117.164__2017-04-10_11-44-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/gonzo__3.13.0-117.164__2017-04-10_11-42-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1359803] Re: External mic not being used in combo port

[Vyacheslav]

Experiencing same problem on Debian Jessie on Lenovo G40-30. After
assigning pin 0x18 to microphone acpi_listen prints that microphone is
plugged in but pavucontrol still shows mic as unplugged. Also trying to
boost appeared after pin assignment microphone in alsamixer makes large
increasing noise so I think overriding that pin is not a part of
solution for me. Fabianbur's solution didn't work too.

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

Title:
  External mic not being used in combo port

Status in linux package in Ubuntu:
  In Progress

Bug description:
  I'm using Ubuntu 14.04 on my Asus 1015E that only has a combo audio
  port which accepts smartphone type "headsets" (3.5mm TRRS headphones
  with mic on the same wire).

  Ubuntu does not deactivate the built-in mic when I connect my headset.
  It doesn't even use the headset mic and instead keeps picking up audio
  signal from the integrated microphone (that's on my laptop bezel).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  power-inside   4651 F pulseaudio
  Date: Thu Aug 21 20:24:20 2014
  HibernationDevice: RESUME=UUID=d0a4bd33-50b7-419e-80da-efc7ad5b1247
  InstallationDate: Installed on 2013-11-08 (286 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUSTeK COMPUTER INC. 1015E
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=0323822b-7902-4f91-bf79-2a91c47d7df5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (124 days ago)
  dmi.bios.date: 03/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1015E.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 1015E
  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.:bvr1015E.303:bd03/15/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: 1015E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/ms10-34-mcdivittB0-kernel__3.13.0-117.164__2017-04-10_11-23-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/gonzo__3.13.0-117.164__2017-04-10_11-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/1680733

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/ms10-35-mcdivittB0-kernel__3.13.0-117.164__2017-04-10_11-24-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/fozzie__3.13.0-117.164__2017-04-10_11-24-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-117.164-generic/amaura__3.13.0-117.164__2017-04-10_11-15-00/results-index.html

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1680733] Re: linux: 3.13.0-117.164 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1680735
  derivatives:
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 07. April 2017 11:31 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Monday, 10. April 2017 11:03 UTC

** Description changed:

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

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

Title:
  linux: 3.13.0-117.164 -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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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: 1680735
  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/1680733/+subscriptions

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

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-67 or later

[Joseph Salisbury]

@Andrey, thanks for all the help testing.  The fix mentioned by Josh in
comment #19 and you testing in my v2 test kernel will be in the next
kernel release.

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

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

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-67 or later

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: 

[Kernel-packages] [Bug 1638860] Re: Ubuntu 16.10 can't boot properly with Nvidia GTX 1060

[Daniel van Vugt]

Confirmed, zesty (17.04) boots on GTX 1060 just fine now.

Looks almost perfect except that it's using software rendering. That's
expected though.

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

Title:
  Ubuntu 16.10 can't boot properly with Nvidia GTX 1060

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 16.10 can't boot properly with Nvidia GTX 1060. Xorg repeatedly
  tries and fails to start.

  I have to add kernel option 'nomodeset' to get a desktop. Then it's
  just using fbdev :(

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

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

[Kernel-packages] [Bug 1670634] Re: blk-mq: possible deadlock on CPU hot(un)plug

[Frank Heimes]

I copied over the latest 4.4-72 dump from IBM Box to our Canonical private file 
share into my home:
/~fheimes/mclint_20170406_kernel_4_4_0-72_without_openafs.dump.bz2
also reachable via https ...

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

Title:
  blk-mq: possible deadlock on CPU hot(un)plug

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Carsten Jacobi  - 2017-03-07 03:35:31 ==
  I'm evaluating Ubuntu-Xenial on z for development purposes, the test system 
is installed in an LPAR with one FCP-LUN which is accessable by 4 pathes (all 
pathes are configured).
  The system hangs regularly when I make packages with "pdebuild" using the 
pbuilder packaging suit.
  The local Linux development team helped me out with a pre-analysis that I can 
post here (thanks a lot for that):

  With the default settings and under a certain workload,
  blk_mq seems to get into a presumed "deadlock".
  Possibly this happens on CPU hot(un)plug.

  After the I/O stalled, a dump was pulled manually.
  The following information is from the crash dump pre-analysis.

  $ zgetdump -i dump.0
  General dump info:
Dump format: elf
Version: 1
UTS node name..: mclint
UTS kernel release.: 4.4.0-65-generic
UTS kernel version.: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
System arch: s390x (64 bit)
CPU count (online).: 2
Dump memory range..: 8192 MB
  Memory map:
 - 0001b831afff (7043 MB)
0001b831b000 - 0001 (1149 MB)

  Things look similarly with HWE kernel ubuntu16.04-4.8.0-34.36~16.04.1.

KERNEL: vmlinux.full
  DUMPFILE: dump.0
  CPUS: 2
  DATE: Fri Mar  3 14:31:07 2017
UPTIME: 02:11:20
  LOAD AVERAGE: 13.00, 12.92, 11.37
 TASKS: 411
  NODENAME: mclint
   RELEASE: 4.4.0-65-generic
   VERSION: #86-Ubuntu SMP Thu Feb 23 17:54:37 UTC 2017
   MACHINE: s390x  (unknown Mhz)
MEMORY: 7.8 GB
 PANIC: ""
   PID: 0
   COMMAND: "swapper/0"
  TASK: bad528  (1 of 2)  [THREAD_INFO: b78000]
   CPU: 0
 STATE: TASK_RUNNING (ACTIVE)
  INFO: no panic task found

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
  [ 5281.179589]  [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs]
  [ 5281.179615]  [<03ff805df114>] 

[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-67 or later

[Andrey Vertexx]

I confirm that removing the virtual DVD drive solves the problem with
backup and live migration.

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-67 or later

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

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  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:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: 

[Kernel-packages] [Bug 1681346] Re: package eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att

[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 eject in Ubuntu.
https://bugs.launchpad.net/bugs/1681346

Title:
  package eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in eject package in Ubuntu:
  New

Bug description:
  After start up the system error report pops up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  Uname: Linux 4.4.0-70-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Apr  9 10:12:02 2017
  DuplicateSignature:
   package:eject:2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1
   Processing triggers for libc-bin (2.23-0ubuntu7) ...
   dpkg: error processing package eject (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-04-26 (348 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: eject
  Title: package eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1681346] [NEW] package eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before a

[Harry Morley]

Public bug reported:

After start up the system error report pops up.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
Uname: Linux 4.4.0-70-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun Apr  9 10:12:02 2017
DuplicateSignature:
 package:eject:2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1
 Processing triggers for libc-bin (2.23-0ubuntu7) ...
 dpkg: error processing package eject (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-04-26 (348 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: eject
Title: package eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: eject (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 eject in Ubuntu.
https://bugs.launchpad.net/bugs/1681346

Title:
  package eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in eject package in Ubuntu:
  New

Bug description:
  After start up the system error report pops up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  Uname: Linux 4.4.0-70-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Apr  9 10:12:02 2017
  DuplicateSignature:
   package:eject:2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1
   Processing triggers for libc-bin (2.23-0ubuntu7) ...
   dpkg: error processing package eject (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-04-26 (348 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: eject
  Title: package eject 2.1.5+deb1+cvs20081104-13.1ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[TomaszChmielewski]

apport information

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

Title:
  "port does not support device sleep" on Dell Precision 5520

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing messages like below on Dell Precision 5520, which is on an
  Ubuntu certified hardware list:

  https://certification.ubuntu.com/hardware/201610-25144/

  BIOS is updated to the latest version available: 1.1.3

  The system has this SATA controller:

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA
  controller [AHCI mode] (rev 31)

  And this 256 GB SSD disk:

  Model Number:   SanDisk X400 2.5 7MM 256GB
  Firmware Revision:  X4130012

  There is a firmware upgrade available for SSD storage on Dell website,
  but unfortunately, the installer is Windows only (a weird thing for a
  Ubuntu certified hardware IMO) - therefore, I was no able to apply it.

  dmesg entries which show up follow below:

  [35713.825698] ata2.00: exception Emask 0x10 SAct 0x4 SErr 0x405 action 
0xe frozen
  [35713.825701] ata2.00: irq_stat 0x0040, connection status changed
  [35713.825703] ata2: SError: { PHYRdyChg CommWake DevExch }
  [35713.825704] ata2.00: failed command: WRITE FPDMA QUEUED
  [35713.825707] ata2.00: cmd 61/18:10:e0:8d:0a/00:00:12:00:00/40 tag 2 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [35713.825709] ata2.00: status: { DRDY }
  [35713.825711] ata2: hard resetting link
  [35714.549641] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [35714.550813] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.550816] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.550818] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.550975] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.553832] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.553835] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.553837] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.553886] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.555383] ata2.00: configured for UDMA/133
  [35714.555399] ahci :00:17.0: port does not support device sleep
  [35714.555493] ata2: EH complete
  [36324.490477] ata2.00: exception Emask 0x10 SAct 0x4000 SErr 0x405 
action 0xe frozen
  [36324.490480] ata2.00: irq_stat 0x0040, connection status changed
  [36324.490482] ata2: SError: { PHYRdyChg CommWake DevExch }
  [36324.490484] ata2.00: failed command: WRITE FPDMA QUEUED
  [36324.490487] ata2.00: cmd 61/18:f0:68:08:85/00:00:07:00:00/40 tag 30 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [36324.490488] ata2.00: status: { DRDY }
  [36324.490490] ata2: hard resetting link
  [36325.214543] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [36325.215658] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [36325.215660] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [36325.215662] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [36325.215731] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [36325.218240] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [36325.218242] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [36325.218243] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [36325.218293] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [36325.219965] ata2.00: configured for UDMA/133
  [36325.219982] ahci :00:17.0: port does not support device sleep
  [36325.220079] ata2: EH complete
  [38355.555685] ata2.00: exception Emask 0x10 SAct 0x800 SErr 0x405 
action 0xe frozen
  [38355.555688] ata2.00: irq_stat 0x0040, connection status changed
  [38355.555690] ata2: SError: { PHYRdyChg CommWake DevExch }
  [38355.555693] ata2.00: failed command: READ FPDMA QUEUED
  [38355.555695] ata2.00: cmd 60/20:d8:78:b4:3a/00:00:12:00:00/40 tag 27 ncq 
16384 in
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [38355.555697] ata2.00: status: { DRDY }
  [38355.555699] ata2: hard resetting link
  [38356.282999] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [38356.284112] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  

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

[TomaszChmielewski]

apport information

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

Title:
  "port does not support device sleep" on Dell Precision 5520

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing messages like below on Dell Precision 5520, which is on an
  Ubuntu certified hardware list:

  https://certification.ubuntu.com/hardware/201610-25144/

  BIOS is updated to the latest version available: 1.1.3

  The system has this SATA controller:

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA
  controller [AHCI mode] (rev 31)

  And this 256 GB SSD disk:

  Model Number:   SanDisk X400 2.5 7MM 256GB
  Firmware Revision:  X4130012

  There is a firmware upgrade available for SSD storage on Dell website,
  but unfortunately, the installer is Windows only (a weird thing for a
  Ubuntu certified hardware IMO) - therefore, I was no able to apply it.

  dmesg entries which show up follow below:

  [35713.825698] ata2.00: exception Emask 0x10 SAct 0x4 SErr 0x405 action 
0xe frozen
  [35713.825701] ata2.00: irq_stat 0x0040, connection status changed
  [35713.825703] ata2: SError: { PHYRdyChg CommWake DevExch }
  [35713.825704] ata2.00: failed command: WRITE FPDMA QUEUED
  [35713.825707] ata2.00: cmd 61/18:10:e0:8d:0a/00:00:12:00:00/40 tag 2 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [35713.825709] ata2.00: status: { DRDY }
  [35713.825711] ata2: hard resetting link
  [35714.549641] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [35714.550813] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.550816] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.550818] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.550975] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.553832] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.553835] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.553837] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.553886] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.555383] ata2.00: configured for UDMA/133
  [35714.555399] ahci :00:17.0: port does not support device sleep
  [35714.555493] ata2: EH complete
  [36324.490477] ata2.00: exception Emask 0x10 SAct 0x4000 SErr 0x405 
action 0xe frozen
  [36324.490480] ata2.00: irq_stat 0x0040, connection status changed
  [36324.490482] ata2: SError: { PHYRdyChg CommWake DevExch }
  [36324.490484] ata2.00: failed command: WRITE FPDMA QUEUED
  [36324.490487] ata2.00: cmd 61/18:f0:68:08:85/00:00:07:00:00/40 tag 30 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [36324.490488] ata2.00: status: { DRDY }
  [36324.490490] ata2: hard resetting link
  [36325.214543] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [36325.215658] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [36325.215660] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [36325.215662] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [36325.215731] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [36325.218240] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [36325.218242] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [36325.218243] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [36325.218293] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [36325.219965] ata2.00: configured for UDMA/133
  [36325.219982] ahci :00:17.0: port does not support device sleep
  [36325.220079] ata2: EH complete
  [38355.555685] ata2.00: exception Emask 0x10 SAct 0x800 SErr 0x405 
action 0xe frozen
  [38355.555688] ata2.00: irq_stat 0x0040, connection status changed
  [38355.555690] ata2: SError: { PHYRdyChg CommWake DevExch }
  [38355.555693] ata2.00: failed command: READ FPDMA QUEUED
  [38355.555695] ata2.00: cmd 60/20:d8:78:b4:3a/00:00:12:00:00/40 tag 27 ncq 
16384 in
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [38355.555697] ata2.00: status: { DRDY }
  [38355.555699] ata2: hard resetting link
  [38356.282999] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [38356.284112] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  

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

[TomaszChmielewski]

apport information

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

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

Title:
  "port does not support device sleep" on Dell Precision 5520

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing messages like below on Dell Precision 5520, which is on an
  Ubuntu certified hardware list:

  https://certification.ubuntu.com/hardware/201610-25144/

  BIOS is updated to the latest version available: 1.1.3

  The system has this SATA controller:

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA
  controller [AHCI mode] (rev 31)

  And this 256 GB SSD disk:

  Model Number:   SanDisk X400 2.5 7MM 256GB
  Firmware Revision:  X4130012

  There is a firmware upgrade available for SSD storage on Dell website,
  but unfortunately, the installer is Windows only (a weird thing for a
  Ubuntu certified hardware IMO) - therefore, I was no able to apply it.

  dmesg entries which show up follow below:

  [35713.825698] ata2.00: exception Emask 0x10 SAct 0x4 SErr 0x405 action 
0xe frozen
  [35713.825701] ata2.00: irq_stat 0x0040, connection status changed
  [35713.825703] ata2: SError: { PHYRdyChg CommWake DevExch }
  [35713.825704] ata2.00: failed command: WRITE FPDMA QUEUED
  [35713.825707] ata2.00: cmd 61/18:10:e0:8d:0a/00:00:12:00:00/40 tag 2 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [35713.825709] ata2.00: status: { DRDY }
  [35713.825711] ata2: hard resetting link
  [35714.549641] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [35714.550813] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.550816] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.550818] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.550975] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.553832] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.553835] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.553837] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.553886] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.555383] ata2.00: configured for UDMA/133
  [35714.555399] ahci :00:17.0: port does not support device sleep
  [35714.555493] ata2: EH complete
  [36324.490477] ata2.00: exception Emask 0x10 SAct 0x4000 SErr 0x405 
action 0xe frozen
  [36324.490480] ata2.00: irq_stat 0x0040, connection status changed
  [36324.490482] ata2: SError: { PHYRdyChg CommWake DevExch }
  [36324.490484] ata2.00: failed command: WRITE FPDMA QUEUED
  [36324.490487] ata2.00: cmd 61/18:f0:68:08:85/00:00:07:00:00/40 tag 30 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [36324.490488] ata2.00: status: { DRDY }
  [36324.490490] ata2: hard resetting link
  [36325.214543] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [36325.215658] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [36325.215660] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [36325.215662] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [36325.215731] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [36325.218240] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [36325.218242] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [36325.218243] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [36325.218293] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [36325.219965] ata2.00: configured for UDMA/133
  [36325.219982] ahci :00:17.0: port does not support device sleep
  [36325.220079] ata2: EH complete
  [38355.555685] ata2.00: exception Emask 0x10 SAct 0x800 SErr 0x405 
action 0xe frozen
  [38355.555688] ata2.00: irq_stat 0x0040, connection status changed
  [38355.555690] ata2: SError: { PHYRdyChg CommWake DevExch }
  [38355.555693] ata2.00: failed command: READ FPDMA QUEUED
  [38355.555695] ata2.00: cmd 60/20:d8:78:b4:3a/00:00:12:00:00/40 tag 27 ncq 
16384 in
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [38355.555697] ata2.00: status: { DRDY }
  [38355.555699] ata2: hard resetting link
  [38356.282999] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [38356.284112] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  

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

[TomaszChmielewski]

apport information

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

Title:
  "port does not support device sleep" on Dell Precision 5520

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm seeing messages like below on Dell Precision 5520, which is on an
  Ubuntu certified hardware list:

  https://certification.ubuntu.com/hardware/201610-25144/

  BIOS is updated to the latest version available: 1.1.3

  The system has this SATA controller:

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA
  controller [AHCI mode] (rev 31)

  And this 256 GB SSD disk:

  Model Number:   SanDisk X400 2.5 7MM 256GB
  Firmware Revision:  X4130012

  There is a firmware upgrade available for SSD storage on Dell website,
  but unfortunately, the installer is Windows only (a weird thing for a
  Ubuntu certified hardware IMO) - therefore, I was no able to apply it.

  dmesg entries which show up follow below:

  [35713.825698] ata2.00: exception Emask 0x10 SAct 0x4 SErr 0x405 action 
0xe frozen
  [35713.825701] ata2.00: irq_stat 0x0040, connection status changed
  [35713.825703] ata2: SError: { PHYRdyChg CommWake DevExch }
  [35713.825704] ata2.00: failed command: WRITE FPDMA QUEUED
  [35713.825707] ata2.00: cmd 61/18:10:e0:8d:0a/00:00:12:00:00/40 tag 2 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [35713.825709] ata2.00: status: { DRDY }
  [35713.825711] ata2: hard resetting link
  [35714.549641] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [35714.550813] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.550816] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.550818] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.550975] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.553832] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [35714.553835] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [35714.553837] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [35714.553886] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [35714.555383] ata2.00: configured for UDMA/133
  [35714.555399] ahci :00:17.0: port does not support device sleep
  [35714.555493] ata2: EH complete
  [36324.490477] ata2.00: exception Emask 0x10 SAct 0x4000 SErr 0x405 
action 0xe frozen
  [36324.490480] ata2.00: irq_stat 0x0040, connection status changed
  [36324.490482] ata2: SError: { PHYRdyChg CommWake DevExch }
  [36324.490484] ata2.00: failed command: WRITE FPDMA QUEUED
  [36324.490487] ata2.00: cmd 61/18:f0:68:08:85/00:00:07:00:00/40 tag 30 ncq 
12288 out
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [36324.490488] ata2.00: status: { DRDY }
  [36324.490490] ata2: hard resetting link
  [36325.214543] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [36325.215658] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [36325.215660] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [36325.215662] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [36325.215731] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [36325.218240] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [36325.218242] ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) 
filtered out
  [36325.218243] ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION 
OVERLAY) filtered out
  [36325.218293] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by 
device (Stat=0x51 Err=0x04)
  [36325.219965] ata2.00: configured for UDMA/133
  [36325.219982] ahci :00:17.0: port does not support device sleep
  [36325.220079] ata2: EH complete
  [38355.555685] ata2.00: exception Emask 0x10 SAct 0x800 SErr 0x405 
action 0xe frozen
  [38355.555688] ata2.00: irq_stat 0x0040, connection status changed
  [38355.555690] ata2: SError: { PHYRdyChg CommWake DevExch }
  [38355.555693] ata2.00: failed command: READ FPDMA QUEUED
  [38355.555695] ata2.00: cmd 60/20:d8:78:b4:3a/00:00:12:00:00/40 tag 27 ncq 
16384 in
  res 50/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x10 
(ATA bus error)
  [38355.555697] ata2.00: status: { DRDY }
  [38355.555699] ata2: hard resetting link
  [38356.282999] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [38356.284112] ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
  [38356.284114]