From owner-freebsd-hackers  Mon Dec  4 06:12:37 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id GAA04155
          for hackers-outgoing; Mon, 4 Dec 1995 06:12:37 -0800
Received: from bigbird.vmicls.com (bigbird.vmicls.com [198.17.96.3])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA04149
          for <hackers@freebsd.org>; Mon, 4 Dec 1995 06:12:35 -0800
Received: from gonzo by bigbird.vmicls.com (8.6.9/SMI-4.1-vmicls-master-host-1)
	id JAA15171; Mon, 4 Dec 1995 09:15:08 -0500
From: Jerry.Kendall@vmicls.com (Jerry Kendall)
Organization: VMI Communications and Learning Systems
Received: by gonzo (5.0/vmi-client-host-1) id AA28479; Mon, 4 Dec 1995 09:15:06 +0500
Date: Mon, 4 Dec 1995 09:15:06 +0500
Message-Id: <9512041415.AA28479.gonzo@vmicls.com>
To: uhclem%nemesis@fw.ast.com, hackers@freebsd.org
Subject: Re: Mission Impossible-style crashes on 2.1.0
X-Sun-Charset: US-ASCII
content-length: 1178
Sender: owner-hackers@freebsd.org
Precedence: bulk

> I have several systems (6) that I recently upgraded to 2.1.0-RELEASE.
> These systems all ran 2.0.5 previously, and had no crashes in at
> least the previous 90 days (very nice).
> 
> However, in the seven days since upgrading to 2.1.0, the same hardware
> has experienced an average of 10 unexpected reboots, or just over
> one a day.  The systems with more load (news vs no news) crash more often.

Frank, I had a similar problem with 2.0.5R.
My situation was all based on my systems rebooting at 02:01:00 EVERY single
day. After much looking around, I found that this was when /etc/security was
being run via cron. I could run it manually and it was OK. If cron ran it,
the system would silently reboot.

It would reboot when it tried the check my CDROM. I realize that your
problem is not with CDROM drives, but maybe having a CDROM drive is
only the catalyst for a bigger problem that my system no longer exhibits due
to some other change that I made.

Try to see if it happens at the same time every day or perhaps in some sequence.
If so, check out the /etc/crontab file to see if there is something
being started when the system reboots.


Hope this helps....


Jerry