Skip to contentSkip to conversation

sis5513 fatal udma problems

DISCUSSION Jim Studt 2 participants 2 messages Jan 3, 2001

lore
Share & tools
lore

Jim Studt

author
#0 lore 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? :-)

Signature · 6 lines
                                     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 [email protected]
Please read the FAQ at http://www.tux.org/lkml/
#1 lore raw
Quoted 21 lines · Jim Studt

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.

Quoted 6 lines

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.

Signature · 7 lines
-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 [email protected]
Please read the FAQ at http://www.tux.org/lkml/