From owner-freebsd-stable@FreeBSD.ORG Tue Sep 16 19:34:12 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFE51106566C; Tue, 16 Sep 2008 19:34:12 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 7891F8FC08; Tue, 16 Sep 2008 19:34:12 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m8GJY9cb022666; Tue, 16 Sep 2008 15:34:10 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m8GJY9oe039218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Sep 2008 15:34:09 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200809161934.m8GJY9oe039218@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 16 Sep 2008 15:34:07 -0400 To: Jeremy Chadwick , Clint Olsen From: Mike Tancsa In-Reply-To: <20080916185401.GA71275@icarus.home.lan> References: <20080916170452.GB4861@0lsen.net> <20080916175858.GA70396@icarus.home.lan> <20080916181903.GC7540@0lsen.net> <20080916185401.GA71275@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: stable@freebsd.org Subject: Re: Help debugging DMA_READ errors 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, 16 Sep 2008 19:34:12 -0000 At 02:54 PM 9/16/2008, Jeremy Chadwick wrote: >However, there's no sign of DMA errors in the SMART log. I'm not sure >what to make of that; I really would expect there to be some. Would not bad cables (or trays) be consistent with symptoms like that ? i.e. the OS sees errors, but when we ask the drive, it says, "what errors". I am sure there are other things that could cause this, but in the past I would start with the cables and or trays. ---Mike