Kernel Panic - MacBook Pro Apple M1 13 Inch

Part Four:

com.apple.driver.mDNSOffloadUserClient 1.0.1b8

com.apple.iokit.IONetworkingFamily 3.4

com.apple.iokit.IOSerialFamily 11

com.apple.driver.AppleSEPManager 1.0.1

com.apple.driver.AppleA7IOP 1.0.2

com.apple.driver.IOSlaveProcessor 1

com.apple.driver.AppleBiometricSensor 2

com.apple.iokit.IOHIDFamily 2.0.0

com.apple.AUC 1.0

com.apple.iokit.IOAVFamily 1.0.0

com.apple.iokit.IOHDCPFamily 1.0.0

com.apple.iokit.IOCECFamily 1

com.apple.iokit.IOAudio2Family 1.0

com.apple.driver.AppleEmbeddedAudioLibs 1.17

com.apple.driver.AppleFirmwareUpdateKext 1

com.apple.driver.AppleM2ScalerCSCDriver 265.0.0

com.apple.iokit.IOSurface 289.3

com.apple.driver.IODARTFamily 1

com.apple.security.quarantine 4

com.apple.security.sandbox 300.0

com.apple.kext.AppleMatch 1.0.0d1

com.apple.driver.AppleMobileFileIntegrity 1.0.5

com.apple.kext.CoreTrust 1

com.apple.security.AppleImage4 3.0.0

com.apple.iokit.IOCryptoAcceleratorFamily 1.0.1

com.apple.driver.AppleARMPlatform 1.0.2

com.apple.iokit.IOStorageFamily 2.1

com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0

com.apple.iokit.IOReportFamily 47

com.apple.kec.pthread 1

com.apple.kec.corecrypto 11.1

com.apple.kec.Libm 1

** Stackshot Succeeded ** Bytes Traced 304666 (Uncompressed 765552) **

Is this consistently for the same panic reason? if so, you may have a hardware issue, and should seek service.

In this context, DART appear to stand for Device Address Resolution Table, a complex way to decide what I/O (i.e., not RAM) is being addressed, and finding its ring-buffers.

Yep, its just happened yet again. Top part of the kernal panic report reads as:

panic(cpu 2 caller 0xfffffe0016a544c4): "dart-disp0 (0xfffffe2336360000): SMMU(SMMU) error: SID 0 PTE invalid exception on read with DVA 0x4c000 (TTBR 0 SEG 0 PTE 0x13) ERROR_STATUS 0x80000004 TIME 0x4eef5ecb6e7 TTE 0 AXI_ID 0)"

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 20C69

Kernel version: Darwin Kernel Version 20.2.0: Wed Dec 2 20:40:21 PST 2020; root:xnu-7195.60.75~1/RELEASE_ARM64_T8101

Fileset Kernelcache UUID: 3E6AA74DF723BCB886499A5AAB34FA34

Kernel UUID: 48F71DB3-6C91-3E62-9576-3A1DCEF2B536

iBoot version: iBoot-6723.61.3

secure boot?: YES

Paniclog version: 13

KernelCache slide: 0x000000000d8a4000

KernelCache base: 0xfffffe00148a8000

Kernel slide: 0x000000000e3e4000

Kernel text base: 0xfffffe00153e8000

Kernel text exec base: 0xfffffe00154b0000

mach_absolute_time: 0x1e51137452

Epoch Time: sec usec

Boot : 0x6006f009 0x000c691b

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x60070534 0x00089dc5

It appears I may need to contact the vendor, doesn't it? Thanks for your help and advice.

*edit* this report is different from the previous one despite it being the same issue (my end, at least). Any ideas what this means?

When you have the same panic-reason over and over, that suggest you have a problem that can be tracked down and fixed.'' This one appears to be related to DART.

Be sure to send a printed panic report in when you submit your Mac for service.

When you have completely different panic reasons "all over the map" that suggests something far more complex or a RAM memory issue.

NB>> On these MacBook Pro models, you MUST have a Trusted Backup on hand. Your boot drive will NOT be returned to you if the mainboard is swapped out during service.

Plenty of people, myself included, are having multiple daily crash/restart/kernel panics with no thunderbolt connections whatsoever, doing simple things like browsing with Safari or recording audio with LumaFusion, etc. The M1 problem is much bigger than one device or connection. Apple has a real problem on its hands and, so far, has nothing but evasion (or silence) for its users. It’s been maybe fifteen years since I had a Mac that kernel panic/crashed even once. My new MacBook Pro has done it every day I’ve used it for more than about an hour it this last week. A troubling debut for M1 silicon/Big Sur for sure.

At present, we have no known work-arounds for DART problems. It may take a mainboard swap to solve the issue. This is new custom silicon, and they may not be testing them thoroughly enough to weed out the ones that fail this way "after about hour of use."

They are NOT going to chase you down. If you have an issue, DO NOT wait for a software update, "Get Support" and work with them on a cause and some form of relief. Only they know the best form for that relief.

Get Support

Welp, I’m packing up my 2nd M1 Mac for return to Apple. Note: the kernel panics have mostly stopped (except for when my Promise Pegasus thunderbolt raid array is plugged in). So why am I returning it? Because my new MacBook (ahem) “Pro” doesn’t connect to more than one external display. It’s 2021! My 2014 and 2018’MB “Pros” can drive multiple external 4k monitors. But my 2020 M1 MB (ahem) “Pro” cannot?? Sad! Steve Jobs must be rolling over in his grave at the mediocrity which has seeped into Apple. BL: It’s apparently too much to ask to have your “Pro” MacBook to not throw kernel panics or to connect to more than one external display.

I just wanted to give an update about my

personal experience. I’m now 99% sure that my kernel woes were related to one specific program I was running that wasn’t optimized for Apple’s M1 chip (Football Manager 20). I have had my MacBook Pro for 2 months now and haven’t encountered this issue in any other case, though I’m sure the issue is still a problem that Apple should be addressing.

Driving a 6K display is not mediocre.

It just does not happen to line up with the display approach you were using.

Steve would tell you insisting on two displays, while you could be using one as large as 6K is like a faster buggy-whip.

If, out of ALL the Applications you are running, only Football Manager does not work properly, Apple will NOT be spending Apple Engineering time to figure out why.

If you want that situation improved, apply pressure to the publishers of Football Manager, who are now unable to have happy Users running on the Apple-Silicon M1 MacBooks.

A bit of positive news. I held off for the past two weeks to be sure that the kernal crashing issue had really passed, which it now seems to have done. Just to refresh, my M1 MacBook Pro, with 16GB RAM, was crashing once a day, after even very light use (Safari, etc) and with no peripherals of any kind attached and Bluetooth either on or off.

After trying multiple things, I began to wonder if I had imported the problem with the migration of my Home Folder from my desktop (iMac), running Catalina to my Big Sur MacBook.

Therefore I went back through all of the User/Library folders and deleted everything that didn't seem absolutely necessary, from the entire contents of much of my Application Support folder to all the irrelevant prefs files in my Preferences folders. From the little I know on the subject, none of these should have been responsible for Kernel Panics in any circumstances, but I was going crazy trying to find the problem.

And it seems I have. Somewhere there the culprit must have been lurking. Because, even before I upgrade to Big Sur 11.2.1 (maybe tomorrow) the kernal crashing seems to have stopped and the MacBook is running perfectly. For those who, like myself a couple of weeks back, were close to giving up, it might be worth an hour or so with a feather duster clearing out any cobwebs that you didn't think could still be there, and maybe tripping you up.

LOL dude deleted my reply because I exposed his mediocrity!

Kernel Panic is not ONE problem, it is one of thousands of problems.

You have not provided enough information to even understand what your issue is.

What Mac? what MacOS? what kernel panic report?

The entire crash report is posted at https://www.beachstreetnews.com/m1-mac-mini-daily-crashes/ for anyone interested to see if it matches theirs line for line.

As noted in my reply to seminolefans no crash today, only change was in energy saver preferences as noted in post.