Issues with large drives going back to PIO

[Buckie]

Haha, laugh! I bought it 2 years ago, this was the dream of my
childhood, in 1996 I was literally drooling over anything PentiumPro
and dual seemed like an impossible dream. Was VERY hard to find, the
motherboard especially. Bought from some guy who kept them in a
garage. Cost $30 + $10(!) for a PPro radiator. It would still be more
than satisfactory if only it wasn't the need to write large amount of
CDs at 48x speed and that's why I'd need UDMA controller. The rest is
recorded history. But Gigabyte sucks anyway. I've yet to see a BIOS
THIS buggy (as in my current PPro motherboard).

Z

PS. Do you want to buy one? It's packed in a lovely Thermaltake Xaser
II case by the way, lighting included!

Friday, August 1, 2003, 2:35:19 AM, you wrote:

PK> Where are you getting Dual PentiumPro system from??

PK> --Peter
PK> ----- Original Message ----- 
PK> From: "Buckie" <freebsd1 at centrum.cz>
PK> To: <freebsd-hackers at freebsd.org>
PK> Sent: Thursday, July 31, 2003 3:14 PM
PK> Subject: Re: Issues with large drives going back to PIO


PK> Woo. I have just the same thing with a 10Gb Seagate Barracuda ATA III
PK> drive here. It appears to occur only when Seagate is attached to the
PK> wonderful SI0680 controller (falls back to PIO during boot time and
PK> after resetting through atacontrol). There's definitely a 'thing'
PK> about these controllers. It never does happen on WDMA modes though, on
PK> internal Intel controller.
PK> But I have an idea - this Seagate drive has some bad sectors in there,
PK> so I had Windows sometimes falling back to PIO for this drive because
PK> of these physical errors. Strange anyway.

PK> And we seem to have one thing in common: dual PentiumPro systems...

PK> Z


PK>> Hello.

PK>> A few months ago (May) to be exact, Søren posted a patch (
PK>> http://lists.freebsd.org/pipermail/freebsd-current/2003-May/003275.html
PK>> ) to the FreeBSD-current mailing list relating to IDE drives over a
PK> certian
PK>> size having issues with falling back to PIO mode and other things. This
PK>> patch was commited, and is currently in 5.1-RELEASE, and my friend told
PK> me
PK>> to try applying to the patch to fix the problem (although the patch was
PK>> already commited). There does NOT appear to be anything wrong with the
PK>> drives, as I have run tests on them and stuck them in another FreeBSD
PK>> 5.1-RELEASE box, and the problem seems to disappear.

PK>> The error I'm getting is..:

PK>> Jul 26 18:17:58 devil kernel: ad3: UDMA ICRC error cmd=write fsbn
PK> 198898911
PK>> of 198898911-198899166 retrying
PK>> Jul 26 18:17:58 devil kernel: ad3: UDMA ICRC error cmd=write fsbn
PK> 198902239
PK>> of 198902239-198902494 retrying
PK>> Jul 26 18:17:58 devil kernel: ad3: UDMA ICRC error cmd=write fsbn
PK> 198902239
PK>> of 198902239-198902494 retrying
PK>> Jul 29 12:43:28 devil kernel: ad2: UDMA ICRC error cmd=write fsbn
PK> 203789023
PK>> of 203789023-203789038 retrying
PK>> Jul 29 12:43:28 devil kernel: ad2: UDMA ICRC error cmd=write fsbn
PK> 203789023
PK>> of 203789023-203789038 falling back to PIO mode

PK>> and

PK>> ad3: UDMA ICRC error cmd=write fsbn 198898911 of 198898911-198899166
PK>> retrying
PK>> ad3: UDMA ICRC error cmd=write fsbn 198902239 of 198902239-198902494
PK>> retrying
PK>> ad3: UDMA ICRC error cmd=write fsbn 198902239 of 198902239-198902494
PK>> retrying
PK>> ad2: UDMA ICRC error cmd=write fsbn 203789023 of 203789023-203789038
PK>> retrying
PK>> ad2: UDMA ICRC error cmd=write fsbn 203789023 of 203789023-203789038
PK>> retrying
PK>> ad2: UDMA ICRC error cmd=write fsbn 203789023 of 203789023-203789038
PK>> retrying
PK>> ad2: UDMA ICRC error cmd=write fsbn 203789023 of 203789023-203789038
PK> falling
PK>> back to PIO mode

PK>> The drives are 120GB Maxtor 7200RPM with 2MB cache, I have 3 of them;
PK> and I
PK>> have experienced the same error with FreeBSD 5.1-RELEASE, and
PK> 4.8-RELEASE
PK>> (4.8, which always made the drives go back to PIO mode no matter what).
PK> The
PK>> board is a Asus P4SDX:

PK>> ad0: 117246MB <Maxtor 6Y120L0> [238216/16/63] at ata0-master UDMA133
PK>> ad1: 78167MB <Maxtor 4R080J0> [158816/16/63] at ata0-slave UDMA133
PK>> ad2: 117246MB <Maxtor 6Y120L0> [238216/16/63] at ata1-master UDMA133
PK>> ad3: 117246MB <Maxtor 6Y120L0> [238216/16/63] at ata1-slave UDMA133

PK> _______________________________________________
PK> freebsd-hackers at freebsd.org mailing list
PK> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
PK> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"





-- 
Best regards,
 Buckie                            mailto:freebsd1 at centrum.cz