From owner-freebsd-stable@FreeBSD.ORG Tue Dec 7 06:04:20 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 BB68916A4CE for ; Tue, 7 Dec 2004 06:04:20 +0000 (GMT) Received: from thepentagon.org (mail.thepentagon.org [12.168.180.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59CE843D60 for ; Tue, 7 Dec 2004 06:04:20 +0000 (GMT) (envelope-from freebsd-stable@thepentagon.org) Received: from webmail.thepentagon.org (localhost [127.0.0.1]) by thepentagon.org (8.12.11/8.12.11) with ESMTP id iB771spJ027797 for ; Tue, 7 Dec 2004 01:01:54 -0600 Received: from adsl-065-007-255-129.sip.jan.bellsouth.net ([65.7.255.129]) (SquirrelMail authenticated user twelch); by webmail.thepentagon.org with HTTP; Tue, 7 Dec 2004 01:01:54 -0600 (CST) Message-ID: <55368.65.7.255.129.1102402914.squirrel@65.7.255.129> Date: Tue, 7 Dec 2004 01:01:54 -0600 (CST) From: "Tim Welch" To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.5.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: DMA errors with SATA on 5.x 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: Tue, 07 Dec 2004 06:04:20 -0000 I'm getting NID not found/DMA errors on 5-STABLE with a Seagate 200gb sata drive: ad2: FAILURE - WRITE_DMA status=51 error=10 LBA=268435455 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.html 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? uname -a: FreeBSD mercury 5.3-STABLE FreeBSD 5.3-STABLE #0: Mon Dec 6 21:51:28 CST 2004 root@mercury:/usr/obj/usr/src/sys/mercury i386 Thanks, Tim