Date: Sat, 23 Apr 2005 09:07:26 -0400 From: Mike Tancsa <mike@sentex.net> To: =?ISO-8859-1?Q?Erik_N=F8rgaard?= <norgaard@locolomo.org> Cc: freebsd-questions@freebsd.org Subject: Re: 5.4-RC2: Unexpected reboots Message-ID: <hnhk61hc7b3h5l2nj88egdf8dge0brkcln@4ax.com> In-Reply-To: <426A25D4.5060508@locolomo.org> References: <426A25D4.5060508@locolomo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 23 Apr 2005 12:39:16 +0200, in sentex.lists.freebsd.questions you wrote: >Hi, > >I have had problems recently keeping my 5.3 up, then I upgraded to=20 >5.4-RC2. Things seemed stable, but then I just ran last: > >I didn't realise the crashes while locked in with ssh, I thought it was=20 > >Any ideas what causes this? Any ideas how I can tune syslog to grap the=20 >events? If its a software bug thats causing the machine to crash, enable dumpon so that you have at least a core dump that will tell you where the panic is. e.g. if your swap is ad0s1b dumpon -v /dev/ad0s1b Build a kernel with debug symbols (dont worry, this wont get installed, it will just be there for postmortems) by adding=20 makeoptions DEBUG=3D-g #Build kernel with symbols to your kernel and recompile then add dumpdev=3D"/dev/ad0s1b" # Device name to crashdump to (or NO). dumpdir=3D"/var/crash" # Directory where crash dumps are to be stored to /etc/rc.conf The next time you get a reboot if its due to a kernel bug, it will save the dump file in /var/crash =46or more info, see http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kern= eldebug.html#KERNELDEBUG-OBTAIN -------------------------------------------------------- Mike Tancsa, Sentex communications http://www.sentex.net Providing Internet Access since 1994 mike@sentex.net, (http://www.tancsa.com)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?hnhk61hc7b3h5l2nj88egdf8dge0brkcln>