Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

December / MacOS 10.14.2 2018 Macbook Pro "Bridge OS" Kernel Panic Poll

Has your 2018 Macbook Pro KP'd with the Bridge OS error since 10.4.2 GM

  • Total voters
    119
  • Poll closed .
RumorConsumer said:
So interestingly (if these napkin statistics are any indication of reality) our ratio of affected machines is going down. We were at 70/30 in November and now we're above 80% not affected or resolved. That seems like its within the margin of error for either "small progress" or "nothing has changed". One thought I had was to start another poll for mid-month asking only those who had issues if their issues were resolved. Thoughts?
Click to expand...

I think that the only information that's important is the number of people experiencing faults before the updates and the number after.

It looks like Apple has made some headway but that the T2 faults still can occur.

It will be very difficult for the user to get a handle on the T2 faults until Apple acknowledges them and gives a cause.
 
  • Like
Reactions: xgman
MacBook Pro (15-inch, 2018) i9 32GB ram user here. Laptop is about 1 month old.

The latest BridgeOS update that 10.14.2 brought improved things a lot compared to the previous situation where I would, at worst, 7 KPs a day: since I installed it on Dec 7th, so far I have received 2 KPs. Unfortunately even 1 KP is really one too many as interrupting the workflow can be catastrophic (not to mention losing unsaved data).

I am torn about returning the laptop back and enduring the productivity hit while waiting for its replacement or pray that a follow up update from Apple will fix the issue entirely. In this regard it'd be very helpful to know if this issue affects certain machines due to a hardware fault that currently Apple engineers are trying to workaround with bridgeos updates or something else; of course it's unlikely we'll ever know for sure.
 
Plutonius said:
I think that the only information that's important is the number of people experiencing faults before the updates and the number after.

It looks like Apple has made some headway but that the T2 faults still can occur.

It will be very difficult for the user to get a handle on the T2 faults until Apple acknowledges them and gives a cause.
Click to expand...

Well all I know is I had zero faults with my imac 17 with the exact same installs and same peripherals and now with the new imac pro, I continue to have bridge os crashes on some startups. It's maddening. I also get hung shut downs but I don't think that is related. I've grown to hate turning on the computer. By the way tried the current new beta and it got worse.

I am ready to try a new imac pro if Apple will cooperate, but I see no signs of that whatsoever. What a waste of money.
 
Last edited:
So I last posted in the Nov poll, but it's now been more than a month since I got my MBP back from the repair center and still no KPs and still on 10.14.1. I still have no idea what they did - as I posted before, the work order says they only wiped the computer and did a clean install of the OS. Whatever magic they performed, I'm still in the clear...
 
pulch said:
So I last posted in the Nov poll, but it's now been more than a month since I got my MBP back from the repair center and still no KPs and still on 10.14.1. I still have no idea what they did - as I posted before, the work order says they only wiped the computer and did a clean install of the OS. Whatever magic they performed, I'm still in the clear...
Click to expand...
thats somewhat remarkable actually
 
  • Like
Reactions: SDColorado
pulch said:
So I last posted in the Nov poll, but it's now been more than a month since I got my MBP back from the repair center and still no KPs and still on 10.14.1. I still have no idea what they did - as I posted before, the work order says they only wiped the computer and did a clean install of the OS. Whatever magic they performed, I'm still in the clear...
Click to expand...
That is all they ever offer to do. Wipe and start over. Did it ever occur to them that computers are for using and not for wiping? Whatever, that is all they ever suggested for my case. I told them never mind and just close it. Useless!
 
Plutonius said:
Unfortunately, that's all they can do :(.
Click to expand...
Thats not true. I have sent many, many, many computers to Apple's repair depot and they will occasionally ignore obvious failures and do a software restore, while other times replacing god knows how many components when it was something that seemed quite easy. The repair depot ultimately does a phenomenal job in my experience.
 
The repair depot can't fix a flawed piece of hardware like the T2 chip. (or can they?) either way they won't admit a problem.
 
  • Like
Reactions: Plutonius
Mine has been crashing more frequently than ever (which is still to say not a lot). Especially when I let the machine sleep with my 2x 4k UltraFine displays connected. . . .In fact, that is the ONLY time it crashes. This morning I was greeted with a login screen and the other day I plugged the displays in and both went yellow and the machine rebooted. Yay.
 
I have been checking out al of the forums here. I am now convinced that the T2 problem can happen with every model Apple has released with the T2, from the iMac Pro last year, the 2018 MacBook Pro, 2018 Macbook Air and 2018 Mac Mini. That's just the way it is, with Apple refusing to acknowledge the problem, apparently unable or unwilling to do anything about it, and they continue to ship these devices with the same issue. So there we are. Buyers BE BRAVE, and if you take the plunge on any of these models be prepared to spend your life with the "Geniuses."
 
  • Like
Reactions: Howard2k
mreg376 said:
I have been checking out al of the forums here. I am now convinced that the T2 problem can happen with every model Apple has released with the T2, from the iMac Pro last year, the 2018 MacBook Pro, 2018 Macbook Air and 2018 Mac Mini. That's just the way it is, with Apple refusing to acknowledge the problem, apparently unable or unwilling to do anything about it, and they continue to ship these devices with the same issue. So there we are. Buyers BE BRAVE, and if you take the plunge on any of these models be prepared to spend your life with the "Geniuses."
Click to expand...


I’m sure statistically the issue isn’t massive. I bet we’re talking about a relatively small number of machines overall. But there are still far too many incidents being reported for my taste. I was considering a 2018 13”, the quad core would be great, but that’s a ******** of money to spend on a machine that might be flakey.

I’ll wait for T3 for sure, and only then if it’s rock solid. Otherwise I’ll hang onto my 2015 until it gives up the ghost and grudgingly move back to Windows. There’s just no way I’d spend the kind of money Apple is asking on a T2 based system.
 
Agreed. Of course we can't be sure how massive the problem is, and we only see a tiny snapshot of users here, but since the exact same apparent defect is spread across many models I think we can conclude that this is a major, if not "massive," problem. Even more disturbing is that it's been a year and Apple is still shipping new devices, from $1,200 to $13,000 each, with the same issue.

EDIT: Speaking of disturbing, I recently bought a 2018 i7/16GB/512GB MacBook Pro and after it froze five times in a row just trying to get it to update from macOS 10.14.1 to 10.14.2, I returned it. AT NO POINT during the mail return process did Apple even ask why it was being returned.
 
Last edited:
  • Like
Reactions: turbineseaplane
mreg376 said:
Agreed. Of course we can't be sure how massive the problem is, and we only see a tiny snapshot of users here, but since the exact same apparent defect is spread across many models I think we can conclude that this is a major, if not "massive," problem. Even more disturbing is that it's been a year and Apple is still shipping new devices, from $1,200 to $13,000 each, with the same issue.

EDIT: Speaking of disturbing, I recently bought a 2018 i7/16GB/512GB MacBook Pro and after it froze five times in a row just trying to get it to update from macOS 10.14.1 to 10.14.2, I returned it. AT NO POINT during the mail return process did Apple even ask why it was being returned.
Click to expand...

It’s true this feels rocky and the good news is they’re using all the same stuff. They’ll dial it in I have faith.
 
Well I got my 2018 MPB 13" i5 a few days ago, it had Mojave preinstalled (I don't remember the exact version), after using Migration Assisgant from 2015 MPB I got first crash within few hours but forgot to capture the crash log because I blamed it on the migrating data from old machine.

So I decided to erase the disk completely and proceeded with clean installation of Mojave 10.14.2 through Recovery Tools. After a few hours of using under idle load it crashed again so I saved the log.

In it's content's it's clearly visible that the issue was kernel panic caused by the Bridge OS 3.2 (16P2542).
It doesn't look really good considering that this T2/Bridge OS issues are happening now for almost a half a year and there is still no solid solution from Apple.
 
  • Like
Reactions: SDColorado
Good lord do they need to get this fixed..

Brand new computers crashing after a simple migration?

I've restored 3 different older Mac's from migrations this week and they all went flawlessly.
C'mon Apple - get your ish sorted
 
  • Like
Reactions: SDColorado
mjedynski said:
It doesn't look really good considering that this T2/Bridge OS issues are happening now for almost a half a year and there is still no solid solution from Apple.
Click to expand...


Well over a year. The T2 issue didn't start with the MBPro, it started with the iMac Pro.
 
  • Like
Reactions: SDColorado
Has anybody noticed that in the original poll the majority of people have never had a T2 issue?
 
mjedynski said:
So I decided to erase the disk completely and proceeded with clean installation of Mojave 10.14.2 through Recovery Tools. After a few hours of using under idle load it crashed again so I saved the log.

.
Click to expand...

Are you seeing this Apple? (guess not since they only look on their forum) but it shows the wipe and start over method isn't any better than the "pull out" method. Both are wishful thinking.
 
Very interestingly though, "No and Never Did" is a dominant force here. It flies in the face of the "any of these machines are capable of crashing at time" theory.
 
RumorConsumer said:
Very interestingly though, "No and Never Did" is a dominant force here. It flies in the face of the "any of these machines are capable of crashing at time" theory.
Click to expand...
I’m part of the “No and Never Did” but it’s only been 3 weeks. One issue I have is the battery percentage, there’s roughly a 5% difference at the logon screen compared to after logged-on, someone said FileVault is the cause and disabling it is a temporary fix, a cosmetic issue.

I still have FileVault encryption enabled, it sleeps/wakes alot, and one cable connected to a CalDigit TS3 Plus dock for charging, using an external monitor (dp-to-dp/native 1920x1080), external SSD/Time Machine, USB scanner, USB cooling pad, 3.5mm audio to soundbar, and hardwired network and it’s undocked time to time. Also using a bluetooth keyboard and mouse. I did wipe the internal SSD clean, checked for errors, and installed 10.14.2 the first day I received it but probably nothing related to the KP issues. I will share any issues that arise and keep an eye on the logs. Hope I don’t have to change my voting poll or this thing will be returned asap, glta.

i7/16GB/1TB/Vega 20/15”/Mojave 10.14.2
 
unglued said:
I’m part of the “No and Never Did” but it’s only been 3 weeks. One issue I have is the battery percentage, there’s roughly a 5% difference at the logon screen compared to after logged-on, someone said FileVault is the cause and disabling it is a temporary fix, a cosmetic issue.

I still have FileVault encryption enabled, it sleeps/wakes alot, and one cable connected to a CalDigit TS3 Plus dock for charging, using an external monitor (dp-to-dp/native 1920x1080), external SSD/Time Machine, USB scanner, USB cooling pad, 3.5mm audio to soundbar, and hardwired network and it’s undocked time to time. Also using a bluetooth keyboard and mouse. I did wipe the internal SSD clean, checked for errors, and installed 10.14.2 the first day I received it but probably nothing related to the KP issues. I will share any issues that arise and keep an eye on the logs. Hope I don’t have to change my voting poll or this thing will be returned asap, glta.

i7/16GB/1TB/Vega 20/15”/Mojave 10.14.2
Click to expand...
what CPU frequency and what OS did it ship with out of curiosity.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back