Issues with large drives going back to PIO

Peter Kieser pfak at telus.net
Thu Jul 31 13:45:46 PDT 2003


Hello.

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

The error I'm getting is..:

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

and

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

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

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

uname -a output:

FreeBSD devil.mphknet.ca 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Sun Jul  6
14:15:37 PDT 2003     peter at devil.mphknet.ca:/usr/src/sys/i386/compile/DEVIL
i386

dmesg:

Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD 5.1-RELEASE #0: Sun Jul  6 14:15:37 PDT 2003
    peter at devil.mphknet.ca:/usr/src/sys/i386/compile/DEVIL
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0442000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0442244.
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 1600119912 Hz
CPU: Intel(R) Pentium(R) 4 CPU 1.60GHz (1600.12-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf24  Stepping = 4

Features=0x3febfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA
,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM>
real memory  = 536854528 (511 MB)
avail memory = 516734976 (492 MB)
Pentium Pro MTRR support enabled
npx0: <math processor> on motherboard
npx0: INT 16 interface
acpi0: <ASUS   P4SDX   > on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 10 entries at 0xc00f1630
acpi0: power button is handled as a fixed feature programming model.
Timecounter "ACPI-fast"  frequency 3579545 Hz
acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0
acpi_cpu0: <CPU> on acpi0
acpi_cpu1: <CPU> on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
isab0: <PCI-ISA bridge> at device 2.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <SiS 963 UDMA133 controller> port
0xb400-0xb40f,0xb800-0xb803,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 irq 11
at device 2.5 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: <serial bus, USB> at device 3.0 (no driver attached)
pci0: <serial bus, USB> at device 3.1 (no driver attached)
pci0: <serial bus, USB> at device 3.3 (no driver attached)
sis0: <SiS 900 10/100BaseTX> port 0x9800-0x98ff mem 0xf6000000-0xf6000fff at
device 4.0 on pci0
pcib0: slot 4 INTA is routed to irq 5
sis0: Ethernet address: 00:0c:6e:2b:46:ed
miibus0: <MII bus> on sis0
rlphy0: <RTL8201L 10/100 media interface> on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci0: <display, VGA> at device 9.0 (no driver attached)
fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> port
0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0: <Parallel port bus> on ppc0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A
atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
orm0: <Option ROM> at iomem 0xc0000-0xc7fff on isa0
pmtimer0 on isa0
sc0: <System console> on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
Timecounters tick every 10.000 msec
ipfw2 initialized, divert disabled, rule-based forwarding enabled, default
to accept, logging limited to 100 packets/entry by default
DUMMYNET initialized (011031)
IPv6 packet filtering initialized, default to accept, logging limited to 100
packets/entry
acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0%
ad0: 117246MB <Maxtor 6Y120L0> [238216/16/63] at ata0-master UDMA133
ad1: 78167MB <Maxtor 4R080J0> [158816/16/63] at ata0-slave UDMA133
ad2: 117246MB <Maxtor 6Y120L0> [238216/16/63] at ata1-master UDMA133
ad3: 117246MB <Maxtor 6Y120L0> [238216/16/63] at ata1-slave UDMA133
Mounting root from ufs:/dev/ad0s1a

I have not had the box crash, or anything in that matter. Just very slow
access to the drives because they have switched back to PIO; and I have to
force them back with atacontrol to regain the speed.

Any suggestions, comments, tips? Should I be trying to replace the drive?
How can I do that if MaxDiag doesn't give me an error code so I can get the
drives RMAed?

Cheers,

--Peter




More information about the freebsd-hackers mailing list