From: Gregory Haskins <gregory.haskins.ml@gmail.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev@ozlabs.org, linux-rt-users@vger.kernel.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 15:58:20 -0400 [thread overview]
Message-ID: <4831DBDC.8000008@gmail.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?
> I've never gotten any -rt patchsets to work on this CPU, and it always
> seems to be related to the disk driver.
> I've tried since 2.6.16 ppc.... (2.6.16, 2.6.18 on ppc, 2.6.24 and 25 on
> powerpc)
>
> Even though this is a custom board, I'm pretty sure I can get it to fail
> on a pq2fads board with the same disk controller.
Im not sure if LOCKDEP is available for that architecture. Have you
tried it? Its pretty good at flushing these kinds of issues out
(assuming its available).
-Greg
next prev parent reply other threads:[~2008-05-19 19:59 UTC|newest]
Thread overview: 11+ 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:29 ` Scott Wood
2008-05-19 19:41 ` Rune Torgersen
2008-05-19 19:58 ` Gregory Haskins [this message]
2008-05-19 21:11 ` Scott Wood
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:49 ` Scott Wood
2008-05-19 22:08 ` 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=4831DBDC.8000008@gmail.com \
--to=gregory.haskins.ml@gmail.com \
--cc=gregory.haskins@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=runet@innovsys.com \
--cc=scottwood@freescale.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).