Date: Mon, 14 Feb 2005 09:39:53 +0100 From: Gerald Heinig <gheinig@syskonnect.de> To: Ashwin Chandra <ashcs@ucla.edu> Cc: freebsd-hackers@freebsd.org Subject: Re: VMCORE NOT FOUND Message-ID: <421063D9.5060401@syskonnect.de> In-Reply-To: <001001c51149$95f085a0$58e243a4@ash> References: <001901c510e1$aecc7c90$58e243a4@ash> <200502122218.42458.doconnor@gsoft.com.au> <003201c5113e$c56321e0$58e243a4@ash> <2777.24.107.98.253.1108241734.squirrel@24.107.98.253> <001001c51149$95f085a0$58e243a4@ash>
next in thread | previous in thread | raw e-mail | index | archive | help
Ashwin Chandra wrote: > ryan, > i think i was a bit vague in my email. I am correctly usnig the swap > device and dump directory. Before the system reboots the core should be > saved from the swap device (before it mounts) and into the path that i > specified. dumpdev="/dev/ad0s1b", our 2gb swap device and > dumpdir="/usr/crash" > So I am doing all this correctly, yet still no dump comes up and I am > not sure why! =( Hi Ashwin, for what it's worth, I have exactly the same problem on my Dell GX 260/FreeBSD 5.3 RELEASE machine. When it panics, it says it's starting to write a dump, but doesn't continue. The disk lights remain off, so there's definitely no activity. Strangely enough, when I use my Dual Tyan box (AMD-based) with a kernel compiled with the same config file, I get a dump without ahny problems. I mentioned this on -hackers a few weeks ago. Cheers, Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?421063D9.5060401>