#648598 Gnome3: complete system freeze, fallback OK

Package:
xserver-xorg-video-radeon
Source:
xserver-xorg-video-ati
Description:
X.Org X server -- AMD/ATI Radeon display driver
Submitter:
Joost Kraaijeveld
Date:
2011-12-27 07:45:09 UTC
Severity:
important
#648598#5
Date:
2011-11-13 10:26:42 UTC
From:
To:
Dear Maintainer,

After some time running Gnome3 with the new shell my system lock up. It completely freezes, nothing works: no alt+F1 ,
ctrl+alt+del, alt-backspace, no remote login via ssh possible and the machine does not respons to pings. The only way to reboot
is using the power button (off and than on). Just using the reset button results in not finding the boot disk anymore. I can't find
anything in any of the log files (messages, kernel, debug, daemon). The freeze *almost* always happens during drag and drop operations or when using the mouse to click on icons (menu, evolution expanding threads etc). Sometimes it happens when doing nothing with the system but when audio is playing. Running Gnome3 in the fallback mode works OK and no freeze happens.
#648598#12
Date:
2011-11-14 14:15:11 UTC
From:
To:
I would suggest using KMS rather than UMS.  When you switch to KMS,
I'd also suggest using the r600 gallium 3D driver and removing the
Virtual line from your xorg.conf.

Alex
#648598#17
Date:
2011-11-14 14:15:11 UTC
From:
To:
I would suggest using KMS rather than UMS.  When you switch to KMS,
I'd also suggest using the r600 gallium 3D driver and removing the
Virtual line from your xorg.conf.

Alex
#648598#22
Date:
2011-11-14 14:34:35 UTC
From:
To:
disable that to be able to use the machine and file the bug. Sorry about
the confusion.

Further, is there a difference between the xserver-xorg-video-radion
driver and the "r600 gallium driver" and if so, what is the Debian
package for that? I did notice that glxinfo did say it was using gallium
0.4. Would that mean that I was using the right driver?
#648598#27
Date:
2011-11-14 14:34:35 UTC
From:
To:
disable that to be able to use the machine and file the bug. Sorry about
the confusion.

Further, is there a difference between the xserver-xorg-video-radion
driver and the "r600 gallium driver" and if so, what is the Debian
package for that? I did notice that glxinfo did say it was using gallium
0.4. Would that mean that I was using the right driver?
#648598#32
Date:
2011-11-14 16:19:46 UTC
From:
To:
On Mon, Nov 14, 2011 at 9:34 AM, Joost Kraaijeveld <J.Kraaijeveld@askesis.nl> wrote:

I'm not familiar with the debian packages.  The r600 gallium driver is
the 3D OpenGL driver. xorg-video-radeon is the Xorg ddx(2D, Xv,
xrandr, etc.).  If glxinfo says gallium 0.4 on RV670 that is correct.

Alex
#648598#37
Date:
2011-11-14 16:19:46 UTC
From:
To:
On Mon, Nov 14, 2011 at 9:34 AM, Joost Kraaijeveld <J.Kraaijeveld@askesis.nl> wrote:

I'm not familiar with the debian packages.  The r600 gallium driver is
the 3D OpenGL driver. xorg-video-radeon is the Xorg ddx(2D, Xv,
xrandr, etc.).  If glxinfo says gallium 0.4 on RV670 that is correct.

Alex
#648598#42
Date:
2011-11-14 17:41:52 UTC
From:
To:
[ Dropping submit@bugs.debian.org from CC, we don't want to keep
submitting new bug reports... ]

Is KMS stable with radeon.agpmode=-1? If not, please provide the
corresponding bug report information with KMS enabled.
#648598#47
Date:
2011-11-15 16:12:21 UTC
From:
To:
Setting agpmode=-1 in the radeon-kms.conf did not help.

Contents of radeon-kms.conf at the time of the crash:

options radeon modeset=1
options radeon agpmode=-1


After rebooting and login, the following sequence immediately
resulted in a complete system freeze as described in the original report:

- open the menu in the left upper corner
- start Evolution from the shortcuts
- start Totem from the shortcuts
- CRASH/FREEZE

I tried it several times, all with the same result.

Attached the the Xorg.0.log and dmesg from the last crash.
#648598#52
Date:
2011-11-15 16:39:46 UTC
From:
To:
Oh well, thanks for testing it.


https://bugs.freedesktop.org/show_bug.cgi?id=41838 (which is somewhat
similar in that it only happens with gnome-shell, though it's about a
different card generation) suggests that current upstream Mesa Git might
help, if you ever feel adventurous again.
#648598#57
Date:
2011-12-27 07:23:56 UTC
From:
To:
After upgrading to xserver-xorg-video-radeon 6.14.3-2 and gnome-shell
3.2.1-8, it took noticeably longer for the crash to happen, with
modeset=1 and NOT setting agpmode=-1. When I tried with agpmode=-1
enabled, the crash was almost instantly after the first click on a file
in Nautilus which was the first application I started.

The crash happened when I clicked on a Icedove (3.2.16) news group
thread to expand the thread.  Again nothing in the system logs but
the .xsession-error log attached) showed a triple "this should not be
happening! arrgggggh!". This message appears to be coming from Java
script code:
http://mxr.mozilla.org/comm-central/source/mailnews/db/gloda/modules/mimemsg.js#142.

BTW: this thread
http://web.archiveorange.com/archive/v/5xtclEOZOi0UA8C4qpun connects the
problem with a possibly faulty NVidia videodriver.

Is there anything I can do to help with good diagnostics? The problem is
rather annoying (which is an understatement), because the fall-back gets
almost unusable slow after some time. More specifically after opening
multiple windows and using Evolution. Performance returns only for a
short time after closing the windows and especially Evolution but for an
always short period. In the end I must reboot to get acceptable
performance again.

TIA