From owner-freebsd-isp@FreeBSD.ORG Thu Dec 28 00:52:05 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 72F9E16A403 for ; Thu, 28 Dec 2006 00:52:05 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 0C43313C473 for ; Thu, 28 Dec 2006 00:52:04 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 17252 invoked by uid 399); 28 Dec 2006 00:25:23 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 28 Dec 2006 00:25:23 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45930EF1.2040105@FreeBSD.org> Date: Wed, 27 Dec 2006 16:25:21 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061215) MIME-Version: 1.0 To: Jan Knepper References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <200612261808.08984.mario@schmut.com> <4592690B.7080800@digitaldaemon.com> In-Reply-To: <4592690B.7080800@digitaldaemon.com> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-isp@freebsd.org, Tim McCullagh , Mario Theodoridis , FreeBSD Hackers Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD-stable@freebsd.org List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Dec 2006 00:52:05 -0000 [Attempting to redirect this to -stable, where it's more appropriate.] Jan Knepper wrote: > FreeBSD 5.x branch run on that machine for almost 2 years without a > problem and magically the same time period in *hours* that I upgrade the > machine I get hardware problems too? Not an impossible coincidence, but > not very likely... Depends on how you did the upgrade. Was the machine running continuously for 2 years, then you turned it off, then you did the upgrade? I had a box die that way because (we found out later) that the system drive's spindle had "issues" that were not apparent until it had been turned off, cooled down, then spun (sort of) back up. IOW, you're probably right, but "magical" hardware problems that develop during upgrade periods are more common than a lot of people realize. Meanwhile, back at the ranch, if you can't easily get a serial console up and running, your earlier suggestion of putting the box back to the last known good 5.x release is a good one. At least that can help rule out hardware _failure_, as opposed to hardware-used-differently issues. hth, Doug -- This .signature sanitized for your protection