From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Eric Nelson <eric@nelint.com>
Cc: Fawad Lateef <fawadlateef@gmail.com>,
GuJiangfei <qiledexin@163.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kernelnewbies <kernelnewbies@kernelnewbies.org>,
linux-rt-users@vger.kernel.org
Subject: Re: Question regarding RT patches for ARM
Date: Wed, 17 May 2017 18:02:13 +0200 [thread overview]
Message-ID: <20170517160213.go3fiyhf5vmr7bmj@linutronix.de> (raw)
In-Reply-To: <c0fc9f9b-ae0b-66d3-71c7-e2b98f6900e0@nelint.com>
On 2017-05-17 07:45:39 [-0700], Eric Nelson wrote:
> Hi Fawad,
Hi Fawad,
> On 05/17/2017 06:40 AM, Fawad Lateef wrote:
> > > > I'm not sure about the unhandled page fault, but the stalls may be
> > > > because of the SDMA driver.
> > > >
> > > > See this patch in the Freescale/NXP community for kernel 4.1:
> > > > https://github.com/Freescale/meta-freescale/blob/master/recipes-kernel/linux/linux-fslc-imx-rt/0003-Work-around-CPU-stalls-in-the-imx-sdma-driver.patch
That is something I see for the first time. The description says that it
leads to this stall but it fails to explain _how_ it got there.
> > > Thanks for the patch link. I will give it a try.
> >
> > Talked to hardware manufacturer and they applied the patch.
> >
> > Still that SDMA is only used for NOR flash and only u-boot and its
> > environment are stored in nor flash. So not sure if that is going to
> > help in any case.
> >
>
> SDMA is used for much more than NOR flash (SSI, USB, and sometimes
> UARTs).
>
> > So I would really like few more suggestions OR confirmations about ARM
> > (cortex-A9 based imx6) (preemept)-RT support/patches are stable and
> > can be used for final products.
> >
>
> I don't have any experience with the RT patches on 4.9 or later
> kernels, but do know that they're being used on i.MX6 with the
> vendor kernels (3.10.x, 4.1.x).
I just looked into a few boot logs and it seems the Phyflex board (imx6
quad) bootet v4.9.27-rt18, run cyclictest including some tests and
nothing produced this "unhandled page fault" you mention here. This
includes the previous RT version in the v4.9 line.
Of this "page fault" happens on boot, it has to do something without
your .config + hw combination. If it happens at rune-time it is probably
triggered by a driver or an application is triggering this.
> Regards,
>
>
> Eric
Sebastian
next prev parent reply other threads:[~2017-05-17 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGgoGu6=EKCkzbZ0=i+4e+9rJUvxG-SUix1AQVch8VF=OmokVw@mail.gmail.com>
2017-05-15 13:06 ` Question regarding RT patches for ARM Richard Weinberger
[not found] ` <3aa42082.b247.15c0c29ca5e.Coremail.qiledexin@163.com>
2017-05-15 13:09 ` Fawad Lateef
2017-05-15 13:47 ` Sebastian Andrzej Siewior
2017-05-15 14:07 ` Fawad Lateef
2017-05-15 14:12 ` Eric Nelson
2017-05-15 14:20 ` Fawad Lateef
2017-05-17 13:40 ` Fawad Lateef
2017-05-17 14:45 ` Eric Nelson
2017-05-17 16:02 ` Sebastian Andrzej Siewior [this message]
2017-05-18 11:08 ` Fawad Lateef
2017-05-18 20:10 ` Sebastian Andrzej Siewior
2017-05-18 8:45 ` Fawad Lateef
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=20170517160213.go3fiyhf5vmr7bmj@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=eric@nelint.com \
--cc=fawadlateef@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=qiledexin@163.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