From: Jim Studt <jim@federated.com>
To: linux-kernel@vger.kernel.org
Subject: sis5513 fatal udma problems
Date: Wed, 3 Jan 2001 15:10:39 -0600 (CST) [thread overview]
Message-ID: <200101032110.PAA08416@core.federated.com> (raw)
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? :-)
--
Jim Studt, President
The Federated Software Group, Inc.
-
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/
next reply other threads:[~2001-01-03 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 21:10 Jim Studt [this message]
2001-01-03 22:02 ` sis5513 fatal udma problems Steven Walter
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=200101032110.PAA08416@core.federated.com \
--to=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