Created attachment 365928 [details]
Xorg.0.log from when problem occured.
Description of problem:
Xorg stopped responding to keyboard input. Mouse movement continued, but no
response to mouse clicks. Xorg was consuming all available CPU time.
Version-Release number of selected component (if applicable):
Don't know which of these are relevant, so listing all for completeness:
It has happened about a dozen times now over a couple of months - no idea what triggers it
Steps to Reproduce:
Keyboard and mouse click inputs stopped responding
killall -9 Xorg from an ssh session allowed my to log back in again.
Graphics chip is an NVIDIA GeForce FX Go5650
Created attachment 365929 [details]
gdb bt -f output
I had not had this problem since I originally opened bug #517625,
but it occurred again. I attach the output of gdb backtrace, and
strace -p as requested.
Update package versons:
No doubt others of the packages have been updated, but these seem the salient ones.
Created attachment 365930 [details]
strace -p output
I have truncated the output since there were thousands of lines all the same
Do you happen to have your kernel log from when this issue occurred? The output of the dmesg command while the machine is hung would be perfect, /var/log/messages will do otherwise.
Created attachment 366271 [details]
/var/log/messages during suspend/resume
Ok, there was no mention of suspend/resume prior to this? The problem doesn't occur without using it?
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions).
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
I haven't experienced this problem for a couple of months now.
Thank you for letting us know.