From: Conor Dooley <conor.dooley@microchip.com>
To: opensbi@lists.infradead.org
Subject: Boot failure after QEMU's upgrade to OpenSBI v1.3 (was Re: [PATCH for-8.2 6/7] target/riscv: add 'max' CPU type)
Date: Wed, 19 Jul 2023 08:07:31 +0100 [thread overview]
Message-ID: <20230719-dioxide-panic-cda48b1d8d1b@wendy> (raw)
In-Reply-To: <CAKmqyKO3O87ETntm7pzMPedKW19ANpEp5nM4jFiHXO76K9saTQ@mail.gmail.com>
On Wed, Jul 19, 2023 at 11:32:55AM +1000, Alistair Francis wrote:
> If there is no OpenSBI 1.3.1 release we should add something to the
> release notes. @Conor Dooley are you able to give a clear sentence on
> how the boot fails?
Uhh, I'll give it a shot, but hopefully it is not required :)
In version v1.3, OpenSBI's aclint drivers fail to initialise if they
encounter a disabled CPU node in the devicetree. Attempting to boot
using, for example, the Linux kernel's PolarFire SoC or Freedom U540
devicetrees, will fail with the error:
"init_coldboot: ipi init failed (error -1009)"
Please see OpenSBI commit c6a3573 ("lib: utils: Fix sbi_hartid_to_scratch()
usage in ACLINT drivers")
<https://github.com/riscv-software-src/opensbi/commit/c6a35733b74aeff612398f274ed19a74f81d1f37>
for the fix.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/opensbi/attachments/20230719/839e4402/attachment.sig>
next prev parent reply other threads:[~2023-07-19 7:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230712190149.424675-1-dbarboza@ventanamicro.com>
[not found] ` <20230712190149.424675-7-dbarboza@ventanamicro.com>
[not found] ` <20230712-stench-happiness-40c2ea831257@spud>
[not found] ` <3e9b5be8-d3ca-3a17-bef9-4a6a5bdc0ad0@ventanamicro.com>
[not found] ` <20230712-tulip-replica-0322e71c3e81@spud>
[not found] ` <744cbde6-7ce5-c327-3c5a-3858e994cc39@ventanamicro.com>
[not found] ` <20230712-superhero-rabid-578605f52927@spud>
[not found] ` <5dd3366d-13ba-c7fb-554f-549d97e7d4f9@ventanamicro.com>
[not found] ` <20230712-fancied-aviator-270f51166407@spud>
2023-07-13 22:12 ` Boot failure after QEMU's upgrade to OpenSBI v1.3 (was Re: [PATCH for-8.2 6/7] target/riscv: add 'max' CPU type) Conor Dooley
2023-07-13 22:35 ` Daniel Henrique Barboza
2023-07-13 23:04 ` Conor Dooley
2023-07-14 4:30 ` Anup Patel
2023-07-14 10:19 ` Conor Dooley
2023-07-14 12:28 ` Conor Dooley
2023-07-15 9:12 ` Atish Patra
2023-07-19 1:32 ` Alistair Francis
2023-07-19 5:39 ` Anup Patel
2023-07-19 9:53 ` Alistair Francis
2023-07-19 15:21 ` Anup Patel
2023-07-19 15:45 ` Bin Meng
2023-07-19 16:10 ` Anup Patel
2023-07-19 16:18 ` Bin Meng
2023-07-19 16:17 ` Andreas Schwab
2023-07-19 7:07 ` Conor Dooley [this message]
2023-07-14 12:35 ` Anup Patel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230719-dioxide-panic-cda48b1d8d1b@wendy \
--to=conor.dooley@microchip.com \
--cc=opensbi@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox