That is very unfortunate. When you say your network died, do you mean you lost your wifi? What is the network menu bar? I'm trying to follow the different kinds of ways this KP issue is manifesting for various people. My original MBP shut down the first day I used it, and the fans were on full blast even though the MBP was cool (almost cold) to the touch. There is a video on YT by a guy who frequently does Apple videos, and he reported this same problem with a shut down and fans on full blast. I had to do an SMC reset to get the fans to stop and the MBP to start back up. I just don't understand the whole network thing you're describing.
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.
December / MacOS 10.14.2 2018 Macbook Pro "Bridge OS" Kernel Panic Poll
- Thread starter RumorConsumer
- Start date
- Sort by reaction score
Menu bar = the area to the right of the menus on the top of the screen. Clicking on the Wifi icon make the cursor spin while over it, wifi is dead (haven't tried it connected with ethernet cable), ping's don't work, wifi/network is dead.
The two scenarios I have encountered are this (as described in my post) and opening my laptop in the morning to the laptop having been rebooted and a Crash Report when I log in.
I have experienced the problem with opening my original MBP in the morning and finding a crash report. I think that particular thing happened only once. But there were also times when I'd open my MBP and it would start up, which must mean, I believe, that it had shut down all on its own due to a KP, I presume.
So this has been an on/off thing for me since getting one at launch. I got it specifically to test Mojave betas (until switching to it after GM). Right away had problems with the T2, until nearly the last beta. Then at GM back to problems. Finally restored the T2 firmware and problems went away. Was fine on 10.14.2 betas, but when GM released for 10.14.2, I reinstalled Mojave from scratch and then upgraded to 10.14.2, and now back to problems. Tried restoring the firmware again, but this time it doesn’t seem to have made a difference.
I’m not sure why things go back and forth from working to not, and I wish I could pin something specific down other than the firmware version mattering a *lot*. It would be nice if Apple would let us pick the firmware version to choose to restore if things are going to be buggy.
I’m not sure why things go back and forth from working to not, and I wish I could pin something specific down other than the firmware version mattering a *lot*. It would be nice if Apple would let us pick the firmware version to choose to restore if things are going to be buggy.
For them to do that would be tacit acknowledgement that their firmware versions aren't working right, and of the existence of a problem to begin with. I don't think that is something Apple would ever do.
Thank you for this post. A few questions, though, if you don't mind:
(1) What is "GM"?
(2) When you are seeing problems, what are you seeing? KPs with error message pop-ups? Random shutdowns? Any problems with peripherals?
(3) Regardless of whether you get a pop-up warning message, can you tell if a KP has occurred by looking in Console under System Reports>ProxiedDevice-Bridge? Will they show up there?
(4) Why would you go to the expense of buying a MBP just to test betas? That seems like a huge expense. I'm thinking maybe that that kind of investment of time and money means you are someone who is particularly knowledgeable about these types of things?
GM means Gold Master, the official version to be released widely to users regardless they are beta users or not.
Unfortunately, I believe that most computer users are uninformed and will just attribute the problem as a typical annoying computer crash (i.e. they will say and do nothing about the issue).
@Plutonius - I think you're probably right, but I just don't understand how most people would think it typical. My other Macs basically just don't crash. They stay on 24/7. My Mac Pro only crashes sometimes in FCPX (when I do a who series of very minute trim/nudge edits). My iMac almost never crashed until I upgraded to High Sierra, and very, very rarely now. When my MBP crashes, I certainly notice it.
On a separate note, when the MBP crashes from a KP, should you see an error report in Console? How long do error reports stay visible in Console? Thanks
I suspect it would be more obvious to people with dedicated desktop computers that exhibit the problem. Laptops, by their portability and punctuated use (ie not as a home server, always online system). I could easily see people pop their laptop open in the morning, see the login screen and not think twice about having to log in, and then dismiss the innocuous looking Crash Report as some random panel that popped up. The systems isn't freaking out at them, no data's lost, and Facebook pops up just fine again so they move on with their day.
I'm with you, though, none of my other Mac's crash like this 2018 MBP does. I have a 2011 Mac Mini that's been chugging along since 2011 with reboots only when I run upgrades.
@jbg95 - Did you finish your thought in that second sentence? Were you going to say that laptops are more subject to problems even those without the T2 chip?
Do you know the answer to my Console question? I'm really trying to figure out if my replacement MBP shut itself down randomly. I ddidn't see a pop up crash window and I see nothing in Console. The problem is, even if it was a restart caused by the T2 chip, I don't if there would be a report in Console. And, if there would be, how long it would stay visible there. Thanks
Gotta love when the system crashes and shuts down while you're trying to reply to a forum post about the system crashing. It just happened again.
Yeah, I didn't finish my sentence, did I?
Got distracted by a call. Point was, laptop users (especially less frequent users, non-pros) probably don't notice the effects crashes as much as others. I notice when there are fingerprints and dust on the screen, or slight variations in heat when the CPU is working. A crash is very obvious to me (and I'm sure you all as well).Regarding logging the crashes, I haven't spent enough time to go track the logs down. I've been cut and pasting them out of the Crash Report into separate files. I'm sure they're in a log in Activity Monitor somewhere. My replacement laptop arrives tomorrow, I'm hoping to rapidly put this behind me and not have to delve into troubleshooting at a deeper level.
Regarding what to look for after the reboot, you're looking for a window to pop up:
Click on Report and you'll see the text.
Yep, as far as I can only the most recent panic file is stored, I don't see more than one *panic file (today's) in the folder.
Last edited:
For those that are crashing. Do you have the FileVault turned on? I haven't had a single crash, but I have FileVault turned off. I was recommended when I got my 2017 MBP to not use FileVault by a Apple Engineer unless I really needed encryption. If so, just use an external drive.
I didn't/don't use FileVault and was experiencing crashes/panics.
No issues with my Vega 20 either. No File Vault or secure boot. I use sleep though and have a caldigit ts3+ dock, with caldigit external storage, and dvd rom.
You are lucky. I just returned my second 2018 MBP Vega 20. Both had the T2/Bridge OS issues. Now I bought a new 2017 MBP that has the T1 chip. I just couldn't play musical MacBooks any longer. I would have loved to have had a working Vega 20.
Sorry man. Wish there was a simple fix for you. I know it's rough to not get a working machine especially after spending that kind of money on it.
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?