Unfortunately the problem is still there even with the new board. The computer crashes when in stand by.
When I look at the core_analytics log I see a bug_type: 211.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2018 MacBook Pros crashing with "Bridge OS" error
- Thread starter kryptticAZ
- Start date
- Sort by reaction score
Unfortunately the problem is still there even with the new board. The computer crashes when in stand by.
When I look at the core_analytics log I see a bug_type: 211.
{"caused_by":"macos","macos_version":"Mac OS X 10.15.1 (19B88)","os_version":"Bridge OS 4.1 (17P1081)","macos_system_state":"running","incident_id":"78F474F1-0C35-479F-811D-1DA508C38A6E","timestamp":"2019-12-01 08:26:02.87 +0000","bug_type":"210"}
This is the first time in 1 year of daily use that I got an error. I found the machine restarted when I opened the lid. The time stamp is at a time I was not using the machine. weird!
This is the first time in 1 year of daily use that I got an error. I found the machine restarted when I opened the lid. The time stamp is at a time I was not using the machine. weird!
Get this type of errors when mac restart after sleep, no errors though if wifi is turned off.
Any ideas what is the cause?
[EDIT]: No attached devices
Any ideas what is the cause?
[EDIT]: No attached devices
Code:
panic(cpu 2 caller 0xffffff7f9df2f970): "DSB0(MacBookPro15,2): thunderbolt power on failed 0xffffffff\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-370.0.2/IOPCIBridge.cpp:1396
Backtrace (CPU 2), Frame : Return Address
0xffffff8131b839e0 : 0xffffff801d53bb1b
0xffffff8131b83a30 : 0xffffff801d6733e5
0xffffff8131b83a70 : 0xffffff801d664e5e
0xffffff8131b83ac0 : 0xffffff801d4e2a40
0xffffff8131b83ae0 : 0xffffff801d53b207
0xffffff8131b83be0 : 0xffffff801d53b5eb
0xffffff8131b83c30 : 0xffffff801dcd24f9
0xffffff8131b83ca0 : 0xffffff7f9df2f970
0xffffff8131b83cc0 : 0xffffff7f9df18bdb
0xffffff8131b83d20 : 0xffffff7f9df18d8c
0xffffff8131b83d60 : 0xffffff7f9df18f33
0xffffff8131b83da0 : 0xffffff7f9df19104
0xffffff8131b83dc0 : 0xffffff7f9df17320
0xffffff8131b83e10 : 0xffffff7f9df21b33
0xffffff8131b83e30 : 0xffffff801dc27164
0xffffff8131b83ea0 : 0xffffff801dc26f6a
0xffffff8131b83ec0 : 0xffffff801d57d765
0xffffff8131b83f40 : 0xffffff801d57d291
0xffffff8131b83fa0 : 0xffffff801d4e213e
Kernel Extensions in backtrace:
com.apple.iokit.IOPCIFamily(2.9)[1286D5E5-A6A1-3C44-A244-04C068903DB2]@0xffffff7f9df10000->0xffffff7f9df46fff
BSD process name corresponding to current thread: kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev
Mac OS version:
19C57
Kernel version:
Darwin Kernel Version 19.2.0: Sat Nov 9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64
Kernel UUID: C3E7E405-C692-356B-88D3-C30041FD1E72
Kernel slide: 0x000000001d200000
Kernel text base: 0xffffff801d400000
__HIB text base: 0xffffff801d300000
System model name: MacBookPro15,2 (Mac-827FB448E656EC26)
System shutdown begun: NO
System uptime in nanoseconds: 2033028006352
last loaded kext at 482015119579: >!UAudio 320.49 (addr 0xffffff7fa188d000, size 434176)
loaded kexts:
@filesystems.smbfs 3.4
>!AGraphicsDevicePolicy 4.5.21
@fileutil 20.036.15
@AGDCPluginDisplayMetrics 4.5.21
>!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.2f4
>!AUpstreamUserClient 3.6.8
>!APlatformEnabler 2.7.0d0
>AGPM 111.4.1
>X86PlatformShim 1.0.0
>pmtelemetry 1
>!A!IKBLGraphics 14.0.3
@Dont_Steal_Mac_OS_X 7.0.0
>AGDCBacklightControl 4.5.21
>BridgeAudioCommunication 6.60
>ACPI_SMC_PlatformPlugin 1.0.0
>!AThunderboltIP 3.1.3
>!ABacklight 180.1
>!AFIVRDriver 4.1.0
>!AAVEBridge 6.1
>!ABridgeAudio!C 6.60
>!AGFXHDA 100.1.422
>!A!IPCHPMC 2.0.1
>!ATopCaseHIDEventDriver 3420.1
>!AHIDALSService 1
>!A!ICFLGraphicsFramebuffer 14.0.3
>!A!ISlowAdaptiveClocking 4.0.0
>!AMCCSControl 1.13
@filesystems.autofs 3.0
@filesystems.apfs 1412.61.1
>BCMWLANFirmware4355.Hashstore 1
>BCMWLANFirmware4364.Hashstore 1
>BCMWLANFirmware4377.Hashstore 1
>!AFileSystemDriver 3.0.1
@filesystems.hfs.kext 522.0.9
@BootCache 40
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
>!AVirtIO 1.0
>!ABCMWLANBusInterfacePCIe 1
@private.KextAudit 1.0
>!ASmartBatteryManager 161.0.0
>!AACPIButtons 6.1
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
$!AImage4 1
@nke.applicationfirewall 303
$TMSafetyNet 8
@!ASystemPolicy 2.0.0
|EndpointSecurity 1
>!UAudio 320.49
>!AGraphicsControl 4.5.21
|IOAVB!F 800.17
>!ASSE 1.0
>IOPlatformPluginLegacy 1.0.0
>!AHDA!C 283.15
|IOHDA!F 283.15
@!AGPUWrangler 4.5.21
>!ABacklightExpert 1.1.0
>X86PlatformPlugin 1.0.0
>!AThunderboltEDMSink 4.2.2
>!AThunderboltDPOutAdapter 6.2.4
>!AActuatorDriver 3420.2
|IONDRVSupport 569.3
>IOPlatformPlugin!F 6.0.0d8
>!AHIDKeyboard 209
>!AHS!BDriver 3420.1
>IO!BHIDDriver 7.0.2f4
>!AMultitouchDriver 3420.2
>!AInputDeviceSupport 3420.4
>!ASMBusPCI 1.0.14d1
|IO!BHost!CUARTTransport 7.0.2f4
|IO!BHost!CTransport 7.0.2f4
>!A!ILpssUARTv1 3.0.60
>!A!ILpssUARTCommon 3.0.60
>!AOnboardSerial 1.0
@!AGraphicsDeviceControl 4.5.21
|IOAccelerator!F2 438.2.8
|IOSlowAdaptiveClocking!F 1.0.0
>!ASMBus!C 1.0.18d1
|IOGraphics!F 569.3
@plugin.IOgPTPPlugin 800.14
|IOEthernetAVB!C 1.1.0
@kext.triggers 1.0
>usb.IOUSBHostHIDDevice 1.2
>usb.cdc.ecm 5.0.0
>usb.cdc.ncm 5.0.0
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>!AXsanScheme 3
>usb.!UVHCIBCE 1.2
>usb.!UVHCI 1.2
>usb.!UVHCICommonBCE 1.0
>usb.!UVHCICommon 1.0
>!AEffaceableNOR 1.0
|IOBufferCopy!C 1.1.0
|IOBufferCopyEngine!F 1
|IONVMe!F 2.1.0
>!AThunderboltPCIDownAdapter 2.5.2
>!AThunderboltDPInAdapter 6.2.4
>!AThunderboltDPAdapter!F 6.2.4
>!AHPM 3.4.4
>!A!ILpssI2C!C 3.0.60
>!A!ILpssDmac 3.0.60
|IOSurface 269.6
@filesystems.hfs.encodings.kext 1
|IOAudio!F 300.2
@vecLib.kext 1.2.0
>!AThunderboltNHI 5.8.1
|IOThunderbolt!F 7.4.7
>!ABCMWLANCore 1.0.0
>mDNSOffloadUserClient 1.0.1b8
>IOImageLoader 1.0.0
|IOSerial!F 11
|IO80211!FV2 1200.12.2b1
>corecapture 1.0.4
|IOSkywalk!F 1
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
>!A!ILpssI2C 3.0.60
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
>!A!ILpssGspi 3.0.60
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
>!ASMCRTC 1.0
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$quarantine 4
$sandbox 300.0
@kext.!AMatch 1.0.0d1
>!AKeyStore 2
>!UTDM 489.60.3
|IOSCSIBlockCommandsDevice 422.0.2
>!ACredentialManager 1.0
>KernelRelayHost 1
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
|CoreAnalytics!F 1
|IOTimeSync!F 800.14
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 7.0.2f4
|IO!BPacketLogger 7.0.2f4
|IOUSBMass!SDriver 157.40.7
|IOSCSIArchitectureModel!F 422.0.2
|IO!S!F 2.1
|IOUSBHost!F 1.2
>usb.!UCommon 1.0
>!UHostMergeProperties 1.2
>!ABusPower!C 1.0
|IOReport!F 47
>!AACPIPlatform 6.1
>!ASMC 3.1.9
>watchdog 1
|IOPCI!F 2.9
|IOACPI!F 1.4
@kec.pthread 1
@kec.corecrypto 1.0
@kec.Libm 1
I am having the same issue as well, but am unsure if it has to do because of the dual monitor setup. The MBP goes through these turning monitors on and off cycles.
I have noticed using Adobe products and MAMP crashes it as well. Tonight, I am testing unplugging both monitors and leaving Adobe products and MAMP on to see what happens.
Another thing I have noticed, this only happens when the lid is closed. When it is opened, the MBP works fine.
Additional information, this wasn’t happening before. Even after upgrading to Catalina. It started happening when I began using dual monitors.
13” Mid 2018 MBP 16gb ram 512gb ssd
EDIT:
I disabled “Wifi Access” and “Nap time” within power saver and no crash. It seems like those too features in addition to the two monitors, kept messing with the MBP’s power, which then somehow made the MBP to restart itself. Let me know if anyone can replicate what I have done and hopefully it may help someone fix the issue. I’ll keep monitoring.
I have noticed using Adobe products and MAMP crashes it as well. Tonight, I am testing unplugging both monitors and leaving Adobe products and MAMP on to see what happens.
Another thing I have noticed, this only happens when the lid is closed. When it is opened, the MBP works fine.
Additional information, this wasn’t happening before. Even after upgrading to Catalina. It started happening when I began using dual monitors.
13” Mid 2018 MBP 16gb ram 512gb ssd
EDIT:
I disabled “Wifi Access” and “Nap time” within power saver and no crash. It seems like those too features in addition to the two monitors, kept messing with the MBP’s power, which then somehow made the MBP to restart itself. Let me know if anyone can replicate what I have done and hopefully it may help someone fix the issue. I’ll keep monitoring.
Last edited:
I had the same problem, 17th month old MBP 15" 32GB ram-2TB HD.
I started waking up to apple crash reports daily then 2 weeks ago the freeze fast fan then restart became daily, often 5 or 6 times a day often during mission critical work.
The latest experiment seems to have worked? No crashes for 2 days.
basically I went to my user folder/preferences and trashed them all (make sure you have an empty trash folder to do this) Then I restarted my computer a couple of times with no preferences so it was able to generate new ones. Then I selected all preferences in my trash folder and dragged them back into my User/preference folder and restarted, ran Disc Utility and so far 2 days without a crash.
Prior to this set step i had spoken to 3 Apple tech support folks including one administrator and they were of no help really.
So I:
Ran Disc Utility
I reset the PRAM
Reset the SMC (numerous times)
I used a backup HD to start up then erase my computers HD completely.
Used MacOS Recovery to install a clean copy of High Sierra 10.13.6
Then I used Migration Asst. to import all my Applications and user settings.
But after doing all of this within one hour I had the very same freeze and crash.
Freezes and crashes continued until I trashed all preferences then reinstalled them all.
So trashing the preferences seems to have stopped my Freeze and crashes?
2 days so far.
I will be back here is I get anymore crashes to report. Good luck, Seems after 2 years Apple still has no clue what to suggest to fix this or what is going on with this issue. Tech support email blissfully ignorant on this issue, I guess its hard to admit there is a problem with your product if you have no reliable fix.
I started waking up to apple crash reports daily then 2 weeks ago the freeze fast fan then restart became daily, often 5 or 6 times a day often during mission critical work.
The latest experiment seems to have worked? No crashes for 2 days.
basically I went to my user folder/preferences and trashed them all (make sure you have an empty trash folder to do this) Then I restarted my computer a couple of times with no preferences so it was able to generate new ones. Then I selected all preferences in my trash folder and dragged them back into my User/preference folder and restarted, ran Disc Utility and so far 2 days without a crash.
Prior to this set step i had spoken to 3 Apple tech support folks including one administrator and they were of no help really.
So I:
Ran Disc Utility
I reset the PRAM
Reset the SMC (numerous times)
I used a backup HD to start up then erase my computers HD completely.
Used MacOS Recovery to install a clean copy of High Sierra 10.13.6
Then I used Migration Asst. to import all my Applications and user settings.
But after doing all of this within one hour I had the very same freeze and crash.
Freezes and crashes continued until I trashed all preferences then reinstalled them all.
So trashing the preferences seems to have stopped my Freeze and crashes?
2 days so far.
I will be back here is I get anymore crashes to report. Good luck, Seems after 2 years Apple still has no clue what to suggest to fix this or what is going on with this issue. Tech support email blissfully ignorant on this issue, I guess its hard to admit there is a problem with your product if you have no reliable fix.
Last edited:
Hello!
Here, too, the same problems: when idle, my new MacBook Pro 16 inch sometimes (not always) simply goes out and restarts automatically when it opens.
What is interesting, Apple has already exchanged this because the first one had other errors - but both also had the Bridge OS error.
I connected an Apple Thunderbolt display via an original Apple Thunderbolt adapter (Thunderbolt 3 to Thunderbolt 2).
Now I have strong doubts whether this will also happen with the Pro Display XDR. Because at prices of almost 12,000 euros, I would have a huge problem with such a mistake.
What do you all mean?
(Sorry for my english, that was created with google translator)
Here, too, the same problems: when idle, my new MacBook Pro 16 inch sometimes (not always) simply goes out and restarts automatically when it opens.
What is interesting, Apple has already exchanged this because the first one had other errors - but both also had the Bridge OS error.
I connected an Apple Thunderbolt display via an original Apple Thunderbolt adapter (Thunderbolt 3 to Thunderbolt 2).
Now I have strong doubts whether this will also happen with the Pro Display XDR. Because at prices of almost 12,000 euros, I would have a huge problem with such a mistake.
What do you all mean?
(Sorry for my english, that was created with google translator)
Attachments
Problem is back, my computer randomly froze and restarted 3 times today, twice in sleep mode, once while I was working on it. 4 days without a crash and now it’s back.
bummer.
bummer.
High Sierra 10.13.6 with all latest security updates. No interest in Catalina yet, I have too much pro software that is not supported by Catalina.
Seems like it. My 2018 MBP was solid for 16 months before this issue started on mine.
i am concerned that Apple are so quiet on the issue, no one at Apple acknowledges the problem officially, they tell you the same thing, re install blah blah but that did not fix mine.
This seems to be a huge issue on what are actually our most valuable work tools. The forums and numerous publications are quite vocal about this issue but Apple are dead quiet. I think it’s something very serious, like the T2 chip or something that will be an expensive PR disaster once there is enough pressure for a resolution from consumers like us.
Has anyone had a reliable fix from Apple for this problem? My computer is out of its warranty so I do not want to pay for a problem that seems to be an inherent design flaw.
i am concerned that Apple are so quiet on the issue, no one at Apple acknowledges the problem officially, they tell you the same thing, re install blah blah but that did not fix mine.
This seems to be a huge issue on what are actually our most valuable work tools. The forums and numerous publications are quite vocal about this issue but Apple are dead quiet. I think it’s something very serious, like the T2 chip or something that will be an expensive PR disaster once there is enough pressure for a resolution from consumers like us.
Has anyone had a reliable fix from Apple for this problem? My computer is out of its warranty so I do not want to pay for a problem that seems to be an inherent design flaw.
First time this "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available" error happened to me. 2018 MacBook Pro 13", 512GB 8GB RAM--it's out of warranty, have had it since October '18.
At the time this happened, was streaming video thru a VPN to an TV HD…which I do often. Sometimes at work I use the MBP hooked up to a Dell D6000 & two Dell 2K monitors (using DisplayLink).
It's never crashed using this setup. Nor has the MBP ever crashed while streaming. Or, really, doing anything. I did see a kernel panic once before but it was after a Mojave update--and I didn't save the logs unfortunately.
Reading through these pages makes me feel like someone with a head cold that logs on to WebMD & thinks they have a terminal illness. I'm not sure if I should be super-concerned and worried about my MBP being out of warranty and what could be going on here or if it's just a one-off incident that will go away…like a head cold.
At the time this happened, was streaming video thru a VPN to an TV HD…which I do often. Sometimes at work I use the MBP hooked up to a Dell D6000 & two Dell 2K monitors (using DisplayLink).
It's never crashed using this setup. Nor has the MBP ever crashed while streaming. Or, really, doing anything. I did see a kernel panic once before but it was after a Mojave update--and I didn't save the logs unfortunately.
Reading through these pages makes me feel like someone with a head cold that logs on to WebMD & thinks they have a terminal illness. I'm not sure if I should be super-concerned and worried about my MBP being out of warranty and what could be going on here or if it's just a one-off incident that will go away…like a head cold.
This guy upgraded the CPU in his new Mac Pro and got a Bad Magic crash. Don't know if the CPU caused it but he took massive risk doing that with a $6K machine.
forums.macrumors.com
Mac Pro 2019 CPU Upgraded to 28 Cores, shut Down unexpectedly. [solved] with More Update
Got the Mac Pro 2019 Yesterday, then replace to 28cores CPU 3275M, and add 4 x 32 RAM Then I was trying to test lightroom export speed, the task is to resize 8000 JPGs When exporting, CPU 28 cores are fully loaded, but a few minutes later, the whole machine just shuts down. I tried 4-5 times...
forums.macrumors.com
He solved it, the heatsink was not tightened enough.This guy upgraded the CPU in his new Mac Pro and got a Bad Magic crash. Don't know if the CPU caused it but he took massive risk doing that with a $6K machine.
Mac Pro 2019 CPU Upgraded to 28 Cores, shut Down unexpectedly. [solved] with More Update
Got the Mac Pro 2019 Yesterday, then replace to 28cores CPU 3275M, and add 4 x 32 RAM Then I was trying to test lightroom export speed, the task is to resize 8000 JPGs When exporting, CPU 28 cores are fully loaded, but a few minutes later, the whole machine just shuts down. I tried 4-5 times...
Whole story is here mark my words, I did a lot of research on this. The issue is due to Apple placing a non x86 command set ARM based T2 chip in between intel processor and SSD. (This happened in 2018. Any unit bought after this date is a candidate of this hardware/software error.) To conduct the command translation, they wrote the Bridge OS. Before Catalina I was getting Bridge OS kernel panics with my macbook pro and imac pro. With Catalina it has turned to “ BAD MAGIC” error.
I have files I keep to replicate the issue in front of geniuses. Because there is no console log when this happens. They take your macbook pro or imac pro in and say it is ok.
PROBABLE SOLUTIONS WHICH MAY WORK FOR SOME PEOPLE (NONE WORKED FOR ME BY THE WAY =0 )
——-TURN OFF ANY SECURTIY MEASURES THAT NECESSITATES THE USE OF T2 CHIP (SECURE BOOT, DISK ENCRYPTION ETC) from recovery screen before starting mac os.
——-reset the T2 controller: https://support.apple.com/en-us/HT201295#t2"
——"Another recommendation was to reflash the T2 controller firmware: https://help.apple.com/configurator/mac/2.7.1/?lang=en#/apdebea5be51"
———T2 chip query (to check whether replacement logic board is the same faulty batch or not)
Here is the method to find it:
1. Open Terminal
2. cd /usr/libexec
3.
For short info:
./remotectl list
<your UUID> localbridge iBridge2,3 J680AP 3.6 (16P6571/16.16.6571.0.0,0) -
For all the details:
./remotectl dumpstate
I set a camera everytime I worked with the computer and showed the geniuses the videos of kernel panics. Apple support knows the bad magic error yet they make you run thru all the protocol they are given by Apple. Do not give up. Some are really rude. Push push push. I made the apple store prepare reports that the computer cannot be fixed (stamped and signed)
Both of my machines got their logic boards replaced (memory also for imac pro, for macbook pro memory and ssd is on the logic board) I got them replaced. But the issue is on going. There are reddit users reporting problems with 16” macbook pros...
Get your money back if you can, there is definitely something wrong with the T2 hardware. Had it been software, they would have solved it since High Sierra. I am having the issue since High Sierra, Mojave and now Catalina. This issue is very serious but turns out that it will be addressed just like the iphone 6s battery-gate. It took them years to admit... Please write to me and I will try my best to help. Good luck everyone.
I have files I keep to replicate the issue in front of geniuses. Because there is no console log when this happens. They take your macbook pro or imac pro in and say it is ok.
PROBABLE SOLUTIONS WHICH MAY WORK FOR SOME PEOPLE (NONE WORKED FOR ME BY THE WAY =0 )
——-TURN OFF ANY SECURTIY MEASURES THAT NECESSITATES THE USE OF T2 CHIP (SECURE BOOT, DISK ENCRYPTION ETC) from recovery screen before starting mac os.
——-reset the T2 controller: https://support.apple.com/en-us/HT201295#t2"
——"Another recommendation was to reflash the T2 controller firmware: https://help.apple.com/configurator/mac/2.7.1/?lang=en#/apdebea5be51"
———T2 chip query (to check whether replacement logic board is the same faulty batch or not)
Here is the method to find it:
1. Open Terminal
2. cd /usr/libexec
3.
For short info:
./remotectl list
<your UUID> localbridge iBridge2,3 J680AP 3.6 (16P6571/16.16.6571.0.0,0) -
For all the details:
./remotectl dumpstate
I set a camera everytime I worked with the computer and showed the geniuses the videos of kernel panics. Apple support knows the bad magic error yet they make you run thru all the protocol they are given by Apple. Do not give up. Some are really rude. Push push push. I made the apple store prepare reports that the computer cannot be fixed (stamped and signed)
Both of my machines got their logic boards replaced (memory also for imac pro, for macbook pro memory and ssd is on the logic board) I got them replaced. But the issue is on going. There are reddit users reporting problems with 16” macbook pros...
Get your money back if you can, there is definitely something wrong with the T2 hardware. Had it been software, they would have solved it since High Sierra. I am having the issue since High Sierra, Mojave and now Catalina. This issue is very serious but turns out that it will be addressed just like the iphone 6s battery-gate. It took them years to admit... Please write to me and I will try my best to help. Good luck everyone.
Check your T2 model. J680AP seems to be the most faulty one... Though I have seen people in this thread, reporting Bad Magic kernel panic with J780AP
It seems that Apple has manufactured two kinds of _MacBookPro15,1_. One of them has J680AP T2 processor, which is distributed to the market at least before April 2019. The other one has J780AP T2 processor, which should be distributed after that.
It's not hard to find your T2 model:
Go to terminal
/usr/libexec/remotectl list
iBridge2,3 J680AP 4.2 (17P2551/17.16.12551.0.0,0)
It seems that Apple has manufactured two kinds of _MacBookPro15,1_. One of them has J680AP T2 processor, which is distributed to the market at least before April 2019. The other one has J780AP T2 processor, which should be distributed after that.
It's not hard to find your T2 model:
Go to terminal
/usr/libexec/remotectl list
iBridge2,3 J680AP 4.2 (17P2551/17.16.12551.0.0,0)