Re: 3.0 kernel crash (network related)

[Niklas Hallqvist <niklas@appli.se>]

> Date: Wed, 5 Dec 2001 10:01:28 +0100
> From: Toni Mueller <openbsd-tech@oeko.net>
> 
> ddb> trace
> _Debugger(0,e0595cb0,80,210,1401a8c0,e0901138,e9f25c18,e01b273f,e0162437,e01c3ddd,e0901100,e9r25c2c,90,e089be40,80,e9f25c3c,e01c8e6b,e0901154,e9f25c48,e014f257,e0595cb0,0,e08f2200,e9f25cec,e089fd00,e089be40,e962b800,e9f25cec,e02215fa,e0901100,e9f25c98,e014e6b8,e088a000,e089fd00,e962e824,4,e0867aa0,e0595cb0,e08f2200,e0863100,e088a040,800,e9f25c98,e0168ee7,40881000,e962b806,0,1,e088a040,e088a000,e9f25ca0,e0101a1d,e088a000,80,10,e0900010,e08f2200,e0959cb0,e9f25cf8,e089d700,10) at _Debugger+0x4
> _panic(e01b2437,e01c3ddd,e0901100,e9f25c2c,90) at _panic+0x81
> _pool_get(e0595cb0,0,e08f2200,e9f25cec,e089fd00) AT _pool_get+0x223
> _fxp_add_rfabuf(e088a000,e089fd00,e962e824,4) at fxp_add_rfabuf+0x33
> _fxp_intr(e088a000) at _fxp_intr+0x1e0
> _Xrecurse10() at _Xrecurse10+0x79
> ---interrupt---
> _pool_get(e0595cb0,0,80,4,e090b800) at _pool_get+0x2c6
> _tcp_output(e08f2200,1,e9e77870,e9f25f24) at _tcp_output+0x8ef
> _tcp_userreq(e0901100,8,0,e0863100,e9f25ed8,e01b93ee) at _tcp_userreq+0x46e
> _soreceive(e0901100,0,e9f25ed8,0,0) at _soreceive+0xa80
> _soo_read(e9e58738,e9e58754,e9f25ed8,e0882600,e9f25f88) at _soo_read+0x1f
> _dofileread(e9e778870,5,e9e58738,dfbf9378,4000) at _dofileread+0x7d
> _sys_read(e9e77870,e9f25f88,e9f25f80,400000c0,0) at _sys_read+0x44
> _syscall() at _syscall+0x242
> ---syscall (number 3)---
> 0x401fcae7

As art said this can't happen! :-)

But, it could... What date did you rsync, can you look at the
CVS version of src/sys/arch/i386/isa/isa_machdep.c?  There
was a window roughly two weeks ago where this was possible,

Can you show us the output from

dmesg | grep irq

?  I bet you have irq sharing on irq10 with some audio device.
If so just rsync a newer tree.

Niklas