I am changing the title a little. Note that the Pentium bug is caused by
a modified form of the Compare and Exchange instruction when executed in
locked mode - suspiciously similar to the Cyrix bug, isn't it ?
Happily we seem to have a solution. :-)
Problem:
==========
B. James Phillippe wrote:
...
> Do you know if the S3 Trio 64 PCI-based video card might have this
> problem? My 2.1.62 system with the 6x86 and no-lock setting froze after
> about 20 minutes in X, as soon as I tried to start Communicator 4.03
> (which worked fine previously). After rebooting, I've been leary to go
> into X or start Communicator, and the system has been running fine now for
> about 2 hours, with the same no-lock setting (and I ran an exhaustive
> benchmark on it during that time, as well).
...
Solution:
==========
OK, now please _revert_ your previous no_lock patch. Recompile :-(
Reinstall :-( Reboot :-(
As my grandma used to say: "I told you!" ;-)
This time, _please_ use set6x86. I can assure you that it takes less
time to download, compile and install set6x86 than to recompile the
kernel. Just add the following line to the default rc.cyrix script:
set6x86 -p 0xe3 -s 0x04
This sets weak locking _only_ in the DRAM, and enforces strong locking
elsewhere (i.e. on all PCI memory space).
Check that ARR7 is correctly set using the utility that comes with
set6x86.
Now please reload X, test Netscape, etc...
Testing goes on. :-)
Cheers,
========================================================
Andrew D. Balsa
Home Page: http://www.tux.org/~balsa
andrewbalsa@usa.net
========================================================