Here is what we know so far,

Disco Kernel 5.0.0-38 , reboots just fine on S390x Zvm and KVM. 
This appears to only affect the lpar. 

The Lpar reboots just fine if we boot the previous cycles kernel and
issue a "$sudo reboot" from the command lines.

Looking at the commits for disco, it could be one of these causing this.

b3ff8122bafa s390/idle: fix cpu idle time calculation
98f8642e75cd s390/cmm: fix information leak in cmm_timeout_handler()
72006d0879eb s390/uaccess: avoid (false positive) compiler warnings
fced71a08bdf s390/mm: fix -Wunused-but-set-variable warnings

Will try to isolate and see if reverting these makes any difference in
behavior.

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

** Changed in: linux (Ubuntu)
     Assignee: (unassigned) => Sean Feole (sfeole)

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

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

Title:
  Unable to reboot Disco on Ubuntu LPAR s390x (5.0.0-38)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With the proposed Disco kernel (5.0.0-38)
  I can't reboot the s390x LPAR node s2lp4

  When I tried to reboot the system it will render the system into a
  "Not operating" status.

  I tried to watch the output from the Integrated ASCII console and the
  Operating system messages from IBM Hardware Management Console. But
  there is nothing interesting there

  From Operating System Messages, it ends at:
  [  OK  ] Reached target Final Step.
  [  OK  ] Started Reboot.
  [  OK  ] Reached target Reboot.
  And never proceed from this point. And HMC shows "Not operating"

  From Integrated ASCII console it just shows the login prompt, never
  prints any other message.

  Reboot works fine with older kernel (5.0.0-37)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-38-generic 5.0.0-38.41
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.4
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu Dec  5 06:46:12 2019
  HibernationDevice: RESUME=UUID=eae923f9-f5a4-41c0-b3e4-04786207dbaa
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: root=UUID=1a6af794-84a9-4034-a213-39506b9bb91c 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-38-generic N/A
   linux-backports-modules-5.0.0-38-generic  N/A
   linux-firmware                            1.178.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Reply via email to