I'm lucky to have to crashes, but after the update fans are always at the maximum speed while CPU temperature is around 45C and stable. Installed a Macs Fan Control and now it's back quiet with the same temperature (45C) during normal web browsing and fans at the minimal speed back again. Although if I disable the control it gets back to the maximum. Did try to reset SMC both ways described on official site.
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
Hello everyone,
I own new MacMini i7 2018, bought in February. It is really nice (but pricey) piece of hardware. Unfortunately, I experience BridgeOS "userspace panic: remoted connection watchdog expired" almost from very beginning. Actually I believe that it started to occur when I have started leaving more devices plugged when Mac mini goes asleep. Right now I have 4K LG display via USB-C->DisplayPort, USB-C hub for printer and external MIDI keyboard and USB-C -> NVMe for external Photos SSD. I started with only 4K monitor plugged via HDMI, but due to 4:2:2 I swapped to USB->C, then later I bought USB-C hub and USB-C->NVMe.
I am sending my crash reports to Apple under rdar://48136887
The problem is that Apple constantly asks me to generate kernel core dumps, which require both 2nd Mac and Ethernet connection. I do have (staingated) MBP 2013 and Ethernet switch somewhere in the drawer, but I normally use WiFi only. And it is really cumbersome to power MacBook plug it to Ethernet every time I need to wake my Mac Mini - just in case it crashes and I can catch kernel core dump.
I asked them if there is another way to grab core dumps without 2nd Mac and/or Ethernet, but they simply keep responding with same PDF instructions. Probably not speaking with real person at all there at https://bugreport.apple.com/web/?problemID=48136887
I own several iPhones, some old Macs, etc. but recently my Apple experience is mixed-bag.
I own new MacMini i7 2018, bought in February. It is really nice (but pricey) piece of hardware. Unfortunately, I experience BridgeOS "userspace panic: remoted connection watchdog expired" almost from very beginning. Actually I believe that it started to occur when I have started leaving more devices plugged when Mac mini goes asleep. Right now I have 4K LG display via USB-C->DisplayPort, USB-C hub for printer and external MIDI keyboard and USB-C -> NVMe for external Photos SSD. I started with only 4K monitor plugged via HDMI, but due to 4:2:2 I swapped to USB->C, then later I bought USB-C hub and USB-C->NVMe.
I am sending my crash reports to Apple under rdar://48136887
The problem is that Apple constantly asks me to generate kernel core dumps, which require both 2nd Mac and Ethernet connection. I do have (staingated) MBP 2013 and Ethernet switch somewhere in the drawer, but I normally use WiFi only. And it is really cumbersome to power MacBook plug it to Ethernet every time I need to wake my Mac Mini - just in case it crashes and I can catch kernel core dump.
I asked them if there is another way to grab core dumps without 2nd Mac and/or Ethernet, but they simply keep responding with same PDF instructions. Probably not speaking with real person at all there at https://bugreport.apple.com/web/?problemID=48136887
I own several iPhones, some old Macs, etc. but recently my Apple experience is mixed-bag.
- They refused to replace my Staingated MBP screen because it was too old, despite stains were there for almost 3 yrs, I got no recall information directly from Apple and I was not that much bothered until they became much bigger recently and the I have learned that I am no longer eligible, and I would need to pay $600 for something that is obvious manufacturing flaw. Btw. I was relocating so for last 2yrs I had no time to follow Apple news.
- When trying to watch 4K videos and Photos via iTunes Home Sharing and Apple TV 4K, iTunes keeps crashing in random moments. So it is simply not possible to see single day album without experience numerous crashes and reloads of library on Apple TV.
- iTunes Homes Sharing does not play H.265/HEVC 4K videos recorded with iPhone XR, despite all devices (iPhone, Mac, Apple TV) have H.265 hardware support. So Apple TV is only capable on the paper.
- My Samsung MDF no longer scans in Color in Mojave - known but unfixed problem reported in many places. I had to find a workaround and find some Samsung/HP software that does it instead.
Last edited:
Ok, it actually does crash in addition to the fans working on the max speed. Managed to get logs:
{"caused_by":"unknown","macos_version":"Mac OS X 10.14.4 (18E226)","os_version":"Bridge OS 3.4 (16P4507)","macos_system_state":"running","incident_id":"0C77937B-AD84-4E4A-B719-B54F9C495730","timestamp":"2019-03-31 07:31:48.58 +0000","bug_type":"210"}
{
"build" : "Bridge OS 3.4 (16P4507)",
"product" : "iBridge2,3",
"kernel" : "Darwin Kernel Version 18.5.0: Mon Mar 11 20:29:36 PDT 2019; root:xnu-4903.251.3~1\/RELEASE_ARM64_T8010",
"incident" : "0C77937B-AD84-4E4A-B719-B54F9C495730",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2019-03-31 07:31:48.55 +0000",
"panicString" : "panic(cpu 1 caller 0xfffffff026080d64): ANS2 Recoverable Panic - assert failed: [12075], src\/platform\/marin\/soc\/t8012\/apcie\/apcie.c:333:timed out waiting for topology from SMC - power(14)\n assert failed: [12075], src\/platform\/marin\/soc\/t8012\/apcie\/apcie.c:333:timed out waiting for topology from SMC\nRTKit: RTKit_iOS-973.250.56.release - Client: t8012.release-AppleStorageProcessorANS2-177.250.49~42~177.250.49~42\n!UUID: 0eca96bb-7ca8-3a74-b008-14d8b36b800d\nTime: 0x000000000e5da15f\n\nFaulting task 0 Call Stack:
{"caused_by":"unknown","macos_version":"Mac OS X 10.14.4 (18E226)","os_version":"Bridge OS 3.4 (16P4507)","macos_system_state":"running","incident_id":"0C77937B-AD84-4E4A-B719-B54F9C495730","timestamp":"2019-03-31 07:31:48.58 +0000","bug_type":"210"}
{
"build" : "Bridge OS 3.4 (16P4507)",
"product" : "iBridge2,3",
"kernel" : "Darwin Kernel Version 18.5.0: Mon Mar 11 20:29:36 PDT 2019; root:xnu-4903.251.3~1\/RELEASE_ARM64_T8010",
"incident" : "0C77937B-AD84-4E4A-B719-B54F9C495730",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2019-03-31 07:31:48.55 +0000",
"panicString" : "panic(cpu 1 caller 0xfffffff026080d64): ANS2 Recoverable Panic - assert failed: [12075], src\/platform\/marin\/soc\/t8012\/apcie\/apcie.c:333:timed out waiting for topology from SMC - power(14)\n assert failed: [12075], src\/platform\/marin\/soc\/t8012\/apcie\/apcie.c:333:timed out waiting for topology from SMC\nRTKit: RTKit_iOS-973.250.56.release - Client: t8012.release-AppleStorageProcessorANS2-177.250.49~42~177.250.49~42\n!UUID: 0eca96bb-7ca8-3a74-b008-14d8b36b800d\nTime: 0x000000000e5da15f\n\nFaulting task 0 Call Stack:
Well it seems since the 10.14.4 update I now get bridge OS kernel panics every few days. When I had none for 4wks of ownership since new on 10.14.3, I think I had a system uptime of 20+ days running.
I just restored my 2018 15 Pro Vega 20 via time machine backup, to my March 25th backup with 10.14.3, but the T2 firmware is still 16P4507, how can I get it back to 16P3133 ?
I just restored my 2018 15 Pro Vega 20 via time machine backup, to my March 25th backup with 10.14.3, but the T2 firmware is still 16P4507, how can I get it back to 16P3133 ?
I do not believe that there is any way you can roll back the T2 firmware. Your only option other than living with that one for a while is likely going to be to update to 14.14.5 which has Firmware Version: 16P55095c
Hmmm, interesting that they are still working on T2 and Bridge OS in the .5 release, from what I can see (via people old crash logs pin forums), nothing changed from 10.14.0 to 10.14.3, same t2 firmware and Bridge OS version. I also tried running the 10.14.3 combo updater, no luck. might stick with .3 and see if any more pop up.
It changed in every 14.14.4 beta I ran all the way to the release version and then again in 14.14.5. I had issues through 14.14.4 with restarts and random shutdowns. I haven't had any similar issues with 14.14.5 yet
10.14.5 is still crashing for me
Bummer
I haven't had a crash yet, but that doesn't mean much other than I haven't had one yet
Wish we could get some of the news sites to pick up on this issue, i've submitted to a few but nothing ever comes of it.
I wish we could get consumer reports to pick up on it as well and issue a "do not recommend" as they did with the Microsoft Surface Devices a couple of years back. It got MS's attention, I wonder if it would also get Apples. I have written to Consumer Reports about it, but they give me the "the ratings are based on reviews from owners." So either enough aren't having the issue or enough are contacting Consumer Reports about them.
This would be really nice and, i guess, the only chance to get apple to make some statement about this issue. I already tried to convince a german news site to report about it when the new MacMini was released showing same T2 connected kernel panics. They were not averse to report about it. I could give it a new try.
I bought my MBP in Nov18 and the KPs have occurred since the first day. Unfortunately i cannot afford to hand in my MBP for days, as i am writing a thesis. I'm totally pissed off and i am looking forward to the day, when i visit the genius bar....
My 2017 iMac PRO *NEVER* crashed until updating to 10.14.4. Now I'm crashing 3-5 times per day. Every crash is the same -
{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.4 (18E226)","os_version":"Bridge OS 3.4 (16P4507)","macos_system_state":"sleep","incident_id":"28088CBC-1927-40A8-A81E-B471AA4B357B","timestamp":"2019-04-05 13:11:57.28 +0000","bug_type":"210"}
{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.4 (18E226)","os_version":"Bridge OS 3.4 (16P4507)","macos_system_state":"sleep","incident_id":"28088CBC-1927-40A8-A81E-B471AA4B357B","timestamp":"2019-04-05 13:11:57.28 +0000","bug_type":"210"}
Update: went to beta to see if it addressed issue: 10.14.5 Beta (18F96h)
It didn't - already crashed twice so far.
{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.5 (18F96h)","os_version":"Bridge OS 3.5 (16P55095c)","macos_system_state":"running","incident_id":"533FB55E-9BD1-46B5-A665-207C6C40163F","timestamp":"2019-04-05 14:31:37.07 +0000","bug_type":"210"}
I read it might be IO related - so I shut Time Machine off to see if that helps. I will report back if it does.
Followup #2 Time Machine didn't help although frequency of error is down. Now only 2-3 times per day. I am upgrading to 10.14.5 Beta 2 to see if that helps (just released)
Followup #3:
10.14.5 Beta 2 did not help either. It's gotten worse now. Only way to power it up is to unplug for 30+ seconds and then hit power button. Crashes randomly. I've tried turning off all secure boot options from recovery and rand disk repair (no issues found). Brining in to apple service.
{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.5 (18F108f)","os_version":"Bridge OS 3.5 (16P55107b)","macos_system_state":"running","incident_id":"D34B7254-2A79-4D31-B3DF-FCF8A22112A6","timestamp":"2019-04-14 01:13:52.39 +0000","bug_type":"210"}
Followup #4:
I took my mac to Apple. I told them the issue. The insisted their diagnostics (which are more advanced than hardware test they claim) coupled with their known-how will fix it. They called back after a few days and said they couldn't reproduce the error.. and insisted that wiping the machine would solve it. I begged them not to, stating I had bootcamp and a ton of time setting things up I didn't want to loose.. but they insisted it was the only way - refusing to try booting from external drive for their testing. *sigh* So I said go ahead and got my mac back after a few more days.
Guess what? No solve. Here it is AGAIN crashing with the SAME issue. I mean, it's bridgeOS... it's not my userspace software. Anyway. Here is error.
{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.4 (18E227)","os_version":"Bridge OS 3.5 (16P55107b)","macos_system_state":"running","incident_id" ...
As you can see, they downgraded me from beta. My iMac is now crashing hard 7+ times a day in all states.. watching a video, while idle / on login screen, while typing in terminal, you name it.. So frustrating.
Followup #5:
So my hopes that OS 10.14.5 official release would clean things up are dashed. It's still crashing. While I use it, or even in the middle of the night by itself. I've escalated with apple support demanding hardware replacement. They had me run a software audit and I also submitted some of my kernel panics. *crosses finger* hope they fix this soon.
{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.5 (18F132)","os_version":"Bridge OS 3.5 (16P5125)","macos_system_state":"running","incident_id":"DEAE6542-134F-4BB7-BA51-887C6882A67B","timestamp":"2019-05-16 01:33:22.80 +0000","bug_type":"210"}
It didn't - already crashed twice so far.
{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.5 (18F96h)","os_version":"Bridge OS 3.5 (16P55095c)","macos_system_state":"running","incident_id":"533FB55E-9BD1-46B5-A665-207C6C40163F","timestamp":"2019-04-05 14:31:37.07 +0000","bug_type":"210"}
I read it might be IO related - so I shut Time Machine off to see if that helps. I will report back if it does.
Followup #2 Time Machine didn't help although frequency of error is down. Now only 2-3 times per day. I am upgrading to 10.14.5 Beta 2 to see if that helps (just released)
Followup #3:
10.14.5 Beta 2 did not help either. It's gotten worse now. Only way to power it up is to unplug for 30+ seconds and then hit power button. Crashes randomly. I've tried turning off all secure boot options from recovery and rand disk repair (no issues found). Brining in to apple service.
{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.5 (18F108f)","os_version":"Bridge OS 3.5 (16P55107b)","macos_system_state":"running","incident_id":"D34B7254-2A79-4D31-B3DF-FCF8A22112A6","timestamp":"2019-04-14 01:13:52.39 +0000","bug_type":"210"}
Followup #4:
I took my mac to Apple. I told them the issue. The insisted their diagnostics (which are more advanced than hardware test they claim) coupled with their known-how will fix it. They called back after a few days and said they couldn't reproduce the error.. and insisted that wiping the machine would solve it. I begged them not to, stating I had bootcamp and a ton of time setting things up I didn't want to loose.. but they insisted it was the only way - refusing to try booting from external drive for their testing. *sigh* So I said go ahead and got my mac back after a few more days.
Guess what? No solve. Here it is AGAIN crashing with the SAME issue. I mean, it's bridgeOS... it's not my userspace software. Anyway. Here is error.
{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.4 (18E227)","os_version":"Bridge OS 3.5 (16P55107b)","macos_system_state":"running","incident_id" ...
As you can see, they downgraded me from beta. My iMac is now crashing hard 7+ times a day in all states.. watching a video, while idle / on login screen, while typing in terminal, you name it.. So frustrating.
Followup #5:
So my hopes that OS 10.14.5 official release would clean things up are dashed. It's still crashing. While I use it, or even in the middle of the night by itself. I've escalated with apple support demanding hardware replacement. They had me run a software audit and I also submitted some of my kernel panics. *crosses finger* hope they fix this soon.
{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.5 (18F132)","os_version":"Bridge OS 3.5 (16P5125)","macos_system_state":"running","incident_id":"DEAE6542-134F-4BB7-BA51-887C6882A67B","timestamp":"2019-05-16 01:33:22.80 +0000","bug_type":"210"}
Last edited:
10.14.4 GA here with a 2018 MBP 15" and I'm getting this probably once a week. Once during a webcast where everyone thought I fell off the earth in the middle of my preso... What is the official Apple response here? I'm about to find out myself...
Personal experience and an interesting outcome:
I have two 2018 MacBook Pro 15" (i9/ Vega 20 / 32 GB / 1TB). One is currently getting repaired due to a faulty logic board (ate **** and died). This story is related to the second one that I am currently using.
I had a relatively stable system on 10.14.3. No major issues or crashes that I can recall.
I updated it to 10.14.4 a few days ago and it started experiencing kernel panics related to BridgeOS multiple times per day. I went into recovery mode, wiped the drive, and reinstalled 10.14.4. The kernel panics continued.
Tried internet recovery wipe and restore. Panics kept occurring. Tried to wipe and restore a couple more times and every install continued to have multiple kernel panics (one every five to ten minutes). After getting tired of the amount of time being wasted doing internet restores, I downloaded the DMG and created a bootable USB to keep trying different methods of getting it to work.
Eventually, I started running into an issue where the system would not allow me to use TouchID, add fingerprints, or set up Apple Pay (even on a fresh install) either during initial setup or through system preferences. It told me that I had to remove fingerprints before I could add any...even though there were no fingerprints on the installation. I was perplexed.
I booted back into recovery with the bootable DMG and nuked the drive again before going into terminal and using the "xartutil --erase-all" command to wipe the Secure Enclave. I then reinstalled a fresh copy of 10.14.4 onto the hard drive.
Since then I have not had a single kernel panic (knocking on wood) and the TouchID / Apple Pay functionality has been restored. I'm not advocating that anyone try this unless they are at their wits end, have a generally unusable or unstable computer, and they have no other recourse. I'm not sure why this would have had any difference in respect to the BridgeOS crashes (maybe a corrupt file or the way that it interacts with different OS versions?), but it has returned my sanity for now.
WARNING: DO NOT USE the "xartutil --erase-all" command unless you are OK with wiping your hard drive and reinstalling a new copy of the OS. Doing so will wipe the Secure Enclave, including decryption keys that you need to access the data on your hard drive. If you choose to ignore my advice...well...don't yell at me. Also of note, make sure that you boot into recovery and disable all of your Secure Boot settings if you plan on using an external media device to boot into recovery. If you don't...well...you're going to have a bad time.
I have two 2018 MacBook Pro 15" (i9/ Vega 20 / 32 GB / 1TB). One is currently getting repaired due to a faulty logic board (ate **** and died). This story is related to the second one that I am currently using.
I had a relatively stable system on 10.14.3. No major issues or crashes that I can recall.
I updated it to 10.14.4 a few days ago and it started experiencing kernel panics related to BridgeOS multiple times per day. I went into recovery mode, wiped the drive, and reinstalled 10.14.4. The kernel panics continued.
Tried internet recovery wipe and restore. Panics kept occurring. Tried to wipe and restore a couple more times and every install continued to have multiple kernel panics (one every five to ten minutes). After getting tired of the amount of time being wasted doing internet restores, I downloaded the DMG and created a bootable USB to keep trying different methods of getting it to work.
Eventually, I started running into an issue where the system would not allow me to use TouchID, add fingerprints, or set up Apple Pay (even on a fresh install) either during initial setup or through system preferences. It told me that I had to remove fingerprints before I could add any...even though there were no fingerprints on the installation. I was perplexed.
I booted back into recovery with the bootable DMG and nuked the drive again before going into terminal and using the "xartutil --erase-all" command to wipe the Secure Enclave. I then reinstalled a fresh copy of 10.14.4 onto the hard drive.
Since then I have not had a single kernel panic (knocking on wood) and the TouchID / Apple Pay functionality has been restored. I'm not advocating that anyone try this unless they are at their wits end, have a generally unusable or unstable computer, and they have no other recourse. I'm not sure why this would have had any difference in respect to the BridgeOS crashes (maybe a corrupt file or the way that it interacts with different OS versions?), but it has returned my sanity for now.
WARNING: DO NOT USE the "xartutil --erase-all" command unless you are OK with wiping your hard drive and reinstalling a new copy of the OS. Doing so will wipe the Secure Enclave, including decryption keys that you need to access the data on your hard drive. If you choose to ignore my advice...well...don't yell at me. Also of note, make sure that you boot into recovery and disable all of your Secure Boot settings if you plan on using an external media device to boot into recovery. If you don't...well...you're going to have a bad time.
Last edited:
Time since boot: 8 days 11:03
Good times after rollback to 10.14.3 last week ✌️
[doublepost=1554937126][/doublepost]wow, less than one minute later while I was just typing on my phone. no peripherals attached. only safari open and charger connected. why is my screen black.... hmmm oh;
{"caused_by":"macos","macos_version":"Mac OS X 10.14.3 (18D109)","os_version":"Bridge OS 3.4 (16P4507)","macos_system_state":"running","incident_id":"32A3E907-347A-4500-BEF2-6AB1F4D1BED1","timestamp":"2019-04-10 22:55:56.43 +0000","bug_type":"210"}
Man this thing is so hard to work out. so it panicked at around 8:55-57am on today the 11th of April (Australia), but the timestamp above was for last night after sleeping the device. Somehow I was able to plug into power, open this page in safari and type a message before it rebooted...
Good times after rollback to 10.14.3 last week ✌️
[doublepost=1554937126][/doublepost]wow, less than one minute later while I was just typing on my phone. no peripherals attached. only safari open and charger connected. why is my screen black.... hmmm oh;
{"caused_by":"macos","macos_version":"Mac OS X 10.14.3 (18D109)","os_version":"Bridge OS 3.4 (16P4507)","macos_system_state":"running","incident_id":"32A3E907-347A-4500-BEF2-6AB1F4D1BED1","timestamp":"2019-04-10 22:55:56.43 +0000","bug_type":"210"}
Man this thing is so hard to work out. so it panicked at around 8:55-57am on today the 11th of April (Australia), but the timestamp above was for last night after sleeping the device. Somehow I was able to plug into power, open this page in safari and type a message before it rebooted...
Last edited: