[Kernel-packages] [Bug 1774740] Re: Cannot hibernate : systemd-sleep[22332]: Failed to write 'disk' to /sys/power/state: Cannot allocate memory

[Kai-Heng Feng]

This is more likely to be a kernel bug.

** Also 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/1774740

Title:
  Cannot hibernate : systemd-sleep[22332]: Failed to write 'disk' to
  /sys/power/state: Cannot allocate memory

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

Bug description:
  Roughly every other time, hibernating (via systemctl hibernate) fails
  : it begins then I get back to lightdm prompt.

  journalctl shows the lines

  systemd[1]: Starting Hibernate...
  systemd-sleep[22333]: Spawned 
/lib/systemd/system-sleep/10_unattended-upgrades-hibernate as 22334.
  systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/hdparm as 22335.
  systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/10_grub-common as 
22336.
  systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/wpasupplicant as 
22337.
  systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/tuxonice as 22338.
  systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/back_to_ram as 22339.
  systemd-sleep[22333]: 
/lib/systemd/system-sleep/10_unattended-upgrades-hibernate succeeded.
  systemd-sleep[22333]: /lib/systemd/system-sleep/back_to_ram succeeded.
  systemd-sleep[22333]: /lib/systemd/system-sleep/hdparm succeeded.
  systemd-sleep[22333]: /lib/systemd/system-sleep/tuxonice succeeded.
  systemd-sleep[22333]: /lib/systemd/system-sleep/10_grub-common succeeded.
  systemd-sleep[22333]: /lib/systemd/system-sleep/wpasupplicant succeeded.
  systemd-sleep[22332]: system-sleep succeeded.
  systemd-sleep[22332]: Suspending system...
  kernel: PM: hibernation entry
  kernel: PM: Syncing filesystems ... 
  kernel: PM: done.
  kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
  kernel: OOM killer disabled.
  kernel: PM: Marking nosave pages: [mem 0x-0x0fff]
  kernel: PM: Marking nosave pages: [mem 0x00058000-0x00058fff]
  kernel: PM: Marking nosave pages: [mem 0x0009e000-0x000f]
  kernel: PM: Marking nosave pages: [mem 0xabbf4000-0xabbf5fff]
  kernel: PM: Marking nosave pages: [mem 0xbb835000-0xbc5fefff]
  kernel: PM: Marking nosave pages: [mem 0xbc60-0x]
  kernel: PM: Basic memory bitmaps created
  kernel: PM: Preallocating image memory... 
  kernel: acpi LNXPOWER:16: Turning OFF
  kernel: acpi LNXPOWER:15: Turning OFF
  kernel: acpi LNXPOWER:14: Turning OFF
  kernel: acpi LNXPOWER:13: Turning OFF
  kernel: acpi LNXPOWER:12: Turning OFF
  kernel: acpi LNXPOWER:11: Turning OFF
  kernel: acpi LNXPOWER:10: Turning OFF
  kernel: acpi LNXPOWER:0f: Turning OFF
  kernel: acpi LNXPOWER:0e: Turning OFF
  kernel: acpi LNXPOWER:0d: Turning OFF
  kernel: acpi LNXPOWER:0c: Turning OFF
  kernel: acpi LNXPOWER:0b: Turning OFF
  kernel: acpi LNXPOWER:0a: Turning OFF
  kernel: acpi LNXPOWER:09: Turning OFF
  kernel: acpi LNXPOWER:08: Turning OFF
  kernel: acpi LNXPOWER:07: Turning OFF
  kernel: acpi LNXPOWER:06: Turning OFF
  kernel: acpi LNXPOWER:05: Turning OFF
  kernel: acpi LNXPOWER:04: Turning OFF
  kernel: acpi LNXPOWER:03: Turning OFF
  kernel: PM: Basic memory bitmaps freed
  kernel: OOM killer enabled.
  kernel: Restarting tasks ... done.
  kernel: video LNXVIDEO:00: Restoring backlight state
  kernel: PM: hibernation exit
  whoopsie[1377]: [00:31:31] Cannot reach: https://daisy.ubuntu.com
  whoopsie[1377]: [00:31:31] Cannot reach: https://daisy.ubuntu.com
  systemd-sleep[22332]: Failed to write 'disk' to /sys/power/state: Cannot 
allocate memory
  acpid[1079]: client 1225[0:0] has disconnected
  systemd[1]: systemd-hibernate.service: Main process exited, code=exited, 
status=1/FAILURE
  acpid[1079]: client connected from 1225[0:0]
  systemd[1]: Failed to start Hibernate.
  acpid[1079]: 1 client rule loaded
  systemd[1]: Dependency failed for Hibernate.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu21.2
  ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun  2 00:34:35 2018
  InstallationDate: Installed on 2016-09-07 (632 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision Tower 3620
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6ebb7e70-29f5-4ddf-a1a1-8cc58113961a ro nomodeset
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.8.1
  dmi.board.name: 09WH54
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.8.1:bd01/31/

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

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

Title:
  mdadm raid soft lock-ups ubuntu kernel 4.13.0-36 Inbox  x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  we're running Ubuntu 16.04.4, mdadm - v3.3 and Kernel 4.13.0-36(ubuntu 
package linux-image-generic-hwe-16.04).
  We have created raid10 using 22 960GB SSDs [1] . The problem we're
  experiencing is that /usr/share/mdadm/checkarray
  (executed by cron, included in a mdadm pkg) results in (soft?)
  deadlock - load on the node spikes up to 500-700 and all I/O operations
  are blocked for a period of time. We can see traces liek these [2] in
  our kernel log.

  e.g. it ends up in static state like

  test@os-node1:~$ cat /proc/mdstat
  Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] 
[raid10]
  md1 : active raid10 dm-23[9] dm-22[8] dm-21[7] dm-20[6] dm-18[4] dm-19[5] 
dm-17[3]
  dm-16[21] dm-15[20] dm-14[2] dm-13[19] dm-12[18] dm-11[17]
  dm-10[16] dm-9[15] dm-8[14] dm-7[13] dm-6[12] dm-5[11] 
dm-4[10] dm-3[1] dm-2[0]
10313171968 blocks super 1.2 512K chunks 2 near-copies [22/22] 
[UU]
[===>.]  check = 19.0% (1965748032/10313171968) 
finish=1034728.8min speed=134K/sec
bitmap: 0/39 pages [0KB], 131072KB chunk
  unused devices: 

  and the only solution is to hard reboot the node. What we found out is that it
  doesn't happen on idle raid, we have to generate some significant load
  (10 VMs running fio[3] with 500GB HDDs.) to be able to reproduce the issue.

  Anyone ever experienced similar issues? Do you have any suggestions how to
  better trouble shoot this issue and maybe identify if disks or software layer
  is responsible for this behavior

  [1] http://www.samsung.com/us/dell/pdfs/PM1633a_Flyer_2016_v4.pdf
  [2] https://gist.github.com/haad/09213bab1bc30a00c7d255c0bc60897b
  [3] https://github.com/axboe/fio

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

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Cannot hibernate : systemd-sleep[22332]: Failed to write 'disk' to
  /sys/power/state: Cannot allocate memory

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

Bug description:
  Roughly every other time, hibernating (via systemctl hibernate) fails
  : it begins then I get back to lightdm prompt.

  journalctl shows the lines

  systemd[1]: Starting Hibernate...
  systemd-sleep[22333]: Spawned 
/lib/systemd/system-sleep/10_unattended-upgrades-hibernate as 22334.
  systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/hdparm as 22335.
  systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/10_grub-common as 
22336.
  systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/wpasupplicant as 
22337.
  systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/tuxonice as 22338.
  systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/back_to_ram as 22339.
  systemd-sleep[22333]: 
/lib/systemd/system-sleep/10_unattended-upgrades-hibernate succeeded.
  systemd-sleep[22333]: /lib/systemd/system-sleep/back_to_ram succeeded.
  systemd-sleep[22333]: /lib/systemd/system-sleep/hdparm succeeded.
  systemd-sleep[22333]: /lib/systemd/system-sleep/tuxonice succeeded.
  systemd-sleep[22333]: /lib/systemd/system-sleep/10_grub-common succeeded.
  systemd-sleep[22333]: /lib/systemd/system-sleep/wpasupplicant succeeded.
  systemd-sleep[22332]: system-sleep succeeded.
  systemd-sleep[22332]: Suspending system...
  kernel: PM: hibernation entry
  kernel: PM: Syncing filesystems ... 
  kernel: PM: done.
  kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
  kernel: OOM killer disabled.
  kernel: PM: Marking nosave pages: [mem 0x-0x0fff]
  kernel: PM: Marking nosave pages: [mem 0x00058000-0x00058fff]
  kernel: PM: Marking nosave pages: [mem 0x0009e000-0x000f]
  kernel: PM: Marking nosave pages: [mem 0xabbf4000-0xabbf5fff]
  kernel: PM: Marking nosave pages: [mem 0xbb835000-0xbc5fefff]
  kernel: PM: Marking nosave pages: [mem 0xbc60-0x]
  kernel: PM: Basic memory bitmaps created
  kernel: PM: Preallocating image memory... 
  kernel: acpi LNXPOWER:16: Turning OFF
  kernel: acpi LNXPOWER:15: Turning OFF
  kernel: acpi LNXPOWER:14: Turning OFF
  kernel: acpi LNXPOWER:13: Turning OFF
  kernel: acpi LNXPOWER:12: Turning OFF
  kernel: acpi LNXPOWER:11: Turning OFF
  kernel: acpi LNXPOWER:10: Turning OFF
  kernel: acpi LNXPOWER:0f: Turning OFF
  kernel: acpi LNXPOWER:0e: Turning OFF
  kernel: acpi LNXPOWER:0d: Turning OFF
  kernel: acpi LNXPOWER:0c: Turning OFF
  kernel: acpi LNXPOWER:0b: Turning OFF
  kernel: acpi LNXPOWER:0a: Turning OFF
  kernel: acpi LNXPOWER:09: Turning OFF
  kernel: acpi LNXPOWER:08: Turning OFF
  kernel: acpi LNXPOWER:07: Turning OFF
  kernel: acpi LNXPOWER:06: Turning OFF
  kernel: acpi LNXPOWER:05: Turning OFF
  kernel: acpi LNXPOWER:04: Turning OFF
  kernel: acpi LNXPOWER:03: Turning OFF
  kernel: PM: Basic memory bitmaps freed
  kernel: OOM killer enabled.
  kernel: Restarting tasks ... done.
  kernel: video LNXVIDEO:00: Restoring backlight state
  kernel: PM: hibernation exit
  whoopsie[1377]: [00:31:31] Cannot reach: https://daisy.ubuntu.com
  whoopsie[1377]: [00:31:31] Cannot reach: https://daisy.ubuntu.com
  systemd-sleep[22332]: Failed to write 'disk' to /sys/power/state: Cannot 
allocate memory
  acpid[1079]: client 1225[0:0] has disconnected
  systemd[1]: systemd-hibernate.service: Main process exited, code=exited, 
status=1/FAILURE
  acpid[1079]: client connected from 1225[0:0]
  systemd[1]: Failed to start Hibernate.
  acpid[1079]: 1 client rule loaded
  systemd[1]: Dependency failed for Hibernate.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu21.2
  ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun  2 00:34:35 2018
  InstallationDate: Installed on 2016-09-07 (632 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision Tower 3620
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=6ebb7e70-29f5-4ddf-a1a1-8cc58113961a ro nomodeset
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.8.1
  dmi.board.name: 09WH54
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.8.1:bd01/31/2018:svnDellInc.:pnPrec

[Kernel-packages] [Bug 1776158] [NEW] Xenial update to 4.4.135 stable release

[Juerg Haefliger]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree
   or a minimally backported form of that patch. The 4.4.135 upstream
   stable stable patch set is now available. It should be included
   in the Ubuntu kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.135 stable release shall be
   applied:

  * Linux 4.4.135
  * Revert "vti4: Don't override MTU passed on link creation via IFLA_MTU"

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


** Tags: kernel-stable-tracking-bug

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

** Description changed:

- 
  SRU Justification
  
  Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree
-or a minimally backported form of that patch. The 4.4.135 upstream
-stable stable patch set is now available. It should be included
-in the Ubuntu kernel as well.
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree
+    or a minimally backported form of that patch. The 4.4.135 upstream
+    stable stable patch set is now available. It should be included
+    in the Ubuntu kernel as well.
  
-git://git.kernel.org/
+    git://git.kernel.org/
  
  TEST CASE: TBD
  
-The following patches from the 4.4.135 stable release shall be
-applied:
+    The following patches from the 4.4.135 stable release shall be
+    applied:
  
- 
+   * Linux 4.4.135
+   * Revert "vti4: Don't override MTU passed on link creation via IFLA_MTU"

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

Title:
  Xenial update to 4.4.135 stable release

Status in linux package in Ubuntu:
  Invalid

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree
     or a minimally backported form of that patch. The 4.4.135 upstream
     stable stable patch set is now available. It should be included
     in the Ubuntu kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.135 stable release shall be
     applied:

* Linux 4.4.135
* Revert "vti4: Don't override MTU passed on link creation via IFLA_MTU"

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

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

[Kernel-packages] [Bug 1776159] [NEW] mdadm raid soft lock-ups ubuntu kernel 4.13.0-36 Inbox x

[haad]

Public bug reported:

we're running Ubuntu 16.04.4, mdadm - v3.3 and Kernel 4.13.0-36(ubuntu package 
linux-image-generic-hwe-16.04).
We have created raid10 using 22 960GB SSDs [1] . The problem we're
experiencing is that /usr/share/mdadm/checkarray
(executed by cron, included in a mdadm pkg) results in (soft?)
deadlock - load on the node spikes up to 500-700 and all I/O operations
are blocked for a period of time. We can see traces liek these [2] in
our kernel log.

e.g. it ends up in static state like

test@os-node1:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] 
[raid10]
md1 : active raid10 dm-23[9] dm-22[8] dm-21[7] dm-20[6] dm-18[4] dm-19[5] 
dm-17[3]
dm-16[21] dm-15[20] dm-14[2] dm-13[19] dm-12[18] dm-11[17]
dm-10[16] dm-9[15] dm-8[14] dm-7[13] dm-6[12] dm-5[11] 
dm-4[10] dm-3[1] dm-2[0]
  10313171968 blocks super 1.2 512K chunks 2 near-copies [22/22] 
[UU]
  [===>.]  check = 19.0% (1965748032/10313171968) 
finish=1034728.8min speed=134K/sec
  bitmap: 0/39 pages [0KB], 131072KB chunk
unused devices: 

and the only solution is to hard reboot the node. What we found out is that it
doesn't happen on idle raid, we have to generate some significant load
(10 VMs running fio[3] with 500GB HDDs.) to be able to reproduce the issue.

Anyone ever experienced similar issues? Do you have any suggestions how to
better trouble shoot this issue and maybe identify if disks or software layer
is responsible for this behavior

[1] http://www.samsung.com/us/dell/pdfs/PM1633a_Flyer_2016_v4.pdf
[2] https://gist.github.com/haad/09213bab1bc30a00c7d255c0bc60897b
[3] https://github.com/axboe/fio

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1776159

Title:
  mdadm raid soft lock-ups ubuntu kernel 4.13.0-36 Inbox  x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  we're running Ubuntu 16.04.4, mdadm - v3.3 and Kernel 4.13.0-36(ubuntu 
package linux-image-generic-hwe-16.04).
  We have created raid10 using 22 960GB SSDs [1] . The problem we're
  experiencing is that /usr/share/mdadm/checkarray
  (executed by cron, included in a mdadm pkg) results in (soft?)
  deadlock - load on the node spikes up to 500-700 and all I/O operations
  are blocked for a period of time. We can see traces liek these [2] in
  our kernel log.

  e.g. it ends up in static state like

  test@os-node1:~$ cat /proc/mdstat
  Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] 
[raid10]
  md1 : active raid10 dm-23[9] dm-22[8] dm-21[7] dm-20[6] dm-18[4] dm-19[5] 
dm-17[3]
  dm-16[21] dm-15[20] dm-14[2] dm-13[19] dm-12[18] dm-11[17]
  dm-10[16] dm-9[15] dm-8[14] dm-7[13] dm-6[12] dm-5[11] 
dm-4[10] dm-3[1] dm-2[0]
10313171968 blocks super 1.2 512K chunks 2 near-copies [22/22] 
[UU]
[===>.]  check = 19.0% (1965748032/10313171968) 
finish=1034728.8min speed=134K/sec
bitmap: 0/39 pages [0KB], 131072KB chunk
  unused devices: 

  and the only solution is to hard reboot the node. What we found out is that it
  doesn't happen on idle raid, we have to generate some significant load
  (10 VMs running fio[3] with 500GB HDDs.) to be able to reproduce the issue.

  Anyone ever experienced similar issues? Do you have any suggestions how to
  better trouble shoot this issue and maybe identify if disks or software layer
  is responsible for this behavior

  [1] http://www.samsung.com/us/dell/pdfs/PM1633a_Flyer_2016_v4.pdf
  [2] https://gist.github.com/haad/09213bab1bc30a00c7d255c0bc60897b
  [3] https://github.com/axboe/fio

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

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

[Kernel-packages] [Bug 1746299] Update Released

[Łukasz Zemczak]

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

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

Title:
  update makedumpfile tool version to v1.6.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Artful:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  New upstream kernel versions, as those in linux-hwe package, require a newer 
makedumpfile to be supported. Otherwise, all copies fallback to copying the 
entire memory.

  [Test case]
  kdump-tools has been installed, system rebooted, then crash trigerred and 
verified that a small dump file was present on /var/crash/. Tested on amd64 and 
ppc64le.

  [Regression potential]
  Many other bug fixes have been included in the latest version of the package. 
The changes are supposed to fix these bugs, and have been tested as well. 
However, as the total of changes is not trivial, there is impact of regression 
that has been minimized by the tests done. Regression potential of not 
supporting older kernels has been tested with the kernels shipped on xenial and 
artful as well.


  
  

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-30 
10:46:53 ==
  ---Problem Description---
  update makedumpfile to latest version v1.6.3 that officially supports
  up to kernel version 4.14.8. Since makedumpfile is inherently backward 
compatible,
  this would not break existing functionality..

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   makedumpfile reports ""The kernel version is not supported" while generating 
vmcore
  Also, there is a possibility of bogus address translations in makedumpfile 
tool with
  missing upstream patches. Can't be so sure without an exhaustive testing. 
Instead,
  it would be a good idea to go with the version which officially supports the 
kernel
  version in question.

  Userspace tool common name: makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Hari Krishna Bathini  - 2018-01-30 
10:49:13 ==
  With kernel version updated to 4.13.0, please update makedumpfile tool
  version to 1.6.3 which officially supports up to kernel version 4.14.8 [1].

  Thanks
  Hari

  [1]
  http://lists.infradead.org/pipermail/kexec/2018-January/019853.html

  This needs to be tagged for both 16.04.4 & 18.04 releases

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

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

[Kernel-packages] [Bug 1708043] Re: Lenovo X1 Carbon Gen5 fails to resume

[Schemen]

Hi!

I use a Lenovo X1 Carbon 5th Gen. I also have the described suspend
behavior. I was able to "solve" the problem by installing a Mainline
Kernel (v4.17 RC7 -> http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.17-rc7/). With that, suspend and resume works as
intended again.

My BIOS should also be on the latest released version.

>From time to time I run into the problem that my ethernet connection is
not working anymore using the Lenovo USB C dock, wlan is still
functional. This might be a related problem, maybe not.

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

Title:
  Lenovo X1 Carbon Gen5 fails to resume

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Last week it worked fine, this week however if I open the lid for it
  to resume the power light flashes for a bit, then comes on solid, the
  but screen stays blank and the machine is unresponsive. I have to
  power it off / on again in order to use it. It might be related to the
  APST issue with Samsung NVMe SSDs, I'm not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.11.0-10-generic 4.11.0-10.15
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dean   1652 F...m pulseaudio
   /dev/snd/controlC0:  dean   1652 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Aug  1 17:39:20 2017
  HibernationDevice: RESUME=UUID=fb0675d7-391c-4293-a2c5-d283708f1284
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.11.0-10-generic N/A
   linux-backports-modules-4.11.0-10-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-23 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-041300rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1776113] Re: Laptop does not suspend when lid is closed

[Luis Alberto Pabón]

I've been experiencing the same problem since friday on a Dell XPS 9560
laptop on Bionic. I created a different user account to test and laptop
doesn't suspend, but if I switch that user to a Mate Desktop session it
works fine.

These are the relevant lines on my logind.conf file:

~ cat /etc/systemd/logind.conf  |grep -i lid  
HandleLidSwitch=ignore
#HandleLidSwitchDocked=ignore
#LidSwitchIgnoreInhibited=yes

Curiously, I can see this config file was changed last (presumably due
to an update?) just last friday june the 8th, which is perhaps too much
of a coincidence:

/etc/systemd ~ ll 
total 36K
-rw-r--r--  1 root root 1.1K Apr  2 20:25 journald.conf
-rw-r--r--  1 root root 1017 Jun  8 13:33 logind.conf
drwxr-xr-x  2 root root 4.0K Oct  4  2017 network
-rw-r--r--  1 root root  601 Apr 12 12:12 resolved.conf
drwxr-xr-x 21 root root 4.0K Jun 11 08:18 system
-rw-r--r--  1 root root 1.7K Apr  2 20:25 system.conf
-rw-r--r--  1 root root  604 Apr  2 20:25 timesyncd.conf
drwxr-xr-x  3 root root 4.0K May 10 15:52 user
-rw-r--r--  1 root root 1.2K Jul 12  2017 user.conf

This happens on:
  * Ubuntu gnome session
  * Vanilla gnome session
  * Unity 7 session

Suspend on lid closed works correctly on
  * Mate session

I do not mix DE's on the same user, always create a new one to use with
it to avoid home folder pollution.

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

Title:
  Laptop does not suspend when lid is closed

Status in linux-signed package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  In Tweaks > Power, "Suspend when laptop lid is closed" is ON, but my
  laptop does not suspend when the lid is closed.  The laptop is a
  Thinkpad P50.

  When closing the laptop lid, no events show up in dmesg.

  This is my /etc/systemd/login.conf:

  [Login]
  #NAutoVTs=6
  #ReserveVT=6
  #KillUserProcesses=no
  #KillOnlyUsers=
  #KillExcludeUsers=root
  #InhibitDelayMaxSec=5
  #HandlePowerKey=poweroff
  #HandleSuspendKey=suspend
  #HandleHibernateKey=hibernate
  HandleLidSwitch=suspend
  HandleLidSwitchDocked=suspend
  #PowerKeyIgnoreInhibited=no
  #SuspendKeyIgnoreInhibited=no
  #HibernateKeyIgnoreInhibited=no
  #LidSwitchIgnoreInhibited=yes
  #HoldoffTimeoutSec=30s
  #IdleAction=ignore
  #IdleActionSec=30min
  #RuntimeDirectorySize=10%
  #RemoveIPC=yes
  #InhibitorsMax=8192
  #SessionsMax=8192
  #UserTasksMax=33%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 10 14:16:10 2018
  InstallationDate: Installed on 2018-03-26 (76 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-17 (24 days ago)

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

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

[Kernel-packages] [Bug 1751329] Re: kdump-tools won't load until after network is online

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.6.3-2~17.10.1

---
makedumpfile (1:1.6.3-2~17.10.1) artful; urgency=medium

  * Backport latest makedumpfile to artful. (LP: #1746299)

 -- Thadeu Lima de Souza Cascardo   Mon, 21 May
2018 10:56:29 -0300

** Changed in: makedumpfile (Ubuntu Artful)
   Status: Triaged => Fix Released

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

Title:
  kdump-tools won't load until after network is online

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Triaged
Status in makedumpfile source package in Artful:
  Fix Released

Bug description:
  This, at least, causes kdump-tools to load only after some timeout. It
  could be loaded much earlier.

  kdump-tools only requires the network to be online when it's
  configured to dump to ssh or nfs, and only when dumping, not when
  loading.

  We should have three services/units here:

  1) the loading service, does not require network;
  2) the dumping service, that works for local dumps, does not require network;
  3) the dumping service, that works remotely, requires network.

  Now, as per LP#1681909, maybe we should not require network-online,
  but use some other way to verify that the host where we want to dump
  is online, given a certain (configured) timeout.

  Cascardo.

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

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

[Kernel-packages] [Bug 1746299] Re: update makedumpfile tool version to v1.6.3

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.6.3-2~17.10.1

---
makedumpfile (1:1.6.3-2~17.10.1) artful; urgency=medium

  * Backport latest makedumpfile to artful. (LP: #1746299)

 -- Thadeu Lima de Souza Cascardo   Mon, 21 May
2018 10:56:29 -0300

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

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

Title:
  update makedumpfile tool version to v1.6.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Artful:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  New upstream kernel versions, as those in linux-hwe package, require a newer 
makedumpfile to be supported. Otherwise, all copies fallback to copying the 
entire memory.

  [Test case]
  kdump-tools has been installed, system rebooted, then crash trigerred and 
verified that a small dump file was present on /var/crash/. Tested on amd64 and 
ppc64le.

  [Regression potential]
  Many other bug fixes have been included in the latest version of the package. 
The changes are supposed to fix these bugs, and have been tested as well. 
However, as the total of changes is not trivial, there is impact of regression 
that has been minimized by the tests done. Regression potential of not 
supporting older kernels has been tested with the kernels shipped on xenial and 
artful as well.


  
  

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-30 
10:46:53 ==
  ---Problem Description---
  update makedumpfile to latest version v1.6.3 that officially supports
  up to kernel version 4.14.8. Since makedumpfile is inherently backward 
compatible,
  this would not break existing functionality..

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   makedumpfile reports ""The kernel version is not supported" while generating 
vmcore
  Also, there is a possibility of bogus address translations in makedumpfile 
tool with
  missing upstream patches. Can't be so sure without an exhaustive testing. 
Instead,
  it would be a good idea to go with the version which officially supports the 
kernel
  version in question.

  Userspace tool common name: makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Hari Krishna Bathini  - 2018-01-30 
10:49:13 ==
  With kernel version updated to 4.13.0, please update makedumpfile tool
  version to 1.6.3 which officially supports up to kernel version 4.14.8 [1].

  Thanks
  Hari

  [1]
  http://lists.infradead.org/pipermail/kexec/2018-January/019853.html

  This needs to be tagged for both 16.04.4 & 18.04 releases

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

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

[Kernel-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.6.3-2~17.10.1

---
makedumpfile (1:1.6.3-2~17.10.1) artful; urgency=medium

  * Backport latest makedumpfile to artful. (LP: #1746299)

 -- Thadeu Lima de Souza Cascardo   Mon, 21 May
2018 10:56:29 -0300

** Changed in: makedumpfile (Ubuntu Artful)
   Status: Invalid => Fix Released

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.6.3-2~17.10.1

---
makedumpfile (1:1.6.3-2~17.10.1) artful; urgency=medium

  * Backport latest makedumpfile to artful. (LP: #1746299)

 -- Thadeu Lima de Souza Cascardo   Mon, 21 May
2018 10:56:29 -0300

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

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

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Released
Status in makedumpfile source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

  break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
  a0b1280368d1e91ab72f849ef095b4f07a39bbf1

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

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

[Kernel-packages] [Bug 1751329] Re: kdump-tools won't load until after network is online

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.6.3-2~16.04.1

---
makedumpfile (1:1.6.3-2~16.04.1) xenial; urgency=medium

  * Backport latest makedumpfile to xenial. (LP: #1746299)
  * Revert to build-depending on dh-systemd, as xenial does not have
debhelper >= 9.20160709.

 -- Thadeu Lima de Souza Cascardo   Mon, 21 May
2018 11:02:15 -0300

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: Triaged => Fix Released

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

Title:
  kdump-tools won't load until after network is online

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Artful:
  Fix Released

Bug description:
  This, at least, causes kdump-tools to load only after some timeout. It
  could be loaded much earlier.

  kdump-tools only requires the network to be online when it's
  configured to dump to ssh or nfs, and only when dumping, not when
  loading.

  We should have three services/units here:

  1) the loading service, does not require network;
  2) the dumping service, that works for local dumps, does not require network;
  3) the dumping service, that works remotely, requires network.

  Now, as per LP#1681909, maybe we should not require network-online,
  but use some other way to verify that the host where we want to dump
  is online, given a certain (configured) timeout.

  Cascardo.

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

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

[Kernel-packages] [Bug 1750021] Re: fails to dump with latest kpti fixes

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.6.3-2~16.04.1

---
makedumpfile (1:1.6.3-2~16.04.1) xenial; urgency=medium

  * Backport latest makedumpfile to xenial. (LP: #1746299)
  * Revert to build-depending on dh-systemd, as xenial does not have
debhelper >= 9.20160709.

 -- Thadeu Lima de Souza Cascardo   Mon, 21 May
2018 11:02:15 -0300

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

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

Title:
  fails to dump with latest kpti fixes

Status in linux package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in makedumpfile source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  When commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 ("mm/sparsemem:
  Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y") was
  backported, it broke the exporting of mem_section on vmcoreinfo.

  makedumpfile will fail to dump in that case. Backporting a kernel fix
  will make it work again, but that means that some kernel versions
  won't be dumpable. A solution for makedumpfile should be done as well.

  Cascardo.

  break-fix: 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4
  a0b1280368d1e91ab72f849ef095b4f07a39bbf1

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

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

[Kernel-packages] [Bug 1746299] Re: update makedumpfile tool version to v1.6.3

[Launchpad Bug Tracker]

This bug was fixed in the package makedumpfile - 1:1.6.3-2~16.04.1

---
makedumpfile (1:1.6.3-2~16.04.1) xenial; urgency=medium

  * Backport latest makedumpfile to xenial. (LP: #1746299)
  * Revert to build-depending on dh-systemd, as xenial does not have
debhelper >= 9.20160709.

 -- Thadeu Lima de Souza Cascardo   Mon, 21 May
2018 11:02:15 -0300

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

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

Title:
  update makedumpfile tool version to v1.6.3

Status in The Ubuntu-power-systems project:
  In Progress
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Artful:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  New upstream kernel versions, as those in linux-hwe package, require a newer 
makedumpfile to be supported. Otherwise, all copies fallback to copying the 
entire memory.

  [Test case]
  kdump-tools has been installed, system rebooted, then crash trigerred and 
verified that a small dump file was present on /var/crash/. Tested on amd64 and 
ppc64le.

  [Regression potential]
  Many other bug fixes have been included in the latest version of the package. 
The changes are supposed to fix these bugs, and have been tested as well. 
However, as the total of changes is not trivial, there is impact of regression 
that has been minimized by the tests done. Regression potential of not 
supporting older kernels has been tested with the kernels shipped on xenial and 
artful as well.


  
  

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-30 
10:46:53 ==
  ---Problem Description---
  update makedumpfile to latest version v1.6.3 that officially supports
  up to kernel version 4.14.8. Since makedumpfile is inherently backward 
compatible,
  this would not break existing functionality..

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   makedumpfile reports ""The kernel version is not supported" while generating 
vmcore
  Also, there is a possibility of bogus address translations in makedumpfile 
tool with
  missing upstream patches. Can't be so sure without an exhaustive testing. 
Instead,
  it would be a good idea to go with the version which officially supports the 
kernel
  version in question.

  Userspace tool common name: makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Hari Krishna Bathini  - 2018-01-30 
10:49:13 ==
  With kernel version updated to 4.13.0, please update makedumpfile tool
  version to 1.6.3 which officially supports up to kernel version 4.14.8 [1].

  Thanks
  Hari

  [1]
  http://lists.infradead.org/pipermail/kexec/2018-January/019853.html

  This needs to be tagged for both 16.04.4 & 18.04 releases

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

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

[Kernel-packages] [Bug 1776113] Re: Laptop does not suspend when lid is closed

[Luis Alberto Pabón]

All gnome sessions above are on X btw, not Wayland.

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

Title:
  Laptop does not suspend when lid is closed

Status in linux-signed package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  In Tweaks > Power, "Suspend when laptop lid is closed" is ON, but my
  laptop does not suspend when the lid is closed.  The laptop is a
  Thinkpad P50.

  When closing the laptop lid, no events show up in dmesg.

  This is my /etc/systemd/login.conf:

  [Login]
  #NAutoVTs=6
  #ReserveVT=6
  #KillUserProcesses=no
  #KillOnlyUsers=
  #KillExcludeUsers=root
  #InhibitDelayMaxSec=5
  #HandlePowerKey=poweroff
  #HandleSuspendKey=suspend
  #HandleHibernateKey=hibernate
  HandleLidSwitch=suspend
  HandleLidSwitchDocked=suspend
  #PowerKeyIgnoreInhibited=no
  #SuspendKeyIgnoreInhibited=no
  #HibernateKeyIgnoreInhibited=no
  #LidSwitchIgnoreInhibited=yes
  #HoldoffTimeoutSec=30s
  #IdleAction=ignore
  #IdleActionSec=30min
  #RuntimeDirectorySize=10%
  #RemoveIPC=yes
  #InhibitorsMax=8192
  #SessionsMax=8192
  #UserTasksMax=33%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 10 14:16:10 2018
  InstallationDate: Installed on 2018-03-26 (76 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-17 (24 days ago)

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

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

[Kernel-packages] [Bug 1776113] Re: Laptop does not suspend when lid is closed

[Luis Alberto Pabón]

Commenting out the line

 HandleLidSwitch=suspend

restores normal behaviour. Since I didn't change it to begin with, I
gather an update did this judging by how its last modified date was the
same day suspend-on-lidclose stopped working.

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

Title:
  Laptop does not suspend when lid is closed

Status in linux-signed package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  In Tweaks > Power, "Suspend when laptop lid is closed" is ON, but my
  laptop does not suspend when the lid is closed.  The laptop is a
  Thinkpad P50.

  When closing the laptop lid, no events show up in dmesg.

  This is my /etc/systemd/login.conf:

  [Login]
  #NAutoVTs=6
  #ReserveVT=6
  #KillUserProcesses=no
  #KillOnlyUsers=
  #KillExcludeUsers=root
  #InhibitDelayMaxSec=5
  #HandlePowerKey=poweroff
  #HandleSuspendKey=suspend
  #HandleHibernateKey=hibernate
  HandleLidSwitch=suspend
  HandleLidSwitchDocked=suspend
  #PowerKeyIgnoreInhibited=no
  #SuspendKeyIgnoreInhibited=no
  #HibernateKeyIgnoreInhibited=no
  #LidSwitchIgnoreInhibited=yes
  #HoldoffTimeoutSec=30s
  #IdleAction=ignore
  #IdleActionSec=30min
  #RuntimeDirectorySize=10%
  #RemoveIPC=yes
  #InhibitorsMax=8192
  #SessionsMax=8192
  #UserTasksMax=33%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 10 14:16:10 2018
  InstallationDate: Installed on 2018-03-26 (76 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: Upgraded to bionic on 2018-05-17 (24 days ago)

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

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

[Kernel-packages] [Bug 1776177] [NEW] Xenial update to 4.4.136 stable release

[Juerg Haefliger]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree
   or a minimally backported form of that patch. The 4.4.136 upstream
   stable stable patch set is now available. It should be included
   in the Ubuntu kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.136 stable release shall be
   applied:

  * Linux 4.4.136
  * sparc64: Fix build warnings with gcc 7.
  * mm: fix the NULL mapping case in __isolate_lru_page()
  * fix io_destroy()/aio_complete() race
  * Kbuild: change CC_OPTIMIZE_FOR_SIZE definition
  * drm/i915: Disable LVDS on Radiant P845
  * hwtracing: stm: fix build error on some arches
  * stm class: Use vmalloc for the master map
  * scsi: scsi_transport_srp: Fix shost to rport translation
  * MIPS: prctl: Disallow FRE without FR with PR_SET_FP_MODE requests
  * MIPS: ptrace: Fix PTRACE_PEEKUSR requests for 64-bit FGRs
  * iio:kfifo_buf: check for uint overflow
  * dmaengine: usb-dmac: fix endless loop in usb_dmac_chan_terminate_all()
  * i2c: rcar: revoke START request early
  * i2c: rcar: check master irqs before slave irqs
  * i2c: rcar: don't issue stop when HW does it automatically
  * i2c: rcar: init new messages in irq
  * i2c: rcar: refactor setup of a msg
  * i2c: rcar: remove spinlock
  * i2c: rcar: remove unused IOERROR state
  * i2c: rcar: rework hw init
  * i2c: rcar: make sure clocks are on when doing clock calculation
  * tcp: avoid integer overflows in tcp_rcv_space_adjust()
  * irda: fix overly long udelay()
  * ASoC: Intel: sst: remove redundant variable dma_dev_name
  * rtlwifi: rtl8192cu: Remove variable self-assignment in rf.c
  * cfg80211: further limit wiphy names to 64 bytes
  * selinux: KASAN: slab-out-of-bounds in xattr_getsecurity
  * tracing: Fix crash when freeing instances with event triggers
  * Input: elan_i2c_smbus - fix corrupted stack
  * Revert "ima: limit file hash setting by user to fix and log modes"
  * xfs: detect agfl count corruption and reset agfl
  * sh: New gcc support
  * USB: serial: cp210x: use tcflag_t to fix incompatible pointer type
  * powerpc/64s: Clear PCR on boot
  * arm64: lse: Add early clobbers to some input/output asm operands

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


** Tags: kernel-stable-tracking-bug

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

** Description changed:

- 
  SRU Justification
  
  Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree
-or a minimally backported form of that patch. The 4.4.136 upstream
-stable stable patch set is now available. It should be included
-in the Ubuntu kernel as well.
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree
+    or a minimally backported form of that patch. The 4.4.136 upstream
+    stable stable patch set is now available. It should be included
+    in the Ubuntu kernel as well.
  
-git://git.kernel.org/
+    git://git.kernel.org/
  
  TEST CASE: TBD
  
-The following patches from the 4.4.136 stable release shall be
-applied:
+    The following patches from the 4.4.136 stable release shall be
+    applied:
  
- 
+   * Linux 4.4.136
+   * sparc64: Fix build warnings with gcc 7.
+   * mm: fix the NULL mapping case in __isolate_lru_page()
+   * fix io_destroy()/aio_complete() race
+   * Kbuild: change CC_OPTIMIZE_FOR_SIZE definition
+   * drm/i915: Disable LVDS on Radiant P845
+   * hwtracing: stm: fix build error on some arches
+   * stm class: Use vmalloc for the master map
+   * scsi: scsi_transport_srp: Fix shost to rport translation
+   * MIPS: prctl: Disallow FRE without FR with PR_SET_FP_MODE requests
+   * MIPS: ptrace: Fix PTRACE_PEEKUSR requests for 64-bit FGRs
+   * iio:kfifo_buf: check for uint overflow
+   * dmaengine: usb-dmac: fix endless loop in usb_dmac_chan_terminate_all()
+   * i2c: rcar: revoke START request early
+   * i2c: rcar: check master irqs before slave irqs
+   * i2c: rcar: don't issue stop when HW does it automatically
+   * i2c: rcar: init new messages in irq
+   * i2c: rcar: refactor setup of a msg
+   * i2c: rcar: remove spinlock
+   * i2c: rcar: remove unused IOERROR state
+   * i2c: rcar: rework hw init
+   * i2c: rcar: make sure clocks are on when doing clock calculation
+   * tcp: avoid integer overflows in tcp_rcv_space_adjust()
+   * ir

[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

[Louis Bouchard]

Hello,
For information, the current presence of kexec-tools in -proposed causes a 
dependency problem when installing the linux-crashdump meta-package :

# apt update
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu xenial-security InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
11 packages can be upgraded. Run 'apt list --upgradable' to see them.
# apt install linux-crashdump
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-crashdump : Depends: kdump-tools but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

When adding the -proposed archive, linux-crashdump installs correctly.

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

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  In Progress
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Latest kexec-tools is needed to load/kexec recent kernels. For older 
releases, like xenial, it's needed to support linux-hwe kernels.

  [Regression Potential]
  It might fail to load the GA kernels, like a 4.4 kernel on xenial.

  [Test case]
  Different kernels on different architectures have been tested.

  
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the
  crash kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

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

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048
  [   85.731745] NUMA
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd 
ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bn

[Kernel-packages] [Bug 1776076] [NEW] package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Kille

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

virtualbox installation getting stuck

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: virtualbox-dkms 5.2.10-dfsg-6
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun Jun 10 19:11:06 2018
ErrorMessage: installed virtualbox-dkms package post-installation script 
subprocess was killed by signal (Killed)
InstallationDate: Installed on 2018-06-10 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
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: virtualbox
Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: 
installed virtualbox-dkms package post-installation script subprocess was 
killed by signal (Killed)
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic
-- 
package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed 
virtualbox-dkms package post-installation script subprocess was killed by 
signal (Killed)
https://bugs.launchpad.net/bugs/1776076
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to dkms in Ubuntu.

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

[Kernel-packages] [Bug 1776076] Re: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)

[LocutusOfBorg]

hello cyphermox, do you have any clue about what might be wrong with
DKMS now?

** Package changed: virtualbox (Ubuntu) => dkms (Ubuntu)

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

Title:
  package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade:
  installed virtualbox-dkms package post-installation script subprocess
  was killed by signal (Killed)

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  virtualbox installation getting stuck

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: virtualbox-dkms 5.2.10-dfsg-6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jun 10 19:11:06 2018
  ErrorMessage: installed virtualbox-dkms package post-installation script 
subprocess was killed by signal (Killed)
  InstallationDate: Installed on 2018-06-10 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  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: virtualbox
  Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: 
installed virtualbox-dkms package post-installation script subprocess was 
killed by signal (Killed)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1775672] [NEW] virtualbox-dkms installation hangs in 18.04 (with secure boot)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

apt install virtualbox hangs during virtualbox-dkms installation:

# apt install virtualbox
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  dkms libgsoap-2.8.60 libqt5opengl5 libqt5printsupport5 libvncserver1
  virtualbox-dkms virtualbox-qt
Suggested packages:
  menu vde2 virtualbox-guest-additions-iso
The following NEW packages will be installed:
  dkms libgsoap-2.8.60 libqt5opengl5 libqt5printsupport5 libvncserver1
  virtualbox virtualbox-dkms virtualbox-qt
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/27.0 MB of archives.
After this operation, 117 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package dkms.
(Reading database ... 185903 files and directories currently installed.)
Preparing to unpack .../0-dkms_2.3-3ubuntu9.1_all.deb ...
Unpacking dkms (2.3-3ubuntu9.1) ...
Selecting previously unselected package libgsoap-2.8.60:amd64.
Preparing to unpack .../1-libgsoap-2.8.60_2.8.60-2build1_amd64.deb ...
Unpacking libgsoap-2.8.60:amd64 (2.8.60-2build1) ...
Selecting previously unselected package libqt5opengl5:amd64.
Preparing to unpack .../2-libqt5opengl5_5.9.5+dfsg-0ubuntu1_amd64.deb ...
Unpacking libqt5opengl5:amd64 (5.9.5+dfsg-0ubuntu1) ...
Selecting previously unselected package libqt5printsupport5:amd64.
Preparing to unpack .../3-libqt5printsupport5_5.9.5+dfsg-0ubuntu1_amd64.deb ...
Unpacking libqt5printsupport5:amd64 (5.9.5+dfsg-0ubuntu1) ...
Selecting previously unselected package libvncserver1:amd64.
Preparing to unpack .../4-libvncserver1_0.9.11+dfsg-1ubuntu1_amd64.deb ...
Unpacking libvncserver1:amd64 (0.9.11+dfsg-1ubuntu1) ...
Selecting previously unselected package virtualbox-dkms.
Preparing to unpack .../5-virtualbox-dkms_5.2.10-dfsg-6_all.deb ...
Unpacking virtualbox-dkms (5.2.10-dfsg-6) ...
Selecting previously unselected package virtualbox.
Preparing to unpack .../6-virtualbox_5.2.10-dfsg-6_amd64.deb ...
Unpacking virtualbox (5.2.10-dfsg-6) ...
Selecting previously unselected package virtualbox-qt.
Preparing to unpack .../7-virtualbox-qt_5.2.10-dfsg-6_amd64.deb ...
Unpacking virtualbox-qt (5.2.10-dfsg-6) ...
Setting up libvncserver1:amd64 (0.9.11+dfsg-1ubuntu1) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
Setting up libqt5printsupport5:amd64 (5.9.5+dfsg-0ubuntu1) ...
Setting up libqt5opengl5:amd64 (5.9.5+dfsg-0ubuntu1) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Setting up libgsoap-2.8.60:amd64 (2.8.60-2build1) ...
Setting up dkms (2.3-3ubuntu9.1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for shared-mime-info (1.9-2) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Setting up virtualbox-dkms (5.2.10-dfsg-6) ...
Loading new virtualbox-5.2.10 DKMS files...
Building for 4.15.0-22-generic
Progress: [ 85%] [#.] 


$ dpkg -l | grep virtualbox
ii  unity-scope-virtualbox 0.1+13.10.20130723-0ubuntu1  
  all  VirtualBox scope for Unity
iU  virtualbox 5.2.10-dfsg-6
  amd64x86 virtualization solution - base binaries
iF  virtualbox-dkms5.2.10-dfsg-6
  all  x86 virtualization solution - kernel module sources for 
dkms
iU  virtualbox-qt  5.2.10-dfsg-6
  amd64x86 virtualization solution - Qt based user interface
$ 


$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
$

$ apt-cache policy virtualbox-dkms 
virtualbox-dkms:
  Installed: 5.2.10-dfsg-6
  Candidate: 5.2.10-dfsg-6
  Version table:
 *** 5.2.10-dfsg-6 500
500 http://us.archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu bionic/multiverse i386 Packages
100 /var/lib/dpkg/status
$ apt-cache policy dkms 
dkms:
  Installed: 2.3-3ubuntu9.1
  Candidate: 2.3-3ubuntu9.1
  Version table:
 *** 2.3-3ubuntu9.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
100 /var/lib/dpkg/status
 2.3-3ubuntu9 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages
$ 

What I expected to happen:  successfully install the packag

[Kernel-packages] [Bug 1775875] Re: Ubuntu 18.04 Lenovo X1 Carbon 5th fails to suspend after detaching dock station (NULL pointer dereference)

[Kai-Heng Feng]

I guess this is a dupe of LP: #1768852.

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

Title:
  Ubuntu 18.04 Lenovo X1 Carbon 5th fails to suspend after detaching
  dock station (NULL pointer dereference)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  uname -r
  4.15.0-22-generic

  How to reproduce:
  1) connect dock station
  2) disconnect dock station
  3) type: systemctl suspend

  Result: system doesn't respond. Only Alt + Print Screen + SUB works.

  There is a workaround for this issue - disable USB for thunderbolt 3
  in BIOS. But this is slightly an overkill.

  Error from kern.log:

  Jun  4 12:09:33 ya-x1 kernel: [  375.060038] pcieport :0a:03.0: Refused 
to change power state, currently in D3
  Jun  4 12:09:33 ya-x1 kernel: [  375.061527] xhci_hcd :0d:00.0: remove, 
state 1
  Jun  4 12:09:33 ya-x1 kernel: [  375.061532] usb usb6: USB disconnect, device 
number 1
  Jun  4 12:09:33 ya-x1 kernel: [  375.061533] usb 6-1: USB disconnect, device 
number 2
  Jun  4 12:09:33 ya-x1 kernel: [  375.061572] xhci_hcd :0d:00.0: xHCI host 
controller not responding, assume dead
  Jun  4 12:09:33 ya-x1 kernel: [  375.061578] r8152 6-1:1.0 enx0050b68eac7d: 
Stop submitting intr, status -108
  Jun  4 12:09:33 ya-x1 kernel: [  375.116210] xhci_hcd :0d:00.0: USB bus 6 
deregistered
  Jun  4 12:09:33 ya-x1 kernel: [  375.116217] xhci_hcd :0d:00.0: remove, 
state 1
  Jun  4 12:09:33 ya-x1 kernel: [  375.116220] usb usb5: USB disconnect, device 
number 1
  Jun  4 12:09:33 ya-x1 kernel: [  375.116222] usb 5-3: USB disconnect, device 
number 3
  Jun  4 12:09:33 ya-x1 kernel: [  375.117197] xhci_hcd :0d:00.0: Host halt 
failed, -19
  Jun  4 12:09:33 ya-x1 kernel: [  375.117199] xhci_hcd :0d:00.0: Host not 
accessible, reset failed.
  Jun  4 12:09:33 ya-x1 kernel: [  375.117307] xhci_hcd :0d:00.0: USB bus 5 
deregistered
  Jun  4 12:09:33 ya-x1 kernel: [  375.147887] pcieport :0a:02.0: Refused 
to change power state, currently in D3
  Jun  4 12:09:33 ya-x1 kernel: [  375.149415] pcieport :0a:01.0: Refused 
to change power state, currently in D3
  Jun  4 12:09:33 ya-x1 kernel: [  375.150959] xhci_hcd :0b:00.0: remove, 
state 4
  Jun  4 12:09:33 ya-x1 kernel: [  375.150965] usb usb4: USB disconnect, device 
number 1
  Jun  4 12:09:33 ya-x1 kernel: [  375.151217] xhci_hcd :0b:00.0: USB bus 4 
deregistered
  Jun  4 12:09:33 ya-x1 kernel: [  375.151223] xhci_hcd :0b:00.0: xHCI host 
controller not responding, assume dead
  Jun  4 12:09:33 ya-x1 kernel: [  375.151230] xhci_hcd :0b:00.0: remove, 
state 1
  Jun  4 12:09:33 ya-x1 kernel: [  375.151233] usb usb3: USB disconnect, device 
number 1
  Jun  4 12:09:33 ya-x1 kernel: [  375.151234] usb 3-1: USB disconnect, device 
number 2
  Jun  4 12:09:33 ya-x1 kernel: [  375.192843] usb 3-4: USB disconnect, device 
number 3
  Jun  4 12:09:33 ya-x1 kernel: [  375.194286] BUG: unable to handle kernel 
NULL pointer dereference at 0034
  Jun  4 12:09:33 ya-x1 kernel: [  375.194294] IP: 
tty_unregister_driver+0xd/0x70
  Jun  4 12:09:33 ya-x1 kernel: [  375.194295] PGD 0 P4D 0 
  Jun  4 12:09:33 ya-x1 kernel: [  375.194298] Oops:  [#1] SMP PTI
  Jun  4 12:09:33 ya-x1 kernel: [  375.194300] Modules linked in: cdc_ether 
usbnet r8152 mii hid_generic snd_usb_audio usbhid snd_usbmidi_lib ccm 
thunderbolt bnep snd_hda_codec_hdmi snd_hda_codec_conexant 
snd_hda_codec_generic nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp arc4 kvm_intel snd_soc_skl kvm snd_soc_skl_ipc 
snd_hda_ext_core snd_soc_sst_dsp irqbypass snd_soc_sst_ipc crct10dif_pclmul 
snd_soc_acpi crc32_pclmul snd_soc_core ghash_clmulni_intel snd_compress 
ac97_bus pcbc snd_pcm_dmaengine snd_seq_midi snd_hda_intel snd_hda_codec 
snd_seq_midi_event snd_hda_core snd_hwdep aesni_intel uvcvideo snd_rawmidi 
aes_x86_64 input_leds crypto_simd glue_helper snd_pcm videobuf2_vmalloc cryptd 
intel_cstate intel_rapl_perf videobuf2_memops iwlmvm videobuf2_v4l2 joydev 
mac80211 serio_raw btusb videobuf2_core snd_seq
  Jun  4 12:09:33 ya-x1 kernel: [  375.194335]  thinkpad_acpi btrtl btbcm 
intel_wmi_thunderbolt wmi_bmof btintel nvram iwlwifi rtsx_pci_ms videodev 
bluetooth snd_seq_device snd_timer media cfg80211 memstick snd ecdh_generic 
mei_me mei intel_pch_thermal ucsi_acpi shpchp typec_ucsi typec soundcore 
mac_hid acpi_pad tpm_crb sch_fq_codel parport_pc ppdev lp parport ip_tables 
x_tables autofs4 rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops e1000e psmouse ptp nvme pps_core nvme_core 
drm rtsx_pci wmi i2c_hid video hid
  Jun  4 12:09:33 ya-x1 kernel: [  375.194366] CPU: 0 PID: 4588 Comm: 
kworker/u8:3 Not 

[Kernel-packages] [Bug 1775672] Re: virtualbox-dkms installation hangs in 18.04 (with secure boot)

[LocutusOfBorg]

** Package changed: virtualbox (Ubuntu) => dkms (Ubuntu)

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

Title:
  virtualbox-dkms installation hangs in 18.04 (with secure boot)

Status in dkms package in Ubuntu:
  New

Bug description:
  apt install virtualbox hangs during virtualbox-dkms installation:

  # apt install virtualbox
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
dkms libgsoap-2.8.60 libqt5opengl5 libqt5printsupport5 libvncserver1
virtualbox-dkms virtualbox-qt
  Suggested packages:
menu vde2 virtualbox-guest-additions-iso
  The following NEW packages will be installed:
dkms libgsoap-2.8.60 libqt5opengl5 libqt5printsupport5 libvncserver1
virtualbox virtualbox-dkms virtualbox-qt
  0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/27.0 MB of archives.
  After this operation, 117 MB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Selecting previously unselected package dkms.
  (Reading database ... 185903 files and directories currently installed.)
  Preparing to unpack .../0-dkms_2.3-3ubuntu9.1_all.deb ...
  Unpacking dkms (2.3-3ubuntu9.1) ...
  Selecting previously unselected package libgsoap-2.8.60:amd64.
  Preparing to unpack .../1-libgsoap-2.8.60_2.8.60-2build1_amd64.deb ...
  Unpacking libgsoap-2.8.60:amd64 (2.8.60-2build1) ...
  Selecting previously unselected package libqt5opengl5:amd64.
  Preparing to unpack .../2-libqt5opengl5_5.9.5+dfsg-0ubuntu1_amd64.deb ...
  Unpacking libqt5opengl5:amd64 (5.9.5+dfsg-0ubuntu1) ...
  Selecting previously unselected package libqt5printsupport5:amd64.
  Preparing to unpack .../3-libqt5printsupport5_5.9.5+dfsg-0ubuntu1_amd64.deb 
...
  Unpacking libqt5printsupport5:amd64 (5.9.5+dfsg-0ubuntu1) ...
  Selecting previously unselected package libvncserver1:amd64.
  Preparing to unpack .../4-libvncserver1_0.9.11+dfsg-1ubuntu1_amd64.deb ...
  Unpacking libvncserver1:amd64 (0.9.11+dfsg-1ubuntu1) ...
  Selecting previously unselected package virtualbox-dkms.
  Preparing to unpack .../5-virtualbox-dkms_5.2.10-dfsg-6_all.deb ...
  Unpacking virtualbox-dkms (5.2.10-dfsg-6) ...
  Selecting previously unselected package virtualbox.
  Preparing to unpack .../6-virtualbox_5.2.10-dfsg-6_amd64.deb ...
  Unpacking virtualbox (5.2.10-dfsg-6) ...
  Selecting previously unselected package virtualbox-qt.
  Preparing to unpack .../7-virtualbox-qt_5.2.10-dfsg-6_amd64.deb ...
  Unpacking virtualbox-qt (5.2.10-dfsg-6) ...
  Setting up libvncserver1:amd64 (0.9.11+dfsg-1ubuntu1) ...
  Processing triggers for mime-support (3.60ubuntu1) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
  Setting up libqt5printsupport5:amd64 (5.9.5+dfsg-0ubuntu1) ...
  Setting up libqt5opengl5:amd64 (5.9.5+dfsg-0ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Setting up libgsoap-2.8.60:amd64 (2.8.60-2build1) ...
  Setting up dkms (2.3-3ubuntu9.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for man-db (2.8.3-2) ...
  Processing triggers for shared-mime-info (1.9-2) ...
  Processing triggers for gnome-menus (3.13.3-11ubuntu1) ...
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Setting up virtualbox-dkms (5.2.10-dfsg-6) ...
  Loading new virtualbox-5.2.10 DKMS files...
  Building for 4.15.0-22-generic
  Progress: [ 85%] [#.] 

  
  $ dpkg -l | grep virtualbox
  ii  unity-scope-virtualbox 0.1+13.10.20130723-0ubuntu1
all  VirtualBox scope for Unity
  iU  virtualbox 5.2.10-dfsg-6  
amd64x86 virtualization solution - base binaries
  iF  virtualbox-dkms5.2.10-dfsg-6  
all  x86 virtualization solution - kernel module sources 
for dkms
  iU  virtualbox-qt  5.2.10-dfsg-6  
amd64x86 virtualization solution - Qt based user interface
  $ 

  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $

  $ apt-cache policy virtualbox-dkms 
  virtualbox-dkms:
Installed: 5.2.10-dfsg-6
Candidate: 5.2.10-dfsg-6
Version table:
   *** 5.2.10-dfsg-6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/multiverse amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/multiverse i386 
Packages
  100 /var/lib/dpkg/status
  $ apt-cache policy dkms 
  dkms:
Installed: 2.3-3ubuntu9.1
Candidate: 2.3-3ub

[Kernel-packages] [Bug 1772760] Re: Touchpad slows down and then stops working

[Kai-Heng Feng]

https://wiki.ubuntu.com/Kernel/KernelBootParameters

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

Title:
  Touchpad slows down and then stops working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Cannot find a reason, but sometimes once a day, sometimes twice a day,
  my touchpad starts to work slowly, like jumping, and after a few
  seconds, it completely stops working. At some point, I did something
  with Terminal and it started working, but cannot reproduce it. The
  only thing that seems to be really working is to Suspend laptop and
  come back in Ubuntu (or restart, but that means to close everything +
  it takes more time). While I wrote this text, it seems to have
  recovered by itself, it is working right now, but this is unreliable
  and cannot be used in production (what about stopping it during a
  presentation, cannot suspend in a meeting). Hopefully, it is some
  kernel problem, as I reported kernel package.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May 23 01:15:44 2018
  InstallationDate: Installed on 2018-04-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   florin 2029 F...m pulseaudio
   /dev/snd/controlC0:  florin 2029 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99eb1e80-1ec0-4526-8cff-0691084ec0f8
  InstallationDate: Installed on 2018-04-27 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=470c0ce8-f352-4f58-977c-af6d3998d302 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1776177] Re: Xenial update to 4.4.136 stable release

[Juerg Haefliger]

List of previously applied patches:
  * Revert "ima: limit file hash setting by user to fix and log modes"

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

Title:
  Xenial update to 4.4.136 stable release

Status in linux package in Ubuntu:
  Invalid

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree
     or a minimally backported form of that patch. The 4.4.136 upstream
     stable stable patch set is now available. It should be included
     in the Ubuntu kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.136 stable release shall be
     applied:

* Linux 4.4.136
* sparc64: Fix build warnings with gcc 7.
* mm: fix the NULL mapping case in __isolate_lru_page()
* fix io_destroy()/aio_complete() race
* Kbuild: change CC_OPTIMIZE_FOR_SIZE definition
* drm/i915: Disable LVDS on Radiant P845
* hwtracing: stm: fix build error on some arches
* stm class: Use vmalloc for the master map
* scsi: scsi_transport_srp: Fix shost to rport translation
* MIPS: prctl: Disallow FRE without FR with PR_SET_FP_MODE requests
* MIPS: ptrace: Fix PTRACE_PEEKUSR requests for 64-bit FGRs
* iio:kfifo_buf: check for uint overflow
* dmaengine: usb-dmac: fix endless loop in usb_dmac_chan_terminate_all()
* i2c: rcar: revoke START request early
* i2c: rcar: check master irqs before slave irqs
* i2c: rcar: don't issue stop when HW does it automatically
* i2c: rcar: init new messages in irq
* i2c: rcar: refactor setup of a msg
* i2c: rcar: remove spinlock
* i2c: rcar: remove unused IOERROR state
* i2c: rcar: rework hw init
* i2c: rcar: make sure clocks are on when doing clock calculation
* tcp: avoid integer overflows in tcp_rcv_space_adjust()
* irda: fix overly long udelay()
* ASoC: Intel: sst: remove redundant variable dma_dev_name
* rtlwifi: rtl8192cu: Remove variable self-assignment in rf.c
* cfg80211: further limit wiphy names to 64 bytes
* selinux: KASAN: slab-out-of-bounds in xattr_getsecurity
* tracing: Fix crash when freeing instances with event triggers
* Input: elan_i2c_smbus - fix corrupted stack
* Revert "ima: limit file hash setting by user to fix and log modes"
* xfs: detect agfl count corruption and reset agfl
* sh: New gcc support
* USB: serial: cp210x: use tcflag_t to fix incompatible pointer type
* powerpc/64s: Clear PCR on boot
* arm64: lse: Add early clobbers to some input/output asm operands

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

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

[Kernel-packages] [Bug 1768849] Re: Battery power depleting rapidly

[Bug Watch Updater]

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=199605.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-05-03T13:46:05+00:00 jebeld17 wrote:

Created attachment 275743
Export from Sysinfo GUI app

Percentage battery power left depletes rapidly with regular use of the PC.
This issue does not occur on such a scale in Windows, leaving me to believe 
this is an issue with something in Linux using too many resources.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May 3 09:34:17 2018
InstallationDate: Installed on 2018-05-01 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768849/comments/4


On 2018-05-03T13:48:48+00:00 jebeld17 wrote:

Dependencies.txt:
https://bugs.launchpad.net/linux/+bug/1768849/+attachment/5132985/+files/Dependencies.txt

ProcCpuInfoMinimal.txt:
https://bugs.launchpad.net/linux/+bug/1768849/+attachment/5132986/+files/ProcCpuinfoMinimal.txt

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768849/comments/5


On 2018-05-08T03:30:28+00:00 rui.zhang wrote:

what is the model name of your laptop?
please confirm if this is a duplicate of bug #198665, by confirming the test 
results for comment #40.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768849/comments/8


On 2018-05-08T17:42:53+00:00 jebeld17 wrote:

See Sysinfo export.
I'm trying to find the exact model number now...

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768849/comments/9


On 2018-05-08T17:46:15+00:00 jebeld17 wrote:

Model: Inspiron 13 5xxx series, i5368-6453GRY.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768849/comments/10


On 2018-05-09T20:12:18+00:00 jebeld17 wrote:

(In reply to Zhang Rui from comment #2)
> what is the model name of your laptop?
> please confirm if this is a duplicate of bug #198665, by confirming the test
> results for comment #40.

This issue is not occurring when my computer is off, so it cannot be a
duplicate of bug #198665.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768849/comments/12


On 2018-05-22T16:01:46+00:00 yu.c.chen wrote:

Could you please use powertop to track which components are the offenders?
And also please provide the turbostat/top/perf record to check the activity of 
the system?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768849/comments/13


On 2018-05-30T05:05:39+00:00 yu.c.chen wrote:

ping

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768849/comments/14


On 2018-06-11T02:38:14+00:00 yu.c.chen wrote:

Closed due to insufficient data within 3 weeks, please feel free to
reopen if you can help provide the powertop result for further
debugging.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768849/comments/15


** Changed in: linux
   Status: Unknown => Invalid

** Changed in: linux
   Importance: Unknown => High

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

Title:
  Battery power depleting rapidly

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Percentage battery power left depletes rapidly with regular use of the PC, 
when the computer is on.
  This issue does not occur on such a scale in Windows, leaving me to believe 
this is an issue with something in Linux using too many resources.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-gene

[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions

[Nivedita Singhvi]

I would have thought this would be the relevant patch:

bonding: speed/duplex update at NETDEV_UP event
 Mahesh Bandewar authored and davem330 committed on Sep 28, 2017
1 parent b5c7d4e commit 4d2c0cda07448ea6980f00102dc3964eb25e241c 

However, it was first available in v4.15-rc1.

At least as far as bonding kernel changes go, there does not
seem another obvious candidate that might have fixed this problem
between 4.12 and 4.13 (first skim).

At least for one scenario I looked at, we got a bad speed/duplex
setting, which eventually ended up with the bond interface 
aggregating on a separate port, and/or ending up in LACP DISABLED
state which it never got out of. We only checked correct/latest
device speed/duplex settings via the NETDEV_CHANGE path, where
we called _ethtool_get_settings(). If we don't receive a change
event again to correct the speed/duplex, we never recover.

There are some other patches which help address this at different
points, but are either before or later (see above) the window.

I'll take a look at code outside the bonding dir which might
impact this. 

Joseph, could you provide the raw config files you used as well?
It was not super clear in the png image if those were the only
diffs. They did not seem very relevant diffs either.

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

Title:
  [i40e] LACP bonding start up race conditions

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

Bug description:
  When provisioning Ubuntu servers with MAAS at once, some bonding pairs
  will have unexpected LACP status such as "Expired". It randomly
  happens at each provisioning with the default xenial kernel(4.4), but
  not reproducible with HWE kernel(4.13). I'm using Intel X710 cards
  (Dell-branded).

  Using the HWE kernel works as a workaround for short term, but it's
  not ideal since 4.13 is not covered by Canonical Livepatch service.

  How to reproduce:
  1. configure LACP bonding with MAAS
  2. provision machines
  3. check the bonding status in /proc/net/bonding/bond*

  frequency of occurrence:
  About 5 bond pairs in 22 pairs at each provisioning.

  [reproducible combination]
  $ uname -a
  Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 1.4.25-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  [non-reproducible combination]
  $ uname -a
  Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo ethtool -i eno1
  driver: i40e
  version: 2.1.14-k
  firmware-version: 6.00 0x800034e6 18.3.6
  expansion-rom-version: 
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-116-generic 4.4.0-116.140
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  6 06:37 seq
   crw-rw 1 root audio 116, 33 Mar  6 06:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Mar  6 06:46:32 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R730
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 
console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-116-generic N/A
   linux-backports-modules-4.4.0-116-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/16/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.5
  dmi.board.name: 072T6D
  dmi.

[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

[Łukasz Zemczak]

I have stopped the phasing of makedumpfile in xenial-updates until this
package gets released as well. Please perform validation of this bug in
-proposed as soon as possible so that both packages can be released.

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

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  In Progress
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Latest kexec-tools is needed to load/kexec recent kernels. For older 
releases, like xenial, it's needed to support linux-hwe kernels.

  [Regression Potential]
  It might fail to load the GA kernels, like a 4.4 kernel on xenial.

  [Test case]
  Different kernels on different architectures have been tested.

  
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the
  crash kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

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

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048
  [   85.731745] NUMA
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd 
ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast 
i2c_algo_bit ttm drm_kms_helper mdio libcrc32c crc32c_vpmsum mlx5_core 
syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci mlxfw libahci nvme 
devlink nvme_core
  [   85.732704] CPU: 10 PID: 4316 Comm: bash Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   85.732764] task: c03fcb141700 task.stack: c03fc2374000
  [   85.732858] NIP: c078f588 LR: c07904b8 CTR: 
c078f560
  [   85.732977] REGS: c03fc23779f0 TRAP: 0300   Not tainted  
(4.13.0-17-generic)
  [   85.733066] MSR: 90009033 
  [   85.733075]   CR: 2842  XER: 2004
  [   85.733201] CFAR: c07904b4 DAR:  DSISR: 4200 
SOFTE: 1
  [   85.733201] GPR00: c07904b8 c03fc2377c70 c15f6000 
0063
  [   85.733201] GPR04: c03feedfade8 c03feee12068 90009033 
000a
  [   85.733201] GPR08: 0007 0001  
90001003
  [   85.

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[anuj]

I'm using kernel version 4.9.73
4.9.73 #0 SMP PREEMPT Wed May 30 13:39:24 2018 aarch64 GNU/Linux
The problem reproduces for me as soon as I do ftp(vsftpd 3.0.3 server on DUT) 
to the DUT. After that it just hangs and keeps giving the msg every 10 secs 
waiting for lo to become free. Usage count=1.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1753510] Re: Cannot boot/install AMD Ryzen 2400G

[Peter Silva]

yes:  4 Cores/8 Processing Threads,  I tried 0-7 and 0-3.  0-7 crashes
worse than 0-3.  I could imagine the number being related to cores,
rather than threads.

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

Title:
  Cannot boot/install AMD Ryzen 2400G

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Did a motherboard swap on a trusty old computer that ran ubuntu for 10 years 
or so. Now it only runs windows (same hardware fresh installs windows with no 
issue). brand new ryzen 2nd gen with graphics.
   
  I know about graphics drivers issues, wasn't expecting that to be dealt with.
  Just trying to use it as a cpu. So I put in an older (RADEON HD 7850 
pitcairn) video card to get some functionality.

  Without the video card, it boots, but the display is unusable. I can
  ssh in and see that it works fine as a server, but cannot use terminal
  or graphical display.

  With the video card, Put daily ubuntu Bionic image, and "Try Ubuntu",
  and it goes into an infinite loop. photo attached.  I tried 16.04.4 and
  I think it just went into a blank screen.

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

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

[Kernel-packages] [Bug 1776211] [NEW] kdump fails to take dump with smt set to 2, hmc dumpstart

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

--Problem Description---
kdump fails to take dump with smt set to 2, hmc dumpstart

---Issue observed---
[0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
[0.004118] SMP NR_CPUS=2048 
[0.004120] NUMA 
[0.004125] pSeries
[0.004132] Modules linked in:
[0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic 
#13-Ubuntu
[0.004153] task: c00046715900 task.stack: c00046134000
[0.004162] NIP: c0006468 LR: c801764c CTR: 006cdc70
[0.004173] REGS: c00047fe3ce0 TRAP: 0700   Not tainted  
(4.13.0-12-generic)
[0.004181] MSR: 80081031 
[0.004193]   CR: 8804  XER: 2003
[0.004204] CFAR: c0006454 SOFTE: 0 
[0.004204] GPR00: c801764c c00047fe3f60 c95e3000 
 
[0.004204] GPR04: 0001 0002  
ffdf 
[0.004204] GPR08:  2804 0002 
0002 
[0.004204] GPR12:  cfff c00046137f90 
0b5452d8 
[0.004204] GPR16: fffd 089ffd10 0136 
0b55d378 
[0.004204] GPR20: 0060 1eca 0a6c 
0007 
[0.004204] GPR24:   c9621ed0 
 
[0.004204] GPR28:  c00046134000 c00046137c80 
c9105df8 
[0.004328] NIP [c0006468] 0xc0006468
[0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
[0.004345] Call Trace:
[0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0 
(unreliable)
[0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
[0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
[0.004393] [c00046137c10] [c8008ac4] 
hardware_interrupt_common+0x114/0x120
[0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
[0.004409] LR = arch_local_irq_restore+0x40/0x90
[0.004423] [c00046137f00] [0005] 0x5 (unreliable)
[0.004436] [c00046137f20] [c8049824] start_secondary+0x324/0x350
[0.004450] [c00046137f90] [c800aa6c] 
start_secondary_prolog+0x10/0x14
[0.004460] Instruction dump:
[0.004467]        
 
[0.004484]        
 
[0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
[0.004512] 
[0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
[0.004525] SMP NR_CPUS=2048 
[0.004526] NUMA 
[0.004532] pSeries
[0.004540] Modules linked in:
[0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G  D 
4.13.0-12-generic #13-Ubuntu
[0.004561] task: c9579f00 task.stack: c95dc000
[0.004569] NIP: c0006460 LR: c80b6e80 CTR: 
[0.004580] REGS: c95dfb20 TRAP: 0700   Tainted: G  D  
(4.13.0-12-generic)
[0.004589] MSR: 80081031 
[0.004599]   CR: 22002228  XER: 2004
[0.004611] CFAR: c000493c SOFTE: 0 
[0.004611] GPR00:  c95dfda0 c95e3000 
 
[0.004611] GPR04:    
 
[0.004611] GPR08:  22002228 7fff 
0008 
[0.004611] GPR12:  cfff0a80 c00c7e137f90 
09980600 
[0.004611] GPR16: 1ec7 0001  
 
[0.004611] GPR20:    
0007 
[0.004611] GPR24: 0008 c800 0800 
 
[0.004611] GPR28:  0008 c9621ed0 
c9622354 
[0.004729] NIP [c0006460] 0xc0006460
[0.004739] LR [c80b6e80] pseries_lpar_idle+0x30/0x50
[0.004746] Call Trace:
[0.004756] [c95dfda0] [c95dfe90] 
init_thread_union+0x3e90/0x4000 (unreliable)
[0.004771] [c95dfe00] [c801e314] arch_cpu_idle+0x54/0x160
[0.004784] [c95dfe30] [c8c6b92c] default_idle_call+0x4c/0x7c
[0.004798] [c95dfe50] [c815da14] do_idle+0x244/0x320
[0.004810] [c95dfea0] [c815dd28] cpu_startup_entry+0x38/0x50
[0.004823] [c95dfed0] [c800d2dc] rest_init+0xec/0x110
[0.004835] [c95dff00] [c8fe40fc] start_kernel+0x584/0x5a4
[0.004848] [c95dff90] [c800ab7c] 
start_here_common+0x1c/0x520
[0.004857] Instruction dump:
[0.004864]        
 
[0.004881]        

[Kernel-packages] [Bug 1764645] Re: Bluetooth not working

[Joseph Salisbury]

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

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

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

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

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

Title:
  Bluetooth not working

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

Bug description:
  I've installed the Ubuntu Bionic Beta 2 and everything works fine but
  the bluetooth (perfectly working with Xenial). In bluetooth control
  panel the slider is impossible to move to "on".

  1) Ubuntu Release (via 'lsb_release -rd')
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) Version of package (apt-cache policy gnome-bluetooth)
  gnome-bluetooth:
Installato: 3.28.0-2
Candidato:  3.28.0-2
Tabella versione:
   *** 3.28.0-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  I expected to switch on the bluetooth.

  4) What happened instead
  Bluetooth won't switch on.

  5) Output of rfkill list is:
  0: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no
  1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

  6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
  03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless 
  Network Adapter [168c:0034] (rev 01)
  Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- 
  size Mini PCIe Card [1a56:2003]
  Kernel driver in use: ath9k
  Kernel modules: ath9k
  04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit 
  Ethernet [1969:10a1] (rev 10)
  Bus 002 Device 002: ID 8087:8000 Intel Corp. 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 002: ID 8087:8008 Intel Corp. 
  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 004: ID 04f2:b414 Chicony Electronics Co., Ltd 
  Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. 
   
  AR3012 Bluetooth 4.0
  Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. 
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [   17.715399] Bluetooth: Core ver 2.22
  [   17.715414] Bluetooth: HCI device and connection manager initialized
  [   17.715416] Bluetooth: HCI socket layer initialized
  [   17.715418] Bluetooth: L2CAP socket layer initialized
  [   17.715422] Bluetooth: SCO socket layer initialized
  [   17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
  [   18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   18.600649] Bluetooth: BNEP filters: protocol multicast
  [   18.600651] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stormy 1484 F pulseaudio
   /dev/snd/controlC0:  stormy 1484 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 08:46:30 2018
  HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: ASUSTeK COMPUTER INC. G750JH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  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
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G750JH.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G750JH
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG750JH.20

[Kernel-packages] [Bug 1776211] kdump-log

[bugproxy]

Default Comment by Bridge

** Attachment added: "kdump-log"
   
https://bugs.launchpad.net/bugs/1776211/+attachment/5151256/+files/kdump_smt_2

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

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

Title:
  kdump fails to take dump with smt set to 2, hmc dumpstart

Status in linux package in Ubuntu:
  New

Bug description:
  --Problem Description---
  kdump fails to take dump with smt set to 2, hmc dumpstart

  ---Issue observed---
  [0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
  [0.004118] SMP NR_CPUS=2048 
  [0.004120] NUMA 
  [0.004125] pSeries
  [0.004132] Modules linked in:
  [0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic 
#13-Ubuntu
  [0.004153] task: c00046715900 task.stack: c00046134000
  [0.004162] NIP: c0006468 LR: c801764c CTR: 
006cdc70
  [0.004173] REGS: c00047fe3ce0 TRAP: 0700   Not tainted  
(4.13.0-12-generic)
  [0.004181] MSR: 80081031 
  [0.004193]   CR: 8804  XER: 2003
  [0.004204] CFAR: c0006454 SOFTE: 0 
  [0.004204] GPR00: c801764c c00047fe3f60 c95e3000 
 
  [0.004204] GPR04: 0001 0002  
ffdf 
  [0.004204] GPR08:  2804 0002 
0002 
  [0.004204] GPR12:  cfff c00046137f90 
0b5452d8 
  [0.004204] GPR16: fffd 089ffd10 0136 
0b55d378 
  [0.004204] GPR20: 0060 1eca 0a6c 
0007 
  [0.004204] GPR24:   c9621ed0 
 
  [0.004204] GPR28:  c00046134000 c00046137c80 
c9105df8 
  [0.004328] NIP [c0006468] 0xc0006468
  [0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
  [0.004345] Call Trace:
  [0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0 
(unreliable)
  [0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
  [0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
  [0.004393] [c00046137c10] [c8008ac4] 
hardware_interrupt_common+0x114/0x120
  [0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
  [0.004409] LR = arch_local_irq_restore+0x40/0x90
  [0.004423] [c00046137f00] [0005] 0x5 (unreliable)
  [0.004436] [c00046137f20] [c8049824] 
start_secondary+0x324/0x350
  [0.004450] [c00046137f90] [c800aa6c] 
start_secondary_prolog+0x10/0x14
  [0.004460] Instruction dump:
  [0.004467]        
 
  [0.004484]        
 
  [0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
  [0.004512] 
  [0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
  [0.004525] SMP NR_CPUS=2048 
  [0.004526] NUMA 
  [0.004532] pSeries
  [0.004540] Modules linked in:
  [0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G  D 
4.13.0-12-generic #13-Ubuntu
  [0.004561] task: c9579f00 task.stack: c95dc000
  [0.004569] NIP: c0006460 LR: c80b6e80 CTR: 

  [0.004580] REGS: c95dfb20 TRAP: 0700   Tainted: G  D  
(4.13.0-12-generic)
  [0.004589] MSR: 80081031 
  [0.004599]   CR: 22002228  XER: 2004
  [0.004611] CFAR: c000493c SOFTE: 0 
  [0.004611] GPR00:  c95dfda0 c95e3000 
 
  [0.004611] GPR04:    
 
  [0.004611] GPR08:  22002228 7fff 
0008 
  [0.004611] GPR12:  cfff0a80 c00c7e137f90 
09980600 
  [0.004611] GPR16: 1ec7 0001  
 
  [0.004611] GPR20:    
0007 
  [0.004611] GPR24: 0008 c800 0800 
 
  [0.004611] GPR28:  0008 c9621ed0 
c9622354 
  [0.004729] NIP [c0006460] 0xc0006460
  [0.004739] LR [c80b6e80] pseries_lpar_idle+0x30/0x50
  [0.004746] Call Trace:
  [0.004756] [c95dfda0] [c95dfe90] 
init_thread_union+0x3e90/0x4000 (unreliable)
  [0.004771] [c95dfe00] [c801e314] arch_cpu_idl

[Kernel-packages] [Bug 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart

[Frank Heimes]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Tags added: ppc64el-kdump triage-g

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

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

Title:
  kdump fails to take dump with smt set to 2, hmc dumpstart

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

Bug description:
  --Problem Description---
  kdump fails to take dump with smt set to 2, hmc dumpstart

  ---Issue observed---
  [0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
  [0.004118] SMP NR_CPUS=2048 
  [0.004120] NUMA 
  [0.004125] pSeries
  [0.004132] Modules linked in:
  [0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic 
#13-Ubuntu
  [0.004153] task: c00046715900 task.stack: c00046134000
  [0.004162] NIP: c0006468 LR: c801764c CTR: 
006cdc70
  [0.004173] REGS: c00047fe3ce0 TRAP: 0700   Not tainted  
(4.13.0-12-generic)
  [0.004181] MSR: 80081031 
  [0.004193]   CR: 8804  XER: 2003
  [0.004204] CFAR: c0006454 SOFTE: 0 
  [0.004204] GPR00: c801764c c00047fe3f60 c95e3000 
 
  [0.004204] GPR04: 0001 0002  
ffdf 
  [0.004204] GPR08:  2804 0002 
0002 
  [0.004204] GPR12:  cfff c00046137f90 
0b5452d8 
  [0.004204] GPR16: fffd 089ffd10 0136 
0b55d378 
  [0.004204] GPR20: 0060 1eca 0a6c 
0007 
  [0.004204] GPR24:   c9621ed0 
 
  [0.004204] GPR28:  c00046134000 c00046137c80 
c9105df8 
  [0.004328] NIP [c0006468] 0xc0006468
  [0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
  [0.004345] Call Trace:
  [0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0 
(unreliable)
  [0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
  [0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
  [0.004393] [c00046137c10] [c8008ac4] 
hardware_interrupt_common+0x114/0x120
  [0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
  [0.004409] LR = arch_local_irq_restore+0x40/0x90
  [0.004423] [c00046137f00] [0005] 0x5 (unreliable)
  [0.004436] [c00046137f20] [c8049824] 
start_secondary+0x324/0x350
  [0.004450] [c00046137f90] [c800aa6c] 
start_secondary_prolog+0x10/0x14
  [0.004460] Instruction dump:
  [0.004467]        
 
  [0.004484]        
 
  [0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
  [0.004512] 
  [0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
  [0.004525] SMP NR_CPUS=2048 
  [0.004526] NUMA 
  [0.004532] pSeries
  [0.004540] Modules linked in:
  [0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G  D 
4.13.0-12-generic #13-Ubuntu
  [0.004561] task: c9579f00 task.stack: c95dc000
  [0.004569] NIP: c0006460 LR: c80b6e80 CTR: 

  [0.004580] REGS: c95dfb20 TRAP: 0700   Tainted: G  D  
(4.13.0-12-generic)
  [0.004589] MSR: 80081031 
  [0.004599]   CR: 22002228  XER: 2004
  [0.004611] CFAR: c000493c SOFTE: 0 
  [0.004611] GPR00:  c95dfda0 c95e3000 
 
  [0.004611] GPR04:    
 
  [0.004611] GPR08:  22002228 7fff 
0008 
  [0.004611] GPR12:  cfff0a80 c00c7e137f90 
09980600 
  [0.004611] GPR16: 1ec7 0001  
 
  [0.004611] GPR20:    
0007 
  [0.004611] GPR24: 0008 c800 0800 
 
  [0.004611] GPR28:  0008 c9621ed0 
c9622354 
  [0.004729] NIP [c0006460] 0xc0006460
  [0.004739] LR [c80b6e80] pseries_lpar_idle+0x30/0x50
  [0.004746] Call Trace:
  [0.004756] [c95dfda0] [c95df

[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

[Thadeu Lima de Souza Cascardo]

Managed to kexec a 4.4 and a 4.15 kernel on xenial with kexec-tools
1:2.0.16-1ubuntu1~16.04.1.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  In Progress
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Committed
Status in kexec-tools source package in Artful:
  Fix Committed
Status in kexec-tools source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Latest kexec-tools is needed to load/kexec recent kernels. For older 
releases, like xenial, it's needed to support linux-hwe kernels.

  [Regression Potential]
  It might fail to load the GA kernels, like a 4.4 kernel on xenial.

  [Test case]
  Different kernels on different architectures have been tested.

  
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the
  crash kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

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

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048
  [   85.731745] NUMA
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd 
ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast 
i2c_algo_bit ttm drm_kms_helper mdio libcrc32c crc32c_vpmsum mlx5_core 
syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci mlxfw libahci nvme 
devlink nvme_core
  [   85.732704] CPU: 10 PID: 4316 Comm: bash Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   85.732764] task: c03fcb141700 task.stack: c03fc2374000
  [   85.732858] NIP: c078f588 LR: c07904b8 CTR: 
c078f560
  [   85.732977] REGS: c03fc23779f0 TRAP: 0300   Not tainted  
(4.13.0-17-generic)
  [   85.733066] MSR: 90009033 
  [   85.733075]   CR: 2842  XER: 2004
  [   85.733201] CFAR: c07904b4 DAR:  DSISR: 4200 
SOFTE: 1
  [   85.733201] GPR00: c07904b8 c03fc2377c70 c15f6000 
0063
  [   85.733201] GPR04: c03feedfade8 c03feee12068 90009033 
000a
  [   85.733201] GPR08: 0007 0001  
90001003
  [   85.733201] GPR12: c078f560 c

[Kernel-packages] [Bug 1659618] Re: Enable ARM64 support in kexec-tools

[Launchpad Bug Tracker]

This bug was fixed in the package kexec-tools -
1:2.0.16-1ubuntu1~16.04.1

---
kexec-tools (1:2.0.16-1ubuntu1~16.04.1) xenial; urgency=low

  * Backport latest kexec-tools from bionic to xenial (LP: #1743529).

 -- Thadeu Lima de Souza Cascardo   Fri, 23 Feb
2018 12:11:36 -0300

** Changed in: kexec-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Enable ARM64 support in kexec-tools

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in kexec-tools source package in Yakkety:
  Fix Committed
Status in kexec-tools package in Debian:
  Fix Released

Bug description:
  [IMPACT]
   * kexec-tools in Xenial (16.04) currently does not support ARM64
     architecture.
   * Backport support for ARM64 arch from upstream
     https://github.com/horms/kexec-tools
   * Majority of the patches are contained in kexec/arch/arm64/ except for
     one patch that impacts purgatory and common device tree routines.

  [TEST CASE]
   * I built kexec-tools for ARM64 and tested it on HW using the following
     testcase:
     $ sudo kexec -l /boot/vmlinuz--generic
   --initrd=/boot/initrd.img--generic
   --command-line="root=UUID= ro vt.handoff=7"
     $ sudo kexec -e
   * I was able to kexec the new kernel successfully.
   * [ 6702.357899] kexec_core: Starting new kernel
     [0.00] Booting Linux on physical CPU 0x200
     [0.00] Linux version -generic (buildd@bos01-arm64-008)
     (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) )
     [0.00] Boot CPU: AArch64 Processor [510f8000]

  [REGRESSION POTENTIAL]
   * Since patches are confined to arm[64] there is a low overall risk of
     regression.

  [OTHER INFO]
   * You can find a Xenial kexec-tools package built for AMD64, i386 and
     ARM64 in my PPA
     https://launchpad.net/~manjo/+archive/ubuntu/kexec-tools
   * This package is built using the Xenial source package for kexec-tools
     with ARM64 enablement patches applied.
   * Please pull the changes from my PPA package and integrate into Ubuntu
     Xenial kexec-tools after review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1659618/+subscriptions

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

[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns

[Nicolas Dichtel]

It works for me, 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/1774225

Title:
  netns: unable to follow an interface that moves to another netns

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

Bug description:
  The following upstream patches are missing (v4.16):

  6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
  c36ac8e23073 ("dev: always advertise the new nsid when the netns iface 
changes")
  38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a

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

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

[Kernel-packages] [Bug 1663400] Re: kexec: arm64: Increase the upper limit for RAM segments

[Launchpad Bug Tracker]

This bug was fixed in the package kexec-tools -
1:2.0.16-1ubuntu1~16.04.1

---
kexec-tools (1:2.0.16-1ubuntu1~16.04.1) xenial; urgency=low

  * Backport latest kexec-tools from bionic to xenial (LP: #1743529).

 -- Thadeu Lima de Souza Cascardo   Fri, 23 Feb
2018 12:11:36 -0300

** Changed in: kexec-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  kexec: arm64: Increase the upper limit for RAM segments

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in kexec-tools source package in Yakkety:
  Fix Committed
Status in kexec-tools package in Debian:
  Fix Released

Bug description:
  [Impact]
  Currently kexec is unable to see all the "System RAM" recorded in /proc/iomem.

  On a newer UEFI based Qualcomm target the number of system ram regions
  retrieved from /proc/iomem  are ~40. Currently KEXEC_SEGMENT_MAX is
  set to 16, which represents the kexec segments passed to kexec_load
  syscall, like kernel image, initrd image etc. The patch increases the
  value to 64. This enables kexec to see all the "System RAM" as
  recorded in /proc/iomem.

  [Test Case]
  == System RAM reported by /proc/iomem ==
  ubuntu@ubuntu:~$ sudo cat /proc/iomem | grep "System RAM"
  0020-0020 : System RAM
  0082-0307 : System RAM
  0308-0308 : System RAM
  0309-031f : System RAM
  0320-033f : System RAM
  0341-0589 : System RAM
  058a-058a : System RAM
  058b-058b : System RAM
  058c-0597 : System RAM
  0598-05987fff : System RAM
  05988000-0598bfff : System RAM
  0598c000-05a0 : System RAM
  05a1-05aa : System RAM
  05ab-05ca0fff : System RAM
  05ca1000-08ca : System RAM
  08cb-08cf : System RAM
  08d0-08ed : System RAM
  08ee-08ee0fff : System RAM
  08ee1000-08ee3fff : System RAM
  08ee4000-08ee : System RAM
  08ef-092a : System RAM
  092b-092d : System RAM
  092e-09422fff : System RAM
  09423000-0949 : System RAM
  094a-0957 : System RAM
  0958-0958cfff : System RAM
  0958d000-098c : System RAM
  098d-098d0fff : System RAM
  098d1000-098dbfff : System RAM
  098dc000-0e8b : System RAM
  0e8c-0e8e : System RAM
  0e8f-0fff : System RAM
  1080-17fe : System RAM
  1c02-1c7f : System RAM
  1c80-1c80 : System RAM
  1c81-7efb : System RAM
  7efc-7efd : System RAM
  7efe-7efe : System RAM
  7eff-7eff : System RAM
  7f00-17 : System RAM
  ubuntu@ubuntu:~$

  == BEFORE PATCH: System RAM reported by kexec ==
  ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.7.0-2-generic --reuse-cmd 
--initrd=/boot/initrd.img-4.7.0-2-generic | grep "System RAM"
  get_memory_ranges_iomem_cb: 0020 - 0020 : System RAM
  get_memory_ranges_iomem_cb: 0082 - 0307 : System RAM
  get_memory_ranges_iomem_cb: 0308 - 0308 : System RAM
  get_memory_ranges_iomem_cb: 0309 - 031f : System RAM
  get_memory_ranges_iomem_cb: 0320 - 033f : System RAM
  get_memory_ranges_iomem_cb: 0341 - 0589 : System RAM
  get_memory_ranges_iomem_cb: 058a - 058a : System RAM
  get_memory_ranges_iomem_cb: 058b - 058b : System RAM
  get_memory_ranges_iomem_cb: 058c - 0597 : System RAM
  get_memory_ranges_iomem_cb: 0598 - 05987fff : System RAM
  get_memory_ranges_iomem_cb: 05988000 - 0598bfff : System RAM
  get_memory_ranges_iomem_cb: 0598c000 - 05a0 : System RAM
  get_memory_ranges_iomem_cb: 05a1 - 05aa : System RAM
  get_memory_ranges_iomem_cb: 05ab - 05ca0fff : System RAM
  get_memory_ranges_iomem_cb: 05ca1000 - 08ca : System RAM
  get_memory_ranges_iomem_cb: 08cb - 08cf : System RAM

  ==AFTER PATCH: System RAM reported by kexec ==
  ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.7.0-2-generic --reuse-cmd 
--initrd=/boot/initrd.img-4.7.0-2-generic | grep "System RAM"
  get_memory_ranges_iomem_cb: 0020 - 0020 : System RAM
  get_memory_ranges_iomem_cb: 0082 - 0307 : System RAM
  get_memory_ranges_iomem_cb: 0308 - 0308 : System RAM
  get_memory_ranges_iomem_cb: 0309 - 031f : System RAM
  get_memory_ranges_iomem_cb: 0320 - 033f : System RAM
  get_memory_ranges_iomem_cb: 0341 - 0589 : System RAM
  get_memory_ranges_iomem_cb: 058a - 058a : Syst

[Kernel-packages] [Bug 1661363] Re: Fails to load compressed kernels on arm64

[Launchpad Bug Tracker]

This bug was fixed in the package kexec-tools -
1:2.0.16-1ubuntu1~16.04.1

---
kexec-tools (1:2.0.16-1ubuntu1~16.04.1) xenial; urgency=low

  * Backport latest kexec-tools from bionic to xenial (LP: #1743529).

 -- Thadeu Lima de Souza Cascardo   Fri, 23 Feb
2018 12:11:36 -0300

** Changed in: kexec-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Fails to load compressed kernels on arm64

Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in kexec-tools source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  kexec-tools will not load a compressed kernel on arm64. Ubuntu ships 
compressed kernel images on arm64 starting with 16.10 (and hwe kernels for 
16.04). A workaround is to manually decompress the kernel before loading it, 
but this is not supported by the use-kexec-for-reboot-by-default feature of the 
kexec-tools package.

  [Test Case]
  ubuntu@ubuntu:~$ sudo file /boot/vmlinuz-4.9.0-15-generic
  /boot/vmlinuz-4.9.0-15-generic: gzip compressed data, max compression, from 
Unix
  ubuntu@ubuntu:~$ sudo kexec -d -l /boot/vmlinuz-4.9.0-15-generic -t Image
  arch_process_options:141: command_line: (null)
  arch_process_options:143: initrd: (null)
  arch_process_options:144: dtb: (null)
  kernel: 0x8ff61010 kernel_size: 0x6ee18b
  get_memory_ranges_iomem_cb: 4000 - bfff : System RAM
  get_memory_ranges_iomem_cb: 0001 - 00013858 : System RAM
  get_memory_ranges_iomem_cb: 00013875 - 00013bc1 : System RAM
  get_memory_ranges_iomem_cb: 00013c00 - 00013fff : System RAM
  image_arm64_probe: Bad arm64 image header.
  elf_arm64_probe: Not an ELF executable.
  image_arm64_probe: Bad arm64 image header.
  Cannot determine the file type of /boot/vmlinuz-4.9.0-15-generic

  [Regression Risk]
  kexec-tools did not support arm64 until zesty so, assuming the fix is 
localized to arm64 code, regression risk is negligible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1661363/+subscriptions

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

[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

[Launchpad Bug Tracker]

This bug was fixed in the package kexec-tools -
1:2.0.16-1ubuntu1~17.10.1

---
kexec-tools (1:2.0.16-1ubuntu1~17.10.1) artful; urgency=low

  * Backport latest kexec-tools from bionic to artful (LP: #1743529).

 -- Thadeu Lima de Souza Cascardo   Tue, 06 Mar
2018 04:43:58 -0300

** Changed in: kexec-tools (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  In Progress
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in kexec-tools source package in Artful:
  Fix Released
Status in kexec-tools source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Latest kexec-tools is needed to load/kexec recent kernels. For older 
releases, like xenial, it's needed to support linux-hwe kernels.

  [Regression Potential]
  It might fail to load the GA kernels, like a 4.4 kernel on xenial.

  [Test case]
  Different kernels on different architectures have been tested.

  
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the
  crash kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

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

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048
  [   85.731745] NUMA
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd 
ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast 
i2c_algo_bit ttm drm_kms_helper mdio libcrc32c crc32c_vpmsum mlx5_core 
syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci mlxfw libahci nvme 
devlink nvme_core
  [   85.732704] CPU: 10 PID: 4316 Comm: bash Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   85.732764] task: c03fcb141700 task.stack: c03fc2374000
  [   85.732858] NIP: c078f588 LR: c07904b8 CTR: 
c078f560
  [   85.732977] REGS: c03fc23779f0 TRAP: 0300   Not tainted  
(4.13.0-17-generic)
  [   85.733066] MSR: 90009033 
  [   85.733075]   CR: 2842  XER: 2004
  [   85.733201] CFAR: c07904b4 DAR:  DSISR: 4200 
SOFTE: 1
  [   85.733201] GPR00: c07904b8 c03fc2377c70 c15f6000 
0063
  [   85.733201] GPR04: c0

[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

[Thadeu Lima de Souza Cascardo]

$ dpkg -s kexec-tools | grep Version
Version: 1:2.0.16-1ubuntu1~17.10.1
$ uname -r
4.13.0-43-generic

Verified on artful as well.

** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  In Progress
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in kexec-tools source package in Artful:
  Fix Released
Status in kexec-tools source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Latest kexec-tools is needed to load/kexec recent kernels. For older 
releases, like xenial, it's needed to support linux-hwe kernels.

  [Regression Potential]
  It might fail to load the GA kernels, like a 4.4 kernel on xenial.

  [Test case]
  Different kernels on different architectures have been tested.

  
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the
  crash kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

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

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048
  [   85.731745] NUMA
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd 
ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast 
i2c_algo_bit ttm drm_kms_helper mdio libcrc32c crc32c_vpmsum mlx5_core 
syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci mlxfw libahci nvme 
devlink nvme_core
  [   85.732704] CPU: 10 PID: 4316 Comm: bash Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   85.732764] task: c03fcb141700 task.stack: c03fc2374000
  [   85.732858] NIP: c078f588 LR: c07904b8 CTR: 
c078f560
  [   85.732977] REGS: c03fc23779f0 TRAP: 0300   Not tainted  
(4.13.0-17-generic)
  [   85.733066] MSR: 90009033 
  [   85.733075]   CR: 2842  XER: 2004
  [   85.733201] CFAR: c07904b4 DAR:  DSISR: 4200 
SOFTE: 1
  [   85.733201] GPR00: c07904b8 c03fc2377c70 c15f6000 
0063
  [   85.733201] GPR04: c03feedfade8 c03feee12068 90009033 
000a
  [   85.733201] GPR08: 0007 0001  
90001003
  [   85.

[Kernel-packages] [Bug 1743529] Update Released

[Łukasz Zemczak]

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

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

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  In Progress
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in kexec-tools source package in Artful:
  Fix Released
Status in kexec-tools source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Latest kexec-tools is needed to load/kexec recent kernels. For older 
releases, like xenial, it's needed to support linux-hwe kernels.

  [Regression Potential]
  It might fail to load the GA kernels, like a 4.4 kernel on xenial.

  [Test case]
  Different kernels on different architectures have been tested.

  
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the
  crash kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

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

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048
  [   85.731745] NUMA
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd 
ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast 
i2c_algo_bit ttm drm_kms_helper mdio libcrc32c crc32c_vpmsum mlx5_core 
syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci mlxfw libahci nvme 
devlink nvme_core
  [   85.732704] CPU: 10 PID: 4316 Comm: bash Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   85.732764] task: c03fcb141700 task.stack: c03fc2374000
  [   85.732858] NIP: c078f588 LR: c07904b8 CTR: 
c078f560
  [   85.732977] REGS: c03fc23779f0 TRAP: 0300   Not tainted  
(4.13.0-17-generic)
  [   85.733066] MSR: 90009033 
  [   85.733075]   CR: 2842  XER: 2004
  [   85.733201] CFAR: c07904b4 DAR:  DSISR: 4200 
SOFTE: 1
  [   85.733201] GPR00: c07

[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

[Launchpad Bug Tracker]

This bug was fixed in the package kexec-tools -
1:2.0.16-1ubuntu1~16.04.1

---
kexec-tools (1:2.0.16-1ubuntu1~16.04.1) xenial; urgency=low

  * Backport latest kexec-tools from bionic to xenial (LP: #1743529).

 -- Thadeu Lima de Souza Cascardo   Fri, 23 Feb
2018 12:11:36 -0300

** Changed in: kexec-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  In Progress
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in kexec-tools source package in Artful:
  Fix Released
Status in kexec-tools source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Latest kexec-tools is needed to load/kexec recent kernels. For older 
releases, like xenial, it's needed to support linux-hwe kernels.

  [Regression Potential]
  It might fail to load the GA kernels, like a 4.4 kernel on xenial.

  [Test case]
  Different kernels on different architectures have been tested.

  
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the
  crash kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

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

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048
  [   85.731745] NUMA
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd 
ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast 
i2c_algo_bit ttm drm_kms_helper mdio libcrc32c crc32c_vpmsum mlx5_core 
syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci mlxfw libahci nvme 
devlink nvme_core
  [   85.732704] CPU: 10 PID: 4316 Comm: bash Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   85.732764] task: c03fcb141700 task.stack: c03fc2374000
  [   85.732858] NIP: c078f588 LR: c07904b8 CTR: 
c078f560
  [   85.732977] REGS: c03fc23779f0 TRAP: 0300   Not tainted  
(4.13.0-17-generic)
  [   85.733066] MSR: 90009033 
  [   85.733075]   CR: 2842  XER: 2004
  [   85.733201] CFAR: c07904b4 DAR:  DSISR: 4200 
SOFTE: 1
  [   85.733201] GPR00: c07904b8 c03fc2377c70 c15f6000 
0063
  [   85.733201] GPR04: c0

[Kernel-packages] [Bug 1760173] Re: zfs, zpool commands hangs for 10 seconds without a /dev/zfs

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu Bionic)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Artful)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  zfs, zpool commands hangs for 10 seconds without a /dev/zfs

Status in lxd package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Artful:
  Fix Committed
Status in zfs-linux source package in Bionic:
  Fix Committed
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, Xenial, Artful, Bionic ==

  When outside a lxd container with zfs storage, zfs list or zpool
  status either returns or reports what's going on.

  When inside a lxd container with zfs storage, zfs list or zpool status
  appears to hang, no output for 10 seconds.

  == Fix ==

  Inside a container we don't need the 10 seconds timeout, so check for
  this scenario and set the timeout to default to 0 seconds.

  == Regression Potential ==

  Minimal, this caters for a corner case inside a containerized
  environment, the fix will not alter the behaviour for other cases.

  -

  1. # lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2. # apt-cache policy zfsutils-linux
  zfsutils-linux:
    Installed: 0.6.5.6-0ubuntu19
    Candidate: 0.6.5.6-0ubuntu19
    Version table:
   *** 0.6.5.6-0ubuntu19 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. When inside a lxd container with zfs storage, zfs list or zpool
  status either return or report what's going on.

  4. When inside a lxd container with zfs storage, zfs list or zpool
  status appears to hang, no output for 10 seconds.

  strace reveals that without a /dev/zfs the tools wait for it to appear
  for 10 seconds but do not provide a command line switch to disable or
  make it more verbose.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu19
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 18:09:29 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1771238] Re: Not able to passthrough > 32 PCIe devices to a KVM Guest

[ Christian Ehrhardt ]

I got access to such a machine and successfully added >32 cards via
hotplug as well as statically in the initial guest xml of libvirt.

I face maybe related issue around "accel/kvm/kvm-all.c:952:
kvm_irqchip_commit_routes: Assertion `ret == 0' failed." now but noting
seems like the old DPC issue.

Closing this bug (and considering to open a new one for the different
issue mentioned above).

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

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

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

Title:
  Not able to passthrough > 32 PCIe devices to a KVM Guest

Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  Using an Ubuntu Server 16.04-based host with KVM hypervisor installed,
  we are unable to launch a vanilla Ubuntu Server 16.04.4 guest with >=
  32 PCIe devices. It is 100% reproducible. Using fewer PCIe devices
  works fine. We are using the vanilla kvm and qemu packages from the
  Canonical repos.

  The ultimate goal is to create a KVM Guest wherein I can passthrough
  44 PCI devices.

  When a KVM Guest launches, it also has some internal PCIe devices
  including host bridge, USB, IDE (for virtual disk), and virtual nic
  etc.

  Script used to launch all devices looks like this:

  #!/bin/bash 
  NAME=16gpuvm 

  sudo qemu-img create -f qcow2 /home/lab/kvm/images/${NAME}.img 40G && 
  sudo virt-install \ 
  --name ${NAME} \ 
  --ram 716800 \ 
  --vcpus 88 \ 
  --disk path=/home/lab/kvm/images/${NAME}.img,format=qcow2 \ 
  --network bridge=virbr0 \ 
  --graphics none \ 
  --host-device 34:00.0 \ 
  --host-device 36:00.0 \ 
  --host-device 39:00.0 \ 
  --host-device 3b:00.0 \ 
  --host-device 57:00.0 \ 
  --host-device 59:00.0 \ 
  --host-device 5c:00.0 \ 
  --host-device 5e:00.0 \ 
  --host-device 61:00.0 \ 
  --host-device 62:00.0 \ 
  --host-device 63:00.0 \ 
  --host-device 65:00.0 \ 
  --host-device 66:00.0 \ 
  --host-device 67:00.0 \ 
  --host-device 35:00.0 \ 
  --host-device 3a:00.0 \ 
  --host-device 58:00.0 \ 
  --host-device 5d:00.0 \ 
  --host-device 2e:00.0 \ 
  --host-device 2f:00.0 \ 
  --host-device 51:00.0 \ 
  --host-device 52:00.0 \ 
  --host-device b7:00.0 \ 
  --host-device b9:00.0 \ 
  --host-device bc:00.0 \ 
  --host-device be:00.0 \ 
  --host-device e0:00.0 \ 
  --host-device e2:00.0 \ 
  --host-device e5:00.0 \ 
  --host-device e7:00.0 \ 
  --host-device c1:00.0 \ 
  --host-device c2:00.0 \ 
  --host-device c3:00.0 \ 
  --host-device c5:00.0 \ 
  --host-device c6:00.0 \ 
  --host-device c7:00.0 \ 
  --host-device b8:00.0 \ 
  --host-device bd:00.0 \ 
  --host-device e1:00.0 \ 
  --host-device e6:00.0 \ 
  --host-device b1:00.0 \ 
  --host-device b2:00.0 \ 
  --host-device da:00.0 \ 
  --host-device db:00.0 \ 
  --console pty,target_type=serial \ 
  --location http://ftp.ubuntu.com/ubuntu/dists/xenial/main/installer-amd64 \ 
  --initrd-inject=/home/lab/kvm/images/preseed.cfg \ 
  --extra-args=" 
  console=ttyS0,115200 
  locale=en_US 
  console-keymaps-at/keymap=us 
  console-setup/ask_detect=false 
  console-setup/layoutcode=us 
  keyboard-configuration/layout=USA 
  keyboard-configuration/variant=USA 
  hostname=${NAME} 
  file=file:/preseed.cfg 
  "

  Passing > 32 device causes this issue:  32nd device hits a DPC error
  and the host/HV crashes:

  
  Apr 25 22:34:35 xpl-evt-16 kernel: [18125.977496] dpc :5b:10.0:pcie210: 
DPC containment event, status:0x0009 source:0x
  Apr 25 22:34:35 xpl-evt-16 kernel: [18125.977500] dpc :5b:10.0:pcie210: 
DPC unmasked uncorrectable error detected, remove downstream devices
  Apr 25 22:34:35 xpl-evt-16 kernel: [18125.994326] vfio-pci :5e:00.0: 
Refused to change power state, currently in D3
  Apr 25 22:34:35 xpl-evt-16 kernel: [18125.994427] iommu: Removing device 
:5e:00.0 from group 92

  
  From syslog (attached)

  Apr 25 22:37:13 xpl-evt-16 kernel: [2.194358] dpc :bb:04.0:pcie210: 
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+ 
RP PIO Log 0, DL_ActiveErr+
  Apr 25 22:37:13 xpl-evt-16 kernel: [2.194387] dpc :bb:10.0:pcie210: 
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+ 
RP PIO Log 0, DL_ActiveErr+
  Apr 25 22:37:13 xpl-evt-16 kernel: [2.194413] dpc :d9:00.0:pcie210: 
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+ 
RP PIO Log 0, DL_ActiveErr+
  Apr 25 22:37:13 xpl-evt-16 kernel: [2.194439] dpc :d9:01.0:pcie210: 
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+ 
RP PIO Log 0, DL_ActiveErr+
  Apr 25 22:37:13 xpl-evt-16 kernel: [2.194472] dpc :d9:02.0:pcie210: 
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+ 
RP PIO Log 0, DL_ActiveErr+
  Apr 25 22:37:13 xpl-evt-16 kernel: [ 

[Kernel-packages] [Bug 1774484] Re: package linux-firmware 1.173.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 127

[Seth Forshee]

Why do you say it has something to do with livepatch? This is the error
from the log:

awk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined
symbol: UP

This looks like a problem with the libreadline library, but since the
library being used is in /usr/local/lib it looks like something you have
installed manually, not something from an Ubuntu package. I'd suggest
uninstalling the library and trying the update again.

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

Title:
  package linux-firmware 1.173.1 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 127

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  The failure has something to do with live patch

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Tue May 29 09:03:40 2018
  Dependencies:
   
  DuplicateSignature:
   package:linux-firmware:1.173.1
   Setting up linux-firmware (1.173.1) ...
   awk: symbol lookup error: /usr/local/lib/libreadline.so.7: undefined symbol: 
UP
   dpkg: error processing package linux-firmware (--configure):
installed linux-firmware package post-installation script subprocess 
returned error exit status 127
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 127
  PackageArchitecture: all
  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-firmware
  Title: package linux-firmware 1.173.1 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1774950] Re: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

[cmeerw]

I am seeing this problem on an Acer Travelmate B115 (Intel Pentium N3540
CPU, 4 GB RAM, no SSD)

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

Title:
  Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and
  Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Kubuntu 18.04 on 3 different machines (my friend's
  and my own) with no suspend problems but my HP Pavilion 11 x360 does
  not suspend.

  It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse,
  Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu
  18.04.

  I have also tried suspend using a live USB of 18.04 on this machine
  and it fails in the same way, so does not appear to be caused by any
  additional programs that I had installed.

  By installing an older kernel (4.14) on Kubuntu 18.04 the suspend
  function works as expected.

  Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the
  suspend failure that freezes the machine and requires a hard reset.

  
  Correct behaviour is - 

  Screen goes blank, fan goes off, power LED flashes to show machine is
  in suspend. Pressing power button triggers 'resume' function.

  
  What happens - 

  Screen goes blank, fan stays on, power LED stays on. Machine stays in
  this state and does not respond to any keyboard interaction, mouse
  movement or power button presses.

  
  Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response.

  The only way to use the machine is to shut down by holding down the
  power button.

  
  Checking the logs suggests that the machine believes it is in suspend mode 
sleep [deep] when it isn't.

  Having to hard reset to get any response means that the kernel logs
  say no more than sleep [deep]

  pm-suspend also results in the same problems with kernels 4.15 and
  4.16, but works fine with 4.14.

  It is curious that a machine that suspends fine on an earlier 4.14
  kernel no longer works with 4.15 and above, whilst 3 other machines
  (including one with pretty similar hardware) do not exhibit this
  problem.

  There are only a handful of questions about it on the forums but at
  least 3 other people have the same problem:

  https://askubuntu.com/questions/1029405/ubuntu-18-04-crashes-on-
  resuming-from-suspend

  https://askubuntu.com/questions/1041369/after-upgrading-
  from-17-10-ubuntu-18-04-wont-sleep-suspend

  I am attempting to round up anyone else with the same issue and point
  them to this bug report.

  My laptop is HP Pavilion x360 11-n013na 
  Matalaks is Acer Aspire ES1-511
  collisionTwo has XPS 9560

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

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

[Kernel-packages] [Bug 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart

[Manoj Iyer]

** Changed in: makedumpfile (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

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

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

Title:
  kdump fails to take dump with smt set to 2, hmc dumpstart

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

Bug description:
  --Problem Description---
  kdump fails to take dump with smt set to 2, hmc dumpstart

  ---Issue observed---
  [0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
  [0.004118] SMP NR_CPUS=2048 
  [0.004120] NUMA 
  [0.004125] pSeries
  [0.004132] Modules linked in:
  [0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic 
#13-Ubuntu
  [0.004153] task: c00046715900 task.stack: c00046134000
  [0.004162] NIP: c0006468 LR: c801764c CTR: 
006cdc70
  [0.004173] REGS: c00047fe3ce0 TRAP: 0700   Not tainted  
(4.13.0-12-generic)
  [0.004181] MSR: 80081031 
  [0.004193]   CR: 8804  XER: 2003
  [0.004204] CFAR: c0006454 SOFTE: 0 
  [0.004204] GPR00: c801764c c00047fe3f60 c95e3000 
 
  [0.004204] GPR04: 0001 0002  
ffdf 
  [0.004204] GPR08:  2804 0002 
0002 
  [0.004204] GPR12:  cfff c00046137f90 
0b5452d8 
  [0.004204] GPR16: fffd 089ffd10 0136 
0b55d378 
  [0.004204] GPR20: 0060 1eca 0a6c 
0007 
  [0.004204] GPR24:   c9621ed0 
 
  [0.004204] GPR28:  c00046134000 c00046137c80 
c9105df8 
  [0.004328] NIP [c0006468] 0xc0006468
  [0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
  [0.004345] Call Trace:
  [0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0 
(unreliable)
  [0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
  [0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
  [0.004393] [c00046137c10] [c8008ac4] 
hardware_interrupt_common+0x114/0x120
  [0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
  [0.004409] LR = arch_local_irq_restore+0x40/0x90
  [0.004423] [c00046137f00] [0005] 0x5 (unreliable)
  [0.004436] [c00046137f20] [c8049824] 
start_secondary+0x324/0x350
  [0.004450] [c00046137f90] [c800aa6c] 
start_secondary_prolog+0x10/0x14
  [0.004460] Instruction dump:
  [0.004467]        
 
  [0.004484]        
 
  [0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
  [0.004512] 
  [0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
  [0.004525] SMP NR_CPUS=2048 
  [0.004526] NUMA 
  [0.004532] pSeries
  [0.004540] Modules linked in:
  [0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G  D 
4.13.0-12-generic #13-Ubuntu
  [0.004561] task: c9579f00 task.stack: c95dc000
  [0.004569] NIP: c0006460 LR: c80b6e80 CTR: 

  [0.004580] REGS: c95dfb20 TRAP: 0700   Tainted: G  D  
(4.13.0-12-generic)
  [0.004589] MSR: 80081031 
  [0.004599]   CR: 22002228  XER: 2004
  [0.004611] CFAR: c000493c SOFTE: 0 
  [0.004611] GPR00:  c95dfda0 c95e3000 
 
  [0.004611] GPR04:    
 
  [0.004611] GPR08:  22002228 7fff 
0008 
  [0.004611] GPR12:  cfff0a80 c00c7e137f90 
09980600 
  [0.004611] GPR16: 1ec7 0001  
 
  [0.004611] GPR20:    
0007 
  [0.004611] GPR24: 0008 c800 0800 
 
  [0.004611] GPR28:  0008 c9621ed0 
c9622354 
  [0.004729] NIP [c0006460] 0xc0006460
  [0.004739] LR [c80b6e80] pseries_lpar_idle+0x30/0x50
  [0.004746] Call Trace:
  [0.004756] [c95dfda0] [c95dfe90] 
init_thread_union+0x3e90/0x4000 (unreliable)
  [0.004771] [c95dfe00] [c801e314] arch_cpu_idle+0x54/

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

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Importance: Undecided => Critical

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

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

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

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

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

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

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

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

  ```
  $ uname -a
  Linux flughafenberlinbrandenburgwillybrandt 4.4.0-124-generic #148-Ubuntu SMP 
Wed May 2 13:02:22 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
  $ dpkg -l linux-image-4.15.0-22-generic
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version
Architecture   Description
  
+++-==-==-==-=
  ii  linux-image-4.15.0-22-generic  4.15.0-22.24   
ppc64elSigned kernel image generic
  $ more /etc/os-release 
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  ```
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 23 16:40 seq
   crw-rw 1 root audio 116, 33 May 23 16:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=2c3dd738-785a-469b-843e-9f0ba8b47b0d ro 
rootflags=subvol=@ quiet splash
  ProcLoadAvg: 0.01 0.08 0.04 2/1373 28071
  ProcSwaps: Filename 

[Kernel-packages] [Bug 1762844] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel

[Manoj Iyer]

** Tags added: triage-a

-- 
You 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:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

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] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c000200e0b20fae0] c0c56ae4 unix_stream_sendmsg+0x264/0x5c0
  [c000200e0b20fbc0] c0b1ec64 sock_sendms

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Manoj Iyer]

** Tags removed: triage-a
** Tags added: triage-g

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  New
Status in crash source package in Artful:
  In Progress
Status in crash source package in Bionic:
  Fix Released

Bug description:
  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)
   
  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8001-22C 

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows 

  Once you generate the kdump 
  use crash to analyze the vmcore and we get this error 

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)   
  WARNING: cannot access vmalloc'd module memory

  
  crash: invalid structure member offset: thread_info_task
 FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

100833e0: (undetermined)
1017d220: OFFSET_verify+80
1011552c: task_init+5084
1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

commit c8178eca9c74f81a7f803a58d339635cc152e8d9
Author: Dave Anderson 
Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

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

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

[Kernel-packages] [Bug 1757402] Re: Ubuntu18.04:pKVM - Host in hung state and out of network after few hours of stress run on all guests

[Manoj Iyer]

** Changed in: linux (Ubuntu Artful)
   Status: Incomplete => Won't Fix

** Changed in: ubuntu-power-systems
   Status: Incomplete => Fix Released

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

Title:
  Ubuntu18.04:pKVM - Host  in hung state and out of network after few
  hours of stress run on all guests

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - INDIRA P. JOGA  - 2018-02-11 
12:37:25 ==
  Problem Description:
  ===
  After few hours of run system is in hung state with, "rcu_sched detected 
stalls on CPUs/tasks" messages on the host IPMI console and host is out of 
network .

  Steps to re-create:
  ==
  > Installed Ubuntu1804 on boslcp3 host.

  root@boslcp3:~# uname -a
  Linux boslcp3 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:15:55 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:~# uname -r
  4.13.0-25-generic

  > root@boslcp3:~# ppc64_cpu --smt
  SMT is off

  > Hugepage set up

  echo 8500 > /proc/sys/vm/nr_hugepages

  > Defined the guests from host machine

  IdName   State
  
   2 boslcp3g2  shut off
   3 boslcp3g3  shut off
   4 boslcp3g4  shut off
   6 boslcp3g1  shut off
   7 boslcp3g5  shut off

  > Started and installed ubuntu1804 daily build on all the guests.

  root@boslcp3:~# virsh list --all
   IdName   State
  
   2 boslcp3g2  running
   3 boslcp3g3  running
   4 boslcp3g4  running
   6 boslcp3g1  running
   7 boslcp3g5  running

  > Started regression run (IO_BASE_TCP_NFS) tests on all 5 guests.
  NOTE: Removed madvise test case from BASE focus areas.

  > Run went fine for few hours on all guests.

  >  After few hours of run ,Host system is in hung state and  host
  console dumps CPU stall messages as below

  [SOL Session operational.  Use ~? for help]
  [250867.133429] INFO: rcu_sched detected stalls on CPUs/tasks:
  [250867.133499]   (detected by 86, t=62711832 jiffies, g=497, c=496, 
q=31987857)
  [250867.133554] All QSes seen, last rcu_sched kthread activity 62711828 
(4357609080-4294897252), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [250867.133690] rcu_sched kthread starved for 62711828 jiffies! g497 c496 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x100
  [250931.133433] INFO: rcu_sched detected stalls on CPUs/tasks:
  [250931.133494]   (detected by 3, t=62727832 jiffies, g=497, c=496, 
q=31995625)
  [250931.133572] All QSes seen, last rcu_sched kthread activity 62727828 
(4357625080-4294897252), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [250931.133741] rcu_sched kthread starved for 62727828 jiffies! g497 c496 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x100
  [250995.133432] INFO: rcu_sched detected stalls on CPUs/tasks:
  [250995.133480]   (detected by 54, t=62743832 jiffies, g=497, c=496, 
q=32004479)
  [250995.133526] All QSes seen, last rcu_sched kthread activity 62743828 
(4357641080-4294897252), jiffies_till_next_fqs=1, root ->qsmask 0x0
  [250995.133645] rcu_sched kthread starved for 62743828 jiffies! g497 c496 
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x100

  > Not able to get the prompt

  > Ping /shh to boslcp3 also fails

  [ipjoga@kte ~]$ ping boslcp3
  PING boslcp3.isst.aus.stglabs.ibm.com (10.33.0.157) 56(84) bytes of data.
  From kte.isst.aus.stglabs.ibm.com (10.33.11.31) icmp_seq=1 Destination Host 
Unreachable
  From kte.isst.aus.stglabs.ibm.com (10.33.11.31) icmp_seq=2 Destination Host 
Unreachable
  From kte.isst.aus.stglabs.ibm.com (10.33.11.31) icmp_seq=3 Destination Host 
Unreachable

  [ipjoga@kte ~]$ ssh root@boslcp3
  ssh: connect to host boslcp3 port 22: No route to host

  > boslcp3 is not reachable

  > Attached boslcp3 host console logs

  == Comment: #1 - INDIRA P. JOGA  - 2018-02-11 
12:39:29 ==
  Added Host console logs

  == Comment: #24 - VIPIN K. PARASHAR  - 2018-02-16 
05:46:13 ==
  From Linux logs
  ===

  [72072.290071] watchdog: BUG: soft lockup - CPU#132 stuck for 22s! [CPU 
12/KVM:15579]
  [72072.290218] CPU: 132 PID: 15579 Comm: CPU 12/KVM Tainted: GWL  
4.13.0-32-generic #35-Ubuntu
  [72072.290220] task: c000200debf82e00 task.stack: c000200e140f8000
  [72072.290221] NIP: c0c779e0 LR: c008166893a0 CTR: 
c0c77980
  [72072.290223] REGS: c000200e140fb790 TRAP: 0901   Tainted: GWL   
(4.13.0-32-generic)
  [72072.290224] MSR:

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

[Manoj Iyer]

These patches were accepted and are in route for 18.04.1.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

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
  ^X
  ^C

  7. ping to boslcp3g3 is fine but guest c

[Kernel-packages] [Bug 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart

[Thadeu Lima de Souza Cascardo]

Hari mentions linux commits, so I don't think there is anything for us
to do on makedumpfile side here. I'll ask Joe to produce a kernel with
those commits.

Cascardo.

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

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

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

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

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

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

Title:
  kdump fails to take dump with smt set to 2, hmc dumpstart

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

Bug description:
  --Problem Description---
  kdump fails to take dump with smt set to 2, hmc dumpstart

  ---Issue observed---
  [0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
  [0.004118] SMP NR_CPUS=2048 
  [0.004120] NUMA 
  [0.004125] pSeries
  [0.004132] Modules linked in:
  [0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic 
#13-Ubuntu
  [0.004153] task: c00046715900 task.stack: c00046134000
  [0.004162] NIP: c0006468 LR: c801764c CTR: 
006cdc70
  [0.004173] REGS: c00047fe3ce0 TRAP: 0700   Not tainted  
(4.13.0-12-generic)
  [0.004181] MSR: 80081031 
  [0.004193]   CR: 8804  XER: 2003
  [0.004204] CFAR: c0006454 SOFTE: 0 
  [0.004204] GPR00: c801764c c00047fe3f60 c95e3000 
 
  [0.004204] GPR04: 0001 0002  
ffdf 
  [0.004204] GPR08:  2804 0002 
0002 
  [0.004204] GPR12:  cfff c00046137f90 
0b5452d8 
  [0.004204] GPR16: fffd 089ffd10 0136 
0b55d378 
  [0.004204] GPR20: 0060 1eca 0a6c 
0007 
  [0.004204] GPR24:   c9621ed0 
 
  [0.004204] GPR28:  c00046134000 c00046137c80 
c9105df8 
  [0.004328] NIP [c0006468] 0xc0006468
  [0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
  [0.004345] Call Trace:
  [0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0 
(unreliable)
  [0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
  [0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
  [0.004393] [c00046137c10] [c8008ac4] 
hardware_interrupt_common+0x114/0x120
  [0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
  [0.004409] LR = arch_local_irq_restore+0x40/0x90
  [0.004423] [c00046137f00] [0005] 0x5 (unreliable)
  [0.004436] [c00046137f20] [c8049824] 
start_secondary+0x324/0x350
  [0.004450] [c00046137f90] [c800aa6c] 
start_secondary_prolog+0x10/0x14
  [0.004460] Instruction dump:
  [0.004467]        
 
  [0.004484]        
 
  [0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
  [0.004512] 
  [0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
  [0.004525] SMP NR_CPUS=2048 
  [0.004526] NUMA 
  [0.004532] pSeries
  [0.004540] Modules linked in:
  [0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G  D 
4.13.0-12-generic #13-Ubuntu
  [0.004561] task: c9579f00 task.stack: c95dc000
  [0.004569] NIP: c0006460 LR: c80b6e80 CTR: 

  [0.004580] REGS: c95dfb20 TRAP: 0700   Tainted: G  D  
(4.13.0-12-generic)
  [0.004589] MSR: 80081031 
  [0.004599]   CR: 22002228  XER: 2004
  [0.004611] CFAR: c000493c SOFTE: 0 
  [0.004611] GPR00:  c95dfda0 c95e3000 
 
  [0.004611] GPR04:    
 
  [0.004611] GPR08:  22002228 7fff 
0008 
  [0.004611] GPR12:  cfff0a80 c00c7e137f90 
09980600 
  [0.004611] GPR16: 1ec7 0001  
 
  [0.004611] GPR20:    
0007 
  [0.004611] G

[Kernel-packages] [Bug 1768898] Re: smp_call_function_single/many core hangs with stop4 alone

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Committed

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

Title:
  smp_call_function_single/many core hangs with stop4 alone

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

Bug description:
  == SRU Justification ==
  IBM reports that this bug occurs with stop4 which results in soft lockups/rcu 
stalls.
  This is a kernel synchronization issue leading to a dead lock.

  This bug was introduced by commit 7bc54b652f13 in v4.8-rc1.  This
  regression is fixed by mainline commit c0f7f5b6c6910.

  == Fix ==
  c0f7f5b6c6910 ("cpufreq: powernv: Fix hardlockup due to synchronous smp_call 
in timer interrupt")

  == Regression Potential ==
  Low. Fixes current regression.  Cc'd to upstream stable, so it has had
  additon upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  Recently we discovered this bug occurs just alone with stop4 which
  results in soft lockups/rcu stalls.

  ```
  root@ltc-boston125:~# [15523.619395] systemd[1]: systemd-journald.service: 
Processes still around after final SIGKILL. Entering failed mode.
  [15523.619508] systemd[1]: systemd-journald.service: Failed with result 
'timeout'.
  [15523.619769] systemd[1]: Failed to start Journal Service.
  [15523.620618] systemd[1]: systemd-journald.service: Service has no hold-off 
time, scheduling restart.
  [15523.620774] systemd[1]: systemd-journald.service: Scheduled restart job, 
restart counter is at 21.
  [15523.621462] systemd[1]: Stopped Journal Service.
  [15523.621635] systemd[1]: systemd-journald.service: Found left-over process 
1561 (systemd-journal) in control group while starting unit. Ignoring.
  [15523.621756] systemd[1]: This usually indicates unclean termination of a 
previous run, or service implementation deficiencies.
  [15523.621888] systemd[1]: systemd-journald.service: Found left-over process 
69060 (systemd-journal) in control group while starting unit. Ignoring.
  [15523.622029] systemd[1]: This usually indica[15541.629904] INFO: rcu_sched 
self-detected stall on CPU
  [15541.629958]60-: (2 GPs behind) idle=146/142/0 
softirq=300022/300022 fqs=999069
  [15541.630046] (t=2415546 jiffies g=184827 c=184826 q=57111)
  [15541.630101] NMI backtrace for cpu 60
  [15541.630135] CPU: 60 PID: 4810 Comm: tlbie_test Tainted: G L   
4.15.0-15-generic #16-Ubuntu
  [15541.630207] Call Trace:
  [15541.630232] [c000201a1da96b00] [c0ceb35c] dump_stack+0xb0/0xf4 
(unreliable)
  [15541.630298] [c000201a1da96b40] [c0cf4d48] 
nmi_cpu_backtrace+0x1f8/0x200
  [15541.630363] [c000201a1da96bd0] [c0cf4ee8] 
nmi_trigger_cpumask_backtrace+0x198/0x1f0
  [15541.630429] [c000201a1da96c60] [c002f2d8] 
arch_trigger_cpumask_backtrace+0x28/0x40
  [15541.630495] [c000201a1da96c80] [c01a913c] 
rcu_dump_cpu_stacks+0xf4/0x158
  [15541.630560] [c000201a1da96cd0] [c01a81e8] 
rcu_check_callbacks+0x8e8/0xb40
  [15541.630625] [c000201a1da96e00] [c01b64a8] 
update_process_times+0x48/0x90
  [15541.630689] [c000201a1da96e30] [c01ce1f4] 
tick_sched_handle.isra.5+0x34/0xd0
  [15541.630753] [c000201a1da96e60] [c01ce2f0] 
tick_sched_timer+0x60/0xe0
  [15541.630818] [c000201a1da96ea0] [c01b7054] 
__hrtimer_run_queues+0x144/0x370
  [15541.630883] [c000201a1da96f20] [c01b7fac] 
hrtimer_interrupt+0xfc/0x350
  [15541.630948] [c000201a1da96ff0] [c00248f0] 
__timer_interrupt+0x90/0x260
  [15541.631013] [c000201a1da97040] [c0024d08] timer_interrupt+0x98/0xe0
  [15541.631069] [c000201a1da97070] [c0009014] 
decrementer_common+0x114/0x120
  [15541.631135] --- interrupt: 901 at smp_call_function_single+0x134/0x180
  [15541.631135] LR = smp_call_function_single+0x110/0x180
  [15541.631230] [c000201a1da973d0] [c01d55e0] 
smp_call_function_any+0x180/0x250
  [15541.631294] [c000201a1da97430] [c0acd3e8] 
gpstate_timer_handler+0x1e8/0x580
  [15541.631359] [c000201a1da974e0] [c01b46b0] call_timer_fn+0x50/0x1c0
  [15541.631433] [c000201a1da97560] [c01b4958] expire_timers+0x138/0x1f0
  [15541.631488] [c000201a1da975d0] [c01b4bf8] 
run_timer_softirq+0x1e8/0x270
  [15541.631553] [c000201a1da97670] [c0d0d6c8] __do_softirq+0x158/0x3e4
  [15541.631608] [c000201a1da97750] [c0114be8] irq_exit+0xe8/0x120
  [15541.631663] [c000201a1da97770] [c0024d0c] timer_interrupt+0x9c/0xe0
  [15541.631718] [c000201a1da977a0] [c0009014] 
decrementer_common+0x114/0x120
  [15541.6317

[Kernel-packages] [Bug 1769927] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g4:ubuntu1604:'kdump-config show' shows Not ready to kdump even after doing kdump setup.

[Frank Heimes]

** Changed in: makedumpfile (Ubuntu)
   Status: Triaged => Incomplete

** Changed in: ubuntu-power-systems
   Status: Triaged => Incomplete

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g4:ubuntu1604:'kdump-config
  show' shows Not ready to kdump even after doing kdump setup.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  Incomplete

Bug description:
  Problem Description:
  ===

  'kdump-config show' shows Not ready to kdump even after doing kdump
  setup on ubuntu160404 guest.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:1.20 & PNOR: 20180420 levels
  2. Installed p8 compat guest with ubutnu160404

  root@boslcp3g4:~# uname -a
  Linux boslcp3g4 4.4.0-122-generic #146-Ubuntu SMP Mon Apr 23 15:33:25 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3g4:~# uname -r
  4.4.0-122-generic

  3. Installed linux-crashdump crash dump utility.

  4. root@boslcp3g4:~# cat  /etc/default/grub.d/kexec-tools.cfg
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4096M"
  root@boslcp3g4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.4.0-116-generic 
root=UUID=8be749b1-a5a8-4ab8-986c-ee4fcc61165e ro
  root@boslcp3g4:~#

  5. rebooted guest and checked kdump status.

  root@boslcp3g4:~# /etc/init.d/kdump-tools status
  ? kdump-tools.service - Kernel crash dump capture service
Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
Active: active (exited) since Sun 2018-05-06 04:18:37 EDT; 7min ago
   Process: 2317 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/SUCCESS)
  Main PID: 2317 (code=exited, status=0/SUCCESS)
 Tasks: 0
Memory: 0B
   CPU: 0
CGroup: /system.slice/kdump-tools.service

  May 06 04:18:37 boslcp3g4 systemd[1]: Starting Kernel crash dump capture 
service...
  May 06 04:18:37 boslcp3g4 kdump-tools[2317]: Starting kdump-tools:  * no 
crashkernel= parameter in the kernel cmdline
  May 06 04:18:37 boslcp3g4 systemd[1]: Started Kernel crash dump capture 
service.
  root@boslcp3g4:~# sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' 
/etc/default/kdump-tools

  
  4. kdump state

  root@boslcp3g4:~# kdump-config show
  * no crashkernel= parameter in the kernel cmdline
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
/var/lib/kdump/vmlinuz
  kdump initrd:
/var/lib/kdump/initrd.img
  current state:Not ready to kdump

  kexec command:
   no kexec command recorded

  --> It still says 'Not ready to kdump'

  --> Becuase of this state not able take dump when guest hangs/crashes

  > Tried again changing crashkernel parameter on ubuntu160404 guest- p8
  compat ,but still facing same issue

  root@boslcp3g4:/kte/tools/setup.d# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.4.0-122-generic 
root=UUID=8be749b1-a5a8-4ab8-986c-ee4fcc61165e ro ro splash quiet xmon=on 
crashkernel=512M crashkernel=4096M
  root@boslcp3g4:/kte/tools/setup.d#

  root@boslcp3g4:/kte/tools/setup.d# /etc/init.d/kdump-tools status
  ? kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
 Active: active (exited) since Sun 2018-05-06 04:59:51 EDT; 14min ago
   Main PID: 2330 (code=exited, status=0/SUCCESS)
  Tasks: 0
 Memory: 0B
CPU: 0
 CGroup: /system.slice/kdump-tools.service

  May 06 04:59:50 boslcp3g4 systemd[1]: Starting Kernel crash dump capture 
se.
  May 06 04:59:51 boslcp3g4 kdump-tools[2330]: Starting kdump-tools:  * 
Invali...g
  May 06 04:59:51 boslcp3g4 kdump-tools[2330]:  * Creating symlink 
/var/lib/kd...g
  May 06 04:59:51 boslcp3g4 kdump-tools[2330]:  * Invalid symlink : 
/var/lib/k...z
  May 06 04:59:51 boslcp3g4 kdump-tools[2330]:  * Creating symlink 
/var/lib/kd...z
  May 06 04:59:51 boslcp3g4 kdump-tools[2330]:  * /etc/default/kdump-tools: 
KD...g
  May 06 04:59:51 boslcp3g4 systemd[1]: Started Kernel crash dump capture 
service.
  Hint: Some lines were ellipsized, use -l to show in full.

  
  root@boslcp3g4:/kte/tools/setup.d# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-122-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: broken symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-122-generic
  current state:Not ready to kdump

  kexec command:
no kexec command recorded

  --> Still kdump state shows 'Not ready  to kdump'

  Regards,
  Indira

  > > > Thanks Breno! You point out that 4.4.0-113 is in use. Where did you 
notice
  > > > that? 

[Kernel-packages] [Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Committed

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

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

Bug description:
  == SRU Justification ==
  IBM is requesting these nine patches to be SRU'd to Bionic.  IBM found
  that the current Bionic kernel contains a problem related to qla2xxx
  driver which causes the following:

  [   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-20-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-20.21-generic 4.15.20)
  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

  We were able to get rid of this problem cherry picking some of the
  upstream patches. Do you think they might fit in the SRU criteria?

  The commit ids are below and they were easily cherry picked.

  eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug 
after firmware timeout
  6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin 
trigger from sending too many commands
  7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in 
qla2x00_async_iocb_timeout()
  045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call 
dma_free_coherent with IRQ disabled.
  1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session 
free in qlt_free_session_done
  d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session 
deletion by using work_lock
  Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: 
Fixup locking for session deletion')
  94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused 
argument from qlt_schedule_sess_for_dele?
  9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup 
for N2N


  == Regression Potential ==
  Medium.  There are nine patches in this pull request.  They are not specific 
to a
  paticular arch, but they are specific to qla2xxx.

  == Test Case ==
  A test kernel was built with these patches and tested by IBM.
  IBM states the test kernel resolved the bug.

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel

[Frank Heimes]

** Tags removed: triage-a
** Tags added: triage-g

-- 
You 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:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

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] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c000200e0b20fae0] c0c56ae4 unix_stream_sendmsg+0x264/0x5c0
  [c000200e0b20fbc0] c0

[Kernel-packages] [Bug 1762844] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into xmon after moving to 4.15.0-15.16 kernel

[Manoj Iyer]

Looks like the bionic-proposed kernel works for IBM, and so marking this
fix-committed.

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

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

** Changed in: ubuntu-power-systems
   Status: Incomplete => 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/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:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

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] c

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

[Brad Figg]

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

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

** Tags removed: block-proposed-precise

** Tags removed: block-proposed

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

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

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

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

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

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

[Kernel-packages] [Bug 1774190] Re: linux: 3.13.0-151.201 -proposed tracker

[Andy Whitcroft]

** Tags removed: kernel-block-proposed

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

Title:
  linux: 3.13.0-151.201 -proposed tracker

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

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

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

  backports: bug 1774191 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1774126] Re: linux-oem: 4.13.0-1030.33 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-xenial

** Tags removed: block-proposed

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

Title:
  linux-oem: 4.13.0-1030.33 -proposed tracker

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

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

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

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

[Kernel-packages] [Bug 1774190] Re: linux: 3.13.0-151.201 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-trusty

** Tags removed: block-proposed

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

Title:
  linux: 3.13.0-151.201 -proposed tracker

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

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

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

  backports: bug 1774191 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1772966] Re: linux-aws: 4.4.0-1061.70 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-xenial

** Tags removed: block-proposed

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

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

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

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

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

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

[Kernel-packages] [Bug 1772963] Re: linux-aws: 4.4.0-1023.23 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-trusty

** Tags removed: block-proposed

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

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

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

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

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

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

[Kernel-packages] [Bug 1774124] Re: linux: 4.13.0-45.50 -proposed tracker

[Andy Whitcroft]

** Tags removed: kernel-block-proposed

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

Title:
  linux: 4.13.0-45.50 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  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 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
  derivatives: bug 1774125 (linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1772960] Re: linux: 4.4.0-128.154 -proposed tracker

[Andy Whitcroft]

** Tags removed: kernel-block-proposed

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

Title:
  linux: 4.4.0-128.154 -proposed tracker

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

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

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

  backports: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws)
  derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 
1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1772960] Re: linux: 4.4.0-128.154 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-xenial

** Tags removed: block-proposed

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

Title:
  linux: 4.4.0-128.154 -proposed tracker

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

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

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

  backports: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws)
  derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 
1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1772964] Re: linux-kvm: 4.4.0-1027.32 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-xenial

** Tags removed: block-proposed

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

Title:
  linux-kvm: 4.4.0-1027.32 -proposed tracker

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

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

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

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

[Kernel-packages] [Bug 1774124] Re: linux: 4.13.0-45.50 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-artful

** Tags removed: block-proposed

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

Title:
  linux: 4.13.0-45.50 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  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 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
  derivatives: bug 1774125 (linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1770003] Re: qla2xxx: Fix page fault at kmem_cache_alloc_node()

[Manoj Iyer]

As per the kernel team, release from -proposed to -updates should happen
today. June 11th.

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

Title:
  qla2xxx: Fix page fault at kmem_cache_alloc_node()

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

Bug description:
  == SRU Justification ==
  IBM is requesting these nine patches to be SRU'd to Bionic.  IBM found
  that the current Bionic kernel contains a problem related to qla2xxx
  driver which causes the following:

  [   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-20-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-20.21-generic 4.15.20)
  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

  We were able to get rid of this problem cherry picking some of the
  upstream patches. Do you think they might fit in the SRU criteria?

  The commit ids are below and they were easily cherry picked.

  eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug 
after firmware timeout
  6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin 
trigger from sending too many commands
  7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in 
qla2x00_async_iocb_timeout()
  045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call 
dma_free_coherent with IRQ disabled.
  1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session 
free in qlt_free_session_done
  d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session 
deletion by using work_lock
  Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx: 
Fixup locking for session deletion')
  94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused 
argument from qlt_schedule_sess_for_dele?
  9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup 
for N2N


  == Regression Potential ==
  Medium.  There are nine patches in this pull request.  They are not specific 
to a
  paticular arch, but they are specific to qla2xxx.

  == Test Case ==
  A test kernel was built with these patches and tested by IBM.
  IBM states the test kernel resolved the bug.

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

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

[Kernel-packages] [Bug 1772927] Re: linux: 4.15.0-23.25 -proposed tracker

[Andy Whitcroft]

** Tags removed: kernel-block-proposed

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

Title:
  linux: 4.15.0-23.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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 1772935 (linux-hwe-edge), bug 1772940 (linux-azure), bug 
1772942 (linux-azure-edge)
  derivatives: bug 1772929 (linux-raspi2), bug 1772930 (linux-azure), bug 
1772931 (linux-aws), bug 1772932 (linux-kvm), bug 1772933 (linux-oem), bug 
1772934 (linux-gcp)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

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

[Manoj Iyer]

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

** Changed in: ubuntu-power-systems
   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/1773162

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1773964] Re: IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: In Progress => 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/1773964

Title:
  IPL: ppc64_cpu --frequency hang with INFO: rcu_sched detected stalls
  on CPUs/tasks on w34 and wsbmc016 with 920.1714.20170330n

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  == Comment: #0 - Application Cdeadmin <> - 2018-05-22 09:36:12 ==

  == Comment: #1 - Application Cdeadmin <> - 2018-05-22 09:36:14 ==
   State: Open by: swanman on 22 May 2018 09:17:33 

  Both w34 and wsbmc016 are stopped on this failure, where we get hung
  up on the following FFDC gathering step in the OS:

  #(CDT) 2018/05/22 05:07:19.398218 - 0.211662 - Issuing: OS Execute Command 
ppc64_cpu --frequency ignore_err=1
  #(CDT) 2018/05/22 05:07:19.437808 - 0.024108 - Issuing: ppc64_cpu --frequency 

  , and the last console output shows:
  # tail -200 /var/log/obmc-console.log 
  s this GP) idle=82a/140/0 softirq=2689/2689 fqs=241989 
  [13668.719850]  (detected by 3, t=3075620 jiffies, g=30289, c=30288, q=796881)
  [13732.630691] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13732.630727]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=242996 
  [13732.630757]  (detected by 3, t=3091597 jiffies, g=30289, c=30288, q=799822)
  [13795.649568] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13795.649597]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=243942 
  [13795.649631]  (detected by 7, t=3107351 jiffies, g=30289, c=30288, q=802916)
  [13860.140483] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13860.140516]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=244940 
  [13860.140557]  (detected by 3, t=3123473 jiffies, g=30289, c=30288, q=806646)
  [13924.731404] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13924.731438]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=245874 
  [13924.731484]  (detected by 3, t=3139620 jiffies, g=30289, c=30288, q=809909)
  [13988.642290] INFO: rcu_sched detected stalls on CPUs/tasks:
  [13988.642321]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=246892 
  [13988.642362]  (detected by 3, t=3155596 jiffies, g=30289, c=30288, q=813048)
  [14052.661176] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14052.661211]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=247857 
  [14052.661266]  (detected by 3, t=3171600 jiffies, g=30289, c=30288, q=816185)
  [14115.680024] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14115.680051]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=248819 
  [14115.680085]  (detected by 4, t=3187355 jiffies, g=30289, c=30288, q=819190)
  [14180.154911] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14180.154945]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=249833 
  [14180.154986]  (detected by 132, t=3203473 jiffies, g=30289, c=30288, 
q=822138)
  [14244.968067]I F: Ne talls onCPUs/tasks
  [14244669838]   75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=2[14244.669944]  (detected by 3, t=3219600 jiffies, 
g=30289, c=30288, q=825384)
  [14308.748680] Id detected stalls on CPUs/tasks:
  [14308.748719]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=251755 
  [14308.748755]  (detected by 3, t=3235620 jiffies, g=30289, c=30288, q=828445)
  [14333.081775] Watchdog CPU:132 Hard LOCKUP
  [14344.750295] Watchdog CPU:132 became unstuck
  [14372.735558] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14372.735587]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=252722 
  [14372.735611]  (detected by 6, t=3251616 jiffies, g=30289, c=30288, q=831375)
  [14435.910193] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14435.910219]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=253675 
  [14435.910253]  (detected by 3, t=3267409 jiffies, g=30289, c=30288, q=834375)
  [14500.167195] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14500.167230]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=254601 
  [14500.167273]  (detected by 134, t=3283473 jiffies, g=30289, c=30288, 
q=837600)
  [14564.664395] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14564.664427]  75-: (5904 ticks this GP) idle=82a/140/0 
softirq=2689/2689 fqs=255493 
  [14564.664470]  (detected by 3, t=3299596 jiffies, g=30289, c=30288, q=840539)
  [14628.665755] INFO: rcu_sched detected stalls on CPUs/tasks:
  [14628.665790]  75-: (5904 ticks this GP) idl

[Kernel-packages] [Bug 1772927] Re: linux: 4.15.0-23.25 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-bionic

** Tags removed: block-proposed

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

Title:
  linux: 4.15.0-23.25 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in 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 1772935 (linux-hwe-edge), bug 1772940 (linux-azure), bug 
1772942 (linux-azure-edge)
  derivatives: bug 1772929 (linux-raspi2), bug 1772930 (linux-azure), bug 
1772931 (linux-aws), bug 1772932 (linux-kvm), bug 1772933 (linux-oem), bug 
1772934 (linux-gcp)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-xenial

** Tags removed: block-proposed

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

Title:
  linux-gcp: 4.13.0-1019.23 -proposed tracker

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

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

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

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

[Kernel-packages] [Bug 1771780] Re: [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and stop5 idle states when all CORES are guarded

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: Triaged => In Progress

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

Title:
  [LTCTest][OPAL][OP920] cpupower idle-info is not listing stop4 and
  stop5 idle states when all CORES are guarded

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == SRU Justification ==
  During testing, IBM found that cpupower idle-info is not listing stop4 and
  stop5 idle states when all CORES are guarded.  A patch has been
  submitted upstream by IBM.  However, the patch has not landed in
  linux-next or mainline as of yet.  For that reason, this SRU request is
  being sent as a SAUCE patch request.

  
  == Fix ==
  UBUNTU: SAUCE: cpuidle/powernv : init all present cpus for deep states

  == Regression Potential ==
  Low.  Limited to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2018-05-16 04:07:59 ==
  ---Problem Description---
  cpupower idle-info is not listing stop4 and stop5 idle states when all CORES 
are guarded

  ---uname output---
  Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = P9

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
  Install a P9 Open Power Hardware with Ubuntu 18.04 OS.

  root@ltc-wspoon11:~# uname -a
  Linux ltc-wspoon11 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  root@ltc-wspoon11:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  Then guard an entire processor and also guard all the CORES in the
  processor 0 except for 1 single core.

  root@ltc-wspoon11:~# opal-gard list
   ID   | Error| Type   | Path
  ---
   0001 |  | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core0
   0002 |  | Manual | /Sys0/Node0/Proc0/EQ1/EX0/Core1
   0003 |  | Manual | /Sys0/Node0/Proc1
   0004 |  | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core1
   0005 |  | Manual | /Sys0/Node0/Proc0/EQ2/EX0/Core0
   0006 |  | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core0
   0007 |  | Manual | /Sys0/Node0/Proc0/EQ2/EX1/Core1
   0008 |  | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core0
   0009 |  | Manual | /Sys0/Node0/Proc0/EQ3/EX0/Core1
   000a |  | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core0
   000b |  | Manual | /Sys0/Node0/Proc0/EQ3/EX1/Core1
   000c |  | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core0
   000d |  | Manual | /Sys0/Node0/Proc0/EQ4/EX0/Core1
   000e |  | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core0
   000f |  | Manual | /Sys0/Node0/Proc0/EQ4/EX1/Core1
   0010 |  | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core0
   0011 |  | Manual | /Sys0/Node0/Proc0/EQ5/EX0/Core1
   0012 |  | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core0
   0013 |  | Manual | /Sys0/Node0/Proc0/EQ5/EX1/Core1
   0014 |  | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core0
   0015 |  | Manual | /Sys0/Node0/Proc0/EQ1/EX1/Core1
   0016 |  | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core1
   0017 |  | Manual | /Sys0/Node0/Proc0/EQ0/EX1/Core0
  ===

  Then execute the cpupower idle-info command to check the idle states
  being shown in the OS.

  root@ltc-wspoon11:~# cpupower idle-info
  CPUidle driver: powernv_idle
  CPUidle governor: menu
  analyzing CPU 0:

  Number of idle states: 7
  Available idle states: snooze stop0_lite stop0 stop1_lite stop1 stop2_lite 
stop2
  snooze:
  Flags/Description: snooze
  Latency: 0
  Usage: 774653
  Duration: 7698954
  stop0_lite:
  Flags/Description: stop0_lite
  Latency: 1
  Usage: 2751
  Duration: 11363825
  stop0:
  Flags/Description: stop0
  Latency: 2
  Usage: 2343
  Duration: 915084
  stop1_lite:
  Flags/Description: stop1_lite
  Latency: 5
  Usage: 20
  Duration: 1533
  stop1:
  Flags/Description:

[Kernel-packages] [Bug 1769927] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g4:ubuntu1604:'kdump-config show' shows Not ready to kdump even after doing kdump setup.

[Thadeu Lima de Souza Cascardo]

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

I have reported this and fixed it on bionic. Now, should have just been
made available on xenial and artful.

** This bug has been marked a duplicate of bug 1751328
   kdump-tools won't create initrd for previously installed kernels

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g4:ubuntu1604:'kdump-config
  show' shows Not ready to kdump even after doing kdump setup.

Status in The Ubuntu-power-systems project:
  Incomplete
Status in makedumpfile package in Ubuntu:
  Incomplete

Bug description:
  Problem Description:
  ===

  'kdump-config show' shows Not ready to kdump even after doing kdump
  setup on ubuntu160404 guest.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:1.20 & PNOR: 20180420 levels
  2. Installed p8 compat guest with ubutnu160404

  root@boslcp3g4:~# uname -a
  Linux boslcp3g4 4.4.0-122-generic #146-Ubuntu SMP Mon Apr 23 15:33:25 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3g4:~# uname -r
  4.4.0-122-generic

  3. Installed linux-crashdump crash dump utility.

  4. root@boslcp3g4:~# cat  /etc/default/grub.d/kexec-tools.cfg
  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4096M"
  root@boslcp3g4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.4.0-116-generic 
root=UUID=8be749b1-a5a8-4ab8-986c-ee4fcc61165e ro
  root@boslcp3g4:~#

  5. rebooted guest and checked kdump status.

  root@boslcp3g4:~# /etc/init.d/kdump-tools status
  ? kdump-tools.service - Kernel crash dump capture service
Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
Active: active (exited) since Sun 2018-05-06 04:18:37 EDT; 7min ago
   Process: 2317 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/SUCCESS)
  Main PID: 2317 (code=exited, status=0/SUCCESS)
 Tasks: 0
Memory: 0B
   CPU: 0
CGroup: /system.slice/kdump-tools.service

  May 06 04:18:37 boslcp3g4 systemd[1]: Starting Kernel crash dump capture 
service...
  May 06 04:18:37 boslcp3g4 kdump-tools[2317]: Starting kdump-tools:  * no 
crashkernel= parameter in the kernel cmdline
  May 06 04:18:37 boslcp3g4 systemd[1]: Started Kernel crash dump capture 
service.
  root@boslcp3g4:~# sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' 
/etc/default/kdump-tools

  
  4. kdump state

  root@boslcp3g4:~# kdump-config show
  * no crashkernel= parameter in the kernel cmdline
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
/var/lib/kdump/vmlinuz
  kdump initrd:
/var/lib/kdump/initrd.img
  current state:Not ready to kdump

  kexec command:
   no kexec command recorded

  --> It still says 'Not ready to kdump'

  --> Becuase of this state not able take dump when guest hangs/crashes

  > Tried again changing crashkernel parameter on ubuntu160404 guest- p8
  compat ,but still facing same issue

  root@boslcp3g4:/kte/tools/setup.d# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.4.0-122-generic 
root=UUID=8be749b1-a5a8-4ab8-986c-ee4fcc61165e ro ro splash quiet xmon=on 
crashkernel=512M crashkernel=4096M
  root@boslcp3g4:/kte/tools/setup.d#

  root@boslcp3g4:/kte/tools/setup.d# /etc/init.d/kdump-tools status
  ? kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
 Active: active (exited) since Sun 2018-05-06 04:59:51 EDT; 14min ago
   Main PID: 2330 (code=exited, status=0/SUCCESS)
  Tasks: 0
 Memory: 0B
CPU: 0
 CGroup: /system.slice/kdump-tools.service

  May 06 04:59:50 boslcp3g4 systemd[1]: Starting Kernel crash dump capture 
se.
  May 06 04:59:51 boslcp3g4 kdump-tools[2330]: Starting kdump-tools:  * 
Invali...g
  May 06 04:59:51 boslcp3g4 kdump-tools[2330]:  * Creating symlink 
/var/lib/kd...g
  May 06 04:59:51 boslcp3g4 kdump-tools[2330]:  * Invalid symlink : 
/var/lib/k...z
  May 06 04:59:51 boslcp3g4 kdump-tools[2330]:  * Creating symlink 
/var/lib/kd...z
  May 06 04:59:51 boslcp3g4 kdump-tools[2330]:  * /etc/default/kdump-tools: 
KD...g
  May 06 04:59:51 boslcp3g4 systemd[1]: Started Kernel crash dump capture 
service.
  Hint: Some lines were ellipsized, use -l to show in full.

  
  root@boslcp3g4:/kte/tools/setup.d# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-122-generic
  kdump initrd:
 /var/lib/kdump/initrd.img: broken symbolic link to 
/var/lib/kdump/initrd.img-4.4.0-122-generic
  current state:Not ready to kdump

  kexec command:
no kexec command recor

[Kernel-packages] [Bug 1751328] Re: kdump-tools won't create initrd for previously installed kernels

[Thadeu Lima de Souza Cascardo]

This should now be fixed on bionic, artful and xenial.

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

** Changed in: makedumpfile (Ubuntu)
   Status: Fix Released => In Progress

** Changed in: makedumpfile (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  kdump-tools won't create initrd for previously installed kernels

Status in makedumpfile package in Ubuntu:
  Fix Released

Bug description:
  When kdump-tools is installed, it creates an initrd for the running
  kernel. For kernels installed after that, the postinst part will be
  run and a initrd will be created as well. However, for kernels that
  are already installed, it won't create them.

  As an example, when the user is running 4.4.0-112-generic, but has
  4.13.0-32-generic installed, kdump-tools will create an initrd for
  4.4.0-112-generic. When the user later reboots into 4.13.0-32-generic,
  the initrd is not present, and kdump-tools won't load.

  Cascardo.

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

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

[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Released

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

Title:
  Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic
  -not syncing: Out of memory message when crash is triggered.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in kexec-tools package in Ubuntu:
  Fix Released
Status in kexec-tools source package in Xenial:
  Fix Released
Status in kexec-tools source package in Artful:
  Fix Released
Status in kexec-tools source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Latest kexec-tools is needed to load/kexec recent kernels. For older 
releases, like xenial, it's needed to support linux-hwe kernels.

  [Regression Potential]
  It might fail to load the GA kernels, like a 4.4 kernel on xenial.

  [Test case]
  Different kernels on different architectures have been tested.

  
  == Comment: #0 - INDIRA P. JOGA
  Problem Description:
  ===
  System hung with kernel panic Kernel panic - not syncing: Out of memory 
message when crash is triggered

  Steps to re-create:
  ==
  > Installed ubuntu1804 daily build on Witherspoon test system
  root@whip:~# uname -a
  Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@whip:~# uname -r
  4.13.0-17-generic

  > root@whip:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   507G2.0G504G 19M728M
503G
  Swap:  2.0G  0B2.0G

  > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the
  crash kernel parameter=4096M

  > Updated grub using update-grub command and reboot system.

  cat root@whip:~# cat /proc/cmdline
  root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
crashkernel=4096M

  > kdump status before triggering crash

  root@whip:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.13.0-17-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet 
irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz

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

  >  Enabled sysrq
  root@whip:~# sysctl -w kernel.sysrq=1
  kernel.sysrq = 1

  > Triggered crash and it hangs with kernel panic- OOM message as below

  root@whip:~# echo c > /proc/sysrq-trigger
  [   85.731415] sysrq: SysRq : Trigger a crash
  [   85.731472] Unable to handle kernel paging request for data at address 
0x
  [   85.731584] Faulting instruction address: 0xc078f588
  [   85.731670] Oops: Kernel access of bad area, sig: 11 [#1]
  [   85.731744] SMP NR_CPUS=2048
  [   85.731745] NUMA
  [   85.731790] PowerNV
  [   85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag 
sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag 
af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart 
cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd 
ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac 
scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace 
sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast 
i2c_algo_bit ttm drm_kms_helper mdio libcrc32c crc32c_vpmsum mlx5_core 
syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci mlxfw libahci nvme 
devlink nvme_core
  [   85.732704] CPU: 10 PID: 4316 Comm: bash Not tainted 4.13.0-17-generic 
#20-Ubuntu
  [   85.732764] task: c03fcb141700 task.stack: c03fc2374000
  [   85.732858] NIP: c078f588 LR: c07904b8 CTR: 
c078f560
  [   85.732977] REGS: c03fc23779f0 TRAP: 0300   Not tainted  
(4.13.0-17-generic)
  [   85.733066] MSR: 90009033 
  [   85.733075]   CR: 2842  XER: 2004
  [   85.733201] CFAR: c07904b4 DAR:  DSISR: 4200 
SOFTE: 1
  [   85.733201] GPR00: c07904b8 c03fc2377c70 c15f6000 
0063
  [   85.733201] GPR04: c03feedfade8 c03feee12068 90009033 
000a
  [   85.733201] GPR08: 0007 0001  
90001003
  [   85.733201] GPR12: c078f560 c7a66900 10180df8 
10189e30
  [   85.733201] GPR16: 10189ea8 10

[Kernel-packages] [Bug 1714485] Re: Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file system is xfs.

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: Triaged => Fix Committed

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

Title:
  Ubuntu 16.04: kdump fails with error "kdump-tools[1532]: /etc/init.d
  /kdump-tools: 26: [: -ne: unexpected operator" when / file system is
  xfs.

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Zesty:
  Won't Fix
Status in makedumpfile source package in Artful:
  Fix Committed
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2017-08-31 00:33:37 ==
  ---Problem Description---

  Ubuntu 16.04.03: kdump fails with error "kdump-tools[1532]:
  /etc/init.d/kdump-tools: 26: [: -ne: unexpected operator" when / file
  system is xfs.

  ---Steps to Reproduce---

  1. Install Ubuntu 16.04.03 with / as xfs.
  2. Configure kdump.
  3. trigger crash.

  Machine hangs after below log. Attaching console log.

  [  OK  ] Reached target Network is Online.
   Starting Kernel crash dump capture service...
   Starting iSCSI initiator daemon (iscsid)...
  [   12.263089] kdump-tools[1205]: /etc/init.d/kdump-tools: 26: [: -ne: 
unexpected operator
  [  OK  ] Started Kernel crash dump capture service.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).

  
  4. After manual reboot  /etc/default/kdump-tools is empty.

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

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

[Kernel-packages] [Bug 1763685] Re: Fix for flushing TM on coredump only if CPU has TM feature

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: Fix Committed => 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/1763685

Title:
  Fix for flushing TM on coredump only if CPU has TM feature

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  Problem description
  ==
  Fix for flushing TM on coredump only if CPU has TM feature

  ---Additional Hardware Info---
  POWER9/POWER8/compat mode 
   
  Machine Type = P9 baremetal + VM (POWER9, POWER8, Compat mode) 
   
  ---Steps to Reproduce---
   On POWER9 machines it's possible that TM is disabled for use by the VMs and 
if a coredump is generated in the VM it will crash since it will execute TM 
instructions when coredumping if a check is not present on the VM's kernel. 
Since POWER9 can run VM on P8 compatibility mode, it's necessary to patch all 
kernels that run on compat mode as well.
   
  Stack trace output:
   na
   
  Oops output:
   PID: 16438  TASK: c00272f515e0  CPU: 3   COMMAND: "vma05_vdso"
   #0 [c002711f7050] crash_kexec at c01a07e4
   #1 [c002711f7080] die at c0025278
   #2 [c002711f7120] _exception at c0025594
   #3 [c002711f72b0] program_check_exception at c0a0e1b8
   #4 [c002711f7330] program_check_common at c0006308
   Program Check [700] exception frame:
   R0:  R1:  c002711f7620R2:  c1274700
   R3:  c00272f51af0R4:  80010280b033R5:  
   R6:  0100R7:  R8:  
   R9:  0002R10: R11: 
   R12: c0010720R13: c7b81b00R14: 
   R15: R16: c002711f7db0R17: 00040006
   R18: c0002ab95800R19: 0100R20: 0001
   R21: 0002R22: c0bfc1c8R23: c002711f79b8
   R24: c0a30480R25: c0a30478R26: 0018
   R27: R28: c0002ab95800R29: 
   R30: 0100R31: c00272f515e0
   NIP: c005b10cMSR: 80010288b033OR3: c00108e0
   CTR: c0010720LR:  c00108e4XER: 2000
   CCR: 28002448MQ:  0001DAR: c00275599748
   DSISR: c00274092988 Syscall Result: 
   #5 [c002711f7620] tm_save_sprs at c005b10c
   [Link Register] [c002711f7620] vsr_get at c00108e4
   #6 [c002711f7770] fill_thread_core_info at c03d8b44
   #7 [c002711f7820] fill_note_info at c03d8e94
   #8 [c002711f78b0] elf_core_dump at c03d94d4
   #9 [c002711f7a90] do_coredump at c03dfcf4
  #10 [c002711f7c20] get_signal_to_deliver at c01061d4
  #11 [c002711f7d10] do_signal at c001beac
  #12 [c002711f7e00] do_notify_resume at c001c2cc
  #13 [c002711f7e30] ret_from_except_lite at c000a7b0
   System Call [c00] exception frame:
   R0:  00faR1:  3fffd0470f00R2:  3fffa8af7f00
   R3:  R4:  4036R5:  000b
   R6:  3fffd0471428R7:  1770R8:  4036
   R9:  R10: R11: 
   R12: R13: 3fffa8babb80R14: 
   R15: R16: R17: 
   R18: R19: R20: 
   R21: R22: R23: 
   R24: R25: R26: 
   R27: 3fffa8b9fbb8R28: 3fffa8baR29: 3fffa8b9f550
   R30: R31: 
   NIP: 3fffa8ad54c8MSR: 8000d033OR3: 4036
   CTR: LR:  155cXER: 
   CCR: 42000442MQ:  0001DAR: 3fffa89b2100
   DSISR: 4000 Syscall Result: 

  == Comment: #1 - Gustavo Bueno Romero  - 2018-04-12 
17:24:21 ==
  Dear maintainer, please cherry-pick the fix alreayd available upstream 
containing the additional check to avoid the issue here described. It must 
apply cleanly on stable kernels:

  "powerpc/tm: Flush TM only if CPU has TM feature":
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c1fa0768a8713b135848f78fd43ffc208d8ded70

  Please cherry-pick the pointed out fix and apply it to kernel:

  HWE 4.x
  HWE 4.13

  HWE-edge

[Kernel-packages] [Bug 1744173] Re: rfi-flush: Switch to new linear fallback flush

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1744173

Title:
  rfi-flush: Switch to new linear fallback flush

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Change flush method from "congruence-first with dependencies" to "linear with 
no dependencies", which increases flush performance by 8x on P8, and
  3x on P9. Measured with null syscall loop, which will have the flush area in 
the L2 cache.

  The flush also becomes simpler and more adaptable to different cache
  geometries.

  [Test Case]
  TBD.

  [Regression Potential]
  The risk is deemed low since the changes are confined to POWER only and the 
provided test kernels have been tested by IBM.

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

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

[Kernel-packages] [Bug 1746299] Re: update makedumpfile tool version to v1.6.3

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Released

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

Title:
  update makedumpfile tool version to v1.6.3

Status in The Ubuntu-power-systems project:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Artful:
  Fix Released
Status in makedumpfile source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  New upstream kernel versions, as those in linux-hwe package, require a newer 
makedumpfile to be supported. Otherwise, all copies fallback to copying the 
entire memory.

  [Test case]
  kdump-tools has been installed, system rebooted, then crash trigerred and 
verified that a small dump file was present on /var/crash/. Tested on amd64 and 
ppc64le.

  [Regression potential]
  Many other bug fixes have been included in the latest version of the package. 
The changes are supposed to fix these bugs, and have been tested as well. 
However, as the total of changes is not trivial, there is impact of regression 
that has been minimized by the tests done. Regression potential of not 
supporting older kernels has been tested with the kernels shipped on xenial and 
artful as well.


  
  

  == Comment: #0 - Hari Krishna Bathini  - 2018-01-30 
10:46:53 ==
  ---Problem Description---
  update makedumpfile to latest version v1.6.3 that officially supports
  up to kernel version 4.14.8. Since makedumpfile is inherently backward 
compatible,
  this would not break existing functionality..

  Contact Information = hbath...@in.ibm.com

  ---uname output---
  na

  Machine Type = na

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   makedumpfile reports ""The kernel version is not supported" while generating 
vmcore
  Also, there is a possibility of bogus address translations in makedumpfile 
tool with
  missing upstream patches. Can't be so sure without an exhaustive testing. 
Instead,
  it would be a good idea to go with the version which officially supports the 
kernel
  version in question.

  Userspace tool common name: makedumpfile

  The userspace tool has the following bit modes: 64-bit

  Userspace rpm: makedumpfile

  Userspace tool obtained from project website:  na

  *Additional Instructions for hbath...@in.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Hari Krishna Bathini  - 2018-01-30 
10:49:13 ==
  With kernel version updated to 4.13.0, please update makedumpfile tool
  version to 1.6.3 which officially supports up to kernel version 4.14.8 [1].

  Thanks
  Hari

  [1]
  http://lists.infradead.org/pipermail/kexec/2018-January/019853.html

  This needs to be tagged for both 16.04.4 & 18.04 releases

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

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

[Kernel-packages] [Bug 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart

[Joseph Salisbury]

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

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

Title:
  kdump fails to take dump with smt set to 2, hmc dumpstart

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in makedumpfile source package in Artful:
  New

Bug description:
  --Problem Description---
  kdump fails to take dump with smt set to 2, hmc dumpstart

  ---Issue observed---
  [0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
  [0.004118] SMP NR_CPUS=2048 
  [0.004120] NUMA 
  [0.004125] pSeries
  [0.004132] Modules linked in:
  [0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic 
#13-Ubuntu
  [0.004153] task: c00046715900 task.stack: c00046134000
  [0.004162] NIP: c0006468 LR: c801764c CTR: 
006cdc70
  [0.004173] REGS: c00047fe3ce0 TRAP: 0700   Not tainted  
(4.13.0-12-generic)
  [0.004181] MSR: 80081031 
  [0.004193]   CR: 8804  XER: 2003
  [0.004204] CFAR: c0006454 SOFTE: 0 
  [0.004204] GPR00: c801764c c00047fe3f60 c95e3000 
 
  [0.004204] GPR04: 0001 0002  
ffdf 
  [0.004204] GPR08:  2804 0002 
0002 
  [0.004204] GPR12:  cfff c00046137f90 
0b5452d8 
  [0.004204] GPR16: fffd 089ffd10 0136 
0b55d378 
  [0.004204] GPR20: 0060 1eca 0a6c 
0007 
  [0.004204] GPR24:   c9621ed0 
 
  [0.004204] GPR28:  c00046134000 c00046137c80 
c9105df8 
  [0.004328] NIP [c0006468] 0xc0006468
  [0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
  [0.004345] Call Trace:
  [0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0 
(unreliable)
  [0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
  [0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
  [0.004393] [c00046137c10] [c8008ac4] 
hardware_interrupt_common+0x114/0x120
  [0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
  [0.004409] LR = arch_local_irq_restore+0x40/0x90
  [0.004423] [c00046137f00] [0005] 0x5 (unreliable)
  [0.004436] [c00046137f20] [c8049824] 
start_secondary+0x324/0x350
  [0.004450] [c00046137f90] [c800aa6c] 
start_secondary_prolog+0x10/0x14
  [0.004460] Instruction dump:
  [0.004467]        
 
  [0.004484]        
 
  [0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
  [0.004512] 
  [0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
  [0.004525] SMP NR_CPUS=2048 
  [0.004526] NUMA 
  [0.004532] pSeries
  [0.004540] Modules linked in:
  [0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G  D 
4.13.0-12-generic #13-Ubuntu
  [0.004561] task: c9579f00 task.stack: c95dc000
  [0.004569] NIP: c0006460 LR: c80b6e80 CTR: 

  [0.004580] REGS: c95dfb20 TRAP: 0700   Tainted: G  D  
(4.13.0-12-generic)
  [0.004589] MSR: 80081031 
  [0.004599]   CR: 22002228  XER: 2004
  [0.004611] CFAR: c000493c SOFTE: 0 
  [0.004611] GPR00:  c95dfda0 c95e3000 
 
  [0.004611] GPR04:    
 
  [0.004611] GPR08:  22002228 7fff 
0008 
  [0.004611] GPR12:  cfff0a80 c00c7e137f90 
09980600 
  [0.004611] GPR16: 1ec7 0001  
 
  [0.004611] GPR20:    
0007 
  [0.004611] GPR24: 0008 c800 0800 
 
  [0.004611] GPR28:  0008 c9621ed0 
c9622354 
  [0.004729] NIP [c0006460] 0xc0006460
  [0.004739] LR [c80b6e80] pseries_lpar_idle+0x30/0x50
  [0.004746] Call Trace:
  [0.004756] [c95dfda0] [c95dfe90] 
init_thread_union+0x3e90/0x4000 (unreliable)
  [0.004771] [c95dfe00] [c801e314] arch_cpu_idle+0x54/0x160
  [  

[Kernel-packages] [Bug 1772932] Re: linux-kvm: 4.15.0-1011.11 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-bionic

** Tags removed: block-proposed

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

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

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

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

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

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

[Kernel-packages] [Bug 1772931] Re: linux-aws: 4.15.0-1010.10 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-bionic

** Tags removed: block-proposed

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

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

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

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

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

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

[Kernel-packages] [Bug 1772934] Re: linux-gcp: 4.15.0-1009.9 -proposed tracker

[Brad Figg]

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

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

** Tags removed: block-proposed-bionic

** Tags removed: block-proposed

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

Title:
  linux-gcp: 4.15.0-1009.9 -proposed tracker

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

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

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

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

[Kernel-packages] [Bug 1731768] Re: Random desktop freeze

[Van Stokes, Jr.]

Problem still persists with 18.04 running nvidia-396 drivers.
More details here 
https://askubuntu.com/questions/1030466/ubuntu-18-04-keeps-freezing-nvidia

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

Title:
  Random desktop freeze

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

Bug description:
  Since the last update (384.90-0ubuntu0.16.04.1 to
  384.90-0ubuntu0.16.04.2) I experience random desktop freezes. To
  recover I have to switch to tty1 and do a restart of the lightdm
  service. This has the consequence of closing all running applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-384 384.90-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 12 16:13:56 2017
  InstallationDate: Installed on 2016-11-19 (358 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nvidia-graphics-drivers-384
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart

[Manoj Iyer]

** Changed in: makedumpfile (Ubuntu Artful)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

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

** Changed in: ubuntu-power-systems
   Status: New => In Progress

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

Title:
  kdump fails to take dump with smt set to 2, hmc dumpstart

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in makedumpfile source package in Artful:
  New

Bug description:
  --Problem Description---
  kdump fails to take dump with smt set to 2, hmc dumpstart

  ---Issue observed---
  [0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
  [0.004118] SMP NR_CPUS=2048 
  [0.004120] NUMA 
  [0.004125] pSeries
  [0.004132] Modules linked in:
  [0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic 
#13-Ubuntu
  [0.004153] task: c00046715900 task.stack: c00046134000
  [0.004162] NIP: c0006468 LR: c801764c CTR: 
006cdc70
  [0.004173] REGS: c00047fe3ce0 TRAP: 0700   Not tainted  
(4.13.0-12-generic)
  [0.004181] MSR: 80081031 
  [0.004193]   CR: 8804  XER: 2003
  [0.004204] CFAR: c0006454 SOFTE: 0 
  [0.004204] GPR00: c801764c c00047fe3f60 c95e3000 
 
  [0.004204] GPR04: 0001 0002  
ffdf 
  [0.004204] GPR08:  2804 0002 
0002 
  [0.004204] GPR12:  cfff c00046137f90 
0b5452d8 
  [0.004204] GPR16: fffd 089ffd10 0136 
0b55d378 
  [0.004204] GPR20: 0060 1eca 0a6c 
0007 
  [0.004204] GPR24:   c9621ed0 
 
  [0.004204] GPR28:  c00046134000 c00046137c80 
c9105df8 
  [0.004328] NIP [c0006468] 0xc0006468
  [0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
  [0.004345] Call Trace:
  [0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0 
(unreliable)
  [0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
  [0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
  [0.004393] [c00046137c10] [c8008ac4] 
hardware_interrupt_common+0x114/0x120
  [0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
  [0.004409] LR = arch_local_irq_restore+0x40/0x90
  [0.004423] [c00046137f00] [0005] 0x5 (unreliable)
  [0.004436] [c00046137f20] [c8049824] 
start_secondary+0x324/0x350
  [0.004450] [c00046137f90] [c800aa6c] 
start_secondary_prolog+0x10/0x14
  [0.004460] Instruction dump:
  [0.004467]        
 
  [0.004484]        
 
  [0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
  [0.004512] 
  [0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
  [0.004525] SMP NR_CPUS=2048 
  [0.004526] NUMA 
  [0.004532] pSeries
  [0.004540] Modules linked in:
  [0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G  D 
4.13.0-12-generic #13-Ubuntu
  [0.004561] task: c9579f00 task.stack: c95dc000
  [0.004569] NIP: c0006460 LR: c80b6e80 CTR: 

  [0.004580] REGS: c95dfb20 TRAP: 0700   Tainted: G  D  
(4.13.0-12-generic)
  [0.004589] MSR: 80081031 
  [0.004599]   CR: 22002228  XER: 2004
  [0.004611] CFAR: c000493c SOFTE: 0 
  [0.004611] GPR00:  c95dfda0 c95e3000 
 
  [0.004611] GPR04:    
 
  [0.004611] GPR08:  22002228 7fff 
0008 
  [0.004611] GPR12:  cfff0a80 c00c7e137f90 
09980600 
  [0.004611] GPR16: 1ec7 0001  
 
  [0.004611] GPR20:    
0007 
  [0.004611] GPR24: 0008 c800 0800 
 
  [0.004611] GPR28:  000

[Kernel-packages] [Bug 1771344] Re: Fix enabling bridge MMIO windows

[Manoj Iyer]

I do not see this patch in bionic kernel, moving the status back to in
progress.

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

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

Title:
  Fix enabling bridge MMIO windows

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  == SRU Justification ==
  IBM is requesting this patch in Bionic and Artful to fix a regression.  The
  regression was introduced in v3.11-rc1.  The patch fixes enabling bridge
  MMIO windows.  Commit 13a83eac373c was also cc'd to upstream stable, and
  has already landed in Xenial via upstream stable updates.

  == Fix ==
  13a83eac373c ("powerpc/eeh: Fix enabling bridge MMIO windows")

  == Regression Potential ==
  Low.  Limited to powerpc and fixes a current regression.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  == Comment: #0 - Breno Leitao 
  On boot we save the configuration space of PCIe bridges. We do this so
  when we get an EEH event and everything gets reset that we can restore
  them.

  Unfortunately we save this state before we've enabled the MMIO space
  on the bridges. Hence if we have to reset the bridge when we come back
  MMIO is not enabled and we end up taking an PE freeze when the driver
  starts accessing again.

  This patch forces the memory/MMIO and bus mastering on when restoring
  bridges on EEH. Ideally we'd do this correctly by saving the
  configuration space writes later, but that will have to come later in
  a larger EEH rewrite. For now we have this simple fix.

  The original bug can be triggered on a boston machine by doing:
   echo 0x8000 > 
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
  On boston, this PHB has a PCIe switch on it.  Without this patch,
  you'll see two EEH events, 1 expected and 1 the failure we are fixing
  here. The second EEH event causes the anything under the PHB to
  disappear (i.e. the i40e eth).

  With this patch, only 1 EEH event occurs and devices properly recover.

  This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should
  be part of Ubuntu 18.04 kernel.

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

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

[Kernel-packages] [Bug 1771844] Re: powerpc/livepatch: Implement reliable stack tracing for the consistency model

[Manoj Iyer]

** Changed in: ubuntu-power-systems
   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/1771844

Title:
  powerpc/livepatch: Implement reliable stack tracing for the
  consistency model

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  In Progress

Bug description:
  == SRU Justification ==
  Livepatch has a consistency model which is a hybrid of kGraft and kpatch:
  it uses kGraft's per-task consistency and syscall barrier switching
  combined with kpatch's stack trace switching. The current approach is
  stack checking of sleeping tasks. If no affected functions are on the
  stack of a given task, the task is patched. In most cases this will patch
  most or all of the tasks on the first try. Otherwise, it'll keep trying
  periodically. This patch implements the reliable stack tracing for
  consistency model a.k.a HAVE_RELIABLE_STACKTRACE.

  This will help in switching livepatching implementation to basic per-task
  consistency model. It is the foundation, which will help us enable
  security patches changing function or data semantics. This is the biggest
  remaining piece needed on ppc64le to make livepatch more generally useful.

  == Fix ==
  df78d3f61480 ("powerpc/livepatch: Implement reliable stack tracing for the 
consistency model")

  == Regression Potential ==
  Low. Limited to powerpc.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=df78d3f6148092d33a9a24c7a9cfac

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

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

[Kernel-packages] [Bug 1776211] Re: kdump fails to take dump with smt set to 2, hmc dumpstart

[Joseph Salisbury]

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

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

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

Title:
  kdump fails to take dump with smt set to 2, hmc dumpstart

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in makedumpfile source package in Artful:
  New

Bug description:
  --Problem Description---
  kdump fails to take dump with smt set to 2, hmc dumpstart

  ---Issue observed---
  [0.004111] Oops: Exception in kernel mode, sig: 4 [#1]
  [0.004118] SMP NR_CPUS=2048 
  [0.004120] NUMA 
  [0.004125] pSeries
  [0.004132] Modules linked in:
  [0.004142] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-12-generic 
#13-Ubuntu
  [0.004153] task: c00046715900 task.stack: c00046134000
  [0.004162] NIP: c0006468 LR: c801764c CTR: 
006cdc70
  [0.004173] REGS: c00047fe3ce0 TRAP: 0700   Not tainted  
(4.13.0-12-generic)
  [0.004181] MSR: 80081031 
  [0.004193]   CR: 8804  XER: 2003
  [0.004204] CFAR: c0006454 SOFTE: 0 
  [0.004204] GPR00: c801764c c00047fe3f60 c95e3000 
 
  [0.004204] GPR04: 0001 0002  
ffdf 
  [0.004204] GPR08:  2804 0002 
0002 
  [0.004204] GPR12:  cfff c00046137f90 
0b5452d8 
  [0.004204] GPR16: fffd 089ffd10 0136 
0b55d378 
  [0.004204] GPR20: 0060 1eca 0a6c 
0007 
  [0.004204] GPR24:   c9621ed0 
 
  [0.004204] GPR28:  c00046134000 c00046137c80 
c9105df8 
  [0.004328] NIP [c0006468] 0xc0006468
  [0.004338] LR [c801764c] __do_irq+0x4c/0x1c0
  [0.004345] Call Trace:
  [0.004354] [c00047fe3f60] [c801764c] __do_irq+0x4c/0x1c0 
(unreliable)
  [0.004368] [c00047fe3f90] [c802ab70] call_do_irq+0x14/0x24
  [0.004380] [c00046137bc0] [c801785c] do_IRQ+0x9c/0x130
  [0.004393] [c00046137c10] [c8008ac4] 
hardware_interrupt_common+0x114/0x120
  [0.004409] --- interrupt: 501 at arch_local_irq_restore+0x5c/0x90
  [0.004409] LR = arch_local_irq_restore+0x40/0x90
  [0.004423] [c00046137f00] [0005] 0x5 (unreliable)
  [0.004436] [c00046137f20] [c8049824] 
start_secondary+0x324/0x350
  [0.004450] [c00046137f90] [c800aa6c] 
start_secondary_prolog+0x10/0x14
  [0.004460] Instruction dump:
  [0.004467]        
 
  [0.004484]        
 
  [0.004506] ---[ end trace 3e5a2a9047ef3cd0 ]---
  [0.004512] 
  [0.004518] Oops: Exception in kernel mode, sig: 4 [#2]
  [0.004525] SMP NR_CPUS=2048 
  [0.004526] NUMA 
  [0.004532] pSeries
  [0.004540] Modules linked in:
  [0.004550] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G  D 
4.13.0-12-generic #13-Ubuntu
  [0.004561] task: c9579f00 task.stack: c95dc000
  [0.004569] NIP: c0006460 LR: c80b6e80 CTR: 

  [0.004580] REGS: c95dfb20 TRAP: 0700   Tainted: G  D  
(4.13.0-12-generic)
  [0.004589] MSR: 80081031 
  [0.004599]   CR: 22002228  XER: 2004
  [0.004611] CFAR: c000493c SOFTE: 0 
  [0.004611] GPR00:  c95dfda0 c95e3000 
 
  [0.004611] GPR04:    
 
  [0.004611] GPR08:  22002228 7fff 
0008 
  [0.004611] GPR12:  cfff0a80 c00c7e137f90 
09980600 
  [0.004611] GPR16: 1ec7 0001  
 
  [0.004611] GPR20:    
0007 
  [0.004611] GPR24: 0008 c800 0800 
 
  [0.004611] GPR28:  0008 c9621ed0 
c9622354 
  [0.004729] NIP [c0006460] 0xc0006460
  [0.004739] LR [c80b6e80] pseries_lpar_idle+0x30/0x50
  [0.004746] Call Trace:
  [0.004756] [c95dfda0] [c95dfe90] 
init_thread_union+0x3e90/0x4000 (unreliable)
  [0.0047

[Kernel-packages] [Bug 1775816] Re: Hang at the 3rd cycle when running S4 stress script on Ubuntu core system.

[Alex Kaluzhny]

This bug is a duplicate of private bug 
https://bugs.launchpad.net/plano/+bug/1776129.
We agreed with Jack_Le to track its resolution in #1776129.

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

Title:
  Hang at the 3rd cycle when running S4 stress script on Ubuntu core
  system.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Image info: Caracalla 16.04-1.35 rev 49/ Caracalla-kernel 4.4.0-2019.20-1 Rev 
84/ Core 16-2.32.8 Rev 4650
  System info: Ubuntu core
  Description of the issue: Hang at the 3rd cycle when running S4 stress script.
  Expected result: Enter S4 and wake up successfully when running S4 stress 
script. 
  Actual result: Hang at the 3rd cycle, and Green LED always ON. 
  Isolation: Manual type “rtcwake -s 120 -m disk” in the terminal, then at the 
third cycle input the command, the SUT hang.

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

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

[Kernel-packages] [Bug 1774124] Re: linux: 4.13.0-45.50 -proposed tracker

[Łukasz Zemczak]

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

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

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

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

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

Title:
  linux: 4.13.0-45.50 -proposed tracker

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

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

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

  backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 
(linux-hwe)
  derivatives: bug 1774125 (linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1774190] Re: linux: 3.13.0-151.201 -proposed tracker

[Łukasz Zemczak]

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

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

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

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

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

Title:
  linux: 3.13.0-151.201 -proposed tracker

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

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

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

  backports: bug 1774191 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1774190] Re: linux: 3.13.0-151.201 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-151.201

---
linux (3.13.0-151.201) trusty; urgency=medium

  * linux: 3.13.0-151.201 -proposed tracker (LP: #1774190)

  * CVE-2018-3639 (x86)
- SAUCE: Set generic SSBD feature for Intel cpus
- KVM: vmx: fix MPX detection
- KVM: x86: Fix MSR_IA32_BNDCFGS in msrs_to_save
- x86/cpu: Add CLZERO detection

  * Trusty cannot load microcode for family 17h AMD processors (LP: #1774082)
- x86/microcode/AMD: Add support for fam17h microcode loading

linux (3.13.0-150.200) trusty; urgency=medium

  * linux: 3.13.0-150.200 -proposed tracker (LP: #1772970)

  * CVE-2018-3639 (x86)
- x86/cpu: Make alternative_msr_write work for 32-bit code
- x86/cpu/AMD: Fix erratum 1076 (CPB bit)
- x86/bugs: Fix the parameters alignment and missing void
- KVM: SVM: Move spec control call after restore of GS
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
- x86/cpufeatures: Disentangle SSBD enumeration
- x86/cpufeatures: Add FEATURE_ZEN
- x86/speculation: Handle HT correctly on AMD
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
- x86/speculation: Add virtualized speculative store bypass disable support
- SAUCE: x86/cpu: Rename x86_amd_ssbd_enable
- x86/speculation: Rework speculative_store_bypass_update()
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
- x86/bugs: Expose x86_spec_ctrl_base directly
- x86/bugs: Remove x86_spec_ctrl_set()
- x86/bugs: Rework spec_ctrl base and mask logic
- x86/speculation, KVM: Implement support for VIRT_SPEC_CTRL/LS_CFG
- KVM: x86: introduce num_emulated_msrs
- KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
- x86/bugs: Rename SSBD_NO to SSB_NO
- KVM: VMX: Expose SSBD properly to guests.

  * CVE-2018-7492
- rds: Fix NULL pointer dereference in __rds_rdma_map

  * CVE-2017-0627
- media: uvcvideo: Prevent heap overflow when accessing mapped controls

  * CVE-2018-8781
- drm: udl: Properly check framebuffer mmap offsets

  * CVE-2018-1068
- netfilter: ebtables: CONFIG_COMPAT: don't trust userland offsets

 -- Stefan Bader   Wed, 30 May 2018 16:02:01
+0200

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-0627

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-1068

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3639

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-7492

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-8781

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

Title:
  linux: 3.13.0-151.201 -proposed tracker

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

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

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

  backports: bug 1774191 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1772960] Re: linux: 4.4.0-128.154 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-128.154

---
linux (4.4.0-128.154) xenial; urgency=medium

  * linux: 4.4.0-128.154 -proposed tracker (LP: #1772960)

  * CVE-2018-3639 (x86)
- x86/cpu: Make alternative_msr_write work for 32-bit code
- x86/bugs: Fix the parameters alignment and missing void
- KVM: SVM: Move spec control call after restore of GS
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
- x86/cpufeatures: Disentangle SSBD enumeration
- x86/cpu/AMD: Fix erratum 1076 (CPB bit)
- x86/cpufeatures: Add FEATURE_ZEN
- x86/speculation: Handle HT correctly on AMD
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
- x86/speculation: Add virtualized speculative store bypass disable support
- x86/speculation: Rework speculative_store_bypass_update()
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
- x86/bugs: Expose x86_spec_ctrl_base directly
- x86/bugs: Remove x86_spec_ctrl_set()
- x86/bugs: Rework spec_ctrl base and mask logic
- x86/speculation, KVM: Implement support for VIRT_SPEC_CTRL/LS_CFG
- KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
- x86/bugs: Rename SSBD_NO to SSB_NO
- KVM: VMX: Expose SSBD properly to guests.

  * [i915_bpo] Fix flickering issue after panel change (LP: #1770565)
- drm/i915: Fix iboost setting for DDI with 4 lanes on SKL
- drm/i915: Name the "iboost bit"
- drm/i915: Program iboost settings for HDMI/DVI on SKL
- drm/i915: Move bxt_ddi_vswing_sequence() call into intel_ddi_pre_enable()
  for HDMI
- drm/i915: Explicitly use ddi buf trans entry 9 for hdmi
- drm/i915: Split DP/eDP/FDI and HDMI/DVI DDI buffer programming apart
- drm/i915: Get the iboost setting based on the port type
- drm/i915: Simplify intel_ddi_get_encoder_port()
- drm/i915: Fix iboost setting for SKL Y/U DP DDI buffer translation entry 2
- drm/i915: KBL - Recommended buffer translation programming for DisplayPort
- drm/i915: Ignore OpRegion panel type except on select machines

  * [SRU][Bionic/Artful] fix false positives in W+X checking (LP: #1769696)
- init: fix false positives in W+X checking

  * [Ubuntu 16.04] kernel: fix rwlock implementation (LP: #1761674)
- SAUCE: (no-up) s390: fix rwlock implementation

  * linux < 4.11: unable to use netfilter logging from non-init namespaces
(LP: #1766573)
- netfilter: allow logging from non-init namespaces

  * [LTC Test] Ubuntu 18.04:  tm_sigreturn failed on P8 compat mode 16.04.04
guest (LP: #1771439)
- powerpc: signals: Discard transaction state from signal frames

  * QCA9377 requires more IRAM banks for its new firmware (LP: #1748345)
- ath10k: update the IRAM bank number for QCA9377

  * i915/kbl_dmc_ver1.bin failed with error -2 package 1.157.17 kernel
4.4.0-116-generic (LP: #1752536)
- ubuntu: i915_bpo - Add MODULE_FIRMWARE for Geminilake's DMC

  * Xenial update to 4.4.131 stable release (LP: #1768825)
- ext4: prevent right-shifting extents beyond EXT_MAX_BLOCKS
- ext4: set h_journal if there is a failure starting a reserved handle
- ext4: add validity checks for bitmap block numbers
- ext4: fix bitmap position validation
- usbip: usbip_host: fix to hold parent lock for device_attach() calls
- usbip: vhci_hcd: Fix usb device and sockfd leaks
- USB: serial: simple: add libtransistor console
- USB: serial: ftdi_sio: use jtag quirk for Arrow USB Blaster
- USB: serial: cp210x: add ID for NI USB serial console
- usb: core: Add quirk for HP v222w 16GB Mini
- USB: Increment wakeup count on remote wakeup.
- ALSA: usb-audio: Skip broken EU on Dell dock USB-audio
- virtio: add ability to iterate over vqs
- virtio_console: free buffers after reset
- drm/virtio: fix vq wait_event condition
- tty: Don't call panic() at tty_ldisc_init()
- tty: n_gsm: Fix long delays with control frame timeouts in ADM mode
- tty: n_gsm: Fix DLCI handling for ADM mode if debug & 2 is not set
- tty: Use __GFP_NOFAIL for tty_ldisc_get()
- ALSA: core: Report audio_tstamp in snd_pcm_sync_ptr
- ALSA: seq: oss: Fix unbalanced use lock for synth MIDI device
- ALSA: hda/realtek - Add some fixes for ALC233
- mtd: cfi: cmdset_0001: Do not allow read/write to suspend erase block.
- mtd: cfi: cmdset_0001: Workaround Micron Erase suspend bug.
- mtd: cfi: cmdset_0002: Do not allow read/write to suspend erase block.
- kobject: don't use WARN for registration failures
- scsi: sd: Defer spinning up drive while SANITIZE is in progress
- ARM: amba: Make driver_override output consistent with other buses
- ARM: amba: Fix race condition with driver_override
- ARM: amba: Don't read past the end of sysfs "driver_override" buffer
- ASoC: fsl_esai: Fix divisor calculation failure at lower ratio
- libceph: va

[Kernel-packages] [Bug 1774082] Re: Trusty cannot load microcode for family 17h AMD processors

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.13.0-151.201

---
linux (3.13.0-151.201) trusty; urgency=medium

  * linux: 3.13.0-151.201 -proposed tracker (LP: #1774190)

  * CVE-2018-3639 (x86)
- SAUCE: Set generic SSBD feature for Intel cpus
- KVM: vmx: fix MPX detection
- KVM: x86: Fix MSR_IA32_BNDCFGS in msrs_to_save
- x86/cpu: Add CLZERO detection

  * Trusty cannot load microcode for family 17h AMD processors (LP: #1774082)
- x86/microcode/AMD: Add support for fam17h microcode loading

linux (3.13.0-150.200) trusty; urgency=medium

  * linux: 3.13.0-150.200 -proposed tracker (LP: #1772970)

  * CVE-2018-3639 (x86)
- x86/cpu: Make alternative_msr_write work for 32-bit code
- x86/cpu/AMD: Fix erratum 1076 (CPB bit)
- x86/bugs: Fix the parameters alignment and missing void
- KVM: SVM: Move spec control call after restore of GS
- x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
- x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
- x86/cpufeatures: Disentangle SSBD enumeration
- x86/cpufeatures: Add FEATURE_ZEN
- x86/speculation: Handle HT correctly on AMD
- x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
- x86/speculation: Add virtualized speculative store bypass disable support
- SAUCE: x86/cpu: Rename x86_amd_ssbd_enable
- x86/speculation: Rework speculative_store_bypass_update()
- x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
- x86/bugs: Expose x86_spec_ctrl_base directly
- x86/bugs: Remove x86_spec_ctrl_set()
- x86/bugs: Rework spec_ctrl base and mask logic
- x86/speculation, KVM: Implement support for VIRT_SPEC_CTRL/LS_CFG
- KVM: x86: introduce num_emulated_msrs
- KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
- x86/bugs: Rename SSBD_NO to SSB_NO
- KVM: VMX: Expose SSBD properly to guests.

  * CVE-2018-7492
- rds: Fix NULL pointer dereference in __rds_rdma_map

  * CVE-2017-0627
- media: uvcvideo: Prevent heap overflow when accessing mapped controls

  * CVE-2018-8781
- drm: udl: Properly check framebuffer mmap offsets

  * CVE-2018-1068
- netfilter: ebtables: CONFIG_COMPAT: don't trust userland offsets

 -- Stefan Bader   Wed, 30 May 2018 16:02:01
+0200

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-0627

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-1068

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3639

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-7492

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-8781

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

Title:
  Trusty cannot load microcode for family 17h AMD processors

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

Bug description:
  [Impact]

  AMD has recently updated the microcode in the linux-firmware tree for
  family 17h processors to address Spectre variant 2. The Trusty 3.13
  kernel cannot load the microcode because it is missing a backport of
  upstream patch f4e9b7af0cd58dd039a0fb2cd67d57cea4889abf which leaves
  AMD machines vulnerable.

  [Test Case (option 1)]

  Test must be done on a 17h family processor:

  1) Take note of the microcode version before applying updated
  microcode:

   $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version
   0x8001227

  2) Get updated amd64-microcode package from the Ubuntu Security Team.
  Install it and reboot machine.

  3) Verify that the microcode version has changed.

  [Test Case (option 2)]

  Alternate test case (useful in the situation that the test system is
  already running the latest microcode revision due to a BIOS update):

  1) Fetch the latest 17h family microcode revision from here (you may
  want to verify the signature):

    https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/tree/amd-ucode/microcode_amd_fam17h.bin

  2) Move it into /lib/firmware/amd-ucode/

  3) Force a microcode reload:

    $ echo 1 | sudo tee /sys/devices/system/cpu/microcode/reload

  4) Verify that the following error message is *not* in your syslog:

  May 30 04:22:55 lodygin kernel: [  388.290105] microcode: patch size mismatch
  May 30 04:22:55 lodygin kernel: [  388.290149] microcode: Patch-ID 
0x08001227: size mismatch.

  [Regression Potential]

  The regression potential to the kernel revolves around the fact that
  the IBRS/IBPB implementation in the 3.13 kernel may not have been put
  through its paces yet due to a lack of available microcode updates.
  There could be a latent bug present that is uncovered.

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