lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 21 Sep 2021 16:49:36 -0500
From:   Suman Anna <s-anna@...com>
To:     Drew Fustini <pdp7pdp7@...il.com>
CC:     Tony Lindgren <tony@...mide.com>,
        Matti Vaittinen <mazziesaccount@...il.com>,
        Grygorii Strashko <grygorii.strashko@...com>,
        "Vaittinen, Matti" <Matti.Vaittinen@...rohmeurope.com>,
        "linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
        Paul Barker <paul.barker@...cloud.com>,
        Peter Ujfalusi <peter.ujfalusi@...il.com>,
        BenoƮt Cousson <bcousson@...libre.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: beaglebone black boot failure Linux v5.15.rc1

On 9/21/21 3:29 PM, Drew Fustini wrote:
> On Tue, Sep 21, 2021 at 9:09 AM Suman Anna <s-anna@...com> wrote:
>>
>> Hi Matti, Tony,
>>
>> On 9/21/21 2:47 AM, Tony Lindgren wrote:
>>> * Matti Vaittinen <mazziesaccount@...il.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
> 

Powered by blists - more mailing lists