[Kernel-packages] [Bug 1766052] [NEW] Incorrect blacklist of bcm2835_wdt

[Kees Cook]

Public bug reported:

Without bcm2835_wdt loaded, Raspberry Pi systems cannot reboot or shut
down. This needs to be removed from the automatic blacklist generated by
the kernel build that ends up in /lib/modprobe.d/blacklist_linux_$(uname
-r).conf

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

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

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

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

** Also affects: linux (Ubuntu Artful)
   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/1766052

Title:
  Incorrect blacklist of bcm2835_wdt

Status in linux package in Ubuntu:
  New
Status in linux source package in Artful:
  New
Status in linux source package in Bionic:
  New

Bug description:
  Without bcm2835_wdt loaded, Raspberry Pi systems cannot reboot or shut
  down. This needs to be removed from the automatic blacklist generated
  by the kernel build that ends up in
  /lib/modprobe.d/blacklist_linux_$(uname -r).conf

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

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

[Kernel-packages] [Bug 1738907] Re: Bluetooth audio latency / delay increasing on video streamig

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth audio latency / delay increasing on video streamig

Status in bluez package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  With my bluetooth headset (A2DP audio protocole) when I watch videos
  streaming with Google Chrome for example. there is a delay increasing
  between audio and video. I tried to change and set up the audio
  latency, but the delay increase, as much as I play bigger video

  
  ubuntu 17.04 or 17.10 64bit

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

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

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

[Launchpad Bug Tracker]

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

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

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

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

Status in linux package in Ubuntu:
  Expired

Bug description:
  Just getting popups on my screen.  Using RDP to connect to the
  desktop.  Unity is default desktop, but loaded mate desktop for rdp to
  work. Not sure what is going on. This is the second error today after
  starting up machine.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1540 F pulseaudio
   /dev/snd/controlC1:  lightdm1540 F pulseaudio
  Date: Fri Feb 16 11:16:07 2018
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=fedbd636-d843-40cb-9003-3e8505325e9c
  InstallationDate: Installed on 2017-12-22 (55 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic.efi.signed 
root=UUID=86d8fd5d-5f2e-46c8-8512-da2f3d0e2e4a ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-112-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF21:bd02/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming 5
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1749765] Re: BUG: Bad page state in process cc1 pfn:b4867

[Launchpad Bug Tracker]

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

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

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

Title:
  BUG: Bad page state in process cc1  pfn:b4867

Status in linux package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  This error happened while I compiled a package. I can not remember if
  it was ffmpeg or OBS.

  The system continued to issue warning windows of the same error after
  closing the previous window.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Thu Feb 15 14:22:26 2018
  Failure: oops
  InstallationDate: Installed on 2018-02-14 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H81M-S2PH
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=3bdb708f-d6b5-4647-b266-3701c00353e3 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad page state in process cc1  pfn:b4867
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-S2PH
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd08/10/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S2PH:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S2PH:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81M-S2PH
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1738907] Re: Bluetooth audio latency / delay increasing on video streamig

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth audio latency / delay increasing on video streamig

Status in bluez package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  With my bluetooth headset (A2DP audio protocole) when I watch videos
  streaming with Google Chrome for example. there is a delay increasing
  between audio and video. I tried to change and set up the audio
  latency, but the delay increase, as much as I play bigger video

  
  ubuntu 17.04 or 17.10 64bit

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

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

[Kernel-packages] [Bug 1750070] Re: package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Expired

Bug description:
  performed:
  sudo apt-get update

  followed by:
  sudo apt-get upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul   5973 F pulseaudio
  Date: Fri Feb 16 21:48:36 2018
  DuplicateSignature:
   package:linux-image-4.4.0-34-generic:4.4.0-34.53
   Setting up linux-image-4.4.0-34-generic (4.4.0-34.53) ...
   Internal Error: Could not find image (/boot/vmlinuz-4.4.0-34-generic)
   dpkg: error processing package linux-image-4.4.0-34-generic (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=194c1b14-cd87-4c9c-b743-538c5a66de00
  InstallationDate: Installed on 2015-05-18 (1005 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Dell Inc. Inspiron 1545
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.16
  SourcePackage: linux
  Title: package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd02/25/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1750232] Re: Linux Mint/Ubuntu is taking modem off-hook during logon

[Launchpad Bug Tracker]

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

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

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

Title:
  Linux Mint/Ubuntu is taking modem off-hook during logon

Status in linux package in Ubuntu:
  Expired

Bug description:
  As of 15 February 2018 (and possibly earlier) the following bug has
  been reintroduced:

  When Linux Mint (Cinnamon OR Mate) OR UBUNTU starts up (_after_ the
  login screen), the Smartlink internal modem is taken off hook, and
  remains off hook (disabling the telephone line) until such time as the
  system is shut down or rebooted (in which case it goes off hook again
  after login).

  This annoying bug was introduced with Linux Mint 17.0 Trusty, and also
  occurs with Ubuntu 14.04. It disappeared with Linux Mint 18.0 Xenial
  (which is based on Ubuntu 16.04). Now it is back, possibly as a result
  of the latest updates, possibly earlier.

  Yes, since Linux no longer supports the Smartlink modem, even with the
  modifications to the kernel that previously worked, I could simply
  disconnect the internal modem. But I dual-boot to Windoze, and DO use
  it without problem in Windoze, so it is more than an annoyance.

  I can understand Linux not supporting hardware, but it is unacceptable
  that Linux is sending commands to unsupported hardware whihc cause it
  to malfunction.

  As a Linux USER, I have no way of isolating the component causing the
  bug. It will require a trace of what is written to the COM port(s)
  during login. But, since it was fixed before, there should be some
  record of the cause and solution.

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

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

[Kernel-packages] [Bug 1750226] Re: BUG: Bad rss-counter state mm:ffff8b256d6f4200 idx:0 val:-2

[Launchpad Bug Tracker]

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

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

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

Title:
  BUG: Bad rss-counter state mm:8b256d6f4200 idx:0 val:-2

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Bionic:
  Expired

Bug description:
  Automatic bug kernel oops on 18.04 devel branch @ 18/2/2018

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 731 F pulseaudio
lotuspsychje   1437 F pulseaudio
  Date: Sun Feb 18 12:16:11 2018
  Failure: oops
  InstallationDate: Installed on 2017-12-16 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215)
  OopsText:
   BUG: Bad rss-counter state mm:8b256d6f4200 idx:0 val:-2
   BUG: Bad rss-counter state mm:8b256d6f4200 idx:3 val:2
   ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
   ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
   ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=c2cc7350-42f8-4953-840d-8330750d7f5c ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:8b256d6f4200 idx:0 val:-2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: KV8-MAX3 (VIA K8T800-8237)
  dmi.board.vendor: http://www.abit.com.tw/
  dmi.board.version: 1.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/29/2004:svn:pn:pvr:rvnhttp//www.abit.com.tw/:rnKV8-MAX3(VIAK8T800-8237):rvr1.x:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1750077] Re: ??

[Launchpad Bug Tracker]

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

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

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

Title:
  ??

Status in linux package in Ubuntu:
  Expired

Bug description:
  ubuntu was doing partial upgrade and this error stuff popped up.

  sorry I cant help anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  dminor2351   1620 F pulseaudio
   /dev/snd/pcmC0D0p:   dminor2351   1620 F...m pulseaudio
   /dev/snd/controlC0:  dminor2351   1620 F pulseaudio
   /dev/snd/controlC2:  dminor2351   1620 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb 16 17:54:58 2018
  HibernationDevice: RESUME=UUID=189383ed-0452-465f-bb0e-64c387d088b5
  InstallationDate: Installed on 2014-04-09 (1409 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=6c63c703-d60d-4b3f-902a-5bc074517498 ro plymouth:debug drm.debug=0xe
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.16
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2005
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS A8N-E ACPI BIOS Revision 1004
  dmi.board.name: A8N-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 2.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-EACPIBIOSRevision1004:bd05/20/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-E:rvr2.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1750156] Re: Touchpad not recognised on ASUS FX553V since install

[Launchpad Bug Tracker]

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

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

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

Title:
  Touchpad not recognised on ASUS FX553V since install

Status in linux package in Ubuntu:
  Expired

Bug description:
  I installed Ubuntu 16.04 several months ago and have been using
  external mouse since then because the touchpad never worked. (Works
  under Windows.) Now upgraded to 17.10 but the problem persists.

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

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

[Kernel-packages] [Bug 1750440] Re: package linux-image-extra-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-extra-4.13.0-32-generic 4.13.0-32.35 failed to
  install/upgrade: subprocess installed post-removal script returned
  error exit status 1

Status in linux package in Ubuntu:
  Expired

Bug description:
  This package failed when I ran an `apt autoremove`.  In particular, it
  appeared to fail as part of some sort of DKMS process.

  The first time I ran `apt autoremove` the DKMS process hung and apt
  stalled at 50% progress.  I had to kill the process for apt to
  continue.

  The second time I ran `apt autoremove` the apt process stalled at 33%
  progress and eventually the crash detector ran and prompted me to
  report this bug.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-extra-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-35.39-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm4604 F pulseaudio
drbarret   5314 F pulseaudio
   /dev/snd/controlC0:  gdm4604 F pulseaudio
drbarret   5314 F pulseaudio
  Date: Mon Feb 19 15:12:14 2018
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=a63bd4bc-211b-488c-8af4-71983fced9d2
  InstallationDate: Installed on 2017-04-01 (324 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Precision M4800
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-35-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-extra-4.13.0-32-generic 4.13.0-32.35 failed to 
install/upgrade: subprocess installed post-removal script returned error exit 
status 1
  UpgradeStatus: Upgraded to artful on 2018-01-22 (28 days ago)
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0T3YTY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd12/22/2016:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

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

[bugproxy]

--- Comment From dnban...@us.ibm.com 2018-04-21 23:43 EDT---
The kernel mentioned in #114 was a quick, rough attempt to force one instance
of free_work/del_work pending at a time.

With that, the machine still seems to be up.

root@boslcp3:~# uptime
22:21:50 up  3:41,  2 users,  load average: 77.72, 82.67, 81.90
root@boslcp3:~# virsh list
IdName   State

1 boslcp3g3  running
2 boslcp3g4  running
4 boslcp3g1  running

And the logs still look clean!

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr 

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

[bugproxy]

--- Comment From dnban...@us.ibm.com 2018-04-21 23:33 EDT---
Continuing from the description at #84...

This is going to be long post. I debated putting it as as
attachment but placing it in the main body will probably
help in searching in the future.

===

So the pool_mayday_timeout() routine basically walked into the
weird/corrupted work item on the pool workqueue corresponding to
cpu 0x68 (104). So the critical question is who may have put
that item there with the strange work->data value
data = R10: 2040

BTW, pool_mayday_timeout got the pool thus:

static void pool_mayday_timeout(struct timer_list *t)
{
struct worker_pool *pool = from_timer(pool, t, mayday_timer);
and then ...
list_for_each_entry(work, >worklist, entry)
send_mayday(work);
}

This is the timer:

struct timer_list {
entry = {
next = 0x5deadbeef200,
pprev = 0x0
},
expires = 0x1018d5103,
function = 0xc012e790 ,
flags = 0x168
}

crash> rd jiffies
c1713b00:  0001018d5380.S..

The corresponding worker pool:
-
struct worker_pool {
lock = {
{
rlock = {
raw_lock = {
slock = 0x8068
}
}
}
},
cpu = 0x68,
node = 0x8,
id = 0xd0,  Note the id!
flags = 0x1,
watchdog_ts = 0x1018d50b0,
worklist = {
next = 0xc00fe2a0b020,
prev = 0xc00fe2a075b0
},
nr_workers = 0x2,
nr_idle = 0x0,
idle_list = {
next = 0xc000200e60eb7db8,
prev = 0xc000200e60eb7db8
},
idle_timer = {
entry = {
next = 0x5deadbeef200,
pprev = 0x0
},
expires = 0x1018c6fa3,
function = 0xc012e980 ,
flags = 0x41c80068
},
mayday_timer = {
entry = {
next = 0x5deadbeef200,
pprev = 0x0
},
expires = 0x1018d5103,
function = 0xc012e790 ,
flags = 0x168
},
...
workers = {
next = 0xc0002000cb9fa138,
prev = 0xc0002000cb9f1708
},
detach_completion = 0x0,
worker_ida = {
ida_rt = {
gfp_mask = 0x700,
rnode = 0xc000200e51923bd8
}
},
attrs = 0xc00ff92cddf8,
hash_node = {
next = 0x0,
pprev = 0x0
},
refcnt = 0x1,
nr_running = {
counter = 0x0
},
rcu = {
next = 0x0,
func = 0x0
}
}

This pool->id will be used to compute a marker for a
deleted/executed item in the future.

Now let's walk through the workers on the work list:

The TWO entries there are:
c00fe2a075b0
c00fe2a0b020

Work struct #1
===
crash> work_struct c00fe2a075a8
struct work_struct {
data = {
counter = 0xc000200e60eba305 <<< DATA GOOD!!! (a pwq)
},
entry = {
next = 0xc000200e60eb7da0,
prev = 0xc00fe2a0b020
},
func = 0xc0080b1af5a8
}

Work struct #2
===
crash> work_struct 0xc00fe2a0b018
struct work_struct {
data = {
counter = 0x2040 <<<--  DATA BAD!!!
},
entry = {
next = 0xc00fe2a0b020,
prev = 0xc00fe2a0b020
},
func = 0xc0080b1af5a8
}

Note that Work struct #2 is the PROBLEM work item!!

One important thing to note: BOTH THE WORK ENTRIES HAVE THE SAME
WORK FUNCTION - i.e the same entity likely created this work.

crash> dis 0xc0080b1af5a8 1
0xc0080b1af5a8 : addis   r2,r12,4

So these work entries were created by the QLogic driver!



--- Comment From dnban...@us.ibm.com 2018-04-21 23:36 EDT---


The call
===
void qlt_unreg_sess(struct fc_port *sess)
...
INIT_WORK(>free_work, qlt_free_session_done);
schedule_work(>free_work);

Now we can look at the embedding structure, which is the following:

crash> fc_port c00fe2a0af58
struct fc_port {
list = {
next = 0xc00fe2a074e8,
prev = 0xc00fe2a09f68
},
vha = 0xc000200e458b69a0,
node_name = "P\005\ah\001\000\241\245",
port_name = "P\005\ah\001\020\241\245",
d_id = {
b24 = 0x8cfdc0,
b = {
al_pa = 0xc0,
area = 0xfd,
domain = 0x8c,
rsvd_1 = 0x0
}
},
loop_id = 0x1000,
old_loop_id = 0x0,
conf_compl_supported = 0x0,
deleted = 0x2,
local = 0x0,
logout_on_delete = 0x1,
logo_ack_needed = 0x0,
keep_nport_handle = 0x0,
send_els_logo = 0x0,
login_pause = 0x0,
login_succ = 0x0,
query = 0x0,
nvme_del_work = {
data = {
counter = 0x0
},
entry = {
next = 0x0,
prev = 0x0
},
func = 0x0
},
nvme_del_done = {
done = 0x0,
wait = {
lock = {
{
rlock = {
raw_lock = {
slock = 0x0
}
}
}
},
head = {
next = 0x0,
prev = 0x0
}
}
},
nvme_prli_service_param = 0x0,
nvme_flag = 0x0,
conflict = 0x0,
logout_completed = 0x0,
generation = 0x0,
se_sess = 0x0,
sess_kref = {
refcount = {
refs = {
counter = 0x0
}
}
},
tgt = 0x0,
expires = 0x0,
del_list_entry = {
next = 0x0,
prev = 0x0
},
free_work = {  ---  THIS IS OUR (CORRUPTED) WORK!
data = {
counter = 0x2040
},
entry = {
next = 0xc00fe2a0b020,
prev = 0xc00fe2a0b020
},
func = 0xc0080b1af5a8 
},
plogi_link = {0x0, 0x0},
tgt_id = 0x0,
old_tgt_id = 0x0,
fcp_prio = 0x0,
fabric_port_name = " \b\000'\370\037N\261",
fp_speed = 0x,
port_type = FCT_TARGET,
state = {
counter = 0x3
},
flags = 0xb,
login_retry = 0x1d,
rport = 0xc00fd91399c8,
drport = 0x0,
supported_classes = 0x8,
fc4_type = 0x8,
fc4f_nvme = 0x0,
scan_state = 

[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Yeah, so I doubt it's a whitespace fix in the rxrpc driver. However, a
diff between the configs on v415-rc2 and v415-rc3 has lots of
differences, the most interesting being this one:


$ diff -u config-4.15.0-041500rc2-generic config-4.15.0-041500rc3-generic
/* ... snip ... */
@@ -5675,9 +5677,9 @@
 # Display Engine Configuration
 #
 CONFIG_DRM_AMD_DC=y
-# CONFIG_DRM_AMD_DC_PRE_VEGA is not set
+CONFIG_DRM_AMD_DC_PRE_VEGA=y
 # CONFIG_DRM_AMD_DC_FBC is not set
-# CONFIG_DRM_AMD_DC_DCN1_0 is not set
+CONFIG_DRM_AMD_DC_DCN1_0=y
 # CONFIG_DEBUG_KERNEL_DC is not set

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

Title:
  Black screen on 18.04 + AMD RX460

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

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

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

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

[Kernel-packages] [Bug 1766027] Re: linux-kvm: 4.15.0-1007.7 -proposed tracker

[Seth Forshee]

** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 4.15.0-1007.7 -proposed tracker

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

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

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

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Confirmed
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 --
  kernel-master-bug: 1766021
  phase: Packaging

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

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

[Kernel-packages] [Bug 1766024] Re: linux-aws: 4.15.0-1006.6 -proposed tracker

[Seth Forshee]

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.15.0-1006.6 -proposed tracker

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

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

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

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

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-aws package in Ubuntu:
  Confirmed
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 --
  kernel-master-bug: 1766021
  phase: Packaging

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

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

Re: [Kernel-packages] [Bug 1764040] Re: Synaptics Touchpad not Detected

[Dave Harton]

Hi Joseph,

No luck... Still not working.

Updated via UKUU. I have attached the screenshot showing the kernel version
plus the list of input devices.

Cheers,
Dave

PS why doesn't the wiki suggest using UKUU to install upstream kernels? So
much easier to do.


dave@dave-laptop:~$ cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=sysrq kbd event0 leds
B: PROP=0
B: EV=120013
B: KEY=40200 3803078f800d001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=046d Product=c077 Version=0111
N: Name="Logitech USB Optical Mouse"
P: Phys=usb-:00:04.0-4/input0
S:
Sysfs=/devices/pci:00/:00:04.0/usb2/2-4/2-4:1.0/0003:046D:C077.0001/input/input1
U: Uniq=
H: Handlers=mouse0 event1
B: PROP=0
B: EV=17
B: KEY=ff 0 0 0 0
B: REL=103
B: MSC=10

I: Bus=0003 Vendor=04f2 Product=b012 Version=0346
N: Name="USB2.0 1.3M UVC WebCam : USB2.0"
P: Phys=usb-:00:04.1-7/button
S: Sysfs=/devices/pci:00/:00:04.1/usb1/1-7/1-7:1.0/input/input2
U: Uniq=
H: Handlers=kbd event2
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus= Vendor= Product= Version=
N: Name="HDA NVidia Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:08.0/sound/card0/input3
U: Uniq=
H: Handlers=event3
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HDA NVidia Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:08.0/sound/card0/input4
U: Uniq=
H: Handlers=event4
B: PROP=0
B: EV=21
B: SW=4


On 19 April 2018 at 17:22, Dave Harton  wrote:

> Hi Joseph,
>
> Moved this to a new directory and tried again:
>
> See below.
>
> Cheers,
> Dave
> dave@dave-laptop:~$ cd Test
> dave@dave-laptop:~/Test$ sudo dpkg -i *.deb
> [sudo] password for dave:
> (Reading database ... 240669 files and directories currently installed.)
> Preparing to unpack 
> linux-headers-4.16.0-041600-generic_4.16.0-041600.201804012230_amd64.deb
> ...
> Unpacking linux-headers-4.16.0-041600-generic
> (4.16.0-041600.201804012230) over (4.16.0-041600.201804012230) ...
> dpkg: dependency problems prevent configuration of
> linux-headers-4.16.0-041600-generic:
>  linux-headers-4.16.0-041600-generic depends on
> linux-headers-4.16.0-041600; however:
>   Package linux-headers-4.16.0-041600 is not installed.
>
> dpkg: error processing package linux-headers-4.16.0-041600-generic
> (--install):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  linux-headers-4.16.0-041600-generic
> dave@dave-laptop:~/Test$
>
>
> On 19 April 2018 at 17:18, Dave Harton  wrote:
>
>> Hi Joseph,
>>
>> Sorry I couldn't get this to install.
>>
>> Here's the output of the terminal.
>>
>> Cheers,
>> Dave
>>
>> dave@dave-laptop:~$ cd Downloads
>> dave@dave-laptop:~/Downloads$ sudo dpkg -i *.deb
>> [sudo] password for dave:
>> dpkg: warning: downgrading cba:i386 from 0.3.6-4 to 0.3.6-1
>> (Reading database ... 240669 files and directories currently installed.)
>> Preparing to unpack cba_0.3.6-1_i386.deb ...
>> Unpacking cba:i386 (0.3.6-1) over (0.3.6-4) ...
>> Preparing to unpack cba_0.3.6-4_i386.deb ...
>> Unpacking cba:i386 (0.3.6-4) over (0.3.6-1) ...
>> Preparing to unpack linux-headers-4.16.0-041600-ge
>> neric_4.16.0-041600.201804012230_amd64.deb ...
>> Unpacking linux-headers-4.16.0-041600-generic
>> (4.16.0-041600.201804012230) over (4.16.0-041600.201804012230) ...
>> More than one copy of package cba:i386 has been unpacked
>>  in this run ! Only configuring it once.
>> dpkg: dependency problems prevent configuration of cba:i386:
>>  cba:i386 depends on libwxbase2.8-0 (>= 2.8.11.0).
>>  cba:i386 depends on libwxgtk2.8-0 (>= 2.8.11.0).
>>
>> dpkg: error processing package cba:i386 (--install):
>>  dependency problems - leaving unconfigured
>> dpkg: dependency problems prevent configuration of
>> linux-headers-4.16.0-041600-generic:
>>  linux-headers-4.16.0-041600-generic depends on
>> linux-headers-4.16.0-041600; however:
>>   Package linux-headers-4.16.0-041600 is not installed.
>>
>> dpkg: error processing package linux-headers-4.16.0-041600-generic
>> (--install):
>>  dependency problems - leaving unconfigured
>> Errors were encountered while processing:
>>  cba:i386
>>  linux-headers-4.16.0-041600-generic
>> dave@dave-laptop:~/Downloads$
>>
>>
>> On 17 April 2018 at 09:13, Joseph Salisbury <
>> joseph.salisb...@canonical.com> wrote:
>>
>>> Would it be possible for you to test the latest upstream kernel? Refer
>>> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
>>> v4.16 kernel[0].
>>>
>>> If this bug is fixed in the mainline kernel, please add the following
>>> tag 'kernel-fixed-upstream'.
>>>
>>> If the mainline kernel does not fix this bug, please add the tag:
>>> 'kernel-bug-exists-upstream'.
>>>
>>> Once testing of the upstream kernel is 

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

[bugproxy]

--- Comment From chngu...@us.ibm.com 2018-04-21 20:09 EDT---
Dwip provided a new kernel and we start test on 3 guests.
root@boslcp3:~# date
Sat Apr 21 19:00:07 CDT 2018
root@boslcp3:~# uptime
19:00:09 up 20 min,  3 users,  load average: 0.01, 0.42, 0.48
root@boslcp3:~# uname -a
Linux boslcp3 4.15.15tst1 #4 SMP Sat Apr 21 16:57:31 CDT 2018 ppc64le ppc64le 
ppc64le GNU/Linux
root@boslcp3:~# virsh list --all
IdName   State

1 boslcp3g3  running
2 boslcp3g4  running
4 boslcp3g1  running
- boslcp3g5  shut off

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c 

[Kernel-packages] [Bug 1765498] Re: linux-kvm: 4.15.0-1006.6 -proposed tracker

[Brad Figg]

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1765490
  phase: Uploaded
+ kernel-phase:Promoted to proposed
+ kernel-phase-changed:Saturday, 21. April 2018 23:36 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1765490
- phase: Uploaded
- kernel-phase:Promoted to proposed
- kernel-phase-changed:Saturday, 21. April 2018 23:36 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
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 --
  kernel-master-bug: 1765490
  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/1765498/+subscriptions

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

[Kernel-packages] [Bug 1766024] Re: linux-aws: -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1766021
+ kernel-phase:Packaging
+ kernel-phase-changed:Saturday, 21. April 2018 23:30 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1766021
- kernel-phase:Packaging
- kernel-phase-changed:Saturday, 21. April 2018 23:30 UTC
+ phase: Packaging

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-aws package in Ubuntu:
  Confirmed
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 --
  kernel-master-bug: 1766021
  phase: Packaging

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

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

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

[bugproxy]

--- Comment From dougm...@us.ibm.com 2018-04-21 19:17 EDT---
We need to see the console messages *before* things go wrong. Please capture 
the SOL console output from boot until this happens.

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c000200e0b20fa30] 

[Kernel-packages] [Bug 1762844] sol console log

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-21 17:04 
EDT---


** Attachment added: "sol console log"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5125257/+files/boslcp3.0421.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1766027] Re: linux-kvm: -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1766021
+ kernel-phase-changed:Saturday, 21. April 2018 23:01 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1766021
- kernel-phase-changed:Saturday, 21. April 2018 23:01 UTC
- kernel-phase:Packaging
+ phase: Packaging

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Confirmed
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 --
  kernel-master-bug: 1766021
  phase: Packaging

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

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

[Kernel-packages] [Bug 1766021] Re: linux: 4.15.0-19.20 -proposed tracker

[Brad Figg]

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1766028 (linux-hwe-edge)
  derivatives: bug 1766022 (linux-raspi2), bug 1766023 (linux-oem), bug 1766024 
(linux-aws), bug 1766025 (linux-azure), bug 1766026 (linux-gcp), bug 1766027 
(linux-kvm)
+ kernel-phase-changed:Saturday, 21. April 2018 23:01 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1766028 (linux-hwe-edge)
  derivatives: bug 1766022 (linux-raspi2), bug 1766023 (linux-oem), bug 1766024 
(linux-aws), bug 1766025 (linux-azure), bug 1766026 (linux-gcp), bug 1766027 
(linux-kvm)
  kernel-phase-changed:Saturday, 21. April 2018 23:01 UTC
  kernel-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.15.0-19.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
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 1766028 (linux-hwe-edge)
  derivatives: bug 1766022 (linux-raspi2), bug 1766023 (linux-oem), bug 1766024 
(linux-aws), bug 1766025 (linux-azure), bug 1766026 (linux-gcp), bug 1766027 
(linux-kvm)
  kernel-phase-changed:Saturday, 21. April 2018 23:01 UTC
  kernel-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

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

[bugproxy]

--- Comment From kla...@br.ibm.com 2018-04-21 18:55 EDT---
(In reply to comment #80)
> (In reply to comment #79)
> > Machine still seems to be up... will check if I can observe anything
> > interesting ...
>
> System just crashes it now. The vmcore is at /var/crash/201804181042

Can we retry this test on the P8 system using Brian's kernel in comment
#94?

Also, please post access information for this system.

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] 

[Kernel-packages] [Bug 1766027] [NEW] linux-kvm: -proposed tracker

[Seth Forshee]

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
-- swm properties --
kernel-master-bug: 1766021

** 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/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux-kvm (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux-kvm (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2018.04.21 kernel-sru-derivative-of-1766021

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

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

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

** Tags added: bionic

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

** Also affects: kernel-sru-workflow/automated-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/promote-to-proposed
   Importance: Undecided
   Status: New

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

** Also affects: kernel-sru-workflow/regression-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/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/promote-to-proposed
   Importance: Undecided => Medium

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

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

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

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

** Tags added: kernel-sru-cycle-d2018.04.21

** Tags added: kernel-sru-derivative-of-1766021

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.

[Kernel-packages] [Bug 1766021] Re: linux: -proposed tracker

[Seth Forshee]

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ backports: bug 1766028 (linux-hwe-edge)
+ derivatives: bug 1766022 (linux-raspi2), bug 1766023 (linux-oem), bug 1766024 
(linux-aws), bug 1766025 (linux-azure), bug 1766026 (linux-gcp), bug 1766027 
(linux-kvm)

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.15.0-19.20 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux: 4.15.0-19.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
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 1766028 (linux-hwe-edge)
  derivatives: bug 1766022 (linux-raspi2), bug 1766023 (linux-oem), bug 1766024 
(linux-aws), bug 1766025 (linux-azure), bug 1766026 (linux-gcp), bug 1766027 
(linux-kvm)

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

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

[Kernel-packages] [Bug 1766024] [NEW] linux-aws: -proposed tracker

[Seth Forshee]

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
-- swm properties --
kernel-master-bug: 1766021

** 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/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux-aws (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux-aws (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2018.04.21 kernel-sru-derivative-of-1766021

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

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

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

** Tags added: bionic

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

** Also affects: kernel-sru-workflow/automated-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/promote-to-proposed
   Importance: Undecided
   Status: New

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

** Also affects: kernel-sru-workflow/regression-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/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/promote-to-proposed
   Importance: Undecided => Medium

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

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

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

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

** Tags added: kernel-sru-cycle-d2018.04.21

** Tags added: kernel-sru-derivative-of-1766021

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.

[Kernel-packages] [Bug 1766021] [NEW] linux: -proposed tracker

[Seth Forshee]

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

** 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/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

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

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

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2018.04.21 kernel-sru-master-kernel

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

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

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

** Tags added: bionic

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

** Also affects: kernel-sru-workflow/automated-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-release
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-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/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-sru-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

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

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

** Tags added: kernel-sru-cycle-d2018.04.21

** Tags added: kernel-sru-master-kernel

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  

[Kernel-packages] [Bug 1765232] Re: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

[Seth Forshee]

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

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

Title:
  Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

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

Bug description:
  SRU Justification

  Impact: Since 4.15.0-15 some machines have been failing to boot due to
  IO hangs. This is caused by patches applied for LP #1759723, which
  assigned managed interrupt vectors and reply queues for all possible
  CPUs, not just present CPUs. Some drivers were not prepared to cope
  with this and end up selecting reply queues not mapped to an online
  CPU, causing IO hangs during boot.

  Fix: There are driver fixes available upstream, but there are 8-ish
  patches in total and we're extremely close to release, so the safer
  bet it to just revert the patches for LP #1759723. We can consider
  reintroducing them with required fixes at a later time.

  Regression Potential: This is obviously going to reintroduce the
  problem the patches were intended to fix. These are less serious than
  the problems which the patches introduced, and IBM has given their
  okay to revert them as well.

  Test Case: Verified to fix affected hardware on LP #1765232.

  ---

  For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to
  4.15.0-15. The system hangs at boot up now. Rolling back to the old
  kernel everything works as expected. It appears to hang while trying
  to enumerate an SD card device, which isn't even installed. I have
  tried this on a Dell R620 and R820 and both have the exact same
  problem. I even downloaded a new installer iso from the daily builds
  to reinstall the OS and the installer hangs too now.

  Support for Dell PowerEdge 12th gen servers appears to be broken with
  kernel 4.15.0-15.

  https://imgur.com/VT9zd0w
  https://imgur.com/4BQPCXo

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

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

[Kernel-packages] [Bug 1765498] Re: linux-kvm: 4.15.0-1006.6 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package-meta
   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/1765498

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-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 promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Confirmed
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 --
  kernel-master-bug: 1765490
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1746848] Re: Ubuntu 17.10 keeps comming back after suspended on a Macbook Pro 15 retina 2013 late

[Otto Julio Ahlert Pinno]

Sorry Kai-Heng Feng but I'm already using Ubuntu 18 since the beginning
of this month. Fortunately, the problem was fixed or never existed in
the new version.

Thank you for your help.

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

Title:
  Ubuntu 17.10 keeps comming back after suspended on a Macbook Pro 15
  retina 2013 late

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I click on the suspend button (alternative of power off button)
  in the menu or I click the power button, the Ubuntu seems like will be
  suspended (with a black screen) and, after 5-10 seconds, come back to
  the login screen.

  Closing the lid also doesn't take effect. It doesn't even turn off the
  display.

  I found that clicking on the suspend button and very quickly closing
  the lid seems to make it stays suspended.

  I'm having this trouble in a Macbook Pro 15 retina 2013 late running a
  Ubuntu 17.10 in the most recent version.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  otto   1600 F pulseaudio
   /dev/snd/controlC0:  otto   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 22:58:16 2018
  InstallationDate: Installed on 2018-01-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Apple Inc. MacBookPro10,1
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=b05cd5cb-c451-4546-a9e0-377ae91a2e44 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00F2.B00.1708080809
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00F2.B00.1708080809:bd08/08/2017:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1762844] sol console log

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-21 17:04 
EDT---


** Attachment added: "sol console log"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5125224/+files/boslcp3.0421.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

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

[bugproxy]

--- Comment From chngu...@us.ibm.com 2018-04-21 17:02 EDT---
Not sure what is going on. The SOL console print out all of these messages...
rcu_sched self-detected stall on CPU
[20705.652053]  95-: (1 GPs behind) idle=c72/2/0 softirq=179/180 fqs=2586003
[20705.652101]   (t=5172329 jiffies g=213 c=212 q=74736)
[20705.652140] Task dump for CPU 95:
[20705.652164] swapper/95  R  running task0 0  1 0x0804
[20705.652213] Call Trace:
[20705.652231] [c000200fff3d3460] [c0149ed8] 
sched_show_task.part.16+0xd8/0x110 (unreliable)
[20705.652288] [c000200fff3d34d0] [c01a9e9c] 
rcu_dump_cpu_stacks+0xd4/0x138
[20705.652336] [c000200fff3d3520] [c01a8f68] 
rcu_check_callbacks+0x8e8/0xb40
[20705.652385] [c000200fff3d3650] [c01b7208] 
update_process_times+0x48/0x90
[20705.652433] [c000200fff3d3680] [c01cef54] 
tick_sched_handle.isra.5+0x34/0xd0
[20705.652482] [c000200fff3d36b0] [c01cf050] tick_sched_timer+0x60/0xe0
[20705.652530] [c000200fff3d36f0] [c01b7db4] 
__hrtimer_run_queues+0x144/0x370
[20705.652578] [c000200fff3d3770] [c01b8d0c] 
hrtimer_interrupt+0xfc/0x350
[20705.652627] [c000200fff3d3840] [c00248f0] 
__timer_interrupt+0x90/0x260
[20705.652675] [c000200fff3d3890] [c0024d08] timer_interrupt+0x98/0xe0
[20705.652716] [c000200fff3d38c0] [c0009014] 
decrementer_common+0x114/0x120
[20705.652765] --- interrupt: 901 at _raw_spin_lock_irqsave+0x88/0x110
[20705.652765] LR = _raw_spin_lock_irqsave+0x80/0x110
[20705.652836] [c000200fff3d3bb0] [c000200fff3d3bf0] 0xc000200fff3d3bf0 
(unreliable)
[20705.652885] [c000200fff3d3bf0] [c0904e90] 
scsi_end_request+0x110/0x270
[20705.652933] [c000200fff3d3c50] [c0905414] 
scsi_io_completion+0x424/0x750
[20705.652981] [c000200fff3d3d10] [c08f949c] 
scsi_finish_command+0x11c/0x1b0
[20705.653029] [c000200fff3d3d90] [c0904428] 
scsi_softirq_done+0x198/0x220
[20705.653078] [c000200fff3d3e20] [c068fe98] blk_done_softirq+0xb8/0xe0
[20705.653126] [c000200fff3d3e60] [c0cffb08] __do_softirq+0x158/0x3e4
[20705.653167] [c000200fff3d3f40] [c0115968] irq_exit+0xe8/0x120
[20705.653207] [c000200fff3d3f60] [c0017788] __do_irq+0x88/0x1c0
[20705.653248] [c000200fff3d3f90] [c002a1b0] call_do_irq+0x14/0x24
[20705.653289] [c000200e582fba90] [c001795c] do_IRQ+0x9c/0x130
[20705.653330] [c000200e582fbae0] [c0009b04] 
h_virt_irq_common+0x114/0x120
[20705.653379] --- interrupt: ea1 at replay_interrupt_return+0x0/0x4
[20705.653379] LR = arch_local_irq_restore+0x74/0x90
[20705.653459] [c000200e582fbdd0] [005f] 0x5f (unreliable)
[20705.653500] [c000200e582fbdf0] [c0ac16d0] 
cpuidle_enter_state+0xf0/0x450
[20705.653549] [c000200e582fbe50] [c017311c] call_cpuidle+0x4c/0x90
[20705.653590] [c000200e582fbe70] [c0173530] do_idle+0x2b0/0x330
[20705.653631] [c000200e582fbec0] [c01737ec] cpu_startup_entry+0x3c/0x50
[20705.653679] [c000200e582fbef0] [c004a050] start_secondary+0x4f0/0x510
[20705.653727] [c000200e582fbf90] [c000aa6c] 
start_secondary_prolog+0x10/0x14
[   ***] (2 of 2) A start job is running for? polling (5h 45min 33s / no limit)

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging 

[Kernel-packages] [Bug 1765232] Re: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

[Seth Forshee]

** Description changed:

+ SRU Justification
+ 
+ Impact: Since 4.15.0-15 some machines have been failing to boot due to
+ IO hangs. This is caused by patches applied for LP #1759723, which
+ assigned managed interrupt vectors and reply queues for all possible
+ CPUs, not just present CPUs. Some drivers were not prepared to cope with
+ this and end up selecting reply queues not mapped to an online CPU,
+ causing IO hangs during boot.
+ 
+ Fix: There are driver fixes available upstream, but there are 8-ish
+ patches in total and we're extremely close to release, so the safer bet
+ it to just revert the patches for LP #1759723. We can consider
+ reintroducing them with required fixes at a later time.
+ 
+ Regression Potential: This is obviously going to reintroduce the problem
+ the patches were intended to fix. These are less serious than the
+ problems which the patches introduced, and IBM has given their okay to
+ revert them as well.
+ 
+ Test Case: Verified to fix affected hardware on LP #1765232.
+ 
+ ---
+ 
  For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to
  4.15.0-15. The system hangs at boot up now. Rolling back to the old
  kernel everything works as expected. It appears to hang while trying to
  enumerate an SD card device, which isn't even installed. I have tried
  this on a Dell R620 and R820 and both have the exact same problem. I
  even downloaded a new installer iso from the daily builds to reinstall
  the OS and the installer hangs too now.
  
  Support for Dell PowerEdge 12th gen servers appears to be broken with
  kernel 4.15.0-15.
  
  https://imgur.com/VT9zd0w
  https://imgur.com/4BQPCXo

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

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

Bug description:
  SRU Justification

  Impact: Since 4.15.0-15 some machines have been failing to boot due to
  IO hangs. This is caused by patches applied for LP #1759723, which
  assigned managed interrupt vectors and reply queues for all possible
  CPUs, not just present CPUs. Some drivers were not prepared to cope
  with this and end up selecting reply queues not mapped to an online
  CPU, causing IO hangs during boot.

  Fix: There are driver fixes available upstream, but there are 8-ish
  patches in total and we're extremely close to release, so the safer
  bet it to just revert the patches for LP #1759723. We can consider
  reintroducing them with required fixes at a later time.

  Regression Potential: This is obviously going to reintroduce the
  problem the patches were intended to fix. These are less serious than
  the problems which the patches introduced, and IBM has given their
  okay to revert them as well.

  Test Case: Verified to fix affected hardware on LP #1765232.

  ---

  For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to
  4.15.0-15. The system hangs at boot up now. Rolling back to the old
  kernel everything works as expected. It appears to hang while trying
  to enumerate an SD card device, which isn't even installed. I have
  tried this on a Dell R620 and R820 and both have the exact same
  problem. I even downloaded a new installer iso from the daily builds
  to reinstall the OS and the installer hangs too now.

  Support for Dell PowerEdge 12th gen servers appears to be broken with
  kernel 4.15.0-15.

  https://imgur.com/VT9zd0w
  https://imgur.com/4BQPCXo

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

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

[Kernel-packages] [Bug 1765232] Re: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

[Seth Forshee]

Thanks for testing, I'll get those reverts sent to the list.

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

Title:
  Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

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

Bug description:
  For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to
  4.15.0-15. The system hangs at boot up now. Rolling back to the old
  kernel everything works as expected. It appears to hang while trying
  to enumerate an SD card device, which isn't even installed. I have
  tried this on a Dell R620 and R820 and both have the exact same
  problem. I even downloaded a new installer iso from the daily builds
  to reinstall the OS and the installer hangs too now.

  Support for Dell PowerEdge 12th gen servers appears to be broken with
  kernel 4.15.0-15.

  https://imgur.com/VT9zd0w
  https://imgur.com/4BQPCXo

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

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

[Kernel-packages] [Bug 1765232] Re: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

[Nikolas Britton]

The kernel from post #12 also works without issue for me too.

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

Title:
  Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

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

Bug description:
  For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to
  4.15.0-15. The system hangs at boot up now. Rolling back to the old
  kernel everything works as expected. It appears to hang while trying
  to enumerate an SD card device, which isn't even installed. I have
  tried this on a Dell R620 and R820 and both have the exact same
  problem. I even downloaded a new installer iso from the daily builds
  to reinstall the OS and the installer hangs too now.

  Support for Dell PowerEdge 12th gen servers appears to be broken with
  kernel 4.15.0-15.

  https://imgur.com/VT9zd0w
  https://imgur.com/4BQPCXo

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

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

[Kernel-packages] [Bug 1765998] Re: FS access deadlock with btrfs quotas enabled

[Michael Sparmann]

I cannot run the affected (production) system using a broken kernel, and it 
will lockup after boot within seconds.
If necessary, I can provide additional information or testing upon request.

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

Title:
  FS access deadlock with btrfs quotas enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running into an issue on Ubuntu Bionic (but not Xenial) where
  shortly after boot, under heavy load from many LXD containers starting
  at once, access to the btrfs filesystem that the containers are on
  deadlocks.

  The issue is quite hard to reproduce on other systems, quite likely
  related to the size of the filesystem involved (4 devices with a total
  of 8TB, millions of files, ~20 subvolumes with tens of snapshots each)
  and the access pattern from many LXD containers at once. It definitely
  goes away when disabling btrfs quotas though. Another prerequisite to
  trigger this bug may be the container subvolumes sharing extents (from
  their parent image or due to deduplication).

  I can only reliably reproduce it on a production system that I can only do 
very limited testing on, however I have been able to gather the following 
information:
  - Many threads are stuck, trying to aquire locks on various tree roots, which 
are never released by their current holders.
  - There always seem to be (at least) two threads executing rmdir syscalls 
which are creating the circular dependency: One of them is in btrfs_cow_block 
=> ... => btrfs_qgroup_trace_extent_post => ... => find_parent_nodes and wants 
to acquire a lock that was already aquired by btrfs_search_slot of the other 
rmdir.
  - Reverting this patch seems to prevent it from happening: 
https://patchwork.kernel.org/patch/9573267/

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

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

[Kernel-packages] [Bug 1765232] Re: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

[Tyler Doherty]

Seth, thanks for the guidance, that did it. Looks like the kernel from
#12 works without issue. Glad you were able to identify the commits that
did 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/1765232

Title:
  Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

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

Bug description:
  For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to
  4.15.0-15. The system hangs at boot up now. Rolling back to the old
  kernel everything works as expected. It appears to hang while trying
  to enumerate an SD card device, which isn't even installed. I have
  tried this on a Dell R620 and R820 and both have the exact same
  problem. I even downloaded a new installer iso from the daily builds
  to reinstall the OS and the installer hangs too now.

  Support for Dell PowerEdge 12th gen servers appears to be broken with
  kernel 4.15.0-15.

  https://imgur.com/VT9zd0w
  https://imgur.com/4BQPCXo

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

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

[Kernel-packages] [Bug 1765232] Re: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

[Seth Forshee]

Make sure you got linux-image-unsigned, linux-modules, *and* linux-
modules-extra. linux-modules-extra has the hpsa driver.

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

Title:
  Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

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

Bug description:
  For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to
  4.15.0-15. The system hangs at boot up now. Rolling back to the old
  kernel everything works as expected. It appears to hang while trying
  to enumerate an SD card device, which isn't even installed. I have
  tried this on a Dell R620 and R820 and both have the exact same
  problem. I even downloaded a new installer iso from the daily builds
  to reinstall the OS and the installer hangs too now.

  Support for Dell PowerEdge 12th gen servers appears to be broken with
  kernel 4.15.0-15.

  https://imgur.com/VT9zd0w
  https://imgur.com/4BQPCXo

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

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

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

[bugproxy]

--- Comment From jos...@br.ibm.com 2018-04-21 15:29 EDT---
Ah, forget it, it's in 4.15.0-15.16 not 4.15.0-16. Anyway, you can revert it if 
required.

Thank you

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

Title:
  ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle
  hangs after hotplug CPU add operation.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  ===
  Performed HOTPLUG cpu attach operation for the guest and guest console 
becomes unresponsive.

  Steps to re-create:
  ==
  1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels
   
  2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes

  root@boslcp3:/home# uname -a
  Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:/home# uname -r
  4.15.0-12-generic

  root@boslcp3g3:/kte/tools/setup.d# uname -a
  Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3g3:/kte/tools/setup.d# uname -r
  4.15.0-12-generic

  3. Started HTX & stress-ng for on guest for 10-15 min

  4. Cleaned up the tests to perform hot-plug and ensure enough memory
  and cpu was there (killed all Process using kill)

  5. Performed cpu hot-plug and guest went into hung state

  Before Hotplug:

  root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu
64

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  



  root@boslcp3:~#  

  6. After this operation, guest becomes unrepsonsive as below

  
  root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more 
than 120 seconds.
  [ 3626.146375]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 
seconds.
  [ 3626.146699]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 
seconds.
  [ 3626.147016]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 
seconds.
  [ 3626.147361]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds.
  [ 3626.147686]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds.
  [ 3626.147937]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds.
  [ 3626.148173]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds.
  [ 3626.148406]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  root@boslcp3g3:~#
  root@boslcp3g3:~# ps -ef | grep stress-ng
  [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds.
  [ 3746.978221]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3746.978301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3746.978447] INFO: task systemd-journal:665 blocked for more than 120 
seconds.
  [ 3746.978534]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3746.978607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 4446.361899] systemd[1]: Failed to start Journal Service.
  [ 4897.632142] systemd[1]: Failed to start Journal Service.


  ^Z
  ^X
  ^C
  ^Z
 

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

[bugproxy]

--- Comment From jos...@br.ibm.com 2018-04-21 15:14 EDT---
Hi Seth,

Just another point is that it's related
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765232) to kernel
4.15.0-15 but as per comment #11 these patches were applied in
4.15.0-16.

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

Title:
  ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle
  hangs after hotplug CPU add operation.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  ===
  Performed HOTPLUG cpu attach operation for the guest and guest console 
becomes unresponsive.

  Steps to re-create:
  ==
  1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels
   
  2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes

  root@boslcp3:/home# uname -a
  Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:/home# uname -r
  4.15.0-12-generic

  root@boslcp3g3:/kte/tools/setup.d# uname -a
  Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3g3:/kte/tools/setup.d# uname -r
  4.15.0-12-generic

  3. Started HTX & stress-ng for on guest for 10-15 min

  4. Cleaned up the tests to perform hot-plug and ensure enough memory
  and cpu was there (killed all Process using kill)

  5. Performed cpu hot-plug and guest went into hung state

  Before Hotplug:

  root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu
64

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  



  root@boslcp3:~#  

  6. After this operation, guest becomes unrepsonsive as below

  
  root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more 
than 120 seconds.
  [ 3626.146375]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 
seconds.
  [ 3626.146699]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 
seconds.
  [ 3626.147016]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 
seconds.
  [ 3626.147361]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds.
  [ 3626.147686]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds.
  [ 3626.147937]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds.
  [ 3626.148173]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds.
  [ 3626.148406]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  root@boslcp3g3:~#
  root@boslcp3g3:~# ps -ef | grep stress-ng
  [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds.
  [ 3746.978221]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3746.978301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3746.978447] INFO: task systemd-journal:665 blocked for more than 120 
seconds.
  [ 3746.978534]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3746.978607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 4446.361899] systemd[1]: Failed to start 

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

[bugproxy]

--- Comment From jos...@br.ibm.com 2018-04-21 14:38 EDT---
Hello Seth,

Without those patches CPU hoplug doesn't work but the issue related on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765232 looks more
urgent yet. I agree to revert it if necessary.

Thanks

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

Title:
  ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle
  hangs after hotplug CPU add operation.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  ===
  Performed HOTPLUG cpu attach operation for the guest and guest console 
becomes unresponsive.

  Steps to re-create:
  ==
  1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels
   
  2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes

  root@boslcp3:/home# uname -a
  Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:/home# uname -r
  4.15.0-12-generic

  root@boslcp3g3:/kte/tools/setup.d# uname -a
  Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3g3:/kte/tools/setup.d# uname -r
  4.15.0-12-generic

  3. Started HTX & stress-ng for on guest for 10-15 min

  4. Cleaned up the tests to perform hot-plug and ensure enough memory
  and cpu was there (killed all Process using kill)

  5. Performed cpu hot-plug and guest went into hung state

  Before Hotplug:

  root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu
64

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  



  root@boslcp3:~#  

  6. After this operation, guest becomes unrepsonsive as below

  
  root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more 
than 120 seconds.
  [ 3626.146375]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 
seconds.
  [ 3626.146699]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 
seconds.
  [ 3626.147016]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 
seconds.
  [ 3626.147361]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds.
  [ 3626.147686]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds.
  [ 3626.147937]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds.
  [ 3626.148173]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds.
  [ 3626.148406]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  root@boslcp3g3:~#
  root@boslcp3g3:~# ps -ef | grep stress-ng
  [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds.
  [ 3746.978221]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3746.978301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3746.978447] INFO: task systemd-journal:665 blocked for more than 120 
seconds.
  [ 3746.978534]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3746.978607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 4446.361899] systemd[1]: Failed 

[Kernel-packages] [Bug 1761831] Re: ASUS B150M Gaming hibernate/resume failure

[Radu Axente]

While booting (ALT+F1) following message are shown:

[0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update 
microcode to version 0xb2 (or later)
[0.00] ACPI BIOS Error (bug): Failure looking up [\SP.PCIO.XHC.RHUB.HS11], 
AE_NOT_FOUND (20180105/dswload-211)
[0.00] ACPI Error: AE_NOT_FOUND, During name lookup/catalog 
(20180105/psobject-252)
[0.00] ACPI Error: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table 
(20180105/tbxfload-228)
[0.00] ACPI Error: 1 table load failures, 8 successful 
(20180105/tbxfload-246)

Ubuntu Bionic Beaver (development branch) MRSPC4L tty1

Don't think this is an issue for my MAIN ISSUE (Hibernate / Resume from 
Hibernate).
Reason:  I receive such / similar messages on my PCs (3 / three) running Ubuntu 
MATE 17.10 where Hibernate / Resume from Hibernate work perfectly with Linux 
Kernel 4.15.x / 4.16.x (installed via ukuu).

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

Title:
  ASUS B150M Gaming hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate /
  Resume from Hibernate - does not work

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mihai  1718 F pulseaudio
   /dev/snd/controlC0:  mihai  1718 F pulseaudio
  Date: Fri Apr  6 20:19:49 2018
  DuplicateSignature: hibernate/resume:System manufacturer System Product 
Name:0601
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03
  InstallationDate: Installed on 2018-04-06 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  InterpreterPath: /usr/bin/python3.6
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
   Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: [System manufacturer System Product Name] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0601
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M PRO GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

[bugproxy]

--- Comment From dougm...@us.ibm.com 2018-04-21 14:26 EDT---
I have ltc-boston1 setup with Ubuntu kernel 4.15.0-15, but there is no SAN 
connected to the QLE2742. I see no problem there right now. I have reserve the 
system for this bug until Monday evening.

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] 

[Kernel-packages] [Bug 1761831] Re: ASUS B150M Gaming hibernate/resume failure

[Radu Axente]

Ubuntu MATE-18.04 - daily build - 21.04.2018 - Kernel
4.16.3-041603.201804190730 (via ukuu)

Additional Drivers - NVIDIA Corporation: GM107 [GeForce GTX 750 Ti]
- Using NVIDIA binary driver-version 340.106 from ndivia-340 (proprietary)

Same issue, hibernate works, resume from hibernate - error!

Cannot automatically submit issue reports "UnreportableReason: This is
not an official Ubuntu package.  Please remove any third party package
and try again."

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

Title:
  ASUS B150M Gaming hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate /
  Resume from Hibernate - does not work

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mihai  1718 F pulseaudio
   /dev/snd/controlC0:  mihai  1718 F pulseaudio
  Date: Fri Apr  6 20:19:49 2018
  DuplicateSignature: hibernate/resume:System manufacturer System Product 
Name:0601
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03
  InstallationDate: Installed on 2018-04-06 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  InterpreterPath: /usr/bin/python3.6
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
   Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: [System manufacturer System Product Name] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0601
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M PRO GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

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

Title:
  FS access deadlock with btrfs quotas enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm running into an issue on Ubuntu Bionic (but not Xenial) where
  shortly after boot, under heavy load from many LXD containers starting
  at once, access to the btrfs filesystem that the containers are on
  deadlocks.

  The issue is quite hard to reproduce on other systems, quite likely
  related to the size of the filesystem involved (4 devices with a total
  of 8TB, millions of files, ~20 subvolumes with tens of snapshots each)
  and the access pattern from many LXD containers at once. It definitely
  goes away when disabling btrfs quotas though. Another prerequisite to
  trigger this bug may be the container subvolumes sharing extents (from
  their parent image or due to deduplication).

  I can only reliably reproduce it on a production system that I can only do 
very limited testing on, however I have been able to gather the following 
information:
  - Many threads are stuck, trying to aquire locks on various tree roots, which 
are never released by their current holders.
  - There always seem to be (at least) two threads executing rmdir syscalls 
which are creating the circular dependency: One of them is in btrfs_cow_block 
=> ... => btrfs_qgroup_trace_extent_post => ... => find_parent_nodes and wants 
to acquire a lock that was already aquired by btrfs_search_slot of the other 
rmdir.
  - Reverting this patch seems to prevent it from happening: 
https://patchwork.kernel.org/patch/9573267/

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

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

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

[bugproxy]

--- Comment From kla...@br.ibm.com 2018-04-21 09:21 EDT---
Should we go back to the stock Ubuntu kernel in an attempt to identify if bug 
167104 is a result of the custom kernel or the newest PNOR?

--- Comment From prad...@us.ibm.com 2018-04-21 13:17 EDT---
(In reply to comment #106)
> Should we go back to the stock Ubuntu kernel in an attempt to identify if
> bug 167104 is a result of the custom kernel or the newest PNOR?

I am looking at all these plethora of bugs on the host and guest, seems
like a constantly shifting problem. I don't think that this particular
instance was because of the custom kernel (reverting some Qlogic
patches). In my opinion memory corruption seems to be gaining currency.

Are systems without the Qlogic adapters seeing any of the problems
reported here?

How do we debug with constantly moving pieces? Can we get a stable base
to start with? By that I mean we go back to a kernel and pnor that
worked in the past. Then using the same kernel advance the pnor and
validate how it works. We might need to limit the testing to "cater" to
the various bugs.

Once we have isolated the pnor, then we repeat with the kernels. Not
sure how long these activities will take, but we might need to consider
running a parallel exercise.

--- Comment From dnban...@us.ibm.com 2018-04-21 14:17 EDT---
boslcp3 seems to have gone off the rails again ... the console is spitting out a
lot of messages like:

[   ***] (2 of 2) A start job is running for?urnal Service

and it is not pingable

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 

[Kernel-packages] [Bug 1765980] Re: IPv6 fragments with nf_conntrack_reasm loaded cause net_mutex deadlock upon LXD container shutdown

[Michael Sparmann]

** Description changed:

  I've spent the last few days tracking down an issue where an attempt to
  shutdown an LXD container after several hours of host uptime on Ubuntu
  Bionic (4.15.0-15.16-generic) would cause a kworker thread to start
  spinning on one CPU core and all subsequent container start/stop
  operations to fail.
  
  The underlying issue is that a kworker thread (executing cleanup_net)
  spins in inet_frags_exit_net, waiting for sum_frag_mem_limit(nf) to
  become zero, which never happens becacuse it has underflowed to some
  negative multiple of 64. That kworker thread keeps holding net_mutex and
  therefore blocks any further container start/stops. That in turn is
  triggered by receiving a fragmented IPv6 MDNS packet in my instance, but
  it could probably be triggered by any fragmented IPv6 traffic.
  
  The reason for the frag mem limit counter to underflow is
  nf_ct_frag6_reasm deducting more from it than the sum of all previous
  nf_ct_frag6_queue calls added, due to pskb_expand_head (called through
  skb_unclone) adding a multiple of 64 to the SKB's truesize, due to
  kmalloc_reserve allocating some additional slack space to the buffer.
  
  Removing this line:
  size = SKB_WITH_OVERHEAD(ksize(data));
  or making it conditional with nhead or ntail being nonzero works around the 
issue, but a proper fix for this seems complicated.
- There is already a comment saying "It is not generally safe to change 
skb->truesize." right about the offending modification of truesize, but the if 
statement guarding it apparently doesn't keep out all problematic cases.
+ There is already a comment saying "It is not generally safe to change 
skb->truesize." right above the offending modification of truesize, but the if 
statement guarding it apparently doesn't keep out all problematic cases.
  I'll leave figuring out the proper way to fix this to the maintainers of this 
area... ;)

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

Title:
  IPv6 fragments with nf_conntrack_reasm loaded cause net_mutex deadlock
  upon LXD container shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've spent the last few days tracking down an issue where an attempt
  to shutdown an LXD container after several hours of host uptime on
  Ubuntu Bionic (4.15.0-15.16-generic) would cause a kworker thread to
  start spinning on one CPU core and all subsequent container start/stop
  operations to fail.

  The underlying issue is that a kworker thread (executing cleanup_net)
  spins in inet_frags_exit_net, waiting for sum_frag_mem_limit(nf) to
  become zero, which never happens becacuse it has underflowed to some
  negative multiple of 64. That kworker thread keeps holding net_mutex
  and therefore blocks any further container start/stops. That in turn
  is triggered by receiving a fragmented IPv6 MDNS packet in my
  instance, but it could probably be triggered by any fragmented IPv6
  traffic.

  The reason for the frag mem limit counter to underflow is
  nf_ct_frag6_reasm deducting more from it than the sum of all previous
  nf_ct_frag6_queue calls added, due to pskb_expand_head (called through
  skb_unclone) adding a multiple of 64 to the SKB's truesize, due to
  kmalloc_reserve allocating some additional slack space to the buffer.

  Removing this line:
  size = SKB_WITH_OVERHEAD(ksize(data));
  or making it conditional with nhead or ntail being nonzero works around the 
issue, but a proper fix for this seems complicated.
  There is already a comment saying "It is not generally safe to change 
skb->truesize." right above the offending modification of truesize, but the if 
statement guarding it apparently doesn't keep out all problematic cases.
  I'll leave figuring out the proper way to fix this to the maintainers of this 
area... ;)

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

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

[Kernel-packages] [Bug 1765498] Re: linux-kvm: 4.15.0-1006.6 -proposed tracker

[Brad Figg]

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

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

** 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 --
  kernel-master-bug: 1765490
  phase: Packaging
+ kernel-phase-changed:Saturday, 21. April 2018 18:05 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1765490
- phase: Packaging
- kernel-phase-changed:Saturday, 21. April 2018 18:05 UTC
- kernel-phase:Uploaded
+ phase: Uploaded

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Confirmed
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 --
  kernel-master-bug: 1765490
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1761831] Re: ASUS B150M Gaming hibernate/resume failure

[Radu Axente]

Ubuntu MATE-18.04 - daily build - 21.04.2018 - Uname: Linux
4.15.0.15-generic x86_64

Additional Drivers - NVIDIA Corporation: GM107 [GeForce GTX 750 Ti]
- Using NVIDIA binary driver-version 340.106 from ndivia-340 (proprietary)

Same issue.  Hibernate works (sudo pm-hibernate), but Resume from
Hibernate doesn't (PC starts normal, like starting the PC after a normal
shutdown).

Cannot submit automatic issue report, "DuplicateOf:
https://bugs.launchpad.net/bugs/176831 (this issue report).

Will remove the nVidia graphic card, and re-install Ubuntu MATE-18.04
daily build (21.04.2018), but I have no hope that it will work.

Please check:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759860 (just the Intel 
CPU and the available Intel GPU) - specially this comment 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759860/comments/7

Looks like there is no issue with Debian 9 and Linux Kernels 4.15 /
4.16.

Please also check my comments here: https://ubuntu-mate.community/t
/hibernation-broken-in-kernel-4-13-0-25/15736

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

Title:
  ASUS B150M Gaming hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate /
  Resume from Hibernate - does not work

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mihai  1718 F pulseaudio
   /dev/snd/controlC0:  mihai  1718 F pulseaudio
  Date: Fri Apr  6 20:19:49 2018
  DuplicateSignature: hibernate/resume:System manufacturer System Product 
Name:0601
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03
  InstallationDate: Installed on 2018-04-06 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  InterpreterPath: /usr/bin/python3.6
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
   Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: [System manufacturer System Product Name] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0601
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M PRO GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

Re: [Kernel-packages] [Bug 1764866] Re: [123779.594327] general protection fault: 0000 [#1] SMP PTI

[Tom Louwrier]

Hi Joseph,

So far I haven't seen it again, so it may have been a one time glitch.

cheers
Tom


On 20-04-18 20:26, Joseph Salisbury wrote:
> Do you have a way to reproduce this bug, or was it a one time event?
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Tags added: kernel-da-key
>
> ** Also affects: linux (Ubuntu Bionic)
>Importance: Medium
>Status: Confirmed
>
> ** Changed in: linux (Ubuntu Bionic)
>Status: Confirmed => Incomplete
>

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

Title:
  [123779.594327] general protection fault:  [#1] SMP PTI

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  Ubuntu 18.04 beta, clean install, updates twice a day.
  Loaded updates this afternoon, no reboot required. Closed the laptop, went 
home and opened it. Some issues winth networking so decided te restart. That 
didn't finish well so had to force a power cycle. Booted well, but got this 
error report.
  Machine is a Dell Latitude 3540 (early 2014).

  If you need more information just let me know.

  cheers
  Tom

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1184 F pulseaudio
thomas 1495 F pulseaudio
  Date: Tue Apr 17 18:41:18 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=8be4eddb-bbc0-427f-89b0-35a54564b33a
  InstallationDate: Installed on 2018-04-14 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180407)
  MachineType: Dell Inc. Latitude 3540
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: [123779.594327] general protection fault:  [#1] SMP PTI
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 02RKKX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/17/2014:svnDellInc.:pnLatitude3540:pvrA06:rvnDellInc.:rn02RKKX:rvrA00:cvnDellInc.:ct8:cvrA06:
  dmi.product.name: Latitude 3540
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460

[David Henningsson]

Kernel 3d7682af228fd78dc46bc: Black screen.

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

Title:
  Black screen on 18.04 + AMD RX460

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

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

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

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

[Kernel-packages] [Bug 1765980] Re: IPv6 fragments with nf_conntrack_reasm loaded cause net_mutex deadlock upon LXD container shutdown

[Michael Sparmann]

The cause of the issue is already understood, and the machine currently isn't 
running an unmodified kernel for debugging reasons. Apport logs won't help here.
Contact me if you need specific information.

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

Title:
  IPv6 fragments with nf_conntrack_reasm loaded cause net_mutex deadlock
  upon LXD container shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've spent the last few days tracking down an issue where an attempt
  to shutdown an LXD container after several hours of host uptime on
  Ubuntu Bionic (4.15.0-15.16-generic) would cause a kworker thread to
  start spinning on one CPU core and all subsequent container start/stop
  operations to fail.

  The underlying issue is that a kworker thread (executing cleanup_net)
  spins in inet_frags_exit_net, waiting for sum_frag_mem_limit(nf) to
  become zero, which never happens becacuse it has underflowed to some
  negative multiple of 64. That kworker thread keeps holding net_mutex
  and therefore blocks any further container start/stops. That in turn
  is triggered by receiving a fragmented IPv6 MDNS packet in my
  instance, but it could probably be triggered by any fragmented IPv6
  traffic.

  The reason for the frag mem limit counter to underflow is
  nf_ct_frag6_reasm deducting more from it than the sum of all previous
  nf_ct_frag6_queue calls added, due to pskb_expand_head (called through
  skb_unclone) adding a multiple of 64 to the SKB's truesize, due to
  kmalloc_reserve allocating some additional slack space to the buffer.

  Removing this line:
  size = SKB_WITH_OVERHEAD(ksize(data));
  or making it conditional with nhead or ntail being nonzero works around the 
issue, but a proper fix for this seems complicated.
  There is already a comment saying "It is not generally safe to change 
skb->truesize." right above the offending modification of truesize, but the if 
statement guarding it apparently doesn't keep out all problematic cases.
  I'll leave figuring out the proper way to fix this to the maintainers of this 
area... ;)

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

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

[Kernel-packages] [Bug 1761831] Re: ASUS B150M Gaming hibernate/resume failure

[Radu Axente]

Ubuntu MATE-18.04 - daily build - 21.04.2018 - Uname: Linux
4.15.0.15-generic x86_64

Additional Drivers - NVIDIA Corporation: GM107 [GeForce GTX 750 Ti]
- Using NVIDIA driver metapackage from nvidia-driver-390 (proprietary, tested)

Same issue.  Hibernate works (sudo pm-hibernate), but Resume from
Hibernate doesn't (PC starts normal, like starting the PC after a
shutdown).

Cannot submit automatic issue report.  It reports "DuplicateOf:
https//bugs.launchpad.net/bugs/176831" (this issue report).

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

Title:
  ASUS B150M Gaming hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE 18.04 Beta 2 - ASUS B150M Gaming motherboard - Hibernate /
  Resume from Hibernate - does not work

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mihai  1718 F pulseaudio
   /dev/snd/controlC0:  mihai  1718 F pulseaudio
  Date: Fri Apr  6 20:19:49 2018
  DuplicateSignature: hibernate/resume:System manufacturer System Product 
Name:0601
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=73c50cf6-8865-4b1e-8bc6-859390fe5c03
  InstallationDate: Installed on 2018-04-06 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  InterpreterPath: /usr/bin/python3.6
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
   Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard 
G230
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=01246553-6d0b-4885-8882-fdd7299f9693 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: [System manufacturer System Product Name] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0601
  dmi.board.asset.tag: Default string
  dmi.board.name: B150M PRO GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0601:bd12/22/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB150MPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1765995] [NEW] package linux-image-4.15.0-18-generic (not installed) failed to install/upgrade: Unterprozess installed linux-image-4.15.0-18-generic package pre-removal script g

[Dejan V.]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-18-generic (not installed)
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
AptOrdering:
 linux-headers-4.15.0-18-generic:amd64: Purge
 linux-image-4.15.0-18-generic:amd64: Purge
 NULL: ConfigurePending
 NULL: PurgePending
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Apr 21 15:05:48 2018
ErrorMessage: Unterprozess installed linux-image-4.15.0-18-generic package 
pre-removal script gab den Fehler-Ausgangsstatus 1 zurück
InstallationDate: Installed on 2017-12-02 (140 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: linux-signed
Title: package linux-image-4.15.0-18-generic (not installed) failed to 
install/upgrade: Unterprozess installed linux-image-4.15.0-18-generic package 
pre-removal script gab den Fehler-Ausgangsstatus 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package linux-image-4.15.0-18-generic (not installed) failed to
  install/upgrade: Unterprozess installed linux-image-4.15.0-18-generic
  package pre-removal script gab den Fehler-Ausgangsstatus 1 zurück

Status in linux-signed package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-18-generic (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  AptOrdering:
   linux-headers-4.15.0-18-generic:amd64: Purge
   linux-image-4.15.0-18-generic:amd64: Purge
   NULL: ConfigurePending
   NULL: PurgePending
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Apr 21 15:05:48 2018
  ErrorMessage: Unterprozess installed linux-image-4.15.0-18-generic package 
pre-removal script gab den Fehler-Ausgangsstatus 1 zurück
  InstallationDate: Installed on 2017-12-02 (140 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: linux-signed
  Title: package linux-image-4.15.0-18-generic (not installed) failed to 
install/upgrade: Unterprozess installed linux-image-4.15.0-18-generic package 
pre-removal script gab den Fehler-Ausgangsstatus 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1765998] [NEW] FS access deadlock with btrfs quotas enabled

[Michael Sparmann]

Public bug reported:

I'm running into an issue on Ubuntu Bionic (but not Xenial) where
shortly after boot, under heavy load from many LXD containers starting
at once, access to the btrfs filesystem that the containers are on
deadlocks.

The issue is quite hard to reproduce on other systems, quite likely
related to the size of the filesystem involved (4 devices with a total
of 8TB, millions of files, ~20 subvolumes with tens of snapshots each)
and the access pattern from many LXD containers at once. It definitely
goes away when disabling btrfs quotas though. Another prerequisite to
trigger this bug may be the container subvolumes sharing extents (from
their parent image or due to deduplication).

I can only reliably reproduce it on a production system that I can only do very 
limited testing on, however I have been able to gather the following 
information:
- Many threads are stuck, trying to aquire locks on various tree roots, which 
are never released by their current holders.
- There always seem to be (at least) two threads executing rmdir syscalls which 
are creating the circular dependency: One of them is in btrfs_cow_block => ... 
=> btrfs_qgroup_trace_extent_post => ... => find_parent_nodes and wants to 
acquire a lock that was already aquired by btrfs_search_slot of the other rmdir.
- Reverting this patch seems to prevent it from happening: 
https://patchwork.kernel.org/patch/9573267/

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

Title:
  FS access deadlock with btrfs quotas enabled

Status in linux package in Ubuntu:
  New

Bug description:
  I'm running into an issue on Ubuntu Bionic (but not Xenial) where
  shortly after boot, under heavy load from many LXD containers starting
  at once, access to the btrfs filesystem that the containers are on
  deadlocks.

  The issue is quite hard to reproduce on other systems, quite likely
  related to the size of the filesystem involved (4 devices with a total
  of 8TB, millions of files, ~20 subvolumes with tens of snapshots each)
  and the access pattern from many LXD containers at once. It definitely
  goes away when disabling btrfs quotas though. Another prerequisite to
  trigger this bug may be the container subvolumes sharing extents (from
  their parent image or due to deduplication).

  I can only reliably reproduce it on a production system that I can only do 
very limited testing on, however I have been able to gather the following 
information:
  - Many threads are stuck, trying to aquire locks on various tree roots, which 
are never released by their current holders.
  - There always seem to be (at least) two threads executing rmdir syscalls 
which are creating the circular dependency: One of them is in btrfs_cow_block 
=> ... => btrfs_qgroup_trace_extent_post => ... => find_parent_nodes and wants 
to acquire a lock that was already aquired by btrfs_search_slot of the other 
rmdir.
  - Reverting this patch seems to prevent it from happening: 
https://patchwork.kernel.org/patch/9573267/

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

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

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

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

Title:
  IPv6 fragments with nf_conntrack_reasm loaded cause net_mutex deadlock
  upon LXD container shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've spent the last few days tracking down an issue where an attempt
  to shutdown an LXD container after several hours of host uptime on
  Ubuntu Bionic (4.15.0-15.16-generic) would cause a kworker thread to
  start spinning on one CPU core and all subsequent container start/stop
  operations to fail.

  The underlying issue is that a kworker thread (executing cleanup_net)
  spins in inet_frags_exit_net, waiting for sum_frag_mem_limit(nf) to
  become zero, which never happens becacuse it has underflowed to some
  negative multiple of 64. That kworker thread keeps holding net_mutex
  and therefore blocks any further container start/stops. That in turn
  is triggered by receiving a fragmented IPv6 MDNS packet in my
  instance, but it could probably be triggered by any fragmented IPv6
  traffic.

  The reason for the frag mem limit counter to underflow is
  nf_ct_frag6_reasm deducting more from it than the sum of all previous
  nf_ct_frag6_queue calls added, due to pskb_expand_head (called through
  skb_unclone) adding a multiple of 64 to the SKB's truesize, due to
  kmalloc_reserve allocating some additional slack space to the buffer.

  Removing this line:
  size = SKB_WITH_OVERHEAD(ksize(data));
  or making it conditional with nhead or ntail being nonzero works around the 
issue, but a proper fix for this seems complicated.
  There is already a comment saying "It is not generally safe to change 
skb->truesize." right about the offending modification of truesize, but the if 
statement guarding it apparently doesn't keep out all problematic cases.
  I'll leave figuring out the proper way to fix this to the maintainers of this 
area... ;)

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

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

[Kernel-packages] [Bug 1765977] [NEW] HiSilicon HNS NIC names are truncated in /proc/interrupts

[dann frazier]

Public bug reported:

[Impact]
HiSilicon HNS NIC names are truncated in /proc/interrupts, making it difficult 
for an admin to associate activity among adapters in the system.

[Test Case]
$ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //'
Without the fix:
  enahisic2i0-tx0
  enahisic2i0-tx1
  [...]
  enahisic2i0-tx8
  enahisic2i0-tx9
  enahisic2i0-tx1
  enahisic2i0-tx1
  enahisic2i0-tx1
  enahisic2i0-tx1
  enahisic2i0-tx1
  enahisic2i0-tx1
With the fix:
  enahisic2i0-tx0
  enahisic2i0-tx1
  enahisic2i0-tx2
  [...]
  enahisic2i0-tx8
  enahisic2i0-tx9
  enahisic2i0-tx10
  enahisic2i0-tx11
  enahisic2i0-tx12
  enahisic2i0-tx13
  enahisic2i0-tx14
  enahisic2i0-tx15

[Regression Risk]
Upstream patch, restricted to a single driver for a system we can directly test.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Artful)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

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

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  HiSilicon HNS NIC names are truncated in /proc/interrupts

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

Bug description:
  [Impact]
  HiSilicon HNS NIC names are truncated in /proc/interrupts, making it 
difficult for an admin to associate activity among adapters in the system.

  [Test Case]
  $ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //'
  Without the fix:
enahisic2i0-tx0
enahisic2i0-tx1
[...]
enahisic2i0-tx8
enahisic2i0-tx9
enahisic2i0-tx1
enahisic2i0-tx1
enahisic2i0-tx1
enahisic2i0-tx1
enahisic2i0-tx1
enahisic2i0-tx1
  With the fix:
enahisic2i0-tx0
enahisic2i0-tx1
enahisic2i0-tx2
[...]
enahisic2i0-tx8
enahisic2i0-tx9
enahisic2i0-tx10
enahisic2i0-tx11
enahisic2i0-tx12
enahisic2i0-tx13
enahisic2i0-tx14
enahisic2i0-tx15

  [Regression Risk]
  Upstream patch, restricted to a single driver for a system we can directly 
test.

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

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

[Kernel-packages] [Bug 1765980] [NEW] IPv6 fragments with nf_conntrack_reasm loaded cause net_mutex deadlock upon LXD container shutdown

[Michael Sparmann]

Public bug reported:

I've spent the last few days tracking down an issue where an attempt to
shutdown an LXD container after several hours of host uptime on Ubuntu
Bionic (4.15.0-15.16-generic) would cause a kworker thread to start
spinning on one CPU core and all subsequent container start/stop
operations to fail.

The underlying issue is that a kworker thread (executing cleanup_net)
spins in inet_frags_exit_net, waiting for sum_frag_mem_limit(nf) to
become zero, which never happens becacuse it has underflowed to some
negative multiple of 64. That kworker thread keeps holding net_mutex and
therefore blocks any further container start/stops. That in turn is
triggered by receiving a fragmented IPv6 MDNS packet in my instance, but
it could probably be triggered by any fragmented IPv6 traffic.

The reason for the frag mem limit counter to underflow is
nf_ct_frag6_reasm deducting more from it than the sum of all previous
nf_ct_frag6_queue calls added, due to pskb_expand_head (called through
skb_unclone) adding a multiple of 64 to the SKB's truesize, due to
kmalloc_reserve allocating some additional slack space to the buffer.

Removing this line:
size = SKB_WITH_OVERHEAD(ksize(data));
or making it conditional with nhead or ntail being nonzero works around the 
issue, but a proper fix for this seems complicated.
There is already a comment saying "It is not generally safe to change 
skb->truesize." right about the offending modification of truesize, but the if 
statement guarding it apparently doesn't keep out all problematic cases.
I'll leave figuring out the proper way to fix this to the maintainers of this 
area... ;)

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

Title:
  IPv6 fragments with nf_conntrack_reasm loaded cause net_mutex deadlock
  upon LXD container shutdown

Status in linux package in Ubuntu:
  New

Bug description:
  I've spent the last few days tracking down an issue where an attempt
  to shutdown an LXD container after several hours of host uptime on
  Ubuntu Bionic (4.15.0-15.16-generic) would cause a kworker thread to
  start spinning on one CPU core and all subsequent container start/stop
  operations to fail.

  The underlying issue is that a kworker thread (executing cleanup_net)
  spins in inet_frags_exit_net, waiting for sum_frag_mem_limit(nf) to
  become zero, which never happens becacuse it has underflowed to some
  negative multiple of 64. That kworker thread keeps holding net_mutex
  and therefore blocks any further container start/stops. That in turn
  is triggered by receiving a fragmented IPv6 MDNS packet in my
  instance, but it could probably be triggered by any fragmented IPv6
  traffic.

  The reason for the frag mem limit counter to underflow is
  nf_ct_frag6_reasm deducting more from it than the sum of all previous
  nf_ct_frag6_queue calls added, due to pskb_expand_head (called through
  skb_unclone) adding a multiple of 64 to the SKB's truesize, due to
  kmalloc_reserve allocating some additional slack space to the buffer.

  Removing this line:
  size = SKB_WITH_OVERHEAD(ksize(data));
  or making it conditional with nhead or ntail being nonzero works around the 
issue, but a proper fix for this seems complicated.
  There is already a comment saying "It is not generally safe to change 
skb->truesize." right about the offending modification of truesize, but the if 
statement guarding it apparently doesn't keep out all problematic cases.
  I'll leave figuring out the proper way to fix this to the maintainers of this 
area... ;)

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

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

[Kernel-packages] [Bug 1765232] Re: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

[Seth Forshee]

And now here's another test build with the upstream fixes. Note that the
last patch needed too much backporting to do in short order, and I had
to include one additional prerequisite:

http://people.canonical.com/~sforshee/lp1765232/linux-4.15.0-18.19+lp1765232v201804211053/

Please test the kernel from comment #12 first though, as I'm more
inclined to revert the patches for the moment. We may consider adding
them back later though with these additional fixes if they are confirmed
to resolve these hangs. Thanks!

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

Title:
  Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

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

Bug description:
  For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to
  4.15.0-15. The system hangs at boot up now. Rolling back to the old
  kernel everything works as expected. It appears to hang while trying
  to enumerate an SD card device, which isn't even installed. I have
  tried this on a Dell R620 and R820 and both have the exact same
  problem. I even downloaded a new installer iso from the daily builds
  to reinstall the OS and the installer hangs too now.

  Support for Dell PowerEdge 12th gen servers appears to be broken with
  kernel 4.15.0-15.

  https://imgur.com/VT9zd0w
  https://imgur.com/4BQPCXo

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

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

[Kernel-packages] [Bug 1765232] Re: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

[Seth Forshee]

Here's a test kernel with the reverts, please let us know ASAP whether
or not this fixes the issue.

http://people.canonical.com/~sforshee/lp1765232/linux-4.15.0-18.19+lp1765232v201804211006/

Thanks!

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

Title:
  Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

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

Bug description:
  For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to
  4.15.0-15. The system hangs at boot up now. Rolling back to the old
  kernel everything works as expected. It appears to hang while trying
  to enumerate an SD card device, which isn't even installed. I have
  tried this on a Dell R620 and R820 and both have the exact same
  problem. I even downloaded a new installer iso from the daily builds
  to reinstall the OS and the installer hangs too now.

  Support for Dell PowerEdge 12th gen servers appears to be broken with
  kernel 4.15.0-15.

  https://imgur.com/VT9zd0w
  https://imgur.com/4BQPCXo

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

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

[Kernel-packages] [Bug 1759723] Re: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation.

[Seth Forshee]

I think the patches from this bug are causing a problem. See LP:
#1765232 for details.

I've identified a number of upstream fixes for these patches, listed on
that bug. We are days out from release though, and the last of them
(d3056812e7df "genirq/affinity: Spread irq vectors among present CPUs as
far as possible") will require backporting or additional commits. We
don't have a lot of time to get testing on this.

As I read the description of this bug, the issue can be summed up as,
"stress the system, do CPU hotplug, then the system becomes
unresponsive." The other issue is summarized as, "my system hangs during
boot." Since the latter will prevent installation of 18.04 I regard it
as the more serious issue.

Given all of this, I'm strongly inclined towards reverting these patches
for the release, then we can look at SRU-ing them along with all
necessary fixes. If the issue here is more serious than my reading of it
(i.e. it will prevent booting and installation of 18.04) please speak up
ASAP.

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

Title:
  ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle
  hangs after hotplug CPU add operation.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  ===
  Performed HOTPLUG cpu attach operation for the guest and guest console 
becomes unresponsive.

  Steps to re-create:
  ==
  1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels
   
  2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes

  root@boslcp3:/home# uname -a
  Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:/home# uname -r
  4.15.0-12-generic

  root@boslcp3g3:/kte/tools/setup.d# uname -a
  Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3g3:/kte/tools/setup.d# uname -r
  4.15.0-12-generic

  3. Started HTX & stress-ng for on guest for 10-15 min

  4. Cleaned up the tests to perform hot-plug and ensure enough memory
  and cpu was there (killed all Process using kill)

  5. Performed cpu hot-plug and guest went into hung state

  Before Hotplug:

  root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu
64

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  



  root@boslcp3:~#  

  6. After this operation, guest becomes unrepsonsive as below

  
  root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more 
than 120 seconds.
  [ 3626.146375]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 
seconds.
  [ 3626.146699]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 
seconds.
  [ 3626.147016]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 
seconds.
  [ 3626.147361]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds.
  [ 3626.147686]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds.
  [ 3626.147937]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds.
  [ 3626.148173]   Tainted: GW4.15.0-12-generic 
#13+leo20180320
  [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds.
  [ 3626.148406]   Tainted: GW

[Kernel-packages] [Bug 1765232] Re: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

[Seth Forshee]

I've been investigating, and I strongly suspect these commits for bug
1759723 are to blame.

 f0aff9ccc834 genirq/affinity: assign vectors to all possible CPUs
 9403a13fd07e blk-mq: simplify queue mapping & schedule with each possisble CPU

As far as I can tell there are 8 other fixes we'd need to look at
including, either addressing the same original commit that these patches
addressed or addressing bugs related to these two patches:

 16ccfff28976 nvme: pci: pass max vectors as num_possible_cpus() to 
pci_alloc_irq_vectors
 8b834bff1b73 scsi: hpsa: fix selection of reply queue
 adbe552349f2 scsi: megaraid_sas: fix selection of reply queue
 b5b6e8c8d3b4 scsi: virtio_scsi: fix IO hang caused by automatic irq vector 
affinity
 7bed45954b95 blk-mq: make sure hctx->next_cpu is set correctly 
 a1c735fb7907 blk-mq: make sure that correct hctx->next_cpu is set
 bffa9909a6b4 blk-mq: don't keep offline CPUs mapped to hctx 0
 d3056812e7df genirq/affinity: Spread irq vectors among present CPUs as far as 
possible

Or we can revert those two patches. I'm considering both options, will
provide one or two test kernels 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/1765232

Title:
  Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

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

Bug description:
  For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to
  4.15.0-15. The system hangs at boot up now. Rolling back to the old
  kernel everything works as expected. It appears to hang while trying
  to enumerate an SD card device, which isn't even installed. I have
  tried this on a Dell R620 and R820 and both have the exact same
  problem. I even downloaded a new installer iso from the daily builds
  to reinstall the OS and the installer hangs too now.

  Support for Dell PowerEdge 12th gen servers appears to be broken with
  kernel 4.15.0-15.

  https://imgur.com/VT9zd0w
  https://imgur.com/4BQPCXo

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

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

[Kernel-packages] [Bug 1760110] Re: Kernel 4.15.0-13.14 reboots instead of powering off (when on battery) on HP Spectre x360 ae-000x

[Dmitry Malykhanov]

4.15.0-12 had the same problem, please see #1756455 [1] (which is
absolutely the same as this one).

I have also tried all mainline kernels from 4.15.3 up to 4.17rc1, and
here are the results:

* all mainline kernels in branch 4.15 do NOT have any issues
* starting with mainline 4.16.0 it is impossible to shut down (reboots instead)
* Ubuntu kernel 4.15.0-12 HAS this problem

So this regression was introduced in Ubuntu kernel 4.15.0-12, and in
mainline kernel 4.16

1. https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1756455

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

Title:
  Kernel 4.15.0-13.14 reboots instead of powering off (when on battery)
  on HP Spectre x360 ae-000x

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This might be a duplicate of #1756455

  HP Spectre x360 13", model 13-ae004na, secure boot on, latest BIOS
  F.15A, Ubuntu is the only system on disk.

  When using kernel 4.15.0-13 the system does not power off but instead
  reboots. Both halt -p from the command line and menu action leads to
  reboot instead of turning hardware off. 4.15.0-12 has the same problem
  (see #1756455). Booting with kernel 4.15.0-10 resolves the issue,
  system turns off power and stays powered off.

  * secure boot enabled or disabled makes no difference

  * kernel 4.15.0-10 correctly powers off system (halt -p) every time,
  power source makes no difference

  * kernel 4.15.0-13 correctly powers off system only when running on AC

  * kernel 4.15.0-13 does NOT power off system (reboots instead) when AC
  power is NOT connected (running on battery) every time

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmitry 1648 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Mar 30 14:39:28 2018
  HibernationDevice: RESUME=UUID=7b592f97-cd3d-46d3-8183-1685fd2441b4
  InstallationDate: Installed on 2018-03-10 (20 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.15:bd02/22/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1755627] Re: ibrs/ibpb fixes result in excessive kernel logging

[daniel CURTIS]

Hello.

Today, I noticed the same entries in a log files such as
'/var/log/syslog' and via dmesg(1) on 16.04 LTS Release (i386/x86_32
arch) with v4.4.0-120-generic (4.4.117) Linux kernel. The one thing,
that is different is 'use_ibrs' value. In my case it's:

[~]$ sudo dmesg
[  464.877859] use_ibrs = 0, use_ibpb = 4
[  467.893757] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
[  467.893762] use_ibrs = 4, use_ibpb = 4
(...)

I'm writing about this, because I don't see '0' in any of the above
posts etc. Anyway, as Mr Kamal Mostafa wrote, I will wait for a
"-proposed" kernel.

Thanks, best regards.

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

Title:
  ibrs/ibpb fixes result in excessive kernel logging

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

Bug description:
  Since at least kernel 4.4.0-116, every invocation of `sysctl -a`
  results in kernel logs similar to the following:

  % sysctl -a &>/dev/null; dmesg -T | tail -8
  [Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:06:36 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:06:36 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:06:36 2018] read cpu 1 ibrs val 0
  [Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:06:36 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:06:36 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:06:36 2018] read cpu 1 ibrs val 0

  The output varies with the number of CPUs.

  After digging a bit, it turns out this is triggered upon every read of
  `kernel.ibrs_dump`:

  % for i in {1..3}; do sysctl kernel.ibrs_dump; dmesg -T | tail -8; echo; 
sleep 1; done
  kernel.ibrs_dump = 0
  [Wed Mar 14 00:08:48 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:08:48 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:08:48 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:08:48 2018] read cpu 1 ibrs val 0
  [Wed Mar 14 00:08:48 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:08:48 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:08:48 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:08:48 2018] read cpu 1 ibrs val 0

  kernel.ibrs_dump = 0
  [Wed Mar 14 00:08:49 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:08:49 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:08:49 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:08:49 2018] read cpu 1 ibrs val 0
  [Wed Mar 14 00:08:49 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:08:49 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:08:49 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:08:49 2018] read cpu 1 ibrs val 0

  kernel.ibrs_dump = 0
  [Wed Mar 14 00:08:50 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:08:50 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:08:50 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:08:50 2018] read cpu 1 ibrs val 0
  [Wed Mar 14 00:08:50 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
  [Wed Mar 14 00:08:50 2018] use_ibrs = 4, use_ibpb = 4
  [Wed Mar 14 00:08:50 2018] read cpu 0 ibrs val 0
  [Wed Mar 14 00:08:50 2018] read cpu 1 ibrs val 0

  
  Those tests were against an EC2 instance running Ubuntu 4.4.0-116.140-generic 
4.4.98 per /proc/version_signature

  Normally this would not be the biggest concern but we have tooling
  that gathers instance info on a schedule, including sysctl output,
  thus resulting in the kernel ring buffer being full of nothing but
  said output in most cases and hindering live troubleshooting as a
  result.

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

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

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

[bugproxy]

--- Comment From chngu...@us.ibm.com 2018-04-20 16:48 EDT---
Boslcp3 is back with the new kernel from #94.

root@boslcp3:~# cat /proc/cmdline
root=UUID=bab108a0-d0a6-4609-87f1-6e33d0ad633c ro splash quiet 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M

I will launch our test soon.

--- Comment From chngu...@us.ibm.com 2018-04-20 20:05 EDT---
(In reply to comment #98)
> Boslcp3 is back with the new kernel from #94.
>
> root@boslcp3:~# uname -a
> Linux boslcp3 4.15.0-18-generic #19 SMP Fri Apr 20 12:45:38 CDT 2018 ppc64le
> ppc64le ppc64le GNU/Linux
> root@boslcp3:~# cat /proc/cmdline
> root=UUID=bab108a0-d0a6-4609-87f1-6e33d0ad633c ro splash quiet
> crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:
> 4096M@128M
>
> I will launch our test soon.

It is not looking good on boslcp3. After I start test, within 3 hours run, 
system is still pingable but I cannot ssh to it. Looking at the console, I see 
these on all over

[ 8785.370897] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 8785.370962]  1-...0: (4 GPs behind) idle=ca2/141/0 
softirq=15273/15273 fqs=1075891
[ 8785.371035]  (detected by 3, t=2179442 jiffies, g=2107, c=2106, q=386665)
[ 8785.371090] Task dump for CPU 1:
[ 8785.371123] kworker/1:3 R  running task0  4111  2 0x0804
[ 8785.371195] Call Trace:
[ 8785.371221] [c000d5c4fa00] [c8133cf8] worker_thread+0x98/0x630 
(unreliable)
[ 8848.390897] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 8848.390964]  1-...0: (4 GPs behind) idle=ca2/141/0 
softirq=15273/15273 fqs=1083603
[ 8848.391037]  (detected by 3, t=2195197 jiffies, g=2107, c=2106, q=389679)
[ 8848.391092] Task dump for CPU 1:
[ 8848.391125] kworker/1:3 R  running task0  4111  2 0x0804
[ 8848.391197] Call Trace:
[ 8848.391223] [c000d5c4fa00] [c8133cf8] worker_thread+0x98/0x630 
(unreliable)
[ 8857.031091] systemd[1]: systemd-journald.service: Start operation timed out. 
Terminating.
***

root@boslcp3:~# uname -a
Linux boslcp3 4.15.0-18-generic #19 SMP Fri Apr 20 12:45:38 CDT 2018 ppc64le 
ppc64le ppc64le GNU/Linux

--- Comment From chetj...@in.ibm.com 2018-04-21 08:08 EDT---
The two guests are impacted due to (In reply to comment #103)
> Updated  boslcp3 with latest PNOR:0420 & restarted tests on guests with
> kernel '4.15.0-18-generic'.
>
> $ ./ipmis bmc-boslcp3 fru print 47
> Product Name  : OpenPOWER Firmware
> Product Version   : open-power-SUPERMICRO-P9DSU-V1.11-20180420-imp
> Product Extra : op-build-4d27fab
> Product Extra : skiboot-v5.11-70-g5307c0ec7899-pc34e21f
> Product Extra : hostboot-742640c
> Product Extra : linux-4.15.14-openpower1-p81c2d44
> Product Extra : petitboot-v1.7.1-p8b80147
> Product Extra : machine-xml-32ce616
> Product Extra : occ-4f49f6
>
> root@boslcp3:~# uname -a
> Linux boslcp3 4.15.0-18-generic #19 SMP Fri Apr 20 12:45:38 CDT 2018 ppc64le
> ppc64le ppc64le GNU/Linux
> root@boslcp3:~# uname -r
> 4.15.0-18-generic
>
> Guests kernel:
> 
> root@boslcp3g3:~# uname -a
> Linux boslcp3g3 4.15.0-15-generic #16+bug166877 SMP Wed Apr 18 14:47:30 CDT
> 2018 ppc64le ppc64le ppc64le GNU/Linux
> root@boslcp3g3:~# uname -r
> 4.15.0-15-generic
>
> Regards,
> Indira

The two guests are impacted in the new run today (bug# 167104) and the
3rd one is not able to reach, but not dumping any console logs, we are
waiting to see what happens!

The host is running fine, so far, but w/o guest run I'm not sure how
soon can we verify this?

Please check on bug#167104 to make this recreate/verify fast.
The host continue

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub

[Kernel-packages] [Bug 1765232] Re: Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

[Seth Forshee]

I'd suggest prioritizing testing of the v4.15.17 mainline kernel as this
is the latest update bionic has incorporated. If that is broken then try
v4.15.18 to see if there's a fix there, otherwise it points to some
Ubuntu-specific changes or backports.

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

Title:
  Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers

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

Bug description:
  For Ubuntu 18.04 amd64 server, I updated the kernel from 4.15.0-13 to
  4.15.0-15. The system hangs at boot up now. Rolling back to the old
  kernel everything works as expected. It appears to hang while trying
  to enumerate an SD card device, which isn't even installed. I have
  tried this on a Dell R620 and R820 and both have the exact same
  problem. I even downloaded a new installer iso from the daily builds
  to reinstall the OS and the installer hangs too now.

  Support for Dell PowerEdge 12th gen servers appears to be broken with
  kernel 4.15.0-15.

  https://imgur.com/VT9zd0w
  https://imgur.com/4BQPCXo

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

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

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

[bugproxy]

--- Comment From dougm...@us.ibm.com 2018-04-21 08:45 EDT---
The latest logs show a panic in process_one_work() on CPU 145, some sort of 
NULL pointer fault, followed by 2 CPUs (22, 125) getting a "Bad interrupt in 
KVM entry/exit code, sig: 6" panic (possibly in response to the panic IPI). 
Those 2 CPUs timeout and the KDUMP kexec starts.

The KDUMP then gets the same process_one_work() panic, this time on CPU
1, followed by Hard LOCKUP detected on CPUs 0 and 1. rcu_sched then
starts detecting the stalled CPU(s), only trying to dump CPU 1.

The problem seems to keep changing. Originally it was a panic on a very
strange address in kmem_cache_alloc_node() from socket code. Later we
see a NULL pointer issue in pool_mayday_timeout() from KVM. Now we are
seeing a panic in process_one_work() from a kworker thread (unknown
workqueue). If these different panics all have the same cause, it would
seem to be something like memory corruption. Not being able to get a
clean dump is going to be a problem.

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   

Re: [Kernel-packages] [Bug 1765346] Re: [LENOVO 20C6CTO1WW] hibernate/resume failure

[Daniel Nespoulous]

Hello, the problem exists since several versions.
This is a new installation from the daily-live 20180418.

I installed
linux-image-4.17.0-041700rc1-generic_4.17.0-041700rc1.201804152230_amd64.deb
but the problem is the same.

When I run "sudo pm-hibernate" the power LED flashes quickly, the screen
turns off then on and power cut off.

Best regards, Daniel


2018-04-20 21:55 GMT+02:00 Joseph Salisbury 
:

> Did this issue start happening after an update/upgrade?  Was there a
> prior kernel version where you were not having this particular problem?
>
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.16 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc1/
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1765346
>
> Title:
>   [LENOVO 20C6CTO1WW] hibernate/resume failure
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   when I want to activate hibernation:
>
>   sudo apt install pm-tools
>   sudo update-initramfs -u -k $(uname -r)
>   sudo pm-hibernate
>
>   and when I restart it does not work and a bug report is activated
>
>   Thank you
>
>   ProblemType: KernelOops
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-4.15.0-15-generic 4.15.0-15.16 [modified:
> boot/vmlinuz-4.15.0-15-generic]
>   ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
>   Uname: Linux 4.15.0-15-generic x86_64
>   AlsaVersion: Advanced Linux Sound Architecture Driver Version
> k4.15.0-15-generic.
>   Annotation: This occurred during a previous hibernation, and prevented
> the system from resuming properly.
>   ApportVersion: 2.20.9-0ubuntu5
>   Architecture: amd64
>   ArecordDevices:
> List of CAPTURE Hardware Devices 
>card 1: PCH [HDA Intel PCH], device 0: CX20751/2 Analog [CX20751/2
> Analog]
>  Subdevices: 1/1
>  Subdevice #0: subdevice #0
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  daniel 1009 F pulseaudio
>/dev/snd/controlC0:  daniel 1009 F pulseaudio
>   Card0.Amixer.info:
>Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf161 irq 31'
>  Mixer name : 'Intel Haswell HDMI'
>  Components : 'HDA:80862807,80860101,0010'
>  Controls  : 35
>  Simple ctrls  : 5
>   Card1.Amixer.info:
>Card hw:1 'PCH'/'HDA Intel PCH at 0xf1614000 irq 29'
>  Mixer name : 'Conexant CX20751/2'
>  Components : 'HDA:14f1510f,17aa502a,00100100'
>  Controls  : 20
>  Simple ctrls  : 9
>   Date: Thu Apr 19 10:54:53 2018
>   DuplicateSignature: hibernate/resume:LENOVO 20C6CTO1WW:J9ETA1WW (2.27 )
>   ExecutablePath: /usr/share/apport/apportcheckresume
>   Failure: hibernate/resume
>   HibernationDevice: RESUME=UUID=0c900fd9-a707-4d1f-8088-f7f5eae10ad9
>   InstallationDate: Installed on 2018-04-18 (0 days ago)
>   InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64
> (20180417)
>   InterpreterPath: /usr/bin/python3.6
>   MachineType: LENOVO 20C6CTO1WW
>   ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
>   ProcEnviron:
>PATH=(custom, no user)
>LANG=fr_FR.UTF-8
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed
> root=UUID=6b35a054-8694-4722-b14c-f81669ed0650 ro quiet splash
> vt.handoff=1
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
> 3.6.5-2
>   PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
> 2.7.14-4
>   RelatedPackageVersions:
>linux-restricted-modules-4.15.0-15-generic N/A
>linux-backports-modules-4.15.0-15-generic  N/A
>linux-firmware 1.173
>   SourcePackage: linux
>   Title: [LENOVO 20C6CTO1WW] hibernate/resume failure
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   dmi.bios.date: 02/27/2018
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: J9ETA1WW (2.27 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20C6CTO1WW
>   dmi.board.vendor: LENOVO
>   dmi.board.version: SDK0E50510 WIN
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   

[Kernel-packages] [Bug 1280636] Re: 14e4:4365 [Dell Inspiron 15 3521] Regulatory domain is not set by default after install for wifi

[Laryllan]

@zebul666
The wl kernel module seems not to honor the crda setting. It doesn't connect to 
high channels at all.
See https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1574196

Nevertheless, Ubuntu still doesn't set the regulatory domain automatically.
I'm using 17.10.

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

Title:
  14e4:4365 [Dell Inspiron 15 3521] Regulatory domain is not set by
  default after install for wifi

Status in crda package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Expired

Bug description:
  After installation of ubuntu 13.10, /etc/default/crda contains the line
  REGDOMAIN=
  i.e. there is no regulatory domain set for the cfg80211 kernel module.

  iw reg get shows a
  country 00
  when I run iw list, it shows channel 12 and 13 as
  "(passive scanning, no IBSS)"
  (which is normal given that the reg domain is not set or the default one)

  hence, I can't even see a public wifi hotspot on channel 13 using
  ubuntu 13.10, in a local fast food restaurant with a big yellow M.
  It's the second one, and they really like to broadcast on channel 13,
  here

  As the installation process knowns the local time, it should be able
  to set the regulatory domain, either to EU or FR in my case, and avoid
  being forced to reboot into Windows (I had the option to), ignoring
  the root cause of the problem.

  So, if I quote the text in comment in /etc/default/crda, every default
  ubuntu installation "may infrige  on local legislature" (not in my
  case here)

  the bug is already in ubuntu 12.04 LTS.

  this is irrelevant but I use the bcmwl-kernel-source driver for my
  Dell 1704 Wireless card based on broadcom BCM4312 chipset on an
  Inspiron 15 (3521).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: crda 1.1.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Feb 15 17:39:41 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-01-22 (23 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: crda
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.crda: 2014-02-15T17:20:58.815551
  --- 
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1512 F pulseaudio
solstice   2146 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=da042858-6f7c-43ab-be22-cdfc22c75f24
  InstallationDate: Installed on 2014-03-01 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301)
  MachineType: Dell Inc. Inspiron 3521
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-13-generic 
root=UUID=50a1d7f2-d90f-40ed-83bc-36a0aba7ceb1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-13.33-generic 3.13.5
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-13-generic N/A
   linux-backports-modules-3.13.0-13-generic  N/A
   linux-firmware 1.125
  StagingDrivers: rts5139
  Tags:  trusty staging
  Uname: Linux 3.13.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 06RYX8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron 3521
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1574196] Re: Card with chipset BCM4360 [14e4:43a0] (rev 03) doesn't see 5Ghz networks with high channel number.

[Laryllan]

Same problem here, maybe it doesn't respect the crda settings provided by 
Ubuntu?
https://packages.ubuntu.com/artful/crda

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

Title:
  Card  with chipset BCM4360 [14e4:43a0] (rev 03) doesn't see 5Ghz
  networks with high channel number.

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  The card  Broadcom Corporation BCM4360 802.11ac Wireless Network
  Adapter [14e4:43a0] (rev 03) doesn't see 5Ghz networks with an high
  channel number, if you change the channel back to a lower one the
  network will be found again.

  In my case with channel 104 the network wasn't seen by the card, with
  channel 40 it works fine

  wireless-info script result:

  ## wireless info START ##

  Report from: 22 Apr 2016 19:23 CEST +0200

  Booted last: 22 Apr 2016 18:51 CEST +0200

  Script from: 27 Sep 2015 00:34 UTC +

  # release ###

  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Codename: trusty

  # kernel 

  Linux 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016
  x86_64 x86_64 x86_64 GNU/Linux

  Parameters: ro, quiet, splash, vt.handoff=7

  # desktop ###

  Ubuntu

  # lspci #

  03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7758]
   Kernel driver in use: r8169

  04:00.0 Network controller [0280]: Broadcom Corporation BCM4360 802.11ac 
Wireless Network Adapter [14e4:43a0] (rev 03)
   Subsystem: Broadcom Corporation Device [14e4:0619]
   Kernel driver in use: wl

  # lsusb #

  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
  Bus 001 Device 004: ID 1532:0016 Razer USA, Ltd DeathAdder Mouse
  Bus 001 Device 003: ID 258a:0001
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  # PCMCIA card info ##

  # rfkill 

  0: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  1: brcmwl-0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  # lsmod #

  wl   6367819  0
  mxm_wmi13021  1 nouveau
  wmi19177  2 mxm_wmi,nouveau
  cfg80211  496328  1 wl

  # interfaces 

  auto lo
  iface lo inet loopback

  # ifconfig ##

  eth0  Link encap:Ethernet  HWaddr 
    UP BROADCAST MULTICAST  MTU:1500  Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  virbr0Link encap:Ethernet  HWaddr 
    inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
    UP BROADCAST MULTICAST  MTU:1500  Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  wlan2 Link encap:Ethernet  HWaddr 
    inet addr:192.168.1.6  Bcast:192.168.1.255  Mask:255.255.255.0
    inet6 addr: fe80::/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:45040 errors:0 dropped:0 overruns:0 frame:7469
    TX packets:33232 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:33581962 (33.5 MB)  TX bytes:6334838 (6.3 MB)
    Interrupt:18

  # iwconfig ##

  eth0  no wireless extensions.

  lono wireless extensions.

  virbr0no wireless extensions.

  wlan2 IEEE 802.11abg  ESSID:"LamerTexWiFi"
    Mode:Managed  Frequency:2.437 GHz  Access Point: 
    Retry  long limit:7   RTS thr:off   Fragment thr:off
    Power Management:off

  # route #

  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0  00 wlan2
  192.168.1.0 0.0.0.0 255.255.255.0   U 9  0

[Kernel-packages] [Bug 1762844] dmesg output 0418

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-18 12:01 
EDT---


** Attachment added: "dmesg output 0418"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5124759/+files/dmesg.201804181042

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

[Kernel-packages] [Bug 1762844] Host console log

[bugproxy]

--- Comment on attachment From chngu...@us.ibm.com 2018-04-13 17:17 
EDT---


The full log of the Host during couple reboot, start test on guest then system 
drop into xmon.

** Attachment added: "Host console log"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5124757/+files/boslcp3.0413.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c 

[Kernel-packages] [Bug 1762844] dmesg logs from xmon prompt_boslcp3

[bugproxy]

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-16 01:31 
EDT---


Attached dl logs from xmon pormpt _boslcp3

** Attachment added: "dmesg logs from xmon prompt_boslcp3"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5124758/+files/dmesg_xmon_boslcp3.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  

[Kernel-packages] [Bug 1762844] console log

[bugproxy]

--- Comment (attachment only) From chngu...@us.ibm.com 2018-04-20 20:08 
EDT---


** Attachment added: "console log"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5124760/+files/boslcp3.0420.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  

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

[bugproxy]

--- Comment From indira.pr...@in.ibm.com 2018-04-21 02:01 EDT---
Updated  boslcp3 with latest PNOR:0420 & restarted tests on guests with kernel 
'4.15.0-18-generic'.

$ ./ipmis bmc-boslcp3 fru print 47
Product Name  : OpenPOWER Firmware
Product Version   : open-power-SUPERMICRO-P9DSU-V1.11-20180420-imp
Product Extra : op-build-4d27fab
Product Extra : skiboot-v5.11-70-g5307c0ec7899-pc34e21f
Product Extra : hostboot-742640c
Product Extra : linux-4.15.14-openpower1-p81c2d44
Product Extra : petitboot-v1.7.1-p8b80147
Product Extra : machine-xml-32ce616
Product Extra : occ-4f49f6

root@boslcp3:~# uname -a
Linux boslcp3 4.15.0-18-generic #19 SMP Fri Apr 20 12:45:38 CDT 2018 ppc64le 
ppc64le ppc64le GNU/Linux
root@boslcp3:~# uname -r
4.15.0-18-generic

Guests kernel:

root@boslcp3g3:~# uname -a
Linux boslcp3g3 4.15.0-15-generic #16+bug166877 SMP Wed Apr 18 14:47:30 CDT 
2018 ppc64le ppc64le ppc64le GNU/Linux
root@boslcp3g3:~# uname -r
4.15.0-15-generic

Regards,
Indira

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 

[Kernel-packages] [Bug 1762844] boslcp3_crash_aprl13

[bugproxy]

--- Comment (attachment only) From indira.pr...@in.ibm.com 2018-04-13 03:24 
EDT---


** Attachment added: "boslcp3_crash_aprl13"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5124756/+files/boslcp3_crash_aprl13.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c 

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

[bugproxy]

--- Comment From prad...@us.ibm.com 2018-04-21 01:53 EDT---
Looks like an Oops similar to the previous one in comment#39 starting a 
sequence of events

root@boslcp3:~# [ 2837.030181] Unable to handle kernel paging request for data 
at address 0x0008
[ 2837.030253] Faulting instruction address: 0xc01336fc
[ 2837.030295] Oops: Kernel access of bad area, sig: 11 [#1]
[ 2837.030328] LE SMP NR_CPUS=2048 NUMA PowerNV
[ 2837.030364] Modules linked in: vhost_net vhost macvtap macvlan tap 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter 
ebtables devlink ip6table_filter ip6_tables iptable_filter rpcsec_gss_krb5 
nfsv4 nfs fscache kvm_hv binfmt_misc kvm dm_service_time dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua joydev input_leds idt_89hpesx mac_hid 
vmx_crypto crct10dif_vpmsum at24 ofpart cmdlinepart uio_pdrv_genirq uio 
powernv_flash mtd ibmpowernv ipmi_powernv ipmi_devintf ipmi_msghandler opal_prd 
nfsd auth_rpcgss nfs_acl lockd grace sunrpc sch_fq_codel ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq ses enclosure hid_generic
[ 2837.030909]  usbhid hid qla2xxx ast i2c_algo_bit ttm ixgbe drm_kms_helper 
mpt3sas nvme_fc syscopyarea sysfillrect nvme_fabrics sysimgblt fb_sys_fops 
nvme_core raid_class crc32c_vpmsum drm i40e scsi_transport_sas 
scsi_transport_fc mdio aacraid
[ 2837.031053] CPU: 145 PID: 1182 Comm: kworker/145:1 Not tainted 
4.15.0-18-generic #19
[ 2837.031107] NIP:  c01336fc LR: c0133cf8 CTR: c0cfefa0
[ 2837.031156] REGS: c000200e44c77a10 TRAP: 0300   Not tainted  
(4.15.0-18-generic)
[ 2837.031204] MSR:  90009033   CR: 28000822  
XER: 
[ 2837.031257] CFAR: c0133cf4 DAR: 0008 DSISR: 4000 
SOFTE: 0
[ 2837.031257] GPR00: c0133cf8 c000200e44c77c90 c16eae00 
c000200e44bda5c0
[ 2837.031257] GPR04: c00fdf6f7da0 c000200e618f7da0 c000200e618fa305 
c00fdf6f7cc8
[ 2837.031257] GPR08: c000200e6190c960 2440  
c0080f04e0f8
[ 2837.031257] GPR12:  c7a83b00 c013c788 
c000200e50ebf3c0
[ 2837.031257] GPR16:    

[ 2837.031257] GPR20: c000200e618f7d80   
fef7
[ 2837.031257] GPR24: 0402  c000200e618f8100 
c1713b00
[ 2837.031257] GPR28: c000200e618f7da0  c000200e618f7d80 
c000200e44bda5c0
[ 2837.031687] NIP [c01336fc] process_one_work+0x3c/0x5a0
[ 2837.031727] LR [c0133cf8] worker_thread+0x98/0x630
[ 2837.031760] Call Trace:
[ 2837.031778] [c000200e44c77c90] [c0133974] 
process_one_work+0x2b4/0x5a0 (unreliable)
[ 2837.031828] [c000200e44c77d20] [c0133cf8] worker_thread+0x98/0x630
[ 2837.031885] [c000200e44c77dc0] [c013c928] kthread+0x1a8/0x1b0
[ 2837.031928] [c000200e44c77e30] [c000b528] 
ret_from_kernel_thread+0x5c/0xb4
[ 2837.031976] Instruction dump:
[ 2837.032001] 6000 7d908026 fba1ffe8 fbc1fff0 91810008 f821ff71 e924 
712a0004
[ 2837.032052] 793d05e4 40820008 3ba0 ebc30048  815e0010 81290100 
714a0004
[ 2837.032104] ---[ end trace ae121b1a8fbe89f8 ]---

A cascading series of events follow ending up in hard lockups. However,
that likely happens when  IPIs fail and these are secondary events.

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi