lock? panic in networking swi

2003-03-07 Thread Juli Mallett

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x20
fault code  = supervisor read, page not present
instruction pointer = 0x8:0xc01d47c6
stack pointer   = 0x10:0xc5d33a90
frame pointer   = 0x10:0xc5d33ab4
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 14 (swi1: net)
trap number = 12
panic: page fault

No core, of course, nm says the ip is likely:
_mtx_unlock_sleep

Thoughts?  This is a kernel from last weekend, I'll try to get something
more recent soon.

FWIW, I'm reproducing these by running gtk-gnutella and telling it to
auto-download anything with talk talk in it, which due to its wonderful
anti-foot-shooting algorithms means it downloads everything with talk in
it, which is quite a lot.

Thanx,
juli.
-- 
juli mallett. email: [EMAIL PROTECTED]; aim: bsdflata; efnet: juli;

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


RE: lock? panic in networking swi

2003-03-07 Thread John Baldwin

On 07-Mar-2003 Juli Mallett wrote:
 
 Fatal trap 12: page fault while in kernel mode
 fault virtual address = 0x20
 fault code= supervisor read, page not present
 instruction pointer   = 0x8:0xc01d47c6
 stack pointer = 0x10:0xc5d33a90
 frame pointer = 0x10:0xc5d33ab4
 code segment  = base 0x0, limit 0xf, type 0x1b
   = DPL 0, pres 1, def32 1, gran 1
 processor eflags  = interrupt enabled, resume, IOPL = 0
 current process   = 14 (swi1: net)
 trap number   = 12
 panic: page fault
 
 No core, of course, nm says the ip is likely:
   _mtx_unlock_sleep
 
 Thoughts?  This is a kernel from last weekend, I'll try to get something
 more recent soon.

Probably an uninitialized mutex or some such.  A stack trace would help.

-- 

John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message