With a slightly higher CPU load (during the game), there are repeated restarts, pink stripes appear on the black screen. I cannot interpret the reports (they are identical, see example below). The problem does not occur with the same load on Macbook Air 2015 (Football Manager 2020 game running via Epic Launcher and Chrome). Big Sur 11.1.
MacBook Air 13″, macOS 11.1
Hi all, lowering memory usage (from around 7GB closer to 6GB, of 8GB total) by closing safari tabs and some (e.g memory) resource hogging app's , e.g Spotify, resolves this issue for me. Apple needs a more elegant way of doing this, e.g low memory warning, unless this is actually a bug in macOS or M1 hardware.
BTW, I can now use an extra monitor memory again without KP's. Although not using an external monitor requires less Vram used (from main Ram) which may resolve the issue instead (but didn't for me, without closing app's).
I've had the same issue with my recently purchased Macbook Pro M1. Error report follows.
Apple store changed my computer. We were hoping that that would put an end to the problem, but I just got the same error. So disappointing... I don't know what to do. Yes, I use a USB-C hub and external display (hdmi).
Please advise.
Same here, here is the log.
It's happening every 10 days, pink lines on screen before crash/restart, the Macbook Air is always USBC connected to a Dell monitor.
I use Microsoft Office (word) / google drive (docs) on Safari a lot.
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)
Thank you Libavius for the solution, which might be helpful for some of us, however it is not enough as far as I am concerned. I connect my MBA M1 to my dell monitor via USBC, in order to :
So connecting via HDMI is not an option for me. Apple needs to take responsibility by addressing this issue ASAP, this is unacceptable. I can't even bring my MBA to the Store because I need it every single day, and I know that they won't solve the problem.
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.
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.
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?
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!!
Same problem on my M1 MacBook Pro, connected to a Belkin "USB-C Multimedia Hub". External display is connected via HDMI, mouse and keyboard via USB. An Ethernet jack is also connected to the Belkin hub, as well as a LaCie USB drive for my TimeMachine backup. The power cord is directly connected to my MacBook Pro. The MBP freezes randomly and then restarts.
Hope this gets resolved soon.
I am also sorry to hear this. It would have been great to hear that you had solved the problem once and for all, but I am pretty cynical about any quick fixes. I am still getting regular crashes (~ 10 per week) on my second MB Air M1.
crash again
panic(cpu 7 caller 0xfffffe001c1d1798): "dart-disp0 (0xfffffe2332d78000): SMMU(SMMU) error: SID 0 PTE invalid exception on read with DVA 0x141c000 (TTBR 0 SEG 0 PTE 0x507) ERROR_STATUS 0x80000004 TIME 0x2d0425fcc69 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: 0x0000000012ff8000
KernelCache base: 0xfffffe0019ffc000
Kernel slide: 0x0000000013b40000
Kernel text base: 0xfffffe001ab44000
Kernel text exec base: 0xfffffe001ac10000
mach_absolute_time: 0x11494d5881
Epoch Time: sec usec
Boot : 0x60dd21c4 0x00082fab
Sleep : 0x00000000 0x00000000
Wake : 0x00000000 0x00000000
Calendar: 0x60dd2dd3 0x00021abc
CORE 0 recently retired instr at 0xfffffe001ad826f4
CORE 1 recently retired instr at 0xfffffe001ad826f4
CORE 2 recently retired instr at 0xfffffe001ad826f4
CORE 3 recently retired instr at 0xfffffe001ad826f4
CORE 4 recently retired instr at 0xfffffe001ad826f8
CORE 5 recently retired instr at 0xfffffe001ad826f8
CORE 6 recently retired instr at 0xfffffe001ad826f8
CORE 7 recently retired instr at 0xfffffe001ad81240
Panicked task 0xfffffe16703dadb8: 354978 pages, 46 threads: pid 646: Discord Helper (
Panicked thread: 0xfffffe166f110000, backtrace: 0xfffffe304d98f4f0, tid: 8029
lr: 0xfffffe001ac5ebe4 fp: 0xfffffe304d98f560
lr: 0xfffffe001ac5e9c8 fp: 0xfffffe304d98f5d0
lr: 0xfffffe001ad87a70 fp: 0xfffffe304d98f5f0
lr: 0xfffffe001ad792b8 fp: 0xfffffe304d98f6a0
lr: 0xfffffe001ac177e8 fp: 0xfffffe304d98f6b0
lr: 0xfffffe001ac5e658 fp: 0xfffffe304d98fa40
lr: 0xfffffe001ac5e658 fp: 0xfffffe304d98fab0
lr: 0xfffffe001b4103e8 fp: 0xfffffe304d98fad0
lr: 0xfffffe001c1d1798 fp: 0xfffffe304d98fd40
lr: 0xfffffe001c1d1270 fp: 0xfffffe304d98fdd0
lr: 0xfffffe001c1d0a5c fp: 0xfffffe304d98fe80
lr: 0xfffffe001b33dec0 fp: 0xfffffe304d98fec0
lr: 0xfffffe001b373dc0 fp: 0xfffffe304d98ff20
lr: 0xfffffe001bd7e8c8 fp: 0xfffffe304d98ffb0
lr: 0xfffffe001b3649e0 fp: 0xfffffe304d98ffc0
lr: 0xfffffe001ad7bce0 fp: 0xfffffe304d98ffe0
lr: 0xfffffe001ac1785c fp: 0xfffffe304d98fff0
Kernel Extensions in backtrace:
com.apple.driver.AppleT8020DART(1.0)[F6E1E036-504F-3FDF-B83B-6732226FF906]@0xfffffe001c1cc000->0xfffffe001c1d3fff
dependency: com.apple.driver.AppleARMPlatform(1.0.2)[F784412E-33CC-3859-B0CB-D0A62C9E26CB]@0xfffffe001b56c000->0xfffffe001b5bbfff
dependency: com.apple.driver.IODARTFamily(1)[55309CB3-D624-3B9B-962A-E82571B663FC]@0xfffffe001cca4000->0xfffffe001ccb7fff
com.apple.driver.AppleInterruptController(1.0d1)[E7931F7A-8581-32B7-8A33-394B279B926C]@0xfffffe001bd7c000->0xfffffe001bd7ffff
dependency: com.apple.driver.AppleARMPlatform(1.0.2)[F784412E-33CC-3859-B0CB-D0A62C9E26CB]@0xfffffe001b56c000->0xfffffe001b5bbfff
last started kext at 389533987: com.apple.driver.AppleHIDKeyboard 224 (addr 0xfffffe001a368000, size 16384)
loaded kexts:
panic(cpu 1 caller 0xfffffe001b7b5798): "dart-disp0 (0xfffffe2333124000): SMMU(SMMU) error: SID 0 PTE invalid exception on read with DVA 0xc38000 (TTBR 0 SEG 0 PTE 0x30e) ERROR_STATUS 0x80000004 TIME 0x2152caac5b0 TTE 0 AXI_ID 0)"
This issue happens on a day-to-day basis now. I have replaced my Belkin USB 3 Hub with a LaCie Hub to try and see if the issue still persists. Yes, it does: first the mouse stops to move, then the display goes pink, and the MacBook restarts.
The issue does NOT happen when there is no Thunderbolt/USB Hub or Dock connected.
As I need peripherals like Ethernet, DisplayPort and USB 3 on my desk, I really don't know what to do to fix this issue.
I've tried any combination of connections: HDMI, DisplayPort, Belkin Ethernet (via Belkin USB 3 Media HUB), Apple Ethernet (via Apple USB Adaptor) …
The "dart-disp0" issue continues to happen and it's super embarrasing when working in home office and having several people in meetings.
This is incredibly frustrating and already disrupting my work significantly. I lost weeks worth of work due to this issue affecting my computer on a daily base.
I replaced my M1 MacBook Pro and the new computer had the same issue (even without restoring it from a backup).
How can we make Apple take responsibility here? Should we report this with TechInsider or a similar tech reviewer?
Macbook Air M1 - kernel panic