MacBook Pro M1 wakes due to USB-C charging?

I am running a MacBook Pro M1 14" on Monterey 12.1 using a (new) LG 34WP85C-B on USB-C.


Sure, my intention was to have only 1 cable going from my MacBook to the Monitor to charge, display and also use the upstream for the monitors USB-hub.


It seems crazy but i assume that my MacBook is waking up due charging from USB. The following "DarkWake" event is suggesting this:

2021-12-20 09:57:49 +0100 DarkWake            	DarkWake from Deep Idle [CDNP] : due to ATC2.USBWakeup/ Using AC (Charge:100%) 45 secs
2021-12-20 09:57:49 +0100 WakeDetails         	DriverReason:ATC2.USBWakeup - DriverDetails:
2021-12-20 09:57:49 +0100 HibernateStats      	hibmode=3 standbydelaylow=0 standbydelayhigh=0


I thought using MagSafe might stop waking up, but this also happens with MagSafe additionally plugged in.


So i recorded the following cycle (pmset -g log):

  • Put the MacBook to sleep, both displays and the mouse turn off
  • After ~3 min my USB Razor mouse lights up (does not matter if connected directly to the MacBook or via. the monitors USB-hub)
  • Seconds after this event my external display also wakes up showing "no input" message
  • The external display puts itself to sleep again after some time
  • Mouse light stays on almost all the time, but I feel occasionally it goes out. Haven't found some meaningful sequence there, looks random.
  • After a few minutes the external display comes to live again and turns off



You see exactly 2 of those "DarkWake" events, the number of on/off events of my external display:

DarkWake from Deep Idle [CDNP] : due to ATC2.USBWakeup/ Using AC (Charge:100%)


This cycle never stops.

External display turns on and off all the time.

"Total Sleep/Wakes" counter incremented by 3.

Mouse light occasionally goes out, but i guess stays on most of the time.


I started to turn off the external display which is annoying, because you have to move several open windows back to their intended work spaces every time you continue your work. As a programmer you know what that means. With the display off, you can still see what is happening from the light of the mouse, but at least the display is not switching on/off all the time.


I did a ~6min sleep using MagSafe and HDMI for the external display:


Mouse does not light up once.

No "DeepWake" and the "Total Sleep/Wakes" counter incremented by 1.

= Expected behaviour when going to sleep and waking up by HID.


pmset -g custom:

AC Power:
 Sleep On Power Button 1
 lowpowermode         0
 standby              1
 ttyskeepawake        1
 hibernatemode        3
 powernap             1
 hibernatefile        /var/vm/sleepimage
 displaysleep         60
 womp                 0
 networkoversleep     0
 sleep                0
 tcpkeepalive         1
 disksleep            10


I also experience "DeepWakes" as described here: https://discussions.apple.com/thread/252061187?page=2

But at this point, I don't think it is my main concern.

It does not seem to have something to do with the annoying behavior described above:


And you can see

ATC2.USBWakeup/ Using AC

in there all the time.


I really wonder why I can't find any information about this. I found some guys on Reddit having the exact same weird behavior going on.


Any ideas?


P.S.: Nice "additional Text" feature where nobody can read anything. They want to make it as hard as possible to get help.

Posted on Dec 20, 2021 1:52 AM

Reply
6 replies

Jan 14, 2022 7:13 AM in response to diego.velasquez.lopez

Sorry, Apple didn't spare a word regarding those wake issues, either officially (AFAIK) nor regarding my open support ticket.


I now use HDMI, MagSafe and a USB-C Hub, three cables instead of one, in order to put the system to sleep without the ever waking external screen. All the other wakes mentioned above (and in a separate thread) still remain. You can watch the light of a USB mouse being active almost all the time.


Essentially, you can't put it to sleep properly, no matter the external screen or not.


Many similar reports all over Reddit and here. This is a major fault and should get much more attention.


Dec 20, 2021 4:38 AM in response to kaz-k

Thanks, I think you are right.

In the meantime I simply tested sleep (w/o prev changing any settings) on a Lenovo ThinkPad (Windows 10 Pro) with the same monitor using USB-C.

Behavior as expected: external monitor stays off and the ThinkPad charges.


I already reported to apple directly and they are aware about this thread too.


Hope that something comes to light.

Jan 14, 2022 7:15 AM in response to theuema

that's annoying, I went from 92% to 53% (from 9pm to 9am)


```

2022-01-14 08:55:07 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:54%) 17 secs  

2022-01-14 08:55:26 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:54%) 17 secs  

2022-01-14 08:55:46 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 16 secs  

2022-01-14 08:56:05 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 16 secs  

2022-01-14 08:56:24 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 16 secs  

2022-01-14 08:56:43 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 16 secs  

2022-01-14 08:57:02 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 18 secs  

2022-01-14 08:57:22 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 17 secs  

2022-01-14 08:57:42 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 16 secs  

2022-01-14 08:58:00 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 17 secs  

2022-01-14 08:58:20 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 16 secs  

2022-01-14 08:58:39 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 17 secs  

2022-01-14 08:58:59 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 5 secs   

2022-01-14 08:59:06 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 8 secs   

2022-01-14 08:59:16 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 6 secs   

2022-01-14 08:59:24 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 6 secs   

2022-01-14 08:59:32 -0500 DarkWake       DarkWake from Deep Idle [CDN] : due to NUB.SPMISw3IRQ nub-spmi0.0x02 rtc/ Using BATT (Charge:53%) 5 secs   

```

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

MacBook Pro M1 wakes due to USB-C charging?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.