That sounds like a different issue and hopefully, it is and just a "one-off" that an exchange will solve for you.
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
That sounds like a different issue and hopefully, it is and just a "one-off" that an exchange will solve for you.
Sir, have you got your 4th machine?
I really hope you have been surprised with an updated Vega 20 model!
Just wanted to update you. I let it crash and reboot and now it's actually showing the BridgeOS error:
{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.1 (16P2088)","timestamp":"2018-11-23 21:59:08.96 +0000","incident_id":"5F59DD76-F924-485E-8C75-D58BA45602E9"}
{
"build" : "Bridge OS 3.1 (16P2088)",
"product" : "iBridge2,7",
"kernel" : "Darwin Kernel Version 18.2.0: Mon Oct 8 20:03:53 PDT 2018; root:xnu-4903.221.2~13\/RELEASE_ARM64_T8010",
"incident" : "5F59DD76-F924-485E-8C75-D58BA45602E9",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2018-11-23 21:59:08.73 +0000",
"panicString" : "panic(cpu 1 caller 0xfffffff0168dda00): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 16P2088\nKernel version: Darwin Kernel Version 18.2.0: Mon Oct 8 20:03:53 PDT 2018; root:xnu-4903.221.2~13\/RELEASE_ARM64_T8010\nKernelCache UUID: AF138948FEAD707D71D002FAB422B44B\nKernel UUID: 5EFB3358-9B03-3179-B78B-A1F9981BD380\niBoot version: iBoot-4513.220.97\nsecure boot?: YES\nx86 EFI Boot State: 0xe\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x3\nx86 Previous Power Transitions: 0x20002000200\nPCIeUp link state: 0x94721614\nPaniclog version: 11\nKernel slide: 0x0000000010200000\nKernel text base: 0xfffffff017204000\nEpoch Time: sec usec\n Boot : 0x5bf7d48e 0x00040932\n Sleep : 0x5bf87504 0x000ca2ab\n Wake : 0x5bf8765b 0x000d0649\n Calendar: 0x5bf8780f 0x000685c0\n\nPanicked task 0xffffffe00050a1c0: 3287 pages, 206 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0008de980, backtrace: 0xffffffe016b43530, tid: 405\n\t\t lr: 0xfffffff0174010c0 fp: 0xffffffe016b43670\n\t\t lr: 0xfffffff0172dd610 fp: 0xffffffe016b43680\n\t\t lr: 0xfffffff017311cf0 fp: 0xffffffe016b439f0\n\t\t lr: 0xfffffff017312068 fp: 0xffffffe016b43a30\n\t\t lr: 0xfffffff017313ca0 fp: 0xffffffe016b43a50\n\t\t lr: 0xfffffff0168dda00 fp: 0xffffffe016b43ac0\n\t\t lr: 0xfffffff0168dfe88 fp: 0xffffffe016b43b60\n\t\t lr: 0xfffffff0168dd1cc fp: 0xffffffe016b43be0\n\t\t lr: 0xfffffff016896ab0 fp: 0xffffffe016b43c10\n\t\t lr: 0xfffffff01779c09c fp: 0xffffffe016b43c50\n\t\t lr: 0xfffffff01779b904 fp: 0xffffffe016b43c90\n\t\t lr: 0xfffffff0172e8614 fp: 0x0000000000000000\n\n",
"panicFlags" : "0x102",
"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 106608 **\n",
"macOSPanicFlags" : "0x0",
"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",
{
"build" : "Bridge OS 3.1 (16P2088)",
"product" : "iBridge2,7",
"kernel" : "Darwin Kernel Version 18.2.0: Mon Oct 8 20:03:53 PDT 2018; root:xnu-4903.221.2~13\/RELEASE_ARM64_T8010",
"incident" : "5F59DD76-F924-485E-8C75-D58BA45602E9",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2018-11-23 21:59:08.73 +0000",
"panicString" : "panic(cpu 1 caller 0xfffffff0168dda00): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 16P2088\nKernel version: Darwin Kernel Version 18.2.0: Mon Oct 8 20:03:53 PDT 2018; root:xnu-4903.221.2~13\/RELEASE_ARM64_T8010\nKernelCache UUID: AF138948FEAD707D71D002FAB422B44B\nKernel UUID: 5EFB3358-9B03-3179-B78B-A1F9981BD380\niBoot version: iBoot-4513.220.97\nsecure boot?: YES\nx86 EFI Boot State: 0xe\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x3\nx86 Previous Power Transitions: 0x20002000200\nPCIeUp link state: 0x94721614\nPaniclog version: 11\nKernel slide: 0x0000000010200000\nKernel text base: 0xfffffff017204000\nEpoch Time: sec usec\n Boot : 0x5bf7d48e 0x00040932\n Sleep : 0x5bf87504 0x000ca2ab\n Wake : 0x5bf8765b 0x000d0649\n Calendar: 0x5bf8780f 0x000685c0\n\nPanicked task 0xffffffe00050a1c0: 3287 pages, 206 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0008de980, backtrace: 0xffffffe016b43530, tid: 405\n\t\t lr: 0xfffffff0174010c0 fp: 0xffffffe016b43670\n\t\t lr: 0xfffffff0172dd610 fp: 0xffffffe016b43680\n\t\t lr: 0xfffffff017311cf0 fp: 0xffffffe016b439f0\n\t\t lr: 0xfffffff017312068 fp: 0xffffffe016b43a30\n\t\t lr: 0xfffffff017313ca0 fp: 0xffffffe016b43a50\n\t\t lr: 0xfffffff0168dda00 fp: 0xffffffe016b43ac0\n\t\t lr: 0xfffffff0168dfe88 fp: 0xffffffe016b43b60\n\t\t lr: 0xfffffff0168dd1cc fp: 0xffffffe016b43be0\n\t\t lr: 0xfffffff016896ab0 fp: 0xffffffe016b43c10\n\t\t lr: 0xfffffff01779c09c fp: 0xffffffe016b43c50\n\t\t lr: 0xfffffff01779b904 fp: 0xffffffe016b43c90\n\t\t lr: 0xfffffff0172e8614 fp: 0x0000000000000000\n\n",
"panicFlags" : "0x102",
"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 106608 **\n",
"macOSPanicFlags" : "0x0",
"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",
Oh thats a bummer. Guy in another thread is having screen flickering issues. Thought maybe your issue was similar to his and that the Vega models were maybe not having as much of an issue with the BridgeOS KP's
A T2 chip is in both so I was doubtful that the 2018 MacBook Pro / Vega would be any different from the original 2018 MacBook Pro.
Likely not, unless Apple had determined that the 555/560X cards were a leading cause of the issue. But if that were true they would discontinue using those and they have not. So I am sure you are correct. But one could hope...
Doesn’t mean apple didn’t update the board in the Vega models to fix the issue silently. They are a different board after all.
[doublepost=1543025122][/doublepost]
Not all. The Vega models have not shown this problem yet.
I assumed he had a Vega model since he answered Donawalts question about the Vega models crashing in #2650, but I guess he would have to confirm that.
So, as I'm on the verge of buying a 2018 MacBook Pro again (after having one in summer and returning due to the crashes) I was frustrated that I'll be spending all that money and basically rolling the dice. Due to this I figured I'd email Tim Cook and join others in voicing my concern. To my surprise, the very same day, I got an email back from Craig Federighi! He asked me to send some diagnostics and if I was using any third-party software that installs kernel extensions (kexts) as these can have bugs that cause kernel panics. He also mentioned how Mojave brought fixes to many of these instabilities so this kind of lines up with how lots people on here had regular crashes early on but aren't getting them anymore. I know others are having regular crashes still but you get what I mean.
My point is that Apple are clearly aware of this so if you're having these crashes you should submit them to Apple and give as much information as possible.
Edit: I sent him this thread and referred back to it a few times.
My point is that Apple are clearly aware of this so if you're having these crashes you should submit them to Apple and give as much information as possible.
Edit: I sent him this thread and referred back to it a few times.
Last edited:
That's an alpha firmware. Expect the final firmware to arrive with the next Mojave update. At least we know that they are still working on it.
Confirmed in the quote, but hereby, Vega 20 with i9 and 32GB, 1TB SSD
[doublepost=1543079645][/doublepost]
Funny, mine was shipped with 16P2088
That's also a higher version than what came with 10.14.1.
What is your macos build?
13" model would not be effected with the KP if that would be the case.
There is something deeper behind this.
Just got it replaced btw, but the build number is: 10.14.1 (18B3094), which is explained as a special release to support the new Vega MacBooks here