From: Timothy Covell <timothy.covell@ashavan.org>
To: Jean-Francois Levesque <jfl@jfworld.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: UDMA problem with Maxtor 7200rpm disk
Date: Wed, 19 Dec 2001 21:18:51 -0600 [thread overview]
Message-ID: <200112200322.fBK3MVSr013812@svr3.applink.net> (raw)
In-Reply-To: <20011219151636.50e930ac.jfl@jfworld.net> <20011219203804.4c68f1ee.jfl@jfworld.net> <20011219214341.66b6b83e.jfl@jfworld.net>
In-Reply-To: <20011219214341.66b6b83e.jfl@jfworld.net>
On Wednesday 19 December 2001 20:43, Jean-Francois Levesque wrote:
> I tried the 2.4.17-rc2 kernel and I was able to boot. (but I'm not with
> 2.4.9, 2.4.12-ac5 and 2.4.16)
>
> Unfortunately, when I try hdparm -d1 /dev/hda, I get the same errors
>
> 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: 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
>
>
> What can influence the DMA on the BIOS else than the disk configuration?
>
> I always get this PCI bus warning :
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
>
> Maybe I have somthing wrong with PCI bus that change everything???
>
> Jean-François
>
> PS: I have the lastest asus BIOS update (1003).
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Three things occur to me:
1. I had a Maxtor disk (of many good ones) which died one month
before its warranty ran out. I just sent it back to Maxtor for a replacement.
2. The PCI bus runs at 33 MHz unless,
a) You have a server running at 66 MHz
b) You overclock your system.
3. From your earlier post, I wasn't sure if you understood PIO/DMA.
Original disks used Programmed Input/Output to increase throughput.
PIO Modes increase from 1 to 2 to 3 to 4. And them the Direct Memory
Access method gained acceptance and resulted in better throughput.
DMA2 is good, DMA4 is great and DMA5 is the best of the best as
of today.
Just my $0.02.
--
timothy.covell@ashavan.org.
next prev parent reply other threads:[~2001-12-20 3:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 20:16 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 2:43 ` Jean-Francois Levesque
2001-12-20 3:18 ` Timothy Covell [this message]
2001-12-20 1:38 ` Jean-Francois Levesque
2001-12-20 9:10 ` Sergey S. Kostyliov
2001-12-23 21:53 Andy Furniss
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=200112200322.fBK3MVSr013812@svr3.applink.net \
--to=timothy.covell@ashavan.org \
--cc=jfl@jfworld.net \
--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
all inboxes | Powered by JetHome®