From: Scott Wood <scottwood@freescale.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: Oops with PREEMPT-RT on 2.6.25.4
Date: Mon, 19 May 2008 16:11:12 -0500 [thread overview]
Message-ID: <4831ECF0.5090101@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B04690162@ismail.innsys.innovsys.com>
Rune Torgersen wrote:
> Scott Wood wrote:
>> You're recursively entering lock_timer_base, which does a
>> spin_lock_irqsave(). Either interrupts are enabled when they should
>> not be, or an interrupt was supposed to be threaded that isn't.
>
> Sort of figured. How do I figure out which one, and how to fix it?
Almost certainly the latter. Is the disk interrupt shared with any
other interrupts, that are marked IRQF_NODELAY? The -rt patch doesn't
seem to handle mixing the two well.
Oh, and just to be sure: you do have CONFIG_PREEMPT_RT turned on, and
not just CONFIG_PREEMPT, right? The non-preempt-rt versions in the -rt
patch don't look like they disable interrupts, though I may just be
getting lost in a sea of underscores and ifdefs.
-Scott
next prev parent reply other threads:[~2008-05-19 21:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 19:05 Oops with PREEMPT-RT on 2.6.25.4 Rune Torgersen
2008-05-19 19:05 ` Rune Torgersen
2008-05-19 19:05 ` Rune Torgersen
2008-05-19 19:29 ` Scott Wood
2008-05-19 19:29 ` Scott Wood
2008-05-19 19:41 ` Rune Torgersen
2008-05-19 19:41 ` Rune Torgersen
2008-05-19 19:41 ` Rune Torgersen
2008-05-19 19:58 ` Gregory Haskins
2008-05-19 19:58 ` Gregory Haskins
2008-05-19 21:11 ` Scott Wood [this message]
2008-05-19 21:16 ` Rune Torgersen
2008-05-19 21:16 ` Rune Torgersen
2008-05-19 21:16 ` Rune Torgersen
2008-05-19 21:38 ` Scott Wood
2008-05-19 21:46 ` Rune Torgersen
2008-05-19 21:46 ` Rune Torgersen
2008-05-19 21:49 ` Scott Wood
2008-05-19 22:08 ` Rune Torgersen
2008-05-19 22:08 ` Rune Torgersen
2008-05-19 22:08 ` Rune Torgersen
2008-05-19 22:23 ` Rune Torgersen
2008-05-19 22:23 ` Rune Torgersen
2008-05-19 22:23 ` Rune Torgersen
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=4831ECF0.5090101@freescale.com \
--to=scottwood@freescale.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=runet@innovsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.