OSX 10.8.2 on a mid 2010 macbook pro sleep issue...

Question

Level 1

0 points

OSX 10.8.2 on a mid 2010 macbook pro sleep issue...

OSX 10.8.2 on a mid 2010 macbook pro. After my laptop goes into sleep mode and I come back and try to log in, the login screen appears but is completely frozen. It will show a time stamp in the menu bar of yesterday afternoon, assuming I let the machine sleep overnight. Any troubleshooting tips on how to find out what was happeing on the machine at that time? Are the event viewers, logs or anything like that?

MacBook Pro (15-inch Mid 2010), Mac OS 8.6 or Earlier

Posted on Oct 9, 2012 6:59 AM

Reply

Answer 1

Linc Davis

Level 10

209,547 points

Oct 9, 2012 11:11 AM in response to kbindera

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 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.

Reply

Answer 2

Oct 9, 2012 11:34 AM in response to kbindera

I've seen many posts on this issue which apparently appears after the 10.8.2 update.

First try a SMC reset.

Then do a Disk Repair

Then download a install the 10.8.2 Combo update.

You can install it right over the Delta update you recently installed with no issues.

DALE

Reply

Answer 3

kbindera Author

Level 1

0 points

Oct 10, 2012 10:33 AM in response to Linc Davis

Linc,

Thanks for the reply. No System Diagnostic Reports but I did include system log entries from right before the hang. Here they are:

10/9/12 3:26:24.000 PM kernel[0]: vmnet: Failed to deep copy mbuf: 12.

10/9/12 3:26:24.000 PM kernel[0]: vmnet: netif-vmnet8: couldn't dup mbuf: 12.

10/9/12 3:28:01.785 PM WindowServer[80]: CGXRegisterWindowWithSystemStatusBar: window 17 already registered

10/9/12 3:28:04.803 PM com.apple.launchd[1]: (com.apple.sleepservicesd[482]) Exited: Killed: 9

10/9/12 3:28:04.000 PM kernel[0]: memorystatus_thread: idle exiting pid 482 [SleepServicesD]

10/9/12 3:28:07.845 PM WindowServer[80]: CGXRegisterWindowWithSystemStatusBar: window 17 already registered

10/9/12 3:28:23.198 PM com.apple.launchd[1]: (com.apple.sleepservicesd[493]) Exited: Killed: 9

10/9/12 3:28:23.000 PM kernel[0]: memorystatus_thread: idle exiting pid 493 [SleepServicesD]

10/9/12 3:28:43.452 PM WindowServer[80]: CGXRegisterWindowWithSystemStatusBar: window 17 already registered

10/9/12 3:28:44.182 PM WindowServer[80]: CGXGetWindowInfo: Invalid window 251

10/9/12 3:28:44.184 PM Dock[187]: CGSBindWindow: Unable to obtain window information

10/9/12 3:28:44.185 PM Dock[187]: CGSGetWindowTags: Invalid window 0xfb

10/9/12 3:28:44.185 PM Dock[187]: find_shared_window: WID 250

10/9/12 3:28:45.147 PM WindowServer[80]: CGXGetWindowType: Invalid window 259

10/9/12 3:28:45.147 PM Dock[187]: find_shared_window: Invalid depth WindowID 0x103

10/9/12 3:28:45.147 PM Dock[187]: CGSGetWindowTags: Invalid window 0x103

10/9/12 3:28:45.147 PM Dock[187]: find_shared_window: WID 258

10/9/12 3:28:45.928 PM com.apple.launchd[1]: (com.apple.sleepservicesd[498]) Exited: Killed: 9

10/9/12 3:28:45.000 PM kernel[0]: memorystatus_thread: idle exiting pid 498 [SleepServicesD]

10/9/12 3:28:46.227 PM com.apple.launchd.peruser.501[137]: ([0x0-0x31031].com.apple.inputmethod.ironwood[492]) Exited: Killed: 9

10/9/12 3:28:46.000 PM kernel[0]: memorystatus_thread: idle exiting pid 492 [DictationIM]

10/9/12 3:28:46.703 PM com.apple.launchd.peruser.501[137]: (com.apple.tccd[480]) Exited: Killed: 9

10/9/12 3:28:46.000 PM kernel[0]: memorystatus_thread: idle exiting pid 480 [tccd]

10/9/12 3:28:58.256 PM com.apple.launchd[1]: (com.apple.sleepservicesd[505]) Exited: Killed: 9

10/9/12 3:28:58.000 PM kernel[0]: memorystatus_thread: idle exiting pid 505 [SleepServicesD]

10/9/12 3:28:58.557 PM com.apple.launchd[1]: (com.apple.cfprefsd.xpc.daemon[475]) Exited: Killed: 9

10/9/12 3:28:58.000 PM kernel[0]: memorystatus_thread: idle exiting pid 475 [cfprefsd]

10/9/12 3:28:58.904 PM com.apple.launchd.peruser.501[137]: (com.apple.cfprefsd.xpc.agent[473]) Exited: Killed: 9

10/9/12 3:28:58.000 PM kernel[0]: memorystatus_thread: idle exiting pid 473 [cfprefsd]

10/9/12 3:29:00.404 PM WindowServer[80]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff

10/9/12 3:29:00.504 PM loginwindow[55]: find_shared_window: WID -1

10/9/12 3:29:00.504 PM loginwindow[55]: CGSGetWindowTags: Invalid window 0xffffffff

10/9/12 3:29:00.504 PM loginwindow[55]: find_shared_window: WID -1

10/9/12 3:29:00.504 PM loginwindow[55]: CGSSetWindowTags: Invalid window 0xffffffff

10/9/12 3:29:00.894 PM mds[51]: (Normal) DiskStore: Disk store AC wakeup

10/9/12 3:29:00.944 PM loginwindow[55]: *** WARNING: -[NSImage compositeToPoint:operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.

10/9/12 3:29:00.946 PM loginwindow[55]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.

10/9/12 3:29:01.083 PM helpd[178]: Could not find access page in directory /Applications/LeapFrogConnect.app/Contents/Resources/English.lproj/Help

10/9/12 3:29:01.154 PM WindowServer[80]: Created shield window 0x108 for display 0x04272ec0

10/9/12 3:29:01.156 PM WindowServer[80]: device_generate_desktop_screenshot: authw 0x7fc571454860(2000), shield 0x7fc575226170(2001)

10/9/12 3:29:01.223 PM WindowServer[80]: device_generate_lock_screen_screenshot: authw 0x7fc571454860(2000), shield 0x7fc575226170(2001)

10/9/12 3:29:01.000 PM kernel[0]: vmnet: bridge-en1: interface en is coming UP

10/9/12 3:29:01.000 PM kernel[0]: vmnet: bridge-en1: interface en is going DOWN

10/10/12 9:17:56.000 AM bootlog[0]: BOOT_TIME 1349875076 0

Reply

Answer 4

Linc Davis

Level 10

209,547 points

Oct 10, 2012 11:06 AM in response to kbindera

Please read this whole message before doing anything.

This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

The purpose of this test is to determine whether your problem is caused by third-party system modifications that load automatically at startup or login.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:

Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
When you see the gray Apple logo, release the shift key.
If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.

*Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.

Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.

The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. Same problem?

After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

Reply

Answer 5

kbindera Author

Level 1

0 points

Oct 11, 2012 7:50 AM in response to Linc Davis

I ran the test and took the machine into safe mode, as you describe. After an extended sleep, I was able to interact with the login screen and log into the desktop. However, once it appeared, I got the spinning beach ball and was not able to intereact with anything. I had to do a hardset after a few minutes of this. I noticed that the time stamp on the tool bar was still reflecting last night's time, when I last interacted with the machine.

Reply

Answer 6

kbindera Author

Level 1

0 points

Oct 11, 2012 7:58 AM in response to kbindera

One more bit of info. I checked the Console log and did not see anything logged there from the desktop interaction I described above. But here is what was available from my last interaction:

10/10/12 7:40:01.527 PM SystemUIServer[162]: -[TCMPortMapper networkDidChange:] NSConcreteNotification 0x7fd39a81a7d0 {name = State:/Network/Global/IPv4; object = <IXSCNotificationManager: 0x7fd39ac60540>; userInfo = {

PrimaryInterface = en1;

PrimaryService = "<DELETED>";

Router = "<DELETED>";

}}

10/10/12 7:40:01.529 PM UserEventAgent[10]: Captive: en1: Not probing '<DELETED>' (protected network)

10/10/12 7:40:01.531 PM awacsd[48]: InnerStore GetWakeInfoForZone: no external port for 88060011.members.btmm.icloud.com.

10/10/12 7:40:01.533 PM configd[17]: network changed: v4(en1!:<DELETED>) DNS Proxy SMB

10/10/12 7:40:01.536 PM SystemUIServer[162]: -[TCMPortMapper networkDidChange:] NSConcreteNotification 0x7fd399cf7780 {name = State:/Network/Global/IPv4; object = <IXSCNotificationManager: 0x7fd39ac60540>; userInfo = {

PrimaryInterface = en1;

PrimaryService = "B5B77841-BC92-46B1-9076-E44D074B3C55";

Router = "<DELETED>";

}}

10/10/12 7:40:01.984 PM hidd[74]: MultitouchHID: device bootloaded

10/10/12 7:40:02.297 PM awacsd[48]: InnerStore GetWakeInfoForZone: no external port for 88060011.members.btmm.icloud.com.

10/10/12 7:40:02.496 PM airportd[319]: _doAutoJoin: Already associated to “<DELETED>)”. Bailing on auto-join.

10/10/12 7:40:02.585 PM SystemUIServer[162]: NAT-PMP: found IP:<DELETEDD>

10/10/12 7:40:07.244 PM CalendarAgent[156]: [com.apple.calendar.store.log.caldav.queue] [Account refresh failed with error: Error Domain=NSURLErrorDomain Code=-1003 "A server with the specified hostname could not be found." UserInfo=<DELETED>{NSUnderlyingError=0x7fa8e04a63c0 "A server with the specified hostname could not be found.", NSErrorFailingURLStringKey=https://<DELETED> NSErrorFailingURLKey=https://<DELETED>, AccountName=iCloud, CalDAVErrFromRefresh=YES, NSLocalizedDescription=A server with the specified hostname could not be found.}]

10/10/12 7:40:07.300 PM WindowServer[105]: Created shield window 0x89 for display 0x04272ec1

10/10/12 7:40:07.301 PM WindowServer[105]: device_generate_desktop_screenshot: authw 0x7febf380ea20(2004), shield 0x7febf261c490(2001)

10/10/12 7:40:07.301 PM com.apple.time[10]: Next maintenance wake [Backup Interval]: <date: 0x7fd313e02b00> Wed Oct 10 19:41:05 2012 EDT (approx)

10/10/12 7:40:07.301 PM com.apple.time[10]: Requesting maintenance wake [Backup Interval]: <date: 0x7fd313e02b00> Wed Oct 10 19:41:05 2012 EDT (approx)

10/10/12 7:40:07.315 PM WindowServer[105]: device_generate_lock_screen_screenshot: authw 0x7febf380ea20(2004), shield 0x7febf261c490(2001)

Reply

Answer 7

Linc Davis

Level 10

209,547 points

Oct 11, 2012 10:12 AM in response to kbindera

I agree with the suggestion to reset the SMC and PRAM. Try that if you haven't already done it.

Reply

Answer 8

kbindera Author

Level 1

0 points

Oct 12, 2012 10:48 AM in response to Linc Davis

SMC and PRAM resets did not work for me. I appreciate all the suggestions.

One thing is that I pretty consistently see this message right at the time the machine hangs:

10/10/12 7:40:07.301 PM com.apple.time[10]: Requesting maintenance wake [Backup Interval]: <date: 0x7fd313e02b00> Wed Oct 10 19:41:05 2012 EDT (approx)

From reading this article:

http://www.macworld.com/article/1167970/up_close_with_mountain_lion_power_nap.ht ml

I learned that this message is something you might get during 'Power Nap'. This is a feature my mid-2010 laptop does not support on Mt. Lion. Maybe the machine is trying to use that feature regardless?

Another tidbit is that I had swapped out my machine's stock hard drive with a Mercury SSD. Maybe something is getting confused.

Anyway, just a thought. I'm going to try messing about with some of the power settings to see if I can work around this.

Any other suggestions are welcome.

Reply

Answer 9

Linc Davis

Level 10

209,547 points

Oct 12, 2012 1:09 PM in response to kbindera

I had swapped out my machine's stock hard drive with a Mercury SSD.

If that's when the problem started, I'd be inclined to put the blame there. You've ruled out all other likely possibilities. About the only other thing you could try is a clean reinstallation of OS X.

Reply

Answer 10

kbindera Author

Level 1

0 points

Oct 18, 2012 11:37 AM in response to Linc Davis

One last update here. To clarify, the problem did not conincide with the drive swap. I did that months back which still on Lion. I started to notice the problem after one of the Mountain Lion updates. I did a fresh install of Mountain Lion, BTW. It was either the second or third auto update when I started to see this.

Anyway, I tried changing some of the power settings, disabling:

-Put hard disks to sleep when possible

-Wake for network access

But this did not help.

I have also tried an OS reinstall. No go.

Oh well, living with this behavior for now.

Reply

Answer 11

Linc Davis

Level 10

209,547 points

Oct 18, 2012 1:03 PM in response to kbindera

It's been a while, but if I understand, you don't have the same problem in safe mode, though you do have a different problem. Is that correct?

Reply

Answer 12

kbindera Author

Level 1

0 points

Oct 29, 2012 6:39 AM in response to Linc Davis

SImilar problem in Safe Mode. It let me log in and see the desktop, but froze immediately.

One laset update...

I swapped out my SSD and put the standard drive back in and did a time machine restore of my entire config. The problem does not occur. And what's more, I don't see some of the messages in the system log that I saw when the SSD was in. The machine appears to just go to sleep properly. Here are the messages:

10/27/12 9:49:43.000 PM kernel[0]: PMStats: Hibernate write took 81010 ms

10/27/12 9:49:43.000 PM kernel[0]: all time: 81010 ms, comp bytes: 7598551040 time: 6997 ms 1035 Mb/s, crypt bytes: 3953257360 time: 5114 ms 737 Mb/s,

10/27/12 9:49:43.000 PM kernel[0]: image 4105980416, uncompressed 7598551040 (806539), compressed 4083975312 (53%), sum1 a7585094, sum2 cb72cf93

10/27/12 9:49:43.000 PM kernel[0]: wired_pages_encrypted 1119230, wired_pages_clear 91465, dirty_pages_encrypted 644420

10/27/12 9:49:43.000 PM kernel[0]: hibernate_write_image done(0)

10/27/12 9:49:43.000 PM kernel[0]: sleep

After that sleep message, no activity is logged, and I was able to come back to the computer on 10/29 and it woke up just fine. With the SSD installed, I never saw a sleep message like this.

So, may be an issue with the way my mid-2010 model and Mountain Lion handle my OWC Mercury SSD.

Again, thanks for all the assits here.

-Keith

Reply

Answer 13

Linc Davis

Level 10

209,547 points

Oct 29, 2012 8:19 AM in response to kbindera

OWC has a good reputation for supporting its products. Check for a firmware update for the SSD. If there isn't one, or if it doesn't solve the problem, you have a warranty claim.

Reply