From: Jasmeet Sidhu <jsidhu@arraycomm.com>
To: Mike Fedyk <mfedyk@matchmail.com>, Shane Wegner <shane@cm.nu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE trouble under 2.2.19pre16 with Hedrick's IDE patch
Date: Tue, 06 Mar 2001 11:01:50 -0800 [thread overview]
Message-ID: <5.0.2.1.2.20010306110143.027c7698@pop.arraycomm.com> (raw)
In-Reply-To: <3AA447EA.CE0EC7AC@matchmail.com>
In-Reply-To: <20010304171528.A4966@cm.nu>
No this error is not by the wrong DMA settings. If you have a drive in dma
mode 5 and the controller does not support it, the kernel will give you a
proper error saying that this dma mode is not supported by the
controller. This is most likly something with the kernel. I'd try
upgrading to the latest 2.4.2-ac?? series.
Let me know if I'm mistaken about this one guys...
Jasmeet
At 06:14 PM 3/5/2001 -0800, Mike Fedyk wrote:
>Shane Wegner wrote:
> >
> > Hi,
> >
> > Whenever I write a substantial amount of data (200mb) to
> > disk, I get these messages. The disks lock for about 10
> > seconds and then come back for about 10 seconds again.
> > This continues until the data is successfully written.
> >
> > ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> > hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> > hde: DMA disabled
>It looks like you have set your drive for a dma mode it doesn't support.
>
>HTH
>
>Mike
>-
>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/
- - -
Jasmeet Sidhu
Unix Systems Administrator
ArrayComm, Inc.
jsidhu@arraycomm.com
www.arraycomm.com
prev parent reply other threads:[~2001-03-06 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 1:15 IDE trouble under 2.2.19pre16 with Hedrick's IDE patch Shane Wegner
2001-03-06 2:14 ` Mike Fedyk
2001-03-06 19:01 ` Jasmeet Sidhu [this message]
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=5.0.2.1.2.20010306110143.027c7698@pop.arraycomm.com \
--to=jsidhu@arraycomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--cc=shane@cm.nu \
/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.