Sleep Failure Error Reboots

[CablDeViL]

If I leave my Hackintosh running and I come back after an hour or so the machine is sitting at the clover bootloader screen. Checking the logs I come up with this.

pmset -g log | grep -i failure

2018-01-05 14:51:12 -0500 Failure Sleep Failure [code:0x340753004000031]:

2018-01-05 19:34:02 -0500 Failure Sleep Failure [code:0x340753000000031]:

2018-01-06 12:17:38 -0500 Failure Sleep Failure [code:0x340753004000031]:

I have read many post about shutdown issues but non like this.

 

[beelzebozo]

If I leave my Hackintosh running and I come back after an hour or so the machine is sitting at the clover bootloader screen. Checking the logs I come up with this.

pmset -g log | grep -i failure

2018-01-05 14:51:12 -0500 Failure Sleep Failure [code:0x340753004000031]:

2018-01-05 19:34:02 -0500 Failure Sleep Failure [code:0x340753000000031]:

2018-01-06 12:17:38 -0500 Failure Sleep Failure [code:0x340753004000031]:

I have read many post about shutdown issues but non like this.

I am experiencing the same issue on my z170-Deluxe at the moment and am trying to narrow it down. I can sleep my CustoMac once but once it goes back to sleep after it wakes, it seems to not know what to do and just restarts; in fact it takes about 5 minutes after it's supposed to sleep. I checked last night on a fresh install of 10.13.2 and an existing upgrade from 10.12.6 and got the same results. I didn't see this issue with 10.12

 

[beelzebozo]

Check these too:
pmset -g stats
pmset -g log

 

[beelzebozo]

Disable Thunderbolt completely in BIOS and it should fix the issue.

 

[TomHsiung]

Disable Thunderbolt completely in BIOS and it should fix the issue.

I have the same error (see logs below) but I don't have thunderbolt port. It seems that this reboot issue happened 6 hours after sleeping. The first reboot issue was with code:0xFFFFFFFF0400001F at about 6 hours after entering sleep. Then the machine rebooted into the login screen. After 1 hour (I set the time to wait to enter sleep 6 hours) the machine entered sleep, and after it had slept for 6 hours, it rebooted again, with code:0xFFFFFFFF0000001F.

My machine is a desktop build and here is what I found from the console.

Toms-iMac:Applications tomshome$ pmset -g log | grep -i failure
2018-01-11 07:21:35 +0800 Failure             	Sleep Failure [code:0xFFFFFFFF0400001F]:                                   	          
2018-01-11 11:57:12 +0800 Failure             	Sleep Failure [code:0xFFFFFFFF0000001F]:                                   	          
2018-01-15 07:48:46 +0800 Failure             	Sleep Failure [code:0xFFFFFFFF0400001F]:                                   	          
2018-01-15 13:00:15 +0800 Failure             	Sleep Failure [code:0xFFFFFFFF0000001F]:                                   	          
2018-01-16 05:56:08 +0800 Failure             	Sleep Failure [code:0xFFFFFFFF0400001F]:                                   	          
2018-01-16 12:59:44 +0800 Failure             	Sleep Failure [code:0xFFFFFFFF0000001F]:                                   	          
2018-01-20 06:00:45 +0800 Failure             	Sleep Failure [code:0xFFFFFFFF0400001F]:                                   	          
2018-01-20 13:04:55 +0800 Failure             	Sleep Failure [code:0xFFFFFFFF0000001F]:                                   	          
Toms-iMac:Applications tomshome$

Apple's official community has threads discussing this issue two, and many many people met the same issue on their machines since 10.13.2 update. Maybe to wait for the fix in Apple's next macOS update is the solution.

Tom

 

[JulioVM]

I am in the same boat, with this output

Julios-iMac:~ julio$ pmset -g log | grep -i failure
2018-01-21 14:32:15 -0500 Failure Sleep Failure [codeEG0(),XHC(XHC),I2C1(AppleIntelLpssI2C),SAT0(AppleIntelPchSeriesAHCI),RP05(RTL8111),RP06(),RP09(),PPMC(),HDEF()]:
2018-01-21 19:01:07 -0500 Failure Sleep Failure [codeEG0(),XHC(XHC),I2C0(AppleIntelLpssI2C),I2C1(AppleIntelLpssI2C),SAT0(AppleIntelPchSeriesAHCI),RP05(RTL8111),RP06(),RP09(),PPMC(),HDEF()]:

 

[TomHsiung]

This issue (sleep failure 0xFFFFFFFF0400001F) is caused by the autopoweroff setting in pmset. Turn off the autopoweroff option should resolve this issue.

 

[beelzebozo]

@TomHsiungNot sure that's the fix.

@CablDeViL See the example for the z170-Deluxe:

2019-08-04 15:45:53.580263-0400 0x44d59 Default 0x0 0 0 kernel: (AppleUSBXHCI) 015354.585393 AppleUSB30XHCIPort@03300000: AppleUSBXHCIPortowerOn: deadline passed (PORTSC 0x00000000)


2019-08-04 15:45:53.580263-0400 0x44d5e Default 0x0 0 0 kernel: (AppleUSBXHCI) 015354.585394 AppleUSB20XHCIPort@03200000: AppleUSBXHCIPortowerOn: deadline passed (PORTSC 0x00000000)


2019-08-04 15:45:53.580282-0400 0x44d5c Default 0x0 0 0 kernel: (AppleUSBXHCI) 015354.585423 AppleUSB20XHCIPort@03100000: AppleUSBXHCIPortowerOn: deadline passed (PORTSC 0x00000000)


2019-08-04 15:45:53.580304-0400 0x44d5d Default 0x0 0 0 kernel: (AppleUSBXHCI) 015354.585451 AppleUSB30XHCIPort@03400000: AppleUSBXHCIPortowerOn: deadline passed (PORTSC 0x00000000)


2019-08-04 15:45:53.585243-0400 0x1062 Default 0x0 358 0 identityservicesd: (IDSFoundation) [com.apple.Transport:GL] GLR 46B (0, 2, 0).


2019-08-04 15:45:53.585583-0400 0x1062 Default 0x0 358 0 identityservicesd: (IDSFoundation) [com.apple.Transport:GL] GLW 144B (0, 2, 0).


2019-08-04 15:45:53.600824-0400 0x44d5e Default 0x0 0 0 kernel: (IOUSBHostFamily) 015354.605981 AppleUSBXHCIAR@03000000: AppleUSBHostController::setPowerStateGated: going to state 1 returned 0xe00002e9


2019-08-04 15:45:53.600838-0400 0x44d5a Default 0x0 0 0 kernel: (IOUSBHostFamily) 015354.605999 AppleUSBXHCIAR@03000000: AppleUSBHostController::hardwareExceptionThreadCallGated: attempting recovery


2019-08-04 15:45:53.600844-0400 0x44d5a Default 0x0 0 0 kernel: (IOUSBHostFamily) 015354.606004 AppleUSBXHCIAR@03000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000004


2019-08-04 15:45:53.600849-0400 0x44d5a Default 0x0 0 0 kernel: (IOUSBHostFamily) 015354.606010 AppleUSBXHCIAR@03000000: AppleUSBHostController::hardwareExceptionThreadCallGated: attempting recovery


2019-08-04 15:45:53.600879-0400 0x44d5e Default 0x0 0 0 kernel: (IOUSBHostFamily) 015354.606038 AppleUSBXHCIAR@03000000: AppleUSBHostController::setPowerStateGated: going to state 2 failed with 0xe00002e9


2019-08-04 15:45:53.600884-0400 0x44d5e Default 0x0 0 0 kernel: (IOUSBHostFamily) 015354.606045 AppleUSBXHCIAR@03000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000008


2019-08-04 15:45:53.605554-0400 0x1062 Default 0x0 358 0 identityservicesd: (IDSFoundation) [com.apple.Transport:GL] GLW 146B (0, 2, 0).


It should be disabled.

If you look in IOJones at the PXSX bridge path, you'll see pci8086,15b6 at that address. In fact, if you look at the last USB device in System Report, you'll see AppleUSBXHCIAR.

8086 15B6 2222 1111 Intel Corporation DSL6540 USB 3.1 Controller [Alpine Ridge]
Serial bus controlle USB controller pci-bridge.pci8 pci8086,15b6 PciRoot(0x0)/Pci(0x1b,0x0)/Pci(0x0,0x0)/

Under powermanagement logs, the following shows:
Sleep Failure [code:0x340753004000031]:

You can see in the 2nd screenshot below where AppleUSBXHCIAR is loaded.

Unfortunately, you have to boot with Above 4G decoding = Enabled for Thunderbolt. USB Port limit fix also don't resolve this.

You should still see the following Controller Driver when Thunderbolt is enabled. AppleUSBXHCIAR is Alpine Ridge.

System will sleep once but after it wakes and attempts to enter sleep state again, it will restart.

 

[beelzebozo]

If I leave my Hackintosh running and I come back after an hour or so the machine is sitting at the clover bootloader screen. Checking the logs I come up with this.

pmset -g log | grep -i failure

2018-01-05 14:51:12 -0500 Failure Sleep Failure [code:0x340753004000031]:

2018-01-05 19:34:02 -0500 Failure Sleep Failure [code:0x340753000000031]:

2018-01-06 12:17:38 -0500 Failure Sleep Failure [code:0x340753004000031]:

I have read many post about shutdown issues but non like this.

See https://www.tonymacx86.com/threads/...-usb-port-control.253981/page-11#post-1996865 for an example of patching USB Ports.

The powermanagement error should be resolved with correct USB patching.