BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

Are you having the problem before and after the supplemental update for MBP 2018?

Last night, before going to bed, I intentionally set the environment similar to when I had my BridgeOS panic:

MBP 2018 is connected to MBP 2015 through thunderbolt 3->2 adapter and cable.

Belkin USB C Express dock connected.

Other peripherals like ethernet, printer, scanner are connected through the dock.

Well, it didn't crash or auto rebooted. The difference I can think of is the supplemental update although it could be more. Will be watching closely...

By the way, the panic log says "bug_type":"210" for everyone reported so far.

Incidentally, got to know this command. And would it be the reason?

$ macerror -210

Mac OS error -210 (buffersTooSmall): can not operate in the memory allowed

I have just received my replacement laptop and the problem still persists. I would say this is a software problem rather than the hardware fault they originally diagnosed.

I set it up initially without migrating any data and it still crashed.

I have tried turning off power nap and it still crashed.

I have been on the line to apple support and sent them diagnostic info.

I do use Parallels, but since working on this issue, I leave it turned off unless I am actively using a VM. So, all of my crashes have been with Parallels not running. Generally, if I am actively working, it doesn't seem to matter what is connected and what software I am using. Sleep brings on the behavior. At least for me.

The only other issue I've found has been that my system now hates to back up to external hard drives. Either TM or Acronis. In mid backup it looses the drive or has a drive error. Cautiously, I would say that I am OK if I direct connect the drive to a native port on the machine rather than through a hub. That has now worked a couple of times. I'll continue to test that aspect. It could be my hub, or Acronis or something else. What stands out to me is that I literally picked up my MBP 2016 and dropped the 2018 in it's place with the same wires and devices connected to the same ports. Now I have the sleep issue, am having trouble with my two external drives working reliably and of course Bootcamp isn't ready yet. I am on my 3rd cycle of formatting and starting again with a fresh initial backup. I trust all of this will get better and hopefully an OS update will come soon.

I have experienced the same crash with only the power adapter connected while in sleep mode.

I also see the following errors in Disk Utility > First Aid

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

These are the same errors that many other with the same kernel panic have noticed.

Just a quick follow up on my call with Apple Support today.

They only asked me if I was running the latest macOS (10.13.6). It is a bit odd thing to ask because the macOS 10.13.6 that comes with MacBook Pro 2018 is newer than the one available in App Store. App Store does not allow me to download macOS High Sierra installer from App Store). Perhaps the Apple Support meant to ask if I installed the macOS High Sierra 10.13.6 Supplemental Update for MacBook Pro 2018.

Anyway, I'm supposed to call them with the case number and ask to speak to senior advisor when the Bridge OS crash again.

And it did crash again.

• Left it idle this morning, with screen saver activated and lid opened.
• Came back from work, pressed space bar
• Could see the power turn on the screen (while remaining black)
• Touch bar prompting for my fingerprint
• Touched it, touch bar changed to normal logged-in buttons, but none responded to touch (e.g. sound)
• Waited 2-3 minutes
• It rebooted on its own
• Same dump as mentionner (BridgeOS, state running, bug type 210)

No software installed, just a clean erased disk and brand new OS install.

I normally work with mine closed sitting in a stand on edge. I may go 3 or 4 weeks or longer without ever seeing the built in display or touch bar. I don’t normally shut down or reboot unless something makes me. So for my recent stretch of good luck, the lid has been closed and I exclusively used external monitors and keyboard. I sleep the monitor by dragging to a hot corner at the end of the day and click the external trackpad to wake up in the morning. I would also say, when support asked me to disconnect and test, I had no resets in 3 days during which I left it ajar 1 time and closed twice (?) or the other way around. Not sure now but I tried both with no resets.

Here's my experience.

My 13” was rock solid for 16 days and on the 16th it had the Bridge OS kernel panic while sleeping. I’d been doing the same things I’d been doing for the previous 2 weeks. Anyway, I talked to Apple and have a replacement coming on the 23rd. Today is day 22 with the original and I’ve not had another restart since that one on day 16. It’s hard to know what caused it. I’m using the same software and it’s connected to the same LG 4K monitor. Here's part of the error (that can be found in System Report > ProxiedDevice-Bridge in the Console app):

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-08-10 15:20:44.84 +0000","incident_id":"..."}

I had the crypto_val messages in Disk Utility when I first got the MacBook so I reinstalled macOS and that cleared it up. I don't believe they're related to the Bridge OS issues.

Good to know that you are also running into SMC being one of the culprits! The idle thread call could be a red herring. But more reports from other users will hopefully confirm one way or the other.

I am currently testing my default setup with all checkboxes enabled in the "Power Adapter" tab and all except Power Nap is checked in the "Battery" tab. And I have automatic graphics switching enabled.

For the first time in almost a month of use, I hit the Bridge OS crash again. I had it a couple times when I first received the MacBook Pro (15" i9, 16GB, 1TB), but disabled Power Nap and then wasn't able to get it to crash even after re-enabling it. But as if on cue, it crashed on me this morning as I was checking a few things before beginning the process of migrating everything off of it onto the new MBP Apple just sent me to replace the crashing first one. I sent the crashing report and the System Diagnostics file to Violet, my AppleCare rep.

What I found interesting was that right out of the box, the replacement MBP had the "crypto_val" errors when running Disk Utility. So I booted into Recovery Mode, erased the hard drive, then did a fresh install of High Sierra, setting up a "test" account. Disk Utility reported no "crypto_val" errors after that. So then I used Migration Assistant (ugh! I didn't have a Thunderbolt 3 cable so used Wi-Fi to transfer between the two...first time I'd ever done it that way. Took 6 hours!) to transfer my account off the original MBP onto the new one. First thing I did after the transfer was run Disk Utility. Thankfully, no "crypto_val" errors again, so I'm feeling like 1 problem down (though I suspect those were never really all that serious to begin with). That said, based on everyone else's reports, I don't feel like I'm out of the woods. I'm sure it's only a matter of time before I encounter a Bridge OS error. Nevertheless, I intend to turn Power Nap off and cross my fingers.

Mine occurs like clockwork. Friday alone it crashed 8 times.

Yesterday, about 5 times.

I’ve got it narrowed down to when my computer sleeps. I’ve disabled power nap as some people recommend but it still crashes

Yep. Same issue. Chatted with Apple Support and reported the issue. First two paragraphs of my error are as follows (see very bottom). This issue always occurs when waking from sleep and with these parameters:

• Reinstalled High Sierra 10.13.6 AFTER supplemental update was available
• Did not restore with time machine or migration assistant
• Issue always occurs when plugged into power
• Power nap was always disabled before/after reinstall of OS. (Never liked it and feel it's still buggy)
• Crash occurs with or without Wake for Wifi Network access enabled
• Have iStat Menus, Jumpcut, Magnet, Carbon Copy Cleaner, and Time Machine, Backup and Sync from Google, and iTunes Helper running in the background.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-08-21 21:28:09.99 +0000","incident_id":"31753AFF-243A-4D95-8296-89CA7E34DF7F"}

{

"build" : "Bridge OS 2.4.1 (15P6703)",

"product" : "iBridge2,3",

"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",

"incident" : "31753AFF-243A-4D95-8296-89CA7E34DF7F",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-08-21 21:28:09.92 +0000",

Your use of a storage device strikes a chord with me and my situation.

Generally, people's reports of problem causes are very diverse. No one thing seems to really emerge except that for the most part, it is good if you don't plug any devices in, though not a fix. I wonder if, overall, this is just a lack of robustness in BridgeOS software/firmware. This is after all, a part of the OS which needs to be extremely robust. But, how many machines have their been in the world with the T2 chip until now? Testing, particularly in the wild, could only be considered limited when compared to the other parts of the OS in the rest of the Mac universe. Some parts of the OS are probably over a decade old. This feels like a set of problems rather than one error somewhere. When you watch a good YouTube video or find a good article about the T2, the T2 is assuming a lot of important functions related to storage and other things. There is a brand new chunk of OS there that hasn't had much runtime in the wild yet compared to the rest of the OS.

Strangely, I haven't had a restart in 10 days. Yet, I am having crazy storage problems with Acronis True Image. It worked fine day in and day out with my MBP 2016. Now I can only get a successful backup half the time. The external drive has been corrupted. I have formatted several times. Acronis spews error logs like crazy. Acronis 2019 was just released and it is the same. It has a feature where the external drive is formatted as bootable for easier recovery, yet after 6 fresh format attempts, it can not make the drive. I moved that target drive over to my Mac mini and it worked immediately on the first time. I am not panicked (no pun) because I use Acronis specifically to back up my Bootcamp partition which isn't available yet. So, TimeMachine is enough for now.

As I said, reading your issue about the USB flash issues reminds me of my own experience, though not with restarts any more. Simply that my use of the external drive has been extremely unreliable since day one. Maybe it is 100% an Acronis issue, but there is definitely something severe going on there, related only to my T2 Mac and T2 has storage responsibilities. But I feel like there have been a few reports of people having storage issues.

Just saw an 'Supplemental Update 2' for MacBook Pro 2018 with Touch Bar hit the App Store. Not much info on what it does, but hopefully it addresses the crashes we've been seeing.

Anyone have an idea how to see the BridgeOS version?

Philip