From owner-freebsd-stable@FreeBSD.ORG Wed Aug 16 01:32:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F8B916A4DA for ; Wed, 16 Aug 2006 01:32:17 +0000 (UTC) (envelope-from darren@nighttide.net) Received: from olmec.nighttide.net (jasper.nighttide.net [207.5.141.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED75A43D46 for ; Wed, 16 Aug 2006 01:32:16 +0000 (GMT) (envelope-from darren@nighttide.net) Received: from olmec.nighttide.net (darren@localhost [127.0.0.1]) by olmec.nighttide.net (8.13.6/8.13.6) with ESMTP id k7G1WFka050141; Tue, 15 Aug 2006 21:32:15 -0400 (EDT) (envelope-from darren@nighttide.net) Received: from localhost (darren@localhost) by olmec.nighttide.net (8.13.6/8.13.6/Submit) with ESMTP id k7G1WFZ7050138; Tue, 15 Aug 2006 21:32:15 -0400 (EDT) (envelope-from darren@nighttide.net) X-Authentication-Warning: olmec.nighttide.net: darren owned process doing -bs Date: Tue, 15 Aug 2006 21:32:15 -0400 (EDT) From: Darren Henderson To: "Android Andrew [:]" In-Reply-To: <44E19FF2.9080709@oberon.pfi.lt> Message-ID: <20060815212146.A50002@olmec> References: <44E19FF2.9080709@oberon.pfi.lt> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1-STABLE: Unexplained power off X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Aug 2006 01:32:17 -0000 On Tue, 15 Aug 2006, Android Andrew [:] wrote: > My system (FreeBSD callisto 6.1-STABLE FreeBSD 6.1-STABLE #4: Mon Aug 14 > 13:32:00 EEST 2006 root@callisto:/usr/obj/usr/src/sys/callisto i386) powers > down during compilation - doesn't matter it is any port (kde, openoffice) or > "make -j4 buildworld". Computer powers off without any message (screen, or The last time I saw something like this it turned out to be a memory issue. Frustraiting as hell, only effected certain compiles but always repeatble. It would get to a certain point, halt, and then reboot, no warnings, no messages. I could do a buildworld just fine but something like compiling pike caused it to tank - eventually it started doing it with something as mundane as pine. Memory passed all the tests the various utilities threw at it. Swaped out some of the ram and the problem went away. Problems like this are never fun to find. -Darren ______________________________________________________________________ Darren Henderson darren@nighttide.net Help fight junk e-mail, visit http://www.cauce.org/