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
That's interesting ! My KP was just when I was plugging in external drives while the laptop just getting out of sleep by opening the lid.
AFAIK none have tested this option. But considering the quote above, it could make sense. I managed to "create" a KP by unplugging an external drive BUT in this case, I booted from it and was running macOS from it too. But it wasn't working as expected because of the new security thing (disk encrypted, had to allow to boot from external drive in Startup Security Utility and after the boot, the OS wasn't allowing a lot of apps to launch properly... anyway, I managed to get what I needed from it). When I tried to reboot, it took a bit long and I wasn't patient anymore so I just unplugged the drive which created a KP, but I would say this one was kind of logic
I am pretty sure I let it as it was, and it was PAFS Encrypted already from my first install.
Actually, you should have got a message at startup stating your computer had to restart. You may check the Console in :
/Library/Logs > DiagnosticReports > ProxiedDevice-Bridge > Retired (picture to help)
View attachment 774574
And still, you can go days or weeks without any KP depending on how you use your Mac. For example if you never leave it with screen or drives attached nor unlock It with your Watch, you are eliminating a lot of risk. Plus from my understanding, some KP were solved since 10.13.6 (hardware KP)
Hi!
I can get to /Library/Logs but then I don't seem to have the DiagnosticReports folder. Where else can I see logs of what happened?
EDIT: I had a typo in the path. I can get to Retired but folder is empty?
Then you most likely haven't had any KP. Nothing yet on my exchanged base 15" model either. Crossing my fingers.
Code:
{"caused_by":"bridgeos","macos_system_state":"shutdown","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-08-06 10:59:17.03 +0000","incident_id":"E0F1F9AC-4313-455E-B9EF-B10118AF8EB6"}
{
"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" : "E0F1F9AC-4313-455E-B9EF-B10118AF8EB6",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2018-08-06 10:59:16.22 +0000"
"panicString" : "panic(cpu 1 caller 0xfffffff015b4a81c): ANS2 Recoverable Panic - assert failed: [11184], src\/aspcore\/system\/seg.c:2393:HIX 10 timed out for segIdx 0x4bd in 8.1 seconds, comp FIFO count 0, bus=6, nandOp=0 - Timer(13)\n assert failed: [11184], src\/aspcore\/system\/seg.c:2393:HIX 10 timed out for segIdx 0x4bd in 8.1 seconds, comp FIFO count 0, bus=6, nandOp=0\nRTKit: RTKit_iOS-848.70.3.release - Client: t8012.release-AppleStorageProcessorANS2-177.77.70~4~177.77.70~4Again this morning. I may have to bite the bullet and do a clean install hoping it helps. If it's a hardware issue Apple will probably remain silent. Have they ever recalled anything? Hoping it's a software issue though.
Does this include the powerbrick?
Would be kinda annoying if that's the case.
lol it's annoying either way
In the past it's been my Henge Stone dock, which also provides power, but obviously it's a hub too.My totally wackadoo semi-solution attempt as of yesterday was reinstalling bettertouchtool, probably to make me feel like I was doing something, but my train of though was it's a kext that interacts with the touch bar and it was installed during a time machine restore so maybe it's better to install it fresh? I dunno but I am frustrated liek everyone in this thread
I’ll be using a Belkin Dock TB3 in a 2 weeks, will be able to do a comparison then.
Anyone who made a swap, was it possible because inside the 14 days or just because they couldn’t solve it after the 14 days? Just to know Apple is dealing with this.
I got one of the kernel panics today too:
I'm relatively confident this is related to the Henge Stone Dock. I've written into their support team and apparently it's a known issue that the dock causes problems with the new 2018 MacBook Pros. They've mentioned it on their website and are working on a fix with Apple: https://hengedocks.com/products/tethered-dock. Is anyone else who's experiencing this panic using one of these docks?
Code:
{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-08-06 04:37:21.11 +0000","incident_id":"C27403E4-00DC-44BB-88CB-EBA5C469A8F8"}I'm relatively confident this is related to the Henge Stone Dock. I've written into their support team and apparently it's a known issue that the dock causes problems with the new 2018 MacBook Pros. They've mentioned it on their website and are working on a fix with Apple: https://hengedocks.com/products/tethered-dock. Is anyone else who's experiencing this panic using one of these docks?
Also for anyone running into the crypto errors, I heard that it was an issue with the system image that Apple used on the new MacBooks. Reinstalling the OS cleared them for me.
I have problems with and without mine
I'm actually supposed to get mine back from them today for a firmware update that hopefully will help with display issues and hard drive disconnections with a hub (that their support said were common to all hubs, even apple's)
No bridgeOS KPs (yet), but I had the crypto_val errors, which made it impossible for me to back up to Time Machine. I did a CCC copy of the system drive, but foolishly skipped the recovery partition. My attempts to reinstall OS got me to the recovery loop ("the system needs to be reinstalled"), then the recovery partition somehow disappeared as well (!!!) and only the Internet Recovery finally fixed things. My Macintosh HD is, oddly, formatted as Mac OS Extended (Journaled) now – I did not do that – but it seems to work without problems, and crypto_val errors are gone.
This is very worrying though. This machine is supposed to last me at least three years...
This is very worrying though. This machine is supposed to last me at least three years...
Why couldn’t you do a timechine backup with the crypto-error? It doesn’t seem to affect anything though?
I have no idea. The backups kept failing (I don't remember the exact message), so I ran Disk Utility and it gave me the crypto-val errors. I googled, and found out this was an iMac Pro problem, which many people solved by clean reinstall, then restoring from backup. But I couldn't do a backup! Hence CCC. When I got into the recovery loop I was in quite a bit of panic, I like fiddling with computers, but not like that.
Yes, I understand it is frustrating... As another guy mentioned a few posts back - maybe you saw - the "henge stone" (lol?) dock is a known issue by now, which apparently is under investigation/pending a fix, but would you be willing to guinea pig using the original power brick instead of your dock? It would be appreciated!lol it's annoying either way
So, I can confirm that the Bridge OS crashes happen with just the power cord plugged in. It happened to me overnight. I put the computer to sleep with nothing but the cord attached and woke up to the Apple logo and message that my Mac restarted due to a problem. The logs show the same Bridge OS 2.4.1 bug type 210 crash.
Note that it took 6 days for this to happen. Previously, I had 5 crashes in the first 7 days of ownership. For those first 7 days, I kept my Thunderbolt 3->2 adapter plugged in during sleep.
[doublepost=1533583523][/doublepost]
I think the crashes happen more often when you have something connected (like a dock), but it still happens with only the power adapter plugged in.
Note that it took 6 days for this to happen. Previously, I had 5 crashes in the first 7 days of ownership. For those first 7 days, I kept my Thunderbolt 3->2 adapter plugged in during sleep.
[doublepost=1533583523][/doublepost]
I think the crashes happen more often when you have something connected (like a dock), but it still happens with only the power adapter plugged in.
Yes, I understand it is frustrating... As another guy mentioned a few posts back - maybe you saw - the "henge stone" (lol?) dock is a known issue by now, which apparently is under investigation/pending a fix, but would you be willing to guinea pig using the original power brick instead of your dock? It would be appreciated!
Not sure what you mean by this, but I've had the crash, like many others documented here, with nothing or anything plugged in, including the regular power adapter.
You said you could make your mac crash reliably by unplugging devices as it sleeps, and mentioned your docking stone thing - which would be the known issue with that device - but does the crashing extend to unplugging other devices too, such as the power brick? That's what I'm asking...
You said you could make your mac crash reliably by unplugging devices as it sleeps, and mentioned your docking stone thing - which would be the known issue with that device - but does the crashing extend to unplugging other devices too, such as the power brick? That's what I'm asking...
It was a bit of an overstatement, it's definitely more connected to sleep in general than anything plugged into the port. I've had it happen with nothing plugged in. It's hard to say because it requires long periods of sleep, at least for me. Of course I'll share any observations here.
I turned off sleep and after previously having it happen every night for 5 days, it didn’t happen on the 6th day. But then it just happened again on day 7. So I’m not sure sleep is the only factor.
I’m using the official Apple dongle with the following connected:
- Official Apple Power cable/charger (USB C)
- Monitor connected via HDMI
- External HDD connected via USB Type-A
I'm on a replacement unit, its been about 4 days and I haven't had crackling or BridgeOS crashes (knock on wood).
I've gotten the OS Bridge error on two machines. I'm on my second one. 2018 13" i7-16g-1TB config. On the second unit, I erased and reloaded OSX to get rid of the crypto errors. All my OS Bridge errors happened during sleep and while the computer was connected to a StarTech thunderbolt / usb C dock. Not sure if it makes a difference.