** Description changed:
- When booting v5.11 based riscv unmatched image in qemu with uboot, it
- fails to boot.
+ [Impact]
- When booting v5.11 based riscv unmatched kernel+initrd directly, it
- boots fine.
+ * u-boot may crash when attempting to boot extlinux.conf which
+ specifies fdtdir; the given u-boot config doesn't specify a dtb filename
+ to load; autodetection tries to make one up using $soc & $board
+ variables; and if one or both of them are not set (as it is the case for
+ qemu) it would crash. Fix this crash by doing validation / checking when
+ quering for $soc & $board variables in autodetectionn.
- Somehow, it seems that u-boot fails to correctly load & start v5.11
- kernel.
+ [Test Plan]
+
+ * Use qemu & uboot produced by the build that fixes this bug report
+ properly and attempt to boot hirsute's riscv64+unmatched image.
+
+ * It should boot correctly without a crash / qemu backtrace.
+
+ [Where problems could occur]
+
+ * This patch is bein upstreamed. If one is using external uboot (i.e.
+ provided by some other vendor) it may still crash when trying to boot
+ Ubuntu's riscv64 rootfs or cloud image.
+
+ [Other Info]
+
+ * Patch is being reviewed upstream
https://lists.denx.de/pipermail/u-boot/2021-May/449176.html
** Changed in: u-boot (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
