* PIIX3 timeout waiting for DMA 2.4 and MAXTOR drive.
@ 2003-07-10 6:24 Gerardo Exequiel Pozzi
2003-07-24 16:43 ` Meelis Roos
0 siblings, 1 reply; 2+ messages in thread
From: Gerardo Exequiel Pozzi @ 2003-07-10 6:24 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]
Hi people,
Recently I was making some tests on old motherboard with PIIX3 chipset,
copying the directory /usr (630mb) from a disc to another one (runlevel
1), in both senses (origin disk in read-only), after a few minutes of
activity (1-2 minutes), different messages from kernel about DMA timeout
appeared.
The problem only happens on disc MAXTOR, as much reading as writing on
it, when transfer data from a disc to another one connected in
different IDE channels. But on the same disc or from a disc to another
one on same IDE channel there is no problem, also probe to invert discs
of channels IDE and the problem repeats on him same disc.
Also probe with another disc MAXTOR same model, and happens exactly the
same.
I read in a page Web on the problem of the DMA timeout with this PIIX3
chipset and discs QUANTUM, and that a possible solution is to
increase the "PCI Latency Timer", then, it fits the Latency with
setpci of all the PCI BUS of 32 to greater numbers, until 0xff and the
problem persists.
Probe both kernels the 2.4.20 and the 2.4.21 (with and without XFS
patch) and the same results.
This a PIIX3 chipset problem with some disks?
This message appears three times during the copy and finaly dma
& multicount is disabled, but reactivated with hdparm without
problems.
hdc: dma_timer_expiry: dma status == 0x20
hdc: timeout waiting for DMA
hdc: timeout waiting for DMA
hdc: (__ide_dma_test_irq) called while not waiting
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: drive not ready for command
ide1: reset: success
Attached the config, dmesg, lspci, and hdparm -i.
ciao, dj
btw: lamentably I do not have at the moment the hardware to prove
(sorry my english)
--
Gerardo Exequiel Pozzi ( djgera )
http://www.vmlinuz.com.ar http://www.djgera.com.ar
KeyID: 0x1B8C330D
Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
[-- Attachment #2: piix3.dma.timeout.txt --]
[-- Type: application/octet-stream, Size: 11275 bytes --]
CONFIG_X86=y
CONFIG_UID16=y
CONFIG_EXPERIMENTAL=y
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y
CONFIG_M586TSC=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_USE_STRING_486=y
CONFIG_X86_ALIGNMENT_16=y
CONFIG_X86_HAS_TSC=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_MCE=y
CONFIG_NOHIGHMEM=y
CONFIG_X86_TSC=y
CONFIG_NET=y
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_ISA=y
CONFIG_PCI_NAMES=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_1284=y
CONFIG_PNP=y
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y
CONFIG_BLK_STATS=y
CONFIG_PACKET=y
CONFIG_NETFILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_SYN_COOKIES=y
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_IDEDMA_AUTO=y
CONFIG_BLK_DEV_IDE_MODES=y
CONFIG_NETDEVICES=y
CONFIG_TUN=m
CONFIG_NET_ETHERNET=y
CONFIG_NET_PCI=y
CONFIG_TULIP=m
CONFIG_DM9102=y
CONFIG_NE2K_PCI=m
CONFIG_8139TOO=m
CONFIG_SIS900=m
CONFIG_WINBOND_840=m
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=m
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_PRINTER=m
CONFIG_RTC=y
CONFIG_REISERFS_FS=m
CONFIG_EXT3_FS=y
CONFIG_JBD=y
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_UMSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_MINIX_FS=m
CONFIG_NTFS_FS=m
CONFIG_PROC_FS=y
CONFIG_DEVPTS_FS=y
CONFIG_EXT2_FS=y
CONFIG_UDF_FS=m
CONFIG_UFS_FS=m
CONFIG_XFS_FS=y
CONFIG_SMB_FS=m
CONFIG_ZISOFS_FS=m
CONFIG_PARTITION_ADVANCED=y
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
CONFIG_SMB_NLS=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_UTF8=y
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB16=y
CONFIG_FBCON_CFB24=y
CONFIG_FBCON_CFB32=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
/dev/hdc:
Model=Maxtor 6E040L0, FwRev=NAR61590, SerialNo=E16C9LQE
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=80293248
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 *mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 udma6
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: (null): 1 2 3 4 5 6 7
00:00.0 Host bridge: Intel Corp. 430VX - 82437VX TVX [Triton VX] (rev 02)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 32
00:07.0 ISA bridge: Intel Corp. 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
00:07.1 IDE interface: Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II] (prog-if 80 [Master])
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Region 4: I/O ports at f000 [size=16]
00:07.2 USB Controller: Intel Corp. 82371SB PIIX3 USB [Natoma/Triton II] (rev 01) (prog-if 00 [UHCI])
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Interrupt: pin D routed to IRQ 11
Region 4: I/O ports at 6000 [size=32]
00:08.0 VGA compatible controller: Cirrus Logic GD 5436 [Alpine] (prog-if 00 [VGA])
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Region 0: Memory at e0000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at <unassigned> [disabled] [size=32K]
00:0a.0 Ethernet controller: Davicom Semiconductor, Inc. Ethernet 100/10 MBit (rev 31)
Subsystem: Unknown device 3030:5032
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+
Latency: 32 (5000ns min, 10000ns max)
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at 6100 [size=256]
Region 1: Memory at e1000000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at <unassigned> [disabled] [size=256K]
Capabilities: [50] Power Management version 1
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Linux version 2.4.21 (root@multimedia) (gcc version 3.2.2) #1 Mon Jul 7 18:28:36 ART 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000002000000 (usable)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
32MB LOWMEM available.
On node 0 totalpages: 8192
zone(0): 4096 pages.
zone(1): 4096 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=linux ro root=301 init=/bin/bash
Initializing CPU#0
Detected 150.002 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 299.00 BogoMIPS
Memory: 29856k/32768k available (1408k kernel code, 2528k reserved, 289k data, 240k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Intel Pentium with F0 0F bug - workaround enabled.
CPU: After generic, caps: 000001bf 00000000 00000000 00000000
CPU: Common caps: 000001bf 00000000 00000000 00000000
CPU: Intel Pentium 75 - 200 stepping 0c
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
PCI: PCI BIOS revision 2.10 entry at 0xfb3c0, last bus=0
PCI: Using configuration type 1
PCI: Probing PCI hardware
Limiting direct PCI/PCI transfers.
Activating ISA DMA hang workarounds.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
SGI XFS snapshot-xfs-2.4.21-2003-07-07_02:01_UTC with no debug enabled
pty: 256 Unix98 ptys configured
Real Time Clock Driver v1.10e
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
eth0: Davicom DM9102 at pci00:0a.0, 00:80:ad:09:74:2e, irq 10.
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX3: IDE controller at PCI slot 00:07.1
PIIX3: chipset revision 0
PIIX3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hda: WDC WD600BB-00CJA1, ATA DISK drive
blk: queue c030e0e0, I/O limit 4095Mb (mask 0xffffffff)
hdc: Maxtor 6E040L0, ATA DISK drive
blk: queue c030e534, I/O limit 4095Mb (mask 0xffffffff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63, (U)DMA
hdc: attached ide-disk driver.
hdc: host protected area => 1
hdc: 80293248 sectors (41110 MB) w/2048KiB Cache, CHS=79656/16/63, (U)DMA
Partition check:
hda: hda1 hda2 hda3
hdc: hdc1
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 240k freed
kjournald starting. Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
hdc: dma_timer_expiry: dma status == 0x20
hdc: timeout waiting for DMA
hdc: timeout waiting for DMA
hdc: (__ide_dma_test_irq) called while not waiting
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: drive not ready for command
ide1: reset: success
hdc: dma_timer_expiry: dma status == 0x20
hdc: timeout waiting for DMA
hdc: timeout waiting for DMA
hdc: (__ide_dma_test_irq) called while not waiting
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: drive not ready for command
ide1: reset: success
hdc: dma_timer_expiry: dma status == 0x20
hdc: timeout waiting for DMA
hdc: timeout waiting for DMA
hdc: (__ide_dma_test_irq) called while not waiting
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: drive not ready for command
ide1: reset: success
hdc: dma_timer_expiry: dma status == 0x20
hdc: timeout waiting for DMA
hdc: timeout waiting for DMA
hdc: (__ide_dma_test_irq) called while not waiting
hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: drive not ready for command
ide1: reset: success
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: PIIX3 timeout waiting for DMA 2.4 and MAXTOR drive.
2003-07-10 6:24 PIIX3 timeout waiting for DMA 2.4 and MAXTOR drive Gerardo Exequiel Pozzi
@ 2003-07-24 16:43 ` Meelis Roos
0 siblings, 0 replies; 2+ messages in thread
From: Meelis Roos @ 2003-07-24 16:43 UTC (permalink / raw)
To: linux-kernel; +Cc: Gerardo Exequiel Pozzi, Holger Lubitz
> This a PIIX3 chipset problem with some disks?
I believe this a MWDMA2 mode bug in Linux IDE layer (but I may be wrong
of course).
> This message appears three times during the copy and finaly dma
> & multicount is disabled, but reactivated with hdparm without
> problems.
>
> hdc: dma_timer_expiry: dma status == 0x20
> hdc: timeout waiting for DMA
> hdc: timeout waiting for DMA
> hdc: (__ide_dma_test_irq) called while not waiting
> hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
>
> hdc: drive not ready for command
> hdc: status timeout: status=0xd0 { Busy }
>
> hdc: drive not ready for command
> ide1: reset: success
I have similar messages from one drive (old pre-UDMA Seagate with MWDMA)
on several computres. In short: 2.4.18 with PIIX driver is OK, 2.4.19
gives errors. ICH2 and new kernels give errors, old kernel not tested
yet. VIA 686b gives errors with newer kernels but also gives different
error on 2.4.18 (which is completely unexplained by me). Most errors
occur during disk load, cp -a of a kernel tree usually triggers it.
Needless to say that 2.5.latest have been the sam as current 2.4.
Details are below.
Since the disk works fine with kernels up to 2.4.18 24x7 and gets quite
a load (it's a kernel compile disk in an old K6/200 with 430TX, also
gets bk pulls for the kernel), the disk is probably working.
Since new kernels give errors not only on PIIX4 and ICH2 but also on
VIA, it is probaly not just Intel IDE driver problem.
So far I have seen 3 people with MWDMA problems, they are included in
the reply except one that I have lost the address for. MWDMA _seems_ to
be the common denominator.
The details:
2.4.18+piix tuning on PIIX4 works OK.
2.4.18+via driver on via 686b gets this:
hdd: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: drive not ready for command
hdd: status timeout: status=0xd0 { Busy }
hdc: DMA disabled
hdd: drive not ready for command
ide1: reset: success
The same is repeated sometimes without "DMA disabled" message but the
thing seems to work.
2.4.22pre on the same piix4 gets this:
hdd: dma_timer_expiry: dma status == 0x61
hda: dma_timer_expiry: dma status == 0x61
hdd: error waiting for DMA
hdd: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status timeout: status=0xd0 { Busy }
hdc: DMA disabled
hdd: drive not ready for command
ide1: reset timed-out, status=0xff
hdd: dma_timer_expiry: dma status == 0x41
hdd: error waiting for DMA
hdd: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status timeout: status=0xd0 { Busy }
hdd: drive not ready for command
ide1: reset timed-out, status=0xff
And the disk is put offline after lots of IO errors.
2.4.22pre on via686b gets this:
hdd: dma_timer_expiry: dma status == 0x60
hdd: timeout waiting for DMA
hdd: timeout waiting for DMA
hdd: (__ide_dma_test_irq) called while not waiting
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: drive not ready for command
hdd: status timeout: status=0xd0 { Busy }
hdc: DMA disabled
hdd: drive not ready for command
ide1: reset: success
and the disk stays working but sometimes stops for quite several
seconds, spits this error and continues.
2.4.22pre on ICH2 gets this _during partition detection_:
hdd: dma_timer_expiry: dma status == 0x40
hdd: timeout waiting for DMA
hdd: timeout waiting for DMA
hdd: (__ide_dma_test_irq) called while not waiting
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: drive not ready for command
so no partitions and no mounting withs this kernel version.
Ths disk is Seagate ST32531A, 4996476 sectors (2558 MB), CHS=4956/16/63.
It is used as secondary slave with different cdroms as secondary
masters. Smart info tells it passes tests, has no relocated sectors yet
but seek error rate and raw read error rate have high raw values:
1 Raw_Read_Error_Rate 0x000a 115 099 000 Old_age Always - 95379906
3 Spin_Up_Time 0x0006 097 097 000 Old_age Always - 3
4 Start_Stop_Count 0x0013 100 100 020 Pre-fail Always - 131
5 Reallocated_Sector_Ct 0x0013 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 068 053 030 Pre-fail Always - 25814353362
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0013 100 100 020 Pre-fail Always - 126
hdparm -i of it:
/dev/hdd:
Model=ST32531A, FwRev=0.62, SerialNo=VE047143
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=4956/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=off
CurCHS=4956/16/63, CurSects=4996476, LBA=yes, LBAsects=4996476
IORDY=on/off, tPIO={min:383,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio3 pio4
DMA modes: mdma0 mdma1 *mdma2
AdvancedPM=no
Drive conforms to: unknown: 0 1 2
and hdparm -I:
/dev/hdd:
ATA device, with non-removable media
Model Number: ST32531A
Serial Number: VE047143
Firmware Revision: 0.62
Standards:
Supported: 2 1
Likely used: 3
Configuration:
Logical max current
cylinders 4956 4956
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 4996476
LBA user addressable sectors: 4996476
device size with M = 1024*1024: 2439 MBytes
device size with M = 1000*1000: 2558 MBytes (2 GB)
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 4
Standby timer values: spec'd by Vendor
R/W multiple sector transfer: Max = 16 Current = 16
DMA: mdma0 mdma1 *mdma2
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=383ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
Power Management feature set
SMART feature set
I did try increasing the timeout for DMA reads and DMA writes in
ide-dma.c but of course this did not help.
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-07-24 16:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-07-10 6:24 PIIX3 timeout waiting for DMA 2.4 and MAXTOR drive Gerardo Exequiel Pozzi
2003-07-24 16:43 ` Meelis Roos
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).