From owner-freebsd-stable@FreeBSD.ORG Thu Dec 9 07:33:09 2004 Return-Path: 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 ADCE216A4CE for ; Thu, 9 Dec 2004 07:33:09 +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 CDFCE43D46 for ; Thu, 9 Dec 2004 07:33:08 +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.12.11/8.12.10) with ESMTP id iB97X2Oa053733; Thu, 9 Dec 2004 08:33:05 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <41B7FF9B.4050700@DeepCore.dk> Date: Thu, 09 Dec 2004 08:32:43 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Garance A Drosihn References: <55368.65.7.255.129.1102402914.squirrel@65.7.255.129> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-stable@freebsd.org cc: Tim Welch Subject: Re: DMA errors with SATA on 5.x [one fix] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 07:33:09 -0000 Garance A Drosihn wrote: > At 1:01 AM -0600 12/7/04, Tim Welch wrote: >=20 >> I'm getting NID not found/DMA errors on 5-STABLE with a Seagate 200gb >> sata drive: >> >> ad2: FAILURE - WRITE_DMA status=3D51 >> error=3D10 LBA=3D268435455 >> >> This appears to be a result of 48-bit addressing. Any time a write is >> attempted to the sector above, I get multiple messages like this. It >> continues until I shut down. After a bit of googling I found this post= : >> >> http://lists.freebsd.org/pipermail/freebsd-hackers/2004-October/008821= =2Ehtml=20 >> >> >> and applied the change suggested. It seems to have fixed the problem, >> and I've had no troubles from this since Nov. 18th when I applied that= >> patch. I'm running an Intel 875PBZ board with the ich5 controller. >> The drive in question is a Seagate ST3200822AS/3.01 (as reported by >> dmesg). So the question is, will this patch be committed anytime soon?= >=20 >=20 > That looks like a pretty safe patch to make. The message says he > just reduced the 48-bit trigger level by one: Yes, I suggested that way back on the lists, and it seems to help those=20 that had this problem. I have had it for quite some time in ATA-mkIII=20 here as well, and since it has no real impact otherwise I've committed=20 it to -current... --=20 -S=F8ren