Bug 38322

Created attachment 49663 [details]
Xorg log from the lockup

Bug still present with git version of radeon driver, attaching the Xorg.0.log

Please attach your dmesg output.

Created attachment 49665 [details]
/var/log/messages

Attaching /var/log/messages (hope that is what dmesg outputs :)), infinite loop happened couple of minutes before Jul 28, 13:53

Does a newer kernel help?  2.6.39 or 3.0?

It does not, I am using 3.0.0 from Debian experimental repository, it still persists.

(In reply to comment #6)
> While running KDE 4.6.3 (Compositing enabled)

Does disabling compositing or tiling work around the problem?

> on two monitors (configured with XRandr),

Please attach the output of

xrandr --verbose

when both monitors are enabled.

> when Goban screensaver starts, the whole graphic system freezes (box
> is still SSH-able tough) and only SysRq combo can reboot the machine. 

If you ssh in, is the X server (and goban, ...) process still alive? If yes, can you attach gdb to the X server and get a backtrace?

> Renderer: Mesa 7.10.2 r600g

Would a newer version of this help by any chance?

Created attachment 50066 [details]
`xrandr --verbose` output

Attaching the `xrandr --verbose` output when both monitors are enabled.

(In reply to comment #6)
> (In reply to comment #6)
> > While running KDE 4.6.3 (Compositing enabled)
> 
> Does disabling compositing or tiling work around the problem?

Disabling compositing does not help, as I turn it off when using second monitor for performance reasons. 

Before enabling Color Tiling I haven't encountered the problem. Now I have it turned on again for performance reasons.

> 
> > on two monitors (configured with XRandr),
> 
> Please attach the output of
> 
> xrandr --verbose
> 
> when both monitors are enabled.

Please see the last attachments.

> 
> > when Goban screensaver starts, the whole graphic system freezes (box
> > is still SSH-able tough) and only SysRq combo can reboot the machine. 
> 
> If you ssh in, is the X server (and goban, ...) process still alive? If yes,
> can you attach gdb to the X server and get a backtrace?

I will do so when I encounter the loop again. It is now not-so-predictable and various applications can trigger it in non-deterministic way.

Also I have upgraded my ati drivers yesterday (to the git head version) and I don't know yet if the problem persists.

> 
> > Renderer: Mesa 7.10.2 r600g
> 
> Would a newer version of this help by any chance?


Upgrading to 7.11 branch (from Debian experimental repository) did not help.

Created attachment 50069 [details]
Xorg backtrace

Xorg backtrace from the crash (caused by running screensaver and quitting it successfully twice and starting Digikam afterwards)

Would http://lists.x.org/archives/xorg-devel/2011-August/024291.html help by any chance?

Thanks, I tested the patch, and so far it looks stable.

(In reply to comment #11)
> Thanks, I tested the patch, and so far it looks stable.

Thanks, can you please test http://lists.x.org/archives/xorg-devel/2011-August/024302.html as well?

(In reply to comment #12)
> (In reply to comment #11)
> > Thanks, I tested the patch, and so far it looks stable.
> 
> Thanks, can you please test
> http://lists.x.org/archives/xorg-devel/2011-August/024302.html as well?

Yes, this patch looks stable too.

The fix has landed in xserver master, and I nominated it for the 1.10 branch.

Thanks.