From owner-freebsd-stable Tue Jul 14 10:43:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08216 for freebsd-stable-outgoing; Tue, 14 Jul 1998 10:43:12 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA08208 for ; Tue, 14 Jul 1998 10:43:11 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yw96U-0003fA-00; Tue, 14 Jul 1998 10:43:02 -0700 Date: Tue, 14 Jul 1998 10:43:01 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Eternal cc: stable@FreeBSD.ORG Subject: Re: New Bug ? In-Reply-To: <003501bdaefc$0c5aa2a0$01646464@et.foci.net> 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 On Tue, 14 Jul 1998, Eternal wrote: > I just cvsup'd around July 2nd and a did a total rebuild. > Now this week the machine has been rebooting by itself, from syslog it shows > no reboot command was initiated, so it looks like something is crashing it. > It also shows no program to which is crashing it. That is pretty consistant with RAM or other hardware failure. > If not, then it is probably a user overflowing the CPU or something of that > sort. Overflowing the CPU? That doesn't happen (or can't happen). > - Jeremy Blawn Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message