Gigabyte GA-Z77X-UP5 TH -- Won't stay asleep with ML 10.8.3

[Pr3fix]

Hello,

I have an annoying issue, where if I manually tell my ML to go to sleep (such as by hitting the power button), it will fall asleep for about 5-10 seconds, and then wake up again at the login screen.

I have no idea what I can do to fix this... Any help is much appreciated! I've tried some of the suggestions on the first few pages of the stickied sleep post, however they didn't seem to help.

Any help is MUCH appreciated!!

EDIT: I believe this is the system log from when I hit the sleep button, up until the system wakesup.

9/1/13 11:37:10.481 AM PleaseSleep[544]: Sleep notification received from the system
9/1/13 11:37:10.503 AM WindowServer[114]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
9/1/13 11:37:10.504 AM loginwindow[83]: find_shared_window: WID -1
9/1/13 11:37:10.504 AM loginwindow[83]: CGSGetWindowTags: Invalid window 0xffffffff
9/1/13 11:37:10.504 AM loginwindow[83]: find_shared_window: WID -1
9/1/13 11:37:10.504 AM loginwindow[83]: CGSSetWindowTags: Invalid window 0xffffffff
9/1/13 11:37:10.670 AM WindowServer[114]: Created shield window 0x150 for display 0x2b282e11
9/1/13 11:37:10.673 AM WindowServer[114]: Created shield window 0x151 for display 0x2b282050
9/1/13 11:37:10.675 AM WindowServer[114]: Created shield window 0x152 for display 0x2b284d4e
9/1/13 11:37:10.675 AM WindowServer[114]: device_generate_desktop_screenshot: authw 0x7fb2b3c06140(2000), shield 0x7fb2b2629f50(2001)
9/1/13 11:37:10.895 AM WindowServer[114]: device_generate_desktop_screenshot: authw 0x7fb2b3c06140(2000), shield 0x7fb2b2629f50(2001)
9/1/13 11:37:10.915 AM WindowServer[114]: device_generate_lock_screen_screenshot: authw 0x7fb2b3c06140(2000), shield 0x7fb2b2629f50(2001)
9/1/13 11:37:10.925 AM WindowServer[114]: device_generate_desktop_screenshot: authw 0x7fb2b3c06140(2000), shield 0x7fb2b2629f50(2001)
9/1/13 11:37:11.461 AM mdworker[805]: Unable to talk to lsboxd
9/1/13 11:37:12.976 AM configd[17]: network changed: v4(en0-:192.168.0.104) DNS- Proxy- SMB
9/1/13 11:37:36.002 AM loginwindow[83]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check
9/1/13 11:37:36.000 AM kernel[0]: Wake reason: ?
9/1/13 11:37:36.000 AM kernel[0]: RTC: PowerByCalendarDate setting ignored
9/1/13 11:37:36.000 AM kernel[0]: Previous Sleep Cause: 5
9/1/13 11:37:36.313 AM WindowServer[114]: handle_will_sleep_auth_and_shield_windows: no lock state data
9/1/13 11:37:36.313 AM WindowServer[114]: handle_will_sleep_auth_and_shield_windows: no lock state data
9/1/13 11:37:36.315 AM WindowServer[114]: handle_will_sleep_auth_and_shield_windows: no lock state data
9/1/13 11:37:36.404 AM WindowServer[114]: Created shield window 0x153 for display 0x003f003f
9/1/13 11:37:36.404 AM WindowServer[114]: handle_will_sleep_auth_and_shield_windows: no lock state data
9/1/13 11:37:36.435 AM loginwindow[83]: resume called when there was already a timer

 

[beelzebozo]

Hello,

I have an annoying issue, where if I manually tell my ML to go to sleep (such as by hitting the power button), it will fall asleep for about 5-10 seconds, and then wake up again at the login screen.

I have no idea what I can do to fix this... Any help is much appreciated! I've tried some of the suggestions on the first few pages of the stickied sleep post, however they didn't seem to help.

Any help is MUCH appreciated!!

EDIT: I believe this is the system log from when I hit the sleep button, up until the system wakesup.

9/1/13 11:37:10.481 AM PleaseSleep[544]: Sleep notification received from the system
9/1/13 11:37:10.503 AM WindowServer[114]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
9/1/13 11:37:10.504 AM loginwindow[83]: find_shared_window: WID -1
9/1/13 11:37:10.504 AM loginwindow[83]: CGSGetWindowTags: Invalid window 0xffffffff
9/1/13 11:37:10.504 AM loginwindow[83]: find_shared_window: WID -1
9/1/13 11:37:10.504 AM loginwindow[83]: CGSSetWindowTags: Invalid window 0xffffffff
9/1/13 11:37:10.670 AM WindowServer[114]: Created shield window 0x150 for display 0x2b282e11
9/1/13 11:37:10.673 AM WindowServer[114]: Created shield window 0x151 for display 0x2b282050
9/1/13 11:37:10.675 AM WindowServer[114]: Created shield window 0x152 for display 0x2b284d4e
9/1/13 11:37:10.675 AM WindowServer[114]: device_generate_desktop_screenshot: authw 0x7fb2b3c06140(2000), shield 0x7fb2b2629f50(2001)
9/1/13 11:37:10.895 AM WindowServer[114]: device_generate_desktop_screenshot: authw 0x7fb2b3c06140(2000), shield 0x7fb2b2629f50(2001)
9/1/13 11:37:10.915 AM WindowServer[114]: device_generate_lock_screen_screenshot: authw 0x7fb2b3c06140(2000), shield 0x7fb2b2629f50(2001)
9/1/13 11:37:10.925 AM WindowServer[114]: device_generate_desktop_screenshot: authw 0x7fb2b3c06140(2000), shield 0x7fb2b2629f50(2001)
9/1/13 11:37:11.461 AM mdworker[805]: Unable to talk to lsboxd
9/1/13 11:37:12.976 AM configd[17]: network changed: v4(en0-:192.168.0.104) DNS- Proxy- SMB
9/1/13 11:37:36.002 AM loginwindow[83]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check
9/1/13 11:37:36.000 AM kernel[0]: Wake reason: ?
9/1/13 11:37:36.000 AM kernel[0]: RTC: PowerByCalendarDate setting ignored
9/1/13 11:37:36.000 AM kernel[0]: Previous Sleep Cause: 5
9/1/13 11:37:36.313 AM WindowServer[114]: handle_will_sleep_auth_and_shield_windows: no lock state data
9/1/13 11:37:36.313 AM WindowServer[114]: handle_will_sleep_auth_and_shield_windows: no lock state data
9/1/13 11:37:36.315 AM WindowServer[114]: handle_will_sleep_auth_and_shield_windows: no lock state data
9/1/13 11:37:36.404 AM WindowServer[114]: Created shield window 0x153 for display 0x003f003f
9/1/13 11:37:36.404 AM WindowServer[114]: handle_will_sleep_auth_and_shield_windows: no lock state data
9/1/13 11:37:36.435 AM loginwindow[83]: resume called when there was already a timer

Disable Internal CPU PLL Overvoltage in BIOS and remove darkwake=0 from org.chameleon.boot.plist.

 

[Pr3fix]

Disable Internal CPU PLL Overvoltage in BIOS and remove darkwake=0 from org.chameleon.boot.plist.

Thanks for the reply -- I did both of those things (my darkwake was actually set to 8, not 0 but I removed it entirely). I also changed CPU PLL Overvoltage in BIOS from auto to disabled.

Didn't help with the sleep issue -- the computer will go to sleep for a few seconds and then roar back to life.

Please help!

 

[Pr3fix]

Any other ideas as to what's waking this up? I'm starting to suspect it has something to do with ECH1, USB controller? Here is my wake log:

Thomass-Mac-Pro:~ Tom$ syslog |grep -i "Wake reason"
Sep 6 00:20:42 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 6 00:42:13 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 6 16:55:28 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 6 17:17:41 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 6 17:39:53 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 6 18:01:20 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 6 18:23:33 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 6 18:45:55 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 7 16:58:18 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 7 17:20:36 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 7 17:42:54 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 7 18:05:02 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 7 18:27:13 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 7 18:49:26 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 10 09:51:17 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 10 14:33:29 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 10 14:55:00 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 10 15:16:31 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 10 15:38:14 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 10 18:16:39 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 11 10:08:03 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 11 11:28:37 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 11 11:35:23 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 11 11:49:37 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: ?
Sep 11 11:54:24 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: EHC1
Sep 11 11:55:32 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: EHC1
Sep 11 12:14:33 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: EHC1
Sep 11 12:31:41 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: EHC1
Sep 11 15:44:01 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: EHC1
Sep 11 17:03:45 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: EHC1
Sep 11 17:13:29 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: PWRB EHC1 (User)
Sep 12 17:22:31 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: PWRB EHC1 (User)
Sep 12 18:04:36 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: EHC1
Sep 12 18:11:10 Thomass-Mac-Pro kernel[0] <Debug>: Wake reason: EHC1
Thomass-Mac-Pro:~ Tom$

 

[Pr3fix]

reading on the forums, others with this board have this issue too.


One suggestion was to delete AppleIntelCPUPowerManagement.kext and GenericUSBXHCI.kext, and set darkwake=0

I did the above but it did not fix my problem (sleeps->wakes up after 2 seconds).

I also tried installing the null AppleIntelCPUPowerManagement.kext from multibeast but it did not help. sudo pmset -a hibernatemode 2 did not help either.

Really could use some help with this issue.. please!!

 

[bthall]

reading on the forums, others with this board have this issue too.


One suggestion was to delete AppleIntelCPUPowerManagement.kext and GenericUSBXHCI.kext, and set darkwake=0

I did the above but it did not fix my problem (sleeps->wakes up after 2 seconds).

I also tried installing the null AppleIntelCPUPowerManagement.kext from multibeast but it did not help. sudo pmset -a hibernatemode 2 did not help either.

Really could use some help with this issue.. please!!

Make sure 'Wake on LAN' is not enabled in your BIOS/UEFI.

-bth

 

[Fokke]

Maybe this helps:
Sound this on BoomR's build:

http://www.tonymacx86.com/golden-bu...core-i7-3770k-ga-z77x-up5-th-32gb-hd4000.html


This new menu option seems to have appeared starting in F10 or for sure F11 version of the UEFI/BIOS. By default, Wake From Thunderbolt Devices = Enabled. I know we don't have hot-swap abilities yetfor Thunderbolt, so when I first got my build up & running, I knew to make sure my TB devices were connected before I powered the machine on. But for me, it didn't matter which TB device I tried to connect (Apple TB > Ethernet Adapter, Apple TB > FW800 Adapter, or my Seagate GoFlex drive withThunderbolt Adapter), within 3-4 seconds of the desktop rendering, my entire system would lock up.

What seemed to be happening was that upon initial system power-up, the TB devices would receive power, but then go to sleep during boot. Once the desktop would render, the TB devices would then power back up again...and BAMM-O: my system would lock up. When poking around the UEFI and finally taking a moment to ponder this Thunderbolt setting, I got to thinking: People report their systems locking up when trying to hot-swap their TB devices. Maybe my TB devices were "off" during boot, then powering back on (in essence, a "hot swap connection") once bootup was complete. Long story short: with my build, setting Wake From Thunderbolt Devices = Disabled fixed this issue! Now all my TB devices work just fine:

 

[Pr3fix]

Make sure 'Wake on LAN' is not enabled in your BIOS/UEFI.

-bth

WOL is disabled.

Maybe this helps:
Sound this on BoomR's build:

http://www.tonymacx86.com/golden-bu...core-i7-3770k-ga-z77x-up5-th-32gb-hd4000.html


This new menu option seems to have appeared starting in F10 or for sure F11 version of the UEFI/BIOS. By default, Wake From Thunderbolt Devices = Enabled. I know we don't have hot-swap abilities yetfor Thunderbolt, so when I first got my build up & running, I knew to make sure my TB devices were connected before I powered the machine on. But for me, it didn't matter which TB device I tried to connect (Apple TB > Ethernet Adapter, Apple TB > FW800 Adapter, or my Seagate GoFlex drive withThunderbolt Adapter), within 3-4 seconds of the desktop rendering, my entire system would lock up.

What seemed to be happening was that upon initial system power-up, the TB devices would receive power, but then go to sleep during boot. Once the desktop would render, the TB devices would then power back up again...and BAMM-O: my system would lock up. When poking around the UEFI and finally taking a moment to ponder this Thunderbolt setting, I got to thinking: People report their systems locking up when trying to hot-swap their TB devices. Maybe my TB devices were "off" during boot, then powering back on (in essence, a "hot swap connection") once bootup was complete. Long story short: with my build, setting Wake From Thunderbolt Devices = Disabled fixed this issue! Now all my TB devices work just fine:

Thank you for the tip, I will try it out however I do not have any thunderbolt devices so I don't think they would be waking it up... will give it a shot anyway.

EDIT:: wake on TB devices was already disabled in my BIOS so that is not the solution, unfortunately.


EDIT 2:: I also do not have a system definition installed, I didn't select any in multibeast.... would this be an issue? I am using an AMD7000 GPU so I wasnt sure if system definition would mess it up or not.

 

[Pr3fix]

Despite the fact that ECH1 represents the USB 2 controller I am beginning to suspect the USB3 kext is at fault -- I accidentally installed the USB3 generic kext from multibeast when I first configured this build.


How do I remove the multibeast generic USB3 kext? What files do I need to remove? I have already deleted GenericUSBXHCI.kext but it didnt seem to change anything.



Any idea how to fix wake reason: ECH1?

 

[Fokke]

You have to rebuild cache and repair permissions after that. I use kext wizard for that.
Try installing the latest GenericUSBXHCI_1.2.6d2 as USB3 driver. It works here at my UP4.