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
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html