Except that kernel panics are bad regardless of how they are reported.
That might bring on *a* kernel panic, but it's not going to trigger the sleep related ones I've been having.
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
Except that kernel panics are bad regardless of how they are reported.
That might bring on *a* kernel panic, but it's not going to trigger the sleep related ones I've been having.
Bridge OS panic means nothing in and of itself; the details are elsewhere.
Did you migrate from another install or did you start clean?
I initially set up from a time machine backup. I was receiving the crypto errors in Disk Utility, so I wiped the drive and reinstalled HS and eventually ran migration assistant to get docs and apps back on the machine.
No I’m not. I tried out the Mojave beta but then did a wipe and clean install going back to High Sierra. As many others have stated on here, when you do that certain firmware gets updated.
Last edited:
That memtest question is a good one. Have you had Apple run their service diagnostic on the machine? If a Mac is KPing regularly with a basic OS on it and is under warranty thats grounds for repair....
I have a CalDigit TS3+ as well (love it, actually). I bought it as an attempt to stop the regular while-sleeping KPs I was getting on my 2017 MBP when I had 2 Dell 4K displays attached. (Spoiler: it did not work).
When I got the 2018 MBP I did testing with single- and dual-display configs, with AND without the CalDigit involved. The presence of the TS3+ seemed to make no difference whatsoever. I tested various configurations overnight for weeks when I got the 2018, before I transitioned to it fully from my 2017, just to see if I could find a way to get the machine to sleep well at night.
. Only thing that works for me is turning the power off to the displays w/o putting macOS to sleep, and letting the machine put itself to sleep as a result of lid being closed with no displays connected. This has been pretty stable, and not too annoying.drdaz: as an aside, when you use the TS3+, do you sometimes have macOS get confused about which display is which and reset the arrangement? sometimes I have to power down a display then power it back up for macOS to say "oh, right, that's display number two"
Looking at the Apple update page. It well could be called a security update because it’s something to do with the t2 chip therefore security. Maybe they wanted to save themselves more embarrassment after the throttle fiasco.
It appears as if more problems have arisen from this. But apart from the sleep/dock/startup/external monitor issue. Has anyone experienced a straight up KP say when browsing or sth.
To my understanding that was also an issue a couple weeks ago. Basically are we a step closer?
It appears as if more problems have arisen from this. But apart from the sleep/dock/startup/external monitor issue. Has anyone experienced a straight up KP say when browsing or sth.
To my understanding that was also an issue a couple weeks ago. Basically are we a step closer?
Can someone break down how to look into what could have caused a bridge is failure. Like what do I have to run in terminal to check?
Also is the sleep to wake freeze a seperate issue? Only had that last night after updating high siera. Was fine all weekend and week.
[doublepost=1535557933][/doublepost]
Also is the sleep to wake freeze a seperate issue? Only had that last night after updating high siera. Was fine all weekend and week.
[doublepost=1535557933][/doublepost]
the 2.6 im using same thing except i had one in the first couple days then nothing. maybe it just got it out of its system, so to speak ;-)
I've had similar display goofiness, forgetting arrangement and rotation (my monitor has a super goofy mount point position lol), I've had issues with the computer staying awake with displays connected or waking while in clamshell. All of that, to me, gives credence to the video issue theory, but doesnt SMC sorta handle sleep and display switching to some extent?I have a CalDigit TS3+ as well (love it, actually). I bought it as an attempt to stop the regular while-sleeping KPs I was getting on my 2017 MBP when I had 2 Dell 4K displays attached. (Spoiler: it did not work).
When I got the 2018 MBP I did testing with single- and dual-display configs, with AND without the CalDigit involved. The presence of the TS3+ seemed to make no difference whatsoever. I tested various configurations overnight for weeks when I got the 2018, before I transitioned to it fully from my 2017, just to see if I could find a way to get the machine to sleep well at night.
drdaz: as an aside, when you use the TS3+, do you sometimes have macOS get confused about which display is which and reset the arrangement? sometimes I have to power down a display then power it back up for macOS to say "oh, right, that's display number two"
I’m a developer. That trace is from Mojave. And while the firmware of Bridge OS sticks, Darwin is the BSD based core of macOS. It gets wiped when you wipe your disk.
Run uname -a in a terminal to see what’s actually running.
Listen man... I have been a Mac user/tech for 24 years myself. Contrary to what that log says I know what OS I am running...
17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64
This is somewhat off topic but I’ve posted about my situation a couple times, I’m still very conflicted on whether to go old tech for cheaper (early 2015 broadwell cpu) or go big for new silicon.
Regardless, let’s say I go for the 2018 non customized (one that they offer on their website, base 8gb ram 250 storage etc) and I luck out with intolerable Kp’s. I request return or exchange, how long does that process take? Can I go and have a different machine within the day?
Regardless, let’s say I go for the 2018 non customized (one that they offer on their website, base 8gb ram 250 storage etc) and I luck out with intolerable Kp’s. I request return or exchange, how long does that process take? Can I go and have a different machine within the day?
"Apple Says Latest macOS Supplemental Update Addresses Audio and Kernel Panic Issues on 2018 MacBook Pro"
So, since people still having the same issues after this install..this somehow confirms that is also an hardware issue..
[doublepost=1535566023][/doublepost]Some says "It's T2 hardware issue, there is no patch possible without letting Intel CPU take over some of the tasks, which compromises the performance."
So, since people still having the same issues after this install..this somehow confirms that is also an hardware issue..
[doublepost=1535566023][/doublepost]Some says "It's T2 hardware issue, there is no patch possible without letting Intel CPU take over some of the tasks, which compromises the performance."
"macOSPanicString" : "Global Reset
Do you know anything about what a Global Reset is in the kernel world? About the only reference I could find was:
https://www.intel.com/content/dam/s...ktop/sb/intel_mebx_user_guide_for_7series.pdf
Several MEBx configuration options require a global reset after they have been
edited by the user. The reset is flagged while in the MEBx UI and passed back to
BIOS to perform the reset request. The MEBx UI has to keep track of which
configuration options require a global reset after exiting MEBx. Multiple
techniques are used to ensure the global reset flow is entered correctly.
The MEBx uses 2 flags for its logic related to signaling global resets: Reboot and
Exit. The ‘Reboot’ flag indicates that the current option will require a reboot after
exiting MEBx. The ‘Exit’ flag is used to force the user out of the MEBx UI.
Reboot – MEBx must set this flag when an option that requires a global reset has
been edited from its original state. A list of global reset options is itemized in the
table below.
Exit – MEBx must completely exit the UI immediately after editing the option.
Table of MEBx UI Global Reset Options:
Option Reboot Exit
Max Logins exceeded...................................Y Y
CPU String Emulation...................................Y N
Manageability Feature Selection (EN->DIS).....Y N
Manageability Feature Selection (DIS->EN).....N N
SOL IDER Username/Password...................... Y N
KVM State...................................................Y N
SOL state....................................................Y N
IDER state..................................................Y N
Other MEBx global reset scenarios include:
1. CPU replacement
2. ME Unconfiguration without MEBx password through system BIOS setting (BPF)
3. ME Unconfiguration by clearing CMOS
These global resets happen when BIOS execute MEBx binary during post. In
these cases MEBx will pass the global reset flag to BIOS to perform global reset
without going through MEBx User Interface.
edited by the user. The reset is flagged while in the MEBx UI and passed back to
BIOS to perform the reset request. The MEBx UI has to keep track of which
configuration options require a global reset after exiting MEBx. Multiple
techniques are used to ensure the global reset flow is entered correctly.
The MEBx uses 2 flags for its logic related to signaling global resets: Reboot and
Exit. The ‘Reboot’ flag indicates that the current option will require a reboot after
exiting MEBx. The ‘Exit’ flag is used to force the user out of the MEBx UI.
Reboot – MEBx must set this flag when an option that requires a global reset has
been edited from its original state. A list of global reset options is itemized in the
table below.
Exit – MEBx must completely exit the UI immediately after editing the option.
Table of MEBx UI Global Reset Options:
Option Reboot Exit
Max Logins exceeded...................................Y Y
CPU String Emulation...................................Y N
Manageability Feature Selection (EN->DIS).....Y N
Manageability Feature Selection (DIS->EN).....N N
SOL IDER Username/Password...................... Y N
KVM State...................................................Y N
SOL state....................................................Y N
IDER state..................................................Y N
Other MEBx global reset scenarios include:
1. CPU replacement
2. ME Unconfiguration without MEBx password through system BIOS setting (BPF)
3. ME Unconfiguration by clearing CMOS
These global resets happen when BIOS execute MEBx binary during post. In
these cases MEBx will pass the global reset flag to BIOS to perform global reset
without going through MEBx User Interface.
Last edited:
You should have gotten a message at startup stating your computer had to restart unexpectedly.
You can check for kernel panic logs as follows:
Console App:
/Library/Logs > DiagnosticReports > ProxiedDevice-Bridge
https://m.imore.com/speaker-or-kernel-panic-issues-your-macbook-pro-try-update
So it’s confirmed that this was to address the kps...yet people still seem to have them...
I’ve also noticed that the kp causes vary quite a bit, I’m starting to think more and More this is hardware related some people may have a faulty part a while others got lucky and got a good part a but part b is screwed etc etc...
So it’s confirmed that this was to address the kps...yet people still seem to have them...
I’ve also noticed that the kp causes vary quite a bit, I’m starting to think more and More this is hardware related
some people may have a faulty part a while others got lucky and got a good part a but part b is screwed etc etc...Resetting the CPU is my assumption (think back to the 90s when each computer had a reset button).
AppleSMC - since essentially the power management - runs into a panic for some (presumably software related) reason and triggers a global reset.
Probably designed to address certain issue but not all of them. That or a fix for one issue caused a problem elsewhere?