Thread (8 messages) 8 messages, 3 authors, 2004-08-30

Re: Libata VIA woes continue. Worked around - *wrong*

From: Jeff Garzik <hidden>
Date: 2004-08-29 07:58:13

Brad Campbell wrote:
Brad Campbell wrote:
quoted
Ok, so after a couple of reboots with max_sector set to 200 the 
problem re-occurs.

It must be something to do with programming the controller or timing 
or some other issue.

I have worked around it by putting my 2 raid-0 drives on my spare 
promise ports, and at UDMA100 with transfers of 2048 sectors they 
behave fine no matter what I throw at them.

Scratch that. After a couple of days if intensive testing/rebooting and 
abuse they play up on the
Promise controller in exactly the same failure mode. Just far harder to 
trigger.

I have removed these bridge board from my system now and thus the 
problem no longer exists. I'm a
little concerned that this might show itself for other people in the 
future but then I guess most
sane people buy SATA hard disks rather than re-use old ATA drives with 
bridge boards.
Well, there are some cases on a few controllers (SiI is one that comes 
to mind) where -- IIRC -- bridges dictate the max is UDMA/100, not 
UDMA/133, even if the underlying device is UDMA/133.

In sata_promise.c or sata_via.c, what happens if you change udma_mask 
from 0x7f to 0x3f?  Do the failures go away?

Cross that bridge if we come to it I guess.
Guffaw ;-)

	Jeff

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help