All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy@furniss.freeserve.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: UDMA problem with Maxtor 7200rpm disk
Date: Sun, 23 Dec 2001 21:53:11 +0000	[thread overview]
Message-ID: <01122321531100.00783@MBC> (raw)



>When I try to enable DMA with hdparm -d1 /dev/hda :

>ide_dmaproc: chipset supported ide_dma_timeout func only: 14
>hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
>hda: timeout waiting for DMA
>ide_dmaproc: chipset supported ide_dma_timeout func only: 14
>hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
>hda: timeout waiting for DMA
>ide_dmaproc: chipset supported ide_dma_timeout func only: 14
>hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
>hda: timeout waiting for DMA
>ide_dmaproc: chipset supported ide_dma_timeout func only: 14
>hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
>hda: DMA disabled
>ide0: reset: success

I got this when I got my 40G 5200 maxtor. I've got an old award bios & PII 
with 440bx chipset.

The solution was to turn off udma in bios my 2.2 kernel and w98 could then 
use mdma.

I noticed that when I tested with a 2.4.9 it could use udma again - even 
though it remains off (for W98 & 2.2) in bios.

Andy.

             reply	other threads:[~2001-12-23 21:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-23 21:53 Andy Furniss [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-19 20:16 UDMA problem with Maxtor 7200rpm disk Jean-Francois Levesque
2001-12-20  0:47 ` Tim Moore
2001-12-20  1:25   ` Jean-Francois Levesque
2001-12-20  1:28 ` GOTO Masanori
2001-12-20  1:38   ` Jean-Francois Levesque
2001-12-20  2:43     ` Jean-Francois Levesque
2001-12-20  3:18       ` Timothy Covell
2001-12-20  9:10 ` Sergey S. Kostyliov

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=01122321531100.00783@MBC \
    --to=andy@furniss.freeserve.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.