From owner-freebsd-stable@FreeBSD.ORG Mon Jun 20 16:30:11 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 F0BA016A449 for ; Mon, 20 Jun 2005 16:30:11 +0000 (GMT) (envelope-from jmartin37@speakeasy.net) Received: from mail28.sea5.speakeasy.net (mail28.sea5.speakeasy.net [69.17.117.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEF3743D1F for ; Mon, 20 Jun 2005 16:30:11 +0000 (GMT) (envelope-from jmartin37@speakeasy.net) Received: (qmail 16564 invoked from network); 20 Jun 2005 16:30:11 -0000 Received: from adsl-211-141-154.asm.bellsouth.net (HELO [192.168.2.101]) (moonlightcheese@[68.211.141.154]) (envelope-sender ) by mail28.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Jun 2005 16:30:11 -0000 Message-ID: <42B6EF10.6090104@speakeasy.net> Date: Mon, 20 Jun 2005 12:30:08 -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: jay@codegurus.org References: <20050620120030.6818B16A420@hub.freebsd.org> <42B6D6BC.4000208@codegurus.org> In-Reply-To: <42B6D6BC.4000208@codegurus.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: ATA_DMA errors (and fs corruption!) (JM) 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 16:30:12 -0000 Jayton Garnett wrote: > I had a similar problem and i changed system cases where i was getting > a ICRC error and FreeBSD refused to load or even mount the root fs, it > was also giving errors with something to do with the ATA something or > other, it turned out to be the cable i used after rebuilding the > system in the new case, i used a normal EIDE cable instead of a ATA > cable :-/ > > hope that helps(probably not) actually, that makes a lot of sense. my computer running FreeBSD is actually just an Eden 5000 V-series. the cable is trimmed to fit the 2.5" hard drive in the tiny case and i'm sure this is having something to do with the timeouts... however the harddrive is recognized as UDMA33 but the cdrom still times out. thanks for the input. note: this setup works fine in windows... maybe someone should take a look at this issue? i'm running the old 5.3-RELEASE (too lazy to update) with a VIA VT8231 SouthBridge (82xxxx ata controller). > > Jay > >> >> 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. >> >> >> > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"