Date: Fri, 1 Dec 2006 11:48:06 -0800 (PST) From: Cheng Jin <chengjin@cs.caltech.edu> To: freebsd-questions@freebsd.org Subject: 5.4 kernel crashdump not consistently working Message-ID: <Pine.LNX.4.60.0612011137080.14849@orchestra.cs.caltech.edu>
next in thread | raw e-mail | index | archive | help
hi, i have run into this strange problem of kernel crashdump not working consistently under FreeBSd 5.4. we have bunch of development machines with identical physical configurations, and every one of them is setup to save the vmcore after a panic. The difference as far as i could tell is the FreeBSD 5.4 version, which different people installed using different methods, CD, network, CVS... I followed the instructions found on the official FreeBSD site as far as i could tell. including in the kernel config file the following options options DDB options KDB options GDB options KDB_UNATTENDED include in the /etc/rc.conf file dumpdev="/dev/ad0s1b" # 2GB swap partition with 1GB of physical memory dumpdir="/usr/crash" # and making sure the dir exists crashdump works on some of these machines, but not on others, and on those that don't work, i just see Dumping 1014MB and the system just sits there. I added a printf line into the dumpsys function, and it seems that it just loops without ever writing anything to disk. for those that are curious about the details, the variables "i", "mb" are always just zero, "count goes up everytime i press a key, and "va" stays at the same memory address, and left never decreases. Comments would be greatly appreciated. Thanks! Cheng -- FAST powered network performance @626 395 8820
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.60.0612011137080.14849>