From owner-freebsd-questions  Mon Jul 27 07:31:40 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA25192
          for freebsd-questions-outgoing; Mon, 27 Jul 1998 07:31:40 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from mailhost.criterion.canon.co.uk (cruella.criterion.canon.co.uk [194.223.249.254])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25185
          for <questions@FreeBSD.ORG>; Mon, 27 Jul 1998 07:31:32 -0700 (PDT)
          (envelope-from adamn@criterion.canon.co.uk)
Received: from csl.com (hermes.criterion.canon.co.uk [194.223.249.13]) by mailhost.criterion.canon.co.uk (8.8.8/8.7.3) with ESMTP id PAA20200 for <questions@FreeBSD.ORG>; Mon, 27 Jul 1998 15:25:53 +0100 (BST)
Message-ID: <35BC8E57.71179C7B@csl.com>
Date: Mon, 27 Jul 1998 15:27:35 +0100
From: Adam Nealis <adamn@criterion.canon.co.uk>
Organization: Criterion Software, Ltd.
X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.34 i686)
MIME-Version: 1.0
To: questions@FreeBSD.ORG
Subject: Re: Reboots Automaticly
References: <000001bdb908$b1f5e100$70a019cb@jason.webace.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Jason McKay wrote:

> Hello,
>
> I am running a P266 MMX, 64megs of RAM with FreeBSD 2.2.6-RELEASE.  It has
> started to reboot with out notice or reason.  Below is the log of automatic
> reboots so far:
>
> reboot   ~                         Mon Jul 27 10:38
> reboot   ~                         Mon Jul 27 09:01
> reboot   ~                         Sun Jul 26 12:16
> reboot   ~                         Thu Jul 23 21:24
> reboot   ~                         Fri Jul 17 19:41
> reboot   ~                         Mon Jul 13 15:45
> reboot   ~                         Sat Jul 11 21:04
> reboot   ~                         Fri Jul 10 07:01
>
> No error messages are reported.  Any suggestions?

Nooo, but if you put

dumpdev="YES"

in /etc/rc.conf

and check that there is something like

# enable dumpdev so that savecore can see it
# /var/crash should be a directory or a symbolic link
# to the crash directory if core dumps are to be saved.
if [ "X${dumpdev}" != X"NO" -a -e ${dumpdev} -a -d /var/crash ]; then
        dumpon ${dumpdev}
        echo -n checking for core dump...
        savecore /var/crash
fi

/etc/rc

then have a look in /var/crash for savecore.? files. Hmm... better ask others
what to do to find out _why_ the kernels panicked (if that is indeed what
happened).

Adam.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message