> How well has the problem been nailed down? Could it be that it just
> showed up first on VIA and the real cause (and fix) remains to be
> discovered? Or does Serverworks somehow have an identical bug in
> their chipset?
There is a notional off by one in the check at least by the rules of the
original chip which do allow the overflow value to be visible momentarily.
Later -ac checks for > not >=
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
