Mac Pro 2009 won't wake from sleep after El Capitan

Question

Level 1

0 points

Mac Pro 2009 won't wake from sleep after El Capitan

HI All,

I just upgraded my early 2009 Mac Pro from latest Yosemite 10.10, to official ElCapitan 10.11. Now when the Mac Pro goes to sleep, the fan kicks into high and the computer becomes unresponsive. My single screen does turn off properly. Neither my apple Bluetooth keyboard nor Logitech MX mouse will wake the system. I have to hold down the power button to get the system back running. This happens whether I manually put it to sleep or let the OS do it after the set time. Sleep worked fine on 10.10 prior to the upgrade. I do have two external drives which use usb. I switched them to FireWire and I still have the problem. I have to fully shutdown the computer all the time now. Has anyone else experienced this? Any ideas? Help is appreciated.

- J

Mac Pro, OS X El Capitan (10.11)

Posted on Oct 5, 2015 9:47 PM

Reply

Answer 1

lllaass

Level 10

210,411 points

Oct 6, 2015 1:06 AM in response to jayhova1

If your Mac doesn't sleep or wake when expected - Apple Support

Note the time of the next freeze. After rebooting open the Console app in Finder>Applications>Utilities and look for log entries at the time of the freeze. Post suspicious ones here.

Do you have any PCle cards besides the graphics card? If so what card(s)?

Reply

Answer 2

jayhova1 Author

Level 1

0 points

Oct 6, 2015 6:14 AM in response to lllaass

Hi, no extra PCIe cards at all. Logs below from just before sleep, to freeze, to next reboot at 9am.

10/6/15 8:31:40.040 AM	coreduetd[76]	LaunchServices: disconnect event received for service com.apple.lsd.modifydb
10/6/15 8:31:48.253 AM	com.apple.xpc.launchd[1]	(com.apple.mdworker.single.08000000-0000-0000-0000-000000000000) Service only ran for 8 seconds. Pushing respawn out by 2 seconds.
10/6/15 8:31:58.420 AM	Console[763]	Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
10/6/15 8:32:33.000 AM	kernel[0]	process xrdd[90] caught causing excessive wakeups. EXC_RESOURCE supressed due to audio playback
10/6/15 8:32:45.073 AM	mds[68]	(Volume.Normal:2464) volume:0x7fa2ea869e00 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/firmwaresyncd.kpYI9L
10/6/15 8:32:45.868 AM	deleted[612]	normalizeUserMountpoint:738 volRoot failed for /Volumes/firmwaresyncd.kpYI9L
10/6/15 8:32:58.288 AM	ntpd[274]	time set +0.213990 s
10/6/15 8:33:02.473 AM	com.apple.SecurityServer[86]	Session 100005 created
10/6/15 8:33:03.330 AM	mdworker[773]	SecStaticCode: verification failed (trust result 5, error -2147409622)
10/6/15 8:33:03.330 AM	mdworker[772]	SecStaticCode: verification failed (trust result 5, error -2147409622)
10/6/15 8:33:11.672 AM	AirPlayUIAgent[523]	2015-10-06 08:33:11.671951 AM [AirPlayUIAgent] BecomingInactive: NSWorkspaceWillSleepNotification
10/6/15 8:33:11.679 AM	diagnostics_agent[529]	AutoSubmitPreference is 0
10/6/15 8:33:11.805 AM	identityservicesd[475]	<IMMacNotificationCenterManager: 0x7fa48072e3a0>: notification observer: com.apple.iChat notification: __CFNotification 0x7fa48042c430 {name = _NSDoNotDisturbEnabledNotification}
10/6/15 8:33:11.806 AM	imagent[482]	<IMMacNotificationCenterManager: 0x7f9933202d60>: notification observer: com.apple.FaceTime notification: __CFNotification 0x7f993311aae0 {name = _NSDoNotDisturbEnabledNotification}
10/6/15 8:33:11.818 AM	identityservicesd[475]	<IMMacNotificationCenterManager: 0x7fa48072e3a0>: NC Disabled: NO
10/6/15 8:33:11.831 AM	identityservicesd[475]	<IMMacNotificationCenterManager: 0x7fa48072e3a0>: DND Enabled: YES
10/6/15 8:33:11.831 AM	identityservicesd[475]	<IMMacNotificationCenterManager: 0x7fa48072e3a0>: Updating enabled: NO (Topics: (

))

10/6/15 8:33:11.831 AM	imagent[482]	<IMMacNotificationCenterManager: 0x7f9933202d60>: NC Disabled: NO
10/6/15 8:33:11.886 AM	imagent[482]	<IMMacNotificationCenterManager: 0x7f9933202d60>: DND Enabled: YES
10/6/15 8:33:11.886 AM	imagent[482]	<IMMacNotificationCenterManager: 0x7f9933202d60>: Updating enabled: NO (Topics: (

))

10/6/15 8:33:11.000 AM	kernel[0]	PM response took 301 ms (553, ChronoSync Sched)
10/6/15 8:33:12.099 AM	WindowServer[234]	device_generate_desktop_screenshot: authw 0x7f858c81dc00(2000), shield 0x7f858f074200(2001)
10/6/15 8:33:12.099 AM	WindowServer[234]	device_generate_lock_screen_screenshot: authw 0x7f858c81dc00(2000)[0, 0, 0, 0] shield 0x7f858f074200(2001), dev [1920,1200]
10/6/15 8:33:12.099 AM	WindowServer[234]	no sleep images for WillPowerOffWithImages
10/6/15 8:33:12.000 AM	kernel[0]	PM response took 435 ms (100, loginwindow)
10/6/15 8:33:12.166 AM	Wireless-AC Network Utility[600]	RtCheckForHang::bGoingToSleep
10/6/15 8:33:21.651 AM	loginwindow[100]	CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
10/6/15 8:33:26.693 AM	powerd[58]	BUG in libdispatch: 15A284 - 1631 - 0x0
10/6/15 8:33:26.000 AM	kernel[0]	IOCTL not recognized: 234 out of 235
10/6/15 8:33:31.000 AM	kernel[0]	PM response took 5132 ms (58, powerd)
10/6/15 8:33:31.000 AM	kernel[0]	AirPort_Brcm43xx::powerChange: System Sleep
10/6/15 9:00:39.000 AM	bootlog[0]	BOOT_TIME 1444136439 0
10/6/15 9:01:09.000 AM	syslogd[48]	Configuration Notice:

ASL Module "com.apple.AccountPolicyHelper" claims selected messages.

Those messages may not appear in standard system log files or in the ASL database.

Reply

Answer 3

Linc Davis

Level 10

209,547 points

Oct 13, 2015 9:25 PM in response to jayhova1

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 the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem.

Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

The login screen appears even if you usually login 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, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Reply

Answer 4

jayhova1 Author

Level 1

0 points

Oct 13, 2015 9:28 PM in response to Linc Davis

Thanks for the troubleshooting tips! I was able to narrow it down to an Edimax AC-1200 (EW-7822UAC) USB wireless adapter. Once I unplugged it everything went to sleep and woke properly. Hopefully this helps anyone else that might be using this adapter. I'm guessing it's because they don't have an official driver for El Capitan yet and don't officially support it. Thanks again!

Reply