linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Poselenov <sposelenov@emcraft.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: kernel crash with ARM64 5.4.47 preempt_rt
Date: Fri, 08 Jan 2021 12:15:05 +0300	[thread overview]
Message-ID: <d868096428ede5ef93cca7431cf67c021bf2541b.camel@emcraft.com> (raw)
In-Reply-To: <20210108082911.cz7oropmnezhqx5p@linutronix.de>

Hi Sebastian,

Thank you for the feedback, it is very helpful.
Could you please provide us with a pointer to the bug?

Thanks again!

Regards,
Sergei
On Fri, 2021-01-08 at 09:29 +0100, Sebastian Andrzej Siewior wrote:
> On 2021-01-07 17:49:02 [+0100], To Sergei Poselenov wrote:
> > On 2020-12-30 14:09:17 [+0300], Sergei Poselenov wrote:
> > > Hello,
> > Hi,
> > 
> > > We applied patch-5.4.47-rt28.patch to NXP 5.4.47-2.2.0 release
> > > ARM64
> > > kernel running on IMX8M NANO chip, and enabled CONFIG_PRREMPT_RT.
> > > We
> > > are observing the following crash (below), on a system running an
> > > application that communicates with some SPI device. Obviously,
> > > the
> > > system doesn't crash without the patch applied.
> > > 
> > > Any thoughts on the reason of the failure would be appreciated.
> > > How would we start debugging the problem?
> > 
> > Can you give v5.10 a try v5.10 and/or enable SLUB_DEBUG?
> 
> Now that I look at it again, you need update to more recent v5.4-RT
> kernel. The current is v5.4.84-rt47, the bug was fixed in v5.4.54-
> rt33.
> 
> > > Thanks!
> > > 
> > > Regards,
> > > Sergei Poselenov,
> > > Emcraft Systems
> Sebastian


  reply	other threads:[~2021-01-08  9:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30 11:09 kernel crash with ARM64 5.4.47 preempt_rt Sergei Poselenov
2021-01-07 16:49 ` Sebastian Andrzej Siewior
2021-01-08  8:29   ` Sebastian Andrzej Siewior
2021-01-08  9:15     ` Sergei Poselenov [this message]
2021-01-08  9:28       ` Sebastian Andrzej Siewior

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=d868096428ede5ef93cca7431cf67c021bf2541b.camel@emcraft.com \
    --to=sposelenov@emcraft.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    /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).