From: "Rune Torgersen" <runet@innovsys.com>
To: "Scott Wood" <scottwood@freescale.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:16:34 -0500 [thread overview]
Message-ID: <DCEAAC0833DD314AB0B58112AD99B93B04690239@ismail.innsys.innovsys.com> (raw)
In-Reply-To: <4831ECF0.5090101@freescale.com>
Scott Wood wrote:
> 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.
Disk is on a muxed PCI interrupt. None of the other interrupts on the
mux is fireing at the time.
Is is possible that the demuxer is not set up right? It is based loosely
on pq2-pci-pic.c
> 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.
Full CONFIG_PREEMPT_RT. I was actually going to try CONFIG_PREEMPT to
see if anything helped.
next prev parent reply other threads:[~2008-05-19 21:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 19:05 Rune Torgersen
2008-05-19 19:29 ` Scott Wood
2008-05-19 19:41 ` Rune Torgersen
2008-05-19 19:58 ` Gregory Haskins
2008-05-19 21:11 ` Scott Wood
2008-05-19 21:16 ` Rune Torgersen [this message]
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=DCEAAC0833DD314AB0B58112AD99B93B04690239@ismail.innsys.innovsys.com \
--to=runet@innovsys.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--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
all inboxes | Powered by JetHome®