MBP 2021 M1 Pro - Shutdown itself while sleeping (warning appears)

[GoztepeEge]

Hello everyone!

I am currently using a 2021 MBP 14" base model for the last 3 months. I am happy with it, however I noticed a weird issue happening in the last 3 nights while I put my computer in a sleep mode.

Here is what I did in this last 3 days:
at night, I stopped working, I plugged off the charger cable, closed the lid. The device (I guess) gets into sleep mode.
- Open applications before closing the lid: Safari, Mail, Spotify
- Charge level before closing the lid: 50%
- HDMI cable of the external display stays connected (external display is closed as well as the MBP)
- MacOS Monterey 12.2.1 (currently the latest OS version)

The next day when I open the lid, it directly asks me to type password instead of having the ability to enter it via TouchID. It is because the computer restarts itself. When I enter the password, it opens the desktop, and a warning appears like "your computer has been restarted due to a problem" and buttons e.g. "report it to Apple".

Now I am curious what is happening, and what causes this?
Does anyone have any idea regarding this?

 

[Sanpete]

Are you doing anything differently from before the last three days? Did you run any unusual software, even if it's now closed?

Simplest thing might be to call Apple, and they'll (hopefully) look at your event logs and see what the problem is. (Or you might be able to do it yourself if you're determined enough.) I'd guess keeping it hooked up to the display is a factor, if the programs you list are the only ones open.

 

[vivid.gear71]

Thanks so much for reporting this issue.
using m1max and had crash TWICE while in sleep last several days on latest OSX.
it seems there is some issue with sleeping.
first crash I got report but second crash just happened a few mins ago didn't have any crash report. it was looking like nothing happened other than I had to manually boot computer

- using aldente to set charging limit to 75%
- Harddrive is connected as time machine
- using belkin gigabit ethernet adapter
- no external display
- mainly using for programming/video editing/browsing using safari

was checking console message and couldn't find anything useful

 

[julesme]

There are some threads on MR reporting similar issues that have caused kernel panics for some Apple Silicon users on Monterey. On these threads (you’ll have to search for them), I’ve seen complaints about third party accessories, sleep / wake problems, and Bluetooth. I think people are hoping it’s fixed in Monterey 12.3 or 12.4.

I made some changes to my setup a few weeks ago, and my kernel panics stopped happening, but unfortunately I can’t be sure exactly what was causing the problem (I’m using an M1 Max 14”, also on the latest Monterey).

 

[MayaUser]

Hello everyone!

I am currently using a 2021 MBP 14" base model for the last 3 months. I am happy with it, however I noticed a weird issue happening in the last 3 nights while I put my computer in a sleep mode.

Here is what I did in this last 3 days:
at night, I stopped working, I plugged off the charger cable, closed the lid. The device (I guess) gets into sleep mode.
- Open applications before closing the lid: Safari, Mail, Spotify
- Charge level before closing the lid: 50%
- HDMI cable of the external display stays connected (external display is closed as well as the MBP)
- MacOS Monterey 12.2.1 (currently the latest OS version)

The next day when I open the lid, it directly asks me to type password instead of having the ability to enter it via TouchID. It is because the computer restarts itself. When I enter the password, it opens the desktop, and a warning appears like "your computer has been restarted due to a problem" and buttons e.g. "report it to Apple".

Now I am curious what is happening, and what causes this?
Does anyone have any idea regarding this?

why it shutdown by itself ?

 

[GoztepeEge]

Are you doing anything differently from before the last three days? Did you run any unusual software, even if it's now closed?

Simplest thing might be to call Apple, and they'll (hopefully) look at your event logs and see what the problem is. (Or you might be able to do it yourself if you're determined enough.) I'd guess keeping it hooked up to the display is a factor, if the programs you list are the only ones open.

Tomorrow maybe I can try to read through logs. I also sent them to Apple as well.
I do nothing different actually. The programs and overall usage type are the same like 1 month ago.

Thanks so much for reporting this issue.
using m1max and had crash TWICE while in sleep last several days on latest OSX.
it seems there is some issue with sleeping.
first crash I got report but second crash just happened a few mins ago didn't have any crash report. it was looking like nothing happened other than I had to manually boot computer

- using aldente to set charging limit to 75%
- Harddrive is connected as time machine
- using belkin gigabit ethernet adapter
- no external display
- mainly using for programming/video editing/browsing using safari

was checking console message and couldn't find anything useful

The only similarity between your and my case is "AlDente", I am using that as well and always limited to 50%. When I put the device into sleep, I plug off the charger. Then in the morning I see that the device was restarted sometime during the night. (Today it has happened as well)

There are some threads on MR reporting similar issues that have caused kernel panics for some Apple Silicon users on Monterey. On these threads (you’ll have to search for them), I’ve seen complaints about third party accessories, sleep / wake problems, and Bluetooth. I think people are hoping it’s fixed in Monterey 12.3 or 12.4.

I made some changes to my setup a few weeks ago, and my kernel panics stopped happening, but unfortunately I can’t be sure exactly what was causing the problem (I’m using an M1 Max 14”, also on the latest Monterey).

I am also using a bluetooth keyboard and Apple mouse as well. But actually I turned them off before putting the device in sleep, so they are not connected while the computer sleeps.

I am also trying to do some changes, however I have no improvement so far. Today the issue happened again. It is getting weird.

 

[Fishrrman]

Try turning off (or removing) AlDente.
Run without it for 3-4 days.
Does this change anything?

 

[GoztepeEge]

Try turning off (or removing) AlDente.
Run without it for 3-4 days.
Does this change anything?

I can give it a try. Thanks for the idea.

I believe this is going to be found out as smth with the AlDente, hence I just sent an e-mail to their support site.

We will see in a few days. If anyone also has the same issue, please leave a message here so we can compare what we use and how we can correlate something among us.

 

[GoztepeEge]

NEW INFO FYI:

I see some people here on other threads telling that they are experiencing the same issue as well.
Some people strongly highlighted that the problem always occur when an external monitor (either HDMI or USB-C) is left connected while the device goes into sleep mode. Some people are also telling that they no more have this crash issue after they tried the Monterey's new version (beta), so maybe we may have a solution in the next update soon.

Threads mentioned:
1) https://forums.macrumors.com/threads/macos-monterey-resume-from-sleep-issues.2327238/
2) https://forums.macrumors.com/threads/mac-pro-6-1-monterey-crashes-in-sleep.2319556/page-14

So now, I am first planning to leave my device in sleep while I plug-off the HDMI cable of my external display. (So far the HDMI cable was always left connected to the MBP)
We will see tomorrow if the crash happens again or not.

I am going to edit this thread again.

 

[vivid.gear71]

I was digging some MAC os crash issue related to aldente https://github.com/davidwernhart/AlDente/issues?q=is:issue+crash+is:closed and could not find concrete one happened this year.
Once Mac goes into sleep, there is not much 3rd party app can do.
If crash happens immediately when it goes to sleep, maybe it could be caused by 3rd party app but if crash happens sometime in the middle of sleeping then it should be OSX level issue

 

[GoztepeEge]

EDIT:

Yesterday I made a test on the MBP, I left it in sleep while the HDMI cable is not connected, today I had no restart problem.
I am going to do the same test tomorrow as well. It seems the problem is not AlDente, but probably the external screen-HDMI connection on the MBP.
But we will see in the next few days after a few more tests.

 

[GoztepeEge]

NEWS:

It seems the issue is not related to AlDente, but the HDMI connection.
I tested it again and noticed that the MBP does not restart itself during sleep if no HDMI cable is connected.
So I now started plugging off my external screen before I let the MBP to sleep.

This is the only workaround I found so far. I hope this can be resolved in a new update of the Monterey.

 

[Fishrrman]

Although you've found "a workaround that works for you", I would not put repeated wear-and-tear on the MBP's HDMI port by plugging/unplugging the cable there.

Instead, I'd try to find another way to "make/break" the connection when necessary to do so.

How I'd do it:
- get a short HDMI cable (male connector on both ends).
- get a cheap "HDMI switch" (one port on one side, two ports on the other side)
- connect it up: MBP ---> short HDMI ---> switchbox ---> existing HDMI ---> display.
Now, if I needed to "break-make" the HDMI connection, I'd just reach over and "flip the switch" on the switchbox one way to break it, then back to re-make it.

This way, no cable connections are fooled with, the switchbox does all the work and gets the wear-and-tear (and not the MBP).

 

[GoztepeEge]

Although you've found "a workaround that works for you", I would not put repeated wear-and-tear on the MBP's HDMI port by plugging/unplugging the cable there.

Instead, I'd try to find another way to "make/break" the connection when necessary to do so.

How I'd do it:
- get a short HDMI cable (male connector on both ends).
- get a cheap "HDMI switch" (one port on one side, two ports on the other side)
- connect it up: MBP ---> short HDMI ---> switchbox ---> existing HDMI ---> display.
Now, if I needed to "break-make" the HDMI connection, I'd just reach over and "flip the switch" on the switchbox one way to break it, then back to re-make it.

This way, no cable connections are fooled with, the switchbox does all the work and gets the wear-and-tear (and not the MBP).

You can be right, however I am not in the same thought.

It is because I experience this issue even though my external computer was off during whole night, but the HDMI was connected.
I mean, I expect that, it would not make any difference if you even use another switcher. Because the HDMI will be still connected at the end.

Using a switch and closing the external screen are the same thing, in my opinion. As long as there is no HDMI connection on the MBP, there exists no issue. I do not know why this is like that, however it is what it is.

Now I have two options:
1) Plugging off the HDMI cable before I put the MBP in sleep every night, or
2) Shutting down the MBP without touching the HDMI cable.

 

[GoztepeEge]

Today I had the same problem even though there was no HDMI connected.

Here is the kernel panic logs:

panic(cpu 1 caller 0xfffffe00108426bc): Wake transition timed out after 35 seconds while calling rootDomain's clients about completed rootDomain's state changes.
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 21D62
Kernel version: Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_ARM64_T6000
Fileset Kernelcache UUID: FA4EB485BA9DC1EBAA5D0E80232A48CC
Kernel UUID: BADF56F4-2876-3FF4-AC12-F25E78B09AA1
iBoot version: iBoot-7429.81.3
secure boot?: YES
Paniclog version: 13
KernelCache slide: 0x0000000008704000
KernelCache base: 0xfffffe000f708000
Kernel slide: 0x0000000008f38000
Kernel text base: 0xfffffe000ff3c000
Kernel text exec slide: 0x0000000009020000
Kernel text exec base: 0xfffffe0010024000
mach_absolute_time: 0x29937d835bb
Epoch Time: sec usec
Boot : 0x622462e0 0x000462fe
Sleep : 0x622b0c7f 0x0008b261
Wake : 0x622b0d39 0x000f2493
Calendar: 0x622b0d5d 0x00004c0f

Zone info:
Foreign : 0xfffffe0017b94000 - 0xfffffe0017ba8000
Native : 0xfffffe10002d0000 - 0xfffffe30002d0000
Readonly : 0xfffffe14ccf9c000 - 0xfffffe1666930000
Metadata : 0xfffffe6b6ce84000 - 0xfffffe6b78e28000
Bitmaps : 0xfffffe6b78e28000 - 0xfffffe6b7e9d8000
CORE 0 PVH locks held: None
CORE 1 PVH locks held: None
CORE 2 PVH locks held: None
CORE 3 PVH locks held: None
CORE 4 PVH locks held: None
CORE 5 PVH locks held: None
CORE 6 PVH locks held: None
CORE 7 PVH locks held: None
CORE 0: PC=0xfffffe00100aaf4c, LR=0xfffffe00100aaf4c, FP=0xfffffe60a5aa3ef0
CORE 1 is the one that panicked. Check the full backtrace for details.
CORE 2: PC=0xfffffe00100aaf50, LR=0xfffffe00100aaf4c, FP=0xfffffe60393abef0
CORE 3: PC=0xfffffe00100aaf50, LR=0xfffffe00100aaf4c, FP=0xfffffe609c9f3ef0
CORE 4: PC=0xfffffe00100aaf50, LR=0xfffffe00100aaf4c, FP=0xfffffe600c633ef0
CORE 5: PC=0xfffffe00100aaf4c, LR=0xfffffe00100aaf4c, FP=0xfffffe60b724bef0
CORE 6: PC=0xfffffe00100aaf4c, LR=0xfffffe00100aaf4c, FP=0xfffffe60b7e1bef0
CORE 7: PC=0xfffffe00100aaf4c, LR=0xfffffe00100aaf4c, FP=0xfffffe6098ef3ef0
Panicked task 0xfffffe20003f0678: 0 pages, 557 threads: pid 0: kernel_task
Panicked thread: 0xfffffe1b34ed9860, backtrace: 0xfffffe6017b4b3e0, tid: 948082
lr: 0xfffffe00100764e8 fp: 0xfffffe6017b4b450
lr: 0xfffffe00100761b8 fp: 0xfffffe6017b4b4c0
lr: 0xfffffe00101b62bc fp: 0xfffffe6017b4b4e0
lr: 0xfffffe00101a86c8 fp: 0xfffffe6017b4b560
lr: 0xfffffe00101a6118 fp: 0xfffffe6017b4b620
lr: 0xfffffe001002b7f8 fp: 0xfffffe6017b4b630
lr: 0xfffffe0010075e2c fp: 0xfffffe6017b4b9d0
lr: 0xfffffe0010075e2c fp: 0xfffffe6017b4ba40
lr: 0xfffffe00108897a0 fp: 0xfffffe6017b4ba60
lr: 0xfffffe00108426bc fp: 0xfffffe6017b4bd80
lr: 0xfffffe001078a748 fp: 0xfffffe6017b4bdb0
lr: 0xfffffe00100c7ab4 fp: 0xfffffe6017b4be30
lr: 0xfffffe00100c8b08 fp: 0xfffffe6017b4bf20
lr: 0xfffffe0010034e78 fp: 0x0000000000000000

last started kext at 1622340029944: com.apple.driver.usb.cdc.ncm 5.0.0 (addr 0xfffffe000fb790b0, size 5071)
loaded kexts:
com.paragon-software.filesystems.ntfs 328.9.15
com.apple.macos.driver.AppleUSBEthernetHost 8.1.1
com.apple.iokit.SCSITaskUserClient 452.60.2
com.apple.filesystems.smbfs 4.0
com.apple.filesystems.autofs 3.0
com.apple.fileutil 20.036.15
com.apple.driver.AppleBluetoothMultitouch 100
com.apple.driver.AppleTopCaseHIDEventDriver 5020.1
com.apple.driver.AppleBiometricServices 1
com.apple.driver.CoreKDL 1
com.apple.driver.SEPHibernation 1
com.apple.driver.BCMWLANFirmware4387.Hashstore 1
com.apple.driver.DiskImages.ReadWriteDiskImage 493.0.0
com.apple.driver.DiskImages.UDIFDiskImage 493.0.0
com.apple.driver.DiskImages.RAMBackingStore 493.0.0
com.apple.driver.DiskImages.FileBackingStore 493.0.0
com.apple.filesystems.apfs 1933.80.3
com.apple.driver.AppleUSBDeviceNCM 5.0.0
com.apple.driver.AppleThunderboltIP 4.0.3
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.nke.l2tp 1.9
com.apple.filesystems.tmpfs 1
com.apple.filesystems.lifs 1
com.apple.IOTextEncryptionFamily 1.0.0
com.apple.filesystems.hfs.kext 582.60.2
com.apple.security.BootPolicy 1
com.apple.BootCache 40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleEmbeddedSimpleSPINORFlasher 1
com.apple.driver.AppleSmartIO2 1
com.apple.driver.AppleSN012776Amp 530.2
com.apple.driver.ApplePMP 1
com.apple.driver.AppleCS42L84Audio 530.2
com.apple.driver.AppleT6000SOCTuner 1
com.apple.driver.AppleT6000CLPCv3 1
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleALSColorSensor 1.0.0d1
com.apple.driver.AppleAOPVoiceTrigger 100.1
com.apple.driver.ApplePMPFirmware 1
com.apple.driver.AppleM68Buttons 1.0.0d1
com.apple.driver.AppleProResHW 128.2.0
com.apple.driver.AppleJPEGDriver 4.7.9
com.apple.driver.AppleAVE2 530.3.0
com.apple.driver.AppleAVD 555
com.apple.AGXG13X 188.10
com.apple.driver.AppleSDXC 3.1.1
com.apple.driver.AppleSamsungSerial 1.0.0d1
com.apple.driver.AppleSerialShim 1
com.apple.driver.AppleMobileDispT600X-DCP 140.0
com.apple.driver.AppleSPMIPMU 1.0.1
com.apple.driver.usb.AppleSynopsysUSB40XHCI 1
com.apple.driver.AppleMCDP29XXUpdateSupport 1
com.apple.driver.AppleDPDisplayTCON 1
com.apple.driver.AppleEventLogHandler 1
com.apple.driver.AppleS5L8960XNCO 1
com.apple.driver.AppleT6000PMGR 1
com.apple.driver.AppleS8000AES 1
com.apple.driver.AppleS8000DWI 1.0.0d1
com.apple.driver.AppleInterruptControllerV2 1.0.0d1
com.apple.driver.AppleT8110DART 1
com.apple.driver.AppleBluetoothModule 1
com.apple.driver.AppleBCMWLANBusInterfacePCIe 1
com.apple.driver.AppleS5L8920XPWM 1.0.0d1
com.apple.driver.AudioDMAController-T600x 100.51
com.apple.driver.AppleT6000DART 1
com.apple.driver.AppleSPIMC 1
com.apple.driver.AppleS5L8940XI2C 1.0.0d2
com.apple.driver.AppleT6000 1
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.driver.usb.AppleUSBUserHCI 1
com.apple.iokit.IOKitRegistryCompatibility 1
com.apple.iokit.EndpointSecurity 1
com.apple.driver.AppleDiskImages2 126.60.3
com.apple.AppleSystemPolicy 2.0.0
com.apple.nke.applicationfirewall 402
com.apple.kec.InvalidateHmac 1
com.apple.kec.AppleEncryptedArchive 1
com.apple.driver.usb.cdc.ncm 5.0.0
com.apple.driver.usb.cdc.ecm 5.0.0
com.apple.driver.usb.cdc.acm 5.0.0
com.apple.driver.usb.serial 6.0.0
com.apple.driver.AppleUSBMergeNub 900.4.2
com.apple.driver.usb.cdc 5.0.0
com.apple.driver.AppleUSBAudio 414.7
com.apple.iokit.IOAudioFamily 300.10
com.apple.vecLib.kext 1.2.0
com.apple.driver.driverkit.serial 6.0.0
com.apple.kext.triggers 1.0
com.apple.iokit.IOAVBFamily 1010.2
com.apple.plugin.IOgPTPPlugin 1000.11
com.apple.iokit.IOEthernetAVBController 1.1.0
com.apple.driver.AppleHSBluetoothDriver 5020.1
com.apple.driver.IOBluetoothHIDDriver 9.0.0
com.apple.driver.AppleActuatorDriver 5430.21
com.apple.driver.AppleMultitouchDriver 5430.21
com.apple.driver.AppleHIDKeyboard 228
com.apple.driver.AppleMesaSEPDriver 100.99
com.apple.iokit.IOBiometricFamily 1
com.apple.driver.AppleSEPHDCPManager 1.0.1
com.apple.driver.AppleTrustedAccessory 1
com.apple.iokit.AppleSEPGenericTransfer 1
com.apple.driver.DiskImages.KernelBacked 493.0.0
com.apple.driver.AppleXsanScheme 3
com.apple.driver.usb.networking 5.0.0
com.apple.driver.AppleThunderboltUSBDownAdapter 1.0.4
com.apple.driver.AppleThunderboltDPInAdapter 8.5.1
com.apple.driver.AppleThunderboltDPAdapterFamily 8.5.1
com.apple.driver.AppleThunderboltPCIDownAdapter 4.1.1
com.apple.nke.ppp 1.9
com.apple.driver.AppleBSDKextStarter 3
com.apple.driver.AppleHIDTransportSPI 5400.30
com.apple.driver.AppleHIDTransport 5400.30
com.apple.driver.AppleInputDeviceSupport 5400.30
com.apple.filesystems.hfs.encodings.kext 1
com.apple.driver.AppleBTM 1.0.1
com.apple.driver.AppleConvergedIPCOLYBTControl 1
com.apple.driver.AppleConvergedPCI 1
com.apple.driver.AppleBluetoothDebug 1
com.apple.driver.AppleDCPDPTXProxy 1.0.0
com.apple.driver.DCPDPFamilyProxy 1
com.apple.driver.AppleCSEmbeddedAudio 530.2
com.apple.driver.AppleDiagnosticDataAccessReadOnly 1.0.0
com.apple.driver.ApplePassthroughPPM 3.0
com.apple.driver.AppleAOPAudio 102.2
com.apple.driver.AppleEmbeddedAudio 530.2
com.apple.iokit.AppleARMIISAudio 100.1
com.apple.driver.AppleSPU 1
com.apple.AGXFirmwareKextG13XRTBuddy 188.10
com.apple.AGXFirmwareKextRTBuddy64 188.10
com.apple.driver.DCPAVFamilyProxy 1
com.apple.iokit.IOGPUFamily 35.11
com.apple.iokit.IONVMeFamily 2.1.0
com.apple.driver.AppleNANDConfigAccess 1.0.0
com.apple.driver.AppleStockholmControl 1.0.0
com.apple.iokit.IOMobileGraphicsFamily-DCP 343.0.0
com.apple.driver.AppleDCP 1
com.apple.driver.AppleFirmwareKit 1
com.apple.iokit.IOMobileGraphicsFamily 343.0.0
com.apple.driver.usb.AppleUSBHostPacketFilter 1.0
com.apple.driver.AppleDialogPMU 1.0.1
com.apple.driver.AppleSPMI 1.0.1
com.apple.driver.AppleUSBXDCIARM 1.0
com.apple.driver.AppleUSBXDCI 1.0
com.apple.iokit.IOUSBDeviceFamily 2.0.0
com.apple.driver.usb.AppleSynopsysUSBXHCI 1
com.apple.driver.usb.AppleUSBXHCI 1.2
com.apple.driver.AppleEmbeddedUSBHost 1
com.apple.driver.usb.AppleUSBHub 1.2
com.apple.driver.usb.AppleUSBHostCompositeDevice 1.2
com.apple.driver.AppleT6000TypeCPhy 1
com.apple.driver.AppleT8103TypeCPhy 1
com.apple.driver.AppleHPM 3.4.4
com.apple.driver.AppleSART 1
com.apple.driver.ApplePMGR 1
com.apple.driver.AppleARMWatchdogTimer 1
com.apple.driver.AppleDisplayCrossbar 1.0.0
com.apple.iokit.IODisplayPortFamily 1.0.0
com.apple.driver.AppleTypeCPhy 1
com.apple.driver.AppleThunderboltNHI 7.2.8
com.apple.driver.AppleT6000PCIeC 1
com.apple.iokit.IOThunderboltFamily 9.3.3
com.apple.driver.ApplePIODMA 1
com.apple.driver.AppleT600xPCIe 1
com.apple.driver.AppleMultiFunctionManager 1
com.apple.driver.AppleBluetoothDebugService 1
com.apple.driver.AppleBCMWLANCore 1.0.0
com.apple.iokit.IO80211Family 1200.12.2b1
com.apple.driver.IOImageLoader 1.0.0
com.apple.driver.AppleOLYHAL 1
com.apple.driver.corecapture 1.0.4
com.apple.driver.AppleEmbeddedPCIE 1
com.apple.driver.AppleMCA2-T600x 600.95
com.apple.driver.AppleEmbeddedAudioLibs 100.9.1
com.apple.driver.AppleFirmwareUpdateKext 1
com.apple.driver.AppleH13CameraInterface 4.87.0
com.apple.driver.AppleH10PearlCameraInterface 17.0.3
com.apple.driver.AppleGPIOICController 1.0.2
com.apple.driver.AppleFireStormErrorHandler 1
com.apple.driver.AppleMobileApNonce 1
com.apple.iokit.IOTimeSyncFamily 1000.11
com.apple.driver.DiskImages 493.0.0
com.apple.iokit.IOGraphicsFamily 593
com.apple.iokit.IOBluetoothSerialManager 9.0.0
com.apple.iokit.IOBluetoothHostControllerUSBTransport 9.0.0
com.apple.iokit.IOBluetoothHostControllerUARTTransport 9.0.0
com.apple.iokit.IOBluetoothHostControllerTransport 9.0.0
com.apple.driver.IOBluetoothHostControllerPCIeTransport 9.0.0
com.apple.iokit.IOBluetoothFamily 9.0.0
com.apple.driver.FairPlayIOKit 68.13.1
com.apple.iokit.CSRBluetoothHostControllerUSBTransport 9.0.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 9.0.0
com.apple.driver.AppleSSE 1.0
com.apple.driver.AppleSEPKeyStore 2
com.apple.driver.AppleUSBTDM 532.40.7
com.apple.iokit.IOUSBMassStorageDriver 209.40.6
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOSCSIBlockCommandsDevice 452.60.2
com.apple.iokit.IOSCSIArchitectureModelFamily 452.60.2
com.apple.driver.AppleIPAppender 1.0
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleEffaceableStorage 1.0
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.KernelRelayHost 1
com.apple.iokit.IOUSBHostFamily 1.2
com.apple.driver.AppleUSBHostMergeProperties 1.2
com.apple.driver.usb.AppleUSBCommon 1.0
com.apple.driver.AppleSMC 3.1.9
com.apple.driver.RTBuddy 1.0.0
com.apple.driver.AppleEmbeddedTempSensor 1.0.0
com.apple.driver.AppleARMPMU 1.0
com.apple.iokit.IOAccessoryManager 1.0.0
com.apple.driver.AppleOnboardSerial 1.0
com.apple.iokit.IOSkywalkFamily 1.0
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.iokit.IONetworkingFamily 3.4
com.apple.iokit.IOSerialFamily 11
com.apple.driver.AppleSEPManager 1.0.1
com.apple.driver.AppleA7IOP 1.0.2
com.apple.driver.IOSlaveProcessor 1
com.apple.driver.AppleBiometricSensor 2
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.CoreAnalyticsFamily 1
com.apple.driver.AppleANELoadBalancer 5.35.2
com.apple.driver.AppleH11ANEInterface 5.35.0
com.apple.AUC 1.0
com.apple.iokit.IOAVFamily 1.0.0
com.apple.iokit.IOHDCPFamily 1.0.0
com.apple.iokit.IOCECFamily 1
com.apple.iokit.IOAudio2Family 1.0
com.apple.driver.AppleIISController 100.1
com.apple.driver.AppleAudioClockLibs 100.9.1
com.apple.driver.AppleM2ScalerCSCDriver 265.0.0
com.apple.iokit.IOSurface 302.11.1
com.apple.driver.IODARTFamily 1
com.apple.security.quarantine 4
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.security.AppleImage4 4.2.0
com.apple.kext.CoreTrust 1
com.apple.iokit.IOCryptoAcceleratorFamily 1.0.1
com.apple.driver.AppleARMPlatform 1.0.2
com.apple.iokit.IOStorageFamily 2.1
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.iokit.IOReportFamily 47
com.apple.kec.pthread 1
com.apple.kec.Libm 1
com.apple.kec.corecrypto 12.0



** Stackshot Succeeded ** Bytes Traced 429919 (Uncompressed 1072080) **

 

[vivid.gear71]

are you still seeing issue even after updating to OSX 12.3 ?

 

[billwheaton]

Well, misery loves company, so here goes:
I have had this same problem starting on 2022-03-18 and once again on 2022-03-19 (today).
I have

• MacBook Pro (16-inch, 2021) that I got on 2021-12-28
• 16GB mem, 1TB SD APFS encrypted
• Monterey 12.3 upgraded last week.
• Monitor is a 34" ultrawide LG with the thunderbolt powered usbc-3 output that I connect to my MBP to power it so that I don't use the apple power brick. ( I don't use DP or HDMI either, just the thunderbolt for video/power, which why I got it - one less cable.)
• Two external Western Digital Passport SSDs - one with 1TB for Time Machine and a 2TB one for abundance.
• Logitech MX Keys and MX Master mouse.
• FFine USB microphone connected to one of the usb ports on the back of the LG ultrawide.
• Logitech Speakers that I recently moved from the LG headphone port to the MBP headphone port
• ATT Uverse NVG599 router,
• HP LaserJet printer

The MBP is normally closed and located under the monitor stand.
I have noticed that if I let the screen turn off (I guess the mbp is sleeping) that when I return to wake it up by hitting the enter key on my keyboard, that it takes a long time to respond. And when it does, it displays the login screen in the lower left 1/3 of the LG, and it will not respond to entering my password. If I hit escape it goes away, and then when I hit enter again, it fills the whole LG screen with the login and I can enter my password and everything behaves normally.

It has been doing that for at least a month now - maybe even since the beginning of February. It has seemingly taken longer and longer to respond.

About a week or so ago - maybe March 10 - I began by turning off as many notifications as I could find that display on the login screen, thinking that maybe it was getting stuck on them before I logged in and while that seemed to help a little, I was just thrilled that I wasn't getting hit with pointless notifications anymore, so maybe it didn't really help much - hard to say...

Yesterday was the first time I had the panic error that begins with:
panic(cpu 1 caller 0xfffffe00108426bc): Wake transition timed out after 35 seconds while calling rootDomain's clients about completed rootDomain's state changes.

Then I read that if you restart it in safe-mode, that it might clear some caches or something and clear out accumulated snot, so I tried that. It did speed up the next couple of reboots, and after it went to sleep it might have sped up a little, but really it was not substancially different than it was before. I still have the unresponsive login on the lower left 1/3 of the LG when I first wake it up throughout the day. When I left it last night, I specifically put it to sleep with the Command-Option-Eject key-chord.

And then this morning, it had restarted and showed me the same log again.

I too will try several things and report back.

 

[polaris20]

I’m having this issue on a M1 Mini now. Started with 12.3. Not pleased.

 

[Chevysales]

Hello everyone!

I am currently using a 2021 MBP 14" base model for the last 3 months. I am happy with it, however I noticed a weird issue happening in the last 3 nights while I put my computer in a sleep mode.

Here is what I did in this last 3 days:
at night, I stopped working, I plugged off the charger cable, closed the lid. The device (I guess) gets into sleep mode.
- Open applications before closing the lid: Safari, Mail, Spotify
- Charge level before closing the lid: 50%
- HDMI cable of the external display stays connected (external display is closed as well as the MBP)
- MacOS Monterey 12.2.1 (currently the latest OS version)

The next day when I open the lid, it directly asks me to type password instead of having the ability to enter it via TouchID. It is because the computer restarts itself. When I enter the password, it opens the desktop, and a warning appears like "your computer has been restarted due to a problem" and buttons e.g. "report it to Apple".

Now I am curious what is happening, and what causes this?
Does anyone have any idea regarding this?

same thing was happening for a while with our 2019 16" Intels... it was fixed in software as I did nothing and it stopped after an update.

searching forum here should find you the long thread.

good luck

 

[polaris20]

Mine flat out crashed mid-app, and restarted. WTF?

So this afternoon, I ended up completely reformatting the machine, and loading MacOS from scratch. Really friggin' annoying, but we'll see what happens.

 

[brosenz]

I can give it a try. Thanks for the idea.

I believe this is going to be found out as smth with the AlDente, hence I just sent an e-mail to their support site.

We will see in a few days. If anyone also has the same issue, please leave a message here so we can compare what we use and how we can correlate something among us.

Did you get any feedback from AlDente tech support?

 

[polaris20]

Actually got a USB stick, created the media, then went back to the latest version of Big Sur. So far, no issues. Definitely a funky software thing on 12.3.

 

[billwheaton]

Well, misery loves company, so here goes:
I have had this same problem starting on 2022-03-18 and once again on 2022-03-19 (today).
I have <snip>

I have not had another incident of this yet.

However, I have begun to inconisistently turn my monitor off before sleeping my machine. And that may help.

But I am a lazy programmer, and I don't like that.

 

[billwheaton]

Actually got a USB stick, created the media, then went back to the latest version of Big Sur. So far, no issues. Definitely a funky software thing on 12.3.

I wonder if you now upgraded to 12.3 if it would magically be okay. Stepping back to BigSur and forward again might be the answer.

 

[polaris20]

I wonder if you now upgraded to 12.3 if it would magically be okay. Stepping back to BigSur and forward again might be the answer.

Maybe. But honestly I think I'll just wait awhile, to see if there's an update that specifically mentions it, or a 12.4, or something. There's really nothing in Monterey that I even care about, when compared to Big Sur.