6

I have a Mac which regularly runs into a problem. The user interface stops reponding, showing a "frozen" user interface. The mouse is still moving but clicking does not trigger anything. This happens about once a week. Solution so far is to force switch-off the Mac and reboot it.

I have ssh root access to the Mac. Killing (kill -9) the active application has no visible impact on what is shown on the screen.

Any ideas on how to diagnose this?

Is there a way to restart the window manager from the ssh shell? Killing /System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphics.framework/Resources/WindowServer seems not to be possible.

The Mac is an early 2008 iMac and runs Lion with latest updates. /Library/Logs/DiagnosticReports is empty.

Update:

Problem stays after update to Mountain Lion.

The WindowServer process is in "uninterruptible wait" state ("U" flag in ps output set):

imac:~ root# ps ax|awk "NR==1|| /WindowServer/"|grep -v awk
  PID   TT  STAT      TIME COMMAND
   86   ??  Us    50:51.69 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphics.framework/Resources/WindowServer -daemon

Any idea for diagnosing what blocks the process?

Any idea for "waking up" the process?

4
  • Rather than DiagnosticReports, check the All Messages output under Console.app
    – slhck
    May 25, 2012 at 8:52
  • Can one access the Console.app output from the ssh session after the machine froze? Otherwise I would need to run all applications non-fullscreen in order to have Console.app always visible. That would be rather uncomfortable.
    – Bernd
    May 25, 2012 at 10:33
  • I think most importantly /var/log/system.log, see also man syslog
    – slhck
    May 25, 2012 at 12:43
  • I did check /var/log/system.log. The last entry before the freeze happend is >15 min. before the freeze happended. ("imac SoftwareUpdateCheck[3036]: SoftwareUpdateCheck (Launch): non-admin user" and "imac com.apple.launchd.peruser.503[205] (com.apple.softwareupdateagent): Throttling respawn: Will start in 1500 seconds")
    – Bernd
    May 25, 2012 at 12:49

1 Answer 1

3

Your log message seems barely related to the problem.

The command to restart the window server is the following, with HUP being a special signal. It's more or less equivalent to logging out from the graphical environment. Beware that all apps are quit immediately.

sudo killall -HUP WindowServer

Of course, this will only cure the symptoms, not the actual cause of the problem. I'd suggest to continue investigating logs of some sort, or trying with another user profile to see if the problem persists (if not, then simply migrate your profile to the new one).

1
  • 1
    I did a killall -HUP on the WindowServer, result was a spinning gear (not the rainbow ball) on top of the frozen screen, running forever. The WindowManager did not restart.
    – Bernd
    May 25, 2012 at 20:43

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.