Anyone else getting these? New to the T2 machines and not sure what they are or whether I should be concerned?
Anyone?
Anyone?
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.
Bridge OS Panic - MBP 2019 16"
- Thread starter randomgeeza
- Start date
- Sort by reaction score
There is a huge thread on this topic which you may want to check. It took me two days to read through it 
My summary is that look for the "PanicString" that will give you the root cause of the problem. The fact that the T2 act as a watchdog and reports catastrophic errors, does not necessarily mean that the problem lies with the T2.
My summary is that look for the "PanicString" that will give you the root cause of the problem. The fact that the T2 act as a watchdog and reports catastrophic errors, does not necessarily mean that the problem lies with the T2.
Just because the panic mentions BridgeOS doesn't mean that's the actual cause of the panic. Post a log here.
In terminal:
/Library/Logs/DiagnosticReports/ProxiedDevice-Bridge. Logs may be in the Retired sub-folder.
In the console app look for DiagnosticReports > ProxiedDevice-Bridge.
In the log lock for "PanicString" this is the root cause for the problem that is reported by the BridgeOs.
/Library/Logs/DiagnosticReports/ProxiedDevice-Bridge. Logs may be in the Retired sub-folder.
In the console app look for DiagnosticReports > ProxiedDevice-Bridge.
In the log lock for "PanicString" this is the root cause for the problem that is reported by the BridgeOs.
"panicString" : "panic(cpu 0 caller 0xfffffff02132cdd0): macOS panic detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 17P1600\nmacOS version: 19B2106
The "paniString" wraps over several lines. Later down you may find information about "Panicked thread". You could try searching the rest of the log for the thread id.
There should also be a "macOSPanicString", though it may only say something like "Bad magic - no log available".
There should also be a "macOSPanicString", though it may only say something like "Bad magic - no log available".
Got Bad Magic! twice today on a brand new 16 inch from an Apple Retail store with a pretty early build date (late September) according to coconut battery. This was while setting up a fresh install and just installing apps. Not a migration, just signed into iCloud and downloading previously purchased apps from the App Store. It's going right back tomorrow!
If you are within the 14 day return period, I would return it and get another.
T2 problems have been occurring since Apple started using the T2 although the problems appear to have mostly been fixed.
I had a few crashes when my 16" was new, but after a few days in I haven't gotten another one for the past two weeks. Not sure if I should swap mine out or not as I don't want to run into issues down the line. Could it be a software issue while indexing/setting up?
I swapped the machine out. Not because of the crash, but other issues that became apparent. There was slight backlight bleed, and when you touched the bottom case, there was a squeak...? And this far, on the replacement machine I haven't had any of those issues. Still got the popping speakers though...