[Bug 2098421] Re: [SRU] U-Boot 2024.01 fails to boot on RISC-V with QEMU 9.0 and cpu=max
Timo Aaltonen
2098421 at bugs.launchpad.net
Fri May 23 07:40:47 UTC 2025
Hello Heinrich, or anyone else affected,
Accepted u-boot into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/u-boot/2024.01+dfsg-1ubuntu5.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: u-boot (Ubuntu Noble)
Status: Confirmed => Fix Committed
** Tags added: verification-needed-noble
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to u-boot in Ubuntu.
https://bugs.launchpad.net/bugs/2098421
Title:
[SRU] U-Boot 2024.01 fails to boot on RISC-V with QEMU 9.0 and cpu=max
Status in u-boot package in Ubuntu:
Fix Released
Status in u-boot source package in Noble:
Fix Committed
Status in u-boot source package in Oracular:
Fix Committed
Status in u-boot source package in Plucky:
Fix Released
Bug description:
[ Impact ]
RISC-V device-trees have moved to using riscv,isa-extensions instead
of riscv,isa. If riscv,isa is missing, U-Boot 2024.01 fails to boot.
This can be demonstrated with QEMU 9.0 and cpu=max.
The following patches provide a remedy:
0d95add3b1c7 ("riscv: cpu: improve multi-letter extension detection in supports_extension()"
b90edde70127 ("riscv: don't read riscv, isa in the riscv cpu's get_desc()")
f39b1b77d822 ("riscv: support extension probing using riscv, isa-extensions")
[Test Plan ]
With QEMU 9.0 installed run:
qemu-system-riscv64 -M virt -cpu max \
-kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf
For regression testing:
Install u-boot-sifive on the Unmatched board and boot.
Install u-boot-microchip on the Icicle board and boot.
Install u-boot-starfive on the VisionFive 2 board and boot.
[ Where problems could occur ]
Booting on QEMU or real hardware might fail if the implementation of
ISA string parsing were incorrect.
[ Other Info ]
n/a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/2098421/+subscriptions
More information about the foundations-bugs
mailing list