ad10: WARNING - READ_DMA UDMA ICRC error (retrying request)
sos at FreeBSD.ORG
Wed Aug 10 22:46:49 GMT 2005
On 10/08/2005, at 22:51, Karl Denninger wrote:
>> Since I came in late in this, I need to know what kind of controller
>> we are talking about, and if the problem is still present in 6.0.
>> I plan to backport ATA from 6.0 to 5-stable when it has settled, so
>> 6.0 is the one and only (pre)release to test with and get back to me
>> with the result.
>> - S?ren
> 6.0 BETA1 AND 5.4 BOTH fail with the SiI 3112 chipsets. Reliably.
> I have two controllers here that are from different manufacturers
> and both
> exhibit the same problem. The SAME disks (two different
> manufacturers -
> hitachi and maxtor) on a motherboard ICH5 adapter work perfectly,
> smartmontools says all 4 (I have two examples of each) are healthy,
> both ALSO work perfectly on and are declared healthy by a 3ware 8502's
> internal diags and operating kernel (smartmontools won't talk to
> them on
> the 8502.)
> This is the subject of the PR I filed back in February.
> Again, if you want either a controller shipped to you OR access to a
> development machine (e.g. ssh in and play) which has the suspect
> configuration on it, the latter of which is probably the best
> option (since
> making it fail is simple) I'm willing to provide either - my only
> caveat is
> that if I send hardware I want it back when you're done, and I
> believe its
> reasonable to expect that 6.0 will get HELD in its release cycle
> until this
> is resolved.
I have plenty of the sii3112's around, so thats not needed, however
I've not managed to get ahold of a machine in which it fails reliably
with ATA as is in 6.0.
> The latter offer (ssh access) has been on the table for several
> months. The
> former I just put on the table as I threw up my hands and bought a
> card - which means I now have TWO of the suspect cards and need
> only one
> for my own testing (in the sandbox)
> I'm willing to go WELL out of my way to make it possible for this
> to get
> fixed, since there appears to be an issue with access to hardware that
> breaks reliably. However, I, and others, would like to know that
> going to see the problem get resolved.
I've already gone WAY out of my way to try to support the sii3112,
and I'm not inclined to waste more of my precious spare time on it.
However, if it really is that important to enough people to try to
workaround the silicon bugs (which very likely isn't possible), get
together and get me failing HW on my desk and time to work on it.
> Again - this is hardware that is STABLE and works under 4.x - in
> the case of
> my specific configuration I ran under 4.x for over a year without a
> incident. With 5.4 and 6.0-BETA I can kill it inside of 2 minutes
> nothing more complicated than a "make -j4 buildworld".
First. you cannot by any degree of the word call the sii3112 for
STABLE hardware, its broken beyond repair or workarounds, and even
the supplier acknowledges that fact.
Second, you cannot possibly have used gmirror (as in the PR) on 4.x
so what was the config back then ?
Third, please get gmirror out of the loop (use atacontrol to create a
mirror if need be) and let me know if that changes anything.
Forth, another thing to try is fumbling with BIOS settings, some
setups has been reported to start working when PCI timings is changed
More information about the freebsd-stable