Macbook Air M1 - kernel panic

Just to add to the experience here.

I play "Eve Online", along with my wife. We both have Mac M1 Minis for "desktop" use, and we both have MacBook Air M1s, for casual use. We can and do game on either/all machines.

We have each had the same PSOD (Pink Screen Of Death) with the same kernel panic. This is principally whilst in-game. Not conclusively - but very typically in response to an event (for example, leaving the game unattended overnight is generally safe -no crash), but performing an action does run a low-chance (1-per-day, typical) of a PSOD.

The Minis are connected through built-in HDMI to standard QHD displays.

The Airs are typically presenting on their built-in displays. My Air, occasionally, connected through a USB-C dongle to my main monitor, but that's infrequent.

There's no "killer combination" - they will all PSOD variously at a low rate.

Other applications are not known to affect in the same way.

That this is more often triggered by an in-game action, I don't believe (gut feel) this is a hardware fault, my thoughts are more that this is driver related in response to some illegal parameter being passed through (likely) the graphic stack. It could be a result of the Eve / Wine combination of software.

Carry on reporting the crash dumps....

Further to my earlier post - I should add I've also got a Mac Pro 5,1 with later GFX, loads of RAM, storage etc, and also a MacBook Air Intel 2018 - both of these play the same game (Eve) without fault. The problem lies with the silicon or software stack that is associated with the M1.

Go to sleep after work, and return back :)))) First time for two month of using :)

MBP 2020 M1 16/512

11.4 (20F71)

IYAMA PL2792Q HDMI (over Apple original adapter)

panic(cpu 1 caller 0xfffffe0019df9798): "dart-dispext0 (0xfffffe2332ce8000): SMMU(SMMU) error: SID 0 PTE invalid exception on read with DVA 0x10000 (TTBR 0 SEG 0 PTE 0x4) ERROR_STATUS 0x80000004 TIME 0x67da1cd48789 TTE 0 AXI_ID 0)"
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 20F71
Kernel version: Darwin Kernel Version 20.5.0: Sat May  8 05:10:31 PDT 2021; root:xnu-7195.121.3~9/RELEASE_ARM64_T8101
Fileset Kernelcache UUID: FB10CC0AB8BAC020BC47A50D64476F11
Kernel UUID: 07259C53-9EF7-32FF-821D-8F28A5985DFA
iBoot version: iBoot-6723.120.36
secure boot?: YES
Paniclog version: 13
KernelCache slide: 0x0000000010c20000
KernelCache base:  0xfffffe0017c24000
Kernel slide:      0x0000000011768000
Kernel text base:  0xfffffe001876c000
Kernel text exec base:  0xfffffe0018838000
mach_absolute_time: 0x27e111af619
Epoch Time:        sec       usec
  Boot    : 0x60b65764 0x000c925b
  Sleep   : 0x60b875f5 0x0004f3af
  Wake    : 0x60b8777c 0x000de899
  Calendar: 0x60b941a4 0x000c0357

CORE 0 recently retired instr at 0xfffffe00189aa6f4
CORE 1 recently retired instr at 0xfffffe00189a9240
CORE 2 recently retired instr at 0xfffffe00189aa6f4
CORE 3 recently retired instr at 0xfffffe00189aa6f4
CORE 4 recently retired instr at 0xfffffe00189aa6f8
CORE 5 recently retired instr at 0xfffffe00189aa6f8
CORE 6 recently retired instr at 0xfffffe00189aa6f8
CORE 7 recently retired instr at 0xfffffe00189aa6f8
Panicked task 0xfffffe1666ecc688: 549630 pages, 486 threads: pid 0: kernel_task
Panicked thread: 0xfffffe166735eca0, backtrace: 0xfffffe306851f4f0, tid: 1585
		  lr: 0xfffffe0018886be4  fp: 0xfffffe306851f560
		  lr: 0xfffffe00188869c8  fp: 0xfffffe306851f5d0
		  lr: 0xfffffe00189afa70  fp: 0xfffffe306851f5f0
		  lr: 0xfffffe00189a12b8  fp: 0xfffffe306851f6a0
		  lr: 0xfffffe001883f7e8  fp: 0xfffffe306851f6b0
		  lr: 0xfffffe0018886658  fp: 0xfffffe306851fa40
		  lr: 0xfffffe0018886658  fp: 0xfffffe306851fab0
		  lr: 0xfffffe00190383e8  fp: 0xfffffe306851fad0
		  lr: 0xfffffe0019df9798  fp: 0xfffffe306851fd40
		  lr: 0xfffffe0019df9270  fp: 0xfffffe306851fdd0
		  lr: 0xfffffe0019df8a5c  fp: 0xfffffe306851fe80
		  lr: 0xfffffe0018f65ec0  fp: 0xfffffe306851fec0
		  lr: 0xfffffe0018f9bdc0  fp: 0xfffffe306851ff20
		  lr: 0xfffffe00199a68c8  fp: 0xfffffe306851ffb0
		  lr: 0xfffffe0018f8c9e0  fp: 0xfffffe306851ffc0
		  lr: 0xfffffe00189a3ce0  fp: 0xfffffe306851ffe0
		  lr: 0xfffffe001883f85c  fp: 0xfffffe306851fff0
		  lr: 0xfffffe0018920258  fp: 0xfffffe401f813c90
		  lr: 0xfffffe0018920258  fp: 0xfffffe401f813d10
		  lr: 0xfffffe001890cd88  fp: 0xfffffe401f813db0
		  lr: 0xfffffe001890dfb8  fp: 0xfffffe401f813e10
		  lr: 0xfffffe001894b4e4  fp: 0xfffffe401f813e60
		  lr: 0xfffffe001894b070  fp: 0xfffffe401f813f00
		  lr: 0xfffffe0018848c38  fp: 0x0000000000000000
      Kernel Extensions in backtrace:
         com.apple.driver.AppleT8020DART(1.0)[F6E1E036-504F-3FDF-B83B-6732226FF906]@0xfffffe0019df4000->0xfffffe0019dfbfff
            dependency: com.apple.driver.AppleARMPlatform(1.0.2)[F784412E-33CC-3859-B0CB-D0A62C9E26CB]@0xfffffe0019194000->0xfffffe00191e3fff
            dependency: com.apple.driver.IODARTFamily(1)[55309CB3-D624-3B9B-962A-E82571B663FC]@0xfffffe001a8cc000->0xfffffe001a8dffff
         com.apple.driver.AppleInterruptController(1.0d1)[E7931F7A-8581-32B7-8A33-394B279B926C]@0xfffffe00199a4000->0xfffffe00199a7fff
            dependency: com.apple.driver.AppleARMPlatform(1.0.2)[F784412E-33CC-3859-B0CB-D0A62C9E26CB]@0xfffffe0019194000->0xfffffe00191e3fff

last started kext at 2104482917610: com.apple.driver.AppleUSBTopCaseDriver	4050.1 (addr 0xfffffe00181f4000, size 16384)

I had the first time today on my 2 months old m1 Macbook air. I was running a simulation which I hadn't run since updating the OS last week. The simulation shows up in the report too "Panicked task 0xfffffe167e80af08: 61 pages, 1 threads: pid 2349: ekt.exe". I am not sure how to interpret these (I am totally new to mac!). Here is my panic report

"panicString" : "panic(cpu 0 caller 0xfffffe001f089798): \"dart-disp0 (0xfffffe2332ee0000): SMMU(SMMU) error: SID 0 PTE invalid exception on read with DVA 0x3304000 (TTBR 0 SEG 0x1 PTE 0x4c1) ERROR_STATUS 0x80000004 TIME 0x28daa4b27c40 TTE 0 AXI_ID 0)

I also noticed that cursor started to stutter a few minutes before the crash but then became fine. Also, I had left the code running over night and the battery had died when I checked in the morning. So when the crash happened it was plugged in.

Exactly what i said before, mouse stutter and the crash after a few minutes.

A dirty workaround is to lock the Macbook, close the lid, wait a few seconds, then open it again. You'll notice that the mouse is smooth again and no crash will happen this time.

I am glad to hear that worked for you Libavius but I am not confident that you problem is gone for good. My situation improved on an old Thunder Bolt display (connected via a Apple Thunderbolt 3 to 2 adaptor) when I separated the key board from the display, but I still get a few kernel panics. Some days zero; some days three.

"it seems the Apple adapter and the Belkin cable did the trick."

For me using a different cable helped as well. I was using the cable shipped with my LG monitor with the Apple adapter. And had the crashes. Now a USB-C to Displayport cable and no issues. The screen is also more responsive.

I had not heard that one about Bluetooth before but I would love for that to be the issue. Something definitive that can be resolved would be great news! I am still not clear why a Bluetooth "shielding" issue would only apply to M1 MB Airs.

I ordered a thunderbolt cable from Apple, as I'm using the usbc cable provided with the Dell monitor right now.

I'm always using a magic keyboard + trackpad connected via bluetooth. I will update you as soon as I use the Apple cable (if I don't get a Panic within 2 weeks of using it, we can assume that it was the cable)

Hi, I believe I have some useful insight into what's causing this serious issue for so many users. In a nutshell, I believe the engineers failed to adequately test the power management features of the M1 devices with external devices when plugged into the AC power....as so many of us are doing working from home during the pandemic.

After returning a defective refurbished MacBook with the Intel chip to Apple, I decided to go for it this April and buy a brand new M1 Air from Costco. I experienced the same VERY frustrating random reboot issue with the replacement MacBook Air M1 they sent me last week which further confirmed my theory.

As we've all seen, this is now a well-known reoccurring, intermittent issue with both the MacMini and Macbooks with the M1 chip when using one external monitor and/or hub. Still, six months later, Apple doesn’t seem to be addressing it in a timely manner. This issue occurs even with the Apple brand adaptor they sent me.  I can't express how frustrating it is having these brand new devices crash on me with so few apps open right before a business meeting or on deadline for major project....ironically for the tech industry clients sometimes. Ugh!! I definitely feel everyone's frustrations whether depending upon these M1s for work or play....especially during COVID.

So here's my ureka moment in trying to get to the bottom of this. Since observing that the issue doesn't seem to be tied to specific apps or brands, I realized it must deal with the power managment of this first-gen chip. I noticed that if I unplug the power cord the problem won’t occur. This suggests Apple failed to test the power management of the new chip enough when using peripheral devices….as most users are during the pandemic at home especially. It seems 'kernal panic’ events will occur as a result of the power mismanagement. 

I feel that Costco and other retailers should demand that this apparent hardware issue be addressed before selling another M1 devicce. Read the user comments on the most reliable media reports online and you'll see the random rebooting is unlikely due to third-party apps causing this as Apple has asserted. This issue occurs even using just Apple Mail, Safari, etc. 

I hope Costco management will take my message seriously and urge Apple to act swiftly and appropriately with your members. We depend on Apple computers for our livelihoods, not just for fun.  Also, if Apple is aware of certain fixes, I feel they are obligated to inform the retailers who sold them and also the end users who paid good money for the Mercedes of computers.

Appleusersince1997, thanks for your insights. I had not thought of the power management issue. For me, it has always occurred when plugged into an external monitor, but I haven’t necessarily had other peripherals attached. The LG monitor does provide a power source. But it was worse with a Dell monitor, which did not. When using that monitor, I plugged in the power supply separately.

Just an update. My Air rebooted overnight while on sleep mode. Apple is sending me a free Belkin HDMI 4K cable. Hopefully that will stop the problem until Apple's engineers fix this horrible thing for good. What a headache. Has anyone else found any solutions?

Not all cases. Again, to re-iterate my earlier posts - has happened on M1 Air without anything connected (including power = disconnected). Maybe not all the same trigger, but Pink-Screen-Of-Death & reboot with warnings of a kernel panic with the usual dart-disp0 log.

Hi Summat. Yes, its true there is more than one kernel panic type showing up. But if I could get rid of all the "panic(cpu 3 caller 0xfffffe00214984c4): "dart-disp0 (0xfffffe233642c000): SMMU(SMMU) error: SID 0 PTE invalid exception on read with DVA........" then my live would be worth living!!