BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

Hi olivier300, Sorry to interrupt you. I could not do the SMC rest sometimes. Even though I could do it, Nothing to being improved. It depends on the condition and maybe the lot. It's complicated according to Apple Store Genius bar staff. Maybe 2019 model is the best...

The same problem with MBP 13' 2018 with Touch Bar

MacBook Pro (13-inch, 2018, 4 TBT3), macOS Mojave (10.14.1)

I don't have any peripheral devices only the charger but when it happened I have used the charger from Google Pixel 2 xl and in macOSPanicString "thunderbolt power on failed" maybe this caused the problem.

Very disappointed by this device

Re: Kernel panic on wake

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 3.1 (16P1065)","timestamp":"2018-11-02 17:45:28.78 +0000",

...

"build" : "Bridge OS 3.1 (16P1065)",

"date" : "2018-11-02 17:45:28.31 +0000",

"kernel" : "Darwin Kernel Version 18.2.0: Fri Oct 5 20:16:59 PDT 2018; root:xnu-4903.221.2~4\/RELEASE_ARM64_T8010",

"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 941088 **\n",

"macOSPanicFlags" : "0x4",

"macOSPanicString" : "panic(cpu 0 caller 0xffffff7f88cf3307): \"DSB0(MacBookPro15,2): thunderbolt power on failed 0xffffffff\n\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/IOPCIFamil y\/IOPCIFamily-330.200.11\/IOPCIBridge.cpp:1314\nBacktrace (CPU 0),

That is true for me, I had this problem only when MBP was closed but I don't have clear steps to reproduce this problem

That fits with what the engineer told me. Machines that went to sleep by closing the lid, or by inactivity, were both having crashes. Also, they had no way to reproduce the problem at will. It happened intermittently, with some machines having the problem multiple times per day, while others could go a week or more with no issues. My two machines had very different frequency of crashes. The first was 3-4 times per week, and the other was less than once per week.

According to the engineer, only a very small percentage of machines sold were reporting the problem, however, if users pressed "cancel", rather than "report problem" in the crash reporter app on reboot, then Apple wouldn't know there had been an issue. Given the variability in frequency, and users not reporting crashes, they were unable to know what percentage of machines sold had the problem.

The lack of reproducibility was also making it hard for the engineers to determine the cause. With no definite cause, they were guessing what was wrong, so while they put together software patches for possible causes, they couldn't know if it had worked until a large number of people with the problem tried the patch and reported back. I used to be a support engineer for NCR Unix systems, and that kind of situation was both rare and a complete nightmare. Until a definite cause was known, rushed fixes were a stab in the dark, very rarely paid off, and sometimes introduced new problems. In fact, it was much smarter to carefully add instrumentation to try and diagnose the problem, rather than to try to actually fix it.

I'm guessing there was a manufacturing fault, for which a software fix has not yet been found. If the problem was still there, then as more machines are sold, I'd expect more and more people contributing to this thread, but the thread isn't getting more active over time. On the other hand, if a software fix had been found, then the thread would die out completely. So, my hunch is they found a manufacturing fault and addressed it (hence the thread is not getting more active), but have yet to find a software fix for the pre-hardware-fix machines (hence the thread is still active, but not growing).

Anyway, that's my 2 cents worth. I'm glad I returned my machines while still under the 12 month warranty. I just wish I could find out if the new machines were any better, so I could get on with upgrading again. My 2009 & 2012 MBPs are seriously struggling. 😟

Own a new MBP 13.3" with TB and 512GB for about a week. I am having at least one kernel panic a day connected to BridgeOS bug_type 210. Talked to the Apple support and an Apple service provider. Nobody knows what's the problem and how to fix it. Apple support suggested a clean install, but this didn't fix the error for me.

Next step would be a reset of the T2 chip. Therefore a second Mac with at least High Sierra is needed.

Did anyone test this?

P.S.: Had a nice working MBP2011 15,5" i7 with SSD, but unfortunately it stopped working due to the known graphic issue. I am really happy that Apple replaced the Logic board with the same faulty chip two years before....

jttaggart wrote:

Let's hope the fact that it's in new machines results in more attention being paid

Sadly, I wouldn't hold your breath.

Going back to August, or possibly before, Apple had a dedicated team trying to find the issue, with no apparent success so far.

Also, there are active threads a year old for iMac Pro's with very similar BridgeOS issues. There must be people who's warranty is ending about now.

Bottom line: One year down Apple continue to sell machines with known issues AND has released four new machines with BridgeOS issues!

What happened to "It Just Works" hey? Poor old Steve must be turning in his grave at an extraordinary RPM.

Hi LoveSteveJobs,

Yes I did install the supplemental update first thing upon receiving the MBA. I installed it through the 'About This Mac -> Software Update' interface. Yes 2018 MBA was connected to a power outlet when I experienced the Bridge OS crash.

This is very interesting. Last week I got my 3rd MacBook Pro 2018, Mojave 10.14.1. The 2 I had previously were crashing with Bridge OS 3.1 error. I was going to get an iMac without the T2 chip as I had to get work done but couldn't get one until 5th December so my only option was to try another MacBook. Since getting the 3rd machine last week I haven't had a single crash. I was wondering if it was hardware or software related and if they had updated Bridge OS. What is very interesting is that you got Bridge OS 3.2 error. Maybe that fixed the problem or maybe not. In your case, not.

And yes, they appear to have been aware of this problem for a year. What I find, (ironic or absurd), is that they suggest you turn off everything related to T2 chip which kind of defeats the purpose and also indicates that they are pretty sure that's the problem. Apple are definitely not the company they used to be.

A very sobering and **** annoying bottom line to say the least. My sympathies.

From other threads, I have learned that these errors show up on on the display models in the Apple stores too.

Hi Andrew, when you see "macOS watchdog detected" panic, what did you do before you see this?

Please, try the steps from "Energy Saver" comment above.

Did you have it fixed? I have same issues

For the BridgeOS version number:

About this Mac -> System report -> Hardware/Controller

I have a French version, so words may differ...

iMac Pro has the 33.2 firmware. Not sure it’s meant for MacBook Pro.

My MBP has been working so well for the last few weeks, I am nervous about updating to Mojave. Advice? Are a significant number of us that have had restarts now running Mojave?

I did wind up replacing my machine, but was quite wary.

It has been working fine so far (about 3 days), but my fingers are still crossed.