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
Thanks Frank! dropping sev to a medium, Glad this is working.
next action item is to isolate and identify why the lpar in question is
acting up.
** Changed in: linux (Ubuntu)
Importance: Critical => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs,
After installing kernel 5.0.0.38.40 from ppa:canonical-kernel-
team/proposed and doing several reboot (shutdown/boot) tests I can
confirm that my system (LPAR) always booted w/o any problems.
Please see attached doc for cmd-logs ...
** Attachment added: "test.txt"
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
** Summary changed:
- Unable to reboot Disco on Ubuntu LPAR s390x (5.0.0-38)
+ Unable to reboot Disco on Ubuntu LPAR s390x (5.0.0-38)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855237
Title:
