Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

14" M1 Pro Kernel Panic - How to diagnose?

D

DB294

macrumors member
Original poster
Oct 23, 2021
86
162
Hello,

I've had two kernel panic restarts in the last ~12 hours on my 14" M1 Pro Macbook Pro. Neither of these crashes happened under load, the first was overnight last night, the second was this afternoon while I was away from the computer.

I am new to macs, so I was wondering how to diagnose the actual problem? I can always take it in to apple, of course, but is there another way to figure out why? My guess is it might have something to do with my thunderbolt dock (CalDigit TS3+), as my display that is connected to that dock was intermittently disconnecting today. But again, I'd like to know how people drill into these problems for sure.
 
I think you're on the right path. Try unplugging from the dock and see if it happens again. If not, then leave with the monitor plugged in and repeat. Then go back to the dock with only the monitor plugged in, adding other devices one by one.

You might also consider just trying a reboot of the Mac with the dock, and see if that makes any difference.

I would also expect the crash reports contain some good info, and someone at Apple support might be able to shed more light on this.

Good luck!
 
I have two displays connected through Caldigit TS3+ and have had a couple of panics upon resuming from sleep. It seems like sleep mode with external monitors (at least with the Caldigit) is extremely buggy in Monterey right now. I'll frequently have one or both monitors not be detected and have to unplug/replug the dock. Super annoying.
 
  • Wow
Reactions: osx'r
sporez said:
I have two displays connected through Caldigit TS3+ and have had a couple of panics upon resuming from sleep. It seems like sleep mode with external monitors (at least with the Caldigit) is extremely buggy in Monterey right now. I'll frequently have one or both monitors not be detected and have to unplug/replug the dock. Super annoying.
Click to expand...

Interesting...I had a thorough conversation with Caldigit support just yesterday as I was considering picking one of these docks up. I specifically asked them if there were any known issues with the new MBPs or Monterey and they told me no, and that their testing has been very successful so far.

Not sure what to think, but perhaps I'm just naive to have believed what they said.
 
osx'r said:
Interesting...I had a thorough conversation with Caldigit support just yesterday as I was considering picking one of these docks up. I specifically asked them if there were any known issues with the new MBPs or Monterey and they told me no, and that their testing has been very successful so far.

Not sure what to think, but perhaps I'm just naive to have believed what they said.
Click to expand...
When the system is running it seems to be fine. It’s sleep mode that seems to mess it up. Also it seems to be worse in clamshell mode. Opening the laptop display usually makes everything start to work again. I’m hoping it’s just bugs that will be worked out soon.
 
I've been having kernel panics with my 14" MBP and Caldigit TS3+ also, maybe one every day or two.

Out of frustration, I've taken the Caldigit out of the loop and now am going MBP - TB3 cable - LG 5K ultrafine - all other USB devices.

Hopefully, this will end the panics.
 
I have a TS3+ connected to my M1 Max 16” since day 1 of laptop release. It literally lives in this configuration with my LG 5K display. Not a single crash.
 
WilliamG said:
I have a TS3+ connected to my M1 Max 16” since day 1 of laptop release. It literally lives in this configuration with my LG 5K display. Not a single crash.
Click to expand...

I dock and undock my m1 pro a couple of times a day from the TS3+ / monitor (without shutting down). I think this state change is a big part of the problem. Do you dock / undock much?
 
My TS3+ used to crash my 16" Intel MBP all the time. I haven't had any issues with the 14" so far. I probably dock/undock once or twice a day.
 
I got a few of those:

panic(cpu 5 caller 0xfffffe002e17c7c8): "LLC Bus error from cpu1: FAR=0x7908560014 LLC_ERR_STS/ADR/INF=0x11000ffc00000080/0x2280000481302060/0x1 addr=0x481302060 cmd=0x14(acc_cifl2c_cmd_ncwr)"
Debugger message: panic
Memory ID: 0x6

According to the interwebs these kept on happening for non-pro M1 users as well, most likely related to either Ethernet (Thunderbolt) or an external screen.
My old TB hub had both, so hard to say. Didn't have a crash yet using a new TB Hub without ethernet (past 4 days).
 
Same issue here on my 14" with a TS3 Plus on macOS 12.1.
I unplugged the MBP from my dock and turned it on after ~5 hours again. That's when it kernel panic'ed apparently.
Did anyone ever have this issue again/solve the issue?

Part of my kernel panic:
"panic(cpu 7 caller 0xfffffe0017503ae4): \"LLC Bus error from cpu1: FAR=0x120030205c LLC_ERR_STS\/ADR\/INF=0x11000ffc00000082\/0x2280001200302058\/0x1 addr=0x1200302058 cmd=0x14(acc_cifl2c_cmd_ncwr)\" @AppleFireStormErrorHandler.cpp:424....
 
TheJulianJES said:
Same issue here on my 14" with a TS3 Plus on macOS 12.1.
I unplugged the MBP from my dock and turned it on after ~5 hours again. That's when it kernel panic'ed apparently.
Did anyone ever have this issue again/solve the issue?

Part of my kernel panic:
"panic(cpu 7 caller 0xfffffe0017503ae4): \"LLC Bus error from cpu1: FAR=0x120030205c LLC_ERR_STS\/ADR\/INF=0x11000ffc00000082\/0x2280001200302058\/0x1 addr=0x1200302058 cmd=0x14(acc_cifl2c_cmd_ncwr)\" @AppleFireStormErrorHandler.cpp:424....
Click to expand...
Yes, many times. Also with a Thunderbolt Dock. I've kind of narrowed it down to a UAD audio interface I've got attached to it which is not yet using proper drivers. If I turn that off before going into standby, everything runs kinda smoothly.
Crash happens every couple of days otherwise. (Not 100% sure if these are related bc of the rather low frequency of crashes).

A quick google search reveals it could also be related to an ethernet interface inside the dock. My new one (Elements Hub) doesn't have one though and with my old TB3 dock I kind of recall it also didnt happen as long as i switched off the audio interface.
 
@matthewadams Interesting to know. For me, it was my first crash so far.
I do use the ethernet interface on the TS3 Plus (and dual monitors) but have no extra audio interface attached to the dock. I'm also not using any of the audio ports on the dock.

I'll keep monitoring the issue.
Edit: I wonder if macOS 12.2 Beta 1 fixes the issue?
 
Last edited:
TheJulianJES said:
Same issue here on my 14" with a TS3 Plus on macOS 12.1.
I unplugged the MBP from my dock and turned it on after ~5 hours again. That's when it kernel panic'ed apparently.
Did anyone ever have this issue again/solve the issue?

Part of my kernel panic:
"panic(cpu 7 caller 0xfffffe0017503ae4): \"LLC Bus error from cpu1: FAR=0x120030205c LLC_ERR_STS\/ADR\/INF=0x11000ffc00000082\/0x2280001200302058\/0x1 addr=0x1200302058 cmd=0x14(acc_cifl2c_cmd_ncwr)\" @AppleFireStormErrorHandler.cpp:424....
Click to expand...
I bought an M1 Pro some days ago and I have noticed the same kernel panic ( @AppleFireStormErrorHandler.cpp:424). I also have a UA Audio Arrow interface attached to my macbook and it happens every time I let it go to sleep. (never when I'm actively using it). Very annoying and I wonder if this is only a software issue (I hope)

My kernel panic:

panic(cpu 1 caller 0xfffffe0023bafae4): "LLC Bus error from cpu1: FAR=0x118068000 LLC_ERR_STS/ADR/INF=0x11000ffc00000082/0x2280080a00102240/0x5 addr=0xa00102240 cmd=0x14(acc_cifl2c_cmd_ncwr)" @AppleFireStormErrorHandler.cpp:424
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 21C52
Kernel version: Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:41 PST 2021; root:xnu-8019.61.5~1/RELEASE_ARM64_T6000
Fileset Kernelcache UUID: 88208EF24C07AA8B02CDA1369E036EBD
Kernel UUID: 2F4E22DC-64BE-3369-B574-0909F0571FA6
iBoot version: iBoot-7429.61.2
secure boot?: YES
Paniclog version: 13
KernelCache slide: 0x000000001b23c000
KernelCache base: 0xfffffe0022240000
Kernel slide: 0x000000001ba68000
Kernel text base: 0xfffffe0022a6c000
Kernel text exec slide: 0x000000001bb50000
Kernel text exec base: 0xfffffe0022b54000
mach_absolute_time: 0x60a9456c81
Epoch Time: sec usec
Boot : 0x61c9fbba 0x00069a9d
Sleep : 0x61ca3f44 0x00011ec4
Wake : 0x61ca3f5d 0x0001fae7
Calendar: 0x61ca3f5f 0x0002692f
 
chepte said:
I bought an M1 Pro some days ago and I have noticed the same kernel panic ( @AppleFireStormErrorHandler.cpp:424). I also have a UA Audio Arrow interface attached to my macbook and it happens every time I let it go to sleep. (never when I'm actively using it). Very annoying and I wonder if this is only a software issue (I hope)
Click to expand...

I hope so. AFAIK Universal Audio are working on an entirely new driver as the current one is still based on the now legacy kernel extensions (therefore potentially causing kernel panics).
 
  • Like
Reactions: Vinceh99
Did anyone ever solve this issue? Until this day I'm still experiencing kernel panics when putting my mac to sleep while it is connected to my Thunderbolt UAD Arrow Audio interface.
 
chepte said:
Did anyone ever solve this issue? Until this day I'm still experiencing kernel panics when putting my mac to sleep while it is connected to my Thunderbolt UAD Arrow Audio interface.
Click to expand...
I still get this issue, a few times a month, when connected to Caldigit TS3+ dock.
 
I have the same issue with a MacBook Pro M1 Pro 14" in macOS Sonoma with a Caldigit TS4. It happens intermittently a few times a month. Looking forward to a solution.
 
nfmohit said:
I have the same issue with a MacBook Pro M1 Pro 14" in macOS Sonoma with a Caldigit TS4. It happens intermittently a few times a month. Looking forward to a solution.
Click to expand...
No such problems with the same laptop and a TS4. Two displays, ethernet, an SSD, a USB keyboard, a mouse dongle and 3.5mm audio routed through the TS4. Crossing fingers it doesn't start happening.

I am using Apple-branded TB4 cables, if that's worth anything.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back