Spent quite a bit of time on this and finally some progress.
This is not a critical bug anymore as I can now successfully reboot my lpar
with the -proposed kernel 5.0.0-38 for SRU Cycle 2019.12.02
During deployment of an lpar we configure DASD aliases via multipath,
usually this is required for disk performance however in our lab we are
always connecting to just 1 disk, so there is no need to i/o performance
in the test lab.
Also it is in question if DASD Aliases should not be used on an lpar as
they may only be for Zvm's, is this a proper supported configuration?
It would appear that having an active subchannel "chzdev -e
0.0.17e0-0.0.XXXX" is what perhaps is leading to this reboot problem.
The system actually is really "rebooting", it simply takes over 20
minutes to accomplish that task.
Why so long?
The assumption is that, once a channel is activated, the system will
build udev rules and rebuild the initramfs. Thus during the reboot
phase, the lpar must query each of the enabled disks to ensure they are
ok. Oddly , we don't see a delay in a shutdown command either.
This is just an assumption since I only see the problem once I activate
host multipath via chzdev. This problem has never been seen or
experienced in the past and is only isolated to this kernel. Xenial,Eoan
-proposed both restart just fine (For this SRU cycle)
It's possible that a commit made within this cycle has exposed this
issue. However for now there is a valid workaround.
In the lpar that Frank Heimes tested, he did NOT have multipathing
configured as his system rebooted without any delays, just as I
experienced after a fresh install (no multipathing configured)
I'm going to leave the severity at Medium as Frank Heimes will obtaining
more information about the disk multipathing on the lpar. To see if this
possibly is the culprit.
** Changed in: linux (Ubuntu)
Assignee: Sean Feole (sfeole) => (unassigned)
** Summary changed:
- Unable to reboot Disco on Ubuntu LPAR s390x (5.0.0-38)
+ Extreme Delayed Reboot with Disco on Ubuntu LPAR s390x (5.0.0-38)
--
You 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:
Extreme Delayed Reboot with Disco on Ubuntu LPAR s390x (5.0.0-38)
Status in Ubuntu on IBM z Systems:
Triaged
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-z-systems/+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
