linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
	Tony Lindgren <tony@atomide.com>
Cc: "Grygorii Strashko" <grygorii.strashko@ti.com>,
	"Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>,
	"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>,
	"Suman Anna" <s-anna@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: beaglebone black boot failure Linux v5.15.rc1
Date: Tue, 21 Sep 2021 18:40:01 +0200	[thread overview]
Message-ID: <7C582E1F-13F6-4432-AE99-FF9B7EE9B06D@goldelico.com> (raw)
In-Reply-To: <cce97271-11d2-cc1a-a0fc-c8e8b4482329@ti.com>

Hi Matti, Tony,

> Am 21.09.2021 um 18:07 schrieb Suman Anna <s-anna@ti.com>:
> 
> 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].

Same for me with a v5.15-rc1 based kernel.

> May I ask what is your BBB board version? My board is rev.A5C.

I have an Rev B6 with EXP41 display attached. I think Matti reported a Rev C board?

> I vaguely remember from all those years ago when I first enabled PRUSS on AM335x
> that some earlier BBB versions had some issues around PRUSS.

What I am not using is PRUSS so it may (or may not) be disabled in CONFIG.

BR,
Nikolaus

  reply	other threads:[~2021-09-21 16:40 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 [this message]
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
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=7C582E1F-13F6-4432-AE99-FF9B7EE9B06D@goldelico.com \
    --to=hns@goldelico.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=peter.ujfalusi@gmail.com \
    --cc=s-anna@ti.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;
as well as URLs for NNTP newsgroup(s).