FS#7497 - Unexpected Lockups in X & GNOME
Attached to Project:
Arch Linux
Opened by Alper Kanat (T-u-N-i-X) - Saturday, 23 June 2007, 15:13 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 09 February 2008, 17:28 GMT
Opened by Alper Kanat (T-u-N-i-X) - Saturday, 23 June 2007, 15:13 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 09 February 2008, 17:28 GMT
|
Details
I experiment some lockups during daily (normal) usage in
GNOME. Such programs like Firefox, Totem or Pidgin sometimes
a program stops responding for a while. Earlier, when I
click on the Exit button for a few times, a messagebox was
appearing that the program stopped responding and if i want
to close it.. When I say yes, it would kill the
processes..
Now, that messagebox generally doesn't appear and X or GNOME locks up. I can move the mouse but none of my clicks or keyboard inputs are accepted. I'm not able to drop to the console by pressing CTRL-ALT-F1.. If i do, i simply kill the processes by myself but the lockup could continue. It's very annoying but I don't know how to replicate this problem. Hope it gets solved.. |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Saturday, 09 February 2008, 17:28 GMT
Reason for closing: Fixed
Additional comments about closing: Author's issue is fixed,
other reports about lookups may be unrelated - reopen separate bugreports if still they're still valid.
Saturday, 09 February 2008, 17:28 GMT
Reason for closing: Fixed
Additional comments about closing: Author's issue is fixed,
other reports about lookups may be unrelated - reopen separate bugreports if still they're still valid.
Do you have some specific applets or other window managers or aiglx/xgl running?
Please provide more details.
If you have something like cpufrequtils/etc. + powernow-k8/speedstep/etc. installed - these lockups may happen (for ~0.5 sec) when CPU is changing its frequency.
I think it depends on motherboard too (I didn't notice this on some motherboards, on same situations).
In my case, the mouse still moves, but does appear to interact with any elements on the screen. This problem seems to present itself after the computer has been idle for some time. I have a dual-core proc and I can ssh in to the box and look at the CPU stats in htop while this is going on, the two cores sitch back and forth on high cpu usage. Core0 will show the x process at 90+% cpu for a couple of seconds, then core1 will take on the load, then core0, etc. If you wait long enough, it seems that the system actually is responding to mouse clicks, just very slowly. One time I left the machine alone for about fifteen minutes and it appeared to have stopped, although I have not been able to recreate this.
I have tried to look for a pattern based on which apps were left open, whether beryl was running or not, etc. and I can't seem to find a common denominator other than it usually is occurring when I sit down at the machine after being away for some time.