Missed clock interrupts...

[Johnny Billquist <bqt%softjar.se@localhost>]

Ok.
First success in trying to figure out where the system might be spending 
unreasonable amounts of time.

Just thought I'd send this in, in case someone have any good ideas 
before I continue digging...

db> bt
panic: Missed clock interrupt!

Stack traceback :
0x86afed1c: bqtbug+0x40(0x18,0)
0x86afed6c: mi_switch+0x146(0x81ab92e0)
0x86afeda0: sleepq_block+0x5a(0,0x1)
0x86afedd8: cv_wait_sig+0x7c(0x81919b54,0x83bddfb4)
0x86afee0c: do_sys_wait+0x105(0x86afef08,0x86afef0c,0,0)
0x86afee78: sys___wait450+0x30(0x81ab92e0,0x86afef4c,0x86afef74)
0x86afef14: syscall+0x89(0x86afefb4)

bqtbug() is my small catch function that triggers a panic in case the 
system now is lowering spl to allow for a clock interrupt, and the clock 
hardware indicates that a clock interrupt have been missed.

        Johnny

--
Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
email: bqt%softjar.se@localhost             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol