You fix it by returning it and buying something else.
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
You fix it by returning it and buying something else.
This doesn’t make any sense, unless you mean to say Apple basically botched the T2 implementation.
Every Mac contains hundreds of chips that Apple doesn’t have design control over. It’s Apple’s job to design the computer in such a way that each chip works together properly. That’s why they have specifications for each chip.
Plenty of other manufacturers make computers with Intel chips without having design control over them and they don’t have these issues, nor do they exist in pre T2-equiped Macs. If anything, you could say it’s because Apple has design control over the T2 that these peoplems have arisen.
Control over other components is not the cause of the T2, its apple's design, and/or execution of the T2 architecture. Lets not shift the blame to not having the details of the intel CPUs when they added a proprietary chip to something that was working fine.
[doublepost=1546257095][/doublepost]
I'm not getting your point, the T2 is an Apple designed ARM processor. Its really not that much different then the CPU found in the watches, which is a lower powered varient to Apple's other idevices.
I probably expressed it poorly.
I think that Apple will put the T2 functionality of the existing T2 ARM into the next generation ARM designed to run in the laptops (i.e. one chip to do everything).
In the end, the fault would be on Apple.
Maybe its my ignorance, but there is no hardcoded functionality in the T2 that is not already in the Apple's Ax CPUs and as it boils down, the T2 is just a CPU that controls certain features. Again I could be misunderstanding the details, but it's my thinking the T2 is just a CPU nothing more, nothing less. The problems are due to the T2 interfacing with the logicboard in such a way that is causing instability. The OS that is running the T2 specifically.
I think it's a matter of semantics. That's why I specified the functionality (programming) in the T2 chip (security implementation, etc).
On an ARM(only) Mac, the security enclave can be done like how it is on an iPhone, just a processor core SoC onto the main A series chip.
Thanks for the detailed post. I just had my first encounter with what could be a KP, though not convinced. I verified by checking "Library>Logs>DiagnosticReports>ProxiedDevice-Bridge" directory. I exhibited the same exact symptoms as you, keeping the display opened, and when I returned around an hour or so later, that's when I experienced the issues. Closing and opening the lid did not solve the issue of a dark display that I couldn't get to turn back on. I actually was using Screens to control my Mac via my iPad prior to returning to use my Macbook. I was forced to hold down TouchID button to force a reboot.
I had the same bug_type":"115 as well, though I did not have the same second log as you had. The file name: "ResetCounter-2018-12-31-183546".
Also, to your theory about the "Prevent the computer from sleeping automatically when the display is off" setting in Energy Prefs: my crash occurred when I was plugged into Power, and hence this feature was toggled On, unlike in your experience. So, I don't think this is something related to the crash. Appreciate your detailed post though - I believe yours was the only other bug_type":"115 in the thread and we experienced the exact same symptoms.
As many of us know, there are all sorts of bugs dating back years related to Macs waking from sleep, especially when connected to peripherals i.e. displays. So hopefully this is just a one-off occurrence related to a bug that's actually related to a MacOS bug versus something related explicitly to a T2 'Panic'. My rationale is this would be a function handled by the T2 (hence the crash report) but not a crash caused as a result of a T2-related issue. Hopefully this is a one-off
FWIW: I have a 2018 15 Inch MBP i9 with 10.14.2 installed.
Last edited:
Some things come to mind you can try. Enable FileVault, confirm Secure Boot is set to Full Security, use an external high res monitor, make it Sleep/Wake alot (this has been the big one), check the logs /Library/Logs/DiagnosticReports, update the OS if you have an older or unpatched one. If you hear Steve's voice all is good, if not, get your notepad and receipts ready and phone charged.
Thanks unglued. This is the fifth Powerbook/MBP I have had, with each one lasting me 5-6 years. On all but one occasion the first copy has been straight back, the most recent two occasions because I have been unhappy with uneven backlighting. This is also the first one I have bought new in 10 years; I have bought refurbs but clearly with the refurb store flooded with high end models (for the first time ever as far as I know) a refurb is not currently a sensible purchase.
I'm fully prepared for it to go back. The only things I will be putting on it in the first instance is audio & photographic software to test its performance and screen to the limits.
Cheers.
I have an update. I was able to reproduce this Bridge OS KP 3 out of 3 times. I’ve been in touch with a senior Apple Advisor. She had me do a data capture using an Apple app and sent the info to an Apple Engineer. I should hear more next week.
Knocking on wood, the Bridge OS KPs I’ve had have all occurred when waking from sleep. It’s inconvenient but not enough for me to return the MacBook Pro. My holiday return window closes in 2 days and I’ve decided not to return it. I’ll keep working with Apple Support. If the KPs increase in frequency or start occurring while I’m working then I’ll try to get a new replacement under AppleCare. I’ve been working with Apple Support on this problem since December 5.
Last edited:
So, I'm in the position where I've got a 2018 MBP15, and a 2018 Mac mini. I bought the MBP to replace an older MBP that became too unreliable for work (it keeps eating fans at a rate of 2/year) as a stop-gap solution until a new desktop was released. Upon release, I bought a BTO mini to be my daily machine, the MBP was to become a travel/spare (i.e in case of hardware faults).
Sure enough, around Christmas the mini crashed and showed the infamous T2 error. I chatted to apple support, they suggested a reinstall, i started that, and it crashed halfway through installation - i chatted to them again and they agreed it should go in to be looked at.
I took it in to an authorised service centre here (Thailand) with a printed page explaining what had happened, and the Apple Support case ID. They accepted it, and seemed to spend a lot of time recording details from the printout.
When I got it back, it turns out they just did a reinstall, and I noticed the original ticket just had: "Fault description: software error" (in Thai, hence I hadn't noticed it when dropping it off). Great so they've solved nothing.
While they had the machine, what do you think happened? The MBP (which took on the role of "spare" pretty well - despite having only 16GB vs the mini's 64GB memory) has started crashing, and upon bootup shows the same T2 error.
Without reading through 120 something pages of replies can someone summarise any approach that has worked at first-party Apple stores (it's a PITA to get to from here, but I'm sick of the "ignore what we're told, do as little as possible to get this thing out the door" approach of the 3rd parties here) to get a decent response? I've got at least 2 hard crashes now on each machine, but one without any log of it (it was during the re-installation).
The next problem is which order to try and get them replaced. I need a machine for work, and neither one has crashed so often that it's unusable.
The mini is BTO, so likely to take longer for a swap, but it also realistically doesn't run 2 4K displays as well as the MBP, and I haven't got an eGPU yet (I've also given up trying to order from local resellers of US brands or the more available Chinese brands for accessories). The MBP is just an off-the-shelf model so if it's to be replaced they almost certainly have stock in hand.
Maybe I should just take both with me, explain the situation, and hope that having spent $US7K on Apple hardware they'll be willing to swap the MBP on the spot and order a replacement mini?
Sure enough, around Christmas the mini crashed and showed the infamous T2 error. I chatted to apple support, they suggested a reinstall, i started that, and it crashed halfway through installation - i chatted to them again and they agreed it should go in to be looked at.
I took it in to an authorised service centre here (Thailand) with a printed page explaining what had happened, and the Apple Support case ID. They accepted it, and seemed to spend a lot of time recording details from the printout.
When I got it back, it turns out they just did a reinstall, and I noticed the original ticket just had: "Fault description: software error" (in Thai, hence I hadn't noticed it when dropping it off). Great so they've solved nothing.
While they had the machine, what do you think happened? The MBP (which took on the role of "spare" pretty well - despite having only 16GB vs the mini's 64GB memory) has started crashing, and upon bootup shows the same T2 error.
Without reading through 120 something pages of replies can someone summarise any approach that has worked at first-party Apple stores (it's a PITA to get to from here, but I'm sick of the "ignore what we're told, do as little as possible to get this thing out the door" approach of the 3rd parties here) to get a decent response? I've got at least 2 hard crashes now on each machine, but one without any log of it (it was during the re-installation).
The next problem is which order to try and get them replaced. I need a machine for work, and neither one has crashed so often that it's unusable.
The mini is BTO, so likely to take longer for a swap, but it also realistically doesn't run 2 4K displays as well as the MBP, and I haven't got an eGPU yet (I've also given up trying to order from local resellers of US brands or the more available Chinese brands for accessories). The MBP is just an off-the-shelf model so if it's to be replaced they almost certainly have stock in hand.
Maybe I should just take both with me, explain the situation, and hope that having spent $US7K on Apple hardware they'll be willing to swap the MBP on the spot and order a replacement mini?
From what I understand, what has happened is this. Apple has included two separate processors, the Core i5/i7/i9 and the T2, in these machines - the T2 is basically an A11 chip found in older iOS devices and it runs a modified version of watchOS. BridgeOS is just what its name implies, it is intended to bridge the gap between an ARM processor (the T2) and an x86_64 processor (the Core i5/i7/i9 series) and BridgeOS isn't up to the task. This problem has been going on for a year now (started with the iMac) and that tells me that either (a) this is a bigger problem and requires more work than Apple is letting on, or (b) Apple doesn't know how to fix the problem.
My question is why do these machines actually need two separate CPU's and two separate operating systems? Clearly this has turned out to be detrimental for users.
Apple claims that the T2 chip was needed for security but many users doubt that is the only reason.
Many users here believe that the primary reason is more control by Apple and that the T2 wasn't really needed.
I’m aware of what the T2 is/does.
I was specifically asking if anyone has worked out a good approach to get apple support staff to acknowledge it’s a fault and replace the machine.
The way development works is that you often don't know how to fix a given problem, until you figure out the solution. Apple has no excuses. They have access to all of the hardware and human expertise necessary to figure this out. Why they haven't? I'm taking a wild guess here, but I would suspect that the problem is a very fundamental problem which can't be bypassed without essentially disabling the T2, and writing an entirely new software stack to pick up the slack. I'm hoping I'm wrong, but if the problem was something they could fix easily, you'd think they would have done it by now. Ages ago, in fact. But, proper testing would most definitely have caught this issue, considering how common it seems to be in day to day usage.
P.S. I looked for this thread because a few minutes ago, I had another BridgeOS crash. Joy.
[doublepost=1546795661][/doublepost]
The issue is that this seems to be an issued triggered by certain usage patterns, and unless you're willing to take the time to find a usage pattern which doesn't cause the thing to crash (mostly involving reduced T2 usage), replacing the computer probably won't fix it.
Reading through the thread, most people were able to solve their T2 problem by getting a replacement. For some people, multiple replacements worked while for for some others , they weren't able to find a replacement that worked.
I still believe that it is most likely a T2 hardware issue.
I'm always skeptical of people who tell me something's fixed, when they're not sure what the actual problem was in the first place. For all we know, they had a panic immediately after reporting it "fixed", or perhaps they just haven't had one yet. I've managed to go an entire week or two without a panic, and sometimes I get them a few times a week, or even a couple in one day. You can't verify that the problem's fixed, if you don't know what the problem was to start with.
I can agree with that except, reading through the post, many people have not got a T2 error since replacement. If people don't get a replacement, the only sure way of not getting a T2 error would be not getting a Mac with a T2 chip in the first place.
It's called mucking up the works. They simply added another possible point of failure to add features that no one was asking for.