From owner-freebsd-stable Tue Feb 9 09:05:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09782 for freebsd-stable-outgoing; Tue, 9 Feb 1999 09:05:36 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09774 for ; Tue, 9 Feb 1999 09:05:30 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id SAA23111 for freebsd-stable@FreeBSD.ORG; Tue, 9 Feb 1999 18:05:26 +0100 (CET) Received: (qmail 1048 invoked by uid 1000); 9 Feb 1999 17:04:24 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 Feb 1999 17:04:24 -0000 Date: Tue, 9 Feb 1999 18:04:24 +0100 (CET) From: Blaz Zupan To: "Chuck O'Donnell" cc: Mike Tancsa , freebsd-stable@FreeBSD.ORG Subject: Re: Spontaneous reboots In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was getting reboots under 3.0-RELEASE, almost always when the daily > scripts run. One of these reboots was directly preceeded by some disk > errors (disk and controller are new) that showed up in > /var/log/messages. I haven't seen anything since a cvsup and 'make > world' on Saturday, Feb 6. This may be an unrelated hardware problem, > don't know yet. I don't think this is the same problem. At least I don't get *ANYTHING* in any log file. If it was a bad disk, I'd notice. And meanwhile I have already replaced the disk with a bigger one and I don't think both disks are bad. I still suspect either a problem with the ed0 driver or with 486-CPU support (which after a quick scan of the relevant kernel cvs log files seems basically unchaged from 2.2.8). Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message