From owner-freebsd-stable@FreeBSD.ORG Mon Jan 9 17:56:00 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 178E5106566C for ; Mon, 9 Jan 2012 17:56:00 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id C706B8FC0C for ; Mon, 9 Jan 2012 17:55:59 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so4512368vcb.13 for ; Mon, 09 Jan 2012 09:55:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=iuRURRrj9QwIIIMLUKiYnYfd+p7+L91mTLzRWx3YTu4=; b=ACzIBqZwiU8AU18UFcP7swFvRfiv6+56npSqpmnE5oP19uKfumyaftuVqBiYcP39Xj pm5h1nl1vFl8DPtCWxPBhjPFzNza11o3kDDAuSuegyvPkluSxbLP4egNiCg/hAMzKbUM XpkvX9bKx5eCxoMvvB9/YwL8PjESabNYl+TKU= MIME-Version: 1.0 Received: by 10.220.156.195 with SMTP id y3mr4855974vcw.50.1326131758986; Mon, 09 Jan 2012 09:55:58 -0800 (PST) Received: by 10.220.191.130 with HTTP; Mon, 9 Jan 2012 09:55:58 -0800 (PST) In-Reply-To: References: Date: Mon, 9 Jan 2012 09:55:58 -0800 Message-ID: From: Freddie Cash To: FreeBSD Stable Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: Mon, 09 Jan 2012 17:56:00 -0000 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 hardw= are issue. Dodgy RAM is my first guess, something cooling-related is my 2nd= , and PSU is my 3rd. It is a little suspicious that you only started having= problems after your upgrade but it could be coincidence or it could be som= ething about the new software tickling the hardware differently than the ol= d. 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. If none of the above helps, we're thinking of swapping the CPUs between the two systems to see if the problems stay with the box or follow the CPU. Thanks for the reply. --=20 Freddie Cash fjwcash@gmail.com