https://bugs.freedesktop.org/show_bug.cgi?id=37785
Summary: [r600g Evergreen] GPU lockup on Blender 2.57 when moving objects Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: ahlaht@gmail.com
Created an attachment (id=47353) --> (https://bugs.freedesktop.org/attachment.cgi?id=47353) dmesg with errors
GPU lockup (waiting for 0x00004E51 last fence id 0x00004E50)
Using the latest git: Linux 2.6.39, drm 61be940, mesa 29ceeeb, xorg 1.10.2, ati 6.14.2
Hardware: HP laptop, Core i5-450M + Radeon HD 5650 REDWOOD (68C1)
Steps to reproduce:
1. Start Blender 2.57 normally: $ blender-2.5 --factory-startup
2. On the default scene with the cube press 'g' to move the cube
3. Use mouse to continuously move the cube on screen on random directions
4. After about 5 seconds Blender freezes but mouse cursor keeps moving
5. A GPU lockup occurs and the provided errors appear on dmesg
The bug is very easy to reproduce on my system. I can keep using the system normally after the bug, but sometimes I have to reset the video mode by switching to text console and then back to Xorg.
Also there is an alternative way to trigger the bug: Instead of moving the cube keep resizing any of the side panels continuously.
The problem disappears if I gpu-switcheroo to i965 so I assume this is something r600g related. Also I was not able to reproduce it on r600c.
https://bugs.freedesktop.org/show_bug.cgi?id=37785
--- Comment #1 from Antti Lahtinen ahlaht@gmail.com 2011-05-31 03:28:00 PDT --- Created an attachment (id=47354) --> (https://bugs.freedesktop.org/attachment.cgi?id=47354) Xorg.log
https://bugs.freedesktop.org/show_bug.cgi?id=37785
Antti Lahtinen ahlaht@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #2 from Antti Lahtinen ahlaht@gmail.com 2011-06-03 11:47:46 PDT --- It seems this was fixed by: b5518834e3ae117eafb32cfc5c7e7af51b4a1078 r600g: cs init fixes
Thanks.
dri-devel@lists.freedesktop.org