[Bug 65192] [r600g] Screensavers lock up machine (screen goes blank, keyboard unresponsive, sound loops; sysrq/ssh possible)

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=65192

--- Comment #5 from Luzipher <luziphermcleod at yahoo.ie> ---
(In reply to comment #4)
> Beware that AFAIK the screensaver hacks aren't spawned from the
> xscreensaver-demo process but from the xscreensaver daemon process. Did you
> confirm that the latter saw the environment variable?

I'm very sure that the environment variable is seen. Today, I added it to my
/etc/environment again, restarted, and confirmed it is there by echo
$R600_HYPERZ, which printed 0, as expected.
I'm starting X manually (with startx), so I'm quite certain that the
xscreensaver daemon process also sees the variable.

All the following tests have been done with R600_HYPERZ=0 in /etc/environment.

As I mentioned in my previous comment, starting antmaze with the command
R600_HYPERZ=0 /usr/lib/misc/xscreensaver/antmaze
works more often. In fact I couldn't get it to crash in about 25 tries today.

What did crash was again juggler3d on the third try when _closing_ its window.
The command used was:
R600_HYPERZ=0 /usr/lib/misc/xscreensaver/juggler3d

Also, by using the xscreensaver-demo application (with R600_HYPERZ=0 in
/etc/environment) and switching between random screensavers, I could trigger a
crash quickly.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130603/e7280ef1/attachment.html>