6 Replies Latest reply: Dec 20, 2012 8:04 PM by Grant Bennet-Alder
Jesper79 Level 1 Level 1 (0 points)

Hi all.


After having installed Mountain Lion on my Mac Pro (just over 1 year old), I´m having a strange problem.


If I´m gone from the computer for a short while, the computer goes into "sleep" mode (sorry, don´t know the correct term). When I come back, I just hit a key og move the mouse, and the computer wakes up.. Brilliant... works as it should do!


BUT, if I´m gone for a longer period of time (say 60 minutes plus), there´s absolutely nothing I can do to make it start again. I can hear that it´s on, and the light indicator over the power button is on, but nothing happens?! Only thing I can do is to hold down the power button until the computer shuts down, and then turn it on again.


This is really annoying, and has only happend with Mountain Lion.

Hope someone can help




Mac Pro, OS X Mountain Lion (10.8.2)
  • Grant Bennet-Alder Level 9 Level 9 (54,295 points)

    You may have had a kernel panic.


    Kernel Panic information is saved in logs and can be read out and examined for clues about the failure. This article show how to get them out, and you can just cut and paste them here for Readers to look at for clues, or take them to the Genius Bar.


    Mac OS X: How to log a kernel panic

  • Linc Davis Level 10 Level 10 (177,815 points)

    If you have more than one user account, these instructions must be carried out as an administrator.

    Launch the Console application in any of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

    Step 1

    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.

    Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Post the messages logged before the boot, while the system was unresponsive or was failing to shut down. Please include the BOOT_TIME message at the end of the log extract.

    Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message. When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

    Please do not indiscriminately dump thousands of lines from the log into a message.

    Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.

    Step 2

    Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the entire contents of the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

  • Jesper79 Level 1 Level 1 (0 points)

    Really appreciate your efforts to help.

    Hope this is what you´re asking for:


    20/12/12 23.27.20,462 mdworker[1195]: Unable to talk to lsboxd

    20/12/12 23.27.20,498 sandboxd[1197]: ([1195]) mdworker(1195) deny mach-lookup com.apple.ls.boxd

    20/12/12 23.27.20,000 kernel[0]: Sandbox: sandboxd(1197) deny mach-lookup com.apple.coresymbolicationd

    20/12/12 23.28.22,000 kernel[0]: HID tickle 7733484 ms

    20/12/12 23.29.08,000 bootlog[0]: BOOT_TIME 1356042548 0


    These are the ones that appear just above the boot time, and they all appear quite a few times.


    Hope you can help!



  • Linc Davis Level 10 Level 10 (177,815 points)

    You tried to wake up the screen by moving the mouse, and then 45 seconds later you forced a reboot. There's no indication of what happened between those events.


    Try resetting the System Management Controller (SMC).

  • Jesper79 Level 1 Level 1 (0 points)

    This time I didn´t really do anything between moving the mouse and forcing a reboot. I know that nothing works...

    I really don´t see what I could have missed?


    I´ll try resetting the SMC (although I don´t see how the computer knows that the power cord is pulled out when it´s shut down??)


  • Grant Bennet-Alder Level 9 Level 9 (54,295 points)

    I don´t see how the computer knows that the power cord is pulled out when it´s shut down??


    When power is COMPLETLY removed, then restored, some Analog circuits on the processor board issue a Reset signal to just about everything, including the System Management Controller (an additional little processor that handles a lot of system details).


    It all wakes up perfectly synchronized and feeling much better.