M1 16" Pro regular kernel panic - always "DCP PANIC" when waking from display sleep

Question

Level 1

20 points

M1 16" Pro regular kernel panic - always "DCP PANIC" when waking from display sleep

So since this arrived finally in March, I've experienced kernel panics on average I'd say every 3 weeks.

Always the same problem, always a similar panic report - "DCP PANIC".

To reproduce - allow laptop to power down display for some time. Press a key to wake up the display again (laptop is not asleep, just display off). Expect the screen to instantly wake up, instead nothing happens for ca 5 seconds whereupon the system restarts.

As of today I've disabled screen power off both on battery & when plugged in (it panics in either case) and instead dimming the screen manually when necessary. Let's see if that's a workaround....

Already posted in this topic which seems to have close by itself due to inactivity New 2021 16" MacBook Pro M1 Max frequent … - Apple Community

I've got panic reports from 2022-04-21 2022-06-09 2022-06-23 2022-07-15 2022-08-04 [one missing here] 2022-09-19 2022-10-04. Updated to the latest MacOS available after each crash if applicable.

The panic messages as follows

2022-04-21:

"panicString" : "panic(cpu 1 caller 0xfffffe0021944ca8): DCP PANIC - ASSERT: AFKWorkloop_rtkit.cpp:251: [status == RTK_ST_OK]

ASSERT: RTK_workloop_init:80000008 - additionThread(27)

ASSERT: AFKWorkloop_rtkit.cpp:251: [status == RTK_ST_OK]

ASSERT: RTK_workloop_init:80000008

RTKit: RTKit-1826.60.2.debug - Client: local-t600xdcp.release

!UUID: d66133a2-256b-3785-8a04-d8d0622efeb4

Time: 0x0000135e3548230c

Faulting task 27

27 additionThread | 015 | 5504\/16384 | RUNNABLE | 0 | [Faulting task]

2022-06-09:

"panicString" : "panic(cpu 1 caller 0xfffffe00187028a4): DCP PANIC - CXXnew[]:44896 - iomfb_video_async(47)

CXXnew[]:44896

RTKit: RTKit-1827.100.26.debug - Client: local-t600xdcp.release

!UUID: 2998c293-b0e0-34e7-ae07-a5d79f620960

Time: 0x0000597446777456

Faulting task 47

47 iomfb_video_async | 016 | 5704\/16384 | RUNNABLE | 0 | [Faulting task]

2022-06-23:

"panicString" : "panic(cpu 0 caller 0xfffffe001c36ad6c): DCP PANIC - CXXnew[]:66272 - iomfb_ap_callee_0(18)

CXXnew[]:66272

RTKit: RTKit-1827.120.2.debug - Client: local-t600xdcp.release

!UUID: 03fd4159-b50c-3b24-ae15-8e6d1196d7e6

Time: 0x00001b4281a69587

Faulting task 18

18 iomfb_ap_callee_0 | 016 | 6784\/16384 | RUNNABLE | 0 | [Faulting task]

2022-07-15:

"panicString" : "panic(cpu 1 caller 0xfffffe0026a22d6c): DCP PANIC - CXXnew[]:44896 - iomfb_video_async(47)

CXXnew[]:44896

RTKit: RTKit-1827.120.2.debug - Client: local-t600xdcp.release

!UUID: 03fd4159-b50c-3b24-ae15-8e6d1196d7e6

Time: 0x00002996805dcde7

Faulting task 47

47 iomfb_video_async | 016 | 5704\/16384 | RUNNABLE | 0 | [Faulting task]

2022-08-04:

"panicString" : "panic(cpu 0 caller 0xfffffe001985ad6c): DCP PANIC - CXXnew[]:66272 - iomfb_ap_callee_0(18)

CXXnew[]:66272

RTKit: RTKit-1827.120.2.debug - Client: local-t600xdcp.release

!UUID: 03fd4159-b50c-3b24-ae15-8e6d1196d7e6

Time: 0x0000257d25119897

Faulting task 18

18 iomfb_ap_callee_0 | 016 | 6784\/16384 | RUNNABLE | 0 | [Faulting task]

2022-09-19:

"panicString" : "panic(cpu 1 caller 0xfffffe002cea1e6c): DCP PANIC - ASSERT: AFKWorkloop_rtkit.cpp:251: [status == RTK_ST_OK]

ASSERT: RTK_workloop_init:80000008 - dpIrq(76)

ASSERT: AFKWorkloop_rtkit.cpp:251: [status == RTK_ST_OK]

ASSERT: RTK_workloop_init:80000008

RTKit: RTKit-1827.120.2.debug - Client: local-t600xdcp.release

!UUID: 1317b7f6-3acf-3776-93f7-a66ed223485b

Time: 0x00001516b5d678d6

Faulting task 76

76 dpIrq | 015 | 4432\/16384 | RUNNABLE | 0 | [Faulting task]

2022-10-04:

"panicString" : "panic(cpu 0 caller 0xfffffe00289f9e6c): DCP PANIC - ASSERT: AFKWorkloop_rtkit.cpp:251: [status == RTK_ST_OK]

ASSERT: RTK_workloop_init:80000008 - additionThread(27)

ASSERT: AFKWorkloop_rtkit.cpp:251: [status == RTK_ST_OK]

ASSERT: RTK_workloop_init:80000008

RTKit: RTKit-1827.120.2.debug - Client: local-t600xdcp.release

!UUID: 1317b7f6-3acf-3776-93f7-a66ed223485b

Time: 0x00001bbd210e1d51

Faulting task 27

27 additionThread | 015 | 5520\/16384 | RUNNABLE | 0 | [Faulting task]

Posted on Oct 10, 2022 11:48 AM

Reply

Answer 1

Barney-15E

Level 10

121,922 points

Oct 16, 2022 5:59 AM in response to ByggareBobby

ByggareBobby wrote:

If it is a rogue Kext, then I've likely installed manually the same things that I had before, so the problem may well re-occur. They also suggested safe mode, but is it really practical to run in safe mode for potentially over a month?

Well, the assumption is you erase the Mac completely and install the OS without migrating anything. Does it work or not work?

If it works, don't install the third-party garbage ware. If it doesn't work, take it to Apple for repair.

Reply

Answer 2

Oct 10, 2022 11:58 AM in response to ByggareBobby

Contact Apple Support, as it would appear to be bad hardware, or maybe bad low-level software or firmware.

Reply

Answer 3

Barney-15E

Level 10

121,922 points

Oct 16, 2022 5:39 AM in response to Anthony1635

I have the same problem, but when I contacted Apple support they only suggest to reinstall macOS Monterey.

That's the first step to make sure there isn't some third-party system modification installed causing the panic. If it works with a clean OS without any modifications, then the problem was something you installed. If it still panics, take it to a Genius Bar or Apple Authorized Repair Center.

Kernel Panics are predominately caused by hardware faults and third-party kernel extensions.

Reply

Answer 4

Oct 16, 2022 5:50 AM in response to ByggareBobby

If it is a rogue kext, then a clean install followed by migration of ONLY the user accounts will restore your mac to sanity. Of course if you just reinstall or migrate EVERYTHING, then you will reinstate whatever was causing the problem.

Please run Etrecheck and post its full report here.

Use the “additional text” button and paste the report into the text box.

By looking at this report (which, unlike panic reports, we CAN read, some of us may notice probable causes.

Reply

Answer 5

ByggareBobby Author

Level 1

20 points

Oct 16, 2022 12:13 PM in response to Barney-15E

In that case I'll be using a plain MacOS with only pre-installed apps for a month of more. If Apple wants to supply me another MBP to use as I like whilst I'm not using the potentially faulty MBP then that's fine.

The problem here which the agents didn't seem to understand is that the issue occurs with no consistency. They offered to stay connected with me whilst I booted into safe mode to see if the issue went away?! I think the shortest uptime I've had before it crashed is less than a week, the longest maybe 6 weeks. What would be useful is if they could add in some more diagnostics such that when it does occur they can try and investigate as opposed to me using a hobbled Mac for an indefinite period of time to see if the problem has disappeared.

For an issue that occurs daily/weekly then trying everything to find something that solves it is a reasonable method. For something that happens on average maybe once month then a more focused approach is needed.

Reply

Answer 6

ByggareBobby Author

Level 1

20 points

Oct 16, 2022 4:51 AM in response to Anthony1635

You're also getting DCP PANiCs?

They suggested that to me too. Installed fresh on Tuesday, wasted 2 days getting things back how I want. Now the wait to see if it's helped...

Reply

Answer 7

Oct 16, 2022 6:06 AM in response to Barney-15E

Thank you. To my side I decided to bring back to Apple for repair. It is still under guarantee.

Reply

Answer 8

Oct 16, 2022 5:30 AM in response to ByggareBobby

Yes :

panic(cpu 0 caller 0xfffffe00123c9cac): DCP PANIC - pcc firmware: mapper_thr.c:1278 signal_out_of_sync() -- - iomfb_mailbox(41)

pcc firmware: mapper_thr.c:1278 signal_out_of_sync() --

RTKit: RTKit-1827.120.2.debug - Client: local-t600xdcp.release

!UUID: 9f30093b-2eba-3d7f-b479-e2492ac7c6e0

Time: 0x000000012e5ce0f8

I don't know what to do. It makes me crazy it's crashing sometimes and loose 3h to reinstall and solve nothing. Do you think it could be an hardware issue ?

Reply

Answer 9

ByggareBobby Author

Level 1

20 points

Oct 16, 2022 5:39 AM in response to Anthony1635

Does anything trigger it? In my case it only happens when waking the screen after it sleeps, never whilst I'm actively using the laptop. No external displays at all.

And whilst it's not unreasonable to see if a fresh re-install cures the issue, surely it would be good to know what actually is going wrong rather than just sweeping the issue under the carpet.

Reply

Answer 10

ByggareBobby Author

Level 1

20 points

Oct 16, 2022 5:45 AM in response to Barney-15E

If it is a rogue Kext, then I've likely installed manually the same things that I had before, so the problem may well re-occur. They also suggested safe mode, but is it really practical to run in safe mode for potentially over a month?

Reply

Answer 11

ByggareBobby Author

Level 1

20 points

Oct 16, 2022 11:57 AM in response to Luis Sequeira1

Etrecheck report

Here it is from the (not quite so) fresh installation.

Nothing was migrated, it was installed cleanly. Only then did I copy over manually settings & saved state for some programs.

This report may or may not be meaningless as that would only be known if I get another DCP panic whenever that may happen.

Reply

Answer 12

Oct 16, 2022 4:39 AM in response to ByggareBobby

I have the same problem, but when I contacted Apple support they only suggest to reinstall macOS Monterey. Is someone could help me ? Thanks Anthony

Reply

M1 16" Pro regular kernel panic - always "DCP PANIC" when waking from display sleep

Similar questions