Instant wake from sleep "Wake reason: GLAN XDCI" (Skylake, El Capitan)

[kn0]

When I put the computer to sleep, it enters sleep mode for less than a second, and then the fans spin up, the lights turn on, and it wakes up again.

$ syslog | grep -i "Wake reason"
Jul 26 23:51:13 kn-mac kernel[0] <Notice>: Wake reason: GLAN XDCI

Troubleshooting so far:

• Wake On LAN is disabled in SysPrefs > Energy Saver and in the BIOS
• When Ethernet cable is disconnected: no change in behavior
• When both Ethernet and USB bluetooth dongle (enabled using BrcmPatchRAM kexts) are disconnected:
  • Wakes up, but keeps the display off. Tries to go back to sleep, wakes itself up again, cycle repeats indefinitely every few minutes.

Can anyone point me in the right direction?

System specifications: OS X 10.11.6, i5-6500, ASUS H110M-A motherboard, GTX 970 w/ web drivers
Clover config.plist should be attached

 

[aa15032261]

Easiest way to solve this problem is to modify dsdt,

1. Find "Device (GLAN)", you should see sth like this:

Device (GLAN)
{
   //......
   Method (_PRW, 0, NotSerialized)  // _PRW: Power Resources for Wake
   {
      Return (GPRW (0x0D, 0x04))
   }
   //......
}

2. Change "Return (GPRW (0x0D, 0x04))" to "Return (GPRW (0x09, 0x04))"
or remove entire _PRW block

 

[BillG66]

Easiest way to solve this problem is to modify dsdt,

1. Find "Device (GLAN)", you should see sth like this:

Device (GLAN)
{
   //......
   Method (_PRW, 0, NotSerialized)  // _PRW: Power Resources for Wake
   {
      Return (GPRW (0x0D, 0x04))
   }
   //......
}

2. Change "Return (GPRW (0x0D, 0x04))" to "Return (GPRW (0x09, 0x04))"
or remove entire _PRW block

I'm having the same problem. Terminal gave me the error GLAN XDCI XHC. Here's what I have in my DSDT:

Method (_PRW, 0, NotSerialized) // _PRW: Power Resources for Wake
{
Return (GPRW (0x6D, 0x04))

I changed the "6D" to "9," but when I tried to save I got an error message in MaciASL...

The document “DSDT.aml” could not be saved.

The compiler returned one or more errors.

And here's what was in the log:

313, 6074, Name already exists in scope (BNUM)
4614, 3130, Result is not used, possible operator timeout will be missed
12704, 3115, Not all control paths return a value (CGLS)

That "Not all control paths return a value" was repeated a lot with a lot of different acronyms at the end. Any idea how I can correct this? I really need my sleep to work. Thanks!

 

[KrisCris]

I'm having the same problem. Terminal gave me the error GLAN XDCI XHC. Here's what I have in my DSDT:



I changed the "6D" to "9," but when I tried to save I got an error message in MaciASL...



And here's what was in the log:



That "Not all control paths return a value" was repeated a lot with a lot of different acronyms at the end. Any idea how I can correct this? I really need my sleep to work. Thanks!

so have you solve that problem?
same value in dsdt, same reason for wake.
i'm not sure whether change 6d to 9 works.

 

[tzaibach]

Hello,

From a week ago, my NUC7 began to wake up by itself only 1-2 seconds after sleep (but keeping monitor off). I think it began after installing a system security update.

So, after reading some threads from the forums, I tried this:

# sudo pmset proximitywake 0

Well, what I really did was the equivalent setting with Hackintool (since this tool warned me about this parameter, as it was set with a value of 1). But this it what this tool modified afterall.

I also added this parameter to the boot arguments.

darkwake=0

And the problem was gone.

Hope this helps.

 

[tzaibach]

Hello,

From a week ago, my NUC7 began to wake up by itself only 1-2 seconds after sleep (but keeping monitor off). I think it began after installing a system security update.

So, after reading some threads from the forums, I tried this:

# sudo pmset proximitywake 0

Well, what I really did was the equivalent setting with Hackintool (since this tool warned me about this parameter, as it was set with a value of 1). But this it what this tool modified afterall.

I also added this parameter to the boot arguments.

darkwake=0

And the problem was gone.

Hope this helps.

Hello again:

Today I've been aware of an additional step needed to repair this unwanted 'wakeup' behaviour, at least if it was caused by a system software update:

You'll need to reinstall/update Clover (I recommend to do it with Hackingtool). I think it is because of a startup script, installed by Clover installer, that the OS system update disables. So it needs to be re-enabled.

As it is shown in the Clover installer log output:

Activating /etc/rc.boot.d/70.disable_sleep_proxy_client.local rc script

This script "disables mDNSResponder sleep proxy client" (and it "will prevent the system waking from sleep every hours").

Hope this helps. Regards,