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
Was this during normal use or during sleep/wake? Would you be so kind as to share the task/thread that panicked? You can use the instructions in my post here:
https://forums.macrumors.com/thread...bridge-os-error.2128976/page-51#post-26384166
I just scanned through all the kexts on my system before/after the update and I am not really seeing much changed on the macOS side, although it did appear that there was at least 1 firmware update during the install, so this update could be more on the hardware/firmware side of things.
like i said..if Apple would release a fix for the bridge error...this update would be on the imac pro too...
I think this is for the audio issues of the MBP
I think this is for the audio issues of the MBP
Damn... Are you serious?
[doublepost=1535485176][/doublepost]
That's a really good logical point.
According to my Apple support specialist, you are wrong. She isn't L1 either, this is the person I've been uploading diagnostics captures to.
prove me wrong....you will see bridge OS error from now on still..
Careful if youre making mu
Please show the full stacktrace. This information is useless. Might as well be a regular OSX Kernel Panic
Please show the full stacktrace. This information is useless. Might as well be a regular OSX Kernel Panic
Define wrong, wrong as in its not just the audio that was rectified? Or wrong as in the bridgeos was in fact rectified
I was talking to the senior tech on my case at Apple about this. He implied that all panics on machines with T2 chips would refer to the Bridge OS.
I know for a fact that no senior advisor would specify one way or another so...
[doublepost=1535485948][/doublepost]
That’s been my experience too.
You said this update isn't intended to fix kernel panics. I said you're wrong. That doesn't mean the update will fix the KPs. We're talking about what the update is intended for.
[doublepost=1535486115][/doublepost]
Thats what I've been suspecting. So really you have to analyze the stack trace which is a major PITA.
[doublepost=1535486261][/doublepost]
Wrong as in, he claims this update isn't intended to fix kernel panics.
The senior tech on my support case called me specifically to make sure I installed the update and monitor for more KPs.
This happened during normal usage. 13" MBP is in clamshell mode (bluetooth keyboard and trackpad). The trackpad just stops clicking and I know I'm screwed.
TID: 382; Name: AppleSMC
I'm now using USB-C to Display Port cord to a Dell 3415W. Previously, I was using the HDMI adapter from apple and that also crashed multiple times during normal usage (I originally thought the adapter was the issue before finding this thread).
Like I said, things had been going really well for the past few days. I was excited to see this update but it crashed about 15 minutes after installing.
But note, I've never really experienced the sleep issues on this laptop (my work laptop) just these normal usage lockups. However, I do experience the sleep/wake issues on my personal laptop (also a 2018 13", hooked up to a LG 5k). I haven't installed the update on that machine yet, but will later tonight.
So in actuality this update may not be T2/KP related at all. It might be for other MBP specific issues, hence why the update is not for the iMP as well which also suffers from T2 related KPs. Fingers crossed they are still working on this.
Thanks for sending this one King724, that's actually quite insightful since it's actually macOS crashing on you, not the T2 chip:
Presumably Dropbox related:
At least this somewhat confirms that bridgeOS is also collecting regular macOS crashes on those machines (which will add to a lot of confusion since it's even harder to differentiate all these crashes between bridgeOS and macOS).
Code:
"panicString" : "panic(cpu 0 caller 0xfffffff018773984): macOS panic detected\nDebugger message:Presumably Dropbox related:
Code:
BSD process name corresponding to current thread: Dropbox\n\At least this somewhat confirms that bridgeOS is also collecting regular macOS crashes on those machines (which will add to a lot of confusion since it's even harder to differentiate all these crashes between bridgeOS and macOS).
Sorry for the mix up! (I've edited my original post and added a note about it being Dropbox).
Looks like the classic AppleSMC related T2 crashes we've been seeing ("tid" number matches the AppleSMC thread in the txt file)
@matthewadams what a guy, our own tech support.
Installing now, just to note, in the Apple Store all the computer I checked appeared as if they were running the new version. There was no real way of checking apart from going to the App Store and looking for updates.
Stated everything was up to date.
Installing now, just to note, in the Apple Store all the computer I checked appeared as if they were running the new version. There was no real way of checking apart from going to the App Store and looking for updates.
Stated everything was up to date.
Ring them up, and ask to be put through to Aftersales / Customer Services. Tell them exactly what's happened, i.e. the support are saying perhaps Mojave will sort things out and that you don't want to be left with a device that may not work after the OS.
If they say no, then just hit them back saying are you not confident that your MBPs are of standard. The only grounds I would return this device is if the OS doesn't fix this specific problem. They should succumb to that.
