From owner-freebsd-isp Mon Jun 19 18:58:19 2000 Delivered-To: freebsd-isp@freebsd.org Received: from bsd.amplex.net (bsd.amplex.net [209.57.124.1]) by hub.freebsd.org (Postfix) with ESMTP id B1A6337B989 for ; Mon, 19 Jun 2000 18:58:15 -0700 (PDT) (envelope-from mark@amplex.net) Received: from server2 (server3.amplex.net [209.57.124.13]) by bsd.amplex.net (8.10.1/8.10.1) with SMTP id e5K1wDo05124 for ; Mon, 19 Jun 2000 21:58:13 -0400 (EDT) From: "Mark Radabaugh - Amplex" To: Subject: RE: FreeBSD 4.0 Rebooting itself Date: Mon, 19 Jun 2000 21:58:14 -0400 Message-ID: <003801bfda5a$ff115120$0d7c39d1@amplex.net> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 In-Reply-To: <00b001bfda4c$bf58c9e0$778d25cb@halenet.com.au> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yeah - same thing with 4.0. Been meaning to ask about it but it wasn't that important at the time. I was guessing bad hardware so I threw Win2000 on it figuring I would see Blue Screen of Death but so far it keeps on ticking. Is there anything to force more logging from the kernal prior to the reboot? I wouldn't even mind if it spit something on the screen and froze (not on a production machine but while debugging it would be handy).... Mark Radabaugh Amplex (419)833-3635 mark@amplex.net > -----Original Message----- > From: owner-freebsd-isp@FreeBSD.ORG > [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Tim McCullagh > Sent: Monday, June 19, 2000 8:16 PM > To: freebsd-isp@FreeBSD.ORG > Subject: FreeBSD 4.0 Rebooting itself > > > Hi All > > I have installed FreeBSD 4.0 on 3 machines a P2 a P3 and > a pentium 166. > On each of these machines the system reboots itself between 1 > and 3 days and > there is no reference or error message in /var/log/messages, > other than the > "WARNING: / was not properly dismounted " . Originally I suspected a > hardware incompatability but on 3 different machines now > makes me wonder > whether it is a configuration error on my part. > > Is or has anyone else had a similar problem? > > > regards > > Tim > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message