public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Feiler <kiza@lionking.org>
To: linux-kernel@vger.kernel.org
Subject: Mixing UDMA33/66 drives, VIA IDE, Linux 2.2.18
Date: Fri, 2 Mar 2001 17:10:49 +0100	[thread overview]
Message-ID: <20010302171049.A555@lionking.org> (raw)

Hello,

	I've run into a problem while using the follwing different drives:
IBM-DTTA-351010 and IBM-DJNA-351520. The first one is a UDMA33 drive and the 
second one seems to be a UDMA66 capable drive, UDMA4. I have attached a 
"hdparm -i" of both drives at the end of the mail.

	Both drives are connected to the same IDE channel on a VIA686A board 
with a 80pin IDE cable. When I try to access the UDMA33 drive I get:

Mar  2 16:08:30 kiza kernel: hda: irq timeout: status=0x58 { DriveReady 
SeekComplete DataRequest }
Mar  2 16:08:41 kiza kernel: hda: timeout waiting for DMA
Mar  2 16:08:41 kiza kernel: hda: irq timeout: status=0x58 { DriveReady 
SeekComplete DataRequest }
Mar  2 16:08:51 kiza kernel: hda: timeout waiting for DMA
Mar  2 16:08:51 kiza kernel: hda: irq timeout: status=0x58 { DriveReady 
SeekComplete DataRequest }
Mar  2 16:09:01 kiza kernel: hda: timeout waiting for DMA
Mar  2 16:09:01 kiza kernel: hda: irq timeout: status=0x58 { DriveReady 
SeekComplete DataRequest }
Mar  2 16:09:01 kiza kernel: hda: DMA disabled
Mar  2 16:09:01 kiza kernel: hdb: DMA disabled
Mar  2 16:09:01 kiza kernel: ide0: reset: success

	and the system continues to work with DMA disabled.

	If I use a 40pin cable to connect the drives there are no problems. If 
I try to set -X66 with hdparm for the UDMA66 disk (that should set UDMA33 
mode, right?) and use the 80 pin cable the problem is not solved.

	The problem seems to be the 80 pin cable. Can't the drives operate in 
different modes independently? Setting a slower transfer mode with hdparm does 
not work. Can it be set otherwise? With a kernel parameter?

	I'm using 2.2.18 with the IDE driver that came with it. Is this maybe 
a problem that was solved in 2.4?

	Or is it just a theoretical "that will not work" problem? :)

Thanks for any help.

Oliver


Output of hdparm -i for both drives. Both are connected with a 40pin cable 
this time:

 Model=IBM-DTTA-351010, FwRev=T56OA73A, SerialNo=WF0KFTR8113
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=34
 BuffType=DualPortCache, BuffSize=466kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=19807200
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4 
 DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 *udma2 

 Model=IBM-DJNA-351520, FwRev=J56OA30K, SerialNo=G80GLW69191
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=34
 BuffType=DualPortCache, BuffSize=430kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=30033360
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4 
 DMA modes: mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 



-- 
Oliver Feiler                                               kiza@gmx.net
http://www.lionking.org/~kiza/pgpkey              PGP key ID: 0x561D4FD2
http://www.lionking.org/~kiza/

                 reply	other threads:[~2001-03-02 16:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010302171049.A555@lionking.org \
    --to=kiza@lionking.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox