preempt crash in 2.6.18
runet at innovsys.com
Mon Oct 16 23:50:40 EST 2006
From: Vitaly Bordug [mailto:vbordug at ru.mvista.com]
On Sat, 14 Oct 2006 09:14:38 +1000
Benjamin Herrenschmidt wrote:
> On Sat, 2006-10-14 at 01:21 +0400, Vitaly Bordug wrote:
> > On Fri, 13 Oct 2006 09:16:52 -0500
> > Rune Torgersen wrote:
> > >
> > > This is from a Freescale 8265 running 2.6.18
> > > Anyone have any idea what this is and how to fix it?
> > >
> > Yes. Actually, I recall alike thing and used to fix with proper
> > spin-locking if the cascade PCI irq, which apparently does do_irq
> > that seems to confuse preempt counters.
> > Just a pure guess.
> How so ? Cascades shouldn't do do_IRQ with the new irq code anyway
> unless this is still arch/ppc, they should do either __do_IRQ or
> better, generic_handle_irq().
To clarify - I was about __do_IRQ and arch/ppc.
Anyway, cascade for PCI is the first place I'd give a look.
In our case it turned out to be in the TIPC network code. post_timeout was called and didn't unlock a lock.
The patch had been in the TIPC tree for abpout 2 days when we saw the problem.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Linuxppc-dev