Re: beaglebone black boot failure Linux v5.15.rc1

[Matti Vaittinen <mazziesaccount@gmail.com>]

Hi dee Ho peeps & Thanks.

On 9/17/21 15:36, Grygorii Strashko wrote:
> 
> 
> On 17/09/2021 14:34, Vaittinen, Matti wrote:
>> Thanks a lot guys!
>>
>> On 9/17/21 14:01, Grygorii Strashko wrote:
>>>
>>>
>>> On 17/09/2021 13:57, Grygorii Strashko wrote:
>>>>
>>>>
>>>> On 17/09/2021 13:28, Vaittinen, Matti wrote:
>>>>> Hi deeee Ho Tony & All,
>>>>>
>>>>> On 9/17/21 09:14, Tony Lindgren wrote:
>>>>>> Hi,
>>>>>>
>>>>>> * Vaittinen, Matti <Matti.Vaittinen@fi.rohmeurope.com> [210916 
>>>>>> 09:15]:
>>>>>
>>>>>>> My beaglebone black (rev c) based test environment fails to boot 
>>>>>>> with
>>>>>>> v5.15-rc1. Boot succeeds with the v5.14.
>>>>>>>>> I added initcall_debug && changed the pr_debug() to pr_err() in
>> really_probe_debug(). Log from that run is attached. The
>> omap_reset_deassert() was not instrumented to print/delay for this run.
> 
> can you try just disable pruss_tm in am335x-bone-common.dtsi?
> 

I did try:

diff --git a/arch/arm/boot/dts/am335x-bone-common.dtsi 
b/arch/arm/boot/dts/am335x-bone-common.dtsi
index 
0ccdc7cd463bc62812f0f2797adb0f7bff1bd1b1..538af3fa0e6361923b40598fd33637c868298a83 
100644
--- a/arch/arm/boot/dts/am335x-bone-common.dtsi
+++ b/arch/arm/boot/dts/am335x-bone-common.dtsi
@@ -402,5 +402,5 @@ &rtc {
  };

  &pruss_tm {
-	status = "okay";
+	status = "disabled";
  };

and the boot did no longer produce an oops.

NFS mount still hung. It took me a while to dig out that the cpsw_new.c 
was not compiled with my config. The TI_CPSW_SWITCHDEV was not set.

I did set the TI_CPSW_SWITCHDEV=y after which the bbb booted-up. 
Enabling the pruss_tm still produces an oops.

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.

Best Regards
	Matti Vaittinen