Date: Thu, 09 Dec 2004 08:32:43 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: Garance A Drosihn <drosih@rpi.edu> Cc: Tim Welch <freebsd-stable@thepentagon.org> Subject: Re: DMA errors with SATA on 5.x [one fix] Message-ID: <41B7FF9B.4050700@DeepCore.dk> In-Reply-To: <p0620075ebddd86599603@[128.113.24.47]> References: <55368.65.7.255.129.1102402914.squirrel@65.7.255.129> <p0620075ebddd86599603@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
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<READY,DSC,ERROR> >> error=3D10<NID_NOT_FOUND> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41B7FF9B.4050700>