[Kernel-packages] [Bug 1686299] Re: Cannot get past login after update to 4.4.0.75-generic

[Kai-Heng Feng]

Sounds like maintainer scripts in Nvidia need some tweaks.

** Also affects: nvidia-graphics-drivers-375 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: 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/1686299

Title:
  Cannot get past login after update to 4.4.0.75-generic

Status in nvidia-graphics-drivers-375 package in Ubuntu:
  New

Bug description:
  After running software update on 16.04 and rebooting, I cannot get
  past the login screen.  The screen appears the wrong resolution and
  squashed smaller than the screen with a black border.  When I login,
  it accepts the password, but after a few seconds the screen gets
  corrupted then resets back to the login screen.

  Rebooting to an older kernel fixed the issue.

  Working:
   4.4.0-72-generic

  Failed:
   4.4.0.75-generic

  I'm using nvidia 340.102

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ben2228 F pulseaudio
   /dev/snd/controlC1:  ben2228 F pulseaudio
   /dev/snd/controlC0:  ben2228 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 25 23:46:40 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a1a4d11a-a791-49f3-9542-90dbd821d0d2
  InstallationDate: Installed on 2012-04-28 (1823 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=7d577aa7-441e-43e2-b6b3-a8500fe017c9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-03-27 (30 days ago)
  dmi.bios.date: 04/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.40
  dmi.board.name: X58 Extreme
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1686299/+subscriptions

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

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

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

Title:
  APST quirk needed for Intel NVMe

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Two users reports issue on Intel NVMe [1] (comment #34, #35).

  File a new bug to let the original bug report stays on Dell & Samsung
  combination.

  [1] https://bugs.launchpad.net/bugs/1678184

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

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

[Kernel-packages] [Bug 1686592] [NEW] APST quirk needed for Intel NVMe

[Kai-Heng Feng]

Public bug reported:

Two users reports issue on Intel NVMe [1] (comment #34, #35).

File a new bug to let the original bug report stays on Dell & Samsung
combination.

[1] https://bugs.launchpad.net/bugs/1678184

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

Title:
  APST quirk needed for Intel NVMe

Status in linux package in Ubuntu:
  New

Bug description:
  Two users reports issue on Intel NVMe [1] (comment #34, #35).

  File a new bug to let the original bug report stays on Dell & Samsung
  combination.

  [1] https://bugs.launchpad.net/bugs/1678184

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

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

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[Kai-Heng Feng]

@Charlotte Manning, @sridhar basam,

I opened another report to focus on Intel NVMe, LP: #1686592.

Can you attach output of `nvme id-ctrl /dev/nvme0` to that bug report?
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/1678184

Title:
  APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1686070] Re: linux: 4.8.0-51.54 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux: 4.8.0-51.54 -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:
  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:
  In Progress
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
Status in linux source package in Yakkety:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1686299] Re: Cannot get past login after update to 4.4.0.75-generic

[Ben Langmuir]

Okay I was able to fix this.  I tried updating to nvidia-375 in case
that was the issue, and during the install I noticed it was compiling
something with clang instead of gcc.  After that I was getting the same
behaviour from both 4.4.0-72 and 4.4.0-75.

I think what happened was:
1. I did update-alternatives to switch cc/c++ to clang
2. I updated my kernel, which rebuilt part of nvidia's driver with clang
3. Broken.

I fixed it by doing:
1. apt-get-purge nvidia-*
2. update-alternatives back to gcc
3. re-install nvidia-375

I'm now using nvidia-375 with kernel 4.4.0-75.

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

Title:
  Cannot get past login after update to 4.4.0.75-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After running software update on 16.04 and rebooting, I cannot get
  past the login screen.  The screen appears the wrong resolution and
  squashed smaller than the screen with a black border.  When I login,
  it accepts the password, but after a few seconds the screen gets
  corrupted then resets back to the login screen.

  Rebooting to an older kernel fixed the issue.

  Working:
   4.4.0-72-generic

  Failed:
   4.4.0.75-generic

  I'm using nvidia 340.102

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ben2228 F pulseaudio
   /dev/snd/controlC1:  ben2228 F pulseaudio
   /dev/snd/controlC0:  ben2228 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 25 23:46:40 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a1a4d11a-a791-49f3-9542-90dbd821d0d2
  InstallationDate: Installed on 2012-04-28 (1823 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=7d577aa7-441e-43e2-b6b3-a8500fe017c9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-03-27 (30 days ago)
  dmi.bios.date: 04/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.40
  dmi.board.name: X58 Extreme
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[NancyHsu]

The link which you provide in comment #37, we can not find the link to
download "amd64 build of linux 4.4.0-20.36 in ubuntu xenial RELEASE".

We try 17.04 kernel, the bug still not fixed.

Could you help to reproduce the bug with PXE server on your side?
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/1646277

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

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

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

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

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

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

[Kernel-packages] [Bug 1686305] Re: Merlin SGMII fail on Ubuntu Xenial HWE kernel

[Thang Nguyen]

Hi Joseph,
Can you help recompile the images for AARCH64 instead of X86_64? The Merlin 
board is using ARM64 CPU, not X86_64.

Thanks for your help,
Thang Q. Nguyen -

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

Title:
  Merlin SGMII fail on Ubuntu Xenial HWE kernel

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

Bug description:
  Using the Ubuntu Xenial HWE installation image at 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial-updates/main/installer-arm64/current/images/hwe-netboot
 to install Ubuntu into the Merlin board, the SGMII port is fail to get IP from 
DHCP.
  After installation, booting into Linux prompt, the SGMII port is fail to get 
IP from DHCP also. Checking with ethtool, the link is always report down.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 11  2016 seq
   crw-rw 1 root audio 116, 33 Feb 11  2016 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2aa90b24-e14e-4854-b52b-b853388a3466
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Merlin Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=8e10d908-38aa-4cb4-990c-4a9bcabc51a4 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-49-generic N/A
   linux-backports-modules-4.8.0-49-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-49-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: Oct 17 2016
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.06.25
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Merlin Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.06.25:bdOct172016:svnAppliedMicro:pnX-GeneMerlinBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMerlinBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Merlin Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 11  2016 seq
   crw-rw 1 root audio 116, 33 Feb 11  2016 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2aa90b24-e14e-4854-b52b-b853388a3466
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Merlin Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=8e10d908-38aa-4cb4-990c-4a9bcabc51a4 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-49-generic N/A
   linux-backports-modules-4.8.0-49-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-49-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: Oct 17 2016
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.06.25
  dmi.board.asset.tag: 

[Kernel-packages] [Bug 1685865] Re: Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-logind

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
da2ba564a6dcf46df4f828624ff55531ff11d5b0

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

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-
  logind

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Used distribution:

  Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7

  After logging in to the gnome login screen, the system freezes. Trying to 
login using the shell (Ctr+Alt+F1) also freezes the system. The following 
ouptut appears on the shell repeatedly:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-logind:913]

  Steps to reproduce the problem:
  Boot Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7 and try to login after boot.

  Further testing results:
  Using Mainline Kernel Version 4.11.0-rc6, login works fine
  Using Kernel Version 4.10.11, login works fine
  Using Kernel Version 4.10.12, the issue is present

  ==> It might be possible the issue has been introduced in a commit in
  4.11.0-rc7 and has been backported to 4.10.12.

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

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

[Kernel-packages] [Bug 1686040] Re: linux: 4.4.0-77.98 -proposed tracker

[Steve Beattie]

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

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

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

Title:
  linux: 4.4.0-77.98 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1667160] Re: Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2

[Markus Birth]

4.8.0-1035 seems to fix the problem. (Didn't check -1034.) Thank you!

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

Title:
  Kernel panic when using rtlwifi since 4.8.0-1025 on RasPi 2

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  I have a Raspberry Pi 2 running Ubuntu 16.10 without problems. I use
  wicd to let it connect to my WiFi with a RTL8188CUS USB dongle. And
  there's a RTL2838 DVB-T USB stick attached to monitor airplane
  positions for Flightradar24.

  After updateing the kernel from 4.8.0-1024, which runs flawlessly, to
  -1025, there's a kernel panic happening 10-20 seconds after booting up
  to the login prompt. I thought the -1026 fixed that, but it's still no
  worky. The trace is scrolling so fast I can't read anything but the
  last page:

  [<808c76c8>] (sock_sendmsg) from...
  [<808c7778>] (sock_write_iter) from...
  [<802c39c8>] (new_sync_write) from...
  [<802c3a4c>] (__vfs_write) from...
  [<802c48d8>] (vfs_write) from...
  [<802c5ab4>] (SyS_write) from...
  Code: e5922004 e0033002 e353 0a0a (e5902034)
  ---[ end trace 0f53d17efe0c6ba ]---
  Kernel panic - not syncing: Fatal exception in interrupt
  CPU2: stopping
  CPU: 2 PID: 21 Comm: migration/2 Tainted: G  D  4.8.0-1026-raspi2 
#29-Ubuntu
  Hardware name: BCM2709
  [<801120ac>] (unwind_backtrace) from ...
  [<8010d2dc>] (show_stack) from ...
  [<8059c38c>] (handle_IPI) from ...
  [<80101564>] (bcm2836_arm_irqchip_handle_irq) from [<80a49f3c>] 
(__irq_svc+0x5c/0x7c)
  Exception stack(0xbb99de68 to 0xbb99deb0)
  de60:    0004  0001 bac05de0 0001
  de80: bac05dcc  a00e0013  bac05d6c bb99dedc bb99dee0 bb99deb8
  dea0: 801d367c 801d35f4 600e0013 
  [<80a49f3c>] (__irq_svc) from ...
  [<801d35f4>] (multi_cpu_stop) from ...
  [<801d38ec>] (cpu_stopper_thread) from ...
  [<8014b71c>] (smpboot_thread_fn) from ...
  [<80147770>] (kthread) from [<80108e28>] (ret_from_fork+0x14/0x2c)

  
  And then this block repeats with CPU3 and CPU0.

  
  Going back to 4.8.0-1024 makes everything work again.

  
  Affected packages:

  linux-image-4.8.0-1025-raspi2:armhf (4.8.0-1025.28)
  linux-image-4.8.0-1026-raspi2:armhf (4.8.0-1026.29)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 25  2016 seq
   crw-rw 1 root audio 116, 33 Jul 25  2016 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.8.0-1024-raspi2.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.10
  Lsusb:
   Bus 001 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
   Bus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 
802.11n Wireless Adapter [Realtek RTL8188CUS]
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0xecd3f749 
smsc95xx.macaddr=B8:27:EB:D3:F7:49 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3ea0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: Ubuntu 4.8.0-1024.27-raspi2 4.8.16
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-1024-raspi2 N/A
   linux-backports-modules-4.8.0-1024-raspi2  N/A
   linux-firmware 1.161.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-1024-raspi2 armv7l
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to yakkety on 2016-10-24 (122 days ago)
  UserGroups: adm audio cdrom dialout floppy fuse netdev plugdev sudo users 
video www-data
  _MarkForUpload: False

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

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

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[sridhar basam]

I am seeing this after upgrading to the 4.8.0-49 kernel on Ubuntu 16.04
with Intel 600P

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1677297] Re: [Zesty] d-i: replace msm_emac with qcom_emac

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: Timur Tabi (timur-tabi) => Manoj Iyer (manjo)

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

Title:
  [Zesty] d-i: replace msm_emac with qcom_emac

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  We landed a patch to support msm_emac module in initrd for amberwing 
platforms. But the upstream driver has since been renamed to qcom_emac. This 
module is needed in d-i's initrd so that these nics can be used to d-i install 
the system. The driver already exists in the zesty kernel under 
drivers/net/ethernet/qualcomm/emac/

  Revert commit 14893d91c9c391f8a4c2668b96ffe60aa728ad23 and add
  qcom_emac to initrd, and change the module name to qcom_emac.

  [Test Case]
  D-I install zesty on amberwing platform and notice that DI does not recognize 
the onboard two port nic.

  [Regression Potential]
  At present this driver applies only to amberwing systems, any regression will 
be isolated to amberwing platforms. The over all risk of regression is low.

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

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

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

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   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/1680888

Title:
  Disable CONFIG_HVC_UDBG on ppc64el

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

Bug description:
  Canonical,

  Could you please disable CONFIG_HVC_UDBG on ppc64el config?

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

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

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

[Kernel-packages] [Bug 1686519] Re: POWER9: CAPI2 enablement

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   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/1686519

Title:
  POWER9: CAPI2 enablement

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Breno Henrique Leitao  - 2017-04-26 
15:08:18 ==
  Hello,

  We would like to include CAPI2  support on the CXL device driver on
  Zesty kernel.

   The coherent accelerator interface is designed to allow the coherent
  connection of accelerators (FPGAs and other devices) to a  POWER
  system. These devices need to adhere to the Coherent Accelerator
  Interface Architecture (CAIA).

  
This PSL Version 9 provides new features such as:
  * Interaction with the nest MMU on the P9 chip.
  * Native DMA support.
  * Supports sending ASB_Notify messages for host thread wakeup.
  * Supports Atomic operations.

  == Comment: #3 - Breno Henrique Leitao  - 2017-04-26 
15:21:25 ==
  These are the patches we need:

  f24be42aab37c6d07c05126673138e06223a6399 cxl: Add psl9 specific code
  d7b1946c7925a270062b2e0718aa57b42ba619c0 cxl: Force psl data-cache flush 
during device shutdown
  abd1d99bb3da42d6c7341c14986f5b8f4dcc6bd5 cxl: Isolate few psl8 specific calls
  64663f372c72cedeba1b1dc86df9cc159ae5a93d cxl: Rename some psl8 specific 
functions
  bdd2e7150644fee4de7167a3e08294ef32eeda11 cxl: Update implementation service 
layer
  6dd2d23403396d8e6d153a6c9db56e1a1012bad8 cxl: Keep track of mm struct 
associated with a context
  66ef20c7834b7df18168b12a57ef01c6ae0d1a81 cxl: Remove unused values in 
bare-metal environment.
  aba81433b50350fde68bf80fe9f75d671e15b5ae cxl: Read vsec perst load image
  39d40871526627fd0e2cfc1e2fb88500a5049c4c cxl: Fix build when CONFIG_DEBUG_FS=n

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

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

[Kernel-packages] [Bug 1686040] Re: linux: 4.4.0-77.98 -proposed tracker

[Brad Figg]

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

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

Title:
  linux: 4.4.0-77.98 -proposed tracker

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

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

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

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

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

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

[Kernel-packages] [Bug 1686154] Re: linux: 3.13.0-118.165 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1686156
  derivatives:
  kernel-stable-phase-changed:Wednesday, 26. April 2017 16:32 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ boot-testing-requested: true
  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/1686154

Title:
  linux: 3.13.0-118.165 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  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
Status in linux source package in Trusty:
  New

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

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

  backports: 1686156
  derivatives:
  kernel-stable-phase-changed:Wednesday, 26. April 2017 16:32 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1685892] Re: macsec: avoid heap overflow in skb_to_sgvec

[Steve Beattie]

This issue needs a second patch applied:
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=5294b83086cc1c35b4efeca03644cf9d12282e5b

(http://www.openwall.com/lists/oss-security/2017/04/26/8)

It was assigned CVE-2017-7477 (http://www.openwall.com/lists/oss-
security/2017/04/25/7)

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-7477

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

Title:
  macsec: avoid heap overflow in skb_to_sgvec

Status in linux package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe source package in Xenial:
  New
Status in linux source package in Yakkety:
  New
Status in linux-hwe source package in Yakkety:
  Invalid
Status in linux source package in Zesty:
  New
Status in linux-hwe source package in Zesty:
  Invalid

Bug description:
  Please apply
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=4d6fa57b4dab0d77f4d8e9d9c73d1e63f6fe8fee

  (See also http://www.openwall.com/lists/oss-security/2017/04/24/4 )

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

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

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[Charlotte Manning]

We're seeing this after upgrading to hwe-edge kernel (4.10.0.X) from Ubuntu 
16.04,
so far three machines:
Intel Skull Canyon NUC6i7KYK  with Intel SSDPEKKF512G nvme

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1684010] Re: 17.04, i915 freeze on VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

[Traumflug]

Kernel 4.10.0.19 from the regular 17.04 repo appears to work fine,
working for some 12 hours now. It's slightly different than the one
@Vaclav Rehak reported above as not working:

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

If there are more kernels I can try for bisecting I'll happily do 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/1684010

Title:
  17.04, i915 freeze on VGA compatible controller: Intel Corporation
  Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just freezes all unity and/or X.
  Nothing in any logs though.

  16.10 worked just fine.

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

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

Re: [Kernel-packages] [Bug 1686511] Status changed to Confirmed

[mark roberts]

What's it mean is it a security risk like a virus?

Thank you

M

On Wed, Apr 26, 2017 at 4:30 PM, Brad Figg 
wrote:

> This change was made by a bot.
>
> ** Changed in: linux (Ubuntu)
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1686511
>
> Title:
>   [Dell Inc. Inspiron 15 7000 Gaming] suspend/resume failure
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   IDk whats going on it asked me if I would report this i said ok
>
>   M
>
>   ProblemType: KernelOops
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-3.13.0-117-generic 3.13.0-117.164
>   ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39
>   Uname: Linux 3.13.0-117-generic x86_64
>   Annotation: This occured during a previous suspend and prevented it from
> resuming properly.
>   ApportVersion: 2.13.3-0ubuntu1
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CurrentDmesg:
>[   16.049163] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>[   32.937953] audit_printk_skb: 153 callbacks suppressed
>[   32.937956] type=1400 audit(1493237227.046:62): apparmor="STATUS"
> operation="profile_replace" profile="unconfined"
> name="/usr/lib/cups/backend/cups-pdf" pid=2042 comm="apparmor_parser"
>[   32.937960] type=1400 audit(1493237227.046:63): apparmor="STATUS"
> operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd"
> pid=2042 comm="apparmor_parser"
>[   32.938246] type=1400 audit(1493237227.046:64): apparmor="STATUS"
> operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd"
> pid=2042 comm="apparmor_parser"
>   Date: Wed Apr 26 16:06:36 2017
>   ExecutablePath: /usr/share/apport/apportcheckresume
>   Failure: suspend/resume
>   HibernationDevice: RESUME=UUID=1e5f6c8a-5793-4263-a9f4-5471b921e117
>   InstallationDate: Installed on 2017-04-26 (0 days ago)
>   InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
>   InterpreterPath: /usr/bin/python3.4
>   IwConfig:
>eth0  no wireless extensions.
>
>lono wireless extensions.
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 002: ID 8087:0a2a Intel Corp.
>Bus 001 Device 003: ID 0c45:6a06 Microdia
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: Dell Inc. Inspiron 15 7000 Gaming
>   ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
>   ProcEnviron:
>TERM=linux
>PATH=(custom, no user)
>   ProcFB: 0 EFI VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-117-generic.efi.signed
> root=UUID=68816c25-6dae-40e3-810c-8e66d4213b95 ro quiet splash
> vt.handoff=7
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-3.13.0-117-generic N/A
>linux-backports-modules-3.13.0-117-generic  N/A
>linux-firmware  1.126
>   RfKill:
>0: hci0: Bluetooth
> Soft blocked: no
> Hard blocked: no
>   SourcePackage: linux
>   Title: [Dell Inc. Inspiron 15 7000 Gaming] suspend/resume failure
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   dmi.bios.date: 01/10/2017
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 01.00.03
>   dmi.board.name: 0MK77P
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: X02
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: dmi:bvnDellInc.:bvr01.00.03:bd01/10/2017:svnDellInc.:
> pnInspiron157000Gaming:pvr:rvnDellInc.:rn0MK77P:rvrX02:
> cvnDellInc.:ct10:cvr:
>   dmi.product.name: Inspiron 15 7000 Gaming
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1686511/+subscriptions
>

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

Title:
  [Dell Inc. Inspiron 15 7000 Gaming] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  IDk whats going on it asked me if I would report this i said ok

  M

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-117-generic 3.13.0-117.164
  ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-117-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [   16.049163] IPv6: 

[Kernel-packages] [Bug 1685865] Re: Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-logind

[LocutusOfBorg]

thanks @jsalisbury, probably all the merges in the kernel trapped me :)

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

Title:
  Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-
  logind

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Used distribution:

  Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7

  After logging in to the gnome login screen, the system freezes. Trying to 
login using the shell (Ctr+Alt+F1) also freezes the system. The following 
ouptut appears on the shell repeatedly:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-logind:913]

  Steps to reproduce the problem:
  Boot Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7 and try to login after boot.

  Further testing results:
  Using Mainline Kernel Version 4.11.0-rc6, login works fine
  Using Kernel Version 4.10.11, login works fine
  Using Kernel Version 4.10.12, the issue is present

  ==> It might be possible the issue has been introduced in a commit in
  4.11.0-rc7 and has been backported to 4.10.12.

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

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

[Kernel-packages] [Bug 1686519] [NEW] POWER9: CAPI2 enablement

[bugproxy]

Public bug reported:

== Comment: #0 - Breno Henrique Leitao  - 2017-04-26 
15:08:18 ==
Hello,

We would like to include CAPI2  support on the CXL device driver on
Zesty kernel.

 The coherent accelerator interface is designed to allow the coherent
connection of accelerators (FPGAs and other devices) to a  POWER system.
These devices need to adhere to the Coherent Accelerator Interface
Architecture (CAIA).


  This PSL Version 9 provides new features such as:
* Interaction with the nest MMU on the P9 chip.
* Native DMA support.
* Supports sending ASB_Notify messages for host thread wakeup.
* Supports Atomic operations.

== Comment: #3 - Breno Henrique Leitao  - 2017-04-26 
15:21:25 ==
These are the patches we need:

f24be42aab37c6d07c05126673138e06223a6399 cxl: Add psl9 specific code
d7b1946c7925a270062b2e0718aa57b42ba619c0 cxl: Force psl data-cache flush during 
device shutdown
abd1d99bb3da42d6c7341c14986f5b8f4dcc6bd5 cxl: Isolate few psl8 specific calls
64663f372c72cedeba1b1dc86df9cc159ae5a93d cxl: Rename some psl8 specific 
functions
bdd2e7150644fee4de7167a3e08294ef32eeda11 cxl: Update implementation service 
layer
6dd2d23403396d8e6d153a6c9db56e1a1012bad8 cxl: Keep track of mm struct 
associated with a context
66ef20c7834b7df18168b12a57ef01c6ae0d1a81 cxl: Remove unused values in 
bare-metal environment.
aba81433b50350fde68bf80fe9f75d671e15b5ae cxl: Read vsec perst load image
39d40871526627fd0e2cfc1e2fb88500a5049c4c cxl: Fix build when CONFIG_DEBUG_FS=n

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


** Tags: architecture-ppc64le bugnameltc-153737 severity-medium 
targetmilestone-inin16043

** Tags added: architecture-ppc64le bugnameltc-153737 severity-medium
targetmilestone-inin16043

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

Title:
  POWER9: CAPI2 enablement

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Breno Henrique Leitao  - 2017-04-26 
15:08:18 ==
  Hello,

  We would like to include CAPI2  support on the CXL device driver on
  Zesty kernel.

   The coherent accelerator interface is designed to allow the coherent
  connection of accelerators (FPGAs and other devices) to a  POWER
  system. These devices need to adhere to the Coherent Accelerator
  Interface Architecture (CAIA).

  
This PSL Version 9 provides new features such as:
  * Interaction with the nest MMU on the P9 chip.
  * Native DMA support.
  * Supports sending ASB_Notify messages for host thread wakeup.
  * Supports Atomic operations.

  == Comment: #3 - Breno Henrique Leitao  - 2017-04-26 
15:21:25 ==
  These are the patches we need:

  f24be42aab37c6d07c05126673138e06223a6399 cxl: Add psl9 specific code
  d7b1946c7925a270062b2e0718aa57b42ba619c0 cxl: Force psl data-cache flush 
during device shutdown
  abd1d99bb3da42d6c7341c14986f5b8f4dcc6bd5 cxl: Isolate few psl8 specific calls
  64663f372c72cedeba1b1dc86df9cc159ae5a93d cxl: Rename some psl8 specific 
functions
  bdd2e7150644fee4de7167a3e08294ef32eeda11 cxl: Update implementation service 
layer
  6dd2d23403396d8e6d153a6c9db56e1a1012bad8 cxl: Keep track of mm struct 
associated with a context
  66ef20c7834b7df18168b12a57ef01c6ae0d1a81 cxl: Remove unused values in 
bare-metal environment.
  aba81433b50350fde68bf80fe9f75d671e15b5ae cxl: Read vsec perst load image
  39d40871526627fd0e2cfc1e2fb88500a5049c4c cxl: Fix build when CONFIG_DEBUG_FS=n

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

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

[Kernel-packages] [Bug 1686519] [NEW] POWER9: CAPI2 enablement

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Breno Henrique Leitao  - 2017-04-26 
15:08:18 ==
Hello,

We would like to include CAPI2  support on the CXL device driver on
Zesty kernel.

 The coherent accelerator interface is designed to allow the coherent
connection of accelerators (FPGAs and other devices) to a  POWER system.
These devices need to adhere to the Coherent Accelerator Interface
Architecture (CAIA).


  This PSL Version 9 provides new features such as:
* Interaction with the nest MMU on the P9 chip.
* Native DMA support.
* Supports sending ASB_Notify messages for host thread wakeup.
* Supports Atomic operations.

== Comment: #3 - Breno Henrique Leitao  - 2017-04-26 
15:21:25 ==
These are the patches we need:

f24be42aab37c6d07c05126673138e06223a6399 cxl: Add psl9 specific code
d7b1946c7925a270062b2e0718aa57b42ba619c0 cxl: Force psl data-cache flush during 
device shutdown
abd1d99bb3da42d6c7341c14986f5b8f4dcc6bd5 cxl: Isolate few psl8 specific calls
64663f372c72cedeba1b1dc86df9cc159ae5a93d cxl: Rename some psl8 specific 
functions
bdd2e7150644fee4de7167a3e08294ef32eeda11 cxl: Update implementation service 
layer
6dd2d23403396d8e6d153a6c9db56e1a1012bad8 cxl: Keep track of mm struct 
associated with a context
66ef20c7834b7df18168b12a57ef01c6ae0d1a81 cxl: Remove unused values in 
bare-metal environment.
aba81433b50350fde68bf80fe9f75d671e15b5ae cxl: Read vsec perst load image
39d40871526627fd0e2cfc1e2fb88500a5049c4c cxl: Fix build when CONFIG_DEBUG_FS=n

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


** Tags: architecture-ppc64le bugnameltc-153737 severity-medium 
targetmilestone-inin16043
-- 
POWER9: CAPI2 enablement
https://bugs.launchpad.net/bugs/1686519
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 1686511] 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/1686511

Title:
  [Dell Inc. Inspiron 15 7000 Gaming] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  IDk whats going on it asked me if I would report this i said ok

  M

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-117-generic 3.13.0-117.164
  ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-117-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [   16.049163] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   32.937953] audit_printk_skb: 153 callbacks suppressed
   [   32.937956] type=1400 audit(1493237227.046:62): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=2042 comm="apparmor_parser"
   [   32.937960] type=1400 audit(1493237227.046:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2042 comm="apparmor_parser"
   [   32.938246] type=1400 audit(1493237227.046:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2042 comm="apparmor_parser"
  Date: Wed Apr 26 16:06:36 2017
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=1e5f6c8a-5793-4263-a9f4-5471b921e117
  InstallationDate: Installed on 2017-04-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  InterpreterPath: /usr/bin/python3.4
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0c45:6a06 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-117-generic.efi.signed 
root=UUID=68816c25-6dae-40e3-810c-8e66d4213b95 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-117-generic N/A
   linux-backports-modules-3.13.0-117-generic  N/A
   linux-firmware  1.126
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: [Dell Inc. Inspiron 15 7000 Gaming] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.03
  dmi.board.name: 0MK77P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.03:bd01/10/2017:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0MK77P:rvrX02:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1036456] Re: [Fujitsu LIFEBOOK AH530] BUG: soft lockup - CPU#0 stuck for 22s!

[Mike Pastor]

The soft lockup bug has manifested itself in the

Linux 3.2.0-126-generic-pae

kernel just one time with opening lid resume - on

 4 18 17

I cannot, with this machine, now, troubleshoot it.

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

Title:
  [Fujitsu LIFEBOOK AH530] BUG: soft lockup - CPU#0 stuck for 22s!

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  60% of the time computer will not resume from suspend when lid is opened.
  Display begins with ACPI errors and Device PNP0C0D:00 errors and
  then a cycle of text after the "BUG: soft lockup - CPU#0 stuck for 22s!"  
error.

  Additionally,
  yelp process consumed 100% of each of the 4 processors in sequence for a long 
time after this event last occured.
  Terminal will not take administrator's password at all - the cursur won't 
move. Therefore, "sudo lspci -vnvn > lspci-vnvn.log" could not be done at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-29-generic-pae 3.2.0-29.46
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
  Uname: Linux 3.2.0-29-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lfeq   1628 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf070 irq 44'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:10ec0269,10cf0200,0014 
HDA:80862804,80860101,0010'
 Controls  : 23
 Simple ctrls  : 10
  Date: Mon Aug 13 20:28:09 2012
  HibernationDevice: RESUME=UUID=306aab40-d7f0-4c2f-95bb-bab8bcb6da07
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: FUJITSU LIFEBOOK AH530
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic-pae 
root=UUID=5e649b17-1a99-456b-bd08-ef7aec3da8c1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-29-generic-pae N/A
   linux-backports-modules-3.2.0-29-generic-pae  N/A
   linux-firmware1.79
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2010
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.16
  dmi.board.name: FJNBB06
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.16:bd08/19/2010:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK AH530
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1686511] [NEW] [Dell Inc. Inspiron 15 7000 Gaming] suspend/resume failure

[mark roberts]

Public bug reported:

IDk whats going on it asked me if I would report this i said ok

M

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-117-generic 3.13.0-117.164
ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39
Uname: Linux 3.13.0-117-generic x86_64
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
 [   16.049163] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [   32.937953] audit_printk_skb: 153 callbacks suppressed
 [   32.937956] type=1400 audit(1493237227.046:62): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=2042 comm="apparmor_parser"
 [   32.937960] type=1400 audit(1493237227.046:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2042 comm="apparmor_parser"
 [   32.938246] type=1400 audit(1493237227.046:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2042 comm="apparmor_parser"
Date: Wed Apr 26 16:06:36 2017
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=1e5f6c8a-5793-4263-a9f4-5471b921e117
InstallationDate: Installed on 2017-04-26 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
InterpreterPath: /usr/bin/python3.4
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 0c45:6a06 Microdia 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 15 7000 Gaming
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-117-generic.efi.signed 
root=UUID=68816c25-6dae-40e3-810c-8e66d4213b95 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-117-generic N/A
 linux-backports-modules-3.13.0-117-generic  N/A
 linux-firmware  1.126
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: [Dell Inc. Inspiron 15 7000 Gaming] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 01/10/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.00.03
dmi.board.name: 0MK77P
dmi.board.vendor: Dell Inc.
dmi.board.version: X02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.03:bd01/10/2017:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0MK77P:rvrX02:cvnDellInc.:ct10:cvr:
dmi.product.name: Inspiron 15 7000 Gaming
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-kerneloops resume suspend trusty

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

Title:
  [Dell Inc. Inspiron 15 7000 Gaming] suspend/resume failure

Status in linux package in Ubuntu:
  New

Bug description:
  IDk whats going on it asked me if I would report this i said ok

  M

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-117-generic 3.13.0-117.164
  ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-117-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [   16.049163] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   32.937953] audit_printk_skb: 153 callbacks suppressed
   [   32.937956] type=1400 audit(1493237227.046:62): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=2042 comm="apparmor_parser"
   [   32.937960] type=1400 audit(1493237227.046:63): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2042 comm="apparmor_parser"
   [   32.938246] type=1400 audit(1493237227.046:64): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2042 comm="apparmor_parser"
  Date: Wed Apr 26 16:06:36 2017
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  

[Kernel-packages] [Bug 1684491] Re: linux: 4.10.0-20.22 -proposed tracker

[Launchpad Bug Tracker]

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

This bug was fixed in the package linux - 4.10.0-20.22

---
linux (4.10.0-20.22) zesty; urgency=low

  * linux: 4.10.0-20.22 -proposed tracker (LP: #1684491)

  * [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move waiting for release to hv_utils_transport itself

 -- Stefan Bader   Wed, 19 Apr 2017 16:13:16
+0200

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

Title:
  linux: 4.10.0-20.22 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Confirmed
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:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

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

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

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

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

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

[Kernel-packages] [Bug 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.10.0-20.22

---
linux (4.10.0-20.22) zesty; urgency=low

  * linux: 4.10.0-20.22 -proposed tracker (LP: #1684491)

  * [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself
(LP: #1682561)
- Drivers: hv: util: move waiting for release to hv_utils_transport itself

 -- Stefan Bader   Wed, 19 Apr 2017 16:13:16
+0200

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

Title:
  [Hyper-V] hv: util: move waiting for release to hv_utils_transport
  itself

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

Bug description:
  We are observing call traces with the -73 and -74 proposed kernels
  that look like this:

  [  240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
  [  240.412299]   Not tainted 4.4.0-73-generic #94-Ubuntu
  [  240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  240.420217] kworker/14:1D 8804e6f23b68 0   179  2 
0x
  [  240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
  [  240.420236]  8804e6f23b68 000181f9 8804ed944600 
8804e6fe3800
  [  240.420241]  8804e6f24000 c0187a48 c0187a40 
8804e6fe3800
  [  240.420243]  8804ea196800 8804e6f23b80 81837845 
7fff
  [  240.420245] Call Trace:
  [  240.420254]  [] schedule+0x35/0x80
  [  240.420256]  [] schedule_timeout+0x1b5/0x270
  [  240.420260]  [] ? kfree+0x13a/0x150
  [  240.420264]  [] ? kfree_const+0x22/0x30
  [  240.420268]  [] ? kobject_release+0x94/0x190
  [  240.420270]  [] ? kobject_put+0x27/0x50
  [  240.420272]  [] wait_for_completion+0xb3/0x140
  [  240.420276]  [] ? wake_up_q+0x70/0x70
  [  240.420284]  [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
  [  240.420288]  [] util_remove+0x21/0x40 [hv_utils]
  [  240.420294]  [] vmbus_remove+0x27/0x30 [hv_vmbus]
  [  240.420301]  [] __device_release_driver+0xa1/0x150
  [  240.420303]  [] device_release_driver+0x23/0x30
  [  240.420306]  [] bus_remove_device+0x101/0x170
  [  240.420308]  [] device_del+0x139/0x270
  [  240.420310]  [] device_unregister+0x1e/0x60
  [  240.420313]  [] vmbus_device_unregister+0x1f/0x50 
[hv_vmbus]
  [  240.420316]  [] vmbus_onoffer_rescind+0x91/0xb0 
[hv_vmbus]
  [  240.420324]  [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
  [  240.420327]  [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
  [  240.420331]  [] process_one_work+0x165/0x480
  [  240.420335]  [] worker_thread+0x4b/0x4c0
  [  240.420338]  [] ? process_one_work+0x480/0x480
  [  240.420341]  [] ? process_one_work+0x480/0x480
  [  240.420345]  [] kthread+0xd8/0xf0
  [  240.420347]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  240.420350]  [] ret_from_fork+0x3f/0x70
  [  240.420352]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  317.360035] serial8250: too much work for irq3

  The following commit should fix this issue:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398

  Waiting for release_event in all three drivers introduced issues on release
  as on_reset() hook is not always called. E.g. if the device was never
  opened we will never get the completion.

  Move the waiting code to hvutil_transport_destroy() and make sure it is
  only called when the device is open. hvt->lock serialization should
  guarantee the absence of races.

  Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
  Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing 
issue")
  Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing 
issue")

  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Signed-off-by: Vitaly Kuznetsov 
  Signed-off-by: K. Y. Srinivasan 
  Signed-off-by: Greg Kroah-Hartman 

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

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

[Kernel-packages] [Bug 1684971] Re: [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain

[Joshua R. Poulson]

Succeeds.

Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-77-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

  Get cloud support with Ubuntu Advantage Cloud Guest:
http://www.ubuntu.com/business/services/cloud

0 packages can be updated.
0 updates are security updates.


Last login: Wed Apr 26 19:33:01 2017 from 167.220.1.17
jrp@jrpcudau:~$ dmesg | grep [Nn][Vv]
[0.00] BIOS-e820: [mem 0x1000-0x1fff] ACPI NVS
[0.108095] smpboot: APIC(0) Converting physical 0 to logical package 0
[0.200051] PM: Registering ACPI NVS region [mem 0x1000-0x1fff] 
(4096 bytes)
[1.150948] rtc_cmos 00:00: alarms up to one month, 114 bytes nvram
[   19.933256] sd 2:0:0:0: [storvsc] Add. Sense: Invalid command operation code
[   19.933268] sd 3:0:1:0: [storvsc] Add. Sense: Invalid command operation code
[   19.933304] sd 2:0:0:0: [storvsc] Add. Sense: Invalid command operation code
[   19.933312] sd 3:0:1:0: [storvsc] Add. Sense: Invalid command operation code
[   21.402336] nvidia: module license 'NVIDIA' taints kernel.
[   21.406984] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
[   21.411864] nvidia c4d9:00:00.0: can't derive routing for PCI INT A
[   21.411867] nvidia c4d9:00:00.0: PCI INT A: no GSI
[   21.414385] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 246
[   21.414395] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  375.51  Wed Mar 
22 10:26:12 PDT 2017 (using threaded interrupts)
[   21.530031] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
UNIX platforms  375.51  Wed Mar 22 09:00:58 PDT 2017
[   21.531290] [drm] [nvidia-drm] [GPU ID 0xc4d9] Loading driver
[   21.594837] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 
245
jrp@jrpcudau:~$ lspci
:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (AGP disabled) (rev 03)
:00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
:00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
:00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
:00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual 
VGA
c4d9:00:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
jrp@jrpcudau:~$ nvidia-smi
Wed Apr 26 19:50:27 2017
+-+
| NVIDIA-SMI 375.51 Driver Version: 375.51|
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  Tesla K80   Off  | C4D9:00:00.0 Off |0 |
| N/A   41CP060W / 149W |  0MiB / 11439MiB |  0%  Default |
+---+--+--+

+-+
| Processes:   GPU Memory |
|  GPU   PID  Type  Process name   Usage  |
|=|
|  No running processes found |
+-+

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

Title:
  [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain

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

Bug description:
  The following patch fixes a problem with "[PATCH] pci-hyperv: Use
  device serial number as PCI domain" where some drivers were expecting
  a u16 instead of a u32 for PCI device serial numbers, as observed by
  Oops and hangs in Azure on NC and NV GPU instances.

  From: Haiyang Zhang 

  This patch uses the lower 16 bits of the serial number as PCI
  domain, otherwise some drivers may not be able to handle it.

  Signed-off-by: Haiyang Zhang 
  ---
   drivers/pci/host/pci-hyperv.c |4 +++-
   1 files changed, 3 insertions(+), 1 deletions(-)

  diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyperv.c
  index e73880c..b18dff3 100644
  --- a/drivers/pci/host/pci-hyperv.c
  +++ 

[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED

[xenus]

Tried the kernel above, unfortunately dkms fails trying to add nvidia module so 
I can't get it running.
Attaching dkms log.

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

Title:
  failed command: READ FPDMA QUEUED

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  occurs intermittently usually when under load, causes the system to
  hang for a while, needs a reboot which then normally fixes the file
  system errors.

  Seems same symptoms and error message as bug 550559 but in a current
  kernel.

  I have a Seagate SSHD drive as ata5.

  Trying the libata.force=noncq kernel param to see if the hangs and
  errors go away.

  Drive passes SMART self test.

  RElevant part of kern.log:

  
  Apr 14 16:52:01 mark-linux kernel: [14294.691801] ata5.00: exception Emask 
0x0 SAct 0x8000 SErr 0x0 action 0x6
  Apr 14 16:52:01 mark-linux kernel: [14294.691814] ata5.00: irq_stat 0x4008
  Apr 14 16:52:01 mark-linux kernel: [14294.691823] ata5.00: failed command: 
READ FPDMA QUEUED
  Apr 14 16:52:01 mark-linux kernel: [14294.691839] ata5.00: cmd 
60/08:78:77:46:25/00:00:62:00:00/40 tag 15 ncq dma 4096 in
  Apr 14 16:52:01 mark-linux kernel: [14294.691839]  res 
41/84:08:78:46:25/00:00:62:00:00/00 Emask 0x410 (ATA bus error) 
  Apr 14 16:52:01 mark-linux kernel: [14294.691847] ata5.00: status: { DRDY ERR 
}
  Apr 14 16:52:01 mark-linux kernel: [14294.691853] ata5.00: error: { ICRC ABRT 
}
  Apr 14 16:52:01 mark-linux kernel: [14294.691863] ata5: hard resetting link
  Apr 14 16:52:01 mark-linux kernel: [14295.167467] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  Apr 14 16:52:02 mark-linux kernel: [14295.244272] ata5.00: configured for 
UDMA/133
  Apr 14 16:52:02 mark-linux kernel: [14295.244286] ata5: EH complete
  Apr 14 18:02:06 mark-linux kernel: [18500.172587] ata5.00: exception Emask 
0x0 SAct 0x7fff SErr 0x0 action 0x6 frozen
  Apr 14 18:02:06 mark-linux kernel: [18500.172601] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172617] ata5.00: cmd 
61/c8:00:17:0c:c0/00:00:5a:00:00/40 tag 0 ncq dma 102400 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172617]  res 
40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172625] ata5.00: status: { DRDY }
  Apr 14 18:02:06 mark-linux kernel: [18500.172631] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172643] ata5.00: cmd 
61/a0:08:af:39:c7/01:00:5a:00:00/40 tag 1 ncq dma 212992 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172643]  res 
40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172650] ata5.00: status: { DRDY }
  Apr 14 18:02:06 mark-linux kernel: [18500.172655] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172667] ata5.00: cmd 
61/30:10:6f:17:f2/00:00:5b:00:00/40 tag 2 ncq dma 24576 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172667]  res 
40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172673] ata5.00: status: { DRDY }
  Apr 14 18:02:06 mark-linux kernel: [18500.172678] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172689] ata5.00: cmd 
61/18:18:67:a4:25/00:00:62:00:00/40 tag 3 ncq dma 12288 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172689]  res 
40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172696] ata5.00: status: { DRDY }
  Apr 14 18:02:06 mark-linux kernel: [18500.172701] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172712] ata5.00: cmd 
61/20:20:b7:b7:25/00:00:62:00:00/40 tag 4 ncq dma 16384 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172712]  res 
40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172719] ata5.00: status: { DRDY }
  Apr 14 18:02:06 mark-linux kernel: [18500.172723] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172735] ata5.00: cmd 
61/30:28:5f:d6:25/00:00:62:00:00/40 tag 5 ncq dma 24576 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172735]  res 
40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172741] ata5.00: status: { DRDY }
  Apr 14 18:02:06 mark-linux kernel: [18500.172746] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172758] ata5.00: cmd 
61/08:30:17:8a:92/00:00:49:00:00/40 tag 6 ncq dma 4096 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172758]  res 
40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172764] ata5.00: status: { DRDY }
  Apr 14 18:02:06 

[Kernel-packages] [Bug 1682892] Re: failed command: READ FPDMA QUEUED

[xenus]

** Attachment added: "dkms log for kerel 3.11 and nvidia 378"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682892/+attachment/4868342/+files/make.log

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

Title:
  failed command: READ FPDMA QUEUED

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  occurs intermittently usually when under load, causes the system to
  hang for a while, needs a reboot which then normally fixes the file
  system errors.

  Seems same symptoms and error message as bug 550559 but in a current
  kernel.

  I have a Seagate SSHD drive as ata5.

  Trying the libata.force=noncq kernel param to see if the hangs and
  errors go away.

  Drive passes SMART self test.

  RElevant part of kern.log:

  
  Apr 14 16:52:01 mark-linux kernel: [14294.691801] ata5.00: exception Emask 
0x0 SAct 0x8000 SErr 0x0 action 0x6
  Apr 14 16:52:01 mark-linux kernel: [14294.691814] ata5.00: irq_stat 0x4008
  Apr 14 16:52:01 mark-linux kernel: [14294.691823] ata5.00: failed command: 
READ FPDMA QUEUED
  Apr 14 16:52:01 mark-linux kernel: [14294.691839] ata5.00: cmd 
60/08:78:77:46:25/00:00:62:00:00/40 tag 15 ncq dma 4096 in
  Apr 14 16:52:01 mark-linux kernel: [14294.691839]  res 
41/84:08:78:46:25/00:00:62:00:00/00 Emask 0x410 (ATA bus error) 
  Apr 14 16:52:01 mark-linux kernel: [14294.691847] ata5.00: status: { DRDY ERR 
}
  Apr 14 16:52:01 mark-linux kernel: [14294.691853] ata5.00: error: { ICRC ABRT 
}
  Apr 14 16:52:01 mark-linux kernel: [14294.691863] ata5: hard resetting link
  Apr 14 16:52:01 mark-linux kernel: [14295.167467] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  Apr 14 16:52:02 mark-linux kernel: [14295.244272] ata5.00: configured for 
UDMA/133
  Apr 14 16:52:02 mark-linux kernel: [14295.244286] ata5: EH complete
  Apr 14 18:02:06 mark-linux kernel: [18500.172587] ata5.00: exception Emask 
0x0 SAct 0x7fff SErr 0x0 action 0x6 frozen
  Apr 14 18:02:06 mark-linux kernel: [18500.172601] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172617] ata5.00: cmd 
61/c8:00:17:0c:c0/00:00:5a:00:00/40 tag 0 ncq dma 102400 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172617]  res 
40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172625] ata5.00: status: { DRDY }
  Apr 14 18:02:06 mark-linux kernel: [18500.172631] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172643] ata5.00: cmd 
61/a0:08:af:39:c7/01:00:5a:00:00/40 tag 1 ncq dma 212992 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172643]  res 
40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172650] ata5.00: status: { DRDY }
  Apr 14 18:02:06 mark-linux kernel: [18500.172655] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172667] ata5.00: cmd 
61/30:10:6f:17:f2/00:00:5b:00:00/40 tag 2 ncq dma 24576 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172667]  res 
40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172673] ata5.00: status: { DRDY }
  Apr 14 18:02:06 mark-linux kernel: [18500.172678] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172689] ata5.00: cmd 
61/18:18:67:a4:25/00:00:62:00:00/40 tag 3 ncq dma 12288 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172689]  res 
40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172696] ata5.00: status: { DRDY }
  Apr 14 18:02:06 mark-linux kernel: [18500.172701] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172712] ata5.00: cmd 
61/20:20:b7:b7:25/00:00:62:00:00/40 tag 4 ncq dma 16384 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172712]  res 
40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172719] ata5.00: status: { DRDY }
  Apr 14 18:02:06 mark-linux kernel: [18500.172723] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172735] ata5.00: cmd 
61/30:28:5f:d6:25/00:00:62:00:00/40 tag 5 ncq dma 24576 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172735]  res 
40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172741] ata5.00: status: { DRDY }
  Apr 14 18:02:06 mark-linux kernel: [18500.172746] ata5.00: failed command: 
WRITE FPDMA QUEUED
  Apr 14 18:02:06 mark-linux kernel: [18500.172758] ata5.00: cmd 
61/08:30:17:8a:92/00:00:49:00:00/40 tag 6 ncq dma 4096 out
  Apr 14 18:02:06 mark-linux kernel: [18500.172758]  res 
40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  Apr 14 18:02:06 mark-linux kernel: [18500.172764] ata5.00: 

[Kernel-packages] [Bug 1686448] Re: Unable to reach higher than package C2 state with Skylake processor

[Leonardo Müller]

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  Unable to reach higher than package C2 state with Skylake processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello

  I have a Lenovo Ideapad 310 with a Intel Core i3-6100U. I have noticed
  its battery last less time on Xubuntu 16.04 than on Windows 10. I have
  searched on internet what could cause it, and found with powertop it
  can't reach states higher than package C state 2, while it could reach
  package C state 10.

  On this particular notebook model, I would expect the battery would
  last a bit more than 5 hours using only browser, as it happens with
  Windows 10 and CentOS 7. On Xubuntu, battery lasts slightly more than
  4 hours. The best was 4h30min, so I am having at least 30 minutes less
  battery time, but generally it is one hour.

  I have tried to get support on Ubuntu Forums, here is the link of the thread:
  https://ubuntuforums.org/showthread.php?t=2357271

  As everything we tried had no success, I am making this report.

  As a reference, CentOS 7 functioned correctly and the battery lasted
  the same time than Windows 10, while Fedora 25 has this problem too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.75.81
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4786 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 26 12:39:30 2017
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2016-12-31 (116 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN39WW:bd01/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1651435] Re: BTRFS error: could not find root 8

[Sly_tom_cat]

... it disappears when quota enabled on btrfs

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

Title:
  BTRFS error: could not find root 8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a KVM guest system which was running for some time now (142
  days uptime).

  Today, I logged in for the first time since months, and got an error
  message in syslog (and console):

  kernel: BTRFS error (device vda2): could not find root 8

  The error happened together with my login (in respect to the date of
  the log entry).

  The system was running with kernel 4.4.0-31-generic when the problem
  occured.

  When googling around, I found some similar results, but nowhere is
  mentioned that this got fixed somehow.

  So far, I could not find anything harmful (I did not reboot yet,
  however).

  I updated the kernel now, eventually that helps.

  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
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Dec 20 13:00 seq
   crw-rw+ 1 root audio 116, 33 Dec 20 13:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Dec 20 13:40:44 2016
  HibernationDevice: RESUME=UUID=419693f3-cd92-4870-a16a-7bede16d9b8a
  InstallationDate: Installed on 2016-06-20 (182 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=ebfbbec2-f4df-4e40-92a5-3db6b57eb8f5 ro rootflags=subvol=@
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.7.5-20140531_083030-gandalf
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20140531_083030-gandalf:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.1:cvnQEMU:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: QEMU
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-57-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2013-08-21 (1229 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IwConfig:
   em1   no wireless extensions.
   
   lono wireless extensions.
  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
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic 
root=UUID=16120d81-8cde-4e81-87cd-f55f65a4923b ro rootflags=subvol=@ 
pcie_aspm=force "acpi_osi=!Windows 2012" acpi=force acpi_enforce_resources=lax 
i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 
i915.semaphores=1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1686448] Re: Unable to reach higher than package C2 state with Skylake processor

[Leonardo Müller]

With this notebook, I am using Xubuntu 16.04 since I bought it. Since
the start battery lasted less time than on Windows 10, but I didn't know
why this was happening. The kernel at December 2016 was way more
problematic, but nearly all the problems were solved, but this one,
which reduces battery time, is still present.

I have tested the upstream kernel, and there are improvements: the
package is reaching C3. While it is only one stage above, this single
stage means 0,4 W of less consumption. When speaking about a system that
uses 7 W, this 0,4 W means more than 5% of economy.

It is still not perfect, as
http://www.intel.com/content/www/us/en/processors/core/6th-gen-core-
family-mobile-u-y-processor-lines-datasheet-vol-1.html states, package
can reach C10, so there is still something to do.

However, when installing the upstream kernel, there were warning
messages:

update-initramfs: Generating /boot/initrd.img-4.11.0-041100rc8-generic
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/skl_huc_ver01_07_1398.bin for 
module i915

I don't mind with bxt* and kbl*, as they are other generations
processors, but there is one Skylake message, so I believe different
problems can happen, and as they are related i915, I suppose it's
graphics.

So, while there is a improvement, it is still saving energy as it could,
so I believe the bug still exists.

** Attachment added: "turbostat411rc8"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686448/+attachment/4868333/+files/turbostat411rc8

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

Title:
  Unable to reach higher than package C2 state with Skylake processor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello

  I have a Lenovo Ideapad 310 with a Intel Core i3-6100U. I have noticed
  its battery last less time on Xubuntu 16.04 than on Windows 10. I have
  searched on internet what could cause it, and found with powertop it
  can't reach states higher than package C state 2, while it could reach
  package C state 10.

  On this particular notebook model, I would expect the battery would
  last a bit more than 5 hours using only browser, as it happens with
  Windows 10 and CentOS 7. On Xubuntu, battery lasts slightly more than
  4 hours. The best was 4h30min, so I am having at least 30 minutes less
  battery time, but generally it is one hour.

  I have tried to get support on Ubuntu Forums, here is the link of the thread:
  https://ubuntuforums.org/showthread.php?t=2357271

  As everything we tried had no success, I am making this report.

  As a reference, CentOS 7 functioned correctly and the battery lasted
  the same time than Windows 10, while Fedora 25 has this problem too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.75.81
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4786 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 26 12:39:30 2017
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2016-12-31 (116 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN39WW:bd01/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1686448] Re: Unable to reach higher than package C2 state with Skylake processor

[Leonardo Müller]

** Attachment added: "powertop411rc8.html"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686448/+attachment/4868334/+files/powertop411rc8.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/1686448

Title:
  Unable to reach higher than package C2 state with Skylake processor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello

  I have a Lenovo Ideapad 310 with a Intel Core i3-6100U. I have noticed
  its battery last less time on Xubuntu 16.04 than on Windows 10. I have
  searched on internet what could cause it, and found with powertop it
  can't reach states higher than package C state 2, while it could reach
  package C state 10.

  On this particular notebook model, I would expect the battery would
  last a bit more than 5 hours using only browser, as it happens with
  Windows 10 and CentOS 7. On Xubuntu, battery lasts slightly more than
  4 hours. The best was 4h30min, so I am having at least 30 minutes less
  battery time, but generally it is one hour.

  I have tried to get support on Ubuntu Forums, here is the link of the thread:
  https://ubuntuforums.org/showthread.php?t=2357271

  As everything we tried had no success, I am making this report.

  As a reference, CentOS 7 functioned correctly and the battery lasted
  the same time than Windows 10, while Fedora 25 has this problem too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.75.81
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4786 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 26 12:39:30 2017
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2016-12-31 (116 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN39WW:bd01/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1651435] Re: BTRFS error: could not find root 8

[Sly_tom_cat]

The same issue on Ubuntu 16.04.2 with BTRFS on single SHDD disk.

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

Title:
  BTRFS error: could not find root 8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a KVM guest system which was running for some time now (142
  days uptime).

  Today, I logged in for the first time since months, and got an error
  message in syslog (and console):

  kernel: BTRFS error (device vda2): could not find root 8

  The error happened together with my login (in respect to the date of
  the log entry).

  The system was running with kernel 4.4.0-31-generic when the problem
  occured.

  When googling around, I found some similar results, but nowhere is
  mentioned that this got fixed somehow.

  So far, I could not find anything harmful (I did not reboot yet,
  however).

  I updated the kernel now, eventually that helps.

  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
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Dec 20 13:00 seq
   crw-rw+ 1 root audio 116, 33 Dec 20 13:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Dec 20 13:40:44 2016
  HibernationDevice: RESUME=UUID=419693f3-cd92-4870-a16a-7bede16d9b8a
  InstallationDate: Installed on 2016-06-20 (182 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=ebfbbec2-f4df-4e40-92a5-3db6b57eb8f5 ro rootflags=subvol=@
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.7.5-20140531_083030-gandalf
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-2.1
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20140531_083030-gandalf:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.1:cvnQEMU:ct1:cvrpc-i440fx-2.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-2.1
  dmi.sys.vendor: QEMU
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-57-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2013-08-21 (1229 days ago)
  InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IwConfig:
   em1   no wireless extensions.
   
   lono wireless extensions.
  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
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic 
root=UUID=16120d81-8cde-4e81-87cd-f55f65a4923b ro rootflags=subvol=@ 
pcie_aspm=force "acpi_osi=!Windows 2012" acpi=force acpi_enforce_resources=lax 
i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 
i915.semaphores=1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  

[Kernel-packages] [Bug 1677297] Re: [Zesty] d-i: replace msm_emac with qcom_emac

[Manoj Iyer]

qcom_emac works fine with the generic phy driver, either the at803x
driver needs to be fixed or the underlying userspace utils like dhclient
needs to retry bringing up the link when it is reported as down. This
should not be a blocker for switching from msm_emac to qcom_emac for
d-i.

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

Title:
  [Zesty] d-i: replace msm_emac with qcom_emac

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  We landed a patch to support msm_emac module in initrd for amberwing 
platforms. But the upstream driver has since been renamed to qcom_emac. This 
module is needed in d-i's initrd so that these nics can be used to d-i install 
the system. The driver already exists in the zesty kernel under 
drivers/net/ethernet/qualcomm/emac/

  Revert commit 14893d91c9c391f8a4c2668b96ffe60aa728ad23 and add
  qcom_emac to initrd, and change the module name to qcom_emac.

  [Test Case]
  D-I install zesty on amberwing platform and notice that DI does not recognize 
the onboard two port nic.

  [Regression Potential]
  At present this driver applies only to amberwing systems, any regression will 
be isolated to amberwing platforms. The over all risk of regression is low.

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

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

[Kernel-packages] [Bug 1684971] Re: [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain

[Joshua R. Poulson]

In progress.

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

Title:
  [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain

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

Bug description:
  The following patch fixes a problem with "[PATCH] pci-hyperv: Use
  device serial number as PCI domain" where some drivers were expecting
  a u16 instead of a u32 for PCI device serial numbers, as observed by
  Oops and hangs in Azure on NC and NV GPU instances.

  From: Haiyang Zhang 

  This patch uses the lower 16 bits of the serial number as PCI
  domain, otherwise some drivers may not be able to handle it.

  Signed-off-by: Haiyang Zhang 
  ---
   drivers/pci/host/pci-hyperv.c |4 +++-
   1 files changed, 3 insertions(+), 1 deletions(-)

  diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyperv.c
  index e73880c..b18dff3 100644
  --- a/drivers/pci/host/pci-hyperv.c
  +++ b/drivers/pci/host/pci-hyperv.c
  @@ -1334,9 +1334,11 @@ static void put_pcichild(struct hv_pci_dev *hpdev,
 * can have shorter names than based on the bus instance UUID.
 * Only the first device serial number is used for domain, so the
 * domain number will not change after the first device is added.
  +  * The lower 16 bits of the serial number is used, otherwise some
  +  * drivers may not be able to handle it.
 */
if (list_empty(>children))
  - hbus->sysdata.domain = desc->ser;
  + hbus->sysdata.domain = desc->ser & 0x;
list_add_tail(>list_entry, >children);
spin_unlock_irqrestore(>device_list_lock, flags);
return hpdev;
  -- 
  1.7.1

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

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

[Kernel-packages] [Bug 1685865] Re: Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-logind

[Stefan Daenzer]

This kernel seems to fix the issue. I am able to login via the login
screen.

This is the output of "uname -a"

tisch@tisch-XPS-15-9560:~$ uname -a
Linux tisch-XPS-15-9560 4.11.0-041100rc6-generic #201704261323 SMP Wed Apr 26 
17:25:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-
  logind

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Used distribution:

  Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7

  After logging in to the gnome login screen, the system freezes. Trying to 
login using the shell (Ctr+Alt+F1) also freezes the system. The following 
ouptut appears on the shell repeatedly:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-logind:913]

  Steps to reproduce the problem:
  Boot Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7 and try to login after boot.

  Further testing results:
  Using Mainline Kernel Version 4.11.0-rc6, login works fine
  Using Kernel Version 4.10.11, login works fine
  Using Kernel Version 4.10.12, the issue is present

  ==> It might be possible the issue has been introduced in a commit in
  4.11.0-rc7 and has been backported to 4.10.12.

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

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

[Kernel-packages] [Bug 1686040] Re: linux: 4.4.0-77.98 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the 4.4.0-77.98 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Wednesday, 26. April 2017 19:02 UTC

** Description changed:

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

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

Title:
  linux: 4.4.0-77.98 -proposed tracker

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

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

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

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

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

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

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

[Joseph Salisbury]

@jac...@de.ibm.com  It would be good to know if this bug is already
fixed in the mainline kernel.  Would it be possible for you to test
4.11-rc8?  It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8/

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

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

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

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

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

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

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

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

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

  crash> dev -d
  MAJOR GENDISKNAME   REQUEST_QUEUE  TOTAL ASYNC  SYNC   DRV
  ...
  8 1e1d6d800  sda1e1d51210  0 23151 4294944145 
N/A(MQ)
  8 1e4e06800  sdc2081b180 23148 4294944148 
N/A(MQ)
  8 1f07800sdb20c75680 23195 4294944101 
N/A(MQ)
  8 1e4e06000  sdd1e4e31210  0 23099 4294944197 
N/A(MQ)
252 1e1d6c800  dm-0   1e1d51b18  9 1 8 
N/A(MQ)
  ...

  So both dm-mpath and sd have requests pending in their block multiqueue.
  The large numbers of sd look strange and seem to be the unsigned formatting 
of the values shown for async multiplied by -1.

  [0.798256] Linux version 4.4.0-65-generic (buildd@z13-011) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #86-Ubuntu SMP Thu Feb 23 
17:54:37 UTC 2017 (Ubuntu 4.4.0-65.86-generic 4.4.49)
  [0.798262] setup: Linux is running natively in 64-bit mode
  [0.798290] setup: Max memory size: 8192MB
  [0.798298] setup: Reserving 196MB of memory at 7996MB for crashkernel 
(System RAM: 7996MB)

  [0.836923] Kernel command line: root=/dev/mapper/mclint_vg-root
  rootflags=subvol=@ crashkernel=196M BOOT_IMAGE=0

  [ 5281.179428] INFO: task xfsaild/dm-11:1604 blocked for more than 120 
seconds.
  [ 5281.179437]   Not tainted 4.4.0-65-generic #86-Ubuntu
  [ 5281.179438] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5281.179440] xfsaild/dm-11   D 007bcf52 0  1604  2 
0x
  [ 5281.179444]0001e931c230 001a6964 0001e6f9b958 
0001e6f9b9d8
0001e15795f0 0001e6f9b988 00ce8c00 
0001ea805c70
0001ea805c00 00ba5ed0 0001e931c1d0 
0001e1579b20
0001ea805c00 0001e15795f0 0001ea805c00 

007d3978 007bc9f8 0001e6f9b9d8 
0001e6f9ba40
  [ 5281.179454] Call Trace:
  [ 5281.179461] ([<007bc9f8>] __schedule+0x300/0x810)
  [ 5281.179462]  [<007bcf52>] schedule+0x4a/0xb0
  [ 5281.179465]  [<007c02aa>] schedule_timeout+0x232/0x2a8
  [ 5281.179466]  [<007bde50>] wait_for_common+0x110/0x1c8
  [ 5281.179472]  [<0017b602>] flush_work+0x42/0x58
  [ 5281.179564]  [<03ff805e14ba>] xlog_cil_force_lsn+0x7a/0x238 [xfs]
  [ 5281.179589]  [<03ff805dee82>] _xfs_log_force+0x9a/0x2e8 [xfs]
  

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Mitchell Tasman]

@Joseph,

Hi again.  FYI, the bug never triggered when I tried your suggestion
from #24 to test the following early Zesty kernel:

https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/12001523

But as noted in my previous comment, the BUG did alas trigger in my
environment while running 4.10.0-20-generic #22~lp1674838.

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

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

[Ben]

Issue definitely persists on 4.11/upstream. I came across an interesting
output in dmesg which may explain why bluetooth works while the WiFi
doesn't:

[17326.525545] iwlwifi :01:00.0: Could not load the [0] uCode section
[17326.525697] iwlwifi :01:00.0: Failed to start INIT ucode: -5
[17326.525702] iwlwifi :01:00.0: Failed to run INIT ucode: -5
[17326.525705] iwlwifi :01:00.0: Failed to start RT ucode: -5
[17391.638774] usb 1-4: USB disconnect, device number 64
[17392.015275] usb 1-4: new full-speed USB device number 65 using xhci_hcd
[17392.156505] usb 1-4: New USB device found, idVendor=8087, idProduct=07dc
[17392.156520] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[17392.179288] Bluetooth: hci0: read Intel version: 3707100180012d0d00
[17392.179426] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
[17392.367199] Bluetooth: hci0: Intel Bluetooth firmware patch completed and 
activated


What's interesting is that iwlwifi "can't load" the uCode/firmware, causing the 
internet/wifi portion to fail, but Bluetooth uses a separate firmware file on 
the same card, which itself works fine. So this probably explains why the 
bluetooth still works.

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

Title:
  Intel Wireless 7260 often crashes

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Mitchell Tasman]

Joseph,

Hi.  I have been running with your test kernel:

$ uname -a
Linux titanic 4.10.0-20-generic #22~lp1674838 SMP Mon Apr 24 18:50:06 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

Unfortunately, it appears that this kernel is still subject to the BUG.
Please see the attached dmesg snippet.


** Attachment added: "dmesg output showing BUG with Joseph's test kernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+attachment/4868330/+files/kern.bug

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

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

[Brad Figg]

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

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

** Description changed:

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1686154
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Wednesday, 26. April 2017 18:32 UTC
+ 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/1686156

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

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

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

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

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Joseph Salisbury]

@Daniel, can you try testing the kernel posted in comment #55?  The
uname output should have the bug number in it:

4.10.0-20-generic #22~lp1674838

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

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

[Thadeu Lima de Souza Cascardo]

** Summary changed:

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

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1686154

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

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

[Kernel-packages] [Bug 1685865] Re: Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-logind

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
88b0b92bdaadfc43b11dc4172219ff0972673790

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1685865/88b0b92bdaadfc43b11dc4172219ff0972673790

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-
  logind

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Used distribution:

  Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7

  After logging in to the gnome login screen, the system freezes. Trying to 
login using the shell (Ctr+Alt+F1) also freezes the system. The following 
ouptut appears on the shell repeatedly:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-logind:913]

  Steps to reproduce the problem:
  Boot Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7 and try to login after boot.

  Further testing results:
  Using Mainline Kernel Version 4.11.0-rc6, login works fine
  Using Kernel Version 4.10.11, login works fine
  Using Kernel Version 4.10.12, the issue is present

  ==> It might be possible the issue has been introduced in a commit in
  4.11.0-rc7 and has been backported to 4.10.12.

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

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

[Kernel-packages] [Bug 1655684] Re: Wi-FI connection is slow/unstable and has a high latency [14e4:4365]

[Launchpad Bug Tracker]

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

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

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

Title:
  Wi-FI connection is slow/unstable and has a high latency [14e4:4365]

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source driver on a BCM43142 card has a slow wifi
  connection with a high latency, while the device works properly on
  Microsoft windows. The result is that browsing is slow and online
  games lag. Pinging the router also reports a much higher latency than
  that of other devices (>70 ms instead of about ~1,5-2 ms).

  Device: 
  0d:00.0 Network controller [0280]: Broadcom Limited BCM43142 802.11b/g/n 
[14e4:4365] (rev 01)
  Subsystem: Hewlett-Packard Company BCM43142 802.11b/g/n [103c:804a]
  Kernel driver in use: wl
  Package:bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1
  Uname: Linux 4.9.2-040902-generic x86_64
  NonfreeKernelModules: wl
  Architecture: amd64
  CurrentDesktop: MATE
  InstallationDate: Installed on 2016-06-02
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=el
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=el_GR.UTF-8
   SHELL=/bin/bash

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Daniel]

https://kopy.io/g2GjC

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Daniel]

daniel@XPS-13:~$ uname -r
4.10.0-20-generic

My computer just froze with this kernel. This issue is _not_ fixed in
this kernel.

As you can see I run a Dell XPS-13 with the Intel network card if that
information helps..? Like others say it freezes randomly or on heavy
load for a longer period of time. I don't use Firefox , but I have
always my mail open which is Thunderbird.

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1685865] Re: Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-logind

[Joseph Salisbury]

The tip of our trees might be different.  If you run this, you should
see the range of commits:


git log --oneline
b9b3322f13f350587f17f0a76f008830e3a420d3..ee921c762cf90652add60ebacb5b90636ac108df


ee921c762cf9 Merge tag 'drm-fixes-for-v4.11-rc7' of 
git://people.freedesktop.org/~airlied/linux
827c30a75839 Merge tag 'pwm/for-4.11-rc7' of 
git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm
2ca62d8a606a Merge branch 'linux-4.11' of git://github.com/skeggsb/linux into 
drm-fixes
88b0b92bdaad Merge tag 'drm-intel-fixes-2017-04-12' of 
git://anongit.freedesktop.org/git/drm-intel into drm-fixes
97d93f35493f Merge tag 'drm-misc-fixes-2017-04-11' of 
git://anongit.freedesktop.org/git/drm-misc into drm-fixes
c7aae6221f73 Merge branch 'etnaviv/fixes' of 
https://git.pengutronix.de/git/lst/linux into drm-fixes
45abdf35cf82 drm/etnaviv: fix missing unlock on error in etnaviv_gpu_submit()
0c45b36f8acc drm/udl: Fix unaligned memory access in udl_render_hline
c053b5a506d3 drm/i915: Don't call synchronize_rcu_expedited under struct_mutex
63987bfebd88 drm/i915: Suspend GuC prior to GPU Reset during GEM suspend
e5199a37f7ed Merge tag 'gvt-fixes-2017-04-07' of 
https://github.com/01org/gvt-linux into drm-intel-fixes
a900152b5c29 pwm: rockchip: State of PWM clock should synchronize with PWM 
enabled state
b997e3edca4f pwm: lpss: Set enable-bit before waiting for update-bit to go low
3c1460e934f3 pwm: lpss: Split Tangier configuration
da2ba564a6dc drm/nouveau: initial support (display-only) for GP107
2907e8670b6e drm/nouveau/kms/nv50: fix double dma_fence_put() when destroying 
plane state
d639fbcc1027 drm/nouveau/kms/nv50: fix setting of HeadSetRasterVertBlankDmi 
method
f94773b9f5ec drm/nouveau/mmu/nv4a: use nv04 mmu rather than the nv44 one
83bce9c2baa5 drm/nouveau/mpeg: mthd returns true on success now
a34f83639490 drm/i915/gvt: set the correct default value of CTX STATUS PTR
cf082a4a264d Merge tag 'gvt-fixes-2017-04-01' of 
https://github.com/01org/gvt-linux into drm-intel-fixes
aa4ce4493c88 drm/i915/gvt: Fix firmware loading interface for GVT-g golden HW 
state
ecf8e89917d6 drm/i915: Use a dummy timeline name for a signaled fence
1383aeca92b7 drm/i915: Ironlake do_idle_maps w/a may be called w/o struct_mutex
9ba2a6261de4 drm/i915/gvt: remove the redundant info NULL check
729a0cd45c88 drm/i915/gvt: adjust mem size for low resolution type
6c9a8cdad48a drm/i915: Avoid lock dropping between rescheduling
f85726905745 drm/i915/gvt: exclude cfg space from failsafe mode
b79c52aef3cd drm/i915/gvt: Activate/de-activate vGPU in mdev ops.
dd68f2ba0720 drm/i915/execlists: Wrap tail pointer after reset tweaking
aa62acfd63e7 drm/i915/perf: remove user triggerable warn
4e5f713ffc20 drm/i915/perf: destroy stream on sample_flags mismatch
9e1764309f57 drm/i915: Align "unfenced" tiled access on gen2, early gen3

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

Title:
  Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-
  logind

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Used distribution:

  Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7

  After logging in to the gnome login screen, the system freezes. Trying to 
login using the shell (Ctr+Alt+F1) also freezes the system. The following 
ouptut appears on the shell repeatedly:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-logind:913]

  Steps to reproduce the problem:
  Boot Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7 and try to login after boot.

  Further testing results:
  Using Mainline Kernel Version 4.11.0-rc6, login works fine
  Using Kernel Version 4.10.11, login works fine
  Using Kernel Version 4.10.12, the issue is present

  ==> It might be possible the issue has been introduced in a commit in
  4.11.0-rc7 and has been backported to 4.10.12.

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

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

[Kernel-packages] [Bug 1685865] Re: Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-logind

[Joseph Salisbury]

@LocutusOfBorg, I did says good for commit b9b3322f1.  This is my
current bisect log:

git bisect log
git bisect start
# good: [39da7c509acff13fc8cb12ec1bb20337c988ed36] Linux 4.11-rc6
git bisect good 39da7c509acff13fc8cb12ec1bb20337c988ed36
# bad: [4f7d029b9bf009fbee76bb10c0c4351a1870d2f3] Linux 4.11-rc7
git bisect bad 4f7d029b9bf009fbee76bb10c0c4351a1870d2f3
# bad: [82f1faa86727de976e38eade5e96a1846742d71e] Merge tag 'fbdev-v4.11-rc6' 
of git://github.com/bzolnier/linux
git bisect bad 82f1faa86727de976e38eade5e96a1846742d71e
# bad: [ee921c762cf90652add60ebacb5b90636ac108df] Merge tag 
'drm-fixes-for-v4.11-rc7' of git://people.freedesktop.org/~airlied/linux
git bisect bad ee921c762cf90652add60ebacb5b90636ac108df
# good: [b9b3322f13f350587f17f0a76f008830e3a420d3] Merge branch 'stable-4.11' 
of git://git.infradead.org/users/pcmoore/audit
git bisect good b9b3322f13f350587f17f0a76f008830e3a420d3

git bisect next
Bisecting: 16 revisions left to test after this (roughly 4 steps)
[63987bfebd8869e00b34e2bdd12e59d71909bec0] drm/i915: Suspend GuC prior to GPU 
Reset during GEM suspend


Marking commit 63987bfebd good asks for the next SHA1 to be tested:

git bisect good 63987bfebd8869e00b34e2bdd12e59d71909bec0
Bisecting: 10 revisions left to test after this (roughly 3 steps)
[88b0b92bdaadfc43b11dc4172219ff0972673790] Merge tag 
'drm-intel-fixes-2017-04-12' of git://anongit.freedesktop.org/git/drm-intel 
into drm-fixes


I'll build that next kernel now.

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

Title:
  Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-
  logind

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Used distribution:

  Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7

  After logging in to the gnome login screen, the system freezes. Trying to 
login using the shell (Ctr+Alt+F1) also freezes the system. The following 
ouptut appears on the shell repeatedly:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-logind:913]

  Steps to reproduce the problem:
  Boot Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7 and try to login after boot.

  Further testing results:
  Using Mainline Kernel Version 4.11.0-rc6, login works fine
  Using Kernel Version 4.10.11, login works fine
  Using Kernel Version 4.10.12, the issue is present

  ==> It might be possible the issue has been introduced in a commit in
  4.11.0-rc7 and has been backported to 4.10.12.

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Joseph Salisbury]

Commit d75450ff40df0199bf13dfb1 is not in any Ubuntu kernel as of yet.

It sounds like this commit fixes the issue.  If possible please test
with that kernel a little longer to confirm it resolves the bug.  If it
does, I'll submit an  SRU request to include that commit in all affected
releases.

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1686448] Re: Unable to reach higher than package C2 state with Skylake processor

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8

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

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

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

Title:
  Unable to reach higher than package C2 state with Skylake processor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello

  I have a Lenovo Ideapad 310 with a Intel Core i3-6100U. I have noticed
  its battery last less time on Xubuntu 16.04 than on Windows 10. I have
  searched on internet what could cause it, and found with powertop it
  can't reach states higher than package C state 2, while it could reach
  package C state 10.

  On this particular notebook model, I would expect the battery would
  last a bit more than 5 hours using only browser, as it happens with
  Windows 10 and CentOS 7. On Xubuntu, battery lasts slightly more than
  4 hours. The best was 4h30min, so I am having at least 30 minutes less
  battery time, but generally it is one hour.

  I have tried to get support on Ubuntu Forums, here is the link of the thread:
  https://ubuntuforums.org/showthread.php?t=2357271

  As everything we tried had no success, I am making this report.

  As a reference, CentOS 7 functioned correctly and the battery lasted
  the same time than Windows 10, while Fedora 25 has this problem too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.75.81
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4786 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 26 12:39:30 2017
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2016-12-31 (116 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN39WW:bd01/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1686268] Re: Backlight brightness level not restored after reboot

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8

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

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

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

Title:
  Backlight brightness level not restored after reboot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am not sure if this is the right place to report this, so feel free
  to move it elsewhere.

  It looks like the systemd-backlight service (/lib/systemd/system
  /systemd-backlight@.service) does not restore the brightness level
  (although it saves it before shut-down).

  However the following command does restore the saved brightness:

  sudo /lib/systemd/systemd-backlight load backlight:intel_backlight

  As a temporary solution to automate it at boot I am using the
  following line added to the root cron:

  @reboot /lib/systemd/systemd-backlight load backlight:intel_backlight

  - Ubuntu 4.10.0-20.22-generic 4.10.8
  - Gnome 3.24

  Please, let me know if you need more info. Thanks.
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dd 1540 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-04-12 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170411)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=/dev/mapper/nvme-ubuntu_gnome ro systemd.restore_state=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/29/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 06X96V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1686299] Re: Cannot get past login after update to 4.4.0.75-generic

[Joseph Salisbury]

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

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

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

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".

Thanks in advance.

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


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

** Tags added: needs-bisect

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

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

Title:
  Cannot get past login after update to 4.4.0.75-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After running software update on 16.04 and rebooting, I cannot get
  past the login screen.  The screen appears the wrong resolution and
  squashed smaller than the screen with a black border.  When I login,
  it accepts the password, but after a few seconds the screen gets
  corrupted then resets back to the login screen.

  Rebooting to an older kernel fixed the issue.

  Working:
   4.4.0-72-generic

  Failed:
   4.4.0.75-generic

  I'm using nvidia 340.102

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ben2228 F pulseaudio
   /dev/snd/controlC1:  ben2228 F pulseaudio
   /dev/snd/controlC0:  ben2228 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 25 23:46:40 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a1a4d11a-a791-49f3-9542-90dbd821d0d2
  InstallationDate: Installed on 2012-04-28 (1823 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=7d577aa7-441e-43e2-b6b3-a8500fe017c9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-03-27 (30 days ago)
  dmi.bios.date: 04/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.40
  dmi.board.name: X58 Extreme
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd04/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1686154] Re: linux: 3.13.0-118.165 -proposed tracker

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1686156
  derivatives:
+ kernel-stable-phase-changed:Wednesday, 26. April 2017 16:32 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1686156
  derivatives:
  kernel-stable-phase-changed:Wednesday, 26. April 2017 16:32 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ 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/1686154

Title:
  linux: 3.13.0-118.165 -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:
  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:
  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
Status in linux source package in Trusty:
  New

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

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

  backports: 1686156
  derivatives:
  kernel-stable-phase-changed:Wednesday, 26. April 2017 16:32 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1686305] Re: Merlin SGMII fail on Ubuntu Xenial HWE kernel

[Joseph Salisbury]

I built a Yakkety test kernel with the two commits mentioned in comment
#1.  The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1686305/

Can you test this kernel and see if it resolves the bug?

Thanks in advance!

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

Title:
  Merlin SGMII fail on Ubuntu Xenial HWE kernel

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

Bug description:
  Using the Ubuntu Xenial HWE installation image at 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial-updates/main/installer-arm64/current/images/hwe-netboot
 to install Ubuntu into the Merlin board, the SGMII port is fail to get IP from 
DHCP.
  After installation, booting into Linux prompt, the SGMII port is fail to get 
IP from DHCP also. Checking with ethtool, the link is always report down.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 11  2016 seq
   crw-rw 1 root audio 116, 33 Feb 11  2016 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2aa90b24-e14e-4854-b52b-b853388a3466
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Merlin Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=8e10d908-38aa-4cb4-990c-4a9bcabc51a4 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-49-generic N/A
   linux-backports-modules-4.8.0-49-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-49-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: Oct 17 2016
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.06.25
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Merlin Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.06.25:bdOct172016:svnAppliedMicro:pnX-GeneMerlinBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMerlinBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Merlin Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 11  2016 seq
   crw-rw 1 root audio 116, 33 Feb 11  2016 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2aa90b24-e14e-4854-b52b-b853388a3466
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Merlin Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=8e10d908-38aa-4cb4-990c-4a9bcabc51a4 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-49-generic N/A
   linux-backports-modules-4.8.0-49-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-49-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: Oct 17 2016
  

[Kernel-packages] [Bug 1685864] Re: System freezes when logging into gnome-shell

[Richard Eames]

** Attachment added: "logs for 4.10-rc3"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685864/+attachment/4868283/+files/importantlogs.4.10-rc3.log

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

Title:
  System freezes when logging into gnome-shell

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

Bug description:
  I upgraded to ubuntu 17.04 this morning, and can no longer login with 
gnome/gnome(classic)/gnome on wayland. When I try, the UI completely freezes, 
and keyboard and mouse no longer respond. 
  However, I am able to ssh into the machine, and see that there is a kernel 
bug in the logs:

  10:48:51 kernel: error: failed to run Kubelet: invalid kubeconfig: stat 
/etc/kubernetes/kubelet.conf: no such file or directory
  10:48:51 kernel: I0424 10:48:50.9799144641 feature_gate.go:144] feature 
gates: map[]
  10:48:51 kernel: ---[ end trace 41c77bd8e97d35e7 ]---
  10:48:51 kernel: CR2: 
  10:48:51 kernel: RIP:   (null) RSP: c17a44fdfa30
  10:48:51 kernel: Code:  Bad RIP value.
  10:48:51 kernel: R13: 55f4bf9307b0 R14: 000a R15: 
55f4bf8f06e0
  10:48:51 kernel: R10: 55f4bf5c0c50 R11: 3246 R12: 
0130
  10:48:51 kernel: RBP: 1c80 R08: 0040 R09: 
0780
  10:48:51 kernel: RDX: 7f96d5f0a360 RSI: c01c64a3 RDI: 
000e
  10:48:51 kernel: RAX: ffda RBX: 7f96e30dcc20 RCX: 
7f96e0afa987
  10:48:51 kernel: RSP: 002b:7f96d5f0a328 EFLAGS: 3246 ORIG_RAX: 
0010
  10:48:51 kernel: RIP: 0033:0x7f96e0afa987
  10:48:51 kernel:  entry_SYSCALL_64_fastpath+0x1e/0xad
  10:48:51 kernel:  SyS_ioctl+0x79/0x90
  10:48:51 kernel:  ? vfs_read+0x96/0x130
  10:48:51 kernel:  ? __vfs_read+0x18/0x40
  10:48:51 kernel:  do_vfs_ioctl+0xa3/0x610
  10:48:51 kernel:  nouveau_drm_ioctl+0x74/0xc0 [nouveau]
  10:48:51 kernel:  ? _copy_to_user+0x54/0x60
  10:48:51 kernel:  ? drm_mode_setplane+0x1a0/0x1a0 [drm]
  10:48:51 kernel:  drm_ioctl+0x21b/0x4c0 [drm]
  10:48:51 kernel:  drm_mode_cursor_ioctl+0x50/0x70 [drm]
  10:48:51 kernel:  ? ep_poll_callback+0xef/0x1f0
  10:48:51 kernel:  drm_mode_cursor_common+0x86/0x180 [drm]
  10:48:51 kernel:  drm_mode_cursor_universal+0x126/0x210 [drm]
  10:48:51 kernel:  ? __ww_mutex_lock_slowpath+0x29a/0x3d0
  10:48:51 kernel:  __setplane_internal+0x1b4/0x280 [drm]
  10:48:51 kernel:  drm_atomic_helper_update_plane+0xec/0x150 [drm_kms_helper]
  10:48:51 kernel:  drm_atomic_commit+0x4b/0x50 [drm]
  10:48:51 kernel:  nv50_disp_atomic_commit+0x19c/0x2a0 [nouveau]
  10:48:51 kernel:  drm_atomic_helper_wait_for_fences+0x48/0x120 
[drm_kms_helper]
  10:48:51 kernel:  ? dma_fence_wait_timeout+0x39/0xf0
  10:48:51 kernel: Call Trace:
  10:48:51 kernel: CR2:  CR3: 0007ed6df000 CR4: 
000406e0
  10:48:51 kernel: CS:  0010 DS:  ES:  CR0: 80050033
  10:48:51 kernel: FS:  7f96d5f0c700() GS:9aeefed0() 
knlGS:
  10:48:51 kernel: R13: 0001 R14: 7fff R15: 
0001
  10:48:51 kernel: R10: 9aeed329b780 R11: 9aeed1157c08 R12: 
9aeed08c6480
  10:48:51 kernel: RBP: c17a44fdfa58 R08:  R09: 
9aeed272a000
  10:48:51 kernel: RDX: 7fff RSI: 0001 RDI: 
9aeed08c6480
  10:48:51 kernel: RAX: 9aeed3402000 RBX: 9aee6883b000 RCX: 
c047afa0
  10:48:51 kernel: RSP: 0018:c17a44fdfa30 EFLAGS: 00010206
  10:48:51 kernel: RIP: 0010:  (null)
  10:48:51 kernel: task: 9aeeafb02d00 task.stack: c17a44fdc000
  10:48:51 kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by 
O.E.M./GA-990FX-GAMING, BIOS F1 11/05/2015
  10:48:51 kernel: CPU: 4 PID: 2212 Comm: InputThread Tainted: G   OE   
4.10.0-20-generic #22-Ubuntu
  10:48:51 kernel:  k10temp fam15h_power parport_pc ppdev lp parport ip_tables 
x_tables autofs4 hid_generic hid_microsoft usbhid hid nouveau mxm_wmi video 
i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
alx drm nvme mdio ahci nvme_core libahci fjes wmi
  10:48:51 kernel: Modules linked in: xt_nat xt_tcpudp veth ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat 
nf_conntrack libcrc32c br_netfilter bridge stp llc aufs pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc snd_hda_codec_hdmi 
dm_crypt btrfs xor nls_iso8859_1 raid6_pq edac_mce_amd edac_core kvm_amd kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc input_leds 
joydev aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec 
snd_seq_midi 

[Kernel-packages] [Bug 1685864] Re: System freezes when logging into gnome-shell

[Richard Eames]

I couldn't boot into 4.10-rc1 (it got stuck at loading the initram), and
the other two allowed me to login, however, there were errors printed:

4.9:
10:02:44 kernel: nouveau :01:00.0: priv: GPC1: 419df4  (1f40820e)
10:02:44 kernel: nouveau :01:00.0: priv: GPC0: 419df4  (1f40820e)
10:02:44 kernel: nouveau :01:00.0: DRM: Pointer to flat panel table invalid
10:02:44 kernel: [Firmware Bug]: CPU7: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU7: APIC id mismatch. Firmware: 17 CPUID: 7
10:02:44 kernel: [Firmware Bug]: CPU6: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU6: APIC id mismatch. Firmware: 16 CPUID: 6
10:02:44 kernel: [Firmware Bug]: CPU5: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU5: APIC id mismatch. Firmware: 15 CPUID: 5
10:02:44 kernel: [Firmware Bug]: CPU4: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU4: APIC id mismatch. Firmware: 14 CPUID: 4
10:02:44 kernel: [Firmware Bug]: CPU3: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 13 CPUID: 3
10:02:44 kernel: [Firmware Bug]: CPU2: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 12 CPUID: 2
10:02:44 kernel: [Firmware Bug]: CPU1: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 11 CPUID: 1
10:02:44 kernel: [Firmware Bug]: CPU0: Using firmware package id 1 instead of 0
10:02:44 kernel: [Firmware Bug]: CPU0: APIC id mismatch. Firmware: 10 CPUID: 0

4.10-rc3:
10:14:38 kernel: nouveau :01:00.0: priv: GPC1: 419df4  (1e40820e)
10:14:38 kernel: nouveau :01:00.0: priv: GPC0: 419df4  (1e40820e)
10:14:38 kernel: nouveau :01:00.0: DRM: Pointer to flat panel table invalid
10:14:38 kernel: nouveau :01:00.0: bus: MMIO write of 80be FAULT at 
10eb14 [ IBUS ]


** Attachment added: "logs for 4.9"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685864/+attachment/4868282/+files/importantlogs.4.9.log

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

Title:
  System freezes when logging into gnome-shell

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

Bug description:
  I upgraded to ubuntu 17.04 this morning, and can no longer login with 
gnome/gnome(classic)/gnome on wayland. When I try, the UI completely freezes, 
and keyboard and mouse no longer respond. 
  However, I am able to ssh into the machine, and see that there is a kernel 
bug in the logs:

  10:48:51 kernel: error: failed to run Kubelet: invalid kubeconfig: stat 
/etc/kubernetes/kubelet.conf: no such file or directory
  10:48:51 kernel: I0424 10:48:50.9799144641 feature_gate.go:144] feature 
gates: map[]
  10:48:51 kernel: ---[ end trace 41c77bd8e97d35e7 ]---
  10:48:51 kernel: CR2: 
  10:48:51 kernel: RIP:   (null) RSP: c17a44fdfa30
  10:48:51 kernel: Code:  Bad RIP value.
  10:48:51 kernel: R13: 55f4bf9307b0 R14: 000a R15: 
55f4bf8f06e0
  10:48:51 kernel: R10: 55f4bf5c0c50 R11: 3246 R12: 
0130
  10:48:51 kernel: RBP: 1c80 R08: 0040 R09: 
0780
  10:48:51 kernel: RDX: 7f96d5f0a360 RSI: c01c64a3 RDI: 
000e
  10:48:51 kernel: RAX: ffda RBX: 7f96e30dcc20 RCX: 
7f96e0afa987
  10:48:51 kernel: RSP: 002b:7f96d5f0a328 EFLAGS: 3246 ORIG_RAX: 
0010
  10:48:51 kernel: RIP: 0033:0x7f96e0afa987
  10:48:51 kernel:  entry_SYSCALL_64_fastpath+0x1e/0xad
  10:48:51 kernel:  SyS_ioctl+0x79/0x90
  10:48:51 kernel:  ? vfs_read+0x96/0x130
  10:48:51 kernel:  ? __vfs_read+0x18/0x40
  10:48:51 kernel:  do_vfs_ioctl+0xa3/0x610
  10:48:51 kernel:  nouveau_drm_ioctl+0x74/0xc0 [nouveau]
  10:48:51 kernel:  ? _copy_to_user+0x54/0x60
  10:48:51 kernel:  ? drm_mode_setplane+0x1a0/0x1a0 [drm]
  10:48:51 kernel:  drm_ioctl+0x21b/0x4c0 [drm]
  10:48:51 kernel:  drm_mode_cursor_ioctl+0x50/0x70 [drm]
  10:48:51 kernel:  ? ep_poll_callback+0xef/0x1f0
  10:48:51 kernel:  drm_mode_cursor_common+0x86/0x180 [drm]
  10:48:51 kernel:  drm_mode_cursor_universal+0x126/0x210 [drm]
  10:48:51 kernel:  ? __ww_mutex_lock_slowpath+0x29a/0x3d0
  10:48:51 kernel:  __setplane_internal+0x1b4/0x280 [drm]
  10:48:51 kernel:  drm_atomic_helper_update_plane+0xec/0x150 [drm_kms_helper]
  10:48:51 kernel:  drm_atomic_commit+0x4b/0x50 [drm]
  10:48:51 kernel:  nv50_disp_atomic_commit+0x19c/0x2a0 [nouveau]
  10:48:51 kernel:  drm_atomic_helper_wait_for_fences+0x48/0x120 
[drm_kms_helper]
  10:48:51 kernel:  ? dma_fence_wait_timeout+0x39/0xf0
  10:48:51 kernel: Call Trace:
  10:48:51 kernel: CR2:  CR3: 0007ed6df000 CR4: 

[Kernel-packages] [Bug 1686448] Re: Unable to reach higher than package C2 state with Skylake processor

[Leonardo Müller]

Here is the powertop output. Tuning additional options to "Good" from
this point start to cause problems, as crackling sound and nonfunctional
mouse.

** Attachment added: "powertop.html"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686448/+attachment/4868281/+files/powertop.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/1686448

Title:
  Unable to reach higher than package C2 state with Skylake processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello

  I have a Lenovo Ideapad 310 with a Intel Core i3-6100U. I have noticed
  its battery last less time on Xubuntu 16.04 than on Windows 10. I have
  searched on internet what could cause it, and found with powertop it
  can't reach states higher than package C state 2, while it could reach
  package C state 10.

  On this particular notebook model, I would expect the battery would
  last a bit more than 5 hours using only browser, as it happens with
  Windows 10 and CentOS 7. On Xubuntu, battery lasts slightly more than
  4 hours. The best was 4h30min, so I am having at least 30 minutes less
  battery time, but generally it is one hour.

  I have tried to get support on Ubuntu Forums, here is the link of the thread:
  https://ubuntuforums.org/showthread.php?t=2357271

  As everything we tried had no success, I am making this report.

  As a reference, CentOS 7 functioned correctly and the battery lasted
  the same time than Windows 10, while Fedora 25 has this problem too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.75.81
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4786 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 26 12:39:30 2017
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2016-12-31 (116 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN39WW:bd01/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1686448] Re: Unable to reach higher than package C2 state with Skylake processor

[Leonardo Müller]

** Attachment added: "sudo turbostat --debug --out turbostat"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686448/+attachment/4868280/+files/turbostat

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

Title:
  Unable to reach higher than package C2 state with Skylake processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello

  I have a Lenovo Ideapad 310 with a Intel Core i3-6100U. I have noticed
  its battery last less time on Xubuntu 16.04 than on Windows 10. I have
  searched on internet what could cause it, and found with powertop it
  can't reach states higher than package C state 2, while it could reach
  package C state 10.

  On this particular notebook model, I would expect the battery would
  last a bit more than 5 hours using only browser, as it happens with
  Windows 10 and CentOS 7. On Xubuntu, battery lasts slightly more than
  4 hours. The best was 4h30min, so I am having at least 30 minutes less
  battery time, but generally it is one hour.

  I have tried to get support on Ubuntu Forums, here is the link of the thread:
  https://ubuntuforums.org/showthread.php?t=2357271

  As everything we tried had no success, I am making this report.

  As a reference, CentOS 7 functioned correctly and the battery lasted
  the same time than Windows 10, while Fedora 25 has this problem too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.75.81
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4786 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 26 12:39:30 2017
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2016-12-31 (116 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN39WW:bd01/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1684971] Re: [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain

[Brad Figg]

Josh,

There is a -proposed kernel ready for testing with this fix.

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

Title:
  [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain

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

Bug description:
  The following patch fixes a problem with "[PATCH] pci-hyperv: Use
  device serial number as PCI domain" where some drivers were expecting
  a u16 instead of a u32 for PCI device serial numbers, as observed by
  Oops and hangs in Azure on NC and NV GPU instances.

  From: Haiyang Zhang 

  This patch uses the lower 16 bits of the serial number as PCI
  domain, otherwise some drivers may not be able to handle it.

  Signed-off-by: Haiyang Zhang 
  ---
   drivers/pci/host/pci-hyperv.c |4 +++-
   1 files changed, 3 insertions(+), 1 deletions(-)

  diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyperv.c
  index e73880c..b18dff3 100644
  --- a/drivers/pci/host/pci-hyperv.c
  +++ b/drivers/pci/host/pci-hyperv.c
  @@ -1334,9 +1334,11 @@ static void put_pcichild(struct hv_pci_dev *hpdev,
 * can have shorter names than based on the bus instance UUID.
 * Only the first device serial number is used for domain, so the
 * domain number will not change after the first device is added.
  +  * The lower 16 bits of the serial number is used, otherwise some
  +  * drivers may not be able to handle it.
 */
if (list_empty(>children))
  - hbus->sysdata.domain = desc->ser;
  + hbus->sysdata.domain = desc->ser & 0x;
list_add_tail(>list_entry, >children);
spin_unlock_irqrestore(>device_list_lock, flags);
return hpdev;
  -- 
  1.7.1

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

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

[Kernel-packages] [Bug 1678676] Re: linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in handle_invept()

[Thadeu Lima de Souza Cascardo]

** Changed in: linux (Ubuntu Trusty)
   Status: Triaged => 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/1678676

Title:
  linux_3.13.0-*.*: nVMX: Check current_vmcs12 before accessing in
  handle_invept()

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  KVM in linux 3.11 - 3.14 (including ubuntu 14.04 linux <= 3.13.0-113.160) has 
a
  flaw in INVEPT emulation that could crash the host.

  [ 1046.384746] BUG: unable to handle kernel NULL pointer dereference at 
0070
  [ 1046.387386] IP: [] handle_invept+0x123/0x170 [kvm_intel]
  [ 1046.389577] PGD 0 
  [ 1046.390273] Oops:  [#1] SMP 

  (tested with Ubuntu 14.04 linux-image-3.13.0-113-generic)

  The host KVM touches NULL pointer (vmx->nested.current_vmcs12) when a
  (crafted or buggy) guest issues a single-context INVEPT instruction
  *without* VMPTRLD like this:

kvm_cpu_vmxon(phys_addr);
ept_sync_context(0);

  (requires nested EPT; full linux kernel module code attached)

  This code is introduced in upstream commit 
bfd0a56b90005f8c8a004baf407ad90045c2b11e
  (nEPT: Nested INVEPT) and removed in 4b855078601fc422dbac3059f2215e776f49780f
  (KVM: nVMX: Don't advertise single context invalidation for invept).
  Therefore there should be two ways to fix this.

  a. pullup bfd0a56b90005f (and 45e11817d5703e)
  b. check current_vmcs12 before accessing for minimal fix:

  diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
  index d9e567f..d785e9c 100644
  --- a/arch/x86/kvm/vmx.c
  +++ b/arch/x86/kvm/vmx.c
  @@ -6391,6 +6391,8 @@ static int handle_invept(struct kvm_vcpu *vcpu)
   
switch (type) {
case VMX_EPT_EXTENT_CONTEXT:
  + if (to_vmx(vcpu)->nested.current_vmptr == -1ull)
  + break;
if ((operand.eptp & eptp_mask) !=
(nested_ept_get_cr3(vcpu) & eptp_mask))
break;

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

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

[Kernel-packages] [Bug 1686448] [NEW] Unable to reach higher than package C2 state with Skylake processor

[Leonardo Müller]

Public bug reported:

Hello

I have a Lenovo Ideapad 310 with a Intel Core i3-6100U. I have noticed
its battery last less time on Xubuntu 16.04 than on Windows 10. I have
searched on internet what could cause it, and found with powertop it
can't reach states higher than package C state 2, while it could reach
package C state 10.

On this particular notebook model, I would expect the battery would last
a bit more than 5 hours using only browser, as it happens with Windows
10 and CentOS 7. On Xubuntu, battery lasts slightly more than 4 hours.
The best was 4h30min, so I am having at least 30 minutes less battery
time, but generally it is one hour.

I have tried to get support on Ubuntu Forums, here is the link of the thread:
https://ubuntuforums.org/showthread.php?t=2357271

As everything we tried had no success, I am making this report.

As a reference, CentOS 7 functioned correctly and the battery lasted the
same time than Windows 10, while Fedora 25 has this problem too.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-generic 4.4.0.75.81
ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
Uname: Linux 4.4.0-75-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  usuario4786 F pulseaudio
CurrentDesktop: XFCE
Date: Wed Apr 26 12:39:30 2017
HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
InstallationDate: Installed on 2016-12-31 (116 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 80UG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro quiet
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-75-generic N/A
 linux-backports-modules-4.4.0-75-generic  N/A
 linux-firmware1.157.8
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/10/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN39WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN39WW:bd01/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.name: 80UG
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

** Attachment added: "Guidelines"
   
https://bugs.launchpad.net/bugs/1686448/+attachment/4868261/+files/lspci-vnvn.log

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

Title:
  Unable to reach higher than package C2 state with Skylake processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello

  I have a Lenovo Ideapad 310 with a Intel Core i3-6100U. I have noticed
  its battery last less time on Xubuntu 16.04 than on Windows 10. I have
  searched on internet what could cause it, and found with powertop it
  can't reach states higher than package C state 2, while it could reach
  package C state 10.

  On this particular notebook model, I would expect the battery would
  last a bit more than 5 hours using only browser, as it happens with
  Windows 10 and CentOS 7. On Xubuntu, battery lasts slightly more than
  4 hours. The best was 4h30min, so I am having at least 30 minutes less
  battery time, but generally it is one hour.

  I have tried to get support on Ubuntu Forums, here is the link of the thread:
  https://ubuntuforums.org/showthread.php?t=2357271

  As everything we tried had no success, I am making this report.

  As a reference, CentOS 7 functioned correctly and the battery lasted
  the same time than Windows 10, while Fedora 25 has this problem too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.75.81
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4786 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 26 12:39:30 2017
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2016-12-31 (116 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro quiet
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1684971] Re: [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain

[Brad Figg]

Josh,

There is a -proposed kernel with this fix. Please test asap.

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

Title:
  [Hyper-V][SAUCE] pci-hyperv: Use only 16 bit integer for PCI domain

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

Bug description:
  The following patch fixes a problem with "[PATCH] pci-hyperv: Use
  device serial number as PCI domain" where some drivers were expecting
  a u16 instead of a u32 for PCI device serial numbers, as observed by
  Oops and hangs in Azure on NC and NV GPU instances.

  From: Haiyang Zhang 

  This patch uses the lower 16 bits of the serial number as PCI
  domain, otherwise some drivers may not be able to handle it.

  Signed-off-by: Haiyang Zhang 
  ---
   drivers/pci/host/pci-hyperv.c |4 +++-
   1 files changed, 3 insertions(+), 1 deletions(-)

  diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyperv.c
  index e73880c..b18dff3 100644
  --- a/drivers/pci/host/pci-hyperv.c
  +++ b/drivers/pci/host/pci-hyperv.c
  @@ -1334,9 +1334,11 @@ static void put_pcichild(struct hv_pci_dev *hpdev,
 * can have shorter names than based on the bus instance UUID.
 * Only the first device serial number is used for domain, so the
 * domain number will not change after the first device is added.
  +  * The lower 16 bits of the serial number is used, otherwise some
  +  * drivers may not be able to handle it.
 */
if (list_empty(>children))
  - hbus->sysdata.domain = desc->ser;
  + hbus->sysdata.domain = desc->ser & 0x;
list_add_tail(>list_entry, >children);
spin_unlock_irqrestore(>device_list_lock, flags);
return hpdev;
  -- 
  1.7.1

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

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

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

Title:
  Unable to reach higher than package C2 state with Skylake processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello

  I have a Lenovo Ideapad 310 with a Intel Core i3-6100U. I have noticed
  its battery last less time on Xubuntu 16.04 than on Windows 10. I have
  searched on internet what could cause it, and found with powertop it
  can't reach states higher than package C state 2, while it could reach
  package C state 10.

  On this particular notebook model, I would expect the battery would
  last a bit more than 5 hours using only browser, as it happens with
  Windows 10 and CentOS 7. On Xubuntu, battery lasts slightly more than
  4 hours. The best was 4h30min, so I am having at least 30 minutes less
  battery time, but generally it is one hour.

  I have tried to get support on Ubuntu Forums, here is the link of the thread:
  https://ubuntuforums.org/showthread.php?t=2357271

  As everything we tried had no success, I am making this report.

  As a reference, CentOS 7 functioned correctly and the battery lasted
  the same time than Windows 10, while Fedora 25 has this problem too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.75.81
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4786 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 26 12:39:30 2017
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2016-12-31 (116 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN39WW:bd01/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1686448] Re: Unable to reach higher than package C2 state with Skylake processor

[Leonardo Müller]

** Attachment added: "Guidelines"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686448/+attachment/4868278/+files/version.log

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

Title:
  Unable to reach higher than package C2 state with Skylake processor

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello

  I have a Lenovo Ideapad 310 with a Intel Core i3-6100U. I have noticed
  its battery last less time on Xubuntu 16.04 than on Windows 10. I have
  searched on internet what could cause it, and found with powertop it
  can't reach states higher than package C state 2, while it could reach
  package C state 10.

  On this particular notebook model, I would expect the battery would
  last a bit more than 5 hours using only browser, as it happens with
  Windows 10 and CentOS 7. On Xubuntu, battery lasts slightly more than
  4 hours. The best was 4h30min, so I am having at least 30 minutes less
  battery time, but generally it is one hour.

  I have tried to get support on Ubuntu Forums, here is the link of the thread:
  https://ubuntuforums.org/showthread.php?t=2357271

  As everything we tried had no success, I am making this report.

  As a reference, CentOS 7 functioned correctly and the battery lasted
  the same time than Windows 10, while Fedora 25 has this problem too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.75.81
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4786 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Apr 26 12:39:30 2017
  HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
  InstallationDate: Installed on 2016-12-31 (116 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed 
root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN39WW:bd01/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1686040] Re: linux: 4.4.0-77.98 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => 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/1686040

Title:
  linux: 4.4.0-77.98 -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:
  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 Committed
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
Status in linux source package in Xenial:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1686305] Re: Merlin SGMII fail on Ubuntu Xenial HWE kernel

[Joseph Salisbury]

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

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

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

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

Title:
  Merlin SGMII fail on Ubuntu Xenial HWE kernel

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

Bug description:
  Using the Ubuntu Xenial HWE installation image at 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial-updates/main/installer-arm64/current/images/hwe-netboot
 to install Ubuntu into the Merlin board, the SGMII port is fail to get IP from 
DHCP.
  After installation, booting into Linux prompt, the SGMII port is fail to get 
IP from DHCP also. Checking with ethtool, the link is always report down.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 11  2016 seq
   crw-rw 1 root audio 116, 33 Feb 11  2016 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2aa90b24-e14e-4854-b52b-b853388a3466
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Merlin Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=8e10d908-38aa-4cb4-990c-4a9bcabc51a4 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-49-generic N/A
   linux-backports-modules-4.8.0-49-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-49-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: Oct 17 2016
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.06.25
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Merlin Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.06.25:bdOct172016:svnAppliedMicro:pnX-GeneMerlinBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMerlinBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Merlin Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 11  2016 seq
   crw-rw 1 root audio 116, 33 Feb 11  2016 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2aa90b24-e14e-4854-b52b-b853388a3466
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Merlin Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=8e10d908-38aa-4cb4-990c-4a9bcabc51a4 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-49-generic N/A
   linux-backports-modules-4.8.0-49-generic  N/A
   linux-firmware1.157.8
  

[Kernel-packages] [Bug 1686305] Re: Merlin SGMII fail on Ubuntu Xenial HWE kernel

[Joseph Salisbury]

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

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

Title:
  Merlin SGMII fail on Ubuntu Xenial HWE kernel

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

Bug description:
  Using the Ubuntu Xenial HWE installation image at 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial-updates/main/installer-arm64/current/images/hwe-netboot
 to install Ubuntu into the Merlin board, the SGMII port is fail to get IP from 
DHCP.
  After installation, booting into Linux prompt, the SGMII port is fail to get 
IP from DHCP also. Checking with ethtool, the link is always report down.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 11  2016 seq
   crw-rw 1 root audio 116, 33 Feb 11  2016 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2aa90b24-e14e-4854-b52b-b853388a3466
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Merlin Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=8e10d908-38aa-4cb4-990c-4a9bcabc51a4 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-49-generic N/A
   linux-backports-modules-4.8.0-49-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-49-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: Oct 17 2016
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.06.25
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Merlin Board
  dmi.board.vendor: AppliedMicro
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Not Specified
  dmi.chassis.type: 23
  dmi.chassis.vendor: AppliedMicro
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAppliedMicro:bvr3.06.25:bdOct172016:svnAppliedMicro:pnX-GeneMerlinBoard:pvr1.0:rvnAppliedMicro:rnX-GeneMerlinBoard:rvr1.0:cvnAppliedMicro:ct23:cvr1.0:
  dmi.product.name: X-Gene Merlin Board
  dmi.product.version: 1.0
  dmi.sys.vendor: AppliedMicro
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 11  2016 seq
   crw-rw 1 root audio 116, 33 Feb 11  2016 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=2aa90b24-e14e-4854-b52b-b853388a3466
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AppliedMicro X-Gene Merlin Board
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=8e10d908-38aa-4cb4-990c-4a9bcabc51a4 ro splash quiet vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-49-generic N/A
   linux-backports-modules-4.8.0-49-generic  N/A
   linux-firmware1.157.8
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.8.0-49-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: Oct 17 2016
  dmi.bios.vendor: AppliedMicro
  dmi.bios.version: 3.06.25
  dmi.board.asset.tag: Not Specified
  dmi.board.name: X-Gene Merlin Board
  dmi.board.vendor: AppliedMicro
  

[Kernel-packages] [Bug 1686040] Re: linux: 4.4.0-77.98 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the 4.4.0-77.98 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  phase: 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/1686040

Title:
  linux: 4.4.0-77.98 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  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
Status in linux source package in Xenial:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1685792] Re: Offlined CPUs of a core fail to come up online on POWER9 DD1 (Ubuntu 17.04)

[Joseph Salisbury]

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

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

Title:
  Offlined CPUs of a core fail to come up online on POWER9 DD1 (Ubuntu
  17.04)

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ranjal G. Shenoy  - 2017-04-20 08:29:13 
==
  Power9 DD1 has a hardware issue due to which  in core whose all threads are 
offlined , when any of the CPUs are onlined, they come online with an incorrect 
PACA thereby resulting in a crash.

  The following fixes sent upstream need to applied to the 17.04 kernel
  to get CPU-Hotplug working correctly on a Power9 DD1 system.

  1) powerpc/linux.git next, commit a7cd88da9704 ("powernv: Move CPU-
  Offline idle state invocation from smp.c to idle.c").

  2) powerpc/linux.git next, the commit 900612315788
  ("powerpc/powernv/smp: Add busy-wait loop as fall back for CPU-
  Hotplug").

  3) powerpc/linux.git, commit f3b3f28493d932 ("powerpc/powernv/idle:
  Don't override default/deepest directly in kernel").

  4) powerpc/linux.git next, commit 17ed4c8f81da ("powerpc/powernv:
  Recover correct PACA on wakeup from a stop on P9 DD1").

  These patches have been backported onto the 17.04 Kernel tagged
  Ubuntu-4.10.0-19.21.

  == Comment: #1 - Ranjal G. Shenoy  - 2017-04-20
  08:29:54 ==

  
  == Comment: #2 - Ranjal G. Shenoy  - 2017-04-20 08:30:37 
==

  
  == Comment: #3 - Ranjal G. Shenoy  - 2017-04-20 08:31:15 
==

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

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

[Kernel-packages] [Bug 1686362] Re: Kernel bug at nvme

[Joseph Salisbury]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc8


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

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

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

Title:
  Kernel bug at nvme

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware is HP Zbook Studio G3 with two nvme devices in m.2 slots.

  I was running three Virtualbox clients while two of them hung. Those
  two which hung were on same nvme disk while the one which remained in
  operation was another nvme disk.

  Dmesg error is attached as "kernel_bug.txt"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Apr 26 12:57:42 2017
  HibernationDevice: RESUME=UUID=976a908c-349d-4393-8d5c-aabba5f56909
  InstallationDate: Installed on 2017-02-14 (70 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: HP HP ZBook Studio G3
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=f7076591-2c4c-485d-9b65-751bf9ce132d ro acpi_osi=Linux
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (9 days ago)
  dmi.bios.date: 11/02/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.15
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.67
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.15:bd11/02/2016:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.67:cvnHP:ct10:cvr:
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

[Antonio DC]

hello thanks for your help! did your instructions above but issue still
persists. There are messages about dependencies after I complete step 5
above.

I attach a pic of the screen.


** Attachment added: "screen shit"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+attachment/4868258/+files/DSC_0050.JPG

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

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

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1680156] Re: smartpqi driver needed in initram disk and installer

[David Duffey]

Hi Brad/Leann,

Some positive feedback that at least one system now works out-of-the-box
with the 17.04 installer.

I want to verify that this driver will land in the 16.04.3 installer
(initrd).

Is it true that any modules in an interim release installer (initrd)
always will automatically also be in the LTS point release installer
(vs. just in the kernel/kernel modules package).

Thanks,

David

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

Title:
  smartpqi driver needed in initram disk and installer

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  In 17.04 we included the smartPQI driver from Microsemi and this
  request is to include the driver into initram disk so that udeb can be
  created and included in the installer kernel as well.

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

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

[Kernel-packages] [Bug 1685860] Re: linux: 4.4.0-76.97 -proposed tracker

[Kleber Sacilotto de Souza]

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

** This bug has been marked a duplicate of bug 1686040
   linux: 4.4.0-77.98 -proposed tracker

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

Title:
  linux: 4.4.0-76.97 -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:
  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:
  In Progress
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
Status in linux source package in Xenial:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[pauljohn32]

To @jsalisbury

So far so good! 28 hours with
http://kernel.ubuntu.com/~jsalisbury/lp1674838.

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-edge package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux-hwe-edge source package in Zesty:
  In Progress

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1686414] [NEW] linux: -proposed tracker

[Stefan Bader]

Public bug reported:

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

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

backports: 1686418
derivatives: 1686419

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

** Affects: linux (Ubuntu Zesty)
 Importance: Medium
 Status: Confirmed


** Tags: block-proposed block-proposed-zesty kernel-release-tracking-bug 
kernel-sru-cycle-2017.04.25-1 kernel-sru-master-kernel zesty

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

** Tags added: block-proposed

** Tags added: block-proposed-zesty

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

** Tags added: zesty

** Changed in: linux (Ubuntu Zesty)
   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/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-packages] [Bug 1658968] Re: ubuntu 16.04.2: crashed at deactivate_slab+0x18c/0x640 when testing dlpar

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   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/1658968

Title:
  ubuntu 16.04.2: crashed at deactivate_slab+0x18c/0x640 when testing
  dlpar

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem Description
  ===
  When testing cpu, memory and slot DLPAR on roselp4, the system crashed.

  ---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 
   
  Stack trace output:
   [ 3289.065350] Unable to handle kernel paging request for data at address 
0xc404565d6a00
  [ 3289.065375] Faulting instruction address: 0xc02e6eec
  [ 3289.065379] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 3289.065382] SMP NR_CPUS=2048 NUMA pSeries
  [ 3289.065386] Modules linked in: rpadlpar_io rpaphp dccp_diag dccp tcp_diag 
udp_diag inet_diag unix_diag af_packet_diag netlink_diag rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) configfs ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) mlx5_ib(OE) 
mlx5_core(OE) mlx4_ib(OE) mlx4_en(OE) ib_sa(OE) ib_mad(OE) ib_core(OE) 
ib_addr(OE) ib_netlink(OE) mlx4_core(OE) mlx_compat(OE) binfmt_misc pseries_rng 
vmx_crypto sunrpc knem(OE) autofs4 dm_round_robin btrfs xor raid6_pq lpfc 
crc32c_vpmsum ipr scsi_transport_fc devlink be2net scsi_dh_emc scsi_dh_rdac 
scsi_dh_alua dm_multipath [last unloaded: mlx4_core]
  [ 3289.065424] CPU: 82 PID: 40197 Comm: drmgr Tainted: G   OE   
4.8.0-34-generic #36~16.04.1-Ubuntu
  [ 3289.065427] task: c0045081ce00 task.stack: c0044d414000
  [ 3289.065430] NIP: c02e6eec LR: c02e7718 CTR: 
c02e7630
  [ 3289.065433] REGS: c0044d417470 TRAP: 0300   Tainted: G   OE
(4.8.0-34-generic)
  [ 3289.065435] MSR: 80010280b033   
CR: 24082822  XER: 2000
  [ 3289.065446] CFAR: c0008750 DAR: c404565d6a00 DSISR: 4000 
SOFTE: 0
 GPR00: c02e7718 c0044d4176f0 c14a6600 
c0047e01f480
 GPR04: 0010 8275 0075 
0001
 GPR08: 0200  8275 
0009
 GPR12: 84002828 c7b4e200  

 GPR16:    
c0d7a800
 GPR20: 1050 c0fd4e6c c003e7933840 
c14daae0
 GPR24: c138dc48  0001 
c0047e00fe80
 GPR28: c404565d6a00 c0047e01f480 c004565de700 
f1159740
  [ 3289.065486] NIP [c02e6eec] deactivate_slab+0x18c/0x640
  [ 3289.065489] LR [c02e7718] slab_cpuup_callback+0xe8/0x170
  [ 3289.065491] Call Trace:
  [ 3289.065493] [c0044d4176f0] [c02e715c] 
deactivate_slab+0x3fc/0x640 (unreliable)
  [ 3289.065498] [c0044d417810] [c02e7718] 
slab_cpuup_callback+0xe8/0x170
  [ 3289.065502] [c0044d417880] [c00f98c8] 
notifier_call_chain+0x98/0x110
  [ 3289.065506] [c0044d4178d0] [c00ca564] __cpu_notify+0x54/0xa0
  [ 3289.065509] [c0044d4178f0] [c00ca77c] 
cpu_notify_nofail+0x2c/0x40
  [ 3289.065512] [c0044d417910] [c00ca7e4] notify_dead+0x54/0x170
  [ 3289.065515] [c0044d4179b0] [c00c98c4] 
cpuhp_invoke_callback+0x84/0x250
  [ 3289.065519] [c0044d417a10] [c00c9bfc] 
cpuhp_down_callbacks+0x8c/0x110
  [ 3289.065523] [c0044d417a60] [c024e328] _cpu_down+0x168/0x2b0
  [ 3289.065526] [c0044d417ac0] [c00cc068] do_cpu_down+0x68/0xb0
  [ 3289.065530] [c0044d417b00] [c0738448] 
cpu_subsys_offline+0x28/0x40
  [ 3289.065534] [c0044d417b20] [c072f9e4] 
device_offline+0x104/0x140
  [ 3289.065538] [c0044d417b60] [c009a7bc] 
dlpar_cpu_remove+0x24c/0x350
  [ 3289.065542] [c0044d417c40] [c009aa50] 
dlpar_cpu_release+0x70/0xe0
  [ 3289.065545] [c0044d417c90] [c0021a04] 
arch_cpu_release+0x44/0x80
  [ 3289.065548] [c0044d417cb0] [c0738c8c] 
cpu_release_store+0x4c/0x80
  [ 3289.065552] [c0044d417ce0] [c072b7b0] dev_attr_store+0x40/0x70
  [ 3289.06] [c0044d417d00] [c03e1e1c] sysfs_kf_write+0x6c/0xa0
  [ 3289.065559] [c0044d417d20] [c03e0cdc] 
kernfs_fop_write+0x17c/0x250
  [ 3289.065563] [c0044d417d70] [c0322b20] __vfs_write+0x40/0x80
  [ 3289.065566] [c0044d417d90] [c0323ec4] vfs_write+0xd4/0x270
  [ 3289.065571] [c0044d417de0] [c0325acc] 

[Kernel-packages] [Bug 1686407] Re: linux: -proposed tracker

[Stefan Bader]

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

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

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

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

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  Invalid

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

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

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

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

[Kernel-packages] [Bug 1676678] Re: ISST-LTE:dotg6:Kernel access of bad area, sig: 11 - during stress tests

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   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/1676678

Title:
  ISST-LTE:dotg6:Kernel access of bad area, sig: 11 - during stress
  tests

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  After running stress tests (IO, TCP, BASE) for a few hours, Ubuntu 17.04 KVM 
guest dotg6 crashed, produced a kdump, and rebooted.
   
  ---uname output---
  Linux dotg6 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = KVM guest on a 8247-22L (host also running Ubuntu 17.04) 
   
   Stack trace output:
   [ 1909.621800] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 1909.621870] SMP NR_CPUS=2048
  [ 1909.621871] NUMA
  [ 1909.621925] pSeries
  [ 1909.622016] Modules linked in: minix nls_iso8859_1 rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace fscache binfmt_misc xfs libcrc32c vmx_crypto 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq dm_service_time 
crc32c_vpmsum virtio_scsi virtio_net scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [ 1909.622401] CPU: 2 PID: 27704 Comm: ppc64_cpu Not tainted 
4.10.0-13-generic #15-Ubuntu
  [ 1909.622536] task: c00042a64200 task.stack: c0003423c000
  [ 1909.622627] NIP: d16a14f4 LR: d16a14a0 CTR: 
c0609d00
  [ 1909.622737] REGS: c0003423f7f0 TRAP: 0380   Not tainted  
(4.10.0-13-generic)
  [ 1909.622850] MSR: 8280b033 
  [ 1909.622860]   CR: 24002428  XER: 2000
  [ 1909.623016] CFAR: c061a238 SOFTE: 1
  [ 1909.623016] GPR00: d16a14a0 c0003423fa70 d16ab8cc 
c00170fd5000
  [ 1909.623016] GPR04:    
7530
  [ 1909.623016] GPR08: c146c700 757465736d642f6e c146dbe0 
d16a2ef8
  [ 1909.623016] GPR12: c0609d00 c1b81200 0008 
0001
  [ 1909.623016] GPR16:    
46f05f80
  [ 1909.623016] GPR20: 46f061f8  46f05f58 
c0017fd4a808
  [ 1909.623016] GPR24: 0001 c00170fc7a30 c1326eb0 
d16a1648
  [ 1909.623016] GPR28: c1471c28 c00170fc7860 71ae4a20 
0058
  [ 1909.623990] NIP [d16a14f4] __virtscsi_set_affinity+0xac/0x200 
[virtio_scsi]
  [ 1909.624114] LR [d16a14a0] __virtscsi_set_affinity+0x58/0x200 
[virtio_scsi]
  [ 1909.624235] Call Trace:
  [ 1909.624278] [c0003423fa70] [d16a14a0] 
__virtscsi_set_affinity+0x58/0x200 [virtio_scsi] (unreliable)
  [ 1909.624445] [c0003423fac0] [d16a1678] 
virtscsi_cpu_online+0x30/0x70 [virtio_scsi]
  [ 1909.624746] [c0003423fae0] [c00db73c] 
cpuhp_invoke_callback+0x3ec/0x5a0
  [ 1909.624887] [c0003423fb50] [c00dba88] 
cpuhp_down_callbacks+0x78/0xf0
  [ 1909.625037] [c0003423fba0] [c0268bb0] _cpu_down+0x150/0x1b0
  [ 1909.625174] [c0003423fc00] [c00de1b4] do_cpu_down+0x64/0xb0
  [ 1909.625330] [c0003423fc40] [c074b834] 
cpu_subsys_offline+0x24/0x40
  [ 1909.625485] [c0003423fc60] [c0743284] device_offline+0xf4/0x130
  [ 1909.625610] [c0003423fca0] [c0743434] online_store+0x64/0xb0
  [ 1909.625736] [c0003423fce0] [c073e37c] dev_attr_store+0x3c/0x60
  [ 1909.625862] [c0003423fd00] [c03faa18] sysfs_kf_write+0x68/0xa0
  [ 1909.625984] [c0003423fd20] [c03f98bc] 
kernfs_fop_write+0x17c/0x250
  [ 1909.626132] [c0003423fd70] [c033c98c] __vfs_write+0x3c/0x70
  [ 1909.626253] [c0003423fd90] [c033e414] vfs_write+0xd4/0x240
  [ 1909.626374] [c0003423fde0] [c033ffc8] SyS_write+0x68/0x110
  [ 1909.626501] [c0003423fe30] [c000b184] system_call+0x38/0xe0
  [ 1909.626624] Instruction dump:
  [ 1909.626691] 2f89 419e0064 3be0 393f0021 3880 792926e4 7d3d4a14 
e9290010
  [ 1909.626835] 2fa9 7d234b78 419e002c e9290020  e9290058 
2fa9 7d2c4b78
  [ 1909.627003] ---[ end trace ecc8a323beb021a2 ]---

   
  crash>  bt
  PID: 27704  TASK: c00042a64200  CPU: 2   COMMAND: "ppc64_cpu"
   #0 [c0003423f630] crash_kexec at c01a04c4
   #1 [c0003423f670] oops_end at c0024da8
   #2 [c0003423f6f0] bad_page_fault at c00627b0
   #3 [c0003423f760] slb_miss_bad_addr at c0026828
   #4 [c0003423f780] bad_addr_slb at c0008acc
   Data SLB Access [380] exception frame:
   R0:  d16a14a0R1:  c0003423fa70R2:  d16ab8cc   
   R3:  c00170fd5000R4:  R5:     
   R6:  R7:  7530R8:  

[Kernel-packages] [Bug 1661684] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: drop in xmon when running dlpar tests under stress

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   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/1661684

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: drop in xmon when running dlpar
  tests under stress

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Ping Tian Han  - 2016-12-26 21:59:52 ==
  ---Problem Description---
  When testing DLPAR, include slot/cpu/mem, under stress on roselp4, system 
dropped into xmon:

  roselp4 login: [   95.511790] sysrq: SysRq : Changing Loglevel
  [   95.511816] sysrq: Loglevel set to 9
  [  289.363833] mlx4_en 0292:60:00.0: removed PHC
  [  293.123896] iommu: Removing device 0292:60:00.0 from group 3
  [  303.173744] pci_bus 0292:60: busn_res: [bus 60-ff] is released
  [  303.173865] rpadlpar_io: slot PHB 658 removed
  [  335.853779] iommu: Removing device 0021:01:00.0 from group 0
  [  345.893764] pci_bus 0021:01: busn_res: [bus 01-ff] is released
  [  345.893869] rpadlpar_io: slot PHB 33 removed
  [  382.204003] min_free_kbytes is not updated to 16885 because user defined 
value 551564 is preferred
  [  446.143648] cpu 152 (hwid 152) Ready to die...
  [  446.464057] cpu 153 (hwid 153) Ready to die...
  [  446.473525] cpu 154 (hwid 154) Ready to die...
  [  446.474077] cpu 155 (hwid 155) Ready to die...
  [  446.483529] cpu 156 (hwid 156) Ready to die...
  [  446.493532] cpu 157 (hwid 157) Ready to die...
  [  446.494078] cpu 158 (hwid 158) Ready to die...
  [  446.503527] cpu 159 (hwid 159) Ready to die...
  [  446.664534] cpu 144 (hwid 144) Ready to die...
  [  446.964113] cpu 145 (hwid 145) Ready to die...
  [  446.973525] cpu 146 (hwid 146) Ready to die...
  [  446.974094] cpu 147 (hwid 147) Ready to die...
  [  446.983944] cpu 148 (hwid 148) Ready to die...
  [  446.984062] cpu 149 (hwid 149) Ready to die...
  [  446.993518] cpu 150 (hwid 150) Ready to die...
  [  446.993543] Querying DEAD? cpu 150 (150) shows 2
  [  446.994098] cpu 151 (hwid 151) Ready to die...
  [  447.133726] cpu 136 (hwid 136) Ready to die...
  [  447.403532] cpu 137 (hwid 137) Ready to die...
  [  447.403772] cpu 138 (hwid 138) Ready to die...
  [  447.403839] cpu 139 (hwid 139) Ready to die...
  [  447.403887] cpu 140 (hwid 140) Ready to die...
  [  447.403937] cpu 141 (hwid 141) Ready to die...
  [  447.403979] cpu 142 (hwid 142) Ready to die...
  [  447.404038] cpu 143 (hwid 143) Ready to die...
  [  447.513546] cpu 128 (hwid 128) Ready to die...
  [  447.693533] cpu 129 (hwid 129) Ready to die...
  [  447.693999] cpu 130 (hwid 130) Ready to die...
  [  447.703530] cpu 131 (hwid 131) Ready to die...
  [  447.704087] Querying DEAD? cpu 132 (132) shows 2
  [  447.704102] cpu 132 (hwid 132) Ready to die...
  [  447.713534] cpu 133 (hwid 133) Ready to die...
  [  447.714064] Querying DEAD? cpu 134 (134) shows 2
  cpu 0x86: Vector: 300 (Data Access) at [c7b0fd40]
  pc: 1ec3072c
  lr: 1ec2fee0
  sp: 1faf6bd0
 msr: 800102801000
 dar: 212d6c1a2a20c
   dsisr: 4200
current = 0xc00474c6d600
paca= 0xc7b6b600   softe: 0irq_happened: 0x01
  pid   = 0, comm = swapper/134
  Linux version 4.8.0-34-generic (buildd@bos01-ppc64el-026) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu SMP Wed Dec 
21 18:53:20 UTC 2016 (Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11)
  WARNING: exception is not recoverable, can't continue
  enter ? for help
  SP (1faf6bd0) is in userspace
  86:mon> 
  86:mon> t
  SP (1faf6bd0) is in userspace
  86:mon> r
  R00 = 000212d6c1a2a20f   R16 = c0ff1c38
  R01 = 1faf6bd0   R17 = c00474c9c080
  R02 = 1ed1be80   R18 = c00474c9c000
  R03 = 1faf6c80   R19 = c13fdf08
  R04 = 0018   R20 = c00474c9c080
  R05 = 00e0   R21 = c13e8ad0
  R06 = 9e04   R22 = c00474c9c000
  R07 = 1faf6d30   R23 = c0047a9a1c40
  R08 = 1faf6d28   R24 = 0002
  R09 = 000212d6c1a2a20c   R25 = c0fd4e6c
  R10 = 1ec1b118   R26 = c0fd4e6c
  R11 = 1ee7e040   R27 = c14daae0
  R12 = 0163c1d8   R28 = 
  R13 = c7b6b600   R29 = 0086
  R14 = c14defb0   R30 = c0fd4e68
  R15 = 0001   R31 = 1faf6bd0
  pc  = 1ec3072c
  cfar= 1ec2fedc
  lr  = 1ec2fee0
  msr = 800102801000   cr  = 4200
  ctr = 1ec48788   xer = 0020   trap =  300
  dar = 000212d6c1a2a20c   dsisr = 4200
  86:mon> 

  
   
  Contact Information = Ping Tian Han/pt...@cn.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 

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Roland Kaiser]

I still think however that shipping Ubuntu kernels with pinctrl-amd
built as a blacklistable module would be an acceptable interim solution
until someone of the AMD/GIGABYTE dream team that's responsible for this
mess can deliver an actual fix.

** Tags added: bitesize kernel-oops

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Roland Kaiser]

Marc, from what I can tell, pinctrl-amd is still enabled on all the
Ubuntu kernels, including the sources in the various git repos
(git://kernel.ubuntu.com/ubuntu/ubuntu-zesty.git etc.)

And I don't think that will change. It is needed for things like
trackpads on some laptops, I believe. Meaning, completely disabling it
may be a fix for us, but it would break stuff for other people.

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1664545] Re: In Ubuntu17.04 as Kvm guest : While trigger kdump console hung having call traces

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

Title:
  In Ubuntu17.04 as Kvm guest  : While trigger kdump console hung having
  call traces

Status in The Ubuntu-power-systems project:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  In ubuntu17.04 as KVM guest on ubuntu KVM Host and trying kdump on
  guest while kdump process  console got hung having call traces

  
  Reproducible Step:

  1- Install Ubuntu17.04 as kvm guest  on ubuntu kvm host 
  2- configure kdump 
  3- trigger kdump 

  Expected Result :

  Kdump should capture

  Actual Result :

  Kdump console hung having continuous call traces

  LOG:

  [0.488534] Freeing unused kernel memory: 4416K (c8e8 - 
c92d)
  [0.488725] This architecture does not have kernel memory protection.
  Loading, please wait...
  starting version 232
  [0.501616] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.501830] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.501981] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502162] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502254] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.502433] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503188] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503270] random: udevadm: uninitialized urandom read (16 bytes read)
  [0.503978] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
  [0.504218] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
  [  242.663388] INFO: task systemd-udevd:151 blocked for more than 120 seconds.
  [  242.663514]   Not tainted 4.9.0-15-generic #16-Ubuntu
  [  242.663553] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.663755] systemd-udevd   D0   151145 0x00040002
  [  242.663795] Call Trace:
  [  242.663868] [c0001fe4ecd0] [c801c3a0] __switch_to+0x2e0/0x4c0
  [  242.663964] [c0001fe4ed30] [c8b19398] __schedule+0x2f8/0x990
  [  242.664076] [c0001fe4ee10] [c8b19a78] schedule+0x48/0xc0
  [  242.664179] [c0001fe4ee40] [c8b1de54] 
schedule_timeout+0x274/0x470
  [  242.664334] [c0001fe4ef30] [c8b19010] 
io_schedule_timeout+0xd0/0x160
  [  242.664502] [c0001fe4ef80] [c8b1a720] bit_wait_io+0x30/0x90
  [  242.664618] [c0001fe4efb0] [c8b1a168] __wait_on_bit+0xf8/0x170
  [  242.664754] [c0001fe4f000] [c824b238] 
wait_on_page_bit+0x98/0xb0
  [  242.664847] [c0001fe4f060] [c824d60c] 
do_read_cache_page+0x21c/0x4e0
  [  242.665008] [c0001fe4f0d0] [c859be78] 
read_dev_sector+0xb8/0x140
  [  242.665126] [c0001fe4f100] [c85a5d88] 
read_lba.isra.0+0x148/0x250
  [  242.665259] [c0001fe4f170] [c85a652c] efi_partition+0x12c/0x830
  [  242.665363] [c0001fe4f2e0] [c859e768] 
check_partition+0x158/0x2d0
  [  242.665469] [c0001fe4f360] [c859c760] 
rescan_partitions+0xe0/0x390
  [  242.665552] [c0001fe4f430] [c8371828] __blkdev_get+0x358/0x490
  [  242.665669] [c0001fe4f4a0] [c8372b50] blkdev_get+0x1a0/0x4a0
  [  242.665784] [c0001fe4f550] [c8599538] 
device_add_disk+0x4a8/0x500
  [  242.665894] [c0001fe4f600] [d0511cc8] 
virtblk_probe+0x560/0x928 [virtio_blk]
  [  242.665983] [c0001fe4f6c0] [c8687700] 
virtio_dev_probe+0x1d0/0x350
  [  242.666050] [c0001fe4f700] [c8716f30] 
driver_probe_device+0x240/0x540
  [  242.666116] [c0001fe4f790] [c871738c] 
__driver_attach+0x15c/0x160
  [  242.666174] [c0001fe4f810] [c87138ec] 
bus_for_each_dev+0x8c/0xf0
  [  242.666232] [c0001fe4f860] [c87162e4] driver_attach+0x34/0x50
  [  242.666289] [c0001fe4f880] [c8715a78] 
bus_add_driver+0x238/0x380
  [  242.666345] [c0001fe4f910] [c871829c] 
driver_register+0x9c/0x180
  [  242.666403] [c0001fe4f980] [c8686abc] 
register_virtio_driver+0x4c/0x60
  [  242.666470] [c0001fe4f9a0] [d0512114] init+0x84/0xd4 
[virtio_blk]
  [  242.666527] [c0001fe4fa10] [c800dde8] 
do_one_initcall+0x68/0x1d0
  [  242.666584] [c0001fe4fad0] [c8b28e00] do_init_module+0x90/0x244
  [  242.43] [c0001fe4fb60] [c8184794] load_module+0x1614/0x17a0
  [  242.666701] [c0001fe4fd30] [c8184c60] 
SyS_finit_module+0xf0/0x170
  [  242.666759] [c0001fe4fe30] [c800bd84] system_call+0x38/0xe0
  

  

[Kernel-packages] [Bug 1681909] Re: Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone.

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

Title:
  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

Status in The Ubuntu-power-systems project:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH  - 2017-03-07 
05:00:29 ==
  ---Problem Description---

  Ubuntu 17.04: dump is not captured in remote host when kdump over ssh
  is configured on firestone.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Check whether kdump is operational using ?# kdump-config show?.
  3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms.
  4. Setup password less ssh connection, generate rsa key.
  # ssh-keygen -t rsa
  5. verify id_rsa and id_rsa.pub are created under /root/.ssh/
  6. Edit /etc/default/kdump-tools and add below entries.
  SSH="ubuntu@9.114.15.239"
  SSH_KEY=/root/.ssh/id_rsa
  7. Propagate RSA key.
  # kdump-config propagate
  8. Restart kdump service.
  # kdump-config load
  9. Trigger Crash using below commands.
  # echo "1" > /proc/sys/kernel/sysrq
  # echo "c" > /proc/sysrq-trigger
  10. Verify dump is available in remote server in configured path.

  Machine details
  ===

  $ ipmitool -I lanplus -H  9.47.70.3 -U ADMIN -P admin sol activate

  $ ssh ubuntu@9.47.70.29

  PW: shriya101

  
  Attaching logs

  == Comment: #1 - PAVITHRA R. PRAKASH  -
  2017-03-07 05:01:42 ==

  
  == Comment: #5 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:19:46 ==
  Hi, 

  Attaching the logs.

  Network info:

  root@ltc-firep3:~# hwinfo --network
  36: None 00.0: 10700 Loopback   
[Created at net.126]
Unique ID: ZsBS.GQNx7L4uPNA
SysFS ID: /class/net/lo
Hardware Class: network interface
Model: "Loopback network interface"
Device File: lo
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown

  37: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 2lHw.ndpeucax6V1
Parent ID: mIXc.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f2
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f2
HW Address: 98:be:94:03:18:4a
Permanent HW Address: 98:be:94:03:18:4a
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #15 (Ethernet controller)

  38: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: 7Onn.ndpeucax6V1
Parent ID: sx0U.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f0
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f0
HW Address: 98:be:94:03:18:48
Permanent HW Address: 98:be:94:03:18:48
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (Ethernet controller)

  39: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: VwX_.ndpeucax6V1
Parent ID: DUng.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f3
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f3
HW Address: 98:be:94:03:18:4b
Permanent HW Address: 98:be:94:03:18:4b
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #25 (Ethernet controller)

  40: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: bZ1s.ndpeucax6V1
Parent ID: J7HY.aXC4wIvegH8
SysFS ID: /class/net/enP33p3s0f1
SysFS Device Link: 
/devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "tg3"
Driver Modules: "tg3"
Device File: enP33p3s0f1
HW Address: 98:be:94:03:18:49
Permanent HW Address: 98:be:94:03:18:49
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (Ethernet controller)
  root@ltc-firep3:~# 


  Thanks,
  Pavithra

  == Comment: #6 - PAVITHRA R. PRAKASH  -
  2017-03-07 23:20:47 ==

  
  == Comment: #7 - PAVITHRA R. PRAKASH  - 2017-03-07 
23:21:27 ==

  
  == Comment: #8 - Urvashi Jawere  - 2017-03-08 02:48:15 ==
  I am able to see some errors in syslog 

[Kernel-packages] [Bug 1685899] Re: [Ubuntu 17.04] - JFS related call traces and system enters xmon when rebooted after installation

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   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/1685899

Title:
  [Ubuntu 17.04] - JFS related call traces and system enters xmon when
  rebooted after installation

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Issue:
  
  JFS related call traces and system enters xmon when rebooted after 
installation 

  Steps to reproduce:
  -
  1 - Install Ubuntu 17.04 the system with 
   - prepboot
  - /root [JFS filesystem]
  - swap space

  2 -After installation when rebooted it gives out call traces like as
  below:

  [3.895246] Unable to handle kernel paging request for data at address 
0x
  [3.895278] Faulting instruction address: 0xd4c5df1c
  [3.895284] Oops: Kernel access of bad area, sig: 11 [#1]
  [3.895287] SMP NR_CPUS=2048 [3.895288] NUMA 
  [3.895290] pSeries
  [3.895292] Modules linked in: ip_tables x_tables autofs4 jfs ibmvscsi 
crc32c_vpmsum
  [3.895301] CPU: 30 PID: 923 Comm: ureadahead Not tainted 4.9.0-15-generic 
#16-Ubuntu
  [3.895304] task: c00381d3c800 task.stack: c00381fd
  [3.895307] NIP: d4c5df1c LR: d4c5deb0 CTR: 
c01279d0
  [3.895310] REGS: c00381fd3500 TRAP: 0300   Not tainted  
(4.9.0-15-generic)
  [3.895313] MSR: 8280b033 [
3.895322]   CR: 48008804  XER: 0001
  [3.895324] CFAR: c0008a60 DAR:  DSISR: 4000 
SOFTE: 1 
  GPR00: d4c5deb0 c00381fd3780 d4c78c28 c003802f40f0 
  GPR04: d4c6f6f0 d4c72b58 0563 d4c78c28 
  GPR08:  00180e97  d4c6a608 
  GPR12: c01279d0 cfb90e00   
  GPR16:     
  GPR20:     
  GPR24:  1000  d4c72b38 
  GPR28: 00180e97 f0e1d5c0 c003812af240 c003802f40b0 
  NIP [d4c5df1c] __get_metapage+0x204/0x6f0 [jfs]
  [3.895372] LR [d4c5deb0] __get_metapage+0x198/0x6f0 [jfs]
  [3.895374] Call Trace:
  [3.895378] [c00381fd3780] [d4c5de6c] 
__get_metapage+0x154/0x6f0 [jfs] (unreliable)
  [3.895384] [c00381fd3870] [d4c4c368] diRead+0x130/0x260 [jfs]
  [3.895388] [c00381fd3920] [d4c424f4] jfs_iget+0x6c/0x1e0 [jfs]
  [3.895393] [c00381fd3950] [d4c43adc] jfs_lookup+0xe4/0x100 
[jfs]
  [3.895398] [c00381fd3a80] [c032a120] lookup_slow+0xe0/0x240
  [3.895402] [c00381fd3b00] [c032e8a8] 
walk_component+0x2d8/0x3f0
  [3.895406] [c00381fd3b70] [c032eb94] 
link_path_walk+0x1d4/0x600
  [3.895409] [c00381fd3c00] [c0330c1c] path_openat+0xbc/0x480
  [3.895413] [c00381fd3c80] [c03328ac] do_filp_open+0xec/0x160
  [3.895417] [c00381fd3db0] [c031863c] do_sys_open+0x1cc/0x380
  [3.895421] [c00381fd3e30] [c000bd84] system_call+0x38/0xe0
  [3.895424] Instruction dump:
  [3.895426] 7909f00e 7fc9f214 3921 f93f0028 fbdf0030 e93d 71280800 
41820460 
  [3.895433] ebdd0030 41920034 e91d0008 e93f0038  811e 
80e70090 39080001 
  [3.895441] ---[ end trace c2aa9ba09ea05eac ]---
  [3.895443] 
  [4.088560] systemd-journald[925]: Received request to flush runtime 
journal from PID 1
  [4.362062] crypto_register_alg 'aes' = 0
  [4.362112] crypto_register_alg 'cbc(aes)' = 0
  [4.362150] crypto_register_alg 'ctr(aes)' = 0
  [4.362191] crypto_register_alg 'xts(aes)' = 0
  [4.366949] pseries_rng: Registering IBM pSeries RNG driver

  When I first connected to the LPAR, it was unresponsive so I restarted
  it from the HMC and surprisingly it came up to the login prompt and I
  logged into the shell. I proceeded to install the matching linux-
  image-4.10.0-15-generic-dbgsym_4.10.0-15.17_ppc64el.ddeb. However, the
  installation of the matching dbgsym wasn't as helpful as I wanted it
  to be. objdump, crash tool, or addr2line wouldn't give me the source
  line correspond to the NIP address.

  I then restarted the LPAR with xmon enabled and it would drop to xmon
  immediately after attempting to remount / and at the same location as
  before at __get_metapage+0x204/0x6f0 [jfs] and again with a
  dereference of 0x0 as the cause of the data exception

  0xd649df54 <__get_metapage+508>:ld  r8,8(r29)
  0xd649df58 <__get_metapage+512>:ld  r9,56(r31)
  0xd649df5c <__get_metapage+516>:ld  

[Kernel-packages] [Bug 1680349] Re: Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine crashes while running stress-ng.

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   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/1680349

Title:
  Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine
  crashes while running stress-ng.

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-03-10 02:43:10 ==
  ---Problem Description---

  Ubuntu 17.04: Kdump fails to capture dump on Firestone NV when machine
  crashes while running stress-ng. Machine hangs.

  ---Steps to Reproduce---

  1. Configure kdump.
  2. Install stress-ng
  # apt-get install stress-ng
  3. Run stress-ng
  # stress-ng - a 0

  
  Logs:
  
  root@ltc-firep3:~# kdump-config load
  Modified cmdline:root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet 
splash irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0 elfcorehdr=155200K 
   * loaded kdump kernel
  root@ltc-firep3:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.10.0-11-generic
  kdump initrd: 
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.10.0-11-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=8b0d5b99-6087-4f40-82ea-375c83a4c139 ro quiet splash 
irqpoll nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz
  root@ltc-firep3:~# stress-ng -a 0
  stress-ng: info:  [3900] defaulting to a 86400 second run per stressor
  stress-ng: info:  [3900] dispatching hogs: 160 af-alg, 160 affinity, 160 aio, 
160 aiol, 160 apparmor, 160 atomic, 160 bigheap, 160 brk, 160 bsearch, 160 
cache, 160 cap, 160 chdir, 160 chmod, 160 chown, 160 chroot, 160 clock, 160 
clone, 160 context, 160 copy-file, 160 cpu, 160 cpu-online, 160 crypt, 160 
daemon, 160 dccp, 160 dentry, 160 dir, 160 dirdeep, 160 dnotify, 160 dup, 160 
epoll, 160 eventfd, 160 exec, 160 fallocate, 160 fanotify, 160 fault, 160 
fcntl, 160 fiemap, 160 fifo, 160 filename, 160 flock, 160 fork, 160 fp-error, 
160 fstat, 160 full, 160 futex, 160 get, 160 getdent, 160 getrandom, 160 
handle, 160 hdd, 160 heapsort, 160 hsearch, 160 icache, 160 icmp-flood, 160 
inotify, 160 io, 160 iomix, 160 ioprio, 160 itimer, 160 kcmp, 160 key, 160 
kill, 160 klog, 160 lease, 160 link, 160 locka, 160 lockbus, 160 lockf, 160 
lockofd, 160 longjmp, 160 lsearch, 160 madvise, 160 malloc, 160 matrix, 160 
membarrier, 160 memcpy, 160 memfd, 160 mergesort, 160 mincore, 160 mknod, 160 
mlock, 1
 60 mmap, 160 mmapfork, 160 mmapmany, 160 mq, 160 mremap, 160 msg, 160 msync, 
160 netlink-proc, 160 nice, 160 nop, 160 null, 160 numa, 160 oom-pipe, 160 
opcode, 160 open, 160 personality, 160 pipe, 160 poll, 160 procfs, 160 pthread, 
160 ptrace, 160 pty, 160 qsort, 160 quota, 160 rdrand, 160 readahead, 160 
remap, 160 rename, 160 resources, 160 rlimit, 160 rmap, 160 rtc, 160 
schedpolicy, 160 sctp, 160 seal, 160 seccomp, 160 seek, 160 sem, 160 sem-sysv, 
160 sendfile, 160 shm, 160 shm-sysv, 160 sigfd, 160 sigfpe, 160 sigpending, 160 
sigq, 160 sigsegv, 160 sigsuspend, 160 sleep, 160 sock, 160 sockfd, 160 
sockpair, 160 spawn, 160 splice, 160 stack, 160 stackmmap, 160 str, 160 stream, 
160 switch, 160 symlink, 160 sync-file, 160 sysfs, 160 sysinfo, 160 tee, 160 
timer, 160 timerfd, 160 tlb-shootdown, 160 tmpfs, 160 tsc, 160 tsearch, 160 
udp, 160 udp-flood, 160 unshare, 160 urandom, 160 userfaultfd, 160 utime, 160 
vecmath, 160 vfork, 160 vforkmany, 160 vm, 160 vm-rw, 160 vm-splice, 160 wait, 1
 60 wcs, 160 xattr, 160 yield, 160 zero, 160 zlib, 160 zombie
  stress-ng: info:  [3900] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [3900] cache allocate: default cache size: 2048K
  stress-ng: info:  [3907] stress-ng-atomic: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [3955] stress-ng-exec: running as root, won't run test.
  stress-ng: info:  [3999] stress-ng-icache: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4040] stress-ng-lockbus: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: info:  [4313] stress-ng-numa: system has 2 of a maximum 256 memory 
NUMA nodes
  stress-ng: info:  [4455] stress-ng-rdrand: this stressor is not implemented 
on this system: ppc64le Linux 4.10.0-11-generic
  stress-ng: fail:  [4558] stress-ng-rtc: ioctl RTC_ALRM_READ failed, errno=22 
(Invalid argument)
  stress-ng: fail:  [4017] stress-ng-key: keyctl KEYCTL_DESCRIBE failed, 

[Kernel-packages] [Bug 1678745] Re: Ubuntu17.04 KVM: Guest crashed @ xfs_perag_get_tag+0x6c

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   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/1678745

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

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

   85 rcu_read_lock();  
 
   86 found = radix_tree_gang_lookup_tag(>m_perag_tree, 
 
  

[Kernel-packages] [Bug 1677685] Re: Target: Configfs Crashes and kernel crash fixes

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   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/1677685

Title:
  Target: Configfs Crashes and kernel crash fixes

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  A number of patches that need to be backported for target subsystem.

  target: Don't BUG_ON during NodeACL dynamic -> explicit conversion
  https://patchwork.kernel.org/patch/9560085/

  target: Use correct SCSI status during EXTENDED_COPY exception
  https://patchwork.kernel.org/patch/9560083/

  target: Fix early transport_generic_handle_tmr abort scenario
  https://patchwork.kernel.org/patch/9560077/

  target: Fix multi-session dynamic se_node_acl double free OOPs
  https://patchwork.kernel.org/patch/9560081/

  target: Fix COMPARE_AND_WRITE ref leak for non GOOD status
  https://patchwork.kernel.org/patch/9560065/

  target: Fix NULL dereference during LUN lookup + active I/O shutdown
  https://patchwork.kernel.org/patch/9587799/

  target: Avoid mappedlun symlink creation during lun shutdown
  https://lkml.org/lkml/2017/3/30/180

   
  Contact Information = Bryant G. Ly/b...@us.ibm.com

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

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

[Kernel-packages] [Bug 1676884] Re: kdump-tools uses the wrong crashkernel command line parameter in ppc64le

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

Title:
  kdump-tools uses the wrong crashkernel command line parameter in
  ppc64le

Status in The Ubuntu-power-systems project:
  New
Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Thiago Jung Bauermann  - 2017-03-24 
11:44:39 ==
  ---Problem Description---
  kdump-tools uses the wrong crashkernel command line parameter in ppc64le:

  u1704le?? grep crashkernel /boot/grub/grub.cfg
  linux   /boot/vmlinux-4.10.0-13-generic 
root=UUID=2d6f73c7-b463-4f02-9ec4-8d4afed0635d ro   crashkernel=384M-:128M

  128M of reserved memory is too small for ppc64le.

  That happens because /etc/default/grub.d/kdump-tools.cfg links to the
  wrong file:

  u1704le??  ls -l /etc/default/grub.d/
  total 8.0K
  lrwxrwxrwx 1 root root  39 Mar 24 13:34 kdump-tools.cfg -> 
/etc/default/grub.d/kdump-tools.default
  -rw-r--r-- 1 root root  80 Jan  5 08:07 kdump-tools.default
  -rw-r--r-- 1 root root 137 Jan  5 08:07 kdump-tools..ppc64el
  u1704le?? 

  As can be seen, it should be pointing to kdump-tools..ppc64el but
  isn't.

  Also, kdump-tools..ppc64el has two dots in it. That doesn't seem right.
  Possibly just a cosmetic issue, but it would be nice if that was fixed.
   
  Contact Information = thiag...@br.ibm.com 
   
  ---uname output---
  Linux u1704le 4.10.0-13-generic #15-Ubuntu SMP Thu Mar 9 20:27:28 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Any ppc64le machine. In this case, a KVM guest hosted on an 
8286-42A. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   sudo apt intall kdump-tools
  Select 'Yes' when asked whether kdump should be enabled.
   
  Userspace tool common name: kdump 
   
  The userspace tool has the following bit modes: 64 bit 

  Userspace rpm: kdump-tools

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for thiag...@br.ibm.com:
  -Attach ltrace and strace of userspace application.

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

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

[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

[Philipp Ludwig]

>From the top of my head:

1) In grub, select Advanced options, then recovery mode
2) Select "Drop to root shell"
3) Press Enter to confirm
4) The filesystem is mounted read-only at this point, so remount it: mount -o 
rw,remount /
5) Install the needed package: apt install xserver-xorg-input-all
6) Press Ctrl+D to leave the root shell.
7) Select resume boot from the menu.

Here are some more information regarding the recovery mode:
https://wiki.ubuntu.com/RecoveryMode

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

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

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

[Antonio DC]

hello, have exact same problem. Upgraded to 16.10 from a working 16.04
and now when 16.10 boots up I'm I cant login because the mouse and
keyboard do not work. It connects to WiFi without issues.

How could I install the xserver-xorg-input-all without a working
keyboard/mouse?

The keyboard works when I go into the advanced menu options. I'm still a
novice user of Ubuntu any instructions would help!!

thank you

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

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

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1685792] Re: Offlined CPUs of a core fail to come up online on POWER9 DD1 (Ubuntu 17.04)

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  Offlined CPUs of a core fail to come up online on POWER9 DD1 (Ubuntu
  17.04)

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ranjal G. Shenoy  - 2017-04-20 08:29:13 
==
  Power9 DD1 has a hardware issue due to which  in core whose all threads are 
offlined , when any of the CPUs are onlined, they come online with an incorrect 
PACA thereby resulting in a crash.

  The following fixes sent upstream need to applied to the 17.04 kernel
  to get CPU-Hotplug working correctly on a Power9 DD1 system.

  1) powerpc/linux.git next, commit a7cd88da9704 ("powernv: Move CPU-
  Offline idle state invocation from smp.c to idle.c").

  2) powerpc/linux.git next, the commit 900612315788
  ("powerpc/powernv/smp: Add busy-wait loop as fall back for CPU-
  Hotplug").

  3) powerpc/linux.git, commit f3b3f28493d932 ("powerpc/powernv/idle:
  Don't override default/deepest directly in kernel").

  4) powerpc/linux.git next, commit 17ed4c8f81da ("powerpc/powernv:
  Recover correct PACA on wakeup from a stop on P9 DD1").

  These patches have been backported onto the 17.04 Kernel tagged
  Ubuntu-4.10.0-19.21.

  == Comment: #1 - Ranjal G. Shenoy  - 2017-04-20
  08:29:54 ==

  
  == Comment: #2 - Ranjal G. Shenoy  - 2017-04-20 08:30:37 
==

  
  == Comment: #3 - Ranjal G. Shenoy  - 2017-04-20 08:31:15 
==

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

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

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   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/1655280

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

Status in The Ubuntu-power-systems project:
  New
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-power-systems/+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 1667245] Re: ISST-LTE:pVM:roselp4:ubuntu 17.04: kdump failed after memory DLPAR

[Manoj Iyer]

** Also affects: ubuntu-power-systems
   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/1667245

Title:
  ISST-LTE:pVM:roselp4:ubuntu 17.04: kdump failed after memory DLPAR

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  After a memory DLPAR removal, kdump doesn't work:

   Starting Kernel crash dump capture service...
  [   67.714593] kdump-tools[3850]: Starting kdump-tools:  * running 
makedumpfile -c -d 31 /proc/vmcore /var/crash/201702230005/dump-incomplete
  Copying data   : [  2.1 %] -/usr/sbin/kdump-config: line 
639:  3897 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [   72.314140] kdump-tools[3850]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [   73.693881] kdump-tools[3850]: cp: error reading '/proc/vmcore': Bad 
address
  [   73.704152] kdump-tools[3850]:  * kdump-tools: failed to save vmcore in 
/var/crash/201702230005
  [   73.823643] kdump-tools[3850]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201702230005/dmesg.201702230005
  [   73.973813] kdump-tools[3850]: The kernel version is not supported.
  [   73.974078] kdump-tools[3850]: The makedumpfile operation may be 
incomplete.
  [   73.983506] kdump-tools[3850]: The dmesg log is saved to 
/var/crash/201702230005/dmesg.201702230005.
  [   73.983752] kdump-tools[3850]: makedumpfile Completed.
  [   73.983998] kdump-tools[3850]:  * kdump-tools: saved dmesg content in 
/var/crash/201702230005
  [   74.104555] kdump-tools[3850]: Thu, 23 Feb 2017 00:05:15 -0600
  [   74.233502] kdump-tools[3850]: Failed to read reboot parameter file: No 
such file or directory
  [   74.233782] kdump-tools[3850]: Rebooting.
  [   86.629777] reboot: Restarting system

  
  The kdump service should be restarted after the memory DLPAR operation.
   
  C
  ---uname output---
  Linux roselp4 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. config kdump on roselp4
  2. do a memory DLPAR removal operation
  3. trigger kdump

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

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

[Kernel-packages] [Bug 1649513] Re: [Ubuntu 16.10] NMI watchdog and soft lockup while running htx memory tests in kernel 4.8.0-17-generic

[Andrew Cloke]

** Also affects: ubuntu-power-systems
   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/1649513

Title:
  [Ubuntu 16.10] NMI watchdog and soft lockup while running htx memory
  tests in kernel 4.8.0-17-generic

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue:
  --
  NMI Watchdog Bug and soft lockup occurs when htx memory test is run in ubuntu 
16.10.

  Environment:
  --
  Arch : ppc64le
  Platform : Ubuntu KVM Guest
  Host : ubuntu 16.10 [4.8.0-17 -kernel ]
  Guest : ubuntu 16.10 [4.8.0-17 - Kernel]

  Steps To Reproduce:
  ---

  1 - Install a Ubuntu KVM Guest and install htx package in the guest got from 
the link,
  http://ausgsa.ibm.com/projects/h/htx/public_html/htxonly/htxubuntu-413.deb 

  2 - Run the Htx mdt.mem

  3 - The system Hits soft lockup Issue as below:

  dmesg o/p:
  [60287.590335] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 1141s! 
[hxemem64:23468]
  [60287.590572] Modules linked in: vmx_crypto ip_tables x_tables autofs4 
ibmvscsi crc32c_vpmsum
  [60287.590585] CPU: 3 PID: 23468 Comm: hxemem64 Tainted: G L  
4.8.0-17-generic #19-Ubuntu
  [60287.590587] task: c012a0971e00 task.stack: c012a2d4
  [60287.590589] NIP: c0015004 LR: c0015004 CTR: 
c0165e90
  [60287.590591] REGS: c012a2d439a0 TRAP: 0901   Tainted: G L   
(4.8.0-17-generic)
  [60287.590592] MSR: 80009033   CR: 48004244  
XER: 
  [60287.590603] CFAR: c0165890 SOFTE: 1 
 GPR00: c0165f9c c012a2d43c20 c14e5e00 
0900 
 GPR04:  0008 000100e4d61a 
 
 GPR08:  0006 000100e4d619 
c012bfee3130 
 GPR12: 3fffae6cdc70 3fffae436900 
  [60287.590627] NIP [c0015004] arch_local_irq_restore+0x74/0x90
  [60287.590630] LR [c0015004] arch_local_irq_restore+0x74/0x90
  [60287.590631] Call Trace:
  [60287.590634] [c012a2d43c20] [c012bfeccd80] 0xc012bfeccd80 
(unreliable)
  [60287.590639] [c012a2d43c40] [c0165f9c] 
run_timer_softirq+0x10c/0x230
  [60287.590644] [c012a2d43ce0] [c0b94adc] __do_softirq+0x18c/0x3fc
  [60287.590648] [c012a2d43de0] [c00d5828] irq_exit+0xc8/0x100
  [60287.590653] [c012a2d43e00] [c0024810] timer_interrupt+0xa0/0xe0
  [60287.590657] [c012a2d43e30] [c0002814] 
decrementer_common+0x114/0x180
  [60287.590659] Instruction dump:
  [60287.590662] 994d023a 2fa3 409e0024 e92d0020 61298000 7d210164 38210020 
e8010010 
  [60287.590670] 7c0803a6 4e800020 6042 4bfed259 <6000> 4be4 
6042 e92d0020 
  [63127.581494] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 339s! 
[hxemem64:23467]
  [63127.629682] Modules linked in: vmx_crypto ip_tables x_tables autofs4 
ibmvscsi crc32c_vpmsum
  [63127.629699] CPU: 2 PID: 23467 Comm: hxemem64 Tainted: G L  
4.8.0-17-generic #19-Ubuntu
  [63127.629701] task: c012a0965800 task.stack: c012a2d58000
  [63127.629703] NIP: 10011e60 LR: 1000ec6c CTR: 
00f33196
  [63127.629706] REGS: c012a2d5bea0 TRAP: 0901   Tainted: G L   
(4.8.0-17-generic)
  [63127.629707] MSR: 8001d033   CR: 
42004482  XER: 
  [63127.629719] CFAR: 10011e68 SOFTE: 1 
 GPR00: 1000e854 3fffadc2e540 10047f00 
000d 
 GPR04: 0200 3ff5a800 5a5a5a5a5a5a5a5a 
3ff5b0667348 
 GPR08:  1006c8e0 1006ca04 
f001 
 GPR12: 3fffae6cdc70 3fffadc36900 
  [63127.629740] NIP [10011e60] 0x10011e60
  [63127.629742] LR [1000ec6c] 0x1000ec6c
  [63127.629743] Call Trace:

  == Comment: #3 - Santhosh G  - 2016-09-28 02:17:29 ==
  Memory Info :

  root@ubuntu:~# cat /proc/meminfo 
  MemTotal:   78539776 kB
  MemFree:72219392 kB
  MemAvailable:   77217088 kB
  Buffers:  212544 kB
  Cached:  5249088 kB
  SwapCached:0 kB
  Active:  1440832 kB
  Inactive:4107264 kB
  Active(anon):  93888 kB
  Inactive(anon): 8640 kB
  Active(file):1346944 kB
  Inactive(file):  4098624 kB
  Unevictable:   0 kB
  Mlocked:   0 kB
  SwapTotal:   3443648 kB
  SwapFree:3443648 kB
  Dirty: 0 kB
  Writeback: 0 kB
  AnonPages: 87296 kB
  Mapped:30400 kB
  Shmem: 16128 kB
  Slab: 381440 kB
  SReclaimable: 295872 kB