Date: Sun, 24 Apr 2005 11:58:19 -0400 From: Paul Mather <paul@gromit.dlib.vt.edu> To: =?ISO-8859-1?Q?S=F8ren?= Schmidt <sos@DeepCore.dk> Cc: freebsd-current@freebsd.org Subject: Re: Fatal TIMEOUT - WRITE_DMA errors return with ATA Mk.III Message-ID: <1114358299.77313.2.camel@zappa.Chelsea-Ct.Org> In-Reply-To: <426B61FF.80001@DeepCore.dk> References: <1114305707.71309.40.camel@zappa.Chelsea-Ct.Org> <426B61FF.80001@DeepCore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2005-04-24 at 11:08 +0200, S=F8ren Schmidt wrote:
> Paul Mather wrote:
> > Since somewhere in the 5.x release cycle, my system has fallen prey to
> > the "TIMEOUT - WRITE_DMA" errors which result in the drive becoming
> > detached (which causes my geom_mirror to break and require rebuilding).
> > According to smartctl and disk diagnostics, there's nothing wrong with
> > my drives. Plus, the problem does not manifest itself under 4-STABLE.
> > (I'm not the only one to have reported this problem.)
> >=20
> > Lately, I'd had success using a patch posted to freebsd-current by Ian
> > Dowse. The "TIMEOUT - WRITE_DMA" errors still occurred, but they
> > weren't fatal. I updated my kernel and world recently, and, alas, the
> > "TIMEOUT - WRITE_DMA" problem has returned once more:
>=20
> You should try a recent -current, I committed cleanups to the timeout=20
> system on the 21'st. You might still have timeouts (which might due to=20
> non-ATA issues) but they should not be fatal unless the HW really does=20
> screw up..
Many thanks! I'll try an upgrade and see if that fixes things.
Cheers,
Paul.
--=20
e-mail: paul@gromit.dlib.vt.edu
"Without music to decorate it, time is just a bunch of boring production
deadlines or dates by which bills must be paid."
--- Frank Vincent Zappa
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1114358299.77313.2.camel>