From: Suman Anna <s-anna@ti.com>
To: Drew Fustini <pdp7pdp7@gmail.com>
Cc: "Tony Lindgren" <tony@atomide.com>,
"Matti Vaittinen" <mazziesaccount@gmail.com>,
"Grygorii Strashko" <grygorii.strashko@ti.com>,
"Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Paul Barker" <paul.barker@sancloud.com>,
"Peter Ujfalusi" <peter.ujfalusi@gmail.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: beaglebone black boot failure Linux v5.15.rc1
Date: Tue, 21 Sep 2021 16:49:36 -0500 [thread overview]
Message-ID: <40077cea-1f5e-de67-58dd-7fae0f63678d@ti.com> (raw)
In-Reply-To: <CAEf4M_B1vam_ykRZmQ5++QArC-=+yooRg25BrQXKE5nk8AtqbA@mail.gmail.com>
On 9/21/21 3:29 PM, Drew Fustini wrote:
> On Tue, Sep 21, 2021 at 9:09 AM Suman Anna <s-anna@ti.com> wrote:
>>
>> Hi Matti, Tony,
>>
>> On 9/21/21 2:47 AM, Tony Lindgren wrote:
>>> * Matti Vaittinen <mazziesaccount@gmail.com> [210920 08:23]:
>>>> Finally, adding the udelay(100); (as Tony suggested) at the end of the
>>>> omap_reset_deassert() did make the oops go away even when pruss_tm was
>>>> enabled. I don't know what would be a proper fix though.
>>
>> I have been able to boot v5.15-rc1 just fine on my BBB without any additional
>> changes [1].
>>
>> May I ask what is your BBB board version? My board is rev.A5C.
>
> That rev is quite old [1]. Would you be able to try a Rev C? It has
> been in production since around 2014 with the move from 2GB to 4GB
> eMMC.
I don't have any rev.C boards handy to try.
I am curious to see if there is some correlation between failures and board
versions. I see that there is a minor processor change to AM3358 from rev.B
onwards compared to the AM3359 that I would have on my board. PRU-ICSS IP would
be present and supported on both though.
regards
Suman
>
> Thanks,
> Drew
> [1] https://elinux.org/Beagleboard:BeagleBoneBlack#Revision_A5C
>
next prev parent reply other threads:[~2021-09-21 21:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 9:15 beaglebone black boot failure Linux v5.15.rc1 Vaittinen, Matti
2021-09-17 6:14 ` Tony Lindgren
2021-09-17 10:28 ` Vaittinen, Matti
2021-09-17 10:47 ` Tony Lindgren
2021-09-17 10:57 ` Grygorii Strashko
2021-09-17 11:01 ` Grygorii Strashko
[not found] ` <615b6fec-6c62-4a97-6d0c-d2e5a5d1ccb2@fi.rohmeurope.com>
2021-09-17 12:36 ` Grygorii Strashko
2021-09-20 10:05 ` Matti Vaittinen
2021-09-21 7:47 ` Tony Lindgren
2021-09-21 16:07 ` Suman Anna
2021-09-21 16:40 ` H. Nikolaus Schaller
2021-09-21 16:49 ` Suman Anna
2021-09-22 9:27 ` Vaittinen, Matti
2021-09-24 18:40 ` Robert Nelson
2021-09-30 8:10 ` Tony Lindgren
2021-09-30 9:41 ` Vaittinen, Matti
2021-09-21 20:29 ` Drew Fustini
2021-09-21 21:49 ` Suman Anna [this message]
2021-09-21 22:00 ` Robert Nelson
2021-09-21 23:53 ` Suman Anna
2021-09-22 8:44 ` Vaittinen, Matti
2021-09-22 8:48 ` Tony Lindgren
2021-09-30 8:06 ` Tony Lindgren
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=40077cea-1f5e-de67-58dd-7fae0f63678d@ti.com \
--to=s-anna@ti.com \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=bcousson@baylibre.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=paul.barker@sancloud.com \
--cc=pdp7pdp7@gmail.com \
--cc=peter.ujfalusi@gmail.com \
--cc=tony@atomide.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