Date: Tue, 7 Aug 2001 16:40:03 -0700 (PDT) From: kachun@newsguy.com (Kachun Lee) To: freebsd-bugs@FreeBSD.org Subject: Re: i386/29315: Promise ATA100 UDMA5 works incorrectly Message-ID: <200108072340.f77Ne3U92581@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR i386/29315; it has been noted by GNATS. From: kachun@newsguy.com (Kachun Lee) To: cch@cc.kmu.edu.tw Cc: freebsd-gnats-submit@FreeBSD.ORG, iedowse@maths.tcd.ie Subject: Re: i386/29315: Promise ATA100 UDMA5 works incorrectly Date: Tue, 07 Aug 2001 16:35:47 -0700 In article <9kni83$11oj$1@FreeBSD.csie.NCTU.edu.tw>, you say... > I have done several tests by the script in attachment. > The results of these tests show that: (simply checked by "grep MD5 > chkcp.txt") > > 1. Intel ICH2 ATA driver (UDMA5 mode) + Seagate-ST320413A -> OK > please see: > http://cc.kmu.edu.tw/~cch/FreeBSD/ata/intel-ich2-udma5-hd.txt > > 2.Promise ATA100 driver (UDMA5 mode) + IBM-DTLA-307030 -> FAIL > (It sometimes works correctly, but incorrectly at most time.) > please see: http://cc.kmu.edu.tw/~cch/FreeBSD/ata/promise-udma5-hd.txt > [snip] I believe this was the same problem described in: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=29045 Plus, if the below article was correct... http://groups.google.com/groups?hl=en&safe=off&th=127674b89a58577c,7&seekm=PaV9 7.311316%24XL1.5437943%40nlnews00.chello.com#p then the problem was with the IBM-DTLA drives. That was what I was afraid of... we have quite a few of those drives. The google article stated the data was always corrupted at the end of a 0x1000 block. Will that offer some insight to the problem? It will be nice there is a work around beside running the drives at U33. I send an email to IBM harddrive support and see if they reply. Regards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108072340.f77Ne3U92581>