From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Yao Zi <me@ziyao.cc>
Cc: michael.opdenacker@rootcommit.com, Drew Fustini <drew@pdp7.com>,
guoren@kernel.org, wefu@redhat.com, inochiama@gmail.com,
opensbi@lists.infradead.org
Subject: Re: TH1520: broken CPU count detection
Date: Thu, 17 Sep 2026 12:54:49 +0200 [thread overview]
Message-ID: <5e67bae3-753c-4f39-bdb2-b912ff2f62e8@rootcommit.com> (raw)
In-Reply-To: <aqrG3uRzSjV58d8R@pie>
Hi Yao
On 9/16/26 6:42 PM, Yao Zi wrote:
> On Tue, Sep 15, 2026 at 09:31:01AM +0200, Michael Opdenacker wrote:
>> Greetings,
>>
>> For the Yocto meta-riscv layer, we're trying to replace the downstream
>> opensbi (called opensbi-revyos) by mainline opensbi:
>> https://github.com/riscv/meta-riscv/pull/685/
>>
>> The board boots fine, but unfortunately, only 1 CPU core is detected. This
>> surfaces in the Linux kernel log:
>>
>> [ 0.089851] smp: Bringing up secondary CPUs ...
>> [ 10.165542] CPU1 failed to report alive state
>> [ 20.241632] CPU2 failed to report alive state
>> [ 30.316980] CPU3 failed to report alive state
> What Linux kernel are you using?
I'm using mainline Linux 7.2.x.
Is this something Linux can manage?
Thanks
Michael
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
next prev parent reply other threads:[~2026-09-17 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 7:31 TH1520: broken CPU count detection Michael Opdenacker
2026-09-16 16:42 ` Yao Zi
2026-09-17 10:54 ` Michael Opdenacker [this message]
2026-09-17 17:36 ` Yao Zi
[not found] ` <7d24d195-02e4-46d3-b0a3-4c48bf6a0d90@rootcommit.com>
2026-09-28 8:44 ` Michael Opdenacker
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=5e67bae3-753c-4f39-bdb2-b912ff2f62e8@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=drew@pdp7.com \
--cc=guoren@kernel.org \
--cc=inochiama@gmail.com \
--cc=me@ziyao.cc \
--cc=opensbi@lists.infradead.org \
--cc=wefu@redhat.com \
/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