Situation
While the lid is closed and running on battery, my Mac wakes every ~15 seconds in a DarkWake state instead of staying properly asleep. pmset -g log shows a repeating pattern over an over:
Over one overnight period this produced ~80-160 DarkWakes/hour, with ~65-70% of them tagged as network-packet-triggered (E_RX_IP_PACKET/ARPT) and occurring in tight bursts (many wakes <20s apart). Battery drops noticeably overnight as a result.
What I've tested
- powernap/womp already disabled on battery --> no effect on the pattern.
- Disabling tcpkeepalive on battery (sudo pmset -b tcpkeepalive 0) --> no improvement, same rate/pattern.
- Turning Wi-Fi and Bluetooth both off before closing the lid --> completely fixes it (flat battery %, DarkWakes drop to ~1/hour, all benign housekeeping, none network-tagged).
Unified log (log show) traces the wake to the Wi-Fi/BT combo chip's SMC signal, and separately shows this chip doesn't support TCP keep-alive hardware offload, but since disabling tcpkeepalive didn't help, the actual driver seems to be Wi-Fi-side network/AWDL-related maintenance traffic (possibly Continuity/AirDrop discovery. I see rapportd/AMPDevice holding open AWDL peer connections to nearby paired Apple devices) rather than keepalive itself.
Anyone else seeing this on Tahoe / M5 hardware?
Looking for a fix short of disabling Wi-Fi/Bluetooth every night to save battery.
While the lid is closed and running on battery, my Mac wakes every ~15 seconds in a DarkWake state instead of staying properly asleep. pmset -g log shows a repeating pattern over an over:
Bash:
2026-09-03 23:45:31 +0200 DarkWake DarkWake from Deep Idle [CDN] : due to smc.sysState.Wake(0x70070000) wifibt SMC.OutboxNotEmpty centauri-alpha E_RX_IP_PACKET ARPT/ Using BATT (Charge:66%) 5 secs
2026-09-03 23:45:36 +0200 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using Batt (Charge:66%) 2 secs
2026-09-03 23:45:38 +0200 DarkWake DarkWake from Deep Idle [CDN] : due to smc.sysState.Wake(0x70070000) wifibt SMC.OutboxNotEmpty centauri-beta/ Using BATT (Charge:66%) 7 secsOver one overnight period this produced ~80-160 DarkWakes/hour, with ~65-70% of them tagged as network-packet-triggered (E_RX_IP_PACKET/ARPT) and occurring in tight bursts (many wakes <20s apart). Battery drops noticeably overnight as a result.
What I've tested
- powernap/womp already disabled on battery --> no effect on the pattern.
- Disabling tcpkeepalive on battery (sudo pmset -b tcpkeepalive 0) --> no improvement, same rate/pattern.
- Turning Wi-Fi and Bluetooth both off before closing the lid --> completely fixes it (flat battery %, DarkWakes drop to ~1/hour, all benign housekeeping, none network-tagged).
Unified log (log show) traces the wake to the Wi-Fi/BT combo chip's SMC signal, and separately shows this chip doesn't support TCP keep-alive hardware offload, but since disabling tcpkeepalive didn't help, the actual driver seems to be Wi-Fi-side network/AWDL-related maintenance traffic (possibly Continuity/AirDrop discovery. I see rapportd/AMPDevice holding open AWDL peer connections to nearby paired Apple devices) rather than keepalive itself.
Anyone else seeing this on Tahoe / M5 hardware?
Looking for a fix short of disabling Wi-Fi/Bluetooth every night to save battery.
