> > Note that there are two different techniques for working around the bug:
> >
> > - set the NO_LOCK bit in CR<whatever>; can cause problems in obscure
> > circumstances (Alan mentioned a graphics / accelerator card problem)
>
> To repeat myself: this crept into linux-2.2.8, ...
I know. I may have said 2.2.7 in a previous message by accident.
>
> > - do some undocumented magic provided by (or reverse engineered from)
> > Cyrix, that seems to modify the CPU behaviour when executing the
> > offending instruction, making to do a noop afterwards. I don't know
> > of any problems caused by this.
>
> ... and this is already in 2.2.10. Don't you guys read the code others
> write?
> :-(
I was summarising the two different fixes and any associated problem as I
understand them. I know about them *because* I read the code; what's your
problem?
--
Satellite Safety Tip #14:
If you see a bright streak in the sky coming at you, duck.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/