linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Roosen Henri <Henri.Roosen@ginzinger.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	Clark Williams <williams@redhat.com>
Subject: Re: RT kernel v4.14 NULL pointer dereferences
Date: Fri, 14 Aug 2020 13:58:48 +0200	[thread overview]
Message-ID: <20200814115848.w4m2bfqttkid6woi@linutronix.de> (raw)
In-Reply-To: <fd9d435b3f6a5f4ffd7ef93763e78c087871d565.camel@ginzinger.com>

On 2020-06-16 07:30:33 [+0000], Roosen Henri wrote:
> Hi RT-experts,
> 
> Duration tests with RT enabled v4.14 kernels on our ARM iMX6Q systems
> are showing "Unable to handle kernel NULL pointer dereference at
> virtual address" after running for some months. The same tests on NON-
> RT kernels don't show any problem and have been running without any
> problems for more than 20 months now.
> 
> I've been updating the tests from time to time with more recent
> kernels. Testing is basically done with cyclictest, in parallel with
> some load scripts/hackbench. Please have a look at the kernel traces:
> 4.14.71-rt44  -> https://paste.debian.net/1152206/
> 4.14.106-rt56 -> https://paste.debian.net/1152204/
> 4.14.146-rt67 -> https://paste.debian.net/1152202/
> 
> I've seen the v4.14-rt branch got some fixes, so my questions are:
> 1) is problem I'm facing known and fixed in v4.14-rt, or
> 2) is the problem I'm seeing a new issue probably still unfixed in
> 4.14.183-rt83 (which I'm testing right now)?
> 
> Any help is highly appreciated!

So this has not fixed all by itself?
Is the 4.14 series the only one that is affected?

> Thanks,
> Henri

Sebastian

  reply	other threads:[~2020-08-14 11:58 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 [this message]
2020-08-17  8:12   ` Roosen Henri
2020-08-17 11:13     ` bigeasy
     [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=20200814115848.w4m2bfqttkid6woi@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).