On a different machine with an older Intel chipset (i945 IIRC), this bug is not reproducible. I don't know if it's due to different instruction set support or a different codepath in the X driver.
On a different machine with an older Intel chipset (i945 IIRC), this bug is not reproducible. I don't know if it's due to different instruction set support or a different codepath in the X driver.