You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

MBP 13 2020 won't recognize USB devices from TB dock after sleeping and connecting to the dock. After unplugging the dock MBP crashes and does SMC reset

Device: MBP 13" 2020 10th gen i5

Catalina 10.15.6

Dock: CalDigit TS3+ with firmware 44.1


I'm not sure if this problem is exclusive to Catalina 10.15.6, but I can't say since my dock arrived after the latest update got shipped and I haven't tried if it works on 10.15.5.


Basically, I unplug the dock at night and put the MBP to sleep. After a few hours of sleep it seems to stop recognizing the USB devices plugged into the dock. The dock has a USB audio interface, a logitech wireless dongle (for G604 mouse), a DP monitor and the power supply for the dock. When I plug it after the mac has been in sleep for hours, the mac won't recognize the audio card and the mouse (just the USB issue we had in previous catalina versions with all kinds of USB hubs and USB devices), but the monitor works and everything has power supplied to it, including the USB devices.

If I then unplug the dock and replug it, often the mac straight-up crashes completely and shuts down, powering on with an error that it recovered from a problem ( it also does an SMC reset).


The error report later states: "Intel CrashLog recorded due to unexpected reset".


This reddit thread speaks of the exact same issue with a different monitor and some people with different docks:

https://www.reddit.com/r/macbookpro/comments/i0m9si


Basically, what I'm saying is that the original USB issue is not fixed yet and now it's much worse because:

  1. You can't fix the USB problem unless you restart the mac - re-plugging the devices into the dock won't solve it
  2. The macbook directly crashes and does an SMC reset if you unplug/replug the dock, wiping your unsaved data and crashing anything else you might have open at the time


Additional problem: Monitor sometimes doesn't wake up at all after mac is awoken from sleep. At one point the monitor went to sleep WHILE I was using the mac actively.


I have tried NVRAM/SMC resets and they did nothing.


I wrote an email to CalDigit and they confirmed a lot of other users have complained about this:


"Our engineers have been investigating into the brand new 2020 MacBooks as we’ve had detailed reports from several of our customers who have tried many different brands of docks, from OWC, Kensington, Elgato and ours and none of them have been able to function correctly via the latest chipsets in these Macs."


PLEASE FIX the usb/dock/monitor issues already! This is a problem of Apple devices exclusively. This is unacceptable for a laptop at this price from the year 2020. Cheap off-brand laptops do not have such issues with peripherals!!

MacBook Pro 13″, macOS 10.15

Posted on Aug 4, 2020 11:01 AM

Reply
Question marked as Top-ranking reply

Posted on Dec 7, 2020 12:06 PM

I've been having this issue w/ my 13" 2020 MBP since I started using it a couple of months ago, with different dock models.



TL;DR


  • Issue reproduced on 2 different 13" 2020 MBPs running 10.15.7, one running a clean macOS install (no additional software installed), w/ 2 different TB docks.
  • 13" 2018 MBP works fine in all of the (same) tested configurations.




Details:


Since I have the benefit of having multiple MBPs and docks to test with, I'm (not that folks here require convincing) incredibly confident this issue isn't due to some people having faulty hardware (e.g. logic board, dock, whatever).


  • I was easily able to reproduce the kernel panic ("Intel CrashLog recorded due to unexpected reset") on a freshly installed 13” 2020 MBP (clean macOS installation- zero software installed).
  • This is consistently reproduced w/ 2 different 10.15.7 builds ((19H2 and 19H15 - didn't bother to test 19H4 and/or 10.15.6).
  • 10.15.5 (19F2200) works fine.
  • 11.0.1 (20B50 - didn't test 20B29) works fine.


I tested 2 different setups:


  • OWC TB3 dock, with 2 devices connected to it- Dell U2719DC monitor (DisplayPort) and Logitech K120 USB keyboard:


                     +---------+
                     |   MBP   |
                     +----+----+
                          |
                          |
                         TB3
                          |
                          v
                   +------+-------+
                   | OWC TB3 dock |
                   +----+-----+---+
                       |     |
                      USB    DP
+---------------+      |     |      +--------------+
| Logitech K120 +------+     +------+ Dell U2719DC |
+---------------+                   +--------------+



                     +---------+
                     |   MBP   |
                     +----+----+
                          |
                          |
                 Apple TB3/TB2 adapter
                          |
                          v
                 +--------+---------+
                 | Apple TB Display |
                 +------------------+


Similar questions

344 replies

Oct 9, 2020 7:41 AM in response to Hacky_4

These are all brilliant suggestions, but why isn't Apple doing anything? I just posted to twitter: Anybody out there remember “I”m a Mac”/“I’m a PC”? Do you feel like the tables have turned? Random reboots, ‘printer not connected’, wonky USB C ports, … A loyal Mac user for 20+ years (heck my 2ci is still in the garage), I’m very disappointed @Apple. 

Oct 9, 2020 8:01 AM in response to logicito

Thank you. There is the difference. hhttps://www.diffchecker.com/hqhWoidB


More reasonable than the plain folder checksum, but still nothing obvious unfortunately. CTRL+F on 'thunderbolt' shows same versions of thunderbolt kexts, "AppleThunderboltEDMSink" seems to be missing on the older macOS - but that's all I could find about thunderbolt. But it may be caused by different kext of course or it may be totally different issue. I'm just thinking of kext, because those are kernel extensions and so essentially drivers for Mac HW.

Oct 9, 2020 8:18 AM in response to Nancy31

Nancy31 wrote:

These are all brilliant suggestions, but why isn't Apple doing anything? I just posted to twitter: Anybody out there remember “I”m a Mac”/“I’m a PC”? Do you feel like the tables have turned? Random reboots, ‘printer not connected’, wonky USB C ports, … A loyal Mac user for 20+ years (heck my 2ci is still in the garage), I’m very disappointed @Apple. 

Same here. It may be actually my last Apple product. Already switched to Android after being loyal to iPhone many years and 2020 MBP may be as well my last MacBook. Apple got me with its "it just works". However it does not seem to be the case anymore. I saw and played with latest Windows 10 a little bit and it's actually great!


The tendency of Windows goes up - Windows 10 with Linux subsystem is great actually. However macOS goes down in my opinion. I liked older OS X better. It definitely worked better. Same for the MacBook hardware - don't get me started with the keyboard and screen issues of the previous MacBooks!

Oct 9, 2020 8:26 AM in response to Hacky_4

I agree, it is very disappointing, especially with the premium price we pay, compared to the PC world, what is challenging to me, is that the eco system integration that Apple provides me with the phone, watch, laptop and tablet is non existent with Windows and Android, they have something but it is still on early stages.

Oct 9, 2020 8:38 AM in response to dd36

I have a 2018 MBP 13" as well, the issue with the keyboard is bad, even though they extended the warranty for the keyboard, they will replace it with the same type, so sooner or later, the replacement will fail again, I had mine already replaced. I would say, good intentions by extending the warranty, poor solution.

Oct 9, 2020 1:21 PM in response to logicito

I normally leave my Mac plugged in to my dock with the dock powered off. (I switch between the CalDigit TS3 and the Anker PowerExpand Elite) This morning when I woke my Mac, the thunderbolt ports (all four) were only using reception scripts (insofar as the ports themselves would not transmit to the dock, to the attached peripherals, but they would receive A/C power just fine). When performing a restart the Mac hung and crashed, following that with a new boot cycle.


The error messages reporting kernel issues are pretty spot on. I get them almost everyday as well as one pertaining to the thunderbolt controller. Kernel issues are onboard AND so is the thunderbolt controller - both functions are IN the CPU. At first, this made me think that there could be a glitch on specific cuts of Intel Gen 10 that weren't up to snuff and were the cause. But not everyone in this conversation has 10th Gen. Then its simple. Using some deduction, the issue seems to be firmware. While some may have noticed that older versions of MacOS lessen the symptomology of the issue we are investigating, the older versions most likely don't ever access the overclocking and core functions of the newer chips in any sense, and therefore wouldn't accidentally trip the over voltage on the controller on the chip.


It's not software. It's not hardware *(well sort of). It's firmware.

Oct 12, 2020 6:15 PM in response to ArtemisAlmighty

What is the Boot ROM version on your computer? You can check that in System Information, Hardware section, If iBridge start with 18. that is the Big Sur firmware, if it is 17. It is the Catalina firmware, I found that the problems happens to me with 18. Firmware, because I had installed Big Sur, then went back to Catalina, and the firmware doesn’t get reverted back to a Catalina firmware.

Oct 14, 2020 7:54 AM in response to broko_fankone

MBP 13'' 2020, 10th GEN i7 with OWC Thunderbolt 3. Catalina 10.15.7.


The behaviour is as described here, and it is annoying. I need to unplug the dock sometimes several times a day, and after re-connecting no devices such us sound card and external disk are detected. (charging works, monitor works and ports used for charging devices - work too).


I can't reproduce restarts. Sometime it does immediately, some other times it takes up to several minutes.


Manual restart with hub connected works, but well, I am expecting a bit more from the machine that is that expensive. What a disaster. I hope this to be fixed ASAP.


Note: I am using this Dock for one and half year now and I never experienced any issues until several weeks ago.

Oct 16, 2020 2:10 AM in response to logicito

I can agree that there are no crashes in the last few hours of using Big Sur Beta 10 with the CalDigit Thunderbolt Dock and the Macbook Pro 13 2020, but my displays connected to the dock are flickering from time to time and my HDD connected to the dock disconnects after a few minutes of using. It seems we have to wait a few months longer and i have to go back to a usb-c-dock, there are no issues till now...

Oct 17, 2020 9:28 AM in response to TelJr

I have the same problem with my all new MacBook Pro 2020 13" (i5 10th gen, 4 TB3-Ports) with an OWC Thunderbolt 3 Dock. I've tested a "small" USB-C-Hub (just with 1 HDMI-Port and just powering over the Apple Power supply): No Problems so far. I suspect there is a problem with the "big" Thunderbolt Docks with own power supply and own chipsets for multiple monitor setups... Hope they fix it soon. Until fix, i just take my USB-C-Hub and a second USB-C to DP-Cable for 2 Monitors. With this combo, no crashes so far.

MBP 13 2020 won't recognize USB devices from TB dock after sleeping and connecting to the dock. After unplugging the dock MBP crashes and does SMC reset

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.