Well, subject says it all, the ATA driver in -stable is now functionally
identical to that in -current.
Please let me know asap if you encounter any (new) problems with the
ATA driver after this commit.
Thanks goes to all that have helped testing this over the last weeks,
and especially to
It seems Nils Holland wrote:
root@poison pciconf -r -b pci0:0:0 0x0:0xff
Thanks! this was a kernel without the corruption fix, and it shows
that you need it, the MWQ bug has been fixed in your BIOS...
I have a new improved patch in the works that covers more chipset
comboes, it'll go into
It seems Matthew Dillon wrote:
Ok, I have more information on Nils problem. First of all, Soren's
patch greatly reduced the rate of corruption. It took 25 loops of
Nils 'cp' test to generate the corruption.
Hmm, did the second change I posted change anything ?
However,
It seems Mike Silbersack wrote:
Agreed, it looks like the MWQ bug isn't addressed by soren's patch. The
decription at
http://www.networking.tzo.com/net/software/readme/faqvl019.htm
doesn't give enough info to patch it, but this post to the linux-kernel
mailing list seems to shed more light
It seems Matthew Dillon wrote:
I am trying to determine if our ATA/VIA setup code may have issues. I
did a google search and came up with a linux-quirks patch which may
apply to the random corruption problems people have been reporting.
Here is the URL:
It seems Matthew Gilbert wrote:
So, general question to everyone having crashes during heavy
IDE workloads: Please post your /var/run/dmesg.boot
output.
atapci0: VIA 82C686 ATA100 controller port 0xd000-0xd00f at device 7.1 on
You have the VIA 82c686b southbridge chip which
101 - 106 of 106 matches
Mail list logo
