<0>Kernel panic: Aiee, killing interupt handler!

[cmustard <cmustard@_SPAM_BLOWS_nyc.rr.com>]

Last night all was well, this morning -> no boot. 

<exerpt>
ds: 0018   es: 0018    ss: 0018
Process insmod (pid:  220,  stackpage=c05b1000)
Stack: c05ff3eo c01154e6 c032eca0 c0399d89 ffffffff 000018c9 c05b1d4c
       3 more lines of address',...

Call Trace: [<c01154e6>] [<c0107f6c>] [<c309z24>] [<c01080d2>] [<c0101a08a>]
            7 more lines of [<address>]

            7 more lines of [<address>]

Code: 0f b7 42 02 f6 c4 40 74 0c 8b 42 44 c7 00 ff ff ff ff eb 0c
 <0>Kernel paniv: Aiee, killing interupt handler!
In interrupt handler - not syncing
</exerpt>

I have been able to reboot, enter runlevel 0 fsck / and work that way but i 
can not boot cold, i will not get by problem. 

I don't think this is a debian specific problem but i am running woody 3.0 
kernel 2.4.18 on a older toshiba satellite 335cds. It's been up running great 
for a few months now, other than this.

I have not experienced this before, any ideas?

TIA

-mus