Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

mac keeps waking after sleep...

fisherking

fisherking

macrumors G4
Original poster
Jul 16, 2010
11,084
5,432
ny somewhere
sorry! as the OP, i added 'resolved' as the 12.3 beta seems to have fixed it for me (and/or resetting my satechi keyboard).

pretty sure it's 12.3 beta, as the problem (for me) started with the 12.2 beta just before the 12.2 official release (where the problem continued).

am in the US. and hope everyone else gets this sorted!
 
M

MahatmaFatal

macrumors newbie
Dec 2, 2012
4
0
GER user here with the same issue (with US magic keyboard via BT) since update to 12.2.
SMC/NVRAM reset etc did not help.

Note that I turned the keyboard off before setting the mac to sleep. Besides that, a usb-c display (unplugged from power) and a usb-c-to-a adapter is connected. The only thing that helped was unplugging all cables from the macbook.

I collected some logs, but I am not sure how to narrow down the root-cause...

❯ log show --start '2022-01-28' | rg -i "Wake reason" -C10 (with ripgrep)
Code: 
2022-01-28 02:59:03.134351+0100 0x337      Default     0x0                  0      0    kernel: (IOBluetoothHIDDriver) **** [IOBluetoothHIDDriver][AppleHSBluetoothDevice][handleSleep][c0-a5-3e-08-7e-cd] -- setting mHandshakeTimeoutCounter to 1 and _mUseSleepTimeout to true -- this = 0x3D80 ****
2022-01-28 02:59:03.134390+0100 0x337      Default     0x0                  149    0    bluetoothd: [com.apple.bluetooth:Server.HID] HIDProfile::prepareForSleep() -- Sending setReport via enqueueUserSpaceHIDDataForDevice for Clear Wake Reason for device 181CFC5C
2022-01-28 02:59:04.865654+0100 0x10d538   Default     0x0                  0      0    kernel: (AppleTopCaseHIDEventDriver) [HID] [ATC] [Error] AppleDeviceManagementHIDEventService::setWakeReason Error setting wake reason (reportID = 0xc5, Return Value = 0xe00002ca)
--
2022-01-28 02:59:05.419070+0100 0x74       Default     0x0                  0      0    kernel: (AppleACPIPlatform) Facs->XFirmwareWakingVector: 0x0
2022-01-28 02:59:05.419073+0100 0x74       Default     0x0                  0      0    kernel: (AppleACPIPlatform) Facs->OspmFlags: 0x0
2022-01-28 02:59:05.430558+0100 0x74       Default     0x0                  0      0    kernel: [105506.902204]: IOPlatformQuiesceAction -> AppleVTD
2022-01-28 02:59:05.430562+0100 0x74       Default     0x0                  0      0    kernel: [105506.903624]: IOPlatformActiveAction -> AppleVTD
2022-01-28 02:59:05.430568+0100 0x74       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI S3 WAKE
2022-01-28 02:59:05.441188+0100 0x74       Default     0x0                  0      0    kernel: (AppleACPIPlatform) Facs->FirmwareWakingVector: 0x0
2022-01-28 02:59:05.441192+0100 0x74       Default     0x0                  0      0    kernel: (AppleACPIPlatform) Facs->Length: 0x40
2022-01-28 02:59:05.441195+0100 0x74       Default     0x0                  0      0    kernel: (AppleACPIPlatform) Facs->Version: 0x1
2022-01-28 02:59:05.441198+0100 0x74       Default     0x0                  0      0    kernel: (AppleACPIPlatform) Facs->XFirmwareWakingVector: 0x0
2022-01-28 02:59:05.441201+0100 0x74       Default     0x0                  0      0    kernel: (AppleACPIPlatform) Facs->OspmFlags: 0x0
2022-01-28 02:59:05.446758+0100 0x74       Default     0x0                  0      0    kernel: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance)
2022-01-28 02:59:05.446762+0100 0x74       Default     0x0                  0      0    kernel: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance)
2022-01-28 02:59:05.446777+0100 0x74       Default     0x0                  0      0    kernel: PMRD: trace point 0x22
2022-01-28 02:59:05.446954+0100 0x74       Default     0x0                  0      0    kernel: IOPlatformWakeAction -> AppleThunderboltHAL
2022-01-28 02:59:05.446963+0100 0x74       Default     0x0                  0      0    kernel: IOPlatformWakeAction -> AppleThunderboltHAL
2022-01-28 02:59:05.446969+0100 0x74       Default     0x0                  0      0    kernel: IOPlatformWakeAction -> AppleRTC
2022-01-28 02:59:05.446976+0100 0x74       Default     0x0                  0      0    kernel: IOPlatformWakeAction -> AppleKeyStore
2022-01-28 02:59:05.446983+0100 0x74       Default     0x0                  0      0    kernel: IOPlatformWakeAction -> AppleSMC
2022-01-28 02:59:05.446992+0100 0x74       Default     0x0                  0      0    kernel: PMRD: trace point 0x23
2022-01-28 02:59:05.451165+0100 0x74       Default     0x0                  0      0    kernel: Started cpu 2 (lapic id 00000002)
2022-01-28 02:59:05.455256+0100 0x74       Default     0x0                  0      0    kernel: Started cpu 4 (lapic id 00000004)
2022-01-28 02:59:05.459353+0100 0x74       Default     0x0                  0      0    kernel: Started cpu 6 (lapic id 00000006)
--
2022-01-28 02:59:10.596056+0100 0x74       Default     0x0                  0      0    kernel: PMRD: PowerChangeDone: ON_STATE->ON_STATE
2022-01-28 02:59:10.596060+0100 0x74       Default     0x0                  0      0    kernel: PMRD: PowerChangeOverride (ON_STATE->ON_STATE, 9, 0x2) tag 0x1ae80008
2022-01-28 02:59:10.596061+0100 0x74       Default     0x0                  0      0    kernel: PMRD: PowerChangeDone: ON_STATE->ON_STATE
2022-01-28 02:59:10.596066+0100 0x74       Default     0x0                  0      0    kernel: PMRD: evaluatePolicy( 6, 0xd35 )
2022-01-28 02:59:10.596067+0100 0x74       Default     0x0                  0      0    kernel: PMRD: dark wake entry
2022-01-28 02:59:10.596070+0100 0x74       Default     0x0                  0      0    kernel: PMRD: DarkWake: sleepASAP 1, clamshell closed 1, disabled 0/1, desktopMode 0, ac 0
2022-01-28 02:59:10.596072+0100 0x74       Default     0x0                  0      0    kernel: PMRD: System sleep prevented by kPMCPUAssertion
2022-01-28 02:59:10.596091+0100 0x10d53c   Activity    0x158524             136    0    dasd: (CoreDuetContext) Duet: ClientContext objectForContextualKeyPath:
2022-01-28 02:59:10.596384+0100 0x10d65c   Default     0x0                  0      0    kernel: PMRD: disk spindown accelerated, was 10 min
2022-01-28 02:59:10.596749+0100 0x10d53c   Activity    0x158525             136    0    dasd: (CoreDuetContext) Duet: ClientContext objectForContextualKeyPath:
2022-01-28 02:59:10.599659+0100 0x10d642   Default     0x0                  0      0    kernel: (AppleTopCaseHIDEventDriver) [HID] [ATC] AppleDeviceManagementHIDEventService::processWakeReason Wake reason: Host (0x01)
2022-01-28 02:59:10.601493+0100 0x326      Default     0x0                  121    0    apsd: <private>: prepareForDarkWake
2022-01-28 02:59:10.601526+0100 0x4e3      Default     0x0                  221    0    mDNSResponder: [com.apple.mDNSResponder:Default] <private>
2022-01-28 02:59:10.601527+0100 0x326      Default     0x0                  121    0    apsd: [com.apple.apsd:daemon] <private>: prepareForDarkWake
2022-01-28 02:59:10.601527+0100 0x4e3      Default     0x0                  221    0    mDNSResponder: [com.apple.mDNSResponder:Default] <private>
2022-01-28 02:59:10.601529+0100 0x4e3      Default     0x0                  221    0    mDNSResponder: [com.apple.mDNSResponder:Default] <private>
2022-01-28 02:59:10.601734+0100 0x10d587   Activity    0x1585bb             184    0    runningboardd: (RunningBoard) acquireAssertionWithDescriptor
2022-01-28 02:59:10.601832+0100 0x10d587   Default     0x1585bb             184    0    runningboardd: (RunningBoard) [com.apple.runningboard:assertion] Acquiring assertion targeting [daemon<com.apple.apsd>:121] from originator [daemon<com.apple.powerd>:85] with description <RBSAssertionDescriptor| "App is holding power assertion" ID:184-85-36198 target:121 attributes:[
    <RBSDomainAttribute| domain:"com.apple.appnap" name:"PowerAssertion" sourceEnvironment:"(null)">,
    <RBSAcquisitionCompletionAttribute| policy:AfterApplication>
    ]>
--
2022-01-28 02:59:10.599659+0100 0x10d642   Default     0x0                  0      0    kernel: (AppleTopCaseHIDEventDriver) [HID] [ATC] AppleDeviceManagementHIDEventService::processWakeReason Wake reason: Host (0x01)
2022-01-28 02:59:10.601493+0100 0x326      Default     0x0                  121    0    apsd: <private>: prepareForDarkWake
2022-01-28 02:59:11.050496+0100 0x10d66c   Default     0x0                  0      0    kernel: (AppleTopCaseHIDEventDriver) [HID] [ATC] AppleDeviceManagementHIDEventService::processWakeReason Wake reason: Host (0x01)
2022-01-28 02:59:41.172745+0100 0x337      Default     0x0                  149    0    bluetoothd: [com.apple.bluetooth:Server.HID] HIDProfile::prepareForSleep() -- Sending setReport via enqueueUserSpaceHIDDataForDevice for Clear Wake Reason for device 181CFC5C
2022-01-28 02:59:44.391890+0100 0x10d66c   Default     0x0                  0      0    kernel: (AppleTopCaseHIDEventDriver) [HID] [ATC] [Error] AppleDeviceManagementHIDEventService::setWakeReason Error setting wake reason (reportID = 0xc5, Return Value = 0xe00002ca)
2022-01-28 02:59:45.786516+0100 0x74       Default     0x0                  0      0    kernel: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance)
2022-01-28 02:59:45.786518+0100 0x74       Default     0x0                  0      0    kernel: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance)
2022-01-28 03:03:41.706708+0100 0x76       Default     0x0                  0      0    kernel: (AppleTopCaseHIDEventDriver) [HID] [ATC] AppleDeviceManagementHIDEventService::processWakeReason Wake reason: Host (0x01)
2022-01-28 03:04:15.060133+0100 0x94b      Default     0x0                  0      0    kernel: (AppleTopCaseHIDEventDriver) [HID] [ATC] AppleDeviceManagementHIDEventService::processWakeReason Wake reason: Keyboard (0x02)


❯ log show --start '2022-01-28' | rg -i "Wake Request" -C10
Code: 
2022-01-28 02:58:27.175901+0100 0x10d192   Default     0x0                  85     0    powerd: [powerd:wakeRequests] Selected RTC wake request: {
    UserVisible = 0;
    appPID = 1292;
    eventtype = wake;
    scheduledby = "com.apple.alarm.user-visible-Weekly Usage Report";
    time = "2022-01-31 02:04:38 +0000";
}

2022-01-28 02:58:44.964103+0100 0x10d3e1   Default     0x0                  85     0    powerd: [powerd:wakeRequests] Selected RTC wake request: {
    UserVisible = 0;
    appPID = 1292;
    eventtype = wake;
    scheduledby = "com.apple.alarm.user-visible-Weekly Usage Report";
    time = "2022-01-31 02:04:38 +0000";
}

2022-01-28 02:59:04.606456+0100 0x10d4ef   Default     0x0                  85     0    powerd: [powerd:wakeRequests] Selected RTC wake request: {
    UserVisible = 0;
    appPID = 1292;
    eventtype = wake;
    scheduledby = "com.apple.alarm.user-visible-Weekly Usage Report";
    time = "2022-01-31 02:04:38 +0000";
}

❯ pmset -g log |grep "Wake Request"
Code: 
2022-01-28 02:58:27 +0100 Wake Requests         [*process=powerd request=TCPKATurnOff deltaSecs=20540 wakeAt=2022-01-28 08:40:47] [process=powerd request=UserWake deltaSecs=259571 wakeAt=2022-01-31 03:04:38 info="com.apple.alarm.user-visible-Weekly Usage Report,1292"]
2022-01-28 02:58:44 +0100 Wake Requests         [*process=powerd request=TCPKATurnOff deltaSecs=20522 wakeAt=2022-01-28 08:40:47] [process=powerd request=UserWake deltaSecs=259553 wakeAt=2022-01-31 03:04:38 info="com.apple.alarm.user-visible-Weekly Usage Report,1292"]
2022-01-28 02:59:04 +0100 Wake Requests         [*process=powerd request=TCPKATurnOff deltaSecs=20503 wakeAt=2022-01-28 08:40:47] [process=powerd request=UserWake deltaSecs=259533 wakeAt=2022-01-31 03:04:38 info="com.apple.alarm.user-visible-Weekly Usage Report,1292"]
2022-01-28 02:59:42 +0100 Wake Requests         [*process=powerd request=TCPKATurnOff deltaSecs=20465 wakeAt=2022-01-28 08:40:47] [process=powerd request=UserWake deltaSecs=259495 wakeAt=2022-01-31 03:04:38 info="com.apple.alarm.user-visible-Weekly Usage Report,1292"]
2022-01-28 02:59:55 +0100 Wake Requests         [*process=powerd request=UserWake deltaSecs=259483 wakeAt=2022-01-31 03:04:38 info="com.apple.alarm.user-visible-Weekly Usage Report,1292"]

❯ pmset -g log | grep -i "wake from"
Code: 
2022-01-28 02:45:30 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:16%) 17 secs
2022-01-28 02:45:55 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:13%) 10 secs
2022-01-28 02:46:13 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:16%) 45 secs
2022-01-28 02:47:27 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:15%) 21 secs
2022-01-28 02:48:08 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:12%) 17 secs
2022-01-28 02:48:50 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:12%) 11 secs
2022-01-28 02:49:19 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:12%) 25 secs
2022-01-28 02:50:30 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:12%) 37 secs
2022-01-28 02:51:15 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:12%) 14 secs
2022-01-28 02:51:58 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:11%) 37 secs
2022-01-28 02:53:24 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:11%) 45 secs
2022-01-28 02:54:48 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:11%) 11 secs
2022-01-28 02:55:07 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:11%) 9 secs
2022-01-28 02:55:24 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:10%) 11 secs
2022-01-28 02:55:56 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:10%) 20 secs
2022-01-28 02:56:44 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:10%) 10 secs
2022-01-28 02:57:44 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:10%) 41 secs
2022-01-28 02:58:33 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:10%) 9 secs
2022-01-28 02:58:51 +0100 DarkWake                DarkWake from Normal Sleep [CDN] : due to EC.DarkPME/Maintenance Using BATT (Charge:10%) 11 secs
 
Last edited:
J.Gallardo

J.Gallardo

macrumors 6502
Apr 4, 2017
448
157
Spain
How it gets fixed (?) for me:

My (intel)iMac in 12.2.1 keeps waking without reason, but I suppose it's because my Logitech MX Anywhere2 mouse. When I leave my mac unattended, the sequence goes as I have configured: screensaver starts after 5', screen goes dark minutes after, and after that, it's supposed to go "sleep".
Watching for a long time, a couple of evenings: just after a minute screen goes dark, it awakes in same situation I left... not even asking for password! (Like it's configured). So, the problem is not just awaking, but my first "security" measure to leave my mac unattended is broken! If I leave the mac alone, the sequence starts again, till sudden wake up barely a minute after screen went off. And over and over...

My first solution:
for a few days, I've being switching off the mouse, quickly, after sending mac to sleep. OK, that works. So the bluetooth mouse seems to be the trigger. (My keyboard is wired, the only bluetooth device known by my mac is the mouse).

BUT:
I've discovered that leaving my mac at night, playing a list in Music, when it ends (screen is dark already when music ends)... the "planned" and configured sleeping happens!
And when I wake up my mac, password is required, as pretended.
All this, leaving my bluetooth mouse ON. Simply: if Music is the front app, everything works nicely.

So: could it be not Monterey, but "FINDER" (when being the "active" app) the culprit of something waking up the system?

Someone more could try to "fix" this inconvenience putting another app in front (I use Music), active, over Finder, to see if awaking keeps happening. Not in my system.
We could narrow this bug to be related to Finder, if someone more can reproduce this.
 
J.Gallardo

J.Gallardo

macrumors 6502
Apr 4, 2017
448
157
Spain
fisherking said:
oops: was posting this as fixed in 12.3 beta 3 (here), but... already reported that!
Click to expand...
Thank you; I forgot also. Nice to know the bug is (soon) mended.
I also left the thread at that point (when knew “beta” fixes it).

I came back when realized “the thing” was a big inconvenience for security reasons too (didn’t pay attention to that at first!). The problem is not as trivial as I thought!.

And came back to tell others about this strange way to avoid fail at “mac sleeping”. I write “strange” because I discovered by chance and surprised me, when I left a music list playing at night and every thing worked as expected.

Of course, the real solution -as you kindly point- is in the way. (But it’s not guaranteed!, I understand. It wouldn’t be first time that a subsequent required function breaks again a -considered- secondary and marginal problem fixed in a beta. I cross my fingers… ??).
 
Last edited:
I

ImToxic

macrumors newbie
Oct 10, 2022
1
1
I think I have a solution for some of the cases posted here. Had the same issue with my M1 MBA waking up a few seconds after putting it to sleep. I'm pretty sure that it was due to this small movement of my Bluetooth mouse just after clicking sleep, when doing it by keyboard shortcut it won't wake up by itself, have done a small experiment with the keyboard shortcut, and then mouse simulating this movement and it seems to be the case. Hope this will help someone.
 
  • Like
Reactions: terran5992
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom