Panic on 4.10 (Not sure of Cause)

Kyle Mott kyle at xraided.net
Fri Jun 18 00:14:22 GMT 2004


I just recently (within the past 45 minutes) had a panic on an SMP 
system (HP Netserver LH3). I've posted output of gdb and uname below. 
I'm not much of a programmer, so I don't really know A) what exactly I'm 
looking at, B) If this information is useful, and C) If there's anything 
I can do to remedy the situation. I can post kernel configs and whatnot 
as needed. Thank's for your help.

Also, what are the gdb errors from? (Deprecated bfd_read... etc.)



root at smith:/usr/crash# gdb -k kernel.debug.03-20-2004 vmcore.0
GNU gdb 4.18 (FreeBSD)
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read 
called at 
/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c 
line 2627 in elfstab_build_psymtabs
Deprecated bfd_read called at 
/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c 
line 933 in fill_symbuf
SMP 0 cpus
IdlePTD at physical address 0x00000000
initial pcb at physical address 0x00312280
panic messages:
---
dmesg: kvm_read: invalid address (c03097f8)
---
 
cannot read proc pointer at ffc00004
 
(kgdb) where
#0  0x160c in ?? ()
cannot read proc at 0
(kgdb)


uname -a: FreeBSD smith.klmhosting.net 4.10-STABLE FreeBSD 4.10-STABLE 
#0: Wed Jun  9 02:30:43 PDT 2004     
kyle at smith.klmhosting.net:/usr/obj/usr/src/sys/SECURITY  i386


-Kyle Mott




More information about the freebsd-stable mailing list