Chris Ridd wrote: >>> (EE) NVIDIA(0): Failed to initialize the GLX module; please check in >>> your X >>> (EE) NVIDIA(0): log file that the GLX module has been loaded in >>> your X >>> (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX >>> module. If >>> (EE) NVIDIA(0): you continue to encounter problems, Please try >>> (EE) NVIDIA(0): reinstalling the NVIDIA driver. >>> >> Please do: >> >> # svccfg -s ogl-select setprop options/vendor=nvidia >> # svcadm restart ogl-select >> >> and restart your desktop. This will cause the NVIDIA GLX module to load >> (and will stop the MESA GLX and swrast modules from being loaded). > > FWIW this is still happening on occasion (twice this morning) and it > always seems to happen when I'm using Thunderbird. I'm currently on > build 111a. > > Is there any way to debug this? Is AIGLX still being enabled or are you now using the NVIDIA GLX (a new /usr/bin/nvidia-SunOS-bug-report.sh would confirm). No board errors were detected in the previous log file so if it is the GPU hanging, it is doing it in a way the timeout detection in the driver misses it.
Since you have a NV43GL board, you can also try picking up a fix particular to that GPU from: http://home.comcast.net/~jdmartin99/NVIDIA-Solaris-x86-180.53-xVM.run However, I doubt this is what you are seeing given the frequency. Does this system have a serial port (ttya)?
