DragonFly bugs List (threaded) for 2003-11
Re: Kernel Panic: bad isr 0
: Alright just for fun here, I'm going to post a few extra lines, exactly
:as they appear.
: This is a brand new compile. I redownloaded source, and rebuilt/installed
: sc0: <System console> at flags 0x100 on isa0
: sc0: VGA <16 virtual consoles, flags=0x300>
: installed MI handler for int 0
: installed MI handler for int 8
: panic: bad isr 0
: Stopped at Debugger+0x34: movb $0,in_Debugger.339
: Given this information, I'm not sure what you mean by;
: > See if you can get a better trace by trying different stack pointers
: > (starting the reported stack pointer and incrementing by 4, in hex),
: > e.g.
: > trace 0xblahblah where 0xblahblah starts at the reported stack
: > pointer
:Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
Hmm. Your kernel sources are still out of date, there are no more
'bad isr' panics. Instead it now says:
netisr_queue: bad isr %d"
netisr_register: bad isr %d"
unregister_netisr: bad isr number: %d\n"
schednetisr: bad isr %d"
I'm not sure why it isn't showing the stack pointer but from the DB>
prompt you should be able to 'show regi' to observe the register set.
%esp is the stack pointer.
I know this isn't all that helpful. I wish trace would work better.
Maybe post your kerel config to the list too, you might have a weird
option or something set that is causing the trace not to work right.