This was fixed during the regular rebase with upstream. We can close
this one now.
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => 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/2003348
Title:
[23.04] Kernel 6.2 does not boot on s390x
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
The kernel team created a first kernel 6.2 for testing purposes.
linux-unstable 6.2.0-4.4 ia available in ppa:canonical-kernel-
team/bootstrap
However this kernel does not boot on s390x and crashes:
https://pastebin.canonical.com/p/qXj4g4bgGH/
or:
...
Ý 0.408281¨ md: Waiting for all devices to be available before autodetect
Ý 0.408283¨ md: If you don't use raid, use raid=noautodetect
Ý 0.408285¨ md: Autodetecting RAID arrays.
Ý 0.408287¨ md: autorun ...
Ý 0.408288¨ md: ... autorun DONE.
Ý 0.408405¨ /dev/root: Can't open blockdev
Ý 0.408409¨ VFS: Cannot open root device "disk/by-path/ccw-0.0.0400-part1"
or
unknown-block(0,0): error -6
Ý 0.408412¨ Please append a correct "root=" boot option; here are the
availa
le partitions:
Ý 0.408415¨ Kernel panic - not syncing: VFS: Unable to mount root fs on
unkno
wn-block(0,0)
Ý 0.408418¨ CPU: 2 PID: 1 Comm: swapper/0 Not tainted 6.2.0-4-generic
#4-Ubun
tu
Ý 0.408421¨ Hardware name: IBM 2964 N63 400 (z/VM 6.4.0)
Ý 0.408423¨ Call Trace:
Ý 0.408425¨ Ý<00000000b5d881b2>¨ dump_stack_lvl+0x62/0x90
Ý 0.408433¨ Ý<00000000b5d78f5c>¨ panic+0x174/0x360
Ý 0.408438¨ Ý<00000000b723e4fe>¨ mount_block_root+0x16e/0x210
Ý 0.408444¨ Ý<00000000b723e7b8>¨ prepare_namespace+0x168/0x1e0
Ý 0.408448¨ Ý<00000000b723dd46>¨ kernel_init_freeable+0x1de/0x1f0
Ý 0.408451¨ Ý<00000000b5d8948e>¨ kernel_init+0x2e/0x1a0
Ý 0.408455¨ Ý<00000000b50d3d30>¨ __ret_from_fork+0x40/0x60
Ý 0.408459¨ Ý<00000000b5d98e4a>¨ ret_from_fork+0xa/0x40
02: HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000
B50E215E
or:
[ 8.693187] /dev/root: Can't open blockdev
[ 8.693191] VFS: Cannot open root device "disk/by-path/ccw-0.0.260b-part1"
or unknown-block(0,0): error -6
[ 8.693194] Please append a correct "root=" boot option; here are the
available partitions:
[ 8.693198] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
Initially we thought it might be related to LVM/DM, but it's not,
since it happens also on single DASD disk installation without LVM and also
on NVMe disks.
It also happens on z15 and on z13.
Messages indicate that either the "root=" argument is wrong or not there.
I can check /proc/cmdline since the system ends up in a crash for me.
However, installing and using 6.1.0-9 works fine.
_____
Steps to re-create:
- Install Ubuntu lunar using:
https://cdimage.ubuntu.com/ubuntu-server/daily-live/current/lunar-live-server-s390x.iso
or:
https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/lunar-live-server-s390x.iso
(- get it updated:
sudo apt -y -q update && sudo apt -y -q full-upgrade && sudo apt autoremove
--purge )
- sudo add-apt-repository --yes ppa:canonical-kernel-team/bootstrap
- $ sudo apt update
- $ sudo apt install --yes linux-image-6.2.0-4-generic
linux-modules-6.2.0-4-generic linux-modules-extra-6.2.0-4-generic
linux-headers-6.2.0-4-generic
- $ sudo reboot
- open the console (e.g. Operating Systems Messages) and monitor the boot/IPL
process, it's fail like above
Do the same with kernel 6.1:
sudo apt install --yes linux-image-6.1.0-9-generic
linux-modules-6.1.0-9-generic linux-modules-extra-6.1.0-9-generic
linux-headers-6.1.0-9-generic
and the system reboots successfully.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003348/+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
