From owner-freebsd-stable@FreeBSD.ORG Mon Jun 20 11:12:02 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 1D5DF16A41C for ; Mon, 20 Jun 2005 11:12:02 +0000 (GMT) (envelope-from freebsd-current@byrnehq.com) Received: from schubert.byrnehq.com (dsl-33-12.dsl.netsource.ie [213.79.33.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86BCC43D58 for ; Mon, 20 Jun 2005 11:12:01 +0000 (GMT) (envelope-from freebsd-current@byrnehq.com) Received: from localhost (mauer.directski.com. [212.147.140.194]) by schubert.byrnehq.com (8.13.3/8.13.3) with ESMTP id j5KCBtEk011189; Mon, 20 Jun 2005 12:11:56 GMT (envelope-from freebsd-current@byrnehq.com) Date: Mon, 20 Jun 2005 12:12:06 +0100 From: Tony Byrne Organization: ByrneHQ X-Priority: 3 (Normal) Message-ID: <1985138264.20050620121206@byrnehq.com> To: Bob Bishop In-Reply-To: <6.2.0.14.2.20050620114339.04461da8@gid.co.uk> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ByrneHQ-SA-Hits: 1.455 X-Scanned-By: MIMEDefang 2.51 on 192.168.10.254 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 Reply-To: Tony Byrne 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 11:12:02 -0000 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. Regards, Tony. -- Tony Byrne