Continuous panic crashes on MBP 2019 13"

Question

Level 1

5 points

Continuous panic crashes on MBP 2019 13"

My MBP 2019 13" crashes everyday randomly when it sleeps/wakes (sometimes even when it's on). The touchbar didn't work after the crashes so I took it to Apple and they replaced touchbar+battery+keyboard but didn't solve it.

They recommended to do a factory reset and not use the backup copy. I used it for a day or two and the problem was still there. The the touchbar now works after the crashes, but I still get them. Sometimes the laptop won't even start after shutting it off (it looks dead but works after 1-2hrs).

It certainly is not a software issue and I am reading in forums that many people are having this same issue.

What is the solution that Apple offers to this malfunctioning?

errors (watchdog timeout & sleep/wake hang)

MacBook Pro 13″, macOS 12.1

Posted on Jan 24, 2022 9:26 AM

Reply

Answer 1

Best reply

Grant Bennet-Alder

Level 10

127,513 points

Jan 24, 2022 10:05 AM in response to plagisbert

That is the report of a possible hardware problem.

dfrd is the 'dynamic function row daemon', ie. the system daemon that talks to the touch bar.

It has not been heard from in far too long, which produces a kernel panic.

You should also consider disabling PowerNap features (unless you desperately need them) as they have also been troublesome.

Reply

Answer 2

plagisbert Author

Level 1

5 points

Jan 24, 2022 12:39 PM in response to Grant Bennet-Alder

Thanks for your response, Grant!

I just disabled Power Nap, it's a useful feature but I can definitely live without it. I will pay attention during the following days to see if it helps.

If it doesn't what would you recommend me to do, since the Macbook is from 2020 and is not covered by regular warranty?

Reply

Answer 3

plagisbert Author

Level 1

5 points

Jan 25, 2022 8:58 AM in response to Grant Bennet-Alder

Hi Grant,

My MBP just restarted while I was using it in a call and I got the report hereunder. This one is different... any ideas?

panic(cpu 1 caller 0xfffffff00d102350): "virtual IOReturn ADPParamFIFO::programFIFO(IOMemoryMap *): ADP FIFO still busy after 1000ms" @ADPParamFIFO.cpp:265

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 19P647

macOS version: 21C52

Kernel version: Darwin Kernel Version 21.2.0: Sun Nov 28 20:41:46 PST 2021; root:xnu-8019.61.5~2/RELEASE_ARM64_T8010

Kernel UUID: 096BFE9E-1498-32D9-A90D-40F573034F7C

iBoot version: iBoot-7429.61.2

secure boot?: YES

x86 EFI Boot State: 0xd

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x5

x86 Previous Power Transitions: 0x10001000100

PCIeUp link state: 0x89473614

Paniclog version: 13

Kernel slide: 0x0000000004904000

Kernel text base: 0xfffffff00b908000

mach_absolute_time: 0xd743c0354c

Epoch Time: sec usec

Boot : 0x61eed9a2 0x00048c3e

Sleep : 0x61f00a96 0x00053466

Wake : 0x61f00d71 0x0008006a

Calendar: 0x61f02b46 0x000d74a5

Zone info:

Foreign : 0xfffffff0741bc000 - 0xfffffff0741cc000

Native : 0xffffffe0007bc000 - 0xffffffe6007bc000

Readonly : 0xffffffe0e6e20000 - 0xffffffe133ae4000

Metadata : 0xffffffeb00bcc000 - 0xffffffeb04d9c000

Bitmaps : 0xffffffeb023cc000 - 0xffffffeb02648000

CORE 0: PC=0x00000001ae8a4424, LR=0x0000000104251e08, FP=0x000000016bddc550

CORE 1 is the one that panicked. Check the full backtrace for details.

Panicked task 0xffffffe21a214000: 423 pages, 3 threads: pid 48: dfrd

Panicked thread: 0xffffffe133ff86f8, backtrace: 0xffffffeb04242a40, tid: 27252

lr: 0xfffffff00c0fb6b4 fp: 0xffffffeb04242a80

lr: 0xfffffff00c0fb444 fp: 0xffffffeb04242af0

lr: 0xfffffff00c236d98 fp: 0xffffffeb04242b70

lr: 0xfffffff00c235f60 fp: 0xffffffeb04242c20

lr: 0xfffffff00c7655fc fp: 0xffffffeb04242c30

lr: 0xfffffff00c0fb158 fp: 0xffffffeb04242fc0

lr: 0xfffffff00c0fb158 fp: 0xffffffeb04243020

lr: 0xfffffff00d25b42c fp: 0xffffffeb04243040

lr: 0xfffffff00d102350 fp: 0xffffffeb04243070

lr: 0xfffffff00d0f682c fp: 0xffffffeb042430b0

lr: 0xfffffff00d0d69d4 fp: 0xffffffeb042430e0

lr: 0xfffffff00d0d5f08 fp: 0xffffffeb042431d0

lr: 0xfffffff00d0ec29c fp: 0xffffffeb04243230

lr: 0xfffffff00d0e2964 fp: 0xffffffeb04243270

lr: 0xfffffff00d0c56ac fp: 0xffffffeb042432c0

lr: 0xfffffff00c6ae5ac fp: 0xffffffeb04243330

lr: 0xfffffff00d0c50f0 fp: 0xffffffeb04243540

lr: 0xfffffff00d0c463c fp: 0xffffffeb04243730

lr: 0xfffffff00d0b3180 fp: 0xffffffeb04243770

lr: 0xfffffff00d0b4a60 fp: 0xffffffeb042437a0

lr: 0xfffffff00c6df404 fp: 0xffffffeb04243800

lr: 0xfffffff00d0b45a4 fp: 0xffffffeb04243880

lr: 0xfffffff00c6e91ec fp: 0xffffffeb04243a20

lr: 0xfffffff00c1fe09c fp: 0xffffffeb04243b40

lr: 0xfffffff00c10172c fp: 0xffffffeb04243bd0

lr: 0xfffffff00c0d6cd8 fp: 0xffffffeb04243d00

lr: 0xfffffff00c0ede70 fp: 0xffffffeb04243d90

lr: 0xfffffff00c22b678 fp: 0xffffffeb04243e60

lr: 0xfffffff00c236328 fp: 0xffffffeb04243f10

lr: 0xfffffff00c7655fc fp: 0xffffffeb04243f20

Reply

Answer 4

plagisbert Author

Level 1

5 points

Jan 25, 2022 9:02 AM in response to plagisbert

Ok, just after sending this message it restarted again with the following report (I don't know what to do):

panic(cpu 1 caller 0xfffffff00d3a5064): userspace watchdog timeout: no successful checkins from dfrd in 180 seconds

service: dfrd, total successful checkins since load (220 seconds ago): 4, last successful checkin: 180 seconds ago

service: remoted, total successful checkins since load (220 seconds ago): 22, last successful checkin: 0 seconds ago

service: bridgeaudiod, total successful checkins since load (220 seconds ago): 23, last successful checkin: 0 seconds ago

service: logd, total successful checkins since load (220 seconds ago): 22, last successful checkin: 0 seconds ago

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 19P647

macOS version: 21C52

Kernel version: Darwin Kernel Version 21.2.0: Sun Nov 28 20:41:46 PST 2021; root:xnu-8019.61.5~2/RELEASE_ARM64_T8010

Kernel UUID: 096BFE9E-1498-32D9-A90D-40F573034F7C

iBoot version: iBoot-7429.61.2

secure boot?: YES

x86 EFI Boot State: 0x16

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0xec

x86 Previous Power Transitions: 0x70707060400

PCIeUp link state: 0x1614

Paniclog version: 13

Kernel slide: 0x0000000005028000

Kernel text base: 0xfffffff00c02c000

mach_absolute_time: 0x14800db18

Epoch Time: sec usec

Boot : 0x61f02b56 0x000c0e73

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x61f02c36 0x00003dd6

Zone info:

Foreign : 0xfffffff05e1bc000 - 0xfffffff05e1cc000

Native : 0xffffffe00015c000 - 0xffffffe60015c000

Readonly : 0xffffffe0e67c0000 - 0xffffffe133484000

Metadata : 0xffffffeb0086c000 - 0xffffffeb049e8000

Bitmaps : 0xffffffeb0206c000 - 0xffffffeb022dc000

CORE 0: PC=0x00000001ed693fe8, LR=0x00000001ed8b2d3c, FP=0x000000016df8cd20

CORE 1 is the one that panicked. Check the full backtrace for details.

Total cpu_usage: 14010680

Thread task pri cpu_usage

0xffffffe3e62ca2d8 watchdogd 97 0

0xffffffe3e5e5dbe0 watchdogd 31 0

0xffffffe3e6694df0 kernel_task 0 4231538

0xffffffe3e66b14e8 kernel_task 0 4929758

Panicked task 0xffffffe13355e4f0: 194 pages, 3 threads: pid 36: watchdogd

Panicked thread: 0xffffffe3e62ca2d8, backtrace: 0xffffffeb0ea330c0, tid: 880

lr: 0xfffffff00c81f6b4 fp: 0xffffffeb0ea33100

lr: 0xfffffff00c81f444 fp: 0xffffffeb0ea33170

lr: 0xfffffff00c95ad98 fp: 0xffffffeb0ea331f0

lr: 0xfffffff00c959f60 fp: 0xffffffeb0ea332a0

lr: 0xfffffff00ce895fc fp: 0xffffffeb0ea332b0

lr: 0xfffffff00c81f158 fp: 0xffffffeb0ea33640

lr: 0xfffffff00c81f158 fp: 0xffffffeb0ea336a0

lr: 0xfffffff00d97f488 fp: 0xffffffeb0ea336c0

lr: 0xfffffff00d3a5064 fp: 0xffffffeb0ea336e0

lr: 0xfffffff00d3a4a58 fp: 0xffffffeb0ea33700

lr: 0xfffffff00ce03404 fp: 0xffffffeb0ea33760

lr: 0xfffffff00d3a3f74 fp: 0xffffffeb0ea33880

lr: 0xfffffff00ce0d1ec fp: 0xffffffeb0ea33a20

lr: 0xfffffff00c92209c fp: 0xffffffeb0ea33b40

lr: 0xfffffff00c82572c fp: 0xffffffeb0ea33bd0

lr: 0xfffffff00c7facd8 fp: 0xffffffeb0ea33d00

lr: 0xfffffff00c811e70 fp: 0xffffffeb0ea33d90

lr: 0xfffffff00c94f678 fp: 0xffffffeb0ea33e60

lr: 0xfffffff00c95a328 fp: 0xffffffeb0ea33f10

lr: 0xfffffff00ce895fc fp: 0xffffffeb0ea33f20

Reply

Answer 5

Jan 25, 2022 9:52 AM in response to plagisbert

those are all essentially the same problem. The buffers are not being cleared while performing I/O. That is likely a Hardware problem. You should run the diagnostic to see if it finds any gross problems. "no faultl found" is NOT the same as "all is well". Regardless, you should contact support:

Get Support

.

Reply

Continuous panic crashes on MBP 2019 13"

Similar questions