Date: Wed, 27 Dec 2006 16:25:21 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Jan Knepper <jan@digitaldaemon.com> Cc: freebsd-isp@freebsd.org, Tim McCullagh <tim@halenet.com.au>, Mario Theodoridis <mario-dated-1167617290.71c9c2@schmut.com>, FreeBSD Hackers <FreeBSD-Hackers@freebsd.org> Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... Message-ID: <45930EF1.2040105@FreeBSD.org> In-Reply-To: <4592690B.7080800@digitaldaemon.com> References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <200612261808.08984.mario@schmut.com> <4592690B.7080800@digitaldaemon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45930EF1.2040105>