From owner-freebsd-stable@FreeBSD.ORG Mon Jun 20 12:02:36 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B36916A41C for ; Mon, 20 Jun 2005 12:02:36 +0000 (GMT) (envelope-from rb@gid.co.uk) Received: from gidgate.gid.co.uk (gid.co.uk [194.32.164.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4970D43D1F for ; Mon, 20 Jun 2005 12:02:35 +0000 (GMT) (envelope-from rb@gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.11.7/8.11.6) id j5KC2K110612; Mon, 20 Jun 2005 13:02:20 +0100 (BST) (envelope-from rb) Message-Id: <6.2.0.14.2.20050620123319.0477e928@gid.co.uk> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 20 Jun 2005 13:02:11 +0100 To: Tony Byrne From: Bob Bishop In-Reply-To: <1985138264.20050620121206@byrnehq.com> References: <8d02aed00506181404642100b9@mail.gmail.com> <42B5DAEA.4040908@nurfuerspam.de> <8d02aed005061918049c8fd8@mail.gmail.com> <67335859.20050620110953@byrnehq.com> <6.2.0.14.2.20050620114339.04461da8@gid.co.uk> <1985138264.20050620121206@byrnehq.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-stable@freebsd.org, Tony Byrne Subject: Re[3]: ATA_DMA errors (and fs corruption!) 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, 20 Jun 2005 12:02:36 -0000 At 12:12 20/06/2005, Tony Byrne wrote: >Hello Bob, > > > >>can be hardware reasons for timeouts such as a dying disk or cable, > >>but I think we've eliminated these in our case. [etc] > >BB> Don't ignore the possibility of failing controller hardware. We had >BB> comparable mysterious problems on a client system, causing a lot of >BB> head-scratching. Eventually the failure went hard and we had to >replace the >BB> motherboard. > >I hear ya! However, moving back to an older kernel changes the >severity of the problem from a timeout every 2 to three minutes during >heavy activity to about 4 or 5 in a 24 hour period. That doesn't >sound like hardware to me. It didn't to me either. Note the use of 'mysterious' :-) I'd eliminated drives and cables, and then did it all over again when the failure went hard, leaving the controller (or something else on the mobo). With a new mobo all the annoying timeouts which I'd put down to driver misbehaviour just went away. -- Bob Bishop +44 (0)118 940 1243 rb@gid.co.uk fax +44 (0)118 940 1295