On Mon, 2020-08-17 at 11:58 +0000, Roosen Henri wrote:
> On Mon, 2020-08-17 at 13:43 +0200, Henri Roosen wrote:
> > On Mon, 2020-08-17 at 13:13 +0200, bigeasy@linutronix.de wrote:
> > > On 2020-08-17 08:12:31 [+0000], Roosen Henri wrote:
> > > > > Is the 4.14 series the only one that is affected?
> > > > 
> > > > No, unfortunately not.
> > > > 
> > > > I ended up testing the v4.14.184-rt84 on two systems and the
> > > > v5.4.45-
> > > > rt27 on another system, all iMX6Q. Only one of the v4.14
> > > > systems
> > > > is
> > > > still running, the other v4.14 system dumping backtraces until
> > > > eventually reset, the v5.4 system endlessly dumping backtraces:
> > > > 
> > > > v4.14: https://paste.ubuntu.com/p/ZdFYhs4pjx/
> > > > v5.4: https://paste.ubuntu.com/p/wZPCQv8KjX/
> > > 
> > > So the 5.4 has an uptime of 45 days until this start?
> > 
> > Correct.
> > 
> > > > If the backtraces don't point to a root-cause, are there any
> > > > kernel
> > > > configuration options which are usefull to track this issue
> > > > down?
> > > 
> > > The 5.4 is not complete, it started earlier and this might be a
> > > follow-up problem (it seems to originate in die()).
> > > You could send me the config, I have an imx6q somewhere so I
> > > might
> > > be
> > > able to take a look. However I want sort another ppc issue first.
> > 
> > Please find the v5.4.45-rt27-config file attached to this email. 

I'm afraid something went wrong with sending attachments to the mailing
list. Please find the v5.4.45-rt27-config here as well: 
https://paste.ubuntu.com/p/Yr9Vf4yNWs/

> > Let 
> 
> To clarify the v5.4.45-rt27 before any confusion: I used the v5.4.44-
> rt27 merged into our v5.4.45 branch.
> 
> > me
> > know if you have any suggestions about the config file or useful
> > debugging I can switch on; I'll be restarting a couple of systems
> > for
> > new duration tests.

Please let me know if there you find any unregularities in my config or
suggestions on any usefull debugging-/forensic-config-options.

Thanks!
Henri