Red Hat Bugzilla – Bug 18575
Strange X Windows Problem
Last modified: 2007-04-18 12:29:04 EDT
I'm having a very odd problem with RedHat7.0 ... seems that if my computer
sits dormant for any length of time X stops responding completely. If I
leave X running and come back everything looks normal, but nothing responds
... the mouse still moves the cursor around but no programs will respond
... even the logout does nothing and i have to ctrl+alt+backspace to get
out. If I exit out of X (even all the way out to the main login) and leave
the system dormant when i come back and log back in X wont even start. To
get anything X related to function I have to actually reboot the computer.
Do you have power saving enabled in the bios ?
Power management is enabled in BIOS. I dual boot with Win98 and would prefer to
keep it enabled as Windows uses the power management features without issue.
The idea here is to find out what is causing the problem. If you are
interested in solving this problem, please try the following:
Disable the Linux screensavers entirely, including monitor powerdown, etc.
Does the problem disappear?
If not, disable Power management in the BIOS as Alan eluded to. Boot
Linux, and try to reproduce the lockup.
Does the problem diisappear? If so, then we've located the problem.
If the problem is in fact power management related, leave the BIOS power
management off, and have windows do power management using other mechanisms
Another alternative for you is to try our latest XFree86 4.0.3 release
which may in fact solve the problem for you if it is in fact XFree86 related.
You'll also need Mesa 3.4-13. You can obtain these at:
You can find any other dependant packages in rawhide. If this does not solve
the problem for you I will need a copy of your Xserver logs from after the
lockup has occured, as well as a copy of your XF86config files. Please
also attache the output of "lspci -v" and "lspci -vn" as well. You can attach
these files via the link below.
Hopefully this will solve the problem for you.
G200 works in latest release fine, at least I can't reproduce this on