M1 Max crashing after upgrading to Monterey 12.3

Question

Level 1

9 points

M1 Max crashing after upgrading to Monterey 12.3

Hi,

I've updated to Monterey 12.3 and ever since I'm getting kernel panic's.

See attached log below:

Panicked task 0xfffffe166696c0b0: 12105 pages, 7 threads: pid 478: backupd
      Kernel Extensions in backtrace:
         com.apple.driver.AppleT6000CLPCv3(1.0)[BD886B9D-9B09-3751-9FDD-8842CBFDE8C9]@0xfffffe0015a7c700->0xfffffe0015abaae7
            dependency: com.apple.driver.AppleARMPlatform(1.0.2)[C17D52A2-9028-37D3-9011-E084C00F96C9]@0xfffffe0014e16750->0xfffffe0014e60d97
            dependency: com.apple.driver.ApplePMGR(1)[2A9D8822-7355-301C-92E1-1BC548794C21]@0xfffffe00157e3350->0xfffffe001582364f
            dependency: com.apple.iokit.IOReportFamily(47)[BD0867F7-DE61-3E4D-ABBE-25CBAD925319]@0xfffffe0016779cf0->0xfffffe001677cd13
            dependency: com.apple.iokit.IOSurface(302.14)[0AADF5BB-8A38-3FC1-BB0D-1A397EE4B16A]@0xfffffe0016858630->0xfffffe0016878ce7
            dependency: com.apple.kec.Libm(1)[744860C4-5A98-3232-9D03-B10D27F164D1]@0xfffffe0016d13e00->0xfffffe0016d17517
         com.apple.filesystems.apfs(1934.101.3)[B696CC0F-264F-384A-AFAE-7D18CDD1509D]@0xfffffe0016e9a530->0xfffffe0016fd0543
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[E43272B6-E721-3B3D-A814-AE6B62A579EA]@0xfffffe001536c510->0xfffffe001537162b
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[8DEC227B-5503-3D49-8BE1-24A919276F2A]@0xfffffe0015df63e0->0xfffffe0015dfc2a3
            dependency: com.apple.iokit.IOStorageFamily(2.1)[0E7F6B6D-FCD2-3154-8BAB-6C010A0217BF]@0xfffffe0016833ba0->0xfffffe0016854753
            dependency: com.apple.kec.corecrypto(12.0)[10DF8078-222D-3E6D-9690-E225E8445BF6]@0xfffffe0017006b40->0xfffffe00170532c7
         com.apple.nke.asp_tcp(8.2.1)[13A56900-A604-3936-8CF2-C4636ADD65EA]@0xfffffe0016fd0550->0xfffffe0016fd8e17
         com.apple.filesystems.afpfs(11.3.1)[98614AD9-1216-344A-BFBF-8F4519F15199]@0xfffffe0016e60be0->0xfffffe0016e9a527
            dependency: com.apple.filesystems.hfs.encodings.kext(1)[DF56C990-FAB9-3142-A63D-5A91FB07B4FA]@0xfffffe0016046c00->0xfffffe0016047b2f
            dependency: com.apple.security.SecureRemotePassword(1.0)[79A95889-FDB6-3232-AE7E-2E0B7908F855]@0xfffffe00159b4430->0xfffffe00159be363

From my understanding backupd is being launched by TimeCapsule (which I'm using). I've just disabled the TC backup mechanism and seems the OS is stable now. I was wondering if this is a known bug?

Thanks in advance..

MacBook Pro 15″, macOS 11.6

Posted on Mar 17, 2022 11:14 AM

Reply

Answer 1

Top-ranking reply

johanfromzoetemeer

Level 1

0 points

Apr 13, 2022 2:37 AM in response to YOUR1

I moved my encrypted backup somewhere else and i am now running a new un-encrypted backup. No crashes so far, seems to run fine now. So the issues appears, as the previous posters suggested' to be in accessing an encrypted backup.

For the personal laptop i'm backing-up now encryption is important but not critical, but for my work-laptop it is essential. I'm a security consultant and keep confidential customer information on my laptop. I need to be able to encrypt my backups; for security reasons, but also per contractual obligation.

My choices are now;

Not updating to 12.3.1. and leaving two critical security vulnerabilities wide open, which is not acceptable security wise
Updating but not making backups, which is not acceptable in a work environment
Updating and making un-encrypted backups, which is not acceptable security wise and per contractual obligation

Please Apple, look into this and fix it.

Reply

Answer 2

Apr 14, 2022 6:42 AM in response to Luis Sequeira1

Would you be so kind as take another look at this? The issue appear to be encryption on time capsule backups. When you turn encryption off, the problem goes away. I do however need encrypted backups...

Reply