Studio Crash Restart

But on closer inspection,

the driver encountering the issue is a PCIe driver:

panic(cpu 0 caller ...): "apciec[pcic1-bridge]::handleInterrupt: Request address is greater than 32 bits linksts=0x99000001 pcielint=0x00020000 linkcdmsts=0x00000800 (ltssm 0x11=L0)\n" @AppleT8103PCIeCPort.cpp:1299

The Drivers 'at the scene of the crime' appear to be the ThunderBolt/ USB-C drivers AND the Apple T6000 Drivers and PCIe Drivers:

Kernel Extensions in backtrace:

com.apple.driver.AppleT6000PCIeC(1.0)[BC7AF2E6-9A13-34D7-A706-6827AAE09C79]@0xfffffe001eb39ee0->0xfffffe001eb52fab

dependency: com.apple.driver.AppleARMPlatform(1.0.2)[9FD6A666-15C3-37F0-A577-FC27967A1628]@0xfffffe001de8e750->0xfffffe001ded8d97

dependency: com.apple.driver.AppleEmbeddedPCIE(1)[9898076D-EB41-3651-9484-85E6DF1F354A]@0xfffffe001e448e50->0xfffffe001e45912f

dependency: com.apple.driver.ApplePIODMA(1)[C6FCAF36-580C-3DEA-BE40-82DB15E5BD5F]@0xfffffe001e856af0->0xfffffe001e85b387

dependency: com.apple.driver.IODARTFamily(1)[2FAFEA37-DDFA-3307-9554-4C001EF5B572]@0xfffffe001f45baf0->0xfffffe001f46f3f3

dependency: com.apple.iokit.IOPCIFamily(2.9)[2DC5887C-F4D0-3C8F-B96A-C920B5CDE175]@0xfffffe001f7d3760->0xfffffe001f7f1d2b

dependency: com.apple.iokit.IOReportFamily(47)[BD0867F7-DE61-3E4D-ABBE-25CBAD925319]@0xfffffe001f7f1d30->0xfffffe001f7f4d53

dependency: com.apple.iokit.IOThunderboltFamily(9.3.3)[03AA55D8-4EDB-35AA-B7A1-D3298B2ACD9B]@0xfffffe001f8f2c60->0xfffffe001fa16663

last started kext at 5283050638: com.editshare.EFS.filesystems.efsfuse 2113.20 (addr 0xfffffe001cac1a60, size 6320)

-------

so the best thing to do first would be to be sure you are using the latest MacOS if possible, then be certain all the drivers for all your complex hardware is completely up-to-date.

the reason for my question is that you have drivers for BOTH sonnet Ethernet and Aquantia Ethenrt loaded, and I thought that might cause issues:

loaded kexts:

com.editshare.EFS.filesystems.efsfuse 2113.20

com.sonnet.driver.SonnetEthernet-10GE 1.8.0

com.apple.filesystems.autofs 3.0

com.apple.AppleEthernetAquantiaAqtionFirmware 1.0.36

...

it's not obvious to my eye.

I though that if you could switch to the built-in 10G Ethernet-over-copper (said to be good for up to 30 meters, and probably longer), you could reduce complexity. But that may not be the issue at all, and you may not have a 10G copper port on your Switch.

Other than that the standard practice of making sure MacOS is completely up-to-date and all your drivers as well means you are not trying to debug already-solved issues.

You could also consider running the diagnostic.

If nothing improves, you may need to contact Apple support, work through their initial checklist, then ask for a specialist. They can refer to stuff like crash reports posted here, but they never use our conclusions (yours or mine) -- they investigate from scratch for themselves. For complex problems, don't bother with online chat.

Official Apple Support

so are you connecting using fiber-optic cables or 10G Ethernet over copper?

are you making two Ethernet connections or one?

"regular" Apple support (non-chat) is staffed by what senior contributors here on the forums call, "first responders". They do an amazing job of patiently working through a checklist of obvious issues with you. They may have additional insights.

When you have exhausted their expertise, they can call in a specialist in the area of interest to explore further. Specialists are not sitting around, they may need to call you back later. Specialists have a deeper understanding, but FAR less patience.

All can refer to what you have posted on the forums, but they do not take our word for anything -- they have their own more rigorous methods for researching these issues.

To get your problem solved, don't let anyone tell you it's fixed until it really IS fixed, or they file a Bug Report on your behalf. Engineering works on fixing well-documented Bug Reports.

yes, that is what they are set up for.