Kernel Panic: bad isr 0
TC Lewis
tfox at dimension-4.dnsalias.net
Sun Nov 23 04:07:35 PST 2003
On Sat, 22 Nov 2003 21:42:36 -0800 (PST), Matthew Dillon
<dillon at xxxxxxxxxxxxxxxxxxxx> wrote:
: 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
:world and
: kernel.
:
: 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
: Debugger("panic")
: Stopped at Debugger+0x34: movb $0,in_Debugger.339
: db>
:
: 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.
-Matt
Matthew Dillon
<dillon at xxxxxxxxxxxxx>
The latest and greatest kernel panic, hope you enjoy it as much as I have
;)
panic: netisr_register: bad isr 0
blah blah blah same as before looks like.
Asmodai said you might want the register... info. I'm still not clear on
what
most of this is, but here you go anyway.
cs 0x8 gd_curthread+0x4
ds 0xc0280010 outb+0x39c
es 0x10 gd_reqflags+0x4
fs 0x18 gd_reqflags+0xc
ss 0x10 gd_reqflags+0x4
eax 0x12 gd_reqflags+0x6
ecx 0xffffffff APTD+0xfff
edx 0x10 gd_reqflags+0x4
ebx 0xc02b0d23
esp 0xc03a6d38
ebp 0xc03a6d40
esi 0x100 gd_reqflags+0xf4
edi 0x1
eip 0xc0277284 Debugger+0x34
efl 0x80246
dr0 0
dr1 0
dr2 0
dr3 0
dr4 0xffff0ff0
dr5 0x400 gd_cnt+9x2bc
dr6 0xffff0ff0
dr7 0x400 gd_cnt+0x2bc
Debugger+0x34: movb $0,0xc0319160
don't quote me on all of that, it's to the best of my neck-craning
skills' ability.
More information about the Bugs
mailing list