linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Tom Cook <tom.k.cook@gmail.com>
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Re: Tracers+cyclictest causing kernel oops
Date: Fri, 21 Jun 2013 17:00:44 +0200	[thread overview]
Message-ID: <20130621150044.GE21228@linutronix.de> (raw)
In-Reply-To: <CAFSh4UyVf18mx3Pf0HbOzLWTGEMNC0rv+7H8etcvsj+R0EgSNA@mail.gmail.com>

* Tom Cook | 2013-06-21 12:21:40 [+0100]:

>> The tracer do not use any special interrupts on purpose.
>> Now that I saw rasperry-pi let me ask this: do you have any
>> non-mainline patches on-top? And if it is the case, could you try to
>> get rid of them?
>
>By 'non-mainline' do you mean in addition to the kernel.org source, or
>in addition to the raspberry pi git tree?  Yes, to the former, no to
>the latter.

You could boot into ramdisk with tiny busybox + cyclictest and disable
the usb driver in question.

>> Also you can try the same test without the RT patches?
>
>Quite right - the same oops happens with "Linux raspberrypi 3.6.11+ #4 PREEMPT".
>
>I think I'm nearly starting to get my head around what's going on
>here.  The USB driver uses FIQs, which normally isn't a problem
>because nothing would interrupt the FIQ handler (or if it did, it
>wouldn't generate a page fault).  But cyclictest runs at a higher
>priority than the USB handler and generates page faults (at least when
>it is initialising).  Eventually it interrupts a USB FIQ handler and
>the memory manager doesn't know what to do with a page fault in a FIQ
>handler, so it oopses.  Does that sound about right?

You said that it oops also on non-RT kernel where cyclictest is not
running ontop of the USB thread. In general, the irq core disables the
interrupts and schedules the interrupt thread with threaded interrupt
support enabled.
But here it seems that FIQ interrupt is not implemented / suppoted
fully.
So either you have to fix this or replace the USB part :)

>Tom

Sebastian

      parent reply	other threads:[~2013-06-21 15:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26  8:04 Tracers+cyclictest causing kernel oops Tom Cook
2013-04-29  7:16 ` Tom Cook
2013-05-03 16:05   ` Sebastian Andrzej Siewior
2013-05-12  5:14     ` Tom Cook
     [not found]     ` <CAFSh4UwD5yyJrtKwUaOX-uiUuzVf7YaDbM4vbZ1EFZBf6F1JHg@mail.gmail.com>
2013-05-21 11:16       ` Sebastian Andrzej Siewior
2013-05-21 15:20         ` Tom Cook
2013-05-27  8:02           ` Uwe Kleine-König
2013-05-27 21:23             ` Tom Cook
2013-05-28  6:53               ` Uwe Kleine-König
2013-06-21 11:01                 ` Tom Cook
2013-05-31  9:23           ` Sebastian Andrzej Siewior
2013-05-31  9:31             ` Tom Cook
2013-06-21 11:21             ` Tom Cook
2013-06-21 14:17               ` Tom Cook
2013-06-21 14:58                 ` Tom Cook
2013-06-21 15:00               ` Sebastian Andrzej Siewior [this message]

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=20130621150044.GE21228@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tom.k.cook@gmail.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).