Re: [PANIC][2.5.66bk3+] run_timer_softirq - IRQ Mishandlings

[Robert Love <rml@tech9.net>]

On Sat, 2003-03-29 at 15:45, Shawn Starr wrote:

> In both panics below c012e9b4 does not exist as a kernel symbol in
> System.map:

The EIP need not exist itself in System.map.  System.map has the symbol
to initial address mapping.  For example,

	100	functionA
	200	functionB

If the EIP was "150" you would be 50 bytes into functionA().

> Code: 89 50 04 89 02 c7 41 30 00 00 00 00 81 3d 60 98 41 c0 3c 4b
>  kernel/timer.c:258: spin_lock(kernel/timer.c:c0419860) already locked by
> kernel/timer.c/398
> Kernel panic: Aiee, killing interrupt handler!
> In interrupt handler - not syncing

This is not a panic, just an oops.  And it was just a debugging check
from spin lock debugging, but unfortunately you were in an interrupt
handler so the machine went bye bye.

It is probably a simple double-lock deadlock, detected by spin lock
debugging.  Knowing the EIP would help... but timer_interrupt() is a
good first guess.

	Robert Love