Date: Mon, 20 Jun 2005 13:02:11 +0100 From: Bob Bishop <rb@gid.co.uk> To: Tony Byrne <freebsd@byrnehq.com> Cc: freebsd-stable@freebsd.org, Tony Byrne <freebsd@byrnehq.com> Subject: Re[3]: ATA_DMA errors (and fs corruption!) Message-ID: <6.2.0.14.2.20050620123319.0477e928@gid.co.uk> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.2.0.14.2.20050620123319.0477e928>