Bug 50661
Summary: | sata_via VT8237 incompatibility with new WD drives | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | BunkoBugsy (vasarhelyizsolt) |
Component: | Serial ATA | Assignee: | Jeff Garzik (jgarzik) |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.9-103 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
BunkoBugsy
2012-11-16 09:01:13 UTC
lspci -xxx on Asus A7V880 configured for non-RAID mode gives following values 52=0x07 (Transport Miscellaneous Control) and 43=0x05 (FIFO Threshold Control) Based on http://www.yuiop.co.uk/epia/stuff/South%20%20Bridge/Data%20Sheet%20VT8237R%20South%20Bridge%20(Revision%202.06)(Lead-Free).pdf Flow Control Water Flag is configured for 32DW, opposed to the documented defaults. Libata module sata_via communicates with 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE Would trying to run setpci -s 00:0f.1 43=44 and setpci -s 00:0f.1 52=0 in rc.local worth a shot or am I reading the above linked data sheet wrong? I'd appreciate any help. Ok, misread dmesg, sata_via actually running on 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) I realize that kernel 2.6.32.7 won't ever make it to Centos 4.9 so I'll try to work this around by adding setpci -s 00:0f.0 52=4 to rc.local. *** This bug has been marked as a duplicate of bug 15173 *** |