Am Samstag, 1. Januar 2022, 23:12:16 CET schrieb Sven Schnelle:
> Hi Eike,
> 
> Rolf Eike Beer <eike-kernel@sf-tec.de> writes:
> > Am Montag, 27. Dezember 2021, 15:30:10 CET schrieb Rolf Eike Beer:
> >> Am Sonntag, 26. Dezember 2021, 18:22:12 CET schrieb John David Anglin:
> >> > On 2021-12-26 11:21 a.m., Rolf Eike Beer wrote:
> >> > > [139181.966881] WARNING: CPU: 1 PID: 0 at kernel/rcu/tree.c:613
> >> > > rcu_eqs_enter.constprop.0+0x8c/0x98
> >> > 
> >> > This is probably not reproducible. You might try this change from Sven
> >> 
> >> At least this time the git testsuite has finished, but with some errors
> >> as
> >> usual.
> > The machine locked up again, but without many output:
> > 
> > [13093.642353] INEQUIVALENT ALIASES 0x96000 and 0xf5bba000 in file xargs
> > [13094.122900] INEQUIVALENT ALIASES 0x110000 and 0xf5a63000 in file find
> > [13260.968430] INEQUIVALENT ALIASES 0x96000 and 0xf5bba000 in file xargs
> > [16995.351108] ttyS ttyS1:[17649.655079] t[17650.739194] t[17658.174951]
> > t[17659.307044] t[24039.432030] INEQUIVALENT ALIASES 0x113000 and
> > 0xf5a66000 in file find
> 
> Looks like you have a serial console connected? If yes, could you trigger a
> 'TOC s' from the BMC, and post the output from 'ser x 0 toc', where x is
> the processer number? This could help debugging this.

Yes, this is all from serial. I guess this only works during the hang? That 
means I have to boot into the bad kernel again and wait until it breaks. 

Eike