Description of problem:
Upon resume from a suspend to ram X does not resume. The system comes up
without much issue (network comes back up and it's capable of sshing into the
machine and running diagnostics) but X spins off and uses 100% of the CPU.
Doing an strace on the Xorg process shows that literally nothing is happening
(strace attachs but displays nothing). Process exsists in Rs+ state accroding
Version-Release number of selected component (if applicable):
xorg starting with FC6-test1
How reproducible / Steps to Reproduce:
1) Suspend machine (echo mem > /sys/power/state) - backlight turns off to the
screen but last image on screen still present.
2) Resume machine backlight turns on, machine resumes.
3) Image on screen is still of that just before suspend.
4) Machine is responsive, hitting the power button invokes the proper shutdown
command. If network is up sshing to the machine is possible.
Screen is frozen at the image prior to suspend.
Machine to come up and X to resume.
Only thing of note is that X has been acting odd as well, sometimes freezing
similar to the resume issue when opening apps though it's not as consistent.
The same problems are there, X is hung, but the system is still alive. Opening
Firefox (with about 100 tabs), evolution, openoffice and a few other large
programs might trigger the problem but it's not consistent
IBM T42 w/ ATI 7500 graphics card
2ghz Pentium M
This could be an X server problem, a video driver problem, a kernel problem,
or any host of other potential causes.
Please attach your X server log file, config file, /var/log/messages
as individual uncompressed file attachments using the link below.
Created attachment 131616 [details]
Created attachment 131617 [details]
Xorg log from a failed resume
Created attachment 131618 [details]
Pertinant section of the log file, from a bit before the suspend to a bit
afterwards. NetworkManager & dhcp messages were stripped because of their
frequency and tendency to clutter the log file
is this still happening with fc6 and/or current development?
Note, that you should try 'pm-suspend' instead of just doing the 'echo mem >
/sys/power/state'. pm-suspend knows modules that should be unloaded, and various
other workarounds for issues.
I have not seen this particular issue since test1 and I am now running the
2.6.19-1.2911.6.3.fc6 and am not seeing issues (and continuing to do echo mem >
/sys/power/state) I'm fine with the bug being closed.
ok. Thanks for the prompt reply.