2018 MacBook Pros crashing with "Bridge OS" error

[xgman]

I am so sick of this stupid error"
{"caused_by":"macos","macos_version":"Mac OS X 10.14.6 (18G29g)","os_version":"Bridge OS 3.6

MADDENING!!!!

Starting to happen at each restart since the last two mojave releases and the latest beta. This is never going to get fixed. And at this point I'd almost be ok with that if they would just tell us why this happens and when to expect hardware that is clean!
[doublepost=1559999852][/doublepost]

Nothing until now,no bridge error but catalina has a lot of little iessues,some already reported here.
Now he cant decide to go back to polish mojave with bridge errors or stay with catalina without this issue
Very frustrating for him last days ..

I don't believe catalina will stay clean for one second. Just wait. . .
[doublepost=1560000185][/doublepost]

I haven’t had a crash for a few months and I’ve had 4 in the past 2 days! Yesterday, it happened and the MacBook restarted. Then, a minute or so later it crashed again. I wasn’t even doing anything.

Yeah, similar story. Very weird.. I just want to know WHY!

 

[timnelso]

Ok, I'll bite. Picked up a refurbished 2017 MBP base model. Same bull-crap. Crashes 3 times daily. I just updated to 10.14.5 Mohave, but before this these are a few of the shutdown codes:

2019-06-06 09:45:32.413686-0400 0xc2 ... kernel: (AppleSMC) Previous shutdown cause: -11

2019-06-06 13:53:23.270644-0400 0xc2 ... kernel: (AppleSMC) Previous shutdown cause: -20

2019-06-06 18:31:32.523973-0400 0xc2 ... kernel: (AppleSMC) Previous shutdown cause: -11

2019-06-07 07:29:05.539992-0400 0xc2 ... kernel: (AppleSMC) Previous shutdown cause: -11

2019-06-07 12:58:16.226970-0400 0xc2 ... kernel: (AppleSMC) Previous shutdown cause: -11

2019-06-07 18:12:18.586498-0400 0xc2 ... kernel: (AppleSMC) Previous shutdown cause: -11

Are those meaningful?

Oh and how do I check for a bridge crash?

 

[Kerbarara]

Mojave has been crashing about once every week on latest version. Also problems with intermittent microfone, trackpad and keyboard after sleep and Touch Bar crashes.

MacBook Pro 2018 Radeon Pro 560X

 

[xgman]

Are those meaningful?

Oh and how do I check for a bridge crash?

They don't seem to have any meaning that Apple can translate, so I'd say meaningless. I had a case with sr. level apple support that was useless. There is a bridge crash log somewhere (maybe in one of the pages in this thread) but I can't remember where, but there isn't any better info there other than to see when they occurred.

EDIT: try this place: panic logs in /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge within Console.

 

[timnelso]

They don't seem to have any meaning that Apple can translate, so I'd say meaningless. I had a case with sr. level apple support that was useless. There is a bridge crash log somewhere (maybe in one of the pages in this thread) but I can't remember where, but there isn't any better info there other than to see when they occurred.

EDIT: try this place: panic logs in /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge within Console.

Wow I find that hilarious. Apple can't translate it's own error codes. Trained monkeys :-(

 

[mreg376]

Hi all,

This may be a little premature, as the 2019 MBPs have only been available for a short time and potentially too short for the following to already have manifested themselves, but I was wondering if any of the early adopters of the 2019 MBPs have seen any of the troubles that the 2018 MBPs have experienced, i.e., has any 2019 MBP had kernel panics, WiFi disconnects, bluetooth disconnects, keyboard problems, external LG monitor disconnects, crackling speakers, corrupted internal SSDs, Software Update failures, Mac App Store failures, AirDrop failures, ping failures, rsync failures, git failures, subversion failures, improperly ejected SMB-mounted external HDDs, Time Machine failures, etc.?

If your 2019 MBP has had any of these problems or others, please list your 2019 machine's specifications and the problems you have experienced.

Thanks,
Solouki

P.S. Since it appears that all of the Mojave updates, both firmware and macOS, have not solved some of these problems for some individuals, I am hoping that the 2019 MBPs do not have these issues.

I asked the same basic question almost two weeks ago. Not a single answer.

 

[hansenc]

I havent had any crashes on 10.14.6 Beta (18G29g)

 

[timnelso]

I know I am going to jinx myself, but after installing 10.14.5 and the 10.14.5 supplemental update I've been running crash free for several days (I was crashing every day before that). Even tried messing with powernap, sleep, etc. to break it and still going fine ... for now :-|

 

[appleuser181]

Hey guys, I know this is random but does the 2019 model suffer from the same BridgeOS crash as well?
I wanted to know if apple fixed this issue without mentioning it anywhere, something they have done in the past!

 

[MacNut]

Hey guys, I know this is random but does the 2019 model suffer from the same BridgeOS crash as well?
I wanted to know if apple fixed this issue without mentioning it anywhere, something they have done in the past!

I assume it's the same T2 chip and the same software in the 2019 MBP.

 

[appleuser181]

I assume it's the same T2 chip and the same software in the 2019 MBP.

Yea they use the same T2 chip on that model as well but I am just wondering how come no one started complaining about that model yet lol

Complaining about the kernel panics due to the BridgeOS issue

 

[MacNut]

Yea they use the same T2 chip on that model as well but I am just wondering how come no one started complaining about that model yet lol

Complaining about the kernel panics due to the BridgeOS issue

Probably not a lot in the wild yet.

 

[Hakiroto]

Yeah, I'd give it some time before coming to any conclusions. As for the crashing stopping with the 10.14.5 update, I hope you don't get any more crashes but I've been crash free for about 4 months and last week, on that version, I had 4 crashes in 2 days. It's now been a few days without one. Same kind of usage and nothing different attached, etc.

 

[timnelso]

Yeah, I'd give it some time before coming to any conclusions. As for the crashing stopping with the 10.14.5 update, I hope you don't get any more crashes but I've been crash free for about 4 months and last week, on that version, I had 4 crashes in 2 days. It's now been a few days without one. Same kind of usage and nothing different attached, etc.

With the supplemental update too?

 

[Hakiroto]

With the supplemental update too?

The 10.14.5 supplemental update is for the 15" models only and I have a 13".

 

[mikedemunck]

I havent experienced any crashes on my 13" 2018 MacBook Pro for months... Always running the latest stable os. Im seriously wondering what causes the crash. If it's a defect in the T2 chip or a serieus bug in it's firmware, wouldn't we all see these crashes? Could it be a piece of software you guys are running which makes for a toxic cocktail?

 

[Hakiroto]

I havent experienced any crashes on my 13" 2018 MacBook Pro for months... Always running the latest stable os. Im seriously wondering what causes the crash. If it's a defect in the T2 chip or a serieus bug in it's firmware, wouldn't we all see these crashes? Could it be a piece of software you guys are running which makes for a toxic cocktail?

Sure, it's possible. I know there was talk of audio software that installed kernel extensions potentially being an issue but as I don't have anything like that it rules it out for me. I use my MacBook Pro in a very standard way: Visual Studio Code, Docker, Node.js, iTerm2, NordVPN, Backblaze, and always a bunch of tabs/windows in Safari. The same kind of workflow I've had for years as a developer using a MacBook Pro. Like you, I had no crashes for months but last week, out of nowhere, I had 4 in 2 days. ¯\_(ツ)_/¯

 

[NasmoQ]

On my 2018 MBP, running 10.14.3, I'd get the BridgeOS crash every night. I turned of the PowerNap option and still had the crashes. I decided to try turning off hibernation and, knock on wood, have a current uptime of several days. In a terminal window I turned it off with the command "sudo pmset -a hibernatemode 0" without the quotes. So far so good.

 

[xgman]

I havent experienced any crashes on my 13" 2018 MacBook Pro for months... Always running the latest stable os. Im seriously wondering what causes the crash. If it's a defect in the T2 chip or a serious bug in it's firmware, wouldn't we all see these crashes? Could it be a piece of software you guys are running which makes for a toxic cocktail?

Various things on make a difference for some. I have very few and only at reboot or startup on occasion, but I have minimized my T2 functions by turning off power nap, file vault, siri, secure boot menu in CMD Recovery, and anything else I can think of. That keeps mine to a minimum, but there are occasions where it just happens out of the blue for no apparent reason. I do agree that there are selective issues going on here and it is extremely hard to trace out. It may not have anything to do with one chip vs another, but may have more to do with how the T2 reacts in certain situations that may be more common with certain users and then throw random in the mix.

 

[donawalt]

I havent experienced any crashes on my 13" 2018 MacBook Pro for months... Always running the latest stable os. Im seriously wondering what causes the crash. If it's a defect in the T2 chip or a serieus bug in it's firmware, wouldn't we all see these crashes? Could it be a piece of software you guys are running which makes for a toxic cocktail?

I too wonder, in fact I think I believe it is a bug based on some combination of a user's usage/apps/settings, since some never get the problem, and I am pretty sure some who get it even get it on multiple machines. In addition, it does seem to be a small percentage of users, again pointing to a unique combination of factors that causes it to happen pretty regularly. I wonder if we will ever know conclusively what the story is..

 

[xgman]

I also think that the signs point to an immature chip that is prone to wacky behavior when taxed or rubbed the wrong way, so to speak, rater than any software conflict as such. And it is very possible that some batches of the chip are less robust than others. It happens. Either way, I'd prefer it wasn't in there to begin with. I've yet to notice any benefit.

 

[mreg376]

So there is still not a single report from a 2019 MBP owner.

 

[taylormills]

So there is still not a single report from a 2019 MBP owner.

MacBook Pro (15-inch, 2019) user here, and I can confirm that this issue still exists... currently happening ~5 times per day.

{"caused_by":"macos","macos_version":"Mac OS X 10.15 (19A471t)","os_version":"Bridge OS 4.0 (17P50466r)","macos_system_state":"running","incident_id":"D23EAB1A-B9AE-4678-BB6E-106F27200928","timestamp":"2019-06-14 21:05:30.96 +0000","bug_type":"210"}

 

[mreg376]

MacBook Pro (15-inch, 2019) user here, and I can confirm that this issue still exists... currently happening ~5 times per day.

{"caused_by":"macos","macos_version":"Mac OS X 10.15 (19A471t)","os_version":"Bridge OS 4.0 (17P50466r)","macos_system_state":"running","incident_id":"D23EAB1A-B9AE-4678-BB6E-106F27200928","timestamp":"2019-06-14 21:05:30.96 +0000","bug_type":"210"}

Ughh. Thanks for the info. I guess... :-(

 

[swissbob]

Ughh. Thanks for the info. I guess... :-(

I guess this error is a Mac book pro and iMac Pro problem, although Mac mini and the Mac book air also are equipped with the T2 they don’t have this problem.

Maybe somebody should do a survey.