This bug was fixed in the package u-boot - 2021.01+dfsg-3ubuntu0~20.04.1
---------------
u-boot (2021.01+dfsg-3ubuntu0~20.04.1) focal; urgency=medium
* SRU of 2021.01+dfsg-3 from hirsute to enable booting on HiFive Unmatched
LP: #1934791, LP: #1925267, LP: #1923162
[ Dimitri John Ledkov ]
* Import meta-sifive u-boot patches.
* Enable sifive_hifive_unmatched_fu740 target.
* Build-depend on opensbi with fu740 errata fix.
* Set default FDT files for the sifive boards.
* Set USE_PREBOOT on unmatched board too (just like unleashed & qemu),
otherwise u-boot's fdtfile from itb is not used (i.e. when
extlinux.conf does not specify fdtdir). LP: #1923162
* Unapply unmatched patches, whilst building unleashed platform. Fixes
failure to boot from sd-card on Unleashed. LP: #1924761
* sifive-unleashed-default-fdt-files.patch: split into unleashed &
unmatched separate patches, for ease of upstreaming to meta-sifive and
u-boot upstreams. Also this ensures that unleashed target is built
with fdtfile= set, as unleashed target unapplies lots of patches.
* Apply upstreamed patch "cmd: pxe_utils: sysboot: fix crash if either
board or soc are not set." This fixes a crash booting any
extlinux.conf with fdtdir specified, and dtbfile not set and
"soc"/"board" not set in the environment LP: #1923162
[ William 'jawn-smith' Wilson ]
* Re-added d/p/lzo-to-lzno.patch as lzop is in universe prior to Groovy
* Updated d/targets for compatibility with focal arm-trusted-firmware
* Updated d/control for compatibility with focal debhelper
* Reinstate rpi-config-migration script for focal
* Prevent stripping of qemu binaries under focal where strip doesn't
recognize the format
[ Dave Jones ]
* In d/control update opensbi dependency for focal
-- William 'jawn-smith' Wilson <william.wil...@canonical.com> Fri, 25
Jun 2021 18:21:47 +0000
** Changed in: u-boot (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
Status in linux-riscv package in Ubuntu:
Invalid
Status in u-boot package in Ubuntu:
Fix Released
Status in u-boot-menu package in Ubuntu:
Fix Released
Status in linux-riscv source package in Focal:
Invalid
Status in u-boot source package in Focal:
Fix Released
Status in u-boot-menu source package in Focal:
Fix Released
Status in linux-riscv source package in Hirsute:
Invalid
Status in u-boot source package in Hirsute:
Confirmed
Status in u-boot-menu source package in Hirsute:
Fix Released
Bug description:
[Impact]
* 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.
[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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+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
