From owner-freebsd-stable@FreeBSD.ORG Tue Jan 10 09:22:36 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C0801065670 for ; Tue, 10 Jan 2012 09:22:36 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id DBDF28FC0C for ; Tue, 10 Jan 2012 09:22:35 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id q0A9MZ2Q006527 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 10 Jan 2012 01:22:35 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id q0A9MZGK006526; Tue, 10 Jan 2012 01:22:35 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA23946; Tue, 10 Jan 12 01:12:23 PST Date: Tue, 10 Jan 2012 08:12:04 -0800 From: perryh@pluto.rain.com To: fjwcash@gmail.com Message-Id: <4f0c6354.ua95H8JsdztgE1m0%perryh@pluto.rain.com> References: In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Upgrade from 8.2-STABLE to 9.0-RELEASE wedges on SuperMicro H8DGiF-based system 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: Tue, 10 Jan 2012 09:22:36 -0000 Freddie Cash wrote: > On Mon, Jan 9, 2012 at 9:50 AM, John Nielsen > wrote: > > From what you've said I strongly suspect that you have some > > kind of hardware issue. Dodgy RAM is my first guess ... > > That's what we're leaning toward as well. We're planning on > doing a BIOS upgrade (betadrive is running v2.00 and alphadrive > is v1.00), then a memtest86+ run, then check firmware on the > SATA controllers. I'd suggest doing the memtest86+ run first, rather than risk doing a BIOS upgrade with bad RAM (which could brick the machine).