Big Sur panic when connect/disconnect usb-c dock

This also happens to me. Currently using the "Wavlink Dual 5K Type-C Laptop Universal Docking Station" and for the past few days, my Intel MBP 2019 (that's on MacOS Monterey 12.0.1) keeps panicking with the following message:

panic(cpu 0 caller 0xffffff8016c411e1): AppleIntelFramebuffer::setPowerState(0xffffffa05e091000 : 0xffffff7fae96d8a8, 2 -> 1) timed out after 45438 ms @IOServicePM.cpp:5524
Panicked task 0xffffff856b3d46a0: 320 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff856f83c2c0, Frame : Return Address
0xffffffd070233ab0 : 0xffffff801649c00d 
0xffffffd070233b00 : 0xffffff80165f5d85 
0xffffffd070233b40 : 0xffffff80165e5763 
0xffffffd070233b90 : 0xffffff801643ba60 
0xffffffd070233bb0 : 0xffffff801649c3dd 
0xffffffd070233cd0 : 0xffffff801649bb96 
0xffffffd070233d30 : 0xffffff8016d18649 
0xffffffd070233da0 : 0xffffff8016c411e1 
0xffffffd070233e00 : 0xffffff8016c409a9 
0xffffffd070233e10 : 0xffffff8016c59f8e 
0xffffffd070233e50 : 0xffffff8016c3f738 
0xffffffd070233e70 : 0xffffff80164ecc85 
0xffffffd070233ee0 : 0xffffff80164edcd2 
0xffffffd070233fa0 : 0xffffff801643b18e 

Process name corresponding to current thread (0xffffff856f83c2c0): kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21A559

Kernel version:
Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64
Kernel UUID: 19BD4E1B-0268-3EE0-BC66-91F035BC9429
KernelCache slide: 0x0000000016200000
KernelCache base:  0xffffff8016400000
Kernel slide:      0x0000000016210000
Kernel text base:  0xffffff8016410000
__HIB  text base: 0xffffff8016300000
System model name: MacBookPro16,1 (Mac-E1008331FDC96864)
System shutdown begun: NO
Hibernation exit count: 0

System uptime in nanoseconds: 21793280334665
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000013d224bba35a
  Sleep   : 0x000005119c4ed4cb 0x00000ca5a50b0d34 0x000004fe2033b80e
  Wake    : 0x00000511b0309208 0x00000cd494d92efa 0x00000511aec95730
Zone info:
Foreign   : 0xffffff802c664000 - 0xffffff802c671000
Native    : 0xffffff805db35000 - 0xffffffa05db35000
Readonly  : 0 - 0
Metadata  : 0xffffffee7aab2000 - 0xffffffee9adc7000
Bitmaps   : 0xffffffee9adc7000 - 0xffffffeea6dc7000
last started kext at 21763387631930: >usb.cdc.acm  5.0.0 (addr 0xffffff7fae62f000, size 12288)
last stopped kext at 3634636454435: com.rugarciap.DisableTurboBoost    0.0.1 (addr 0xffffff7faf8ee000, size 4096)

MBP 16" 2019 running Big Sur 11.6.1 and I’m using CalDigit dock with 2 monitors connected via USB-C and DisplayPort. Mac panics almost daily since the very first day I got this MBP (August 2020). Please, FIX THIS!

Same problem with HP thunderbolt with my Mac. Is there a solution for this ?

This issue has been fixed for me since updating to Monterey / OS 12.

2019 16 inch MBP with a Belkin Thunderbolt 3 Pro Dock, Dell U3818DW monitor, and DisplayPort between the dock and monitor.

I had this problem for months. I used to have a  Dell WD19 Docking station, pure USB-C no Thunderbolt and the only solution was to replace it with a Satechi - Thunderbolt 4 Dock - Model: ST-UCT4DM, it doesn't present any problems as of now. And I have stated in a previous comment that this only happened to my newest MBP MacBook Pro (16-inch, 2019) Processor 2.4 GHz 8-Core Intel Core i9 Memory 64 GB 2667 MHz DDR4 Graphics AMD Radeon Pro 5500M 8 GB Intel UHD Graphics 630 1536 MB Other older MBP didn't present this problem. Apple should provide a better solution other than having users buy new hardware and take responsibility for what seems a compatibility problem.

I've got MacBook Pro (16-inch, 2019) 2.6 GHz 6-Core Intel Core i7 32 GB 2667 MHz DDR4 MD Radeon Pro 5300M 4 GB Intel UHD Graphics 630 1536 MB running 11.6.2 (20G314) and I am having the same problem when plugging into my Belkin Thunderbolt 3 Express Dock HD - Docking station - (Thunderbolt 3) - GigE - 170 Watt . I noticed that sometimes it crashes even with all monitors unplugged. Everything works perfectly fine without the docking station (two 4k monitors via usb-c, 1 GB lan).

I did not have any problems like this in the past with older MacBook Pro 14-inch (2018) running on Catalina.

MacBook Pro (16-inch, 2019) 2.4 GHz 8-Core Intel Core i9 64 GB 2667 MHz DDR4 AMD Radeon Pro 5500M 8 GB

Experienced the issue since 11.3.1 on Big Sur, upgrade to Monterey 12.1 and haven't had the issue since.

Running Mac OS 11.6.2 and have been chasing this issue for multiple weeks. Every time I go through a sleep/wake cycle, if the Mac was removed from the Dock (and sometimes when it is re-attached to the dock) the Mac power cycles and throws a crash report, which I dutifully submit to Apple.

Given that this is A) widespread and ongoing for weeks across all M1 models on Big Sur 11.3 and later, and given that Big Sur is no longer being supported fully by Apple (e.g., they've moved on to Monterey) the conclusion I reach is that they will not be fixing this, which is disappointed. We could summarize the passive reply from Apple as follows:

"Sorry, but our defective operating system will not be fixed. Please update to our next buggy operating system, Monterey, and maybe the issue will be fixed there."

This is seriously disappointing, of course. Apple supposedly supports the current OS and the previous 2, but in this case all available info from Apple and the support community leads to the conclusion that updating to Monterey is the only way to regain stability on the Mac M1 platform. Lost data? Lost reliability? Lost of confidence? Apple: "we don't care."

Having the same issues on all my work laptops which sucks. Means that I can’t use my setup. This needs to be fixed Apple. I’ve submitted these requests for more than a year now. This is not acceptable and shows everyone that you’ve pushed us to use Thunderbolt but then don’t even support it properly.

I receive panic(cpu 1 caller 0xfffffff01d67a024): x86 CPU CATERR detected at least daily on my MacBook Pro (16-inch, 2019), which is connected via TB3 to a Samsung monitor with a hub built-in.

I have a MacBook Pro (15-inch, 2018) connected in the same way, using the same cable, connected to the same model of monitor, and it never has a problem - this is obviously a hardware issue with the 16-inch 2019 models based on all the messages here.

The 2019 model is my work system, so I am currently held back to Monterey 12.0.1, but experienced these issues in Catalina as well.

Full panic snippet:

panic(cpu 1 caller 0xfffffff01d67a024): x86 CPU CATERR detected
Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 19P549
macOS version: 21A559
Kernel version: Darwin Kernel Version 21.1.0: Wed Oct 13 18:09:06 PDT 2021; root:xnu-8019.41.5~2\/RELEASE_ARM64_T8010
Kernel UUID: 5206FA9B-BD6D-381D-A198-5F6E6A09B67F
iBoot version: iBoot-7429.41.4
secure boot?: YES
x86 EFI Boot State: 0x16
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0x1
x86 Previous Power Transitions: 0x70707060400
PCIeUp link state: 0x89271614
Paniclog version: 13
Kernel slide:      0x00000000155ec000
Kernel text base:  0xfffffff01c5f0000
mach_absolute_time: 0x7e76f1e08f0
Epoch Time:        sec       usec
  Boot    : 0x61d86dce 0x0002483c
  Sleep   : 0x00000000 0x00000000
  Wake    : 0x00000000 0x00000000
  Calendar: 0x61ddf443 0x000712f6

Zone info:
Foreign   : 0xfffffff0741b4000 - 0xfffffff0741c4000
Native    : 0xffffffe0003b8000 - 0xffffffe6003b8000
Readonly  : 0 - 0
Metadata  : 0xffffffeb009c8000 - 0xffffffeb04b98000
Bitmaps   : 0xffffffeb021c8000 - 0xffffffeb02430000
CORE 0: PC=0xfffffff01cf119f8, LR=0xfffffff01d51a220, FP=0xffffffeb0faebd50
CORE 1 is the one that panicked. Check the full backtrace for details.
Panicked task 0xffffffe0f2c74658: 0 pages, 230 threads: pid 0: kernel_task
Panicked thread: 0xffffffe0f35d8000, backtrace: 0xffffffeb0ee83670, tid: 426
          lr: 0xfffffff01cdd7388  fp: 0xffffffeb0ee836b0
          lr: 0xfffffff01cdd7118  fp: 0xffffffeb0ee83720
          lr: 0xfffffff01cf0feac  fp: 0xffffffeb0ee837a0
          lr: 0xfffffff01cf0f03c  fp: 0xffffffeb0ee83850
          lr: 0xfffffff01d4395fc  fp: 0xffffffeb0ee83860
          lr: 0xfffffff01cdd6e2c  fp: 0xffffffeb0ee83bf0
          lr: 0xfffffff01cdd6e2c  fp: 0xffffffeb0ee83c50
          lr: 0xfffffff01df2b488  fp: 0xffffffeb0ee83c70
          lr: 0xfffffff01d67a024  fp: 0xffffffeb0ee83ca0
          lr: 0xfffffff01d666f5c  fp: 0xffffffeb0ee83d00
          lr: 0xfffffff01d66d410  fp: 0xffffffeb0ee83d50
          lr: 0xfffffff01d668e48  fp: 0xffffffeb0ee83df0
          lr: 0xfffffff01d666640  fp: 0xffffffeb0ee83e70
          lr: 0xfffffff01d518db4  fp: 0xffffffeb0ee83ea0
          lr: 0xfffffff01d37f3a4  fp: 0xffffffeb0ee83ee0
          lr: 0xfffffff01d37ebb4  fp: 0xffffffeb0ee83f20
          lr: 0xfffffff01d4445a0  fp: 0x0000000000000000

I have been dealing with this issue for months; multiple kernel panic/crashes per day any time I dock or un-dock via USB-C. I just upgraded from Big Sur to Monterey 12.1 (since Apple wouldn't open a support case for me until I did that) - and it actually hasn't had the issue since then. I have docked and undocked several times, even quickly, with no crash. So, if upgrading the OS is an option, give it a try.

12.1 works! My office just approved 12.1 this week and I was able to upgrade beyond 12.0.1. I haven't had a kernel panic in days, and I've been able to keep my lid closed and wake it with my bluetooth keyboard.

This has been widespread between several of our companies iMac's. This is the latest error

. Search again for panic(cpu 2 caller 0xffffff8003a4cc9b): "can't have a namedstream vnode without a valid name\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/d7e177bcf5/Library/Caches/com.apple.xbs/Sources/apfs/apfs-1677.141.1/kext/apfs_vfsutils.c:297 Backtrace (CPU 2), Frame : Return Address 0xffffffa1a8762bd0 :

It's different than the others. Does "can't have a namedstream vnote without a valid name" sound like a different issue? Hoping someone has resolved this before.

One of the other iMac's won't get passed the apple at startup. Tried starting it in recovery but it won't respond to any keys being pressed after cutting the power for over 10 seconds. Ready to pull my hair out dealing with all these issues! Come on apple! Get some answers to the loyal supporters who would only change away if it's forced through issues like these!

Since updating to MacOS to 12.2, my MacBook Pro Intel 2020 is crashing most of the time when disconnecting from a Dell WD19TB docking station. I only rarely had this problem before 12.2.

I have save issue with a mac mini m1, Moneterey 12.2.1, apple I need my money back, f this shit.

I was having the "element modified after free" kernel panic issue on my 16 inch MBP running 11.6 when connecting to a Dell monitor via usb-c cable which is also the power cable. After having gone through this thread here is a list of things that helped few users.

Thanks to one of the posts here, turning off MST has resolved my issue on 11.6 itself.

1. Update OS to 12.x
2. use DisplayPort 1.1 (instead of the default 1.2) on monitor, menu -> Display -> DP 1.2 -> Disable
3. On the monitor, turn off MST which is only needed to daisy chain monitors
4. Switch from USB c to HDMI for display
5. Use different USB c cable or Apple multiport adapter

same issue, mac mini 2018; even with wiped and freshly installed system with nothing except HDMI and ethernet plugged in, no additional SW added, merely logging in and letting it sit would reliably crash it after 25-26 minutes. Took it to "genius" bar last week, they kept the machine for a few days and said they couldn't repro. I brought it home same setup and it was fine for a whole day -- they didn't admit to having done anything to fix it but I was happy. That wasn't long-lived. Now it has crashed every day or two which is less frequently than before but problem persists. Also note this happened last summer too and the geniuses recommended I replace the logic board last fall (cost me almost $500), which also did not fix the problem -- a problem they refuse to admit there is ("our diagnostics give it a clean bill of health") Shame, Apple

I have a Kensington TB dock (dual monitors) which had been working fine, no new hardware or software aside from maybe MacOS (Big Sur) updates. It suddenly started experiencing kernel panics on my 2019 16" MPB when I was not using it (never when I was). This would happen multiple times a day if I rebooted and then ;eft it running. I had an almost exact duplicate setup at another location (same dock, same type cables connecting monitors) and it never had a kernel panic. I finally decided to try to debug the setup difference and found that if I swapped out the TB3 cable connected between the dock and the MBP 16" I now no longer have kernel panics.

We are also seeing this issue in our office.

20x Apple 2019 Intel, Macbook Pros. Using the WD19 Dell dock, with shipping firmware and the latest firmware as of March 30'th (Just came out)

I've also just confirmed this issue on a HP USB-C Dock G4, again with latest firmware. While inconsistent, absoloutely can hard crash the mac (fan spins hard) upon plugging in the dock, sometimes. Probably one in 3 times? Very bad.

Precise error is.

"your computer has been restarted due to a problem" Looks like this https://i.ytimg.com/vi/s9Lry8SXbgI/hqdefault.jpg

Very, very frustrating, we're talking about $180 USD and $250 USD docks here, the WD19 is a powerful high quality dock. Based on the replies here, it seems to me, there's no consistent fix for this.

We are also seeing this issue in our office.

20x Apple 2019 Intel, Macbook Pros. Using the WD19 Dell dock, with shipping firmware and the latest firmware as of March 30'th (Just came out)

I've also just confirmed this issue on a HP USB-C Dock G4, again with latest firmware. While inconsistent, absolutely can hard crash the mac (fan spins hard) upon plugging in the dock, sometimes. Probably one in 3 times? Very bad. Also of interest is the dock otherwise works fine. The problem only occurs unplugging or plugging in the dock sometimes. If you catch it in the right mood, it will work. (You may also see, mouse lag oddities)

Precise error is. "your computer has been restarted due to a problem" (if you google that, you may see a similar black image of it)

Very, very frustrating, we're talking about $180 USD and $250 USD docks here, the WD19 is a powerful high quality dock. Based on the replies here, it seems to me, there's no consistent fix for this?

I can reliably reproduce it on my MacBook Pro (16-inch, 2019) 2.6 GHz 6-Core Intel Core i7 with Big Sur 11.6.2 by plugging Razer Viper 8khz mouse via usb-c.

Interesting that I'm seeing this problem on a Macbook pro (16-inch, 2021) M1 - running Monterey 12.3.1 and a razer thunderbolt 4.0 hub with two monitors plugged in via displayport. Switched to a smaller 3 port hub and used the HDMI built into the laptop and the problem went away, I was getting a reboot on wake up at least 3 times a day otherwise.

Same error every day come back to work when MacBook Pro 16' 2021 M1 pro wake up. macOS is Montery 12.5. Two monitors connected, one by type-c DC directly, one by ugreen docker to VGA.

panic(cpu 0 caller 0xfffffe001dc7de2c): DCPEXT0 PANIC - ASSERT: AFKObject.cpp:27: [__null != p] - dcpdptx-port-epic(34) ASSERT: AFKObject.cpp:27: [__null != p] RTKit: RTKit-1827.120.2.debug - Client: local-t600xdcp.release !UUID: 1317b7f6-3acf-3776-93f7-a66ed223485b Time: 0x0000018068dd76d6

Faulting task 34 Call Stack: 0x000000000001d94c 0x000000000001d45c 0x000000000001d318 0x00000000000203e8 0x000000000003149c 0x0000000000052a8c 0x000000000006e700 0x00000000000308b0 0x000000000001e0ec 0x00000000000306e0 0x000000000006cbe0 0x00000000000b4988 0x00000000000af210 0x00000000000308b0 0x000000000001e0ec 0x00000000000306e0 0x00000000000ba1e4 0x00000000000a3130 0x00000000000a184c 0x00000000000308b0 0x000000000001e0ec 0x00000000000306e0 0x00000000000a175c 0x0000000000039f24 0x0000000000034b84 0x000000000001dde0 0x0000000000011230

Exactly the same thing happening to me. I use a Dell dock and two monitors.

Seeing the same thing when I dock/undock. The TouchBar often flashes/flickers before the crash happens if I'm working on the laptop after undocking. I send a report into Apple each time (example below). Happens 2 to 5 times in a row before stabilizing.

The error message changes a little each time (example below - often has "Sleep/Wake hang detected"). Send into Apple every time.

Dell thunderbolt dock and Sabren monitor adapter with 2 monitors running. OS 12.6 on a 2020 13-inch MacBook Pro with Intel i7.

Is there a workaround for this? Are Apple developers monitoring this site and is there a fix coming at some stage? Are there any docks that work? Is it a dock issue or is it related to transferring from laptop monitor to external monitors?

panic(cpu 1 caller 0xfffffff028ce6bac): Sleep/Wake hang detected @IOPMrootDomain.cpp:12600 Debugger message: panic Memory ID: 0x6 OS release type: User OS version: 19P6066 macOS version: 21G83 Kernel version: Darwin Kernel Version 21.6.0: Wed Aug 10 14:04:32 PDT 2022; root:xnu-8020.141.5~1/RELEASE_ARM64_T8010 Kernel UUID: ED0C23DC-B156-3B2D-A95D-022856D12AD5 iBoot version: iBoot-7459.141.1 secure boot?: YES x86 EFI Boot State: 0x16 x86 System State: 0x1 x86 Power State: 0x1 x86 Shutdown Cause: 0x5 x86 Previous Power Transitions: 0x100010001 PCIeUp link state: not available Paniclog version: 13 Kernel slide:   0x0000000020f48000 Kernel text base: 0xfffffff027f4c000 mach_absolute_time: 0x1ed7308843a Epoch Time:    sec    usec  Boot  : 0x62fdad8e 0x0007708f  Sleep  : 0x62fdbea5 0x0006bd8b  Wake  : 0x62fdc2b1 0x000ac305  Calendar: 0x62ff0d66 0x000916ac

Zone info:  Zone map: 0xffffffe036df4000 - 0xffffffe636df4000  . VM  : 0xffffffe036df4000 - 0xffffffe11d458000  . RO  : 0xffffffe11d458000 - 0xffffffe16a124000  . GEN0 : 0xffffffe16a124000 - 0xffffffe250788000  . GEN1 : 0xffffffe250788000 - 0xffffffe336dec000  . GEN2 : 0xffffffe336dec000 - 0xffffffe41d454000  . GEN3 : 0xffffffe41d454000 - 0xffffffe503abc000  . DATA : 0xffffffe503abc000 - 0xffffffe636df4000  Metadata: 0xffffffee581a0000 - 0xffffffee599a0000  Bitmaps : 0xffffffee599a0000 - 0xffffffee59c04000

CORE 0: PC=0xfffffff02878a924, LR=0xfffffff02878a924, FP=0xffffffe636f43f00 CORE 1 is the one that panicked. Check the full backtrace for details. Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space Panicked task 0xffffffe41d4f8628: 0 pages, 230 threads: pid 0: kernel_task Panicked thread: 0xffffffe3363db0c8, backtrace: 0xffffffee59c637f0, tid: 47855  lr: 0xfffffff02875a64c fp: 0xffffffee59c63830  lr: 0xfffffff02875a3d4 fp: 0xffffffee59c638a0  lr: 0xfffffff028893e48 fp: 0xffffffee59c63910  lr: 0xfffffff028892dec fp: 0xffffffee59c639c0  lr: 0xfffffff028db95fc fp: 0xffffffee59c639d0  lr: 0xfffffff02875a0f0 fp: 0xffffffee59c63d60  lr: 0xfffffff02875a0f0 fp: 0xffffffee59c63dc0  lr: 0xfffffff0298df38c fp: 0xffffffee59c63de0  lr: 0xfffffff028ce6bac fp: 0xffffffee59c63e20  lr: 0xfffffff0287abea0 fp: 0xffffffee59c63f20  lr: 0xfffffff028dc45a0 fp: 0x0000000000000000