Trying to decode kernel panic message

[harrisonjr98]

Had a couple of panics in the last few days on my M1 Mac Mini after a couple of months before that of smooth sailing, trying to figure out the problem. Here's the panic string from the most recent occurence:

"panicString" : "panic(cpu 0 caller 0xfffffe003196fe28): DCP DATA ABORT pc=0x00000000000729c4 Exception class=0x25 (Data Abort taken without a change in Exception level), IL=1, iss=0x7 far=000000000000000000 - cpsrc(45)\nRTKit: RTKit-1558.40.22.debug

I can provide other parts of the panic log if needed, but I'm just looking for some guidance as to how to read this and figure out what caused it. Both times it happened, I was waking the machine from a sleep state - the monitor output briefly flashed fuzzy/pink, and then it rebooted itself and came up with the error. It did *not* happen while the machine was in a sleep state, like some others have had, but while I was waking it up.

Thanks in advance for any guidance.

 

[Quackers]

Sounds like it could be a version of the panic others have found when a monitor is connected via HDMI. Is that the case with yours?
https://discussions.apple.com/thread/252080550

 

[Honza1]

While someone may be able to help you, the first thing you should do is report this to Apple. Apple may actually fix the problem - eventually. Few years ago I reported similar issues I had on my 2017 MBP and they fixed it (after 3 . releases, so not fast) and even let me know that it should be fixed.

 

[harrisonjr98]

Sounds like it could be a version of the panic others have found when a monitor is connected via HDMI. Is that the case with yours?
https://discussions.apple.com/thread/252080550

I saw that thread while researching the issue. My monitor is plugged in via HDMI, but I’m not sure how to compare my panic log to make sure that that’s actually what triggered it. It would make sense, given that it happened when waking up from sleep when the monitor was communicating with a Mac to some extent to “wake up.”

 

[harrisonjr98]

While someone may be able to help you, the first thing you should do is report this to Apple. Apple may actually fix the problem - eventually. Few years ago I reported similar issues I had on my 2017 MBP and they fixed it (after 3 . releases, so not fast) and even let me know that it should be fixed.

This was my first thought too, but I’m not sure what channel to reach out through. Normal online and phone support isn’t knowledgeable about this sort of thing, I’d wager most geniuses even aren’t (or they may be like me and understand conceptually but not be able to really interpret it.)

 

[Quackers]

When I had a KP (different from yours) the report came up on my desktop and insisted I sent it to Apple.
Obviously yours didn't do that so not as easy for you to send it perhaps.

 

[harrisonjr98]

When I had a KP (different from yours) the report came up on my desktop and insisted I sent it to Apple.
Obviously yours didn't do that so not as easy for you to send it perhaps.

This did come up and I sent it off! What I’m trying to do is follow up and find out what’s causing it, though.

 

[harrisonjr98]

Update - this is now happening with almost every wake from sleep. I have not installed any new hardware or software in the last few days.

Here's the latest string:

"panicString" : "panic(cpu 1 caller 0xfffffe00258f3e28): DCP DATA ABORT pc=0x00000000000729c4 Exception class=0x25 (Data Abort taken without a change in Exception level), IL=1, iss=0x7 far=000000000000000000 - cpsrc(43)\nRTKit: RTKit-1558.40.22.debug

 

[Honza1]

This was my first thought too, but I’m not sure what channel to reach out through. Normal online and phone support isn’t knowledgeable about this sort of thing, I’d wager most geniuses even aren’t (or they may be like me and understand conceptually but not be able to really interpret it.)

Did you hear about Mr Google? Try:"apple report a bug"

Feedback - macOS - Apple

 

[harrisonjr98]

Did you hear about Mr Google? Try:"apple report a bug"

Feedback - macOS - Apple

I’ve done this, and submitted the panic report. I’m aware of these normal channels - I guess what I’m looking for is more of a way to figure out what happened specifically on my machine so that I can assess whether it seems more likely hardware/software and follow if it’s a known issue, etc.

 

[ManuCH]

I've had the same kernel panic on my M1 Mac Mini today:

panic(cpu 2 caller 0xfffffe0027877e28): DCP DATA ABORT pc=0x0000000000073890 Exception class=0x25 (Data Abort taken without a change in Exception level), IL=1, iss=0x7 far=000000000000000000 - cpsrc(51)
RTKit: RTKit-1558.80.1.debug - Client: local-ipad13dcp.release

And yes I also have a screen connected to the HDMI port. It's my first kernel panic on this machine and it's about 2 months old. I'm on macOS 11.2.1.