New 16" MacBook Pro M1 Max - Panic crash related to T6000-DART, is it Hardware?

[brosenz]

This is a brand new MacBook Pro M1 Max 16" 64GB 4TB, configured yesterday afternoon, installed typical apps, office, iStat Menus, Things, Webex, Xcode, AlDente, etc. No external devices connected (monitor, hard drives, etc.), only Magic Keyboard with TouchID and MX Master 3, both via Bluetooth. Only the MagSafe cable is connected to the laptop. I am running the latest macOS Monterrey 12.3.1.

Last night around 11PM I closed the lid, today, at 7AM, opened the lid, and it had crashed with a panic code related to the DART:

panic(cpu 0 caller 0xfffffe0024e97e58): "dart-ave1 (0xfffffe2000859800): DART(CPUDART) error: SID 0 PTE invalid exception on write of DVA 0x4939780 (TTBR 0 SEG 0x2 PTE 0x24e) ERROR_STATUS 0x80000404 TIME 0x2caa9782f708 TTE 0 AXI_ID 0x40" @AppleT6000DART.cpp:1407

Kernel Extensions in backtrace:
com.apple.driver.AppleT6000DART(1.0)[CDCFAD47-4549-3143-A8DC-1462E0222823]@0xfffffe0024e92b30->0xfffffe0024e99ed7
dependency: com.apple.driver.AppleARMPlatform(1.0.2)[9FD6A666-15C3-37F0-A577-FC27967A1628]@0xfffffe00241ee750->0xfffffe0024238d97
dependency: com.apple.driver.IODARTFamily(1)[2FAFEA37-DDFA-3307-9554-4C001EF5B572]@0xfffffe00257bbaf0->0xfffffe00257cf3f3

With less than 24 hours since purchased and a Panic/Crash error just a few hours after installed, related to the DART (T6000), it seem hardware related to me, should I get a replacement? Or do you think this is a software bug?

 

[basher]

A quick Internet search points to taking the system into Apple so they can take a deeper dive into the situation.

 

[LinkRS]

This is a brand new MacBook Pro M1 Max 16" 64GB 4TB, configured yesterday afternoon, installed typical apps, office, iStat Menus, Things, Webex, Xcode, AlDente, etc. No external devices connected (monitor, hard drives, etc.), only Magic Keyboard with TouchID and MX Master 3, both via Bluetooth. Only the MagSafe cable is connected to the laptop. I am running the latest macOS Monterrey 12.3.1.

Last night around 11PM I closed the lid, today, at 7AM, opened the lid, and it had crashed with a panic code related to the DART:

panic(cpu 0 caller 0xfffffe0024e97e58): "dart-ave1 (0xfffffe2000859800): DART(CPUDART) error: SID 0 PTE invalid exception on write of DVA 0x4939780 (TTBR 0 SEG 0x2 PTE 0x24e) ERROR_STATUS 0x80000404 TIME 0x2caa9782f708 TTE 0 AXI_ID 0x40" @AppleT6000DART.cpp:1407

Kernel Extensions in backtrace:
com.apple.driver.AppleT6000DART(1.0)[CDCFAD47-4549-3143-A8DC-1462E0222823]@0xfffffe0024e92b30->0xfffffe0024e99ed7
dependency: com.apple.driver.AppleARMPlatform(1.0.2)[9FD6A666-15C3-37F0-A577-FC27967A1628]@0xfffffe00241ee750->0xfffffe0024238d97
dependency: com.apple.driver.IODARTFamily(1)[2FAFEA37-DDFA-3307-9554-4C001EF5B572]@0xfffffe00257bbaf0->0xfffffe00257cf3f3

With less than 24 hours since purchased and a Panic/Crash error just a few hours after installed, related to the DART (T6000), it seem hardware related to me, should I get a replacement? Or do you think this is a software bug?

Howdy,

I am still looking, but an initial search found the following, regarding AlDente....

AlDente will cause a crash on the 12.2 system? - bytemeta

AlDente will cause a crash on the 12.2 system?

githubhot.com

If I find anything else, I will edit this post.

 

[brosenz]

Howdy,

I am still looking, but an initial search found the following, regarding AlDente....

AlDente will cause a crash on the 12.2 system? - bytemeta

AlDente will cause a crash on the 12.2 system?

githubhot.com

If I find anything else, I will edit this post.

It would be interesting to know if the 12.2 issues extend to 12.3.1 as well

 

[mr_roboto]

With less than 24 hours since purchased and a Panic/Crash error just a few hours after installed, related to the DART (T6000), it seem hardware related to me, should I get a replacement? Or do you think this is a software bug?

T6000/T6001 are Apple internal names for the M1 Pro and Max SoCs. Although you have a Max (T6001), many of the drivers are going to reference just "T6000" because they're shared between the two.

DART = Device Address Resolution Table. DART is Apple's IOMMU. In Apple Silicon, almost all IO coprocessors have their own private DART, which provides address virtualization and protection services similar to the CPU's MMU.

error: SID 0 PTE invalid exception on write of DVA 0x4939780 (TTBR 0 SEG 0x2 PTE 0x24e)

I interpret this to be a report that a DART caught an illegal write attempt by the device it's guarding.

This doesn't seem like a hardware issue, it's more likely to be a macOS bug. Or, if any of the software you've installed has kernel extensions, it could be in one of them. (You'll know if you installed a KEXT - these days it involves rebooting into Recovery to downgrade the computer's security mode and check a box to permit KEXTs to be loaded.)

 

[brosenz]

Thank you for the detailed explanation, it is good to know that it is likely not a hardware issue, I haven’t had any more crashes since, I have no kext installed

 

[kangaroosterus]

bronsenz - am having the same panic/reboot happening. Mine is a Macbook Air with 24GB running Ventura 13.0. Only have an external monitor (lightening cable with LG 5K monitor). I exchanged my laptop with an new one to rule out that it is not a hardware issue. Both the old and new laptops were running fine for about 2 weeks then once the issue started happening, it happened at least once a day. Seems like you are not having this issue as of your last post.

Is yours still working without issues? Can you remember what you may have done that fixed the issue?

 

[MayaUser]

I exchanged my laptop with an new one to rule out that it is not a hardware issue.

This way is not guarantee you isnt a hardware issue...remember the butterfly keyboard and so many other...hardware issues can be at larger scale so you can exchange and get a new one with the same issue
But this from the start isnt an hardware issue but a software one

 

[ackerthehacker]

The DART issue is an OS bug ...its been around for awhile ...reared its head back in 13.3 beta and probably wont be fixed until 13.4

 

[Rosember]

And it is still haunting me under Sonoma 14.0 and Sonoma 14.1. The crashes occur between once a week and 6 in a row separated by maybe 30 min. Is there still no solution or work around available? It is driving me nuts and has led to data losses.

 

[Rosember]

I recently observed that these panics could be related to charging non-intelligent devices (like LED lamps etc.) on USB ports of the Mac or hubs.
Unfortunately my experience is limited, but if others would check as well the result might become clearer.

Correction: After another series of crashes without loading anything over USB this hypothesis is falsified. Sorry.

 

[chucker23n1]

I just had it in Sonoma 14.4 (23E214).

I don't believe I've had a kernel panic in months, though, possibly not since Sonoma.