Ok, I applied the ata mkiii patches onto my freebsd 5.4 on our least
important machine that I was speaking of in my first email here, and, so
far, for an hour, no read or write dma errors! Running udma now instead
of pio4 which I had to use before. Massive speed difference of course.
This is
Steve wrote:
If anyone has that link handy, please post. (for the patch)
http://people.freebsd.org/~sos/ATA/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
On Wed, 20 Jul 2005, Steve wrote:
I've found tons of emails, news messages, listserv messages, and even
some bug reports of this seemingly common error.
So, I had been running 5.2 on a server, and, updated to 5.3. Got the
READ_DMA and WRITE_DMA error and retries. So, figuring it might be a
On Wed, 2005-07-20 at 23:54 -0500, Steve wrote:
I've found tons of emails, news messages, listserv messages, and even
some bug reports of this seemingly common error.
So, I had been running 5.2 on a server, and, updated to 5.3. Got the
READ_DMA and WRITE_DMA error and retries. So, figuring
Paul Mather wrote:
One common thread in my case is that
all ran some kind of software RAID (gvinum or gmirror), though not all
of my software RAIDed machines exhibited the DMA problems leading me to
think perhaps it was a hardware/load/disk combination problem.
I do not use RAID at all,
Robert Watson wrote:
6.0 contains a significant re-write and update of the ATA driver, and
corrects a number of known problems with timeouts and reliability.
This rewrite is available as patches against 5.x, but has not been
committed because ATA is a very sensitive thing (lots of very
I've found tons of emails, news messages, listserv messages, and even
some bug reports of this seemingly common error.
So, I had been running 5.2 on a server, and, updated to 5.3. Got the
READ_DMA and WRITE_DMA error and retries. So, figuring it might be a bad
update, took a new drive. put it
