Did you track the package? I’m wondering how long it took for the turnaround on not the actual repair once they received it until they shipped it back to 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
Did you track the package? I’m wondering how long it took for the turnaround on not the actual repair once they received it until they shipped it back to you.
No I haven’t got the Trackingnumber. I am based in switzerland. Shipping takes 1-2 days in every direction.
Today it was exactly 14 days. 3-4 days shipping, 2 Weekends (Nobody works here on saturday and sunday).
6 days to fix it.
Ok, first panic crash just happened on my Catalina beta (during wake up). (First one in 70+ hours. Already good compared to avg about one Bridge OS error 210 every two or three hours on Mojave)
The error is a bit different from Mojave this time, not the previous BridgeOS bug code 210, so I copied the first two lines here
panic(cpu 2 caller 0xffffff7f9912aa68): "DSB0(MacBookPro15,2): thunderbolt power on failed 0xffffffff\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-365/IOPCIBridge.cpp:1389
I have MBP 13 2018 i7 touch bar.
The error is a bit different from Mojave this time, not the previous BridgeOS bug code 210, so I copied the first two lines here
panic(cpu 2 caller 0xffffff7f9912aa68): "DSB0(MacBookPro15,2): thunderbolt power on failed 0xffffffff\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-365/IOPCIBridge.cpp:1389
I have MBP 13 2018 i7 touch bar.
I get this error "thunderbolt power on failed", too. My MBP 13 i5(Mojave 10.14.5) behaves like this:
- Boot up and log in with thunderbolt display and external HDD connected.
- After some hours suddenly the message "HDD disconnected" appears. Then the thunderbolt ports are unresponsive. But only the side, which is/was currently connected.
- Now, when my book goes to sleep mode and i try to wake it up, it restarts(Apple logo) and i get the bug_type"210" with "thunderbolt power on failed".
I wrote here about same issue..
It started to happed more often. I tried to use TIme Machine with external sdd, and it was really hard to complete because of bridge os error every time...
So I went to service without any hope (because of read much about they found nothing). But, for my luck, my mbp freeze during hardware test that they made in my presence. So, later they called me and told that they found some issues during the test. And they do not know what exactly is broken, but will change whole motherboard with T2, HDD, etc included.
Took it back few days ago. It is ok now, hope will not get more errors.
And also - they told me they have only one more case like me... And mbp 2017 is much more unstable and they have many of them (but most of them with broken keyboard). and for mbp 2018 we also have four years to change keyboard if something happens.
So, I would recommend everyone to go to service first...
and, for those who are from Moscow - it is BroBrolab in Aviapark - very good guys, thanks for them
)
It started to happed more often. I tried to use TIme Machine with external sdd, and it was really hard to complete because of bridge os error every time...
So I went to service without any hope (because of read much about they found nothing). But, for my luck, my mbp freeze during hardware test that they made in my presence. So, later they called me and told that they found some issues during the test. And they do not know what exactly is broken, but will change whole motherboard with T2, HDD, etc included.
Took it back few days ago. It is ok now, hope will not get more errors.
And also - they told me they have only one more case like me... And mbp 2017 is much more unstable and they have many of them (but most of them with broken keyboard). and for mbp 2018 we also have four years to change keyboard if something happens.
So, I would recommend everyone to go to service first...
and, for those who are from Moscow - it is BroBrolab in Aviapark - very good guys, thanks for them
)
No issues on 10.14.6 beta. Been 2-3 weeks without a problem.
I hate watching movies in film and get the Mail.app pop up and split the screen. Anyone else found a solution for this?
MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports) owner here
MacOS 10.14.5
Just crashed over night with
"build" : "Bridge OS 3.5 (16P5125)",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2019-07-11 06:31:46.34 +0000",
"incident" : "8478C3EE-47E5-4081-8A46-8C81449EF218",
"kernel" : "Darwin Kernel Version 18.6.0: Thu Apr 25 21:46:37 PDT 2019; root:xnu-4903.261.4~1\/RELEASE_ARM64_T8010",
"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 496496 **\n",
I'm not very technical so I can't post error messages, because I don't know where to look.
However - I have a 2012 mid year retina MacBook pro 15 inch running 10.14.5 Mohave.
Until recently I found the mac very reliable with perhaps 2 crashes in it's entire life.
Since the last update I am now finding that the machine reboots during sleep and sometimes fails to sleep - ie youtube videos keep playing even though the device is fully closed.
It was interesting to see this thread. Obviously I do not have a T2 chip. Could there be a problem in the software?
However - I have a 2012 mid year retina MacBook pro 15 inch running 10.14.5 Mohave.
Until recently I found the mac very reliable with perhaps 2 crashes in it's entire life.
Since the last update I am now finding that the machine reboots during sleep and sometimes fails to sleep - ie youtube videos keep playing even though the device is fully closed.
It was interesting to see this thread. Obviously I do not have a T2 chip. Could there be a problem in the software?
These crashes and their relevant details are specfic to Macs with T2. It is not related to your MacBook crashes.
I have been dealing with my MacBook Pro 15 inch 2018 for the past three days and I am having the exact same report as yours. Did you happen to know what’s wrong with it? Is it really just a software?
I've been good since April 2nd on 10.14.5 (see my last post here). System uptime before todays update to 10.14.6 was 30+ days (it was 3.01GB!!). My machine started up like I had done a fresh install after 10.14.6, it did the, this is True Tone, try it out screen... and then the we are getting your Mac ready with a bunch of "tick" animations, seems a bit weird.
Again, machine gets flogged in FCPX AE Ps LR with external SSD's and a bunch of handbrake encoding. Plus usual 1 billon safari tabs, spotify, iTunes, streaming in browsers, youtube ect... Happy days.
Again, machine gets flogged in FCPX AE Ps LR with external SSD's and a bunch of handbrake encoding. Plus usual 1 billon safari tabs, spotify, iTunes, streaming in browsers, youtube ect... Happy days.
Just had one of these today on a 15" 2019 MBP that's maxed-out on all specs except storage, running 10.14.5. I do use an external GPU with other accessories (mouse, keyboard, network) plugged into that eGPU -- but only one of the Mac's 4 TB3 ports is ever in use.
{
"caused_by":"macos",
"macos_version":"Mac OS X 10.14.5 (18F203)",
"os_version":"Bridge OS 3.5 (16P5200)",
"macos_system_state":"running",
"incident_id":"55F7EAA0-FCE4-4BFC-A4AE-9D431C6246DB",
"timestamp":"2019-07-24 19:09:29.22 +0000",
"bug_type":"210"
}
I wasn't doing anything other than browsing a forum in Safari, on the external monitor (that is plugged into the eGPU). I clicked on an embedded YouTube video and the system completely locked up. After a minute or two the fan kicked up to full speed very briefly then the system rebooted.
This is the first incident on this system which I've had for a few weeks now.
{
"caused_by":"macos",
"macos_version":"Mac OS X 10.14.5 (18F203)",
"os_version":"Bridge OS 3.5 (16P5200)",
"macos_system_state":"running",
"incident_id":"55F7EAA0-FCE4-4BFC-A4AE-9D431C6246DB",
"timestamp":"2019-07-24 19:09:29.22 +0000",
"bug_type":"210"
}
I wasn't doing anything other than browsing a forum in Safari, on the external monitor (that is plugged into the eGPU). I clicked on an embedded YouTube video and the system completely locked up. After a minute or two the fan kicked up to full speed very briefly then the system rebooted.
This is the first incident on this system which I've had for a few weeks now.
So after reading more of these posts (142 pages is quite hefty) I decided to boot up my VM to cause a crash to get a new error report to peruse and scrutinize. But also from previous posts and local troubleshooting I have since turned off all of my 3d video acceleration, reinstalled the virtualbox guest additions, and kept the VM windowed (not full screen).
So now that I *want* to crash, I've been crash-free for ~10 boots so far.
It has been moody. It has been erratic. But last week I'd've given you a million dollars if you could get 5 boots in a row without a crash. This is one slippery disaster.
So I don't propose it as a fix, but curious if anyone else does what I did (no 3d, no full screen, etc) and has better luck.
Another thing I want to keep an eye on is the firmware version of my T2 Security Chip: 16P6568
So now that I *want* to crash, I've been crash-free for ~10 boots so far.
It has been moody. It has been erratic. But last week I'd've given you a million dollars if you could get 5 boots in a row without a crash. This is one slippery disaster.
So I don't propose it as a fix, but curious if anyone else does what I did (no 3d, no full screen, etc) and has better luck.
Another thing I want to keep an eye on is the firmware version of my T2 Security Chip: 16P6568
recently bought a MacBook Pro, 2019 15-inch with i9 and Radeon Pro 560X. Was upgrading thinking I could do the things I used to do with my other Mac (no Touch Bar, no T2 chip)...boot linux, windows, etc using an external drive. No problem with windows, but installing Linux was pretty much impossible. I haven't tried installing Linux using a different machine, and then booting, and at this point I probably won't because I really want to just throw this computer back to the apple store.
In any case, this i9 Macbook pretty much rebooted about 10 times today and about 5 times yesterday. I'm done with Mac...the programming in the T2 chip pretty much enables apple to limit everything you can do with a 3,000 dollar computer.
running 10.14.6, crashed 5 times yesterday, and 10 times today.
machine is a 2019 MacBook Pro, 15 inch i9 model.
reporting back: no luck.
While my previously listed fix of (VBox: no 3d, no full screen, etc) did seem to give me a decent run of good luck, I am back to my usual modus operandi. Had 5 crashes in a row.
also 10.14.6
While my previously listed fix of (VBox: no 3d, no full screen, etc) did seem to give me a decent run of good luck, I am back to my usual modus operandi. Had 5 crashes in a row.
also 10.14.6
2018 MacBook Pro 15", 2.2 i7, 16GB RAM
Boot-ROM-Version: 220.270.99.0.0
iBridge: 16.16.6568.0.0,0
T2 firmware: 16P6568
Never had the Bridge OS kernel panics up until a couple days ago when I updated to macOS 10.14.6. Overall it seems that the original macOS this Mac shipped with was the most stable one (something like 10.13.6), and I hope that macOS 10.15 is better. Probably gonna do a fresh install when it comes out.
EDIT: Reset the SMC, NVRAM/PRAM and did the 10 sec. power button hold to restart the T2. Let's see. Also did a "repair install" of macOS and looked with EtreCheck if I have any kind of junk on the system.
Boot-ROM-Version: 220.270.99.0.0
iBridge: 16.16.6568.0.0,0
T2 firmware: 16P6568
Never had the Bridge OS kernel panics up until a couple days ago when I updated to macOS 10.14.6. Overall it seems that the original macOS this Mac shipped with was the most stable one (something like 10.13.6), and I hope that macOS 10.15 is better. Probably gonna do a fresh install when it comes out.
EDIT: Reset the SMC, NVRAM/PRAM and did the 10 sec. power button hold to restart the T2. Let's see. Also did a "repair install" of macOS and looked with EtreCheck if I have any kind of junk on the system.
Last edited: