[Kernel-packages] [Bug 1625932] Re: Backlight does not change when adjust it higher than 50% after S3

[AceLan Kao]

Perry, yes, I'm still working on this to backport the patches to 3.19 kernel.
But, I can not successfully reproduce this issue on the machines I have.
Could you help to try if the kernel fix the issue?
http://people.canonical.com/~acelan/bugs/lp1646537/

The kernel is a little bit older than the latest one, 
so please make sure to boot the system with the right kernel.
Thanks.

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

Title:
  Backlight does not change when adjust it higher than 50% after S3

Status in HWE Next:
  Fix Released
Status in HWE Next vivid series:
  New
Status in HWE Next xenial series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Backlight does not change when adjust it higher than 50% after S3

  Steps:
  1. Install ubuntu 16.04 and boot into OS
  2. suspend system
  3. resume system from S3
  4. Try to adjust brightness level

  Expected results: Backlight should be changed when adjust it

  Actual results: Backlight does not change when adjust it higher than
  50% after S3

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

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

[Kernel-packages] [Bug 1625932] Re: Backlight does not change when adjust it higher than 50% after S3

[perry_yuan]

Could i know whether the two patches have been merged into Ubuntu 14.04 kernel 
codes ?
I found that the issue still can be reproduced on Ubuntu 3.19.0-78 kernel .

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

Title:
  Backlight does not change when adjust it higher than 50% after S3

Status in HWE Next:
  Fix Released
Status in HWE Next vivid series:
  New
Status in HWE Next xenial series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Backlight does not change when adjust it higher than 50% after S3

  Steps:
  1. Install ubuntu 16.04 and boot into OS
  2. suspend system
  3. resume system from S3
  4. Try to adjust brightness level

  Expected results: Backlight should be changed when adjust it

  Actual results: Backlight does not change when adjust it higher than
  50% after S3

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

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

[Kernel-packages] [Bug 1647400] Re: system freeze when swapping to encrypted swap partition

[Frank Heimes]

** Changed in: ubuntu-z-systems
   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/1647400

Title:
  system freeze when swapping to encrypted swap partition

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Bernd-Rainer Bresser  - 2016-12-05 
04:27:00 ==
  +++ This bug was initially created as a clone of Bug #147836 +++

  ---Problem Description---
  When the system is installed with encrypted swap partition the attempt to 
swap ends in a system freeze. No error, no dump, the system needs to be 
reloaded.
   
  Contact Information = Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM 
   
  ---uname output---
  Linux s38lp65 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = z13 LPAR 
   
  ---System Hang---
   System is frozen. No error, no dump, the system needs to be reloaded.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. install a system with encrypted swap partition. This can be done using 
the installer or via manual updates to /etc/fstab and /etc/crypttab.

  2. Verify encrypted swap partition exists
   cryptsetup status kvmibm-swap
  /dev/mapper/kvmibm-swap is active and is in use.
type:PLAIN
cipher:  aes-xts-plain64:sha256
keysize: 256 bits
device:  /dev/dasda2
offset:  0 sectors
size:8388672 sectors
mode:read/write

  3. force swapping
  this can be done by a command like this (if the system has 8GB memory)
  dd if=/dev/zero of=/dev/null ibs=16k obs=8G count=2MB
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Location:
   
   
  *Additional Instructions for Bernd-Rainer Bresser/Germany/IBM, Wen Yi AG 
Gao/China/IBM: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Bernd-Rainer Bresser  - 2016-12-05 
04:33:24 ==
  - the problem was originally found on KVM for IBM z 1.1.3
  - test on Ubuntu 16.04.1 showed the same issue here
  - on KVM for IBM z 1.1.3 the problem could be solved/circumvented by reverting
 commit 564e81a57f9788b1475127012e0fd44e9049e342
Author: Tetsuo Handa 
Date:   Fri Feb 5 15:36:30 2016 -0800
  mm, vmstat: fix wrong WQ sleep when memory reclaim doesn't make 
any progress

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

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

[Kernel-packages] [Bug 1648279] Re: Ethernet not work after upgrade from kernel 3.19 to 4.4 [10ec:8168]

[AceLan Kao]

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

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

Title:
  Ethernet not work after upgrade from kernel 3.19 to 4.4 [10ec:8168]

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

Bug description:
  [Steps]
  1. install trusty image
  2. "sudo apt-get update" and install available updates to enable upgrading in 
images
  3. enable Trusty -proposed ppa
  4. "sudo apt-get update"
  5. "sudo apt-get dist-upgrade && sudo apt-get install --install-recommends 
linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial"
  6. Reboot system
  7. Check Ethernet

  [Expected results]
  Ethernet work

  [Actual results]
  Ethernet not work

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

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

[Kernel-packages] [Bug 1655076] Re: linux-armadaxp: 3.2.0-1682.109 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Hardware Enablement ARM Kernel 
(canonical-hwe-arm-kernel) => Ike Panhc (ikepanhc)

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-armadaxp source package in Precise:
  In Progress

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655071
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1655076] Re: linux-armadaxp: 3.2.0-1682.109 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Hardware Enablement ARM Kernel 
(canonical-hwe-arm-kernel) => Ike Panhc (ikepanhc)

** Description changed:

  This bug is for tracking the 3.2.0-1682.109 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655071
  phase: Packaging
+ kernel-stable-phase-changed:Wednesday, 11. January 2017 04:47 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 3.2.0-1682.109 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655071
- phase: Packaging
- kernel-stable-phase-changed:Wednesday, 11. January 2017 04:47 UTC
- kernel-stable-phase:Uploaded
+ phase: Uploaded

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-armadaxp source package in Precise:
  In Progress

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655071
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1638526] Re: Unable to install AMD Radeon HD 6950 driver

[Launchpad Bug Tracker]

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

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

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

Title:
  Unable to install AMD Radeon HD 6950 driver

Status in linux package in Ubuntu:
  Expired

Bug description:
  Unable to install the suggested amdgpu-pro drivers for AMD Radeon HD 6950.
  Also, running in nomodeset, else I get a black screen with cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-generic 4.8.0.26.35
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gtan   3413 F pulseaudio
   /dev/snd/controlC2:  gtan   3413 F pulseaudio
   /dev/snd/controlC1:  gtan   3413 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov  2 06:59:23 2016
  HibernationDevice: RESUME=UUID=a1677236-2d0c-407e-addc-330c74d1aa5b
  InstallationDate: Installed on 2016-10-31 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   enp5s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z68MX-UD2H-B3
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=6621d948-2de4-406b-811e-fe183abea3ce ro quiet splash nomodeset 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-26-generic N/A
   linux-backports-modules-4.8.0-26-generic  N/A
   linux-firmware1.161
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F12
  dmi.board.name: Z68MX-UD2H-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd10/12/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68MX-UD2H-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68MX-UD2H-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68MX-UD2H-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1640028] Re: fsck or initramfs not working

[Launchpad Bug Tracker]

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

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

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

Title:
  fsck or initramfs not working

Status in linux package in Ubuntu:
  Expired

Bug description:
  when I boot get to  initramfs, when i type exit i get the following
  error.

  ata1: failed command  READ FDMA QUEDED.
  Kenerl panic.
  Kernel offset :disable

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4323 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Tue Nov  8 06:07:36 2016
  LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed cdrom-detect/try-usb=true noprompt 
floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: r8188eu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BEH6110H.86A.0120.2013.1112.1412
  dmi.board.name: DH61SA
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG38870-201
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBEH6110H.86A.0120.2013.1112.1412:bd11/12/2013:svn:pn:pvr:rvnIntelCorporation:rnDH61SA:rvrAAG38870-201:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1650112] Re: ST Micro lng2dm 3-axis "femto" accelerometer support

[Anthony Wong]

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

Title:
  ST Micro lng2dm 3-axis "femto" accelerometer support

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

Bug description:
  Support ST Micro lng2dm 3-axis "femto" accelerometer in Ubuntu kernel.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1650116] Re: ST Micro hts221 relative humidity sensor support

[Anthony Wong]

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

Title:
  ST Micro hts221 relative humidity sensor support

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

Bug description:
  Support ST Micro hts221 relative humidity sensor in Ubuntu kernel.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1650123] Re: Support ACPI probe for IIO sensor drivers from ST Micro

[Anthony Wong]

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

Title:
  Support ACPI probe for IIO sensor drivers from ST Micro

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

Bug description:
  On ACPI based systems, there are no compatible strings from DT to
  match and probe corresponding drivers. Add support use of unique
  identifiers provided by ACPI for ST Micro IIO drivers (accelerometers,
  pressure sensors and hts221 humidity sensors) instead.

  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1650189] Re: Fix channel data parsing in ST Micro sensor IIO drivers

[Anthony Wong]

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

Title:
  Fix channel data parsing in ST Micro sensor IIO drivers

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

Bug description:
  Use correct read length when reading from ST Micro sensors on i2c/spi
  bus.

  
  This bug is used for tracking purposes, please do not triage.

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

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

[Kernel-packages] [Bug 1652348] Re: initrd dhcp fails / ignores valid response

[Jay Vosburgh]

I have instrumented ipconfig, and determined that the ultimate source of the 
problem
is that, for the case of multiple interfaces, ipconfig has a dependency on the 
kernel's probe order of the network interfaces.

For whatever reason, the -31 kernel probes the network devices in one
order (e.g., ens3 then ens4), and the -57 kernel in the other order
(ens4 first then ens3).

The probe order of network devices (and PCI devices in general) is
explicitly not defined, and so this is not a bug in the kernel itself;
ipconfig is failing due to its dependency on a specific enumeration
order.

The issue in ipconfig is that it is using a single packet socket to
attempt to multiplex packet traffic on multiple interfaces.  Presuming
that ens3 will answer DHCP and ens4 will not, for the case that works,
the order ends up being something like:

send DHCP request on ens3
send DHCP request on ens4
[ system gets DHCP response via ens3 ]
try to receive DHCP reply sent by peer for ens3; this matches, and all is happy

For the case that it fails, the sequence is roughly:

send DHCP request on ens4
send DHCP request on ens3
[ system gets DHCP response via ens3 ]
try to receive DHCP reply sent by peer for ens4; the reply is actually for 
ens3, so ipconfig
throws it away (as the XID, et al, don't match what is expected for the ens4 
DHCP request).

This repeats until ipconfig gives up.

As I said above, the issue is that ipconfig is trying to multiplex
traffic for two interfaces on one packet socket.  This is fine for
sending, but for receiving on an unbound packet socket, there is no way
to receive a packet sent to a specific interface.  Packets are delivered
to recvfrom/recvmsg in the order received.

I note that ipconfig sets sll.sll_ifindex on the msghdr provided to
recvfrom and recvmsg system calls; perhaps the author believed that this
limits received packets to only packets received on that ifindex.  This
is not the case, and the sll_ifindex passed to recvfrom/recvmsg is
ignored.

I'm looking into whether or not there is an simple fix for this that
will let ipconfig function without major rework to utilize one packet
socket per interface.



** Tags removed: kernel-key

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

** Changed in: klibc (Ubuntu)
   Status: Triaged => Confirmed

** Changed in: klibc (Ubuntu)
 Assignee: (unassigned) => Jay Vosburgh (jvosburgh)

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

Title:
  initrd dhcp fails / ignores valid response

Status in klibc package in Ubuntu:
  Confirmed
Status in klibc source package in Xenial:
  Triaged

Bug description:
  Between kernel versions 4.4.0-53 and 4.4.0-57 a bug has been
  (re?)introduced that is breaking dhcp booting in the initrd
  environment.  This is stopping instances that use iscsi storage from
  being able to connect.

  Over serial console it outputs:

  IP-Config: no response after 2 secs - giving up
  IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP
  IP-Config: ens2f1 hardware address 90:e2:ba:d1:36:39 mtu 1500 DHCP RARP
  IP-Config: no response after 3 secs - giving up

  with increasing delays until it fails.  At which point a simple
  ipconfig -t dhcp -d "ens2f0"  works.  The console output is slightly
  garbled but should give you an idea:

  (initramfs) ipconfig -t dhcp -[  728.379793] ixgbe :13:00.0 ens2f0: 
changing MTU from 1500 to 9000
  d "ens2f0"
  IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP
  IP-Config: ens2f0 guessed broadcast address 10.0.1.255
  IP-Config: ens2f0 complete (dhcp from 169.254.169.254):
   addres[  728.980448] ixgbe :13:00.0 ens2f0: detected SFP+: 3
  s: 10.0.1.56broadcast: 10.0.1.255   netmask: 255.255.255.0
   gateway: 10.0.1.1   [  729.148410] ixgbe :13:00.0 ens2f0: NIC Link is Up 
10 Gbps, Flow Control: RX/TX
    dns0 : 169.254.169.254  dns1   : 0.0.0.0
   rootserver: 169.254.169.254 rootpath:
   filename  : /ipxe.efi

  tcpdumps show that dhcp requests are being received from the host, and
  responses sent, but not accepted by the host.  When the ipconfig
  command is issued manually, an identical dhcp request and response
  happens, only this time it is accepted.  It doesn't appear to be that
  the messages are being sent and received incorrectly, just silently
  ignored by ipconfig.

  I was seeing this behaviour earlier this year, which I was able to fix
  by specifying "ip=dhcp" as a kernel parameter.  About a month ago that
  was identified as causing us other problems (long story) and we
  dropped it, at which point we discovered the original bug was no
  longer an issue.

  Putting "ip=dhcp" back on with this kernel no longer fixes the
  problem.

  I've compared the two initrds and effectively the only thing that has
  changed between the two is the kernel components.

  Ubuntu kernel bisect 

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just trying to update using Software Updater

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-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/controlC2:  mitchell   3143 F pulseaudio
   /dev/snd/controlC1:  mitchell   3143 F pulseaudio
   /dev/snd/controlC0:  mitchell   3143 F pulseaudio
  Date: Tue Jan 10 19:57:12 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2015-08-10 (519 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=195540f3-343e-4313-8a47-8f1fd8303313 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD5H
  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.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-UD5H
  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/1655521/+subscriptions

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

[Kernel-packages] [Bug 1655521] Re: package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

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

Title:
  package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Just trying to update using Software Updater

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-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/controlC2:  mitchell   3143 F pulseaudio
   /dev/snd/controlC1:  mitchell   3143 F pulseaudio
   /dev/snd/controlC0:  mitchell   3143 F pulseaudio
  Date: Tue Jan 10 19:57:12 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2015-08-10 (519 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=195540f3-343e-4313-8a47-8f1fd8303313 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD5H
  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.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-UD5H
  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/1655521/+subscriptions

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

[Kernel-packages] [Bug 1655521] [NEW] package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Graham Mitchell]

Public bug reported:

Just trying to update using Software Updater

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-34-generic 4.8.0-34.36
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-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/controlC2:  mitchell   3143 F pulseaudio
 /dev/snd/controlC1:  mitchell   3143 F pulseaudio
 /dev/snd/controlC0:  mitchell   3143 F pulseaudio
Date: Tue Jan 10 19:57:12 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
InstallationDate: Installed on 2015-08-10 (519 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IwConfig:
 lono wireless extensions.
 
 eth1  no wireless extensions.
 
 eth0  no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=195540f3-343e-4313-8a47-8f1fd8303313 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F10
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97X-UD5H
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.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z97X-UD5H
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package yakkety

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

Title:
  package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  New

Bug description:
  Just trying to update using Software Updater

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-34-generic 4.8.0-34.36
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-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/controlC2:  mitchell   3143 F pulseaudio
   /dev/snd/controlC1:  mitchell   3143 F pulseaudio
   /dev/snd/controlC0:  mitchell   3143 F pulseaudio
  Date: Tue Jan 10 19:57:12 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2015-08-10 (519 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=195540f3-343e-4313-8a47-8f1fd8303313 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.8.0-34-generic 4.8.0-34.36 failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD5H
  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 

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

[bugproxy]

--- Comment From pt...@cn.ibm.com 2017-01-10 20:20 EDT---
(In reply to comment #7)
> Assigning to Hari for some assistance but would like to know if this issue
> can be recreated consistently and if so how and does this occur on other
> LPARs running the same level?

Looks like this bug only can be reproduced on roselp4 when triggering
bug 150353. But looks like it is quite easy to trigger it when testing
dlpar.

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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

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

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-59.80-lowlatency/onibi__4.4.0-59.80__2017-01-11_00-18-00/results-index.html

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

Title:
  linux: 4.4.0-59.80 -proposed tracker

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

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

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

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

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

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

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

[Arul]

apport information

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

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
  Jan  9 07:36:53 gorilla kernel: [69325.386696] perf: 

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

[Arul]

apport information

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

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
  Jan  9 07:36:53 gorilla kernel: [69325.386696] perf: 

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

[Arul]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1655356/+attachment/4802626/+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/1655356

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
  Jan  9 07:36:53 gorilla kernel: [69325.386696] perf: interrupt took 

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

[Arul]

apport information

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

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

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate 

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

[Arul]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1655356/+attachment/4802623/+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/1655356

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
  Jan  9 07:36:53 gorilla kernel: [69325.386696] perf: 

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

[Arul]

apport information

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

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
  Jan  9 07:36:53 gorilla kernel: [69325.386696] perf: 

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

[Arul]

apport information

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

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
  Jan  9 07:36:53 gorilla kernel: [69325.386696] perf: interrupt took too 

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

[Arul]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1655356/+attachment/4802621/+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/1655356

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
  Jan  9 07:36:53 gorilla kernel: [69325.386696] perf: interrupt took too 

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

[Arul]

apport information

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

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
  Jan  9 07:36:53 gorilla kernel: [69325.386696] perf: interrupt took too 

[Kernel-packages] [Bug 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

[Arul]

apport information

** Tags added: apport-collected

** Description changed:

  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was running
  Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this problem
  started with errors, OOM and an eventual kernel panic. It can run fine
  for about 3-4 hours or so. I see the following errors on syslog (also
  attached w/ other logs and information I can gather).
  
  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  
  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  
  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
  Jan  9 07:36:53 gorilla kernel: [69325.386696] perf: interrupt took too long 
(7723 > 7712), lowering kernel.perf_event_max_sample_rate to 25750
  
  
  Just to make sure if this is not memory related, I ran memtest for 12 passes 
over night and found no errors on memory. Removed the external backup drives to 
isolate the problem. Checked similar issues on lanchpad.net but most of them 
are related to video driver and power supply.
  
  Appreciate help.
  
  Thanks
  -Arul
  
  Attachments:
  

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

[Arul]

apport information

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

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
  Jan  9 07:36:53 gorilla kernel: [69325.386696] perf: 

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

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-59.80-lowlatency/onza__4.4.0-59.80__2017-01-10_23-56-00/results-index.html

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

Title:
  linux: 4.4.0-59.80 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1655123] Re: Kernel 4.10 stalls on restart

[Mikemecanic]

The only way to reach Grub’s menu is a cold shut down or to unplug the
power supply.

1. The clock is set default to 30sec.(no effect at 3sec.).   The menu is 
black-low-res.
$ sudo update-grub2 shows Kylin boot image and I’m able to open it.  Installer 
was black?

2. HP key enabled in bios gives a third option in the menu: System
Setup.  In/out in ss shows the Grub menu in native res.

3. I was not able to reproduce a bug where boot stalls on Grub with no
count down and stays in idle state until enter’s press.

Done with this install and its 24 hours agreement.  In order to restore
splash screen, a more robust acpi correction(s) would be appreciate.
Thanks in advance!

Regards,

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

Title:
  Kernel 4.10 stalls on restart

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

Bug description:
  For rc2 and rc3, the machine stalls on first restart only (no tty) and
  runs OK after (no shutdown problems).   Same result when removing the
  lowest Kernel (all of them).  Canonical Kernel permanently stalls on
  restart but runs OK.  Plus, the boot sequence passes by the Grub menu
  under 4.10.0-0 (not dual-boot, UEFI).

  Since last night, suspend mode won’t wake-up under rc3 (no tty).  Kernel 4.9 
stable (.0 and .1) are working properly. 4.10-rc1=Kernel panic.  FYI, for a 
couple of months now, Gnome Software refuses to install custom kernel.  
20170107 build.
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-09 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109)
  Package: linux (not installed)
  Tags:  zesty
  Uname: Linux 4.9.1-040901-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-09 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109)
  Package: linux (not installed)
  Tags:  zesty
  Uname: Linux 4.10.0-041000rc2-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-01-09 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109)
  Package: linux (not installed)
  Tags:  zesty
  Uname: Linux 4.10.0-041000rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zz 1890 F pulseaudio
   /dev/snd/controlC0:  zz 1890 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=a3efa8c9-5e91-4fd9-a964-4e50d94b2a8e
  InstallationDate: Installed on 2017-01-09 (0 days ago)
  InstallationMedia: Ubuntu-Kylin 17.04 "Zesty Zapus" - Alpha amd64 (20170109)
  IwConfig:
   enp1s0no wireless extensions.
   
   lono wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: HP 24-b019
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-1-generic.efi.signed 
root=UUID=50b68bf8-7434-4e69-80e7-a4b539b0d36d ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-1.3-generic 4.10.0-rc3
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-1-generic N/A
   linux-backports-modules-4.10.0-1-generic  N/A
   linux-firmware1.162
  RfKill:
   
  Tags:  zesty
  Uname: Linux 4.10.0-1-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: 8CC6351M4W
  dmi.board.name: 81B8
  dmi.board.vendor: HP
  dmi.board.version: 0100
  dmi.chassis.asset.tag: 8CC6351M4W
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.deferred.probe: 0
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd03/25/2016:svnHP:pn24-b019:pvr:rvnHP:rn81B8:rvr0100:cvnHP:ct13:cvr:
  dmi.product.name: 24-b019
  

[Kernel-packages] [Bug 1655437] Re: 16.04 fails to boot with kernel 4.4.0-22-generic

[jeffrey leung]

apport information

** Tags added: apport-collected xenial

** Description changed:

  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to be
  on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards we
  found it wasn't able to boot due to some volume group issues it appears
  from the error messages.
  
  We fixed the driver issue on our end to target the correct inbox kernel
  version and it's working fine. We also haven't seen any issues with
  16.04 and newer kernels. However, management is still concerned about
  the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is it
  possible to look into this issue? Or maybe would it be possible to get
  that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?
  
  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then upgrading
  to 4.4.0-22-generic and rebooting after install.
  
  1. If I install 16.04 with auto partitioning, after updating the kernel
  to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found errors.
  I’ve attached ubuntu.jpg for this.
  
  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.
  
  Thanks,
  Jeff
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba
+ InstallationDate: Installed on 2017-01-10 (0 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
+ IwConfig:
+  enp138s0  no wireless extensions.
+  
+  enp133s0  no wireless extensions.
+  
+  lono wireless extensions.
+ Lsusb:
+  Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and 
Mouse
+  Bus 002 Device 002: ID 8087:8002 Intel Corp. 
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 002: ID 8087:800a Intel Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Cisco Systems Inc UCSB-B420-M4
+ Package: linux (not installed)
+ ProcEnviron:
+  LANGUAGE=en_US
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-21-generic N/A
+  linux-backports-modules-4.4.0-21-generic  N/A
+  linux-firmware1.157
+ RfKill:
+  
+ Tags:  xenial
+ Uname: Linux 4.4.0-21-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 11/07/2016
+ dmi.bios.vendor: Cisco Systems, Inc.
+ dmi.bios.version: B420M4.3.1.2f.0.110720161154
+ dmi.board.name: UCSB-B420-M4
+ dmi.board.vendor: Cisco Systems Inc
+ dmi.board.version: 73-16458-06
+ dmi.chassis.type: 18
+ dmi.chassis.vendor: Cisco Systems Inc
+ dmi.chassis.version: 68-4777-02
+ dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
+ dmi.product.name: UCSB-B420-M4
+ dmi.product.version: 03
+ dmi.sys.vendor: Cisco Systems Inc

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

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to
  be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards
  we found it wasn't able to boot due to some volume group issues it
  appears from the error messages.

  We fixed the driver issue on our end to target the correct inbox
  kernel version and it's working fine. We also haven't seen any issues
  with 16.04 and newer kernels. However, management is still concerned
  about the issue with 16.04 xenial xerus at 

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

[jeffrey leung]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1655437/+attachment/4802615/+files/WifiSyslog.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/1655437

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to
  be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards
  we found it wasn't able to boot due to some volume group issues it
  appears from the error messages.

  We fixed the driver issue on our end to target the correct inbox
  kernel version and it's working fine. We also haven't seen any issues
  with 16.04 and newer kernels. However, management is still concerned
  about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
  it possible to look into this issue? Or maybe would it be possible to
  get that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?

  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then
  upgrading to 4.4.0-22-generic and rebooting after install.

  1. If I install 16.04 with auto partitioning, after updating the
  kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
  errors. I’ve attached ubuntu.jpg for this.

  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.

  Thanks,
  Jeff
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba
  InstallationDate: Installed on 2017-01-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp138s0  no wireless extensions.
   
   enp133s0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and 
Mouse
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Cisco Systems Inc UCSB-B420-M4
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: Cisco Systems, Inc.
  dmi.bios.version: B420M4.3.1.2f.0.110720161154
  dmi.board.name: UCSB-B420-M4
  dmi.board.vendor: Cisco Systems Inc
  dmi.board.version: 73-16458-06
  dmi.chassis.type: 18
  dmi.chassis.vendor: Cisco Systems Inc
  dmi.chassis.version: 68-4777-02
  dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
  dmi.product.name: UCSB-B420-M4
  dmi.product.version: 03
  dmi.sys.vendor: Cisco Systems Inc

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

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

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

[jeffrey leung]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1655437/+attachment/4802610/+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/1655437

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to
  be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards
  we found it wasn't able to boot due to some volume group issues it
  appears from the error messages.

  We fixed the driver issue on our end to target the correct inbox
  kernel version and it's working fine. We also haven't seen any issues
  with 16.04 and newer kernels. However, management is still concerned
  about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
  it possible to look into this issue? Or maybe would it be possible to
  get that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?

  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then
  upgrading to 4.4.0-22-generic and rebooting after install.

  1. If I install 16.04 with auto partitioning, after updating the
  kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
  errors. I’ve attached ubuntu.jpg for this.

  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.

  Thanks,
  Jeff
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba
  InstallationDate: Installed on 2017-01-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp138s0  no wireless extensions.
   
   enp133s0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and 
Mouse
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Cisco Systems Inc UCSB-B420-M4
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: Cisco Systems, Inc.
  dmi.bios.version: B420M4.3.1.2f.0.110720161154
  dmi.board.name: UCSB-B420-M4
  dmi.board.vendor: Cisco Systems Inc
  dmi.board.version: 73-16458-06
  dmi.chassis.type: 18
  dmi.chassis.vendor: Cisco Systems Inc
  dmi.chassis.version: 68-4777-02
  dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
  dmi.product.name: UCSB-B420-M4
  dmi.product.version: 03
  dmi.sys.vendor: Cisco Systems Inc

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

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

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

[jeffrey leung]

apport information

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

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to
  be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards
  we found it wasn't able to boot due to some volume group issues it
  appears from the error messages.

  We fixed the driver issue on our end to target the correct inbox
  kernel version and it's working fine. We also haven't seen any issues
  with 16.04 and newer kernels. However, management is still concerned
  about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
  it possible to look into this issue? Or maybe would it be possible to
  get that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?

  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then
  upgrading to 4.4.0-22-generic and rebooting after install.

  1. If I install 16.04 with auto partitioning, after updating the
  kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
  errors. I’ve attached ubuntu.jpg for this.

  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.

  Thanks,
  Jeff
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba
  InstallationDate: Installed on 2017-01-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp138s0  no wireless extensions.
   
   enp133s0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and 
Mouse
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Cisco Systems Inc UCSB-B420-M4
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: Cisco Systems, Inc.
  dmi.bios.version: B420M4.3.1.2f.0.110720161154
  dmi.board.name: UCSB-B420-M4
  dmi.board.vendor: Cisco Systems Inc
  dmi.board.version: 73-16458-06
  dmi.chassis.type: 18
  dmi.chassis.vendor: Cisco Systems Inc
  dmi.chassis.version: 68-4777-02
  dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
  dmi.product.name: UCSB-B420-M4
  dmi.product.version: 03
  dmi.sys.vendor: Cisco Systems Inc

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

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

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

[jeffrey leung]

apport information

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

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to
  be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards
  we found it wasn't able to boot due to some volume group issues it
  appears from the error messages.

  We fixed the driver issue on our end to target the correct inbox
  kernel version and it's working fine. We also haven't seen any issues
  with 16.04 and newer kernels. However, management is still concerned
  about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
  it possible to look into this issue? Or maybe would it be possible to
  get that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?

  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then
  upgrading to 4.4.0-22-generic and rebooting after install.

  1. If I install 16.04 with auto partitioning, after updating the
  kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
  errors. I’ve attached ubuntu.jpg for this.

  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.

  Thanks,
  Jeff
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba
  InstallationDate: Installed on 2017-01-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp138s0  no wireless extensions.
   
   enp133s0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and 
Mouse
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Cisco Systems Inc UCSB-B420-M4
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: Cisco Systems, Inc.
  dmi.bios.version: B420M4.3.1.2f.0.110720161154
  dmi.board.name: UCSB-B420-M4
  dmi.board.vendor: Cisco Systems Inc
  dmi.board.version: 73-16458-06
  dmi.chassis.type: 18
  dmi.chassis.vendor: Cisco Systems Inc
  dmi.chassis.version: 68-4777-02
  dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
  dmi.product.name: UCSB-B420-M4
  dmi.product.version: 03
  dmi.sys.vendor: Cisco Systems Inc

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

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

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

[jeffrey leung]

apport information

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

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to
  be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards
  we found it wasn't able to boot due to some volume group issues it
  appears from the error messages.

  We fixed the driver issue on our end to target the correct inbox
  kernel version and it's working fine. We also haven't seen any issues
  with 16.04 and newer kernels. However, management is still concerned
  about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
  it possible to look into this issue? Or maybe would it be possible to
  get that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?

  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then
  upgrading to 4.4.0-22-generic and rebooting after install.

  1. If I install 16.04 with auto partitioning, after updating the
  kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
  errors. I’ve attached ubuntu.jpg for this.

  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.

  Thanks,
  Jeff
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba
  InstallationDate: Installed on 2017-01-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp138s0  no wireless extensions.
   
   enp133s0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and 
Mouse
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Cisco Systems Inc UCSB-B420-M4
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: Cisco Systems, Inc.
  dmi.bios.version: B420M4.3.1.2f.0.110720161154
  dmi.board.name: UCSB-B420-M4
  dmi.board.vendor: Cisco Systems Inc
  dmi.board.version: 73-16458-06
  dmi.chassis.type: 18
  dmi.chassis.vendor: Cisco Systems Inc
  dmi.chassis.version: 68-4777-02
  dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
  dmi.product.name: UCSB-B420-M4
  dmi.product.version: 03
  dmi.sys.vendor: Cisco Systems Inc

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

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

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

[jeffrey leung]

apport information

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

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to
  be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards
  we found it wasn't able to boot due to some volume group issues it
  appears from the error messages.

  We fixed the driver issue on our end to target the correct inbox
  kernel version and it's working fine. We also haven't seen any issues
  with 16.04 and newer kernels. However, management is still concerned
  about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
  it possible to look into this issue? Or maybe would it be possible to
  get that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?

  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then
  upgrading to 4.4.0-22-generic and rebooting after install.

  1. If I install 16.04 with auto partitioning, after updating the
  kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
  errors. I’ve attached ubuntu.jpg for this.

  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.

  Thanks,
  Jeff
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba
  InstallationDate: Installed on 2017-01-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp138s0  no wireless extensions.
   
   enp133s0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and 
Mouse
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Cisco Systems Inc UCSB-B420-M4
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: Cisco Systems, Inc.
  dmi.bios.version: B420M4.3.1.2f.0.110720161154
  dmi.board.name: UCSB-B420-M4
  dmi.board.vendor: Cisco Systems Inc
  dmi.board.version: 73-16458-06
  dmi.chassis.type: 18
  dmi.chassis.vendor: Cisco Systems Inc
  dmi.chassis.version: 68-4777-02
  dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
  dmi.product.name: UCSB-B420-M4
  dmi.product.version: 03
  dmi.sys.vendor: Cisco Systems Inc

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

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

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

[jeffrey leung]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1655437/+attachment/4802611/+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/1655437

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to
  be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards
  we found it wasn't able to boot due to some volume group issues it
  appears from the error messages.

  We fixed the driver issue on our end to target the correct inbox
  kernel version and it's working fine. We also haven't seen any issues
  with 16.04 and newer kernels. However, management is still concerned
  about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
  it possible to look into this issue? Or maybe would it be possible to
  get that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?

  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then
  upgrading to 4.4.0-22-generic and rebooting after install.

  1. If I install 16.04 with auto partitioning, after updating the
  kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
  errors. I’ve attached ubuntu.jpg for this.

  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.

  Thanks,
  Jeff
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba
  InstallationDate: Installed on 2017-01-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp138s0  no wireless extensions.
   
   enp133s0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and 
Mouse
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Cisco Systems Inc UCSB-B420-M4
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: Cisco Systems, Inc.
  dmi.bios.version: B420M4.3.1.2f.0.110720161154
  dmi.board.name: UCSB-B420-M4
  dmi.board.vendor: Cisco Systems Inc
  dmi.board.version: 73-16458-06
  dmi.chassis.type: 18
  dmi.chassis.vendor: Cisco Systems Inc
  dmi.chassis.version: 68-4777-02
  dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
  dmi.product.name: UCSB-B420-M4
  dmi.product.version: 03
  dmi.sys.vendor: Cisco Systems Inc

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

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

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

[jeffrey leung]

apport information

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

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to
  be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards
  we found it wasn't able to boot due to some volume group issues it
  appears from the error messages.

  We fixed the driver issue on our end to target the correct inbox
  kernel version and it's working fine. We also haven't seen any issues
  with 16.04 and newer kernels. However, management is still concerned
  about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
  it possible to look into this issue? Or maybe would it be possible to
  get that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?

  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then
  upgrading to 4.4.0-22-generic and rebooting after install.

  1. If I install 16.04 with auto partitioning, after updating the
  kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
  errors. I’ve attached ubuntu.jpg for this.

  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.

  Thanks,
  Jeff
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba
  InstallationDate: Installed on 2017-01-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp138s0  no wireless extensions.
   
   enp133s0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and 
Mouse
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Cisco Systems Inc UCSB-B420-M4
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: Cisco Systems, Inc.
  dmi.bios.version: B420M4.3.1.2f.0.110720161154
  dmi.board.name: UCSB-B420-M4
  dmi.board.vendor: Cisco Systems Inc
  dmi.board.version: 73-16458-06
  dmi.chassis.type: 18
  dmi.chassis.vendor: Cisco Systems Inc
  dmi.chassis.version: 68-4777-02
  dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
  dmi.product.name: UCSB-B420-M4
  dmi.product.version: 03
  dmi.sys.vendor: Cisco Systems Inc

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

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

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

[jeffrey leung]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1655437/+attachment/4802614/+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/1655437

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to
  be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards
  we found it wasn't able to boot due to some volume group issues it
  appears from the error messages.

  We fixed the driver issue on our end to target the correct inbox
  kernel version and it's working fine. We also haven't seen any issues
  with 16.04 and newer kernels. However, management is still concerned
  about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
  it possible to look into this issue? Or maybe would it be possible to
  get that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?

  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then
  upgrading to 4.4.0-22-generic and rebooting after install.

  1. If I install 16.04 with auto partitioning, after updating the
  kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
  errors. I’ve attached ubuntu.jpg for this.

  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.

  Thanks,
  Jeff
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba
  InstallationDate: Installed on 2017-01-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp138s0  no wireless extensions.
   
   enp133s0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and 
Mouse
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Cisco Systems Inc UCSB-B420-M4
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: Cisco Systems, Inc.
  dmi.bios.version: B420M4.3.1.2f.0.110720161154
  dmi.board.name: UCSB-B420-M4
  dmi.board.vendor: Cisco Systems Inc
  dmi.board.version: 73-16458-06
  dmi.chassis.type: 18
  dmi.chassis.vendor: Cisco Systems Inc
  dmi.chassis.version: 68-4777-02
  dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
  dmi.product.name: UCSB-B420-M4
  dmi.product.version: 03
  dmi.sys.vendor: Cisco Systems Inc

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

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

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

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-59.80-lowlatency/onibi__4.4.0-59.80__2017-01-10_22-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/1654282

Title:
  linux: 4.4.0-59.80 -proposed tracker

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

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

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

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

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

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

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

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-59.80-lowlatency/onza__4.4.0-59.80__2017-01-10_22-41-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/1654282

Title:
  linux: 4.4.0-59.80 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1655379] Re: Bug fixes for IBM VNIC Driver

[Tim Gardner]

brenohl - How about this: ? Note that I've used '-s -x' when cherry
picking, and have inserted a BugLink into the patch.

The following changes since commit
e2cafae0c1f4504a34f0910356a31257763b101f:

  ftrace/x86_32: Set ftrace_stub to weak to prevent gcc from using short
jumps to it (2017-01-09 16:25:37 +)

are available in the git repository at:

  git://kernel.ubuntu.com/rtg/ubuntu-yakkety.git vnic

for you to fetch changes up to defac4f7e4bcfde4c89f966a911d6ddbd3145151:

  ibmvnic: Fix size of debugfs name buffer (2017-01-10 16:03:21 -0700)


John Allen (1):
  ibmvnic: Start completion queue negotiation at server-provided optimum 
values

Thomas Falcon (6):
  ibmvnic: Fix GFP_KERNEL allocation in interrupt context
  ibmvnic: Update MTU after device initialization
  ibmvnic: Fix releasing of sub-CRQ IRQs in interrupt context
  ibmvnic: Fix missing brackets in init_sub_crq_irqs
  ibmvnic: Unmap ibmvnic_statistics structure
  ibmvnic: Fix size of debugfs name buffer

 drivers/net/ethernet/ibm/ibmvnic.c | 55 
+--
 drivers/net/ethernet/ibm/ibmvnic.h |  1 +
 2 files changed, 38 insertions(+), 18 deletions(-)


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

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

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

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

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

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

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

Title:
  Bug fixes for IBM VNIC Driver

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

Bug description:
  In order to bring the VNIC driver up to date and pull in fixes for all
  of the bugs we have seen we would need to have the following patches
  applied.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=12608c260d2fe36746508cb4fa20b6e9a5f9c241

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=87737f8810db445db171ca81ca4cc43bd5b067ce

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=d894be57ca92c8a8819ab544d550809e8731137b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=9888d7b02c7793cbbcbdd05dd9e14cc0e78d1db7

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=8bf371e6adff29758cc3c57c17df4486513081f8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=6dbcd8fb5968fda3a5fba019dfb0c80c3139627b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=b7f193da17fb18b752bef77ce52eb49723299bd8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=e1fac0adf0f9b2c1eb49e658e6ed070a744bbaef

  I created a tree based on 16.04.2 kernel and included these commits.

  https://github.com/leitao/ubuntu-yakkety/tree/vnic

  I will be generating kernel binaries, so, we can test it.

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

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

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

[Brad Figg]

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

** 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 3.13.0-108.155~precise1 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: 1655476
+ kernel-stable-phase-changed:Tuesday, 10. January 2017 22:45 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the 3.13.0-108.155~precise1 upload package.
  This bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ derivative-trackers-created: true
  kernel-stable-master-bug: 1655476
- kernel-stable-phase-changed:Tuesday, 10. January 2017 22:45 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/1655480

Title:
  linux-lts-trusty: 3.13.0-108.155~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:
  Confirmed
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 verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1655476
  phase: Packaging

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

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

[Kernel-packages] [Bug 1655476] Re: linux: 3.13.0-108.155 -proposed tracker

[Brad Figg]

Derivative packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-keystone - bug 1655479

Backport packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-lts-trusty (precise1) - bug 1655480

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

** 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 3.13.0-108.155 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-stable-phase-changed:Tuesday, 10. January 2017 22:30 UTC
+ kernel-stable-phase:Packaging

** Description changed:

  This bug is for tracking the 3.13.0-108.155 upload package. This bug
  will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-stable-phase-changed:Tuesday, 10. January 2017 22:30 UTC
  kernel-stable-phase:Packaging
+ 
+ -- swm properties --
+ derivative-trackers-created: true
+ phase: Packaging

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

Title:
  linux: 3.13.0-108.155 -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:
  Confirmed
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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

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

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

  kernel-stable-phase-changed:Tuesday, 10. January 2017 22:30 UTC
  kernel-stable-phase:Packaging

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

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

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

[Kernel-packages] [Bug 1655480] [NEW] linux-lts-trusty: 3.13.0-108.155~precise1 -proposed tracker

[Brad Figg]

Public bug reported:

This bug is for tracking the 3.13.0-108.155~precise1 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: 1655476

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

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

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

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

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

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

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

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

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

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

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Medium
 Status: Confirmed


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

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

** Tags added: block-proposed-precise

** Also affects: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Tags added: precise

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: New => Confirmed

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

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

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

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

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

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

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

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

** Changed in: 

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

[Brad Figg]

tests ran:  23, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-59.80-lowlatency/onza__4.4.0-59.80__2017-01-10_20-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/1654282

Title:
  linux: 4.4.0-59.80 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1654282] onibi (i386) - tests ran: 20, failed: 0

[Brad Figg]

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-59.80-lowlatency/onibi__4.4.0-59.80__2017-01-10_20-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/1654282

Title:
  linux: 4.4.0-59.80 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1655476] [NEW] linux: 3.13.0-108.155 -proposed tracker

[John Donnelly]

Public bug reported:

This bug is for tracking the 3.13.0-108.155 upload package. This bug
will contain status and testing results related to that upload.

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

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

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

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

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

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

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

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

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

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

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

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


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

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

** Tags added: block-proposed-trusty

** Tags added: trusty

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

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

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

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

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

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

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

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

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

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

** Changed in: 

[Kernel-packages] [Bug 1630069] Re: Regression tests can not detect binfmt_elf mmpa semantic change

[John Johansen]

** Changed in: apparmor (Ubuntu)
   Status: New => Fix Released

** Changed in: apparmor
   Status: Fix Committed => Fix Released

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

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

Title:
  Regression tests can not detect binfmt_elf mmpa semantic change

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in apparmor source package in Yakkety:
  Won't Fix
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  == apparmor SRU ==

  [Impact]

   * The exec_stack.sh regression test fails due to a behavior change in 4.8
     kernels from this patch:

     commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46
     Author: Linus Torvalds 
     Date: Mon Aug 22 16:41:46 2016 -0700

     binfmt_elf: switch to new creds when switching to new mm

   * The regression tests were fixed for this kernel change but they were fixed
     in a way that always assumed that kernel change is present. They should 
have
     been adjusted so that they act differently according to whether or not the
     kernel change is present (it is a change that could end up being backported
     through the stable trees).

  [Test Case]

   $ apt-get source apparmor # make sure this fetches the new apparmor source
   $ sudo apt-get install libapparmor-dev
   $ cd tests/regression/apparmor
   $ make USE_SYSTEM=1
   $ sudo bash exec_stack.sh

   The previous command should result in no output and return value of
  0.

  [Regression Potential]

   * This is an extremely low risk change since it only touches regression
     testing code that is not user-facing.

  [Other]

   * Fixed in upstream lp:apparmor tree:

     https://bazaar.launchpad.net/~apparmor-
  dev/apparmor/master/revision/3558

  == Original description ==

  The regression tests are currently hard coded to the semantics of mmap
  in binfmt_elf

  With the recent upstream commit
  9f834ec18defc369d73ccf9e87a2790bfa05bf46 the cred used for the mmap
  changed resulting in test failures. The tests have been patched for
  this change but it results in the test breaking for everyone using
  upstream releases against pre 4.8 kernels.

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

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

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

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.9.0-12.13-generic/ms10-35-mcdivittB0-kernel__4.9.0-12.13__2017-01-10_22-13-00/results-index.html

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

Title:
  linux: 4.9.0-12.13 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1655421] Re: nouveau driver being too conservative about HDMI pixel clock, barring usage of native resolution on 4K displays over HDMI

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2017-January/081801.html

** Package changed: linux-lts-xenial (Ubuntu) => linux (Ubuntu)

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Frode Nordahl (fnordahl)

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Frode Nordahl (fnordahl)

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

Title:
  nouveau driver being too conservative about HDMI pixel clock, barring
  usage of native resolution on 4K displays over HDMI

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

Bug description:
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993311] 
[drm:drm_add_edid_modes.part.22 [drm]] HDMI: DVI dual 0, max TMDS clock 30 
kHz
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993315] nouveau :01:00.0: 
DRM: native mode from largest: 1920x1080@60
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993342] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 69:"3840x2160" 30 297000 3840 
4016 4104 4400 2160 2168 2178 2250 0x48 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993348] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993353] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 73:"2560x1440" 60 241500 2560 
2608 2640 2720 1440 1443 1448 1481 0x40 0x9
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993358] 
[drm:drm_mode_prune_invalid [drm]] Not using 2560x1440 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993363] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 104:"3840x2160" 25 297000 
3840 4896 4984 5280 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993368] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993373] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 105:"3840x2160" 24 297000 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993378] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993383] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 106:"3840x2160" 30 296703 
3840 4016 4104 4400 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993387] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993392] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 116:"3840x2160" 24 296703 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993397] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH

  However it is perfectly valid to use higher pixel clock on some
  graphic cards.

  This patch will allow the end-user to adjust the pixel clock with the hdmimhz 
kernel parameter until the detection code gets good enough:
  
https://github.com/torvalds/linux/commit/1a0c96c075bb4517d4ce4fb6750ee0a3cf38714c

  This page contains a lot of useful information and lead me to a sollution to 
my problem:
  https://www.elstel.org/software/hunt-for-4K-UHD-2160p.html.en

  I think this is worthy of consideration for backport to the Xenial kernel as 
not being able to use the most recent LTS version of Ubuntu Desktop with 
current hardware is a drag.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  frode  2797 F pulseaudio
   /dev/snd/controlC0:  frode  2797 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ae0b4ef2-57b4-4ab5-ac55-be113c10f1d1
  InstallationDate: Installed on 2017-01-08 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Apple Inc. MacBookPro10,1
  NonfreeKernelModules: wl
  Package: linux-image-extra-4.4.0-59-generic 4.4.0-59.80
  PackageArchitecture: amd64
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash hdmimhz=297 vt.handoff=7
  

[Kernel-packages] [Bug 1655420] Re: Ubuntu - ibmveth: abnormally large TCP MSS value caused a TCP session to hang with a zero window

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2017-January/081798.html

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

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

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

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

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

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

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

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

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

Title:
  Ubuntu - ibmveth: abnormally large TCP MSS value caused a TCP session
  to hang with a zero window

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

Bug description:
  == Comment: #0 - THOMAS L. FALCON - 2017-01-10 11:54:24 ==

  This bug is being mirrored for any distributions that include ibmveth
  large send/receive support.  In short, any distribution with ibmveth
  v1.05 will be affected (releases 14.04.5/Wily+)

  2 upstream commits:

  1. Set GSO size and type
  
https://github.com/torvalds/linux/commit/7b5967389f5a8dfb9d32843830f5e2717e20995d
  2. set GSO segments
  
https://github.com/torvalds/linux/commit/94acf164dc8f1184e8d0737be7125134c2701dbe

  A VIOS fix is needed as well.

  ---Problem Description---
  When ibmveth interface on a PowerVM logical partition received a large, 
aggregated packet from firmware, the gso fields in the socket buffer shared 
info were not filled in correctly.  This surfaced in a bug where the TCP rx 
window calculation algorithm returned a Zero Window even when there was 
available space.

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

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

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1655437

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to
  be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards
  we found it wasn't able to boot due to some volume group issues it
  appears from the error messages.

  We fixed the driver issue on our end to target the correct inbox
  kernel version and it's working fine. We also haven't seen any issues
  with 16.04 and newer kernels. However, management is still concerned
  about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
  it possible to look into this issue? Or maybe would it be possible to
  get that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?

  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then
  upgrading to 4.4.0-22-generic and rebooting after install.

  1. If I install 16.04 with auto partitioning, after updating the
  kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
  errors. I’ve attached ubuntu.jpg for this.

  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.

  Thanks,
  Jeff

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

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

[Kernel-packages] [Bug 1655421] [NEW] nouveau driver being too conservative about HDMI pixel clock, barring usage of native resolution on 4K displays over HDMI

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Jan 10 18:56:03 frode-MacBookPro kernel: [4.993311] 
[drm:drm_add_edid_modes.part.22 [drm]] HDMI: DVI dual 0, max TMDS clock 30 
kHz
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993315] nouveau :01:00.0: 
DRM: native mode from largest: 1920x1080@60
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993342] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 69:"3840x2160" 30 297000 3840 
4016 4104 4400 2160 2168 2178 2250 0x48 0x5
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993348] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993353] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 73:"2560x1440" 60 241500 2560 
2608 2640 2720 1440 1443 1448 1481 0x40 0x9
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993358] 
[drm:drm_mode_prune_invalid [drm]] Not using 2560x1440 mode: CLOCK_HIGH
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993363] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 104:"3840x2160" 25 297000 
3840 4896 4984 5280 2160 2168 2178 2250 0x40 0x5
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993368] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993373] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 105:"3840x2160" 24 297000 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993378] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993383] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 106:"3840x2160" 30 296703 
3840 4016 4104 4400 2160 2168 2178 2250 0x40 0x5
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993387] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993392] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 116:"3840x2160" 24 296703 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993397] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH

However it is perfectly valid to use higher pixel clock on some graphic
cards.

This patch will allow the end-user to adjust the pixel clock with the hdmimhz 
kernel parameter until the detection code gets good enough:
https://github.com/torvalds/linux/commit/1a0c96c075bb4517d4ce4fb6750ee0a3cf38714c

This page contains a lot of useful information and lead me to a sollution to my 
problem:
https://www.elstel.org/software/hunt-for-4K-UHD-2160p.html.en

I think this is worthy of consideration for backport to the Xenial kernel as 
not being able to use the most recent LTS version of Ubuntu Desktop with 
current hardware is a drag.
--- 
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  frode  2797 F pulseaudio
 /dev/snd/controlC0:  frode  2797 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=ae0b4ef2-57b4-4ab5-ac55-be113c10f1d1
InstallationDate: Installed on 2017-01-08 (2 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Apple Inc. MacBookPro10,1
NonfreeKernelModules: wl
Package: linux-image-extra-4.4.0-59-generic 4.4.0-59.80
PackageArchitecture: amd64
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash hdmimhz=297 vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
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
Tags:  xenial
Uname: Linux 4.4.0-59-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/20/2016
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00EE.B0B.1610201442
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B0B.1610201442:bd10/20/2016:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: apport-collected xenial
-- 
nouveau driver being too conservative about HDMI pixel clock, barring usage of 
native resolution on 4K displays over HDMI
https://bugs.launchpad.net/bugs/1655421
You received this bug notification because 

[Kernel-packages] [Bug 1655122] Re: linux: 4.9.0-12.13 -proposed tracker

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the 4.9.0-12.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-phase-changed:Tuesday, 10. January 2017 21:45 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.9.0-12.13 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  derivative-trackers-created: true
  phase: Uploaded
- kernel-phase-changed:Tuesday, 10. January 2017 21:45 UTC
- kernel-phase:Uploaded

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

Title:
  linux: 4.9.0-12.13 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1655437] Re: 16.04 fails to boot with kernel 4.4.0-22-generic

[jeffrey leung]

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

Status in linux package in Ubuntu:
  New

Bug description:
  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to
  be on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards
  we found it wasn't able to boot due to some volume group issues it
  appears from the error messages.

  We fixed the driver issue on our end to target the correct inbox
  kernel version and it's working fine. We also haven't seen any issues
  with 16.04 and newer kernels. However, management is still concerned
  about the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is
  it possible to look into this issue? Or maybe would it be possible to
  get that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?

  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then
  upgrading to 4.4.0-22-generic and rebooting after install.

  1. If I install 16.04 with auto partitioning, after updating the
  kernel to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found
  errors. I’ve attached ubuntu.jpg for this.

  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.

  Thanks,
  Jeff

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

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

[Kernel-packages] [Bug 1655437] [NEW] 16.04 fails to boot with kernel 4.4.0-22-generic

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

During ENIC driver development on our end, there was a mistake and the
driver was built on the 4.4.0-22-generic kernel but we intended it to be
on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
testing the ENIC driver, it required a kernel upgrade and afterwards we
found it wasn't able to boot due to some volume group issues it appears
from the error messages.

We fixed the driver issue on our end to target the correct inbox kernel
version and it's working fine. We also haven't seen any issues with
16.04 and newer kernels. However, management is still concerned about
the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is it
possible to look into this issue? Or maybe would it be possible to get
that kernel version removed from the package so a customer doesn't
upgrade to that kernel after an offline install?

I am able to replicate the issue easily by doing an offline install of
16.04 so the kernel does not get automatically upgraded, then upgrading
to 4.4.0-22-generic and rebooting after install.

1. If I install 16.04 with auto partitioning, after updating the kernel
to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found errors.
I’ve attached ubuntu.jpg for this.

2. If I install 16.04 with manual partitioning, I don’t see the vg not
found, but OS still fails to boot and goes to shell. I’ve attached
ubuntu2.jpg for this.

Thanks,
Jeff

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


** Tags: bot-comment
-- 
16.04 fails to boot with kernel 4.4.0-22-generic
https://bugs.launchpad.net/bugs/1655437
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 1655122] Re: linux: 4.9.0-12.13 -proposed tracker

[Brad Figg]

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

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

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

Title:
  linux: 4.9.0-12.13 -proposed tracker

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

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

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

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

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  monitors not disconnected after undocking

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo X1 Carbon (4th gen) and using the Lenovo one-link+ docking 
station. The laptop is connected through the docking station to 2 external 
monitors when docked. When undocking the laptop, the laptop does not detect 
that the monitors have been disconnected (leaving X in a somewhat unworkable 
state). Even worse, when undocking with thelid closed (which would previously 
have resulted in suspend) the laptop now starts working hard and the fan starts 
spinning up (which is particularly bad when forgetting about this and placing 
the laptop in a bag). The laptop also becomes very unresponsive to X actions, 
e.g. xrandr --query takes a a couple of seconds, switching to the console takes 
> 10s. 
  This seems to be related to the following Fedora bug:
  https://bugzilla.redhat.com/show_bug.cgi?id=1392885
  which reports almost identical issues. I have not been able to try a new 
kernel yet to see if issues are fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-30-generic 4.8.0-30.32
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jschrod2726 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 10 21:28:42 2017
  HibernationDevice: RESUME=UUID=de3940cc-d877-44b6-9b33-16a8abd6701c
  InstallationDate: Installed on 2016-10-01 (101 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:5248 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FB006AMS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=a43e313c-5c49-4859-a1aa-4446f2b9c455 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET43W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FB006AMS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB006AMS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB006AMS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FB006AMS
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1655450] [NEW] monitors not disconnected after undocking

[Jochen Schroeder]

Public bug reported:

I have a Lenovo X1 Carbon (4th gen) and using the Lenovo one-link+ docking 
station. The laptop is connected through the docking station to 2 external 
monitors when docked. When undocking the laptop, the laptop does not detect 
that the monitors have been disconnected (leaving X in a somewhat unworkable 
state). Even worse, when undocking with thelid closed (which would previously 
have resulted in suspend) the laptop now starts working hard and the fan starts 
spinning up (which is particularly bad when forgetting about this and placing 
the laptop in a bag). The laptop also becomes very unresponsive to X actions, 
e.g. xrandr --query takes a a couple of seconds, switching to the console takes 
> 10s. 
This seems to be related to the following Fedora bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1392885
which reports almost identical issues. I have not been able to try a new kernel 
yet to see if issues are fixed.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-30-generic 4.8.0-30.32
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jschrod2726 F pulseaudio
CurrentDesktop: Unity
Date: Tue Jan 10 21:28:42 2017
HibernationDevice: RESUME=UUID=de3940cc-d877-44b6-9b33-16a8abd6701c
InstallationDate: Installed on 2016-10-01 (101 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:5248 IMC Networks 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FB006AMS
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=a43e313c-5c49-4859-a1aa-4446f2b9c455 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-30-generic N/A
 linux-backports-modules-4.8.0-30-generic  N/A
 linux-firmware1.161.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET43W (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FB006AMS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB006AMS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB006AMS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20FB006AMS
dmi.product.version: ThinkPad X1 Carbon 4th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug yakkety

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

Title:
  monitors not disconnected after undocking

Status in linux package in Ubuntu:
  New

Bug description:
  I have a Lenovo X1 Carbon (4th gen) and using the Lenovo one-link+ docking 
station. The laptop is connected through the docking station to 2 external 
monitors when docked. When undocking the laptop, the laptop does not detect 
that the monitors have been disconnected (leaving X in a somewhat unworkable 
state). Even worse, when undocking with thelid closed (which would previously 
have resulted in suspend) the laptop now starts working hard and the fan starts 
spinning up (which is particularly bad when forgetting about this and placing 
the laptop in a bag). The laptop also becomes very unresponsive to X actions, 
e.g. xrandr --query takes a a couple of seconds, switching to the console takes 
> 10s. 
  This seems to be related to the following Fedora bug:
  https://bugzilla.redhat.com/show_bug.cgi?id=1392885
  which reports almost identical issues. I have not been able to try a new 
kernel yet to see if issues are fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-30-generic 4.8.0-30.32
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jschrod2726 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 10 21:28:42 2017
  HibernationDevice: RESUME=UUID=de3940cc-d877-44b6-9b33-16a8abd6701c
  InstallationDate: Installed on 2016-10-01 (101 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:5248 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FB006AMS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1654282] onibi (amd64) - tests ran: 33, failed: 0

[Brad Figg]

tests ran:  33, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-59.80-lowlatency/onibi__4.4.0-59.80__2017-01-10_18-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/1654282

Title:
  linux: 4.4.0-59.80 -proposed tracker

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

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

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

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

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

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

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

[Brad Figg]

tests ran:  36, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-59.80-lowlatency/onza__4.4.0-59.80__2017-01-10_18-27-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/1654282

Title:
  linux: 4.4.0-59.80 -proposed tracker

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

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

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

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

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

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

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

[bugproxy]

--- Comment From bren...@br.ibm.com 2017-01-10 14:56 EDT---
I rebased these patches on top of Ubuntu 16.04.2 (4.8.0-32.34)

--- Comment From bren...@br.ibm.com 2017-01-10 14:58 EDT---
I rebased these patches on top of Ubuntu 16.04.2 (4.8.0-32.34)

https://github.com/leitao/ubuntu-yakkety/commits/vnic

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

Title:
  Bug fixes for IBM VNIC Driver

Status in linux package in Ubuntu:
  New

Bug description:
  In order to bring the VNIC driver up to date and pull in fixes for all
  of the bugs we have seen we would need to have the following patches
  applied.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=12608c260d2fe36746508cb4fa20b6e9a5f9c241

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=87737f8810db445db171ca81ca4cc43bd5b067ce

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=d894be57ca92c8a8819ab544d550809e8731137b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=9888d7b02c7793cbbcbdd05dd9e14cc0e78d1db7

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=8bf371e6adff29758cc3c57c17df4486513081f8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=6dbcd8fb5968fda3a5fba019dfb0c80c3139627b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=b7f193da17fb18b752bef77ce52eb49723299bd8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=e1fac0adf0f9b2c1eb49e658e6ed070a744bbaef

  I created a tree based on 16.04.2 kernel and included these commits.

  https://github.com/leitao/ubuntu-yakkety/tree/vnic

  I will be generating kernel binaries, so, we can test it.

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

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

[Kernel-packages] [Bug 1655421] Re: nouveau driver being too conservative about HDMI pixel clock, barring usage of native resolution on 4K displays over HDMI

[Frode Nordahl]

apport information

** Package changed: linux (Ubuntu) => linux-lts-xenial (Ubuntu)

** Tags added: apport-collected xenial

** Description changed:

  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993311] 
[drm:drm_add_edid_modes.part.22 [drm]] HDMI: DVI dual 0, max TMDS clock 30 
kHz
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993315] nouveau :01:00.0: 
DRM: native mode from largest: 1920x1080@60
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993342] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 69:"3840x2160" 30 297000 3840 
4016 4104 4400 2160 2168 2178 2250 0x48 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993348] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993353] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 73:"2560x1440" 60 241500 2560 
2608 2640 2720 1440 1443 1448 1481 0x40 0x9
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993358] 
[drm:drm_mode_prune_invalid [drm]] Not using 2560x1440 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993363] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 104:"3840x2160" 25 297000 
3840 4896 4984 5280 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993368] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993373] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 105:"3840x2160" 24 297000 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993378] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993383] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 106:"3840x2160" 30 296703 
3840 4016 4104 4400 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993387] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993392] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 116:"3840x2160" 24 296703 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993397] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  
  However it is perfectly valid to use higher pixel clock on some graphic
  cards.
  
  This patch will allow the end-user to adjust the pixel clock with the hdmimhz 
kernel parameter until the detection code gets good enough:
  
https://github.com/torvalds/linux/commit/1a0c96c075bb4517d4ce4fb6750ee0a3cf38714c
  
  This page contains a lot of useful information and lead me to a sollution to 
my problem:
  https://www.elstel.org/software/hunt-for-4K-UHD-2160p.html.en
  
- I think this is worthy of consideration for backport to the Xenial
- kernel as not being able to use the most recent LTS version of Ubuntu
- Desktop with current hardware is a drag.
+ I think this is worthy of consideration for backport to the Xenial kernel as 
not being able to use the most recent LTS version of Ubuntu Desktop with 
current hardware is a drag.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  frode  2797 F pulseaudio
+  /dev/snd/controlC0:  frode  2797 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=ae0b4ef2-57b4-4ab5-ac55-be113c10f1d1
+ InstallationDate: Installed on 2017-01-08 (2 days ago)
+ InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ MachineType: Apple Inc. MacBookPro10,1
+ NonfreeKernelModules: wl
+ Package: linux-image-extra-4.4.0-59-generic 4.4.0-59.80
+ PackageArchitecture: amd64
+ ProcFB:
+  0 inteldrmfb
+  1 nouveaufb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash hdmimhz=297 vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
+ 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
+ Tags:  xenial
+ Uname: Linux 4.4.0-59-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/20/2016
+ dmi.bios.vendor: Apple Inc.
+ dmi.bios.version: MBP101.88Z.00EE.B0B.1610201442
+ dmi.board.asset.tag: Base Board Asset Tag#
+ dmi.board.name: Mac-C3EC7CD22292981F
+ dmi.board.vendor: Apple Inc.
+ dmi.board.version: MacBookPro10,1
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Apple Inc.
+ dmi.chassis.version: Mac-C3EC7CD22292981F
+ dmi.modalias: 

[Kernel-packages] [Bug 1579205] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-aws has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  CONFIG_NR_CPUS=256 is too low

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

Bug description:
  Intel Knights Landing systems boot up to 272 processor cores. The
  stock Ubuntu Linux kernel images leave processor cores above 256
  disabled:

  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
256/0xeb ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
257/0xef ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
258/0xf3 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
259/0xf7 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
260/0xfb ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
261/0xff ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
262/0x103 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
263/0x107 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
264/0x10b ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
265/0x10f ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
266/0x113 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
267/0x117 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
268/0x11b ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
269/0x11f ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
270/0x123 ignored.
  [0.00] ACPI: NR_CPUS/possible_cpus limit of 256 reached.  Processor 
271/0x127 ignored.

  I'd request an increase in CONFIG_NR_CPUS to 512. This would match
  Debian's default setting. For comparison, RHEL/CentOS ship with 4096.

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

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

[Kernel-packages] [Bug 1648088] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-aws has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  linux - Memory Bandwidth Monitoring regression

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

Bug description:
  Hi team,,

  I have a customer, who tried to install Xenial or upgrade to 4.4 kernel with 
Trusty on our cloud platform(qemu 1.5.3), reports a defect. he complains that 
only  one cpu is successfully detected, other cpus is disabled if
  he used 4.4 kernel. I tried to bisect Xenial kernel tree, and found that this 
bug was introduced by the following commit.

  commit 31c2013e4ea2e594522980acc3d20e88664b19f1
  Author: Thomas Gleixner 
  Date:   Mon Feb 22 22:19:15 2016 +

  x86/topology: Create logical package id

  BugLink: http://bugs.launchpad.net/bugs/1397880

  For per package oriented services we must be able to rely on the number 
of CPU
  packages to be within bounds. Create a tracking facility, which

  - calculates the number of possible packages depending on
  nr_cpu_ids after boot

  - makes sure that the package id is within the number of possible 
packages. If
the apic id is outside we map it to a logical package id if there is 
enough
space available.

  Provide interfaces for drivers to query the mapping and do translations 
from
  physcial to logical ids.

  and then I backported 7b0501b1e7cddd32b265178e32d332bdfbb532d4 from
  Linus tree to Xenial kernel, the issue goes away, so could we consider
  to backport it to xenial kernel tree to solve this issue in next
  release?

  From 7b0501b1e7cddd32b265178e32d332bdfbb532d4 Mon Sep 17 00:00:00 2001
  From: Jiri Olsa 
  Date: Mon, 15 Aug 2016 12:17:00 +0200
  Subject: [PATCH] x86/smp: Fix __max_logical_packages value setup

  Frank reported kernel panic when he disabled several cores in BIOS
  via following option:

  Thanks
  Wei

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

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

[Kernel-packages] [Bug 1647887] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-aws has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  NVMe driver accidentally reverted to use GSI instead of MSIX

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

Bug description:
  [Impact]

  These commit ids are in the xenial kernel branch.

  Commit 90c9712fbb388077b5e53069cae43f1acbb0102a ("NVMe: Always use MSI/MSI-x
  interrupts") changed the NVMe driver to always use MSI/MSI-x interrupts.
  However, later commit 30d6592fce71beabe18460252c3823747c4742f6 ("NVMe: Don't
  unmap controller registers on reset") as well as commit
  e9820e415895bdd9cfd21f87e80e3e0a10f131f0 ("UBUNTU: (fix) NVMe: Don't unmap
  controller registers on reset") accidentally reverted part of the original
  commit, which reverted the NVMe   driver to using GSI interrupts instead 
of
  always using MSI/MSI-x interrupts.

  The original commit was added because GSI interrupts do not always
  work for NVMe on all systems, while MSI/MSIX interrupts do work.  The
  accidental reversion of the code to use MSI/MSIX causes the NVMe
  driver to not work on some systems with NVMe drives.

  [Test Case]

  On a system with NVMe drive(s) that do not work (because the NVMe
  driver is using the non-working GSI interrupt, instead of MSI/MSIX
  interrupt), test the current xenial kernel, and some or all of the
  NVMe drives will fail to initialize.  Then test with the fixed kernel,
  and all the NVMe drives will initialize.

  [Regression Potential]

  If MSI/MSIX interrupts do not work with NVMe drives on some systems,
  this change would break those systems.  Those systems would also be
  broken by the upstream kernel, however; additionally, without MSI/MSIX
  support, such NVMe controllers would be significantly slower due to
  reliance on a single GSI for notification of completion of all I/O.
  So it's very unlikely there are any systems with NVMe controllers that
  do not support MSI/MSI-x.

  [Other Info]

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

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

[Kernel-packages] [Bug 1648449] Update Released

[Adam Conrad]

The verification of the Stable Release Update for linux-aws has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  NVMe drives in Amazon AWS instance fail to initialize

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

Bug description:
  [Impact]

  On an Amazon AWS instance that has NVMe drives, the NVMe drives fail
  to initialize, and so aren't usable by the system.  If one of the NVMe
  drives contains the root filesystem, the instance won't boot.

  [Test Case]

  Boot an AWS instance with a NVMe drive.  It will fail to initialize
  the NVMe drive(s), and errors will appear in the system log (if the
  system boots at all).  With a patched kernel, all NVMe drives are
  initialized and enumerated and work properly.

  [Regression Potential]

  Patching the NVMe driver may cause problems on other systems using
  NVMe drives.

  [Other Info]

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

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

[Kernel-packages] [Bug 1655065] Re: Regression: Suspend broken on Thinkpad P50 with 4.8.0-32-generic

[Guillaume Martres]

The bug does not appear in 4.10-rc3

** Tags added: kernel-fixed-upstream

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

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

Title:
  Regression: Suspend broken on Thinkpad P50 with 4.8.0-32-generic

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

Bug description:
  Suspending to ram and to disk works perfectly fine on the
  4.8.0-30-generic kernel. On 4.8.0-32-generic it works some of the
  time, but most of the time it freezes the machine. When the machine is
  frozen the screen is turned off, the power button light is on, but the
  machine does not respond to any input including the Magic SysRq keys,
  the only thing that can be done is powering off the machine by
  pressing the power button for 10 seconds. This happens both with
  suspend-to-ram and suspend-to-disk.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-32-generic 4.8.0-32.34
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  smarter1803 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Jan  9 16:42:48 2017
  HibernationDevice: RESUME=UUID=a1a154db-3fbe-43e4-92d1-987022206599
  InstallationDate: Installed on 2012-09-28 (1563 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120928)
  MachineType: LENOVO 20ENCTO1WW
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-32-generic 
root=UUID=bf5c18a6-40c4-4768-82bc-5c47a1324be5 ro ipv6.disable=1 
i915.enable_psr=0
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-32-generic N/A
   linux-backports-modules-4.8.0-32-generic  N/A
   linux-firmware1.161.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-04-15 (269 days ago)
  dmi.bios.date: 08/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET57W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ENCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET57W(1.30):bd08/03/2016:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20ENCTO1WW
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1655421

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  nouveau driver being too conservative about HDMI pixel clock, barring
  usage of native resolution on 4K displays over HDMI

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993311] 
[drm:drm_add_edid_modes.part.22 [drm]] HDMI: DVI dual 0, max TMDS clock 30 
kHz
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993315] nouveau :01:00.0: 
DRM: native mode from largest: 1920x1080@60
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993342] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 69:"3840x2160" 30 297000 3840 
4016 4104 4400 2160 2168 2178 2250 0x48 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993348] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993353] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 73:"2560x1440" 60 241500 2560 
2608 2640 2720 1440 1443 1448 1481 0x40 0x9
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993358] 
[drm:drm_mode_prune_invalid [drm]] Not using 2560x1440 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993363] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 104:"3840x2160" 25 297000 
3840 4896 4984 5280 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993368] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993373] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 105:"3840x2160" 24 297000 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993378] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993383] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 106:"3840x2160" 30 296703 
3840 4016 4104 4400 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993387] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993392] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 116:"3840x2160" 24 296703 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993397] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH

  However it is perfectly valid to use higher pixel clock on some
  graphic cards.

  This patch will allow the end-user to adjust the pixel clock with the hdmimhz 
kernel parameter until the detection code gets good enough:
  
https://github.com/torvalds/linux/commit/1a0c96c075bb4517d4ce4fb6750ee0a3cf38714c

  This page contains a lot of useful information and lead me to a sollution to 
my problem:
  https://www.elstel.org/software/hunt-for-4K-UHD-2160p.html.en

  I think this is worthy of consideration for backport to the Xenial
  kernel as not being able to use the most recent LTS version of Ubuntu
  Desktop with current hardware is a drag.

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

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

[Kernel-packages] [Bug 1655421] Re: nouveau driver being too conservative about HDMI pixel clock, barring usage of native resolution on 4K displays over HDMI

[Frode Nordahl]

In my case setting hdmimhz=297 did the trick.

Hardware:
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 650M 
Mac Edition] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition]
Flags: bus master, fast devsel, latency 0, IRQ 35
Memory at c000 (32-bit, non-prefetchable) [size=16M]
Memory at 9000 (64-bit, prefetchable) [size=256M]
Memory at a000 (64-bit, prefetchable) [size=32M]
I/O ports at 2000 [size=128]
Expansion ROM at c100 [disabled] [size=512K]
Capabilities: 
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau

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

Title:
  nouveau driver being too conservative about HDMI pixel clock, barring
  usage of native resolution on 4K displays over HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993311] 
[drm:drm_add_edid_modes.part.22 [drm]] HDMI: DVI dual 0, max TMDS clock 30 
kHz
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993315] nouveau :01:00.0: 
DRM: native mode from largest: 1920x1080@60
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993342] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 69:"3840x2160" 30 297000 3840 
4016 4104 4400 2160 2168 2178 2250 0x48 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993348] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993353] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 73:"2560x1440" 60 241500 2560 
2608 2640 2720 1440 1443 1448 1481 0x40 0x9
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993358] 
[drm:drm_mode_prune_invalid [drm]] Not using 2560x1440 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993363] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 104:"3840x2160" 25 297000 
3840 4896 4984 5280 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993368] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993373] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 105:"3840x2160" 24 297000 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993378] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993383] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 106:"3840x2160" 30 296703 
3840 4016 4104 4400 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993387] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993392] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 116:"3840x2160" 24 296703 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993397] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH

  However it is perfectly valid to use higher pixel clock on some
  graphic cards.

  This patch will allow the end-user to adjust the pixel clock with the hdmimhz 
kernel parameter until the detection code gets good enough:
  
https://github.com/torvalds/linux/commit/1a0c96c075bb4517d4ce4fb6750ee0a3cf38714c

  This page contains a lot of useful information and lead me to a sollution to 
my problem:
  https://www.elstel.org/software/hunt-for-4K-UHD-2160p.html.en

  I think this is worthy of consideration for backport to the Xenial
  kernel as not being able to use the most recent LTS version of Ubuntu
  Desktop with current hardware is a drag.

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

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

[Kernel-packages] [Bug 1655421] [NEW] nouveau driver being too conservative about HDMI pixel clock, barring usage of native resolution on 4K displays over HDMI

[Frode Nordahl]

Public bug reported:

Jan 10 18:56:03 frode-MacBookPro kernel: [4.993311] 
[drm:drm_add_edid_modes.part.22 [drm]] HDMI: DVI dual 0, max TMDS clock 30 
kHz
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993315] nouveau :01:00.0: 
DRM: native mode from largest: 1920x1080@60
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993342] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 69:"3840x2160" 30 297000 3840 
4016 4104 4400 2160 2168 2178 2250 0x48 0x5
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993348] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993353] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 73:"2560x1440" 60 241500 2560 
2608 2640 2720 1440 1443 1448 1481 0x40 0x9
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993358] 
[drm:drm_mode_prune_invalid [drm]] Not using 2560x1440 mode: CLOCK_HIGH
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993363] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 104:"3840x2160" 25 297000 
3840 4896 4984 5280 2160 2168 2178 2250 0x40 0x5
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993368] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993373] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 105:"3840x2160" 24 297000 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993378] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993383] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 106:"3840x2160" 30 296703 
3840 4016 4104 4400 2160 2168 2178 2250 0x40 0x5
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993387] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993392] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 116:"3840x2160" 24 296703 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
Jan 10 18:56:03 frode-MacBookPro kernel: [4.993397] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH

However it is perfectly valid to use higher pixel clock on some graphic
cards.

This patch will allow the end-user to adjust the pixel clock with the hdmimhz 
kernel parameter until the detection code gets good enough:
https://github.com/torvalds/linux/commit/1a0c96c075bb4517d4ce4fb6750ee0a3cf38714c

This page contains a lot of useful information and lead me to a sollution to my 
problem:
https://www.elstel.org/software/hunt-for-4K-UHD-2160p.html.en

I think this is worthy of consideration for backport to the Xenial
kernel as not being able to use the most recent LTS version of Ubuntu
Desktop with current hardware is a drag.

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

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

Title:
  nouveau driver being too conservative about HDMI pixel clock, barring
  usage of native resolution on 4K displays over HDMI

Status in linux package in Ubuntu:
  New

Bug description:
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993311] 
[drm:drm_add_edid_modes.part.22 [drm]] HDMI: DVI dual 0, max TMDS clock 30 
kHz
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993315] nouveau :01:00.0: 
DRM: native mode from largest: 1920x1080@60
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993342] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 69:"3840x2160" 30 297000 3840 
4016 4104 4400 2160 2168 2178 2250 0x48 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993348] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993353] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 73:"2560x1440" 60 241500 2560 
2608 2640 2720 1440 1443 1448 1481 0x40 0x9
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993358] 
[drm:drm_mode_prune_invalid [drm]] Not using 2560x1440 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993363] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 104:"3840x2160" 25 297000 
3840 4896 4984 5280 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993368] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993373] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 105:"3840x2160" 24 297000 
3840 5116 5204 5500 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993378] 
[drm:drm_mode_prune_invalid [drm]] Not using 3840x2160 mode: CLOCK_HIGH
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993383] 
[drm:drm_mode_debug_printmodeline [drm]] Modeline 106:"3840x2160" 30 296703 
3840 4016 4104 4400 2160 2168 2178 2250 0x40 0x5
  Jan 10 18:56:03 frode-MacBookPro kernel: [4.993387] 

[Kernel-packages] [Bug 1650054] Re: Dell Precision 5520 & 3520 freezes at login screent

[Alex Hung]

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

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

Title:
  Dell Precision 5520 & 3520 freezes at login screent

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

Bug description:
  When Precision 5520 & 3520 run on iGPU (Intel video only) mode, they
  hang at login screen, i.e. bbswitch tries to turn off the dGPU

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

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

[Kernel-packages] [Bug 1655420] [NEW] Ubuntu - ibmveth: abnormally large TCP MSS value caused a TCP session to hang with a zero window

[bugproxy]

Public bug reported:

== Comment: #0 - THOMAS L. FALCON - 2017-01-10 11:54:24 ==

This bug is being mirrored for any distributions that include ibmveth
large send/receive support.  In short, any distribution with ibmveth
v1.05 will be affected (releases 14.04.5/Wily+)

2 upstream commits:

1. Set GSO size and type
https://github.com/torvalds/linux/commit/7b5967389f5a8dfb9d32843830f5e2717e20995d
2. set GSO segments
https://github.com/torvalds/linux/commit/94acf164dc8f1184e8d0737be7125134c2701dbe

A VIOS fix is needed as well.

---Problem Description---
When ibmveth interface on a PowerVM logical partition received a large, 
aggregated packet from firmware, the gso fields in the socket buffer shared 
info were not filled in correctly.  This surfaced in a bug where the TCP rx 
window calculation algorithm returned a Zero Window even when there was 
available space.

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


** Tags: architecture-ppc64le bugnameltc-150410 severity-critical 
targetmilestone-inin---

** Tags added: architecture-ppc64le bugnameltc-150410 severity-critical
targetmilestone-inin---

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

Title:
  Ubuntu - ibmveth: abnormally large TCP MSS value caused a TCP session
  to hang with a zero window

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - THOMAS L. FALCON - 2017-01-10 11:54:24 ==

  This bug is being mirrored for any distributions that include ibmveth
  large send/receive support.  In short, any distribution with ibmveth
  v1.05 will be affected (releases 14.04.5/Wily+)

  2 upstream commits:

  1. Set GSO size and type
  
https://github.com/torvalds/linux/commit/7b5967389f5a8dfb9d32843830f5e2717e20995d
  2. set GSO segments
  
https://github.com/torvalds/linux/commit/94acf164dc8f1184e8d0737be7125134c2701dbe

  A VIOS fix is needed as well.

  ---Problem Description---
  When ibmveth interface on a PowerVM logical partition received a large, 
aggregated packet from firmware, the gso fields in the socket buffer shared 
info were not filled in correctly.  This surfaced in a bug where the TCP rx 
window calculation algorithm returned a Zero Window even when there was 
available space.

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

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

[Kernel-packages] [Bug 644898] Re: required kernel toshiba support not enabled

[Bug Watch Updater]

** Changed in: toshset (Debian)
   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/644898

Title:
  required kernel toshiba support not enabled

Status in linux package in Ubuntu:
  Confirmed
Status in toshset package in Ubuntu:
  Confirmed
Status in toshset package in Debian:
  Fix Released

Bug description:
  Binary package hint: toshset

  The kernel support required to use these utilities isn't installed - I
  can't use extra buttons, hotkeys, or change screen brightness.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: toshset 1.75-2
  ProcVersionSignature: Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic i686
  Architecture: i386
  CheckboxSubmission: 8b15f4fca5292e90a3327d5e528e925e
  CheckboxSystem: 988b7c9be54a1e2525cae7d97805a134
  Date: Wed Sep 22 01:13:08 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_CA.utf8
   SHELL=/bin/bash
  SourcePackage: toshset

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

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

[Kernel-packages] [Bug 1655420] [NEW] Ubuntu - ibmveth: abnormally large TCP MSS value caused a TCP session to hang with a zero window

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - THOMAS L. FALCON - 2017-01-10 11:54:24 ==

This bug is being mirrored for any distributions that include ibmveth
large send/receive support.  In short, any distribution with ibmveth
v1.05 will be affected (releases 14.04.5/Wily+)

2 upstream commits:

1. Set GSO size and type
https://github.com/torvalds/linux/commit/7b5967389f5a8dfb9d32843830f5e2717e20995d
2. set GSO segments
https://github.com/torvalds/linux/commit/94acf164dc8f1184e8d0737be7125134c2701dbe

A VIOS fix is needed as well.

---Problem Description---
When ibmveth interface on a PowerVM logical partition received a large, 
aggregated packet from firmware, the gso fields in the socket buffer shared 
info were not filled in correctly.  This surfaced in a bug where the TCP rx 
window calculation algorithm returned a Zero Window even when there was 
available space.

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


** Tags: architecture-ppc64le bugnameltc-150410 severity-critical 
targetmilestone-inin---
-- 
Ubuntu - ibmveth: abnormally large TCP MSS value caused a TCP session to hang 
with a zero window
https://bugs.launchpad.net/bugs/1655420
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 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[bugproxy]

--- Comment From cha...@us.ibm.com 2017-01-10 12:59 EDT---
Assigning to Hari for some assistance but would like to know if this issue can 
be recreated consistently and if so how and does this occur on other LPARs 
running the same level?

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

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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

[Kernel-packages] [Bug 1654282] onibi (i386) - tests ran: 4, failed: 0

[Brad Figg]

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-59.80-lowlatency/onibi__4.4.0-59.80__2017-01-10_16-39-00/results-index.html

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

Title:
  linux: 4.4.0-59.80 -proposed tracker

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

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

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

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

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

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

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

[Brad Figg]

tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-59.80-lowlatency/onza__4.4.0-59.80__2017-01-10_16-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/1654282

Title:
  linux: 4.4.0-59.80 -proposed tracker

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

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

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

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

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

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

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1655411

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Cannot enable VC4 graphics driver on RPi 3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It seems the VC4 device tree overlay is not applied by the Rpi
  firmware.

  I tried adding dtoverlay=vc4-kms-v3d and adding a corresponding
  .../overlays/vc4-kms-v3d.dtbo file but it seems the Rpi bootloader
  does not apply the overlay at all.

  I merged vc4-kms-v3d.dtbo into bcm2710-rpi-3-b.dtb using a dtmerge utility 
compiled by pulling pieces from (https://github.com/raspberrypi/userland and 
https://github.com/dgibson/dtc)
  The result is here: https://github.com/albaguirre/dtmerge

  With this new device tree binary blob, The VC4 driver (as a module)
  loads (and you can see /dev/dri/ entries)

  I also played around with the tip of u-boot tree
  (git://git.denx.de/u-boot.git) which has support to apply device tree
  overlays - it applied fine and VC4 is at least recognized but the
  driver cannot initialize properly.

  Any idea on what magic incantation is needed for the RPi loaders
  (start.elf etc) to apply the vc4 overlay?

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

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

[Kernel-packages] [Bug 1560482] Re: perf: 24x7: Eliminate domain name suffix in event names

[Luis Henriques]

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

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

Title:
  perf: 24x7: Eliminate domain name suffix in event names

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

Bug description:
  Events in the 24x7 counters can belong to different domains like
  core, chip, virtual CPU home core, etc. To monitor an event, the
  user must specify the required parameters for the event, which
  include its name, the chip/core on which to monitor the event
  as well as the domain.

  Currently the event is specified to the perf tool as:

  'hv_24x7/HPM_0THRD_NON_IDLE_CCYC__PHYS_CORE,core=1/' \

  where the event name is 'HPM_0THRD_NON_IDLE_CCYC', the suffix
  '__PHYS_CORE' specifies the domain, and 'core=1' specifies the 
  core. This is inconsistent in that one parameter is specified
  as a suffix and the other in a parameter=value format.

  To simplify the usage, we can eliminate the suffix and let the 
  user specify the domain also in the param=value format. While
  the domain indices are "well known" or nearly fixed in value,
  we could display the domain indices in sysfs as a reference for 
  the users:

  $ cat /sys/bus/event_source/devices/hv_24x7/interface/domains
  1: Physical Chip
  2: Physical Core
  3: VCPU Home Core
  4: VCPU Home Chip
  5: VCPU Home Node
  6: VCPU Remote Node

  Using these the perf event can now be identified as

  hv_24x7/HPM_0THRD_NON_IDLE_CCYC,domain=2,core=1

  . This feature is implemented by the following commits which have now
  been merged into mainline:

  d34171e: powerpc/perf/hv-24x7: Display domain indices in sysfs
  8f69dc7: powerpc/perf/24x7: Eliminate domain suffix in event names

  == Comment: #1 - Sukadev Bhattiprolu  - 2016-03-21 15:26:33 
==
  Following two upstream commits are also related 24x7 and could
  be included in this feature:

  e5a5886: powerpc/perf/hv-24x7: Fix usage with chip events.
  2b206ee: powerpc/perf/hv-24x7: Display change in counter values

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

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

[Kernel-packages] [Bug 1634129] Re: Couldn't emulate instruction 0x7813427c

[Luis Henriques]

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

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

Title:
  Couldn't emulate instruction 0x7813427c

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

Bug description:
  Couldn't emulate instruction 0x7813427c
  ---

  Cannot boot nested VMs in Xenial or Yakkety w/ kvm accel.
  It worked until Vivid (in spite of not being possible in x86)
  TCG mode works fine, but very slow.

  TCG full emulation is the mode in the x86 world for nested virt.
  However, in Power, we've been using in OpenStack CI w/ kvm accel
  (native virtualization) to speed up 2nd level VMs. It worked until
  Vivid.

  Is the case that kvm accel isn't possible anymore for nested virt
  (aligned with x86 KVM) ? So full emulation TCG mode is the only
  possible mode in newer kernels ?

  qemu-system-ppc64le -machine pseries,accel=kvm,usb=off -m 1G -enable-
  kvm -cpu POWER8E -display none -nographic cirros-d161007-ppc64le-
  disk.img

  lsmod |grep kvm
  kvm_pr 96452  1
  kvm   152984  4 kvm_pr

  
  Nested VM console:

  OF stdout device is: /vdevice/vty@7100
  Preparing to boot Linux version 4.4.0-28-generic (buildd@bos01-ppc64el-018) 
(gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #47-Ubuntu SMP Fri 
Jun 24 10:09:20 UTC 2016 (Ubuntu 4.4.0-28.47-generic 4.4.13)
  Detected machine type: 0101
  Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  command line: BOOT_IMAGE=/boot/vmlinux-4.4.0-28-generic LABEL=cirros-rootfs ro
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0421
alloc_top: 1000
alloc_top_hi : 4000
rmo_top  : 1000
ram_top  : 4000
  found display   : /pci@8002000/vga@0, opening... done
  instantiating rtas at 0x0daf... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x0422 -> 0x04220aa9
  Device tree struct  0x0423 -> 0x0424
  Quiescing Open Firmware ...
  Booting Linux via __start() ?

  


  /var/log/syslog & /var/log/kern.log

  Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.186975] 
kvmppc_handle_exit_pr: emulation at 700 failed (7813427c)
  Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187023] Couldn't emulate 
instruction 0x7813427c (op 30 xop 318)
  Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187066] 
kvmppc_handle_exit_pr: emulation at 700 failed (7813427c)
  Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187113] Couldn't emulate 
instruction 0x7813427c (op 30 xop 318)
  Oct 13 14:07:38 patricia-ub16-10 kernel: [64072.187156] 
kvmppc_handle_exit_pr: emulation at 700 failed (7813427c)

  

  Host:
  cpu   : POWER8E (raw), altivec supported
  clock : 3690.00MHz
  revision  : 2.1 (pvr 004b 0201)

  timebase  : 51200
  platform  : PowerNV
  model : 8247-22L
  machine   : PowerNV 8247-22L
  firmware  : OPAL v3

  
  Guest: Xenial or Yakkety
  Description: Ubuntu 16.10
  Release: 16.10
  Codename: yakkety

  Nested VM:
  CirrOS
  
http://download.cirros-cloud.net/daily/20161007/cirros-d161007-ppc64le-disk.img

  
  This seems to be related
  https://patchwork.kernel.org/patch/9121881/

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

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

[Kernel-packages] [Bug 1655411] [NEW] Cannot enable VC4 graphics driver on RPi 3

[Alberto Aguirre]

Public bug reported:

It seems the VC4 device tree overlay is not applied by the Rpi firmware.

I tried adding dtoverlay=vc4-kms-v3d and adding a corresponding
.../overlays/vc4-kms-v3d.dtbo file but it seems the Rpi bootloader does
not apply the overlay at all.

I merged vc4-kms-v3d.dtbo into bcm2710-rpi-3-b.dtb using a dtmerge utility 
compiled by pulling pieces from (https://github.com/raspberrypi/userland and 
https://github.com/dgibson/dtc)
The result is here: https://github.com/albaguirre/dtmerge

With this new device tree binary blob, The VC4 driver (as a module)
loads (and you can see /dev/dri/ entries)

I also played around with the tip of u-boot tree
(git://git.denx.de/u-boot.git) which has support to apply device tree
overlays - it applied fine and VC4 is at least recognized but the driver
cannot initialize properly.

Any idea on what magic incantation is needed for the RPi loaders
(start.elf etc) to apply the vc4 overlay?

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

** Description changed:

  It seems the VC4 device tree overlay is not applied by the Rpi firmware.
  
  I tried adding dtoverlay=vc4-kms-v3d and adding a corresponding
  .../overlays/vc4-kms-v3d.dtbo file but it seems the Rpi bootloader does
  not apply the overlay at all.
  
  I merged vc4-kms-v3d.dtbo into bcm2710-rpi-3-b.dtb using a dtmerge utility 
compiled by pulling pieces from (https://github.com/raspberrypi/userland and 
https://github.com/dgibson/dtc)
  The result is here: https://github.com/albaguirre/dtmerge
  
  With this new device tree binary blob, The VC4 driver (as a module)
  loads .
  
  I also played around with the tip of u-boot tree
  (git://git.denx.de/u-boot.git) which has support to apply device tree
  overlays - it applied fine and VC4 is at least recognized but the driver
  cannot initialize properly.
  
  Any idea on what magic incantation is needed for the RPi loaders
- (start.elf etc) apply the vc4 overlay?
+ (start.elf etc) to apply the vc4 overlay?

** Description changed:

  It seems the VC4 device tree overlay is not applied by the Rpi firmware.
  
  I tried adding dtoverlay=vc4-kms-v3d and adding a corresponding
  .../overlays/vc4-kms-v3d.dtbo file but it seems the Rpi bootloader does
  not apply the overlay at all.
  
  I merged vc4-kms-v3d.dtbo into bcm2710-rpi-3-b.dtb using a dtmerge utility 
compiled by pulling pieces from (https://github.com/raspberrypi/userland and 
https://github.com/dgibson/dtc)
  The result is here: https://github.com/albaguirre/dtmerge
  
  With this new device tree binary blob, The VC4 driver (as a module)
- loads .
+ loads (and you can see /dev/dri/ entries)
  
  I also played around with the tip of u-boot tree
  (git://git.denx.de/u-boot.git) which has support to apply device tree
  overlays - it applied fine and VC4 is at least recognized but the driver
  cannot initialize properly.
  
  Any idea on what magic incantation is needed for the RPi loaders
  (start.elf etc) to apply the vc4 overlay?

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

Title:
  Cannot enable VC4 graphics driver on RPi 3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It seems the VC4 device tree overlay is not applied by the Rpi
  firmware.

  I tried adding dtoverlay=vc4-kms-v3d and adding a corresponding
  .../overlays/vc4-kms-v3d.dtbo file but it seems the Rpi bootloader
  does not apply the overlay at all.

  I merged vc4-kms-v3d.dtbo into bcm2710-rpi-3-b.dtb using a dtmerge utility 
compiled by pulling pieces from (https://github.com/raspberrypi/userland and 
https://github.com/dgibson/dtc)
  The result is here: https://github.com/albaguirre/dtmerge

  With this new device tree binary blob, The VC4 driver (as a module)
  loads (and you can see /dev/dri/ entries)

  I also played around with the tip of u-boot tree
  (git://git.denx.de/u-boot.git) which has support to apply device tree
  overlays - it applied fine and VC4 is at least recognized but the
  driver cannot initialize properly.

  Any idea on what magic incantation is needed for the RPi loaders
  (start.elf etc) to apply the vc4 overlay?

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

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

[Kernel-packages] [Bug 1355096] Re: Ralink RT3290 [1814:3298] missing bluetooth support with 12.04.5(kernel 3.13)

[sravanth baratam]

lsusb:
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 05c8:0361 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) SunplusIT INC. HP Truevision HD Webcam
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

uname -a:
Linux sravanth-HP-Pavilion-15-Notebook-PC 4.4.0-57-generic #78-Ubuntu SMP Fri 
Dec 9 23:50:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

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

lscpi -nn:
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core 
processor PCI Express Root Port [8086:0151] (rev 09)
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0166] (rev 09)
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04)
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset 
Family High Definition Audio Controller [8086:1e20] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 1 [8086:1e10] (rev c4)
00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 2 [8086:1e12] (rev c4)
00:1c.2 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 3 [8086:1e14] (rev c4)
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation HM76 Express Chipset LPC 
Controller [8086:1e59] (rev 04)
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 
6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family 
SMBus Controller [8086:1e22] (rev 04)
01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun 
XT [Radeon HD 8670A/8670M/8690M / R5 M330] [1002:6660] (rev ff)
07:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
07:00.1 Bluetooth [0d11]: Ralink corp. RT3290 Bluetooth [1814:3298]
08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 07)

rfkill list:
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

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

Title:
  Ralink RT3290 [1814:3298] missing bluetooth support with
  12.04.5(kernel 3.13)

Status in HWE Next:
  Won't Fix
Status in linux-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Look into the spec, the ralink rt3290 should have bluetooth supported,
  https://wikidevi.com/files/Ralink/RT3290%20product%20brief.pdf

  System with fresh 12.04.5 installed does not detect the bluetooth
  correctly.

  rfkill failed to show the bluetooth device:
  ubuntu@201209-11786:~/$ rfkill list all
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  
  However lspci does listed bluetooth device:
  ubuntu@201209-11786:~/$ lspci -v|grep -i RT3290
  02:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
  02:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 05:37:32 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1355096] Re: Ralink RT3290 [1814:3298] missing bluetooth support with 12.04.5(kernel 3.13)

[sravanth baratam]

wts wrong in my hp pavilian 15

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

Title:
  Ralink RT3290 [1814:3298] missing bluetooth support with
  12.04.5(kernel 3.13)

Status in HWE Next:
  Won't Fix
Status in linux-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Look into the spec, the ralink rt3290 should have bluetooth supported,
  https://wikidevi.com/files/Ralink/RT3290%20product%20brief.pdf

  System with fresh 12.04.5 installed does not detect the bluetooth
  correctly.

  rfkill failed to show the bluetooth device:
  ubuntu@201209-11786:~/$ rfkill list all
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  
  However lspci does listed bluetooth device:
  ubuntu@201209-11786:~/$ lspci -v|grep -i RT3290
  02:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
  02:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 05:37:32 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1355096] Re: Ralink RT3290 [1814:3298] missing bluetooth support with 12.04.5(kernel 3.13)

[sravanth baratam]

bluetooth not working

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

Title:
  Ralink RT3290 [1814:3298] missing bluetooth support with
  12.04.5(kernel 3.13)

Status in HWE Next:
  Won't Fix
Status in linux-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Look into the spec, the ralink rt3290 should have bluetooth supported,
  https://wikidevi.com/files/Ralink/RT3290%20product%20brief.pdf

  System with fresh 12.04.5 installed does not detect the bluetooth
  correctly.

  rfkill failed to show the bluetooth device:
  ubuntu@201209-11786:~/$ rfkill list all
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  
  However lspci does listed bluetooth device:
  ubuntu@201209-11786:~/$ lspci -v|grep -i RT3290
  02:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
  02:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: 
boot/vmlinuz-3.13.0-32-generic]
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Mon Aug 11 05:37:32 2014
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[Cesar Herrera]

I finally have paired the E4.5 to Citroen C4. A call starts but it's
impossible to hear anything.

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

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

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

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1655356

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering 

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

[bugproxy]

--- Comment From bren...@br.ibm.com 2017-01-10 12:23 EDT---
I just found that patch d894be57ca92c8a8819ab544d550809e8731137b is not 
required, since it depends on a52ad514fdf3b8a57ca4322c92d2d8d5c6182485, and 
a52ad514fdf3b8a57ca4322c92d2d8d5c6182485 is not in 4.8 tree.

Thus, not adding d894be57ca92c8a8819ab544d550809e8731137b

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

Title:
  Bug fixes for IBM VNIC Driver

Status in linux package in Ubuntu:
  New

Bug description:
  In order to bring the VNIC driver up to date and pull in fixes for all
  of the bugs we have seen we would need to have the following patches
  applied.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=12608c260d2fe36746508cb4fa20b6e9a5f9c241

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=87737f8810db445db171ca81ca4cc43bd5b067ce

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=d894be57ca92c8a8819ab544d550809e8731137b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=9888d7b02c7793cbbcbdd05dd9e14cc0e78d1db7

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=8bf371e6adff29758cc3c57c17df4486513081f8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=6dbcd8fb5968fda3a5fba019dfb0c80c3139627b

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=b7f193da17fb18b752bef77ce52eb49723299bd8

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/ibm/ibmvnic.c?h=v4.10-rc3=e1fac0adf0f9b2c1eb49e658e6ed070a744bbaef

  I created a tree based on 16.04.2 kernel and included these commits.

  https://github.com/leitao/ubuntu-yakkety/tree/vnic

  I will be generating kernel binaries, so, we can test it.

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

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

[Kernel-packages] [Bug 1551712] Re: Belkin Thunderbolt 2 Express Dock HD display port hot plug not supported.

[dunk]

** Attachment added: "lspci_boot_with_thunderbolt_then_reseat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551712/+attachment/4802407/+files/lspci_boot_with_thunderbolt_then_reseat

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

Title:
  Belkin Thunderbolt 2 Express Dock HD display port hot plug not
  supported.

Status in linux package in Ubuntu:
  Invalid

Bug description:
  There are two problems when using this dock:

  1. When booted, connecting the dock only allows USB and Ethernet to work, it 
does not support HDMI or DisplayPort monitors
  2. When booted with the device connected, while the device works fine, 
reseating the dock causes no adapters to work (No USB, Ethernet, HDMI and 
DisplayPort)

  This makes this dock and other Thunderbolt docks unusable, because I
  can't hotplug it correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-30-generic 4.2.0-30.36
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  graingert   1560 F pulseaudio
   /dev/snd/controlC0:  graingert   1560 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  1 12:42:39 2016
  InstallationDate: Installed on 2016-01-05 (55 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=665d68d7-0c44-48e6-9e4c-9496a5c21d21 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,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/1551712/+subscriptions

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

[Kernel-packages] [Bug 1551712] Re: Belkin Thunderbolt 2 Express Dock HD display port hot plug not supported.

[dunk]

** Attachment added: "lsmod_boot_with_thunderbolt_then_reseat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551712/+attachment/4802408/+files/lsmod_boot_with_thunderbolt_then_reseat

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

Title:
  Belkin Thunderbolt 2 Express Dock HD display port hot plug not
  supported.

Status in linux package in Ubuntu:
  Invalid

Bug description:
  There are two problems when using this dock:

  1. When booted, connecting the dock only allows USB and Ethernet to work, it 
does not support HDMI or DisplayPort monitors
  2. When booted with the device connected, while the device works fine, 
reseating the dock causes no adapters to work (No USB, Ethernet, HDMI and 
DisplayPort)

  This makes this dock and other Thunderbolt docks unusable, because I
  can't hotplug it correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-30-generic 4.2.0-30.36
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  graingert   1560 F pulseaudio
   /dev/snd/controlC0:  graingert   1560 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  1 12:42:39 2016
  InstallationDate: Installed on 2016-01-05 (55 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=665d68d7-0c44-48e6-9e4c-9496a5c21d21 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,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/1551712/+subscriptions

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

[Kernel-packages] [Bug 1551712] Re: Belkin Thunderbolt 2 Express Dock HD display port hot plug not supported.

[dunk]

Same symptoms with 4.10.0-041000rc3-generic

I've attaches a copy of syslog which records the system booting with the
Thunderbolt attached, then being removed and re-inserted.

Search for the annotations in the syslog file: 
syslog_boot_with_thunderbolt_then_reseat:
"Removing Thunderbolt"
"Replacing Thunderbolt"
"Done with Thunderbolt"

duncan@relapse:~$ uname -a
Linux relapse 4.10.0-041000rc3-generic #201701081831 SMP Sun Jan 8 23:33:02 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

** Attachment added: "syslog_boot_with_thunderbolt_then_reseat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551712/+attachment/4802406/+files/syslog_boot_with_thunderbolt_then_reseat

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

Title:
  Belkin Thunderbolt 2 Express Dock HD display port hot plug not
  supported.

Status in linux package in Ubuntu:
  Invalid

Bug description:
  There are two problems when using this dock:

  1. When booted, connecting the dock only allows USB and Ethernet to work, it 
does not support HDMI or DisplayPort monitors
  2. When booted with the device connected, while the device works fine, 
reseating the dock causes no adapters to work (No USB, Ethernet, HDMI and 
DisplayPort)

  This makes this dock and other Thunderbolt docks unusable, because I
  can't hotplug it correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-30-generic 4.2.0-30.36
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  graingert   1560 F pulseaudio
   /dev/snd/controlC0:  graingert   1560 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  1 12:42:39 2016
  InstallationDate: Installed on 2016-01-05 (55 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=665d68d7-0c44-48e6-9e4c-9496a5c21d21 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B15.1510261437
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,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/1551712/+subscriptions

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

[Kernel-packages] [Bug 1655356] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

[Brian Murray]

** Tags added: yakkety

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50];
  oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

Status in linux package in Ubuntu:
  New

Bug description:
  I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was
  running Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this
  problem started with errors, OOM and an eventual kernel panic. It can
  run fine for about 3-4 hours or so. I see the following errors on
  syslog (also attached w/ other logs and information I can gather).

  Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [kswapd0:50]
  Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]
  Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 22s! [kswapd0:50]
  Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup 
- CPU#1 stuck for 23s! [kswapd0:50]

  Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
  Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
  Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked 
oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, 
oom_score_adj=0
  Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0

  
  Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
  Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
  Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
  Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
  Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
  Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
  Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
  Jan  9 07:36:53 gorilla kernel: [69325.386696] perf: interrupt took too long 
(7723 > 7712), lowering kernel.perf_event_max_sample_rate to 

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

[Brad Figg]

tests ran:  36, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-59.80-generic/dwalin__4.4.0-59.80__2017-01-10_15-13-00/results-index.html

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

Title:
  linux: 4.4.0-59.80 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1654708] Re: Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with identifier from /mnt/disk/by-id/xxxx

[Launchpad Bug Tracker]

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

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

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

Title:
  Trying to reinstall ZFS on Xenial. Cannot mount existing zpool with
  identifier from /mnt/disk/by-id/

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  zfs-dkms 0.6.5.6-0ubuntu15

  I cant mount/install my zpool. so i tried reinstalling zfslinux-utils,
  which gives me three error messages like this: "zfs-mount.service is a
  disabled" or a static unit, not starting it."...

  If something doesn't work I try googling error messages. most answers
  not totally like my problem but related to dkms, so I tried loading
  zfs-dkms and reinstalling zfslinux-utils.

  I created the zpool with id from /mnt/disk/by-id/ - which is zfs good-
  practice. This may be causing problems with the mount. I dont know...

  Cheers.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu15
  ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35
  Uname: Linux 4.4.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-58-generic
  Date: Sat Jan  7 15:58:15 2017
  DuplicateSignature: 
dkms:zfs-dkms:0.6.5.6-0ubuntu15:/var/lib/dkms/zfs/0.6.5.6/build/module/zfs/zpl_xattr.c:1284:12:
 error: too few arguments to function ‘posix_acl_valid’
  InstallationDate: Installed on 2016-12-26 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161225)
  PackageVersion: 0.6.5.6-0ubuntu15
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu15: zfs kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1655356] [NEW] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:50]; oom-killer; and eventual kernel panic on 16.10 (upgrade from 16.04)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have a Dell (PowerEdge T110/0V52N7, BIOS 1.6.4 03/02/2011) was running
Ubuntu 16.04 for a while. Ever since I upgraded to 16.10, this problem
started with errors, OOM and an eventual kernel panic. It can run fine
for about 3-4 hours or so. I see the following errors on syslog (also
attached w/ other logs and information I can gather).

Jan  9 07:36:32 gorilla kernel: [69304.099302] NMI watchdog: BUG: soft lockup - 
CPU#1 stuck for 22s! [kswapd0:50]
Jan  9 07:37:00 gorilla kernel: [69332.119587] NMI watchdog: BUG: soft lockup - 
CPU#1 stuck for 22s! [kswapd0:50]
Jan  9 07:37:33 gorilla kernel: [69364.114705] NMI watchdog: BUG: soft lockup - 
CPU#3 stuck for 22s! [kswapd0:50]
Jan  9 07:38:01 gorilla kernel: [69392.127352] NMI watchdog: BUG: soft lockup - 
CPU#3 stuck for 22s! [kswapd0:50]
Jan  9 07:38:37 gorilla kernel: [69428.134132] NMI watchdog: BUG: soft lockup - 
CPU#3 stuck for 22s! [kswapd0:50]
Jan  9 07:39:45 gorilla kernel: [69496.112694] NMI watchdog: BUG: soft lockup - 
CPU#1 stuck for 23s! [kswapd0:50]
Jan  9 07:40:13 gorilla kernel: [69524.112050] NMI watchdog: BUG: soft lockup - 
CPU#1 stuck for 22s! [kswapd0:50]
Jan  9 07:40:49 gorilla kernel: [69560.104511] NMI watchdog: BUG: soft lockup - 
CPU#1 stuck for 22s! [kswapd0:50]
Jan  9 07:41:17 gorilla kernel: [69588.107302] NMI watchdog: BUG: soft lockup - 
CPU#1 stuck for 22s! [kswapd0:50]
Jan  9 07:41:45 gorilla kernel: [69616.104843] NMI watchdog: BUG: soft lockup - 
CPU#1 stuck for 23s! [kswapd0:50]

Jan  8 11:52:27 gorilla kernel: [ 2852.818471] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
Jan  9 07:38:56 gorilla kernel: [69448.096571] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
Jan  9 07:39:46 gorilla kernel: [69497.705922] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
Jan  9 07:40:50 gorilla kernel: [69561.956773] sh invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
Jan  9 07:41:10 gorilla kernel: [69582.329364] rsync invoked oom-killer: 
gfp_mask=0x26000d0(GFP_TEMPORARY|__GFP_NOTRACK), order=0, oom_score_adj=0
Jan  9 07:42:40 gorilla kernel: [69672.181041] sessionclean invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
Jan  9 07:42:41 gorilla kernel: [69673.298714] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
Jan  9 07:42:59 gorilla kernel: [69691.320169] apache2 invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
Jan  9 07:43:03 gorilla kernel: [69694.769140] sessionclean invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0
Jan  9 07:43:20 gorilla kernel: [69712.255535] kthreadd invoked oom-killer: 
gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=1, oom_score_adj=0


Jan  8 11:46:11 gorilla kernel: [ 2476.342532] perf: interrupt took too long 
(2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
Jan  8 11:49:04 gorilla kernel: [ 2650.045417] perf: interrupt took too long 
(3147 > 3140), lowering kernel.perf_event_max_sample_rate to 63500
Jan  8 11:49:56 gorilla kernel: [ 2701.973751] perf: interrupt took too long 
(3982 > 3933), lowering kernel.perf_event_max_sample_rate to 5
Jan  8 11:51:47 gorilla kernel: [ 2812.208307] perf: interrupt took too long 
(4980 > 4977), lowering kernel.perf_event_max_sample_rate to 4
Jan  8 13:56:06 gorilla kernel: [ 5678.539070] perf: interrupt took too long 
(2513 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
Jan  8 15:59:49 gorilla kernel: [13101.158417] perf: interrupt took too long 
(3148 > 3141), lowering kernel.perf_event_max_sample_rate to 63500
Jan  9 02:15:54 gorilla kernel: [50065.939132] perf: interrupt took too long 
(3942 > 3935), lowering kernel.perf_event_max_sample_rate to 50500
Jan  9 07:35:30 gorilla kernel: [69241.742219] perf: interrupt took too long 
(4932 > 4927), lowering kernel.perf_event_max_sample_rate to 40500
Jan  9 07:35:54 gorilla kernel: [69265.928531] perf: interrupt took too long 
(6170 > 6165), lowering kernel.perf_event_max_sample_rate to 32250
Jan  9 07:36:53 gorilla kernel: [69325.386696] perf: interrupt took too long 
(7723 > 7712), lowering kernel.perf_event_max_sample_rate to 25750


Just to make sure if this is not memory related, I ran memtest for 12 passes 
over night and found no errors on memory. Removed the external backup drives to 
isolate the problem. Checked similar issues on lanchpad.net but most of them 
are related to video driver and power supply.

Appreciate help.

Thanks
-Arul

Attachments:


syslog
uname.txt
swaps.txt
dmesg.txt
df.txt
lspci.txt
lsusb.txt
meminfo.txt
cpuinfo.txt

** Affects: linux (Ubuntu)
 

[Kernel-packages] [Bug 1413363] Re: bluetooth speaker and suspension issue

[Mathieu Trudel-Lapierre]

No, it's not widely broken. Some things are broken on some hardware, and
it's not all broken in the same way, that's why I asked for logs -- so
we can know what the actual issue is.

I don't have all the hardware in the world, so I can't reproduce these
issues myself.

Dave, if you're still having this issue, could you include the logs as
per comment #3?

Why (recibe-distraction), if you think you're seeing this issue on x86,
you're actually seeing a different bug. Please file your own bug report,
and send me the bug number so I can have a look, but it's most
definitely not the "same issue", as this bug here is specific to the
bluetooth stack on the Ubuntu Phone.

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

Title:
  bluetooth speaker and suspension issue

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Open settings bluetooth
  2. Turn on your blue tooth speaker
  3. Pair the speaker
  4. Open the music app
  5. Play music
  6. Pause the music
  7. Let the phone suspend
  8. After a while it goes into deep sleep and the speaker disconnects
  9. Wake the phone press the play button

  EXPECTED:
  I expected the music to play out of the bluetooth speaker

  ACTUAL:
  A long pause, then a click then the music plays from the internal speaker.  
You can no longer get the music to play  from the bluetooth speaker.

  Things I've tried:
  Reboot the phone re connect to the bt speaker music still plays from the loud 
speaker on the phone.
  Turned off the speaker, restarted it still plays through the Loud speaker on 
the phone

  WORK AROUND:
  Forget the connection. Re pair the device now press play now it works as 
expected.

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

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

[Kernel-packages] [Bug 1649326] Re: EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13 series)

[Rod Smith]

Joseph, any more kernels for me to test? It's been a while.

Also, I ran across bug #1603476, which reports a failure with kernel
3.13.0-92 that might (or might not) be related to this.

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

Title:
  EFI stub loader broken in kernel 3.13.0-101-generic (& later in 3.13
  series)

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

Bug description:
  The EFI stub loader produces consistent boot errors when booting
  Trusty starting with version 3.13.0-101-generic. This bug can be
  reproduced in many ways (using efibootmgr, an EFI shell, rEFInd,
  etc.). One approach is:

  1) Install an EFI shell on the computer and set it as the default boot
 option using efibootmgr.
  2) Copy the kernel and initrd files from /boot to /boot/efi.
  3) Rename the kernel file to use a .efi filename extension.
  4) Reboot into the EFI shell.
  5) Try to launch the kernel with a command like:
 fs0:\vmlinuz-3.13.0-104-generic.efi ro root=/dev/sda2 
initrd=\initrd.img-3.13.0-104-generic

  The result will be a hung or crashed system. (In VirtualBox, in which
  I've tested this, the VM produces a "guru meditation" and the session
  terminates.)

  I myself have tested only with the 3.13.0-104 kernel; however, reports
  from others indicate that the problem began with the 3.13.0-101
  kernel. See this Kubuntu forum thread for details:

  https://www.kubuntuforums.net/showthread.php?71204-Cannot-load-latest-
  kernels

  Note that early on, this thread focuses on rEFInd; however, the bug
  can be reproduced with other boot managers, including the EFI shell,
  as described in the preceding procedure, so I do not believe this is a
  rEFInd bug. rEFInd relies on the EFI stub loader to boot a Linux
  kernel, and I believe it's this component that's failing. The problem
  does NOT occur when using GRUB to launch the kernel. (GRUB does not
  rely on the EFI stub loader.)

  I have NOT encountered the problem with Xenial and its 4.4.0-series kernels 
(last tested: 4.4.0-53-generic) or Yakkety and its 4.8.0-series kernels (last 
tested: 4.8.0-30-generic). I have not yet tested Trusty with kernels from 
series beyond 3.13.0.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   1675 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=561add6d-844e-4428-8378-d92bb112d0fc
  InstallationDate: Installed on 2014-04-27 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-106-generic 
root=UUID=78ff568b-2c22-4b31-9e0c-72703dca4460 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-106-generic N/A
   linux-backports-modules-3.13.0-106-generic  N/A
   linux-firmware  1.127.22
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-106-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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