Often with these 100% X cpu bugs, the problem is caused by a client
application, which is stuck in a loop making X requests. In such cases,
the debugging procedure is to examine your process table (e.g. `ps aux`)
and start killing processes one by one until the system unfreezes.
However, the fact that this occurs on resume makes this bug sound a bit
different. It can't hurt to try the above, and it might turn up
something (I'd probably test killing gnome-settings-daemon, compiz/unity
and some of the other gnome infrastructural bits first).
If all that fails, you can connect to the running X process using gdb
and gather a series of backtraces to see what series of routines it is
hitting. strace can be used here too, although with the X server it
produces so much output it's often unusable for diagnostics.
** Changed in: fglrx-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/968265
Title:
Resuming from sleep leaves Xorg using 100% CPU and unable to turn on
the screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/968265/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
