I’ve been getting “Your computer was restarted because of a problem” errors like this lately:
panic(cpu 0 caller 0xfffffff01e07db08): macOS watchdog detected
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 20P3045
macOS version: 22D68
Kernel version: Darwin Kernel Version 22.3.0: Thu Jan 5 20:17:53 PST 2023; root:xnu-8792.81.2~1/RELEASE_ARM64_T8010
KernelCache UUID: 66D3D9EAC3796DA60EBA5A1BCB588E81
Kernel UUID: A133ECF3-E2EF-3DEA-8A4C-D21463BB0B0D
Boot session UUID: 2D1ABF32-DA0B-4CF2-B82F-BF811BD8C2B3
iBoot version: iBoot-8419.80.7
secure boot?: YES
roots installed: 0
x86 EFI Boot State: 0x16
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0x5
x86 Previous Power Transitions: 0x405060400
PCIeUp link state: 0x89271614
macOS kernel slide: 0x18600000
Paniclog version: 14
Kernel slide: 0x0000000017d2c000
Kernel text base: 0xfffffff01ed30000
mach_absolute_time: 0x7ce0fb8cd1
Epoch Time: sec usec
Boot : 0x640a4370 0x0003d4f9
Sleep : 0x640a7276 0x000d9fc2
Wake : 0x640ab429 0x000d7b2c
Calendar: 0x640add0e 0x00007068
Zone info:
Zone map: 0xffffffdc07cc0000 - 0xffffffe207cc0000
. VM : 0xffffffdc07cc0000 - 0xffffffdcee324000
. RO : 0xffffffdcee324000 - 0xffffffdd3aff0000
. GEN0 : 0xffffffdd3aff0000 - 0xffffffde21654000
. GEN1 : 0xffffffde21654000 - 0xffffffdf07cb8000
. GEN2 : 0xffffffdf07cb8000 - 0xffffffdfee320000
. GEN3 : 0xffffffdfee320000 - 0xffffffe0d4988000
. DATA : 0xffffffe0d4988000 - 0xffffffe207cc0000
Metadata: 0xffffffdc00234000 - 0xffffffdc01a34000
Bitmaps : 0xffffffdc01a34000 - 0xffffffdc01c68000
TPIDRx_ELy = {1: 0xffffffdf076d5088 0: 0x0000000000000000 0ro: 0x0000000000000000 }
CORE 0 is the one that panicked. Check the full backtrace for details.
CORE 1: PC=0xfffffff01ef4e848, LR=0xfffffff01ef4e848, FP=0xffffffeac9fdbf00
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Panicked task 0xffffffde216bd638: 0 pages, 223 threads: pid 0: kernel_task
Panicked thread: 0xffffffdf076d5088, backtrace: 0xffffffec820176c0, tid: 378
lr: 0xfffffff01ef1d44c fp: 0xffffffec82017700
lr: 0xfffffff01ef1d25c fp: 0xffffffec82017770
lr: 0xfffffff01f053220 fp: 0xffffffec820177e0
lr: 0xfffffff01f0521b8 fp: 0xffffffec820178a0
lr: 0xfffffff01eedd5fc fp: 0xffffffec820178b0
lr: 0xfffffff01ef1ccd0 fp: 0xffffffec82017c60
lr: 0xfffffff01f5c6c1c fp: 0xffffffec82017c80
lr: 0xfffffff01e07db08 fp: 0xffffffec82017cb0
lr: 0xfffffff01e065604 fp: 0xffffffec82017d10
lr: 0xfffffff01e06eac8 fp: 0xffffffec82017d60
lr: 0xfffffff01e067b58 fp: 0xffffffec82017e00
lr: 0xfffffff01e064b94 fp: 0xffffffec82017e70
lr: 0xfffffff01de81b40 fp: 0xffffffec82017ea0
lr: 0xfffffff01f51205c fp: 0xffffffec82017ee0
lr: 0xfffffff01f5118b4 fp: 0xffffffec82017f20
lr: 0xfffffff01eee86c0 fp: 0x0000000000000000
That only gives you part of the story. The next step was to look at the Log Reports in Console for reports like panic-full-2023-03-10-073243.0003.ips
.
{"roots_installed":0,"caused_by":"macos","macos_version":"Mac OS X 13.2.1 (22D68)","os_version":"Bridge OS 7.2 (20P3045)","macos_system_state":"running","incident_id":"2D1ABF32-DA0B-4CF2-B82F-BF811BD8C2B3","bridgeos_roots_installed":0,"bug_type":"210","timestamp":"2023-03-10 07:32:43.00 +0000"}
{
"build" : "Bridge OS 7.2 (20P3045)",
"product" : "iBridge2,3",
"socId" : "0x00008012",
"kernel" : "Darwin Kernel Version 22.3.0: Thu Jan 5 20:17:53 PST 2023; root:xnu-8792.81.2~1\/RELEASE_ARM64_T8010",
"incident" : "2D1ABF32-DA0B-4CF2-B82F-BF811BD8C2B3",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2023-03-10 07:32:43.90 +0000",
"panicString" : <REMOVED FOR BREVITY>,
"panicFlags" : "0x902",
"bug_type" : "210",
"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 37852 (Uncompressed 115568) **\n",
"macOSPanicFlags" : "0x0",
"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",
"memoryStatus": <REMOVED FOR BREVITY>,
"binaryImages": <REMOVED FOR BREVITY>,
"processById": <REMOVED FOR BREVITY>
Note that Bridge OS is failing, indicating a Touch Bar issue. I found this SO post suggesting a cron script that restarts the touch bar every 3 minutes.
*/3 * * * * /usr/bin/pkill "Touch Bar agent" &>/dev/null; /usr/bin/killall "ControlStrip" &>/dev/null;
Edit your crontab with crontab -e
then copy and paste that in. It’s not the cleanest solution, but if it gets the job done, I don’t really care.
I’m testing it now to see if it works…