|panic(cpu 4 caller 0xffffff7f8132f948): "XHC2(MacBookPro15,3): thunderbolt power on failed 0xffffffff\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-370.80.1/IOPCIBridge.cpp:1398|
|Backtrace (CPU 4), Frame : Return Address|
|0xffffffa3bfc83a60 : 0xffffff8000937beb|
|0xffffffa3bfc83ab0 : 0xffffff8000a6f4b5|
|0xffffffa3bfc83af0 : 0xffffff8000a60f2e|
|0xffffffa3bfc83b40 : 0xffffff80008dea40|
|0xffffffa3bfc83b60 : 0xffffff80009372d7|
|0xffffffa3bfc83c60 : 0xffffff80009376bb|
|0xffffffa3bfc83cb0 : 0xffffff80010ce059|
|0xffffffa3bfc83d20 : 0xffffff7f8132f948|
|0xffffffa3bfc83d40 : 0xffffff7f81318bb3|
|0xffffffa3bfc83da0 : 0xffffff7f813190ee|
|0xffffffa3bfc83dc0 : 0xffffff7f813172f8|
|0xffffffa3bfc83e10 : 0xffffff7f81321b0b|
|0xffffffa3bfc83e30 : 0xffffff8001022ad4|
|0xffffffa3bfc83ea0 : 0xffffff80010228da|
|0xffffffa3bfc83ec0 : 0xffffff8000979835|
|0xffffffa3bfc83f40 : 0xffffff8000979361|
|0xffffffa3bfc83fa0 : 0xffffff80008de13e|
|Kernel Extensions in backtrace:|
|BSD process name corresponding to current thread: kernel_task|
|Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev|
|Mac OS version:|
|Darwin Kernel Version 19.3.0: Sun Dec 8 22:27:29 PST 2019; root:xnu-6188.8.131.52.1~15/RELEASE_X86_64|
|Kernel UUID: 9EC18232-E356-30D5-84B8-282F31C3917B|
|Kernel slide: 0x0000000000600000|
|Kernel text base: 0xffffff8000800000|
|__HIB text base: 0xffffff8000700000|
|System model name: MacBookPro15,3 (Mac-1E7E29AD0135F9BC)|
|System shutdown begun: NO|
|System uptime in nanoseconds: 751201390207508|
|last loaded kext at 748362383917762: >usb.IOUSBHostHIDDevice 1.2 (addr 0xffffff7f84ca8000, size 45056)|
|last unloaded kext at 748493000428186: >usb.IOUSBHostHIDDevice 1.2 (addr 0xffffff7f84ca8000, size 45056)|
Yeah, i disabled power saving mode. So my display never goes to sleep anymore. That solved it i know i am killing the MacBook . But the previously the MacBook was loosing my work with every panic.
So yep disabled the monitor from turning off. I should say my setup is a 100% on an external monitor. Only times I open the lid is when things doesn't boot up
And this error speaks of a Thunderbolt power failure. When I look under Thunderbolt devices I don't see any device listed there either.
do you mean your MacBook had a panic once and then everything gone kaput? can't boot up anymore? did you try the recovery modes? CMD+R CMD+S etc? also, clearing out the SMC?
I jinxed myself, It crashed itself during a shutdown to install the latest Catalina Developer Updates. But didn't have to unplug anything. it rebooted back in the usual fashion. However, I have reduced the number of USB Hubs from 4 or 5 to 2. both connect via USB-C provides 3 USB3.0 interfaces. I switched the HDMI to a newer adapter which I have been using at work without any issue. If things are stable with the new adapter I will try turning sleep on again.
This 4 USB-c ports is really not enough. My standard setup
And I have to plug these guys in as I do some projects
do you have any recommendations?
I did not. Well, so my issue is a bit more extreme than yours as my ports stop working permanently after the kernel panic (and I’m on my third logic board now). So I just basically tell them that the ports are dead and the computer won’t charge.…
9 mars 2020 kl. 15:45 skrev Ryan McCullagh ***@***.***>: @arneson <https://github.com/arneson> Do you have VirtualBox or Parallels installed? I somehow convinced myself that this is the reason for the crashes. What did you tell them when you brought it to the apple store, since I'm assuming this issue isn't reproducible? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://gist.github.com/e24dc78150d574ade3382eaddaf1827a?email_source=notifications&email_token=AAKAJG7QYB5WXUQMEDWSD3TRGT6G3A5CNFSM4K43XLQ2YY3PNVWWK3TUL52HS4DFVNDWS43UINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAGDUYE#gistcomment-3205506>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKAJGY4FSTKD3L2CLPXCADRGT6G3ANCNFSM4K43XLQQ>.
Latest panic, (unplugged USB-C power connector, plugged USB power connector USB-C adapter, Plug USB-C Ethernet port to USB-C port in MacBook.
on crash and reboot, the external USB keyboard was not recognized. had to open the lid type password. This busts the hypothesis that disabling power savings mode fixes the issue.
Worth mentioning had just booted a VMware image of ubuntu assigning 8 cores (50% of cores) and 8GB (25% RAM) moments before this happened.
there is no
#Catelina 10.15.4 Beta 4
this is the function that this 32 bit code is leading me to, but given that I am running Catelina i doubt this is the correct file, or even if its remotely close to Catelina. I will try to see if my developer licenses allow me to get access to the actual code running
here is a summary of what I am able to gather so far
so the problem is definitely in the new IOKit Framework and how it manages the IO Registry. And most likely on hardware that is not written or tested against Apple's evolving spec on IOKit. My hunch is the crash is due to bad firmware on an untested device.
Potential Isolation approach to the problem
Documentation lacks details on what exactly the function supposed to be doing.
It is also worth mentioning that this part of the kernel code IOKit to be exact is also flagged as Beta, so it's possible that there are lot of bugs, and this panic is just one of many variants.
If you like to know more about this approach of IO Registration and Bridging there is a tool from Apple called
without any arguments, it will dump the state of the current IO Registry.
Light at the end of the tunnel (Maybe?)
It looks like hacking
Implementation of such a state tracking system does have it's own challenges of being able to have produced a near most state prior to panic and having it persisted without much IO weight on the actual machine. I believe those problems can be solved with another machine and UDP packets.
First step towards the goal
I found the ioreg source from Apple, and manage to create a project that can compile and produce a usable output just like the binary version they distribute.
matter of time and luck
So from now on, it will be a matter of time, luck and time If I am able to produce something. I will keep you guys posted here. I can write C code but i have never written Objective-C so challenge accepted.
before you go
i recommend at least getting
and running it to see the size of your IO Registery and the depth of it. It will give you some idea of the complexity of this panic and how it maybe difficult to reproduce.
I got this problem recently, and one of the type-c port is dead. Genius Bar suggest me to replace the logic board.
@arneson - my machine is being repaired right now. My problems became worse since I last updated this thread. My ports also stopped working permanently after the kernel panic and the only thing I could do is forcefully reboot the machine via the power button.
I have collected many kernel panic logs over this time period (January 2020-May 2020) and I even have a video evidence.
Unfortunately, the issue only appears to happen after about 6-8 hours of use. I don't know how to reproduce the issue.
I let it go to sleep etc, no special settings and it just works as expected. Terrified to upgrade osx though so thinking I’ll probably stay on 10.15.1 until 10.16.X is released and hope they fixed it by then.
Just hope I don’t need a newer Xcode-version before that, since that update is blocked for me until I upgrade.
@rmccullagh I have the same kernel panic issue
I'm able to reproduce it by plugging in the Apple USB-C to USB-A/HDMI/Power Passthru dongle (without anything plugged into the dongle) into a port on the right side of my 16" MBP. After plugging in, my machine crashes consistently within 2 minutes. The ports on the left side of my 16" MBP don't recognize the dongle. If I connect a USB-A keyboard to the dongle on the right side, I'm able to use it for a minute before my machine crashes.
All power-saving features are disabled. I also crash when waking from sleep (without anything plugged in).
@devzer01 @arneson I wonder whether we can "patch" this issue by downgrading to
kextstat -b com.apple.iokit.IOPCIFamily # on 10.15.4 outputs: # Index Refs Address Size Wired Name (Version) UUID <Linked Against> # 13 46 0xffffff7f80d11000 0x39000 0x39000 com.apple.iokit.IOPCIFamily (2.9) 1B1F3BBB-9212-3CF9-94F8-8FEF0D3ACEC4 <8 7 6 5 3>
@devzer01 just wonder if you got anywhere with your laptop? I'm having the same issue on a 15" 2018 MBP, out of warranty now and Apple guys told me it would be like $800 to replace the board if that's the issue, they couldn't figure it when I took it in for diagnoses. really sucks.
Edit: just saw this: https://apple.stackexchange.com/a/392859
macOS Catalina 10.15.4
Hey guys, update from me.
After staying on 10.15.1 for ages, I decided to do something about it.
I managed to update through to 10.15.6 and the computer is stable. The fix for me was to apply the “Combo updates” for each version instead of the actual update through software update.
Doing that seems to have fixed my issues and my computer has been running stable for a month or two now.
macOS Catalina 10.15.7
Same issue here
But didn't seem to solve the issue
MBP 2019 16inch
macOS Catalina 10.15.7
`panic(cpu 12 caller 0xffffff7f80d333c5): "DSB0(MacBookPro16,1): thunderbolt power on failed 0xffffffff\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-370.141.1/IOPCIBridge.cpp:1398
BSD process name corresponding to current thread: kernel_task
Mac OS version:
System uptime in nanoseconds: 112769970543
Hey, I have 2018 MBP and started facing this issue a lot after 11.4 update. Then came the 11.5 update and issue seemed mitigated however, I face the issue every time I fire up my machine in the morning.
I tried shutting down my machine overnight and next morning did not face the issue. But if it auto-sleeps, I face the issue again.
Disabling thunderbolt did not make a difference for me. Any update on this issue by anyone?
Catalina 10.15.7 here - this happens when my computer sleeps.
panic(cpu 0 caller 0xffffff7f983523c5): "UPSB(MacBookPro14,3): thunderbolt power on failed 0xffffffff\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-370.141.1/IOPCIBridge.cpp:1398
BSD process name corresponding to current thread: kernel_task
Mac OS version:
System uptime in nanoseconds: 11891458630336