From: Andreas Schwab <schwab@suse.de>
To: Anup Patel <anup@brainfault.org>
Cc: Atish Patra <Atish.Patra@wdc.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: Boot stuck at "smp: Bringing up secondary CPUs ..."
Date: Wed, 06 Feb 2019 11:33:01 +0100 [thread overview]
Message-ID: <mvmbm3p1a1u.fsf@suse.de> (raw)
In-Reply-To: <CAAhSdy33AFXrCQppswWzscy8TQh0Tjp1ixcjFcoB97v6vAwWxw@mail.gmail.com> (Anup Patel's message of "Wed, 6 Feb 2019 15:47:30 +0530")
On Feb 06 2019, Anup Patel <anup@brainfault.org> wrote:
> On Wed, Feb 6, 2019 at 3:34 PM Andreas Schwab <schwab@suse.de> wrote:
>>
>> On Feb 06 2019, Anup Patel <anup@brainfault.org> wrote:
>>
>> > On Wed, Feb 6, 2019 at 2:47 PM Andreas Schwab <schwab@suse.de> wrote:
>> >>
>> >> On Feb 05 2019, Atish Patra <Atish.Patra@wdc.com> wrote:
>> >>
>> >> > Are you loading Linux from U-Boot and openSBI ?
>> >>
>> >> No.
>> >
>> > We requite Atish's SMP fixes to boot upstream kernel on Unleashed board.
>>
>> The same boot image has booted sucessfully before. The problem with SMP
>> bringup only started when I started experimenting with openSBI and
>> U-Boot. Coincidence?
>
> Lot of kernel bugs are hidden due to FDT fixups done by BBL at boot-time.
Then why does it fail with BBL?
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-02-06 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 15:27 Boot stuck at "smp: Bringing up secondary CPUs ..." Andreas Schwab
[not found] ` <F77EA382-959C-4142-9A00-F1EBB58D37F8@wdc.com>
2019-02-06 9:16 ` Andreas Schwab
2019-02-06 9:33 ` Anup Patel
2019-02-06 10:04 ` Andreas Schwab
2019-02-06 10:17 ` Anup Patel
2019-02-06 10:33 ` Andreas Schwab [this message]
2019-02-06 10:37 ` Anup Patel
2019-02-06 10:44 ` Andreas Schwab
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=mvmbm3p1a1u.fsf@suse.de \
--to=schwab@suse.de \
--cc=Atish.Patra@wdc.com \
--cc=anup@brainfault.org \
--cc=linux-riscv@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.