Big Sur panic when connect/disconnect usb-c dock

I've been having the same issue. Dell monitors have this weird features such as MST and DP 1.2. Turn it off and see if it works see full list: https://www.dell.com/community/Monitors/Single-monitor-on-a-PC-MST-Off-DisplayPort-1-2-Disable/td-p/6131242

(you turn this off in the screen options that is built in, not on the mac)

Model Name:	MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports)
Model Identifier:	MacBookPro16,2
Processor Name:	Quad-Core Intel Core i5
Processor Speed:	2 GHz
Number of Processors:	1
Total Number of Cores:	4
L2 Cache (per Core):	512 KB
L3 Cache:	6 MB
Hyper-Threading Technology:	Enabled
Memory:	32 GB

Still experiencing this issue and this is not while I'm connected to an external display. It happens when I spin up Docker for work and when I attempt to do something else that requires streaming i.e. pairing on a task via something like Tuple or Slack or even streaming YouTube music.

This has also happened when connected to an external display and/or connected via SideCar to my iPad

+1 on all of that. Crashes AT LEAST once a day. Thankfully to this thread I can save myself a trip to the apple store.

HI, I see the last incidence of this was from 5 months ago, but I'm having it. I have updated my mac to the latest version (11.6) and it systematically reboots when the laptop is closed (sleeping) and I connect it to a DELL dock. Here's the report.

panic(cpu 5 caller 0xffffff8000e9edf6): [kext.kalloc.2048]: element modified after free (off:1672, val:0xfffffffe00000000, sz:2048, ptr:0xffffff937a255800, prot:zero) 1672: 0xfffffffe00000000 Backtrace (CPU 5), Frame : Return Address 0xffffffa12a1929b0 : 0xffffff800068cfdd 0xffffffa12a192a00 : 0xffffff80007d3fd3 0xffffffa12a192a40 : 0xffffff80007c45ca 0xffffffa12a192a90 : 0xffffff8000631a2f 0xffffffa12a192ab0 : 0xffffff800068c7fd 0xffffffa12a192bd0 : 0xffffff800068caf3 0xffffffa12a192c40 : 0xffffff8000e9cdca 0xffffffa12a192cb0 : 0xffffff8000e9edf6 0xffffffa12a193130 : 0xffffff80006eb976 0xffffffa12a1931a0 : 0xffffff800069c5ec 0xffffffa12a1931f0 : 0xffffff8000dada32 0xffffffa12a193210 : 0xffffff800375d84c 0xffffffa12a193230 : 0xffffff800376bb08 0xffffffa12a193290 : 0xffffff800375dfd4 0xffffffa12a193330 : 0xffffff80037600a7 0xffffffa12a1935e0 : 0xffffff800375e4d9 0xffffffa12a193740 : 0xffffff8003755981 0xffffffa12a193c50 : 0xffffff8000e86af4 0xffffffa12a193ce0 : 0xffffff8000920e40 0xffffffa12a193d40 : 0xffffff8000936d56 0xffffffa12a193f40 : 0xffffff8000d3f1de 0xffffffa12a193fa0 : 0xffffff80006321f6 Kernel Extensions in backtrace: com.apple.security.sandbox(300.0)[1E5C48E7-0D4C-30DA-BFA4-C87B27353F0D]@0xffffff800374c000->0xffffff8003792fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A994AEFE-3919-310E-A2C9-405E864BCB7B]@0xffffff8001cc0000->0xffffff8001cd5fff dependency: com.apple.iokit.IOStorageFamily(2.1)[7C0E4949-640F-3D1D-97AF-030903A22663]@0xffffff800326f000->0xffffff8003280fff dependency: com.apple.kext.AppleMatch(1.0.0d1)[EAD07327-D5B8-36D8-B3CC-DBEE8E4EE295]@0xffffff8001cbc000->0xffffff8001cbefff

Process name corresponding to current thread: NotificationCenter Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version: 20G165

Kernel version: Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT 2021; root:xnu-7195.141.6~3/RELEASE_X86_64 Kernel UUID: C2591F4E-EE82-33CC-8C59-DB81D9AD80DD KernelCache slide: 0x0000000000400000 KernelCache base: 0xffffff8000600000 Kernel slide: 0x0000000000410000 Kernel text base: 0xffffff8000610000 __HIB text base: 0xffffff8000500000 System model name: MacBookPro16,1 (Mac-E1008331FDC96864) System shutdown begun: NO Hibernation exit count: 26

System uptime in nanoseconds: 17717902905029 Last Sleep: absolute base_tsc base_nano Uptime : 0x0000101d454f11d3 Sleep : 0x0000101acfea5760 0x000009c937ae70e6 0x000010050575280f Wake : 0x0000101b01527036 0x00000a14da9d9e62 0x0000101ae0a7ca49 last started kext at 12580617391: >AGPM 122.1 (addr 0xffffff7f99da9000, size 118784) loaded kexts:

AGPM 122.1 !APlatformEnabler 2.7.0d0 X86PlatformShim 1.0.0

@filesystems.autofs 3.0 @fileutil 20.036.15

AudioAUUC 1.70 !ATopCaseHIDEventDriver 4050.1 !AHIDALSService 1

@kext.AMDRadeonX6000 4.0.6 @kext.AMDRadeonServiceManager 4.0.6

!AGraphicsDevicePolicy 6.3.5 !AUpstreamUserClient 3.6.8

@AGDCPluginDisplayMetrics 6.3.5

pmtelemetry 1

|IOUserEthernet 1.0.1

!ABridgeAudio!C 140.4 !AFIVRDriver 4.1.0 ACPI_SMC_PlatformPlugin 1.0.0 usb.!UUserHCI 1 BridgeAudioCommunication 140.4 !AGFXHDA 100.1.433 !AAVEBridge 6.1 !AThunderboltIP 4.0.3 !A!IKBLGraphics 16.0.5

|IO!BSerialManager 8.0.5d7 @Dont_Steal_Mac_OS_X 7.0.0

!AHV 1 !ADiskImages2 1 !AMuxControl2 6.3.5 !AWWANSupport1 4.0.0 !A!ICFLGraphicsFramebuffer 16.0.5 !A!IPCHPMC 2.0.1 AGDCBacklightControl 6.3.5 !ABacklight 180.3 !AMCCSControl 1.14 !A!ISlowAdaptiveClocking 4.0.0 !AWWANSupport 4.0.0 usb.realtek8153patcher 5.0.0 BCMWLANFirmware4378.Hashstore 1 BCMWLANFirmware4377.Hashstore 1 BCMWLANFirmware4364.Hashstore 1 BCMWLANFirmware4355.Hashstore 1 !AFileSystemDriver 3.0.1

@filesystems.tmpfs 1 @filesystems.hfs.kext 556.100.11 @BootCache 40 @!AFSCompression.!AFSCompressionTypeZlib 1.0.0 @!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1

!ABCMWLANBusInterfacePCIeMac 1

@filesystems.apfs 1677.141.2 @private.KextAudit 1.0

!ASmartBatteryManager 161.0.0 !AACPIButtons 6.1 !ASMBIOS 2.1 !AACPIEC 6.1 !AAPIC 1.7

@!ASystemPolicy 2.0.0 @nke.applicationfirewall 311 |IOKitRegistryCompatibility 1 |EndpointSecurity 1 @kext.triggers 1.0

!AHIDKeyboard 224 !AActuatorDriver 4440.3 !AMultitouchDriver 4440.3 !AInputDeviceSupport 4400.35 !AHS!BDriver 4050.1 IO!BHIDDriver 8.0.5d7

@kext.AMDRadeonX6100HWLibs 1.0 @kext.AMDRadeonX6000HWServices 4.0.6

IOPlatformPluginLegacy 1.0.0 X86PlatformPlugin 1.0.0 usb.cdc.acm 5.0.0 usb.serial 6.0.0

|IO!BHost!CUARTTransport 8.0.5d7 |IO!BHost!CTransport 8.0.5d7 @kext.AMDRadeonX6000Framebuffer 4.0.6 @kext.AMDSupport 4.0.6

!AHDA!C 283.15

|IOHDA!F 283.15

!AThunderboltEDMSink 5.0.3

|IOAVB!F 940.4 |IOEthernetAVB!C 1.1.0

!AGraphicsControl 6.3.5

|IOAccelerator!F2 442.9

IOPlatformPlugin!F 6.0.0d8

@!AGPUWrangler 6.3.5 @!AGraphicsDeviceControl 6.3.5

!ABacklightExpert 1.1.0

|IONDRVSupport 585.1 |IOGraphics!F 585.1

!ASMBus!C 1.0.18d1

@plugin.IOgPTPPlugin 985.2

!UAudio 405.39

|IOAudio!F 300.6.1 @vecLib.kext 1.2.0

!ASMBusPCI 1.0.14d1 !A!ILpssUARTv1 3.0.60 !A!ILpssUARTCommon 3.0.60 !AOnboardSerial 1.0

I was able to fix this panic by disabling "DP Daisy Chain" in monitor options. Was experiencing daily crashes after unplugging monitor, which was black after "unsuccessful" connection. My specs:

• MacBook Pro (16-inch, 2019), 2.6 GHz 6-Core Intel Core i7, 32 GB 2667 MHz DDR4, AMD Radeon Pro 5300M 4 GB
• Lenovo P24h-10 via Type-c

I connect my Macbook pro(16 inch with BigSur 11.6) to Dell P2717HC monitor through usb c type.
Macbook pro crashes unexpectedly and even I tried to reconnect 2-3 times continuously.

After I changed MST to off in my Dell monitor Display option. I tried to plug and unplug usb c type connectivity 10 times in my Macbook pro, I have not faced crashing.

I have been encountering this problem in my Macbook Pro 16" i7 and it was really frustrating.

I would like to share that it never happen again after I upgraded to OSX Monterey. I can now connect my Macbook and it works fine, regardless if it is sleeping or not.

Monterey is still not released officially but the beta is beta available for developer & public preview. If you dont want to go unofficial, just hold tight and sooner, this thread will be closed (hopefully).

Same here, 16" MBP (2019) and Radeon Pro 5500M 8GB; I keep encountering the same crash message when I connect my monitor via one of the DP ports on my HP Thunderbolt 3 Dock G2. The dock firmware is up to date. Using the Thunderbolt port to connect my monitor will not cause any crashes.

My 15" MBP (2017) is rock solid with the same dock & monitor setup, no matter how many times I plug and unplug, there are no crashes at all.

I've had the same issue for well over a year - though at least two of three majors versions of the OS ... but the panic has moved to different stack traces - initially in the AMD driver, and not in com.apple.WebKit.Networking ... I can just about re-produce this issue on demand. I'm running dual 4k monitors via DisplayPort, both connected to a CalDigit USB-C Pro dock. I've been in active communication with CalDigit about the issue, and of course, they say it's an apple issue.

I've conducted an experiment -  I got two different brands for USB-C to DisplayPort adaptors, and ran one monitor via the Thunderbolt 3 USB-C Pro Dock, and one via an adaptor directly connected to to a second USB-C port of the MacBook Pro. I did not have a single panic, nor did I have issues with the mac detecting both displays for a couple weeks. (I also ran with both displayPort monitors on USB-C-DisplayPort adaptors, and none connected to the dock, without panics.)

Last night, I put the second display back on the USB-C Pro Dock. Within 12- hours … I now have had a mis-sync of the monitors … one monitor detected, the other was not. Disconnecting and reconnecting the displayPort on the missing monitor - both monitors got detected, but then 1-2 minutes later - the system panicked within the com.apple.WebKit.Networking thread.

I've send nearly every single one in on a report, and was putting additional comments on how to reproduce ... it's annoying that this is continuing.

The work around, of course, seem to simply not do single cable, dual-monitor docking. I'm eye some of the eGPU chassises, as I already have some AMD 580s laying around, from a retired hackintosh experiment, currious if this would bypass the issue. It seems to indicate to me, that this is something to do specially with the USB-C DisplayPort™ Alternate Mode when using the dual channels on a single cable.

But why com.apple.WebKit.Networking ?

panic(cpu 2 caller 0xffffff800b09edf6): [kext.kalloc.2048]: element modified after free (off:1672, val:0xfffffffe00000000, sz:2048, ptr:0xffffff9366d74800, prot:zero)
 1672: 0xfffffffe00000000
[ … ]
0xffffffb0d4c3bfa0 : 0xffffff800a8321f6 
   Kernel Extensions in backtrace:
     com.apple.security.sandbox(300.0)[1E5C48E7-0D4C-30DA-BFA4-C87B27353F0D]@0xffffff800d94c000->0xffffff800d992fff
      dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A994AEFE-3919-310E-A2C9-405E864BCB7B]@0xffffff800bec0000->0xffffff800bed5fff
      dependency: com.apple.iokit.IOStorageFamily(2.1)[7C0E4949-640F-3D1D-97AF-030903A22663]@0xffffff800d46f000->0xffffff800d480fff
      dependency: com.apple.kext.AppleMatch(1.0.0d1)[EAD07327-D5B8-36D8-B3CC-DBEE8E4EE295]@0xffffff800bebc000->0xffffff800bebefff

Process name corresponding to current thread: com.apple.WebKit.Networking
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20G165

Model Name:	MacBook Pro
 Model Identifier:	MacBookPro16,1
 Processor Name:	6-Core Intel Core i7
  Processor Speed:	2.6 GHz
AMD Radeon Pro 5300M:
Chipset Model:	AMD Radeon Pro 5300M

I've been having the same issue. Dell monitors have this weird features such as MST and DP 1.2. Turn it off and see if it works see full list: https://www.dell.com/community/Monitors/Single-monitor-on-a-PC-MST-Off-DisplayPort-1-2-Disable/td-p/6131242

(you turn this off in the screen options that is built in, not on the mac)

This did help for me, for people who may not see.

I have this kernel crash repeatedly. as often as 2 times a day, though not every day since I moved to a CalDigit TB3+ dock and added a second display (so for 6+ month). For about a year I was using an Anker 13-in-1 dock with a single monitor without issues. The anker dock would not support a second display at all (no matter what I tried including working with Anker who said it should work, and it does on my wife's 13" from 2017), so I replaced the dock with CalDigit which appeared to work but I started having these kernel panics. Most commonly when coming out of sleep, or if I disconnect and reconnect the dock. I have a 2019 16" MBP i7 model. It primarily is plugged in 24x7, I rarely move it.

I have 2x Thinkpad p27h-10 displays. 1 connected to the dock on USB-c, the other on display port.

After seeing this post about display port daisy chaining being enabled, I checked and one of the 2 displays in fact had this on. (I tried to initially configure this without docks to daisy chain before I noted though this chipsets support it OS X does not). I will monitor this, and come back here if I continue to have kernel panics now that DP chaining is off. I wonder if the daisy chaining was also preventing the Anker dock from seeing the display.

Similar problem here:

• Macbook Pro 2019
• Big Sur 11.6,
• USB-C Hub: https://www.amazon.com/gp/product/B08DHKMQ1D/
• Hisense H8G as monitor
• 4K HDR 60hz HDMI connection

Whenever my laptop wakes while attached to this hub AND this hub is connected to my Hisense H8G via HDMI, the fan spins up to top speed for 1-2 seconds and then crashes (kernel panic). Sometimes it happens without sleep/wake, but sleep/wake is the guaranteed way to make it happen.

I'm convinced the problem is related solely to the display connection aspect of this connection. If I remove the HDMI cable, but keep the USB-C hub connected, the problem does not persist.

I did not experience this on Catalina. This only occured once I upgraded to Big Sur.

I confirmed the following things that were suggested above:

• Automatic Graphics Switching: off
• Power Nap: off
• I don't have any daisy chain or similar options on my H8G
• I don't have any DisplayPort or associated settings on my H8G

I have the same issue with a MB 16" and a HP G2 docking station with two LG 27" 4K monitors connected to the dock via usb-c. Whenever waking up the Macbook from sleep or when changing something with the cabling, the Macbook panics.

For me there is a work-around however; I keep the first LG monitor connected via usb-c to the thunderbolt port of the dock. The second monitor was connected via usb-c to the usb-c/displayport port of the dock. I switched the single usb-c cable to a plain display-port cable plus additional usb-c to usb-a cable (so I can still use the usb-hub functionality of the monitor). With this setup the panics are gone (fingers crossed).

HTH

I know it's too early, but apparently, the update to Monterey has fixed this for me, it seems. Fingers crossed.

2 days without crashes after upgrading to Monterey. Is this real??? I mean it is too good to be true, right ?

Same here, no more crashes since Monterey upgrade.

Hate to burst your bubble, but the problem still exists in Monterey. It may happen less frequently. It took a week before I hit my first crash, and then it crashed about 5 times in the next 2 days. Then I went about 1.5 weeks and now its crashing multiple times a day again. Exact same stack trace as before.

Also seems to be resolved in :

  System Version: macOS 12.0.1 (21A559)   Kernel Version: Darwin 21.1.0

Been running a week or so with 12.0.1 and back connected to the CalDigit USB-C Pro Dock - single cable Thunderbolt 3 docking, leveraging both DisplayPort connectors at 4k @ 60Hz. It takes an insanely long time for the monitors to re-sync after blanking (I think I prohibit sleep), but no more panics.

However, now web-cams plugged in via the Thunderbolt 3 dock - no longer work. With a simple passive USB-C -> USB-A adaptor, they do work fine. sigh. (so much for single cable docking).

This issue still persists for me in 11.6.1 on a daily basis, is there any known workaround (other than switching to a different computer manufacturer or upgrading a feature release?).

To pour more fire on this flame, yes, this is 100% reproducible in Big Sur 11.6. Plugged into Caldigit hub with external monitor via displayport. Cycling the power a few times on the hub will trigger it. Or waiting for the laptop to sleep overnight. I've been sending crashdumps every night for a week, if anyone at Apple feels like looking into it.

This has been happening for awhile. I am hating the idea but did they just release new macs with ports again and suddenly docs are not working?

Mac Crash 24 nov 7:56am

panic(cpu 4 caller 0xffffff800bfc5396): Kernel trap at 0xffffff800c461e4e, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffdf9359e5a800, CR3: 0x00000002c6bb41da, CR4: 0x00000000003626e0 RAX: 0xffffdf9359e5a800, RBX: 0x0000000000000000, RCX: 0xffffff86a7726100, RDX: 0x00000000fade0c02 RSP: 0xffffffb0c540b910, RBP: 0xffffffb0c540b910, RSI: 0x0000000000000000, RDI: 0xffffff935aed0d00 R8: 0xffffffa05a52f908, R9: 0x00000000000007d0, R10: 0x000000044b8b6bbc, R11: 0x0000000000000000 R12: 0xffffffb0c540ba78, R13: 0xffffff935aed0d00, R14: 0x00000000000000e0, R15: 0xffffff86912ceac0 RFL: 0x0000000000010202, RIP: 0xffffff800c461e4e, CS: 0x0000000000000008, SS: 0x0000000000000000 Fault CR2: 0xffffdf9359e5a800, Error code: 0x0000000000000000, Fault CPU: 0x4, PL: 0, VF: 1

Backtrace (CPU 4), Frame : Return Address 0xffffffb0c540b330 : 0xffffff800be8d25d  0xffffffb0c540b380 : 0xffffff800bfd49d3  0xffffffb0c540b3c0 : 0xffffff800bfc4fca  0xffffffb0c540b410 : 0xffffff800be31a2f  0xffffffb0c540b430 : 0xffffff800be8ca7d  0xffffffb0c540b550 : 0xffffff800be8cd73  0xffffffb0c540b5c0 : 0xffffff800c69d8fa  0xffffffb0c540b630 : 0xffffff800bfc5396  0xffffffb0c540b7b0 : 0xffffff800bfc507d  0xffffffb0c540b800 : 0xffffff800be31a2f  0xffffffb0c540b820 : 0xffffff800c461e4e  0xffffffb0c540b910 : 0xffffff800c3e9f44  0xffffffb0c540b930 : 0xffffff800d85911a  0xffffffb0c540ba60 : 0xffffff800d85bd14  0xffffffb0c540bbd0 : 0xffffff800d8637e0  0xffffffb0c540bc50 : 0xffffff800c69a270  0xffffffb0c540bc80 : 0xffffff800c3edd1c  0xffffffb0c540bd10 : 0xffffff800c3f4ef4  0xffffffb0c540bd50 : 0xffffff800c41413f  0xffffffb0c540be00 : 0xffffff800becd7de  0xffffffb0c540be90 : 0xffffff800bed1a10  0xffffffb0c540bec0 : 0xffffff800be84743  0xffffffb0c540bef0 : 0xffffff800be319fb     Kernel Extensions in backtrace:      com.apple.iokit.EndpointSecurity(1.0)[A69AA270-6627-36D9-A0E1-53A23457AE51]@0xffffff800d84f000->0xffffff800d89efff       dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[61A199C8-BE3B-3351-84B8-266A6A43632F]@0xffffff800d4c0000->0xffffff800d4d5fff       dependency: com.apple.security.quarantine(4)[881FE459-BBDC-3E19-BBF8-2D58415A2AE9]@0xffffff800ef42000->0xffffff800ef49fff

Process name corresponding to current thread: MTLCompilerService

Mac OS version: 20G224

My Macbook Model is 'MacBook Pro (16-inch, 2019)' and OS is 'Monterey 12.0.1(21A559)' The fan suddenly starts spinning quickly, and it reboots. It happens once every few hours. I am currently neurotic. So, I am using it with only power connected to the MacBook. What happens when this happens on a DELL laptop? They come to my seat and fix my laptop. For a dell laptop the same price as the macbook pro, it's 100%. I think all the devices designed and built by Apple are great, but they need a lot of improvement in terms of after-sales support.

Updated to OS11.6. Still crashes with monitor attached through HP Docking station to MBP 2019, 16". It is as decribed above, with no fix in sight. Not satisfying, Apple.

Same here, on 11.6.1. Sometimes crashes, sometimes not, when plugging back to my dell dock-station / Dell screen with my MacBook Pro (16-inch, 2019). (also fan spin at their maximum just before the reboot).

This is really annoying. Isn't there any monitor driver we could force update to fix the issue?

Come on Apple, get your sh*t together and fix this. It's been happening for months on every version for every user that has a MBP 16" and uses a dock.