In the course of using Wings3D (a 3D modeling program, basically CAD), I get what is reported in the kernel log as a GPU lockup. It happens as follows: 1. Start up the program, and begin creating/manipulating some geometry. 2. At some point, the display freezes, with the exception of the mouse pointer. It remains like this for about ten seconds. 3. The display goes black for a few seconds, and then the previous screen returns. 4. The display now responds, with the caveat that the mouse pointer is now invisible. (You can see menu items and such prelight under it, which is about the only way you can tell where it is.) 5. If you can kill Wings3D, everything is back to normal. To aid in debugging, I've put together a log file (attached) that combines the following three streams, interleaved in time: * Normal terminal output from Wings3D (there's only a bit of this, at the beginning and end) * Additional terminal output from having set RADEON_DEBUG=all * Kernel messages in /var/log/messages (search for "GPU lockup") I am running Ubuntu Maverick on amd64 with kernel 2.6.36 plus Alex Deucher's patch for bug #25544, and Mesa packages from Ubuntu's xorg-edgers/radeon PPA built from git 20101103. My video board is an ATI FireGL 8800.
Created attachment 40072 [details] RADEON_DEBUG=all + /var/log/messages interleaved output
No longer reproducible with a recent git build. Will re-open if the bug crops up again.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.