Am Fri, 15 May 2009 08:15:19 -0400
schrieb John Baldwin <j...@freebsd.org>:
Hi John,
> When I have seen this, it has often been due to a hardware failure
> such as bad RAM.
hmmm... I will check this next week.
> > cpuid = 2; apic id = 02
> > instruction pointer = 0x8:0xffffffff805bbc66
>
> Can you do 'x/i 0xffffffff805bbc66'? Also, can you walk up the stack
> to the frame for this panic ('frame 7') and do 'info registers'?
(kgdb) x 0xffffffff805bbc66
0xffffffff805bbc66 <rt_maskedcopy+6>: 0x4912b60f
(kgdb) frame 7
#7 0xffffffff805bbc66 in rt_maskedcopy (src=0xffffffff51e2e6c8,
dst=0xffffff00525ebd80, netmask=0xef3fdf377db53afa)
at /usr/src/sys/net/route.c:1362
1362 {
(kgdb) info registers
rax 0xffffff00525ebd80 -1098129687168
rbx 0xffffff0006b570f8 -1099399073544
rcx 0x10 16
rdx 0xef3fdf377db53afa -1207000745686779142
rsi 0xffffff00525ebd80 -1098129687168
rdi 0xffffffff51e2e6c8 -2921142584
rbp 0xffffffff51e2e4c0 0xffffffff51e2e4c0
rsp 0xffffffff51e2e428 0xffffffff51e2e428
r8 0x0 0
r9 0xef3fdf377db53afa -1207000745686779142
r10 0xffffff00016eba50 -1099487593904
r11 0xffffffff80b3eec0 -2135691584
r12 0xe22173e466d29aa0 -2152311722091570528
r13 0xffffff0006832c00 -1099402368000
r14 0xef3fdf377db53afa -1207000745686779142
r15 0x0 0
rip 0xffffffff805bbc66 0xffffffff805bbc66 <rt_maskedcopy+6>
eflags 0x10286 66182
cs 0x8 8
ss 0x10 16
ds 0x0 0
es 0x0 0
fs 0x0 0
gs 0x0 0
I hope it helps.
--
Martin
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
