Date: Fri, 1 Aug 2003 02:14:52 +0400 From: Buckie <freebsd1@centrum.cz> To: freebsd-hackers@freebsd.org Subject: Re: Issues with large drives going back to PIO Message-ID: <773144414.20030801021452@centrum.cz> In-Reply-To: <004101c357a4$b57b0fe0$bc01a8c0@hartmut82lgcgo> References: <004101c357a4$b57b0fe0$bc01a8c0@hartmut82lgcgo>
next in thread | previous in thread | raw e-mail | index | archive | help
Woo. I have just the same thing with a 10Gb Seagate Barracuda ATA III drive here. It appears to occur only when Seagate is attached to the wonderful SI0680 controller (falls back to PIO during boot time and after resetting through atacontrol). There's definitely a 'thing' about these controllers. It never does happen on WDMA modes though, on internal Intel controller. But I have an idea - this Seagate drive has some bad sectors in there, so I had Windows sometimes falling back to PIO for this drive because of these physical errors. Strange anyway. And we seem to have one thing in common: dual PentiumPro systems... Z PK> Hello. PK> A few months ago (May) to be exact, S=F8ren posted a patch ( PK> http://lists.freebsd.org/pipermail/freebsd-current/2003-May/003275.ht= ml PK> ) to the FreeBSD-current mailing list relating to IDE drives over a c= ertian PK> size having issues with falling back to PIO mode and other things. Th= is PK> patch was commited, and is currently in 5.1-RELEASE, and my friend to= ld me PK> to try applying to the patch to fix the problem (although the patch w= as PK> already commited). There does NOT appear to be anything wrong with th= e 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=3Dwrite fsbn 1= 98898911 PK> of 198898911-198899166 retrying PK> Jul 26 18:17:58 devil kernel: ad3: UDMA ICRC error cmd=3Dwrite fsbn 1= 98902239 PK> of 198902239-198902494 retrying PK> Jul 26 18:17:58 devil kernel: ad3: UDMA ICRC error cmd=3Dwrite fsbn 1= 98902239 PK> of 198902239-198902494 retrying PK> Jul 29 12:43:28 devil kernel: ad2: UDMA ICRC error cmd=3Dwrite fsbn 2= 03789023 PK> of 203789023-203789038 retrying PK> Jul 29 12:43:28 devil kernel: ad2: UDMA ICRC error cmd=3Dwrite fsbn 2= 03789023 PK> of 203789023-203789038 falling back to PIO mode PK> and PK> ad3: UDMA ICRC error cmd=3Dwrite fsbn 198898911 of 198898911-19889916= 6 PK> retrying PK> ad3: UDMA ICRC error cmd=3Dwrite fsbn 198902239 of 198902239-19890249= 4 PK> retrying PK> ad3: UDMA ICRC error cmd=3Dwrite fsbn 198902239 of 198902239-19890249= 4 PK> retrying PK> ad2: UDMA ICRC error cmd=3Dwrite fsbn 203789023 of 203789023-20378903= 8 PK> retrying PK> ad2: UDMA ICRC error cmd=3Dwrite fsbn 203789023 of 203789023-20378903= 8 PK> retrying PK> ad2: UDMA ICRC error cmd=3Dwrite fsbn 203789023 of 203789023-20378903= 8 PK> retrying PK> ad2: UDMA ICRC error cmd=3Dwrite fsbn 203789023 of 203789023-20378903= 8 falling PK> back to PIO mode PK> The drives are 120GB Maxtor 7200RPM with 2MB cache, I have 3 of them;= and I PK> have experienced the same error with FreeBSD 5.1-RELEASE, and 4.8-REL= EASE PK> (4.8, which always made the drives go back to PIO mode no matter what= ). 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?773144414.20030801021452>