From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 65192] [r600g] Screensavers lock up machine (screen goes blank, keyboard unresponsive, sound loops; sysrq/ssh possible) Date: Mon, 03 Jun 2013 17:02:16 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0402238344==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 9764FE5D16 for ; Mon, 3 Jun 2013 10:02:16 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0402238344== Content-Type: multipart/alternative; boundary="1370278936.b47bbF40.14654"; charset="us-ascii" --1370278936.b47bbF40.14654 Date: Mon, 3 Jun 2013 17:02:16 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=65192 --- Comment #5 from Luzipher --- (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. --1370278936.b47bbF40.14654 Date: Mon, 3 Jun 2013 17:02:16 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 5 on bug 65192 from 
(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.
--1370278936.b47bbF40.14654-- --===============0402238344== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0402238344==--