http://bugzilla.opensuse.org/show_bug.cgi?id=851361 http://bugzilla.opensuse.org/show_bug.cgi?id=851361#c15 Egbert Eich <eich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sbrabec@suse.com) --- Comment #15 from Egbert Eich <eich@suse.com> --- (In reply to Stanislav Brabec from comment #14)

Should I re-post the bug to the upstream?

It happened several times before, but now the Xorg.0.log contains some data.

Unfortunately, this data is just the consequence of the lockup not the reason. The reason is hidden somewhere in the command stream sent to the GPU. Here's the deal: I've just slammed an RV620 into a TW box with updates as of today. I played with Google Maps as well as with the image in comment #4. I wasn't able to trigger the issue. I'm sure, if you run a 'dmesg' after a freeze occurred, you will find messages about a freeze and a subsequent engine reset. An upstream bug would be best although I'm not sure if you will catch people's attention on 8 year old hardware. I can help you to collect the right data before you report it upstream and I can also help you once it is upstream. So as a first step, let's collect 'dmesg' after a hang occurred. -- You are receiving this mail because: You are on the CC list for the bug.