It seems Matthew Dillon wrote:
> This is great news! I'm crossing my fingers and hoping that Nils can't
> reproduce the crash any more with Soren's fix.
Me too :)
I have a small change that can be used if performace suffers too badly,
it has not provoked the problem again on any of the systems I've
tried it on so far.:
--- ata-pci.c 25 Dec 2001 14:44:26 -0000 1.24
+++ ata-pci.c 27 Dec 2001 17:24:32 -0000
@@ -97,9 +97,9 @@
if (pci_get_devid(child) == 0x03051106 || /* VIA KT133 */
pci_get_devid(child) == 0x03911106) { /* VIA KX133 */
- pci_write_config(child, 0x75, 0x83, 1);
+ pci_write_config(child, 0x75, 0x80, 1);
pci_write_config(child, 0x76,
- (pci_read_config(child, 0x76, 1) & 0xdf) | 0xd0,1);
+ (pci_read_config(child, 0x76, 1) & 0xf) | 0xd0, 1);
device_printf(dev, "VIA '686b southbridge fix applied\n");
break;
}
> I'm also wondering how applicable this patch might be in regards to
> forcing a 'safe' mode for other PCI chipsets, to allow us to test
> it on non-686B machines that have similar problems.
This patch is specific for VIA K[TX]133 northbridges together with
the 686B southbridge. There might be issues with other new VIA
chipsets that uses the 686B or derivatives, but I have no way to
test that as I dont have any of that HW here in the lab.
-S�ren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
