Topic Title: fglrx, catalyst 9.12, HD4200 Spurious system crashes FIXED Topic Summary: How to debug total system crashes if xinerama is disabled with a dual head setup. Created On: 01/27/2010 10:06 AM Status:
UPDATE: Pls ignore this post - its a problem with KDE not fglrx
MOBO Gigabyte GA-MA-785GMT-UD2H (AM3)
CPU AMD 640 X4
IGP ATI Radeon HD4200 Linux (Fedora) 188.8.131.52-105.2.4.fc11.x86_64
2D Driver Version 8.68.2 Catalyst Control Center Version 2.11
If I set catalyst up with xinerama to drive my twin monitors:
Everything works fine - very robust - no crashes ever.
(note: Compositing is not available for KDE or Gnome desktop effects however)
If I set catalyst up without xinerama:
Everything works fine for a while - upto say 4 hours - then themachine completely crashes; no network, no nothing; a hard reset is required.
The crash happens when the mouse cursor is moving from one monitor to the other. It is sometimes (not always) possible to induce a crash by waving the mouse rapidly between the two monitors.
Using gdm, kdm, gnome or kde makes no difference.
(note: Compositing is available if xinerama is disabled but it makes no difference to the crashing problem whether it's enabled or not)
0. The system is not overclocked.
1. Fglrx kernel module compiles perfectly.
2. With xinerama disabled, the very first time a popup menu appears it is corrupt - looks like an old TV which has lost vertical sync. - black background with diagonal white stripes. It is rapidly repainted correctly however. This behaviour does not happen if xinerama is enabled. (Might suggest memory mapping/initialisation problem?)
3. With or without xinerama /var/log/Xorg.0.log does not show any error messages - just a few innocuous warnings.
4. Because it's a total system failure there's nothing in /var/log/messages or /var/log/dmesg to investigate.
5. I'd prefer to not use xinerama. Certain apps. and the system generally seems "happier" without it.
Any thoughts, solutions or hints on how to debug further please?