Skip to contentSkip to conversation

problems with Seagate 120 GB drives when mutlwrite = 16

DISCUSSION kris 3 participants 4 messages Oct 19, 2003 – Oct 25, 2003

lore
Share & tools
lore

kris

author
#0 lore raw

Hi,

I have noticed some problems with recent large drives, connected to a variety of controllers.

I tested with nforce ide controller, a CMD649 based controller and an Intel 870 cghipset. all have same or similar symptoms.

Linux 2.4.22 kernel : (Linux borg-cube 2.4.22-xfs #2 SMP Tue Oct 7 20:53:04 CEST 2003 i686 unknown)

Oct  6 15:52:12 borg-cube kernel: hdg: dma_timer_expiry: dma status ==
0x21
Oct  6 15:52:22 borg-cube kernel: hdg: timeout waiting for DMA
Oct  6 15:52:22 borg-cube kernel: hdg: timeout waiting for DMA
Oct  6 15:52:22 borg-cube kernel: hdg: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Oct  6 15:52:22 borg-cube kernel:
Oct  6 15:52:22 borg-cube kernel: hdg: drive not ready for command
Oct  6 15:52:22 borg-cube kernel: hdg: status timeout: status=0xd0 {
Busy }
Oct  6 15:52:22 borg-cube kernel:
Oct  6 15:52:22 borg-cube kernel: hdg: no DRQ after issuing WRITE
Oct  6 15:52:22 borg-cube kernel: ide3: reset: success

same in 2.4.20 ( kernel from Suse)

2.6.0-test6 :

Oct  9 09:43:09 borg-cube kernel: hdg: dma_timer_expiry: dma status ==
0x21
Oct  9 09:43:18 borg-cube kernel:
Oct  9 09:43:19 borg-cube kernel: hdg: DMA timeout error
Oct  9 09:43:19 borg-cube kernel: hdg: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Oct  9 09:43:19 borg-cube kernel:
Oct  9 09:43:19 borg-cube kernel: hdg: status timeout: status=0xd0 {
Busy }
Oct  9 09:43:19 borg-cube kernel:
Oct  9 09:43:19 borg-cube kernel: hdg: no DRQ after issuing MULTWRITE
Oct  9 09:43:20 borg-cube kernel: ide3: reset: success

same in 2.6.0-test8

so behaviour is consistent.

I can avoid this with either turning off dma access or disabling the multwrite ( hdparm -m0 /dev/hdg)

is this a known bug, or should I file one ?

kind regards, Kris

#1 lore raw
Quoted 1 line · kris

Hi,

Hi,

Quoted 40 lines

I have noticed some problems with recent large drives, connected to a variety of controllers.

I tested with nforce ide controller, a CMD649 based controller and an Intel 870 cghipset. all have same or similar symptoms.

Linux 2.4.22 kernel : (Linux borg-cube 2.4.22-xfs #2 SMP Tue Oct 7 20:53:04 CEST 2003 i686 unknown)

Oct  6 15:52:12 borg-cube kernel: hdg: dma_timer_expiry: dma status ==
0x21
Oct  6 15:52:22 borg-cube kernel: hdg: timeout waiting for DMA
Oct  6 15:52:22 borg-cube kernel: hdg: timeout waiting for DMA
Oct  6 15:52:22 borg-cube kernel: hdg: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Oct  6 15:52:22 borg-cube kernel:
Oct  6 15:52:22 borg-cube kernel: hdg: drive not ready for command
Oct  6 15:52:22 borg-cube kernel: hdg: status timeout: status=0xd0 {
Busy }
Oct  6 15:52:22 borg-cube kernel:
Oct  6 15:52:22 borg-cube kernel: hdg: no DRQ after issuing WRITE
Oct  6 15:52:22 borg-cube kernel: ide3: reset: success

same in 2.4.20 ( kernel from Suse)

2.6.0-test6 :

Oct  9 09:43:09 borg-cube kernel: hdg: dma_timer_expiry: dma status ==
0x21
Oct  9 09:43:18 borg-cube kernel:
Oct  9 09:43:19 borg-cube kernel: hdg: DMA timeout error
Oct  9 09:43:19 borg-cube kernel: hdg: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Oct  9 09:43:19 borg-cube kernel:
Oct  9 09:43:19 borg-cube kernel: hdg: status timeout: status=0xd0 {
Busy }
Oct  9 09:43:19 borg-cube kernel:
Oct  9 09:43:19 borg-cube kernel: hdg: no DRQ after issuing MULTWRITE
Oct  9 09:43:20 borg-cube kernel: ide3: reset: success
Quoted 8 lines

same in 2.6.0-test8

so behaviour is consistent.

I can avoid this with either turning off dma access or disabling the multwrite ( hdparm -m0 /dev/hdg)

is this a known bug, or should I file one ?

Error message is known, but fact that disabling PIO multiwrite cures it is new, so please fill bugzilla entry.

Thanks!!
--bartlomiej

author
#2 lore raw
Quoted 49 lines · Bartlomiej Zolnierkiewicz
Quoted 1 line · kris

Hi,

Hi,

Quoted 44 lines

I have noticed some problems with recent large drives, connected to a variety of controllers.

I tested with nforce ide controller, a CMD649 based controller and an Intel 870 cghipset. all have same or similar symptoms.

Linux 2.4.22 kernel : (Linux borg-cube 2.4.22-xfs #2 SMP Tue Oct 7 20:53:04 CEST 2003 i686 unknown)

Oct  6 15:52:12 borg-cube kernel: hdg: dma_timer_expiry: dma status ==
0x21
Oct  6 15:52:22 borg-cube kernel: hdg: timeout waiting for DMA
Oct  6 15:52:22 borg-cube kernel: hdg: timeout waiting for DMA
Oct  6 15:52:22 borg-cube kernel: hdg: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Oct  6 15:52:22 borg-cube kernel:
Oct  6 15:52:22 borg-cube kernel: hdg: drive not ready for command
Oct  6 15:52:22 borg-cube kernel: hdg: status timeout: status=0xd0 {
Busy }
Oct  6 15:52:22 borg-cube kernel:
Oct  6 15:52:22 borg-cube kernel: hdg: no DRQ after issuing WRITE
Oct  6 15:52:22 borg-cube kernel: ide3: reset: success

same in 2.4.20 ( kernel from Suse)

2.6.0-test6 :

Oct  9 09:43:09 borg-cube kernel: hdg: dma_timer_expiry: dma status ==
0x21
Oct  9 09:43:18 borg-cube kernel:
Oct  9 09:43:19 borg-cube kernel: hdg: DMA timeout error
Oct  9 09:43:19 borg-cube kernel: hdg: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Oct  9 09:43:19 borg-cube kernel:
Oct  9 09:43:19 borg-cube kernel: hdg: status timeout: status=0xd0 {
Busy }
Oct  9 09:43:19 borg-cube kernel:
Oct  9 09:43:19 borg-cube kernel: hdg: no DRQ after issuing MULTWRITE
Oct  9 09:43:20 borg-cube kernel: ide3: reset: success

same in 2.6.0-test8

so behaviour is consistent.

Quoted 7 lines
Quoted 4 lines

I can avoid this with either turning off dma access or disabling the multwrite ( hdparm -m0 /dev/hdg)

is this a known bug, or should I file one ?

Error message is known, but fact that disabling PIO multiwrite cures it is new, so please fill bugzilla entry.

I have to come back on this... i did not test it enough apparently... when i was transferring cd-images from one system to the other... the dreaded ide reset occurred again...

so disabling multiwrite is not involved.

The 60GB disk (with the OS) is working fine on my nforce ide controller. but the 120GB disks are not... I verified, it is not a cabling issue... used different cables, different lengths, at the moment they are connected with shielded rounded cables.

Is there a fix for this ( not the workaround ... disabling dma) or are these 120Gb disks just plain bad choice.... ;(

I do not notice any problems when i use the disk in windoows, but then again, windows tends to hide these things...;)

kind regards,Kris

#3 lore raw

Hi,

Quoted 7 lines · kris

The 60GB disk (with the OS) is working fine on my nforce ide controller. but the 120GB disks are not... I verified, it is not a cabling issue... used different cables, different lengths, at the moment they are connected with shielded rounded cables.

Is there a fix for this ( not the workaround ... disabling dma) or are these 120Gb disks just plain bad choice.... ;(

No, the same is on smaller Seagate disks, I have alot of 40GB Seagates running on 2.4.16/18 and they put the message on every boot, I can't remember 100% for 2.4.16, but 18 definetly.

Signature · 6 lines
Mark Burazin 
[email protected]
---<>---<>---<>---<>---<>---<>---<>---<>---<>
Lemna d.o.o.
http://www.lemna.biz - [email protected]
<>---<>---<>---<>---<>---<>---<>---<>---<>---