From owner-freebsd-stable@FreeBSD.ORG Mon Jun 20 11:38:08 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 93ED316A41C for ; Mon, 20 Jun 2005 11:38:08 +0000 (GMT) (envelope-from jmartin37@speakeasy.net) Received: from mail27.sea5.speakeasy.net (mail27.sea5.speakeasy.net [69.17.117.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F6FA43D55 for ; Mon, 20 Jun 2005 11:38:08 +0000 (GMT) (envelope-from jmartin37@speakeasy.net) Received: (qmail 17981 invoked from network); 20 Jun 2005 11:38:08 -0000 Received: from adsl-211-141-154.asm.bellsouth.net (HELO [192.168.2.101]) (moonlightcheese@[68.211.141.154]) (envelope-sender ) by mail27.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Jun 2005 11:38:08 -0000 Message-ID: <42B6AA9C.1020101@speakeasy.net> Date: Mon, 20 Jun 2005 07:38:04 -0400 From: JM User-Agent: Mozilla Thunderbird 1.0.2-1.3.3 (X11/20050513) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tony Byrne 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> In-Reply-To: <1985138264.20050620121206@byrnehq.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: 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 11:38:08 -0000 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. > >Regards, > >Tony. > > > i have these same errors on my VIA 823x series chipset. however, the problem is only with the secondary device (acd0 in this case), and might be stemming from some other problem.