Hello.
I was experiencing the same problem with TX4 on both Linux and FreeBSD.
It was determined that the root cause is a hardware bug in controller.
Patch that implements a workaround inspired by vendor-supplied driver:
http://www.spinics.net/lists/linux-ide/msg15858.html
I have not yet had
On Sun, Oct 21, 2007 at 09:19:35AM +0200, Peter Schuller wrote:
Hello,
Since then I have now tried two distinct TX4 cards (but only in one
PCI slot). Both suffer from the same problem. Amazingly a SiI 3114
*does* seem to work in the same PCI slot - no corruption, and no DMA
timeouts and
The card seems to be doing naughty things to the PCI bus under load;
your dmesg ought to be full of PCI timeouts.
No timeouts or errors in dmesg. I expected some, because that is what
I got on another machine (earlier 7-CURRENT) where I was unable to use
SiL/Promise because of such issues. In
Hello,
The following is not a request for help or bug report as such, I just
want to put the information out there in case it helps other people by
encouraging active checking for silent data corruption (also happens
to be a good saved yet again by ZFS story).
I was moving some disks to a
On 21/10/2007, Peter Schuller [EMAIL PROTECTED] wrote:
However, once I started dd:ing large files and reading them back in I
started getting I/O errors from ZFS, because of checksum
mismatches. Turns out all the drives connected to the TX4 in the
raidz2 were generating checksum errors (the
