Contribute
Register

Sierra / Hibernate / reboot

Joined
Feb 3, 2017
Messages
54
Motherboard
Gigabyte GA-Z170N-Gaming 5 (Clover UEFI)
CPU
Intel Core i7-7700k
Graphics
Gigabyte GeForce GTX970 4GB
Mac
MacBook Air, MacBook Pro
Mobile Phone
iOS
Hi All,

I'm running a new install of Sierra 10.12.3 on a Gigabyte GA-Z170N-wifi board.

Initially the system would sleep and wake fine (including PowerNap, seen using pmset -g stats), but now in the morning I am greeted by the Clover boot screen unfortunately.

I have hibernate disabled as recommended (I read this is the default, set by MultiBeast install ?):

Code:
hackintosh01:~ bradtaylor$ pmset -g
System-wide power settings:
Currently in use:
 standby              1
 Sleep On Power Button 1
 womp                 1
 autorestart          0
 hibernatefile        /var/vm/sleepimage
 powernap             1
 networkoversleep     0
 disksleep            10
 sleep                1
 autopoweroffdelay    28800
 hibernatemode        0
 autopoweroff         1
 ttyskeepawake        1
 displaysleep         10
 standbydelay         10800
What surprises me though is when i look through the power log, the last event (before I reboot) occurs at time x. At time x, the hibernate file is also touched.

For today, that occurred ~ 02:42:

Code:
2017-03-09 02:41:37 -0800 Assertions              PID 49(powerd) TimedOut BackgroundTask "Powerd - Wait for client BackgroundTask assertions" 00:00:10  id:0x0xb000083b0 [System: PushSrvc BGTask SRPrevSleep kCPU]          

2017-03-09 02:41:37 -0800 Assertions              PID 49(powerd) TimedOut ApplePushServiceTask "Powerd - Wait for client pushService assertions" 00:00:10  id:0x0xa000083b1 [System: PushSrvc SRPrevSleep kCPU]          

2017-03-09 02:41:37 -0800 com.apple.sleepservices.sessionTerminated    SleepService: window has terminated.                                                   

2017-03-09 02:42:12 -0800 Assertions              PID 49(powerd) TimedOut InternalPreventSleep "com.apple.powermanagement.acwakelinger" 00:00:45  id:0x0xd000083b2 [System: SRPrevSleep kCPU]          

2017-03-09 02:42:12 -0800 Assertions              Summary- [System: No Assertions] Using AC          

2017-03-09 02:42:12 -0800 Sleep                   Entering Sleep state due to 'Maintenance Sleep': Using AC           

2017-03-09 02:42:15 -0800 Wake Requests           [*proc=mDNSResponder request=Maintenance inDelta=6477] [proc=UserEventAgent request=SleepService inDelta=35997 info="AppRefresh:com.apple.apsd.apprefresh,"] [proc=UserEventAgent request=TimerPlugin inDelta=47248 info="BGTask:com.apple.suggestions.harvest,"]           

2017-03-09 02:42:15 -0800 PM Client Acks          Delays to Sleep notifications: [com.apple.apsd is slow(2935 ms)]           

Sleep/Wakes since boot at 2017-03-08 21:49:32 -0800 :3   Dark Wake Count in this sleep cycle:3


Time stamp                Domain                  Message                                                                        Duration      Delay     

==========                ======                  =======                                                                        ========      =====     

UUID: (null)

2017-03-09 09:16:17 -0800 Start                   powerd process is started                                                              

2017-03-09 09:16:17 -0800 Assertions              Summary- [System: No Assertions] Using AC          

2017-03-09 09:16:17 -0800 HibernateStats          hibmode=0 standbydelay=0                                                                 0           

Sleep/Wakes since boot at 2017-03-09 09:16:17 -0800 :0   Dark Wake Count in this sleep cycle:3
And the sleep image file:
Code:
hackintosh01:~ bradtaylor$ ls -lah /var/vm
total 4194304
drwxr-xr-x   3 root  wheel   102B  9 Mar 09:16 .
drwxr-xr-x  25 root  wheel   850B  7 Mar 08:15 ..
-rw------T   1 root  wheel   2.0G  9 Mar 02:42 sleepimage
The only other "interesting" thing i've found is that pmset -g everything will cause a spontaneous reboot.

Anyone have any ideas about this?

thanks... Brad
 
Joined
Feb 3, 2017
Messages
54
Motherboard
Gigabyte GA-Z170N-Gaming 5 (Clover UEFI)
CPU
Intel Core i7-7700k
Graphics
Gigabyte GeForce GTX970 4GB
Mac
MacBook Air, MacBook Pro
Mobile Phone
iOS
RTFM update... :banghead:

Interestingly enough, the default power configuration I started with after MultiBeast 9.0.1 only sets hibernatemode to 0 and leaves standby and autopoweroff set to 1.... My hypothesis is that the kernel is timing out after 10800 s (standbydelay) and then writing to the hibernatefile and kaboom.

I will report back after I disable all three settings and go through another 24hr cycle.

Any comments from pmset experts appreciated.

cheers... Brad

man pmset

SAFE SLEEP ARGUMENTS
hibernatemode supports values of 0, 3, or 25. Whether or not a hibernation image gets written is also dependent on the values of standby and autopoweroff

For example, on desktops that support standby a hibernation image will be written after the specified standbydelay time. To disable hibernation images completely, ensure hibernatemode standby and autopoweroff are all set to 0.

hibernatemode = 0 by default on desktops. The system will not back memory up to persistent storage. The system must wake from the contents of memory; the system will lose context on power loss. This is, historically, plain old sleep.

hibernatemode = 3 by default on portables. The system will store a copy of memory to persistent storage (the disk), and will power memory during sleep. The system will wake from memory, unless a power loss forces it to restore from hibernate image.

hibernatemode = 25 is only settable via pmset. The system will store a copy of memory to persistent storage (the disk), and will remove power to memory. The system will restore from disk image. If you want "hibernation" - slower sleeps, slower wakes, and better battery life, you should use this setting.

Please note that hibernatefile may only point to a file located on the root volume.

STANDBY ARGUMENTS
standby causes kernel power management to automatically hibernate a machine after it has slept for a specified time period. This saves power while asleep. This setting defaults to ON for supported hardware. The setting standby will be visible in pmset -g if the feature is supported on this machine.

standbydelay specifies the delay, in seconds, before writing the hibernation image to disk and powering off memory for Standby.

autopoweroff is enabled by default on supported platforms as an implementation of Lot 6 to the European Energy-related Products Directive. After sleeping for <autopoweroffdelay> seconds, the system will write a hibernation image and go into a lower power chipset sleep. Wakeups from this state will take longer than wakeups from regular sleep.

autopoweroffdelay specifies the delay, in seconds, before entering autopoweroff mode.
 
Joined
Mar 23, 2016
Messages
3
Motherboard
z68xp
CPU
27ook
Graphics
ati 6880 hd
Mac
Classic Mac
Mobile Phone
I have same problem to yours,do you find out how to solve it.Thank you
 
Joined
Feb 3, 2017
Messages
54
Motherboard
Gigabyte GA-Z170N-Gaming 5 (Clover UEFI)
CPU
Intel Core i7-7700k
Graphics
Gigabyte GeForce GTX970 4GB
Mac
MacBook Air, MacBook Pro
Mobile Phone
iOS
Joined
Jun 18, 2010
Messages
81
Motherboard
z170x ud3 ultra + clover
CPU
6700k + z170
Graphics
1080 gtx 2560 x 1440 x2
Mac
iMac, MacBook Pro, Mac mini, Mac Pro
Classic Mac
128K, 512K, Classic, Lisa, Plus, Power Mac, PowerBook, Quadra
Mobile Phone
iOS
I have A similar problem. Crash after some number of dark wake cycles. I have darkewake set to 8 and these setting for power mgmgt.

Code:
System-wide power settings:
Currently in use:
standby              0
Sleep On Power Button 1
womp                 0
autorestart          0
hibernatefile        /dev/null
powernap             1
networkoversleep     0
disksleep            0
sleep                15
autopoweroffdelay    28800
hibernatemode        0
autopoweroff         0
ttyskeepawake        1
displaysleep         15
standbydelay         84000
Code:
Sun May 21 05:51:07 on console
$ pmset -g log | grep -i failure
2017-05-15 21:51:38 -0700 Failure                 Drivers Failure during wake due to PEG0():                                              
2017-05-16 18:28:48 -0700 Failure                 Drivers Failure during wake due to PEG0():                                              
2017-05-17 18:31:55 -0700 Failure                 Drivers Failure during wake due to PEG0():                                              
2017-05-19 01:24:38 -0700 Failure                 Drivers Failure during wake due to PEG0():                                              
2017-05-20 12:42:48 -0700 Failure                 Drivers Failure during wake due to PEG0():
I get the dreaded Drivers failure msg, common on AMD but I'm running a geforce 1080. Sleeps for hours and wakes without problems but longer sleep always causes a reboot. 10.12.5.

I tried disabling hibernate in clover but that setting only seems to effect whether clover tries to resume from hibernate. I'll try different modes for dark wake next. Tough to debug because it takes so long test.


Any ideas?
 
Joined
Feb 3, 2017
Messages
54
Motherboard
Gigabyte GA-Z170N-Gaming 5 (Clover UEFI)
CPU
Intel Core i7-7700k
Graphics
Gigabyte GeForce GTX970 4GB
Mac
MacBook Air, MacBook Pro
Mobile Phone
iOS
I have A similar problem. Crash after some number of dark wake cycles. I have darkewake set to 8 and these setting for power mgmgt.

Code:
System-wide power settings:
Currently in use:
standby              0
Sleep On Power Button 1
womp                 0
autorestart          0
hibernatefile        /dev/null
powernap             1
networkoversleep     0
disksleep            0
sleep                15
autopoweroffdelay    28800
hibernatemode        0
autopoweroff         0
ttyskeepawake        1
displaysleep         15
standbydelay         84000
Code:
Sun May 21 05:51:07 on console
$ pmset -g log | grep -i failure
2017-05-15 21:51:38 -0700 Failure                 Drivers Failure during wake due to PEG0():                                             
2017-05-16 18:28:48 -0700 Failure                 Drivers Failure during wake due to PEG0():                                             
2017-05-17 18:31:55 -0700 Failure                 Drivers Failure during wake due to PEG0():                                             
2017-05-19 01:24:38 -0700 Failure                 Drivers Failure during wake due to PEG0():                                             
2017-05-20 12:42:48 -0700 Failure                 Drivers Failure during wake due to PEG0():
I get the dreaded Drivers failure msg, common on AMD but I'm running a geforce 1080. Sleeps for hours and wakes without problems but longer sleep always causes a reboot. 10.12.5.

I tried disabling hibernate in clover but that setting only seems to effect whether clover tries to resume from hibernate. I'll try different modes for dark wake next. Tough to debug because it takes so long test.


Any ideas?
Is the PEG0() device the geforce 1080? I think that if that is the case, you are at the mercy of the card and the drivers for the card to resume from sleep correctly.

There seems to have been quite a few updates for the nvidia drivers lately - did updating help?

cheers... Brad
 
Joined
Jun 18, 2010
Messages
81
Motherboard
z170x ud3 ultra + clover
CPU
6700k + z170
Graphics
1080 gtx 2560 x 1440 x2
Mac
iMac, MacBook Pro, Mac mini, Mac Pro
Classic Mac
128K, 512K, Classic, Lisa, Plus, Power Mac, PowerBook, Quadra
Mobile Phone
iOS
Is the PEG0() device the geforce 1080? I think that if that is the case, you are at the mercy of the card and the drivers for the card to resume from sleep correctly.

There seems to have been quite a few updates for the nvidia drivers lately - did updating help?

cheers... Brad
Running the latest Nvidia drivers with 10.12.5. Switching dark wake to 10, which does not wake the display, seems to fix the problem.
 
Joined
Jul 16, 2011
Messages
59
Motherboard
Gigabyte Z270X ULTRA GAMING
CPU
i5-7600K
Graphics
Who Knows
Hello

i've got an Z270X Ultra Gaming with 980ti and i5 7600K

I've gote exactly the same issue, crash and reboot after several dark cycles.

I dont know if i can see anything in any log as it crashes immediately, and i dont know the reason.

I've seen also a sleepimage in /var/vm. It's my first hackintosh to see that.

I'm trying also to debug this since days.

This morning, reading this thread, i'm trying a new set of paramaters > darkwake=0 and autopoweroff=0

Probably the smbios used is part of the global issue.

Does anyone found the right solution yet ?
 
Joined
Nov 27, 2011
Messages
12
Motherboard
GA Z170MX-Gaming 5
CPU
Skylake 6700K
Graphics
Aorus Radeon RX 570 4GB
Mac
MacBook Pro
Mobile Phone
iOS
RTFM update... :banghead:

I will report back after I disable all three settings and go through another 24hr cycle.
How did you get on with your testing?

After ages trying to debug a High Sierra sleep issue (CPU PM, Display EEID, USB power, BIOS, my AMD RX 570. You name it.) whereby I could get through the first sleep cycle after boot, but the second one the displays would sleep but the machine wouldn't and rebooted after a few minutes, I have just run:

sudo pmset -a autopoweroff 0
sudo pmset -a hibernatemode 0
sudo pmset -a standby 0

darkwake=1

And the second sleep cycle has been successful. So I'll take that for now!

Is this a noob problem? Probably. But I haven't come across that may posts suggesting this recently - only reference was El Cap, I hope this solution persists. Maybe I'll look into getting standby/autopoweroff working. Save myself some electricity. I'll try enabling both in a few days.
 
Joined
Oct 24, 2018
Messages
1
Motherboard
ga-z77-ds3h
CPU
i5-3570k
Graphics
hd4000
I have A similar problem. Crash after some number of dark wake cycles. I have darkewake set to 8 and these setting for power mgmgt.

Code:
System-wide power settings:
Currently in use:
standby              0
Sleep On Power Button 1
womp                 0
autorestart          0
hibernatefile        /dev/null
powernap             1
networkoversleep     0
disksleep            0
sleep                15
autopoweroffdelay    28800
hibernatemode        0
autopoweroff         0
ttyskeepawake        1
displaysleep         15
standbydelay         84000
Code:
Sun May 21 05:51:07 on console
$ pmset -g log | grep -i failure
2017-05-15 21:51:38 -0700 Failure                 Drivers Failure during wake due to PEG0():                                             
2017-05-16 18:28:48 -0700 Failure                 Drivers Failure during wake due to PEG0():                                             
2017-05-17 18:31:55 -0700 Failure                 Drivers Failure during wake due to PEG0():                                             
2017-05-19 01:24:38 -0700 Failure                 Drivers Failure during wake due to PEG0():                                             
2017-05-20 12:42:48 -0700 Failure                 Drivers Failure during wake due to PEG0():
I get the dreaded Drivers failure msg, common on AMD but I'm running a geforce 1080. Sleeps for hours and wakes without problems but longer sleep always causes a reboot. 10.12.5.

I tried disabling hibernate in clover but that setting only seems to effect whether clover tries to resume from hibernate. I'll try different modes for dark wake next. Tough to debug because it takes so long test.


Any ideas?
Try to set PCI-E at Gen2.0 in bios setting.It works on my pc with Z77 or H81-D3
 
Top