From: Steven Walter <srwalter@yahoo.com>
To: Jim Studt <jim@federated.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sis5513 fatal udma problems
Date: Wed, 3 Jan 2001 16:02:08 -0600 [thread overview]
Message-ID: <20010103160208.A13576@hapablap.dyn.dhs.org> (raw)
In-Reply-To: <200101032110.PAA08416@core.federated.com>
In-Reply-To: <200101032110.PAA08416@core.federated.com>; from jim@federated.com on Wed, Jan 03, 2001 at 03:10:39PM -0600
On Wed, Jan 03, 2001 at 03:10:39PM -0600, Jim Studt wrote:
> The sis5513 has for quite a while had fatal problems with udma on some
> machines. (At least the thelinuxstore PIAs with the P6SET-ML
> motherboard, I have heard other people with the same problem).
>
> The sis5513 driver deliberatly overrides the CONFIG_IDEDMA_AUTO and
> the BIOS settings that might disable UDMA and forces UDMA which works
> for a while then fails, attempts to fallback to a non-DMA mode and
> fails that as well.
>
> The logs end up with something along the lines of...
> hdc: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hdc: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> hdc: status timeout: status=0xd8 { Busy }
> hdc: DMA disabled
> hdc: drive not ready for command
> ide1: reset: success
> hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> hdc: drive not ready for command
> ... but it nevers succeeds in the reset. The drive never becomes ready.
>
> I will make a patch, but I am uncertain what the `right' policy should
> be. I am inclined to first and foremost respect the CONFIG_IDEDMA_AUTO
> flag, then to take the fastest mode which is both capable and enabled in
> the bios.
>
> Thoughts? Please? :-)
What kernel version is this? If its a 2.2.x series kernel, try patching
it with Andre's IDE patches. I've had good luck using UDMA/33 on a
SiS530 (which uses the 5513 ide chipset) using Andre's patches. I've
also been able to use UDMA/33 and UDMA/66 with the latest 2.4.x kernels
and an 80-conductor cable (very important!). I haven't tried 2.2.x+ide
with UDMA/66, though it should work as well.
--
-Steven
"Voters decide nothing. Vote counters decide everything."
-Joseph Stalin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-03 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 21:10 sis5513 fatal udma problems Jim Studt
2001-01-03 22:02 ` Steven Walter [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=20010103160208.A13576@hapablap.dyn.dhs.org \
--to=srwalter@yahoo.com \
--cc=jim@federated.com \
--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