From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Fawad Lateef <fawadlateef@gmail.com>
Cc: Eric Nelson <eric@nelint.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: Thu, 18 May 2017 22:10:33 +0200 [thread overview]
Message-ID: <20170518201033.ygdgdhdslbqypcoj@linutronix.de> (raw)
In-Reply-To: <CAGgoGu7qJegvp8o_33rfVbSWHNH8N4bbiTORXJYziRvKB9=O3w@mail.gmail.com>
On 2017-05-18 13:08:32 [+0200], Fawad Lateef wrote:
> Hi Sebastian,
Hi Fawad,
> > 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.
> >
>
> Yes, this happens at run-time and not always. Sometimes hardware just
> hangs/stalls.
So this sounds like a race condition.
> As now RT is widely used on ARM so to me seems like it something
> related to hardware design/setting OR application.
>
> Another question: Is RT user-space application can make kernel/system
> crash? As to me kernel should kill the app but let itself running
> _but_ not sure in the case of RT patched kernel.
This is correct. With RT or without it: a use space should not be able
to crash the kernel.
It is possible that a race within a driver triggers more reliably on RT.
I would recommend to strip down the system to the minimum where the
issue should not trigger. And then slowly increase the "enabled"
hardware components so you might get an idea when or what could cause
it.
> Thanks,
>
> Fawad Lateef
Sebastian
next prev parent reply other threads:[~2017-05-18 20:10 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
2017-05-18 11:08 ` Fawad Lateef
2017-05-18 20:10 ` Sebastian Andrzej Siewior [this message]
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=20170518201033.ygdgdhdslbqypcoj@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