kernel-packages team mailing list archive
Mailing list archive
[Bug 1557130] Re: Current 4.4 kernel won't boot on powerpc
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-xenial
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Current 4.4 kernel won't boot on powerpc
Status in linux package in Ubuntu:
Status in linux source package in Xenial:
19:06 < stgraber> apw: hey, so looks like powerpc (not 64el) isn't booting with current 4.4 from xenial
19:06 < stgraber> apw: smoser may have some more details for you, all I know is that I dist-upgraded my ppc VM and it stopped booting, smoser had to reboot me into 3.19 manually
19:08 < apw> stgraber, which versoin number is that ?
19:08 < stgraber> ii linux-image-4.4.0-12-powerpc64-smp 4.4.0-12.28 powerpc Linux kernel image for version 4.4.0 on 64-bit PowerPC SMP
19:08 < apw> stgraber, and do you have one which did boot before that, in 4.4 ?
19:08 < smoser> 3.19 booted
19:08 < apw> stgraber, i think we need a bug and i'll get jsalisbury to get this bisected
19:08 < apw> i just realised we don't run adt on power, sigh
19:08 < stgraber> apw: nope, I upgraded from trusty to xenial so it's the first 4.4 I try
19:09 < smoser> qemu cmdline that results in "cant find root" looks like this
19:09 < smoser> qemu-system-ppc64 -name rockne-01 -echr 0x05 -enable-kvm -M pseries -cpu host -smp cores=2,threads=1 -m 8G -net nic,macaddr=52:54:00:00:42:01 -net tap,script=no,downscript=no,ifname=tap4201 -device spapr-vscsi -drive file=/var/lib/libvirt/images/shared/rockne-01/disk1.img -drive file=/var/lib/libvirt/images/shared/rockne-01/eph0.img -drive file=/var/lib/libvirt/images/shared/rockne-01/save.img -nographic -vga none
19:09 < jsalisbury> apw, I'll watch for the bug to come in
19:09 < smoser> where disk1.img has the root filesystem on it.
19:09 < stgraber> apw: the issue is storage related, smoser got dropped into a shell with no block listed in /proc/partitions
19:09 < smoser> only ram disks.
To manage notifications about this bug go to: