Re: Kernel Panic: bad isr 0

[TC Lewis <tfox@xxxxxxxxxxxxxxxxxxxxxxxx>]

> :panic: bad isr 0
> :Debugger("panic")
> :Stopped at      Debugger+0x34: movb     $0,in_Debugger.339
> :
> :Debugger trace reports: (as best as I can see by my craning my neck 
> around
> :and reading from the monitor behind me)
> :
> :Debugger(c03c4d58,c0166ffb,c02b384d,c02eee78,c02e6a6c) at Debugger+0x34
> :dumpmag(73252228,a2922,0,0,0) at dumpmag+0x1b9
> :
> :Thanks in advance ;)
> :
> :-TFox-
>
>     hmm.  The backtrace isn't good.  There are three places where this
>     panic can occur.  I just committed a change to net/netisr.c that
>     does not fix the problem but does clarify which of those three
>     places is generating the panic.
>
>     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
> 			value.
>
>     Also be sure that you are not looking at a double fault.  Is the 
> above
>     panic the initial panic message or did it occur due to another 
> earlier
>     panic?
>
> 					-Matt
> 					Matthew Dillon
> 					<dillon@xxxxxxxxxxxxx>

	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/