I can confirm this on my system, using an S3 Inc. 86C380 [ProSavageDDR K4M266] (rev 02), which according to Xorg.0.log is a "Twister PN133", Chip: id 8d01.
After asking at the xorg mailing list, they directed me to the bug Marcelo Shima was pointing out on his last comment.
I can also run glxinfo, but executing glxgears results in a black window and 100% CPU usage.
So basically, it seems that the DRI locking was broken in the driver, and that that has now been fixed upstream using the following patch: https://bugs.freedesktop.org/attachment.cgi?id=7041 (see the bug report for more information)
I can confirm this on my system, using an S3 Inc. 86C380 [ProSavageDDR K4M266] (rev 02), which according to Xorg.0.log is a "Twister PN133", Chip: id 8d01.
After asking at the xorg mailing list, they directed me to the bug Marcelo Shima was pointing out on his last comment.
I can also run glxinfo, but executing glxgears results in a black window and 100% CPU usage.
So basically, it seems that the DRI locking was broken in the driver, and that that has now been fixed upstream using the following patch: https:/ /bugs.freedeskt op.org/ attachment. cgi?id= 7041 (see the bug report for more information)