From: "bigeasy@linutronix.de" <bigeasy@linutronix.de>
To: Roosen Henri <Henri.Roosen@ginzinger.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"williams@redhat.com" <williams@redhat.com>
Subject: Re: RT kernel v4.14 NULL pointer dereferences
Date: Mon, 17 Aug 2020 13:13:11 +0200 [thread overview]
Message-ID: <20200817111311.zyqjznhferoqqxkh@linutronix.de> (raw)
In-Reply-To: <25412beffb96ab8c2b8f869bdac5a66c49faa5ca.camel@ginzinger.com>
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?
> 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.
> Thanks!
Sebastian
next prev parent reply other threads:[~2020-08-17 11:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 7:30 RT kernel v4.14 NULL pointer dereferences Roosen Henri
2020-08-14 11:58 ` Sebastian Andrzej Siewior
2020-08-17 8:12 ` Roosen Henri
2020-08-17 11:13 ` bigeasy [this message]
[not found] ` <05cc3d6085641c7f0425e45358451b05c5e9fc07.camel@ginzinger.com>
2020-08-17 11:58 ` Roosen Henri
2020-08-26 9:56 ` Roosen Henri
2020-08-27 12:52 ` bigeasy
2020-08-27 13:11 ` bigeasy
2020-08-28 8:47 ` Roosen Henri
2021-01-19 10:57 ` Roosen Henri
2021-01-21 15:29 ` bigeasy
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=20200817111311.zyqjznhferoqqxkh@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=Henri.Roosen@ginzinger.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.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).