(347) 552-2258 help@rossmanngroup.com

820-00923 - Kernel panic and error DSB0 Thunderbolt power on failed during sleep

S

SoloHarty

New member
Another 820-00923 that had severe liquid damage. I had to replace the thunderbolt controller chips, the U7000 charging IC and remove a short circuit on PPBUS_G3H to get it working. It works great when it isn't in sleep mode or trying to update. I am actually typing this message from this board.

The board charges absolutely fine from all ports but when the Mac is sleeping it will randomly kernel panic and come back reporting the main error "DSB0 Thunderbolt power on failed". I also find that if I am updating the MacOS it will reboot to a black screen where the trackpad clicks but nothing on screen. If I leave it running it doesn't update and I have to perform a hard reset (SMC reset or holding down power button) to boot it again where it will update as normal like nothing ever happened.

Anyone came across the kernel panic issue before? I am positive they are related.

Thanks
 
S

SoloHarty

New member
The Mac went to sleep and kernel panicked again. Full report below:

panic(cpu 0 caller 0xffffff802141705a): "DSB0(MacBookPro14,2): thunderbolt power on failed 0x15788086\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-428.40.7/IOPCIBridge.cpp:1428
Backtrace (CPU 0), Frame : Return Address
0xffffffb096773960 : 0xffffff801eab76dd
0xffffffb0967739b0 : 0xffffff801ebfa0e3
0xffffffb0967739f0 : 0xffffff801ebea71a
0xffffffb096773a40 : 0xffffff801ea5ca2f
0xffffffb096773a60 : 0xffffff801eab6f7d
0xffffffb096773b80 : 0xffffff801eab7268
0xffffffb096773bf0 : 0xffffff801f2b9c9a
0xffffffb096773c60 : 0xffffff802141705a
0xffffffb096773c80 : 0xffffff80213fd70f
0xffffffb096773ce0 : 0xffffff80213fd8c2
0xffffffb096773d20 : 0xffffff80213fda6b
0xffffffb096773d60 : 0xffffff80213fdc41
0xffffffb096773d80 : 0xffffff80213fbdc2
0xffffffb096773dd0 : 0xffffff8021406aff
0xffffffb096773df0 : 0xffffff801f1f7ef1
0xffffffb096773e60 : 0xffffff801f1f7c8a
0xffffffb096773e80 : 0xffffff801eafc3b5
0xffffffb096773ef0 : 0xffffff801eafd2c4
0xffffffb096773fa0 : 0xffffff801ea5c13e
Kernel Extensions in backtrace:
com.apple.iokit.IOPCIFamily(2.9)[4A059818-C93E-3144-9A9A-DDB4A59F9990]@0xffffff80213f4000->0xffffff802141bfff

Process name corresponding to current thread: kernel_task

Mac OS version:
20B5012d

Kernel version:
Darwin Kernel Version 20.1.0: Sat Oct 24 21:21:05 PDT 2020; root:xnu-7195.50.3.201.1~1/RELEASE_X86_64
Kernel UUID: 2BA1C8BD-9C95-3FA7-B7A4-F991BB96D49C
KernelCache slide: 0x000000001e800000
KernelCache base: 0xffffff801ea00000
Kernel slide: 0x000000001e810000
Kernel text base: 0xffffff801ea10000
__HIB text base: 0xffffff801e900000
System model name: MacBookPro14,2 (Mac-66E35819EE2D0D05)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 5782575171818
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000005425c56cc02
Sleep : 0x000002fb25a6db8e 0x000029237e6badb0 0x000002f2d8f7a34c
Wake : 0x000002fb3929f932 0x00002c091f42b67c 0x000002fb37450c74
last started kext at 5764106843035: >usb.!UUserHCI 1 (addr 0xffffff7fbe5ef000, size 98304)
last stopped kext at 4636655666322: >usb.!UUserHCI 1 (addr 0xffffff7fbe5ef000, size 98304)
loaded kexts:
>usb.!UUserHCI 1
@filesystems.smbfs 3.4.1
>AudioAUUC 1.70
>!AHIDALSService 1
>!APlatformEnabler 2.7.0d0
>AGPM 119
>X86PlatformShim 1.0.0
@filesystems.autofs 3.0
@fileutil 20.036.15
>!AHDA 283.15
>!A!IPCHPMC 2.0.1
>!AUpstreamUserClient 3.6.8
>!AGraphicsDevicePolicy 6.1.27
>!AEmbeddedOSSupportHost 1
@AGDCPluginDisplayMetrics 6.1.27
>pmtelemetry 1
>LuaHardwareAccess 1.0.16
|IOUserEthernet 1.0.1
|IO!BSerialManager 8.0.1f5
@Dont_Steal_Mac_OS_X 7.0.0
>!AHV 1
>!A!IKBLGraphics 16.0.0
>!ABacklight 180.3
>!ADiskImages2 1
>!A!ISlowAdaptiveClocking 4.0.0
>eficheck 1
>!A!IKBLGraphicsFramebuffer 16.0.0
>!AThunderboltIP 4.0.3
>!AMCCSControl 1.14
@filesystems.apfs 1677.41.3
@filesystems.tmpfs 1
@filesystems.hfs.kext 556.41.1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
>!ATopCaseHIDEventDriver 4000.27
>AirPort.BrcmNIC 1400.1.1
@private.KextAudit 1.0
>!ASmartBatteryManager 161.0.0
>!AACPIButtons 6.1
>!ARTC 2.0
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 310
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
@kext.triggers 1.0
>DspFuncLib 283.15
@kext.OSvKernDSPLib 529
>!AGraphicsControl 6.1.27
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
>!AHDA!C 283.15
|IOHDA!F 283.15
|IOAudio!F 300.6.1
@vecLib.kext 1.2.0
|IO!BHost!CUARTTransport 8.0.1f5
|IO!BHost!CTransport 8.0.1f5
|IOAVB!F 900.12
@plugin.IOgPTPPlugin 900.11
|IOEthernetAVB!C 1.1.0
>!ABacklightExpert 1.1.0
>!A!ILpssUARTv1 3.0.60
>!A!ILpssUARTCommon 3.0.60
>!AOnboardSerial 1.0
|IOSerial!F 11
|IONDRVSupport 585
@!AGPUWrangler 6.1.27
|IOSlowAdaptiveClocking!F 1.0.0
|IOAccelerator!F2 439.35.4
@!AGraphicsDeviceControl 6.1.27
|IOGraphics!F 585
>!ASMBus!C 1.0.18d1
>usb.cdc.ncm 5.0.0
>usb.!UiBridge 1.0
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>!AThunderboltDPInAdapter 8.1.4
>!AThunderboltDPAdapter!F 8.1.4
>!AThunderboltPCIDownAdapter 4.1.1
>!AHPM 3.4.4
>!A!ILpssI2C!C 3.0.60
>!ABSDKextStarter 3
|IOSurface 289.3
@filesystems.hfs.encodings.kext 1
>!AActuatorDriver 4400.28
>!AHIDKeyboard 222
>!AMultitouchDriver 4400.28
>!AInputDeviceSupport 4400.35
>!AHS!BDriver 4000.27
>IO!BHIDDriver 8.0.1f5
>!AHSSPIHIDDriver 61
>!AHSSPISupport 61
>!AThunderboltNHI 7.2.8
|IOThunderbolt!F 9.3.2
>!A!ILpssSpi!C 3.0.60
>!A!ILpssDmac 3.0.60
|IO80211!F 1200.12.2b1
|IOSkywalk!F 1
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
|IONVMe!F 2.1.0
>!A!ILpssI2C 3.0.60
>!A!ILpssGspi 3.0.60
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
|IOUSB!F 900.4.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$!AImage4 3.0.0
|IOTimeSync!F 900.11
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 8.0.1f5
|IOReport!F 47
|IO!BPacketLogger 8.0.1f5
$quarantine 4
$sandbox 300.0
@kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 511.40.9
|IOUSBMass!SDriver 184.40.6
|IOSCSIBlockCommandsDevice 436.40.6
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 436.40.6
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!ACredentialManager 1.0
>KernelRelayHost 1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AACPIPlatform 6.1
>!ASMC 3.1.9
|IOPCI!F 2.9
|IOACPI!F 1.4
>watchdog 1
@kec.pthread 1
@kec.corecrypto 1.0
@kec.Libm 1
 
S

SoloHarty

New member
Ok, I reflowed U2800, UB000, U3100 and U3200. the CD3215 IC's are normally underfilled but when I got this board it was removed badly from U3100 and U3200.

UB300 and UB400 have still got underfill but what I noticed is that if the board is out of the housing, it's stuck at 5V and restarting BUT if I press down on UB400 (still underfilled) then the board gets 20V consistently and turns on. Once it's on it stays on but if I unplug and let it rest for a second, it goes back to being stuck at 5V again UNTIL I press on UB400 again.

What I'm thinking is either a cold or damaged ball in the underfill and that could be causing all my issues. Definitely the kernel panic but most likely the issue with updates rebooting to a black screen too.

Sounds like I will have to dig UB300 and UB400 out and reball them. Ugh.
 
S

SoloHarty

New member
ok, reballed UB300 and UB400. Still the same issue. I've found I don't need a lot of pressure at all to make it get 20V but I have also noticed that while all 4 ports charge when the Mac is on, only the left side gets USB activity. Could this still be CD3215 issues?
 
S

SoloHarty

New member
SOLVED! (I think).

RB090 which connects PP3V3_UPC_TA_LDO and TBT_ T_ROM_HOLD_L was hanging on by a thread. No corrosion near it but I must've been putting just enough flex on the board for it to start up. Replaced and now I'm getting 20v correctly and consistently. Wish I noticed that before reballing UB300/UB400!!

Now to just see if I get any more kernel panics and if it updates correctly without me habing to give it a hard reset.
 
You must log in or register to reply here.
Top