Date: Thu, 12 Jul 2001 13:34:18 +0900 From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp> To: Stephen Degler <sdegler@degler.net> Cc: freebsd-net@FreeBSD.ORG Subject: Re: IPV6 panic? Message-ID: <y7vr8vm935h.wl@condor.jinmei.org> In-Reply-To: <20010712002752.A36881@crusoe.degler.net> References: <20010712002752.A36881@crusoe.degler.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Thu, 12 Jul 2001 00:27:52 -0400, >>>>> Stephen Degler <sdegler@degler.net> said: > I have had several of these since 6/30, after I cvsup'ed > and rebuilt everything. I have been updating fairly frequently, > but the problem seems to persist. > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xdeadc0de > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc02c3b10 > stack pointer = 0x10:0xcbb4ff28 > frame pointer = 0x10:0xcbb4ff3c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 12 (swi6: tty:sio+) > kernel: type 12 trap, code=0 > Stopped at nd6_timer+_0x38: movl 0(%ebx),%eax db> trace > nd6_timer(0) at nd6_timer+0x38 > softclock(0) at softclock_0x30e If possible, please make the kernel core-dump, and get a back trace using gdb (and send it to the list). Also, if you find a procedure that can reproduce the panic, please let us know about it. Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?y7vr8vm935h.wl>