From owner-freebsd-current@FreeBSD.ORG Sun Apr 24 09:10:11 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 141B116A4CE for ; Sun, 24 Apr 2005 09:10:11 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E02543D3F for ; Sun, 24 Apr 2005 09:10:10 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.13.3/8.13.3) with ESMTP id j3O99hrI038159; Sun, 24 Apr 2005 11:09:43 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <426B61FF.80001@DeepCore.dk> Date: Sun, 24 Apr 2005 11:08:15 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0 (X11/20050116) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Paul Mather References: <1114305707.71309.40.camel@zappa.Chelsea-Ct.Org> In-Reply-To: <1114305707.71309.40.camel@zappa.Chelsea-Ct.Org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.12 cc: freebsd-current@freebsd.org Subject: Re: Fatal TIMEOUT - WRITE_DMA errors return with ATA Mk.III X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2005 09:10:11 -0000 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: 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.. --=20 -S=F8ren