tjdracz Posted November 25, 2014 Share Posted November 25, 2014 Hi! I'm running Yosemite 10.10.1 (recently updated from 10.10) and having quite severe issues with sleep and shutdown. Sometimes it seems that when computer tries to shutdown or sleep, it just freezes and cannot be waken up/or started again. Only way to get it back to live state is to forcefully turn it off with holding the power button. On shutdown I can see the message that CPU is to be halted but then I can still see the power LED light on and fan spinning inside. Curiously, it seems that it mostly happens after a prolonged use. If I turn laptop on and try to shut it down or sleep and wake only after 5 minutes or so, all is fine. If I have it working for a whole day at work, I can never seem to be able to reliably shut it down. Anyone have any ideas about that? I've seen other thread around here with similar problems but none of the solutions helped, there I think it was NVIDIA causing some weird behaviour. Attached is my config.plist - it's got Shutdown fix and other assorted stuff. Tried without it and behaviour is pretty much the same. Thanks Tom config.plist.zip Link to comment Share on other sites More sharing options...
sailor25462 Posted November 27, 2014 Share Posted November 27, 2014 Not sure if it may help here as well, but if you have an nvidia GPU try to use the web driver. As you mentioned correctly, there was an issue with reboots (although no freezes). Link to comment Share on other sites More sharing options...
bigben1 Posted November 28, 2014 Share Posted November 28, 2014 check your /s/l/e folder and if you have these kexts 1.applegraphicscontrol.kext 2.appletyMecddriver kext 3.appleupstreamuser client kext remove and rebuild cache. reboot Link to comment Share on other sites More sharing options...
tjdracz Posted December 2, 2014 Author Share Posted December 2, 2014 check your /s/l/e folder and if you have these kexts 1.applegraphicscontrol.kext 2.appletyMecddriver kext 3.appleupstreamuser client kext remove and rebuild cache. reboot AppleGraphicsControl.kext removal promptly killed my hackintosh. Restored it and working fine again. Will see how the things with the deletion of other two go Link to comment Share on other sites More sharing options...
tjdracz Posted December 10, 2014 Author Share Posted December 10, 2014 Okay, after deleting the other two kexts, the situation seemed to be better but it still having issues. Here's the log from shutdown: 10/12/2014 10:40:56.815 loginwindow[69]: Login Window point of no return 10/12/2014 10:40:56.822 Alfred[1125]: Alfred App is exiting, cleaning up... 10/12/2014 10:40:56.826 CoreServicesUIAgent[769]: unexpected message <OS_xpc_error: <error: 0x7fff79305c60> { count = 1, contents = "XPCErrorDescription" => <string: 0x7fff79305f70> { length = 18, contents = "Connection invalid" } }> 10/12/2014 10:40:56.827 Screenhero[1083]: AppSharingAppDelegate[applicationWillTerminate:] 10/12/2014 10:40:56.827 Screenhero[1083]: INFO: saving options... 10/12/2014 10:40:56.828 Screenhero[1083]: AnalyticsApi[recordBatchWithEvents:sync:] 10/12/2014 10:40:56.836 CoreServicesUIAgent[769]: unexpected message <OS_xpc_error: <error: 0x7fff79305c60> { count = 1, contents = "XPCErrorDescription" => <string: 0x7fff79305f70> { length = 18, contents = "Connection invalid" } }> 10/12/2014 10:40:56.859 sharingd[763]: 10:40:56.858 : SIGTERM received, shutting down. 10/12/2014 10:40:56.838 com.apple.xpc.launchd[1]: (com.apple.lateragent[1192]) Service exited due to signal: Killed: 9 10/12/2014 10:40:56.838 com.apple.xpc.launchd[1]: (com.apple.AirPlayUIAgent[779]) Service exited due to signal: Killed: 9 10/12/2014 10:40:56.852 com.apple.xpc.launchd[1]: (com.spotify.webhelper[1007]) Service exited due to signal: Terminated: 15 10/12/2014 10:40:56.852 com.apple.xpc.launchd[1]: (com.apple.iTunesHelper.49448[1062]) Service exited with abnormal code: 1 10/12/2014 10:40:56.853 com.apple.xpc.launchd[1]: (com.github.GitHub.Conduit[1004]) Service exited due to signal: Killed: 9 10/12/2014 10:40:56.861 com.apple.xpc.launchd[1]: (com.apple.EscrowSecurityAlert[1828]) Service exited due to signal: Killed: 9 10/12/2014 10:40:56.862 com.apple.xpc.launchd[1]: (com.apple.internetaccounts[786]) Service exited due to signal: Killed: 9 10/12/2014 10:40:56.970 com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.oneshot.0x1000000d.AppleSpell[1149]) Service exited due to signal: Killed: 9 10/12/2014 10:40:56.970 com.apple.xpc.launchd[1]: (com.apple.coreservices.uiagent[769]) Service exited due to signal: Killed: 9 10/12/2014 10:40:57.344 sessionlogoutd[4341]: sessionlogoutd Launched 10/12/2014 10:40:57.678 sessionlogoutd[4341]: DEAD_PROCESS: 69 console 10/12/2014 10:40:57.842 Screenhero[1083]: AnalyticsApiManager[analyticsRequestSuccessful:] 10/12/2014 10:40:57.842 Screenhero[1083]: INFO: saving options... 10/12/2014 10:40:58.239 com.apple.kextd[20]: Error reconsidering volume /Volumes/Untitled. 10/12/2014 10:40:58.240 shutdown[4342]: halt by Tom: 10/12/2014 10:40:58.000 kernel[0]: Kext loading now disabled. 10/12/2014 10:40:58.000 kernel[0]: Kext unloading now disabled. 10/12/2014 10:40:58.000 kernel[0]: Kext autounloading now disabled. 10/12/2014 10:40:58.000 kernel[0]: Kernel requests now disabled. 10/12/2014 10:40:58.240 shutdown[4342]: SHUTDOWN_TIME: 1418208058 240148 10/12/2014 10:40:58.000 kernel[0]: nspace-handler-set-snapshot-time: 0 10/12/2014 10:40:58.000 kernel[0]: unexpected session: 100000 uid: -1 10/12/2014 10:40:58.000 kernel[0]: nspace-handler-set-snapshot-time: 0 10/12/2014 10:40:58.241 com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.system) System reboot initiated by: shutdown.4342<-sessionlogoutd.4341<-launchd.1 10/12/2014 10:40:58.243 mtmfs[47]: filesystem unmount attempted from stopFS 10/12/2014 10:40:58.251 com.apple.mtmd[24]: Set snapshot time: reset (current time: 2014-12-10 10:40:58 +0000) Anyone have any clues? This issue is seriously driving me mad now Link to comment Share on other sites More sharing options...
aww Posted December 10, 2014 Share Posted December 10, 2014 10/12/2014 10:40:58.239 com.apple.kextd[20]: Error reconsidering volume /Volumes/Untitled. this should give you the clue. Assume, clover was installed in default, no change make to DSDT. (this is not cmos related) On shutdown, OS X try to flush HFS ,EXFAT AND MSDOS volumes. Partially initialized vol cause problem on flush. UTILITIES - > DISK UTILITY - > VERIFY OR FIX EACH PARTITION AND REBOOT. Link to comment Share on other sites More sharing options...
kvonlinee Posted December 10, 2014 Share Posted December 10, 2014 Fire up osx, log in and wait a second to idle, to shutdown enter to terminal. sudo shutdown -h now To reboot sudo shutdown -r now Link to comment Share on other sites More sharing options...
tjdracz Posted December 11, 2014 Author Share Posted December 11, 2014 10/12/2014 10:40:58.239 com.apple.kextd[20]: Error reconsidering volume /Volumes/Untitled. this should give you the clue. Assume, clover was installed in default, no change make to DSDT. (this is not cmos related) On shutdown, OS X try to flush HFS ,EXFAT AND MSDOS volumes. Partially initialized vol cause problem on flush. UTILITIES - > DISK UTILITY - > VERIFY OR FIX EACH PARTITION AND REBOOT. /Volumes/Untitled is my NTFS Windows partition. Any idea how to approach it then? Fire up osx, log in and wait a second to idle, to shutdown enter to terminal. sudo shutdown -h now To reboot sudo shutdown -r now Can do although it would make it boring to do that every time. Although I'm working in terminal all the time so... Link to comment Share on other sites More sharing options...
kvonlinee Posted December 11, 2014 Share Posted December 11, 2014 I done that once, after that i can use the shutdown button normal, i can't explain it. Link to comment Share on other sites More sharing options...
tjdracz Posted December 14, 2014 Author Share Posted December 14, 2014 Okay. So I've started to automatically unmount Windows volume on each boot and that got rid of the reconsidering volume error. Thought it was slightly better but still no dice. It's weird that I can reliably shutdown/sleep short time after boot but after prolonged use, it all hangs... Log from the last sleep that ended in computer still on: 14/12/2014 16:43:36.000 kernel[0]: Google Chrome He (map: 0xffffff802390e5a0) triggered DYLD shared region unnest for map: 0xffffff802390e5a0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:43:40.000 kernel[0]: Google Chrome He (map: 0xffffff8028116c30) triggered DYLD shared region unnest for map: 0xffffff8028116c30, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:43:44.000 kernel[0]: Google Chrome He (map: 0xffffff8028116870) triggered DYLD shared region unnest for map: 0xffffff8028116870, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:43:48.000 kernel[0]: Google Chrome He (map: 0xffffff80276015a0) triggered DYLD shared region unnest for map: 0xffffff80276015a0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:43:52.000 kernel[0]: Google Chrome He (map: 0xffffff8028116870) triggered DYLD shared region unnest for map: 0xffffff8028116870, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:43:56.000 kernel[0]: Google Chrome He (map: 0xffffff80276015a0) triggered DYLD shared region unnest for map: 0xffffff80276015a0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:43:59.000 kernel[0]: Google Chrome He (map: 0xffffff8028116c30) triggered DYLD shared region unnest for map: 0xffffff8028116c30, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:00.000 kernel[0]: Google Chrome He (map: 0xffffff80276015a0) triggered DYLD shared region unnest for map: 0xffffff80276015a0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:04.000 kernel[0]: Google Chrome He (map: 0xffffff8028116c30) triggered DYLD shared region unnest for map: 0xffffff8028116c30, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:08.000 kernel[0]: Google Chrome He (map: 0xffffff802390e4b0) triggered DYLD shared region unnest for map: 0xffffff802390e4b0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:12.000 kernel[0]: Google Chrome He (map: 0xffffff8028116c30) triggered DYLD shared region unnest for map: 0xffffff8028116c30, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:16.000 kernel[0]: Google Chrome He (map: 0xffffff8028116870) triggered DYLD shared region unnest for map: 0xffffff8028116870, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:20.000 kernel[0]: Google Chrome He (map: 0xffffff80276015a0) triggered DYLD shared region unnest for map: 0xffffff80276015a0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:24.000 kernel[0]: Google Chrome He (map: 0xffffff8028116870) triggered DYLD shared region unnest for map: 0xffffff8028116870, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:28.000 kernel[0]: Google Chrome He (map: 0xffffff802390e4b0) triggered DYLD shared region unnest for map: 0xffffff802390e4b0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:32.000 kernel[0]: Google Chrome He (map: 0xffffff8028116c30) triggered DYLD shared region unnest for map: 0xffffff8028116c30, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:36.000 kernel[0]: Google Chrome He (map: 0xffffff80276015a0) triggered DYLD shared region unnest for map: 0xffffff80276015a0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:40.000 kernel[0]: Google Chrome He (map: 0xffffff8028116870) triggered DYLD shared region unnest for map: 0xffffff8028116870, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:42.247 watchdogd[205]: [watchdog_daemon] @( pm_callback) - ref=0x0 msg_type=0xe0000270 msg=0x2b0006 14/12/2014 16:44:42.000 kernel[0]: PM response took 110 ms (183, VDCAssistant) 14/12/2014 16:44:42.000 kernel[0]: PM response took 158 ms (540, LaterAgent) 14/12/2014 16:44:42.000 kernel[0]: PM response took 185 ms (62, blued) 14/12/2014 16:44:42.000 kernel[0]: PM response took 201 ms (56, usbmuxd) 14/12/2014 16:44:42.000 kernel[0]: PM response took 299 ms (208, locationd) 14/12/2014 16:44:42.000 kernel[0]: PM response took 299 ms (49, awdd) 14/12/2014 16:44:44.000 kernel[0]: Google Chrome He (map: 0xffffff80276015a0) triggered DYLD shared region unnest for map: 0xffffff80276015a0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:48.000 kernel[0]: Google Chrome He (map: 0xffffff802390e4b0) triggered DYLD shared region unnest for map: 0xffffff802390e4b0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:52.000 kernel[0]: Google Chrome He (map: 0xffffff8028116c30) triggered DYLD shared region unnest for map: 0xffffff8028116c30, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:56.000 kernel[0]: Google Chrome He (map: 0xffffff8028116870) triggered DYLD shared region unnest for map: 0xffffff8028116870, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:44:59.000 kernel[0]: Google Chrome He (map: 0xffffff80276015a0) triggered DYLD shared region unnest for map: 0xffffff80276015a0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:45:00.000 kernel[0]: Google Chrome He (map: 0xffffff8028116870) triggered DYLD shared region unnest for map: 0xffffff8028116870, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:45:04.000 kernel[0]: Google Chrome He (map: 0xffffff80276015a0) triggered DYLD shared region unnest for map: 0xffffff80276015a0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:45:08.000 kernel[0]: Google Chrome He (map: 0xffffff802390e4b0) triggered DYLD shared region unnest for map: 0xffffff802390e4b0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:45:12.000 kernel[0]: PM notification timeout (pid 1605, Spotify) 14/12/2014 16:45:12.000 kernel[0]: PM notification timeout (pid 1616, Spotify Helper) 14/12/2014 16:45:12.000 kernel[0]: PM notification timeout (pid 1617, Spotify Helper) 14/12/2014 16:45:12.000 kernel[0]: PM notification timeout (pid 1618, Spotify Helper) 14/12/2014 16:45:12.000 kernel[0]: PM notification timeout (pid 1679, Spotify Helper) 14/12/2014 16:45:12.000 kernel[0]: PM notification timeout (pid 6467, Spotify Helper) 14/12/2014 16:45:12.000 kernel[0]: PM notification timeout (pid 9922, Spotify Helper) 14/12/2014 16:45:12.000 kernel[0]: PM notification timeout (pid 10518, Spotify Helper) 14/12/2014 16:45:12.247 Screenhero[372]: INFO: Computer will sleep 14/12/2014 16:45:12.247 Screenhero[372]: INFO: Disconnecting... 14/12/2014 16:45:12.247 Screenhero[372]: INFO: Logging out 14/12/2014 16:45:12.247 watchdogd[205]: [watchdog_daemon] @( pm_callback) - ref=0x0 msg_type=0xe0000280 msg=0x2c0005 14/12/2014 16:45:12.248 Screenhero[372]: Going to sleep! Bye! 14/12/2014 16:45:12.248 watchdogd[205]: [watchdog_daemon] @( wd_daemon_thread) - events buffer: 31r1148 19542s1148 14/12/2014 16:45:12.248 Screenhero[372]: DEBUG: OnLoginStateChange, loginState=3 14/12/2014 16:45:12.248 Screenhero[372]: SHWebView[jingleConnectionStateChanged:] 14/12/2014 16:45:12.249 Screenhero[372]: MasterSessionManager[stopSharingRequested:] 14/12/2014 16:45:12.249 Screenhero[372]: MasterSessionManager[stopAllSessions] 14/12/2014 16:45:12.260 Screenhero[372]: DEBUG: OnLoginStateChange, loginState=0 14/12/2014 16:45:12.260 Screenhero[372]: SHWebView[jingleConnectionStateChanged:] 14/12/2014 16:45:12.261 Screenhero[372]: FBConnection[connectionClosed] 14/12/2014 16:45:12.261 Screenhero[372]: FBConnection[dealloc] 14/12/2014 16:45:12.261 Screenhero[372]: Deallocing: <FBConnection: 0x600000101f80> 14/12/2014 16:45:12.261 Screenhero[372]: DEBUG: OnLoginStateChange, loginState=0 14/12/2014 16:45:12.261 Screenhero[372]: SHWebView[jingleConnectionStateChanged:] 14/12/2014 16:45:12.314 coreaudiod[246]: 2014-12-14 04:45:12.248404 PM [AirPlay] Power: SystemWillSleep 14/12/2014 16:45:12.314 coreaudiod[246]: 2014-12-14 04:45:12.313837 PM [AirPlay] BTLE client stopping to browse for AirPlay Solo Target Presence. 14/12/2014 16:45:12.315 coreaudiod[246]: 2014-12-14 04:45:12.315119 PM [AirPlay] BTLE discovery removing all devices 14/12/2014 16:45:12.000 kernel[0]: PM response took 132 ms (304, identityservices) 14/12/2014 16:45:12.000 kernel[0]: Google Chrome He (map: 0xffffff8028116c30) triggered DYLD shared region unnest for map: 0xffffff8028116c30, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:45:12.000 kernel[0]: PM response took 231 ms (208, locationd) 14/12/2014 16:45:12.000 kernel[0]: PM response took 342 ms (251, UserEventAgent) 14/12/2014 16:45:12.000 kernel[0]: PM response took 421 ms (62, blued) 14/12/2014 16:45:12.710 coreaudiod[246]: 2014-12-14 04:45:12.709482 PM [AirPlay] BTLE client stopped to browse for AirPlay Solo Target Presence. 14/12/2014 16:45:16.000 kernel[0]: Google Chrome He (map: 0xffffff8028116870) triggered DYLD shared region unnest for map: 0xffffff8028116870, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:45:20.000 kernel[0]: Google Chrome He (map: 0xffffff80276015a0) triggered DYLD shared region unnest for map: 0xffffff80276015a0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:45:24.000 kernel[0]: Google Chrome He (map: 0xffffff8028116870) triggered DYLD shared region unnest for map: 0xffffff8028116870, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:45:28.000 kernel[0]: Google Chrome He (map: 0xffffff802390e4b0) triggered DYLD shared region unnest for map: 0xffffff802390e4b0, region 0x7fff96e00000->0x7fff97000000. While not abnormal for debuggers, this increases system memory footprint until the target exits. 14/12/2014 16:45:30.000 kernel[0]: PM response took 3143 ms (28, powerd) 14/12/2014 16:45:30.000 kernel[0]: AirPort_Brcm43xx::powerChange: System Sleep 14/12/2014 16:45:30.000 kernel[0]: [0x32484d000, 0x40000000] 14/12/2014 16:45:30.000 kernel[0]: [0x36484d000, 0x40000000] 14/12/2014 16:45:30.000 kernel[0]: [0x3a484d000, 0x40000000] 14/12/2014 16:45:30.000 kernel[0]: [0x0, 0x0] Really can't see much here. This is driving me nuts now... Link to comment Share on other sites More sharing options...
aikidoka25 Posted April 13, 2015 Share Posted April 13, 2015 I had an almost similar issue, the unit cannot shutdown after waking up from sleep. The screen turned off after the "halt" message, but the unit still powered up. The problem solved after I changed the nvidia kexts to Apple supplied ones. Link to comment Share on other sites More sharing options...
Recommended Posts