From owner-freebsd-questions@FreeBSD.ORG Wed Jan 28 22:51:25 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26B88106566B for ; Wed, 28 Jan 2009 22:51:25 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id E89768FC0C for ; Wed, 28 Jan 2009 22:51:24 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id 5407EAFC1FE; Wed, 28 Jan 2009 13:51:23 -0900 (AKST) From: Mel To: freebsd-questions@freebsd.org Date: Wed, 28 Jan 2009 13:51:23 -0900 User-Agent: KMail/1.9.10 References: <497ECECD.2060403@fxclub.org> <200901281245.17970.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901281351.23115.fbsd.questions@rachie.is-a-geek.net> Cc: Subject: Re: FreeBSD 7.0 reboots on Dell 2950 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jan 2009 22:51:25 -0000 On Wednesday 28 January 2009 13:24:59 Kirk Strauser wrote: > On Jan 28, 2009, at 3:45 PM, Mel wrote: > > On Wednesday 28 January 2009 11:24:50 Kirk Strauser wrote: > >> On Tuesday 27 January 2009 10:32:57 Mel wrote: > >>> Even though 7.1 has bugfixes, this kind of guesswork causes a lot of > >>> downtime for OP without any certainty that things will be any > >>> better. > >> > >> If by "lots" you mean "2 minutes for a reboot", I'd be inclined to > >> agree. > > > > Right, you really want to do buildworld on a production machine that > > experiences random reboots. > > That would make the situation worse how? The worst case is that it > fails during installkernel, leaving him to boot from kernel.old. The worst case is 1 to N random reboots during buildworld (been there, done that), leaving the filesystem inconsistent, needing an fsck -y, unless you trust background_fsck, then finding out it's the hardware, not the OS. It's easy to find out if the OS panics, by enabling crash dumps. Then you can still decide whether an upgrade might fix it and you may even get a clue as to which hardware or kernel subsystem is affected, if the kernel dumps. I've had a machine where I never got buildworld to finish, tried 4 or 5 times hoping to get lucky this time... Reapplying thermal paste to the CPU heatsink made everything work. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.