Some AWT tests deadlock on CentOS 5.4 64-bit. Simple tests like TestGearsAWT deadlock on exit; other tests like TestSharedContextListAWT give an error, but when you look at the stack trace, it's locked up the same way. The NEWT tests and others are OK, so I'm sure my driver is OK this time :)
I'm on CentOS 5.4 64-bit (Linux 2.6.18-164.el5). Video card is a Quadro NVS 295, driver version 260.19.29, X server version 11.0, vendor version 7.1.1 (70101000).
Created attachment 213 [details]
Debug log file
Created attachment 214 [details]
Stack trace (threads suspended after hang)
Here's what the call stack of the threads looks like when I suspend it after it hangs. The Unsafe.park() seems to be a common feature of other tests that deadlock (like TestGearsAWT).
CentOS 6.0 / x86_64 / amd rv620:
X.Org X Server 1.7.7
java version "1.6.0_17"
OpenJDK Runtime Environment (IcedTea6 1.7.9) (rhel-1.36.b17.el6_0-x86_64)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
Default hw accelerated OpenGL:
GL_RENDERER = Mesa DRI R600 (RV620 95C5) 20090101 TCL DRI2
GL_VERSION = 1.5 Mesa 7.7.1
No deadlock, however the mesa3d radeon driver has no pbuffer support,
and also lacks some other glsl features etc.
ati fglrx 11.11 OpenGL:
GL_RENDERER = ATI Radeon HD 3450
GL_VERSION = 3.3.11251 Compatibility Profile Context
No deadlock, all unit tests passed,
even though it took 16 minutes due to some xrandr slowness for the ScreenMode tests.