2019 MacBook Pro Panic
panic(cpu 0 caller 0xfffffff017ec5948): userspace watchdog timeout: no successful checkins from dfrd (2 induced crashes) in 180 seconds dfrd has not exited since first loaded
My 2019 MBP w TouchBar boots up for a couple minutes, makes a loud fan noise and then reboots. The crash log spits out these errors.
panic(cpu 0 caller 0xfffffff017ec5948): userspace watchdog timeout: no successful checkins from dfrd (2 induced crashes) in 180 seconds
dfrd has not exited since first loaded
service: dfrd (2 induced crashes), total successful checkins in 220 seconds: 4, last successful checkin: 180 seconds ago
service: remoted, total successful checkins in 210 seconds: 21, last successful checkin: 0 seconds ago
service: bridgeaudiod, total successful checkins in 220 seconds: 22, last successful checkin: 0 seconds ago
service: logd, total successful checkins in 220 seconds: 21, last successful checkin: 0 seconds agoDebugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 21P2057
macOS version: 23C71
Kernel version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:09:28 PST 2023; root:xnu-10002.61.3~1/RELEASE_ARM64_T8010
KernelCache UUID: 3ABF1CAE467593B1DC6EA0674E50332B
Kernel UUID: 1D1BC1F4-12F1-3532-B69F-61F6683CEB7C
Boot session UUID: 74C42092-2522-47A7-AA6C-9F356F82207C
iBoot version: iBoot-10151.61.4
secure boot?: YES
roots installed: 0
x86 EFI Boot State: 0xd
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0xec
x86 Previous Power Transitions: 0x70707060400
PCIeUp link state: 0x1614
macOS kernel slide: 0x1e600000
Paniclog version: 14
Kernel slide: 0x00000000111b0000
Kernel text base: 0xfffffff0181b4000
mach_absolute_time: 0x13b61fa20
Epoch Time: sec usec
Boot : 0x66bcaed1 0x000b58ee
Sleep : 0x00000000 0x00000000
Wake : 0x00000000 0x00000000
Calendar: 0x66bcafa9 0x000608f7Zone info:
Zone map: 0xffffffdc06588000 - 0xffffffe206588000
. VM : 0xffffffdc06588000 - 0xffffffdcecbec000
. RO : 0xffffffdcecbec000 - 0xffffffdd398b8000
. GEN0 : 0xffffffdd398b8000 - 0xffffffde1ff1c000
. GEN1 : 0xffffffde1ff1c000 - 0xffffffdf06580000
. GEN2 : 0xffffffdf06580000 - 0xffffffdfecbe8000
. GEN3 : 0xffffffdfecbe8000 - 0xffffffe0d3250000
. DATA : 0xffffffe0d3250000 - 0xffffffe206588000
Metadata: 0xffffffe217640000 - 0xffffffe218e40000
Bitmaps : 0xffffffe218e40000 - 0xffffffe218f64000
Extra : 0 - 0TPIDRx_ELy = {1: 0xffffffdfed57eba8 0: 0x0000000000000000 0ro: 0x000000016b6570e0 }
CORE 0 is the one that panicked. Check the full backtrace for details.
CORE 1: PC=0xfffffff0183df008, LR=0xfffffff0183df008, FP=0xffffffeff4157ef0
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Total cpu_usage: 2932478
Thread task pri cpu_usage
0xffffffdfed57eba8 watchdogd 97 0
0xffffffdfecf5aba8 kernel_task 0 33667
0xffffffdfecc802f8 kernel_task 0 29470Panicked task 0xffffffdfecc49190: 173 pages, 3 threads: pid 38: watchdogd
Panicked thread: 0xffffffdfed57eba8, backtrace: 0xffffffeff40670b0, tid: 922
lr: 0xfffffff0183aea90 fp: 0xffffffeff4067120
lr: 0xfffffff0184dd07c fp: 0xffffffeff4067190
lr: 0xfffffff0184dc0b0 fp: 0xffffffeff40672b0
lr: 0xfffffff018371630 fp: 0xffffffeff40672c0
lr: 0xfffffff0183ae4cc fp: 0xffffffeff4067670
lr: 0xfffffff018a2cc58 fp: 0xffffffeff4067690
lr: 0xfffffff017ec5948 fp: 0xffffffeff40676b0
lr: 0xfffffff017ec5090 fp: 0xffffffeff40676d0
lr: 0xfffffff017ec41ec fp: 0xffffffeff40677f0
lr: 0xfffffff0189b8684 fp: 0xffffffeff4067830
lr: 0xfffffff0189b8a28 fp: 0xffffffeff40679d0
lr: 0xfffffff0184aaa4c fp: 0xffffffeff4067af0
lr: 0xfffffff0183b434c fp: 0xffffffeff4067b90
lr: 0xfffffff01838c8ec fp: 0xffffffeff4067bf0
lr: 0xfffffff0183a170c fp: 0xffffffeff4067d20
lr: 0xfffffff0184d2eb0 fp: 0xffffffeff4067df0
lr: 0xfffffff0184dc43c fp: 0xffffffeff4067f10
lr: 0xfffffff018371630 fp: 0xffffffeff4067f20
From what I understand, it is a result of the touch bar not loading in which causes the entire system to crash. Is there a way to fix this? Are there any terminal commands that can stop the touch bar from loading in or disable it?
I have maintained my MBP pretty well without any known damage.
[Edited by Moderator]
