BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

You'll find the logs for these — at least for a little while — in /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge

Happens to me every few days. Contemplating returning this and trying an alternate, identical sample to see if it's perhaps hardware-related.

I am also finding a positive correlation with fewer resets and Power Nap being off.

I am able to switch between Mojave Beta and the latest High Sierra and I was getting multiple daily sleep crashes with Power Nap on no matter which OS I was booted into.

I turned Power Nap off and have now gone 24 hours without a sleep crash within High Sierra. Just installed the latest public Mojave beta into the partition I have for it and will boot into Mojave and see how stable things are there with Power Nap still disabled.

If things seem OK, I will go back to having Power Nap on and see how long it takes to get more frequent crashes.

Good to hear the T2 team is actively trying to fix.

I am waiting to hear how far along my replacement machine is from being delivered. My support specialist was supposed to have begun the process yesterday.

Huge thread about the issue here: 2018 MacBook Pros crashing with "Bridge OS" error | Page 44 | MacRumors Forums

Good video about "BridgeGate" here: The BIGGEST ISSUE with the MacBook Pro 2018! - YouTube

Hi everybody,

I have the same problem. My specs (custom order - arrived yesterday):

MBP 13 / 2.7GHz i7 / 16GB / 1TB

How to reproduce "error & reboot":

- Get USB type-C flash drive - mine was bought from Apple store https://www.apple.com/uk/shop/product/HLN92ZM/A/sandisk-64gb-ultra-dual-drive-us b-type-c?fnode=fdfa86997e21866c3157f86a3616d1d16ed7bc54dfcdb2a293df2462412e8b487 3efa966fa5e5bd9eb4889e739053cbbb1a552d4a62d3af2360fedba2d43af71ff0e736e16e94a894 5436af666e5a946922ca18a5b5db40327ff674fd76a6a20

- Get big enough file and put in on the flash drive - I use VMWare virtual machine file which is about 24GB

- Plug the flash drive into either of the two left side thunderbolt ports

- Copy the file to the Desktop

What will happen (or what does happen on mine mbp):

- Unplug the flash drive and the MacBook will reboot

- On power up there will be the "bridge os" auto report

This only happens with the thunderbolt ports on the left-hand side!!!

I can copy the file OK both ways if the flash drive is plugged into one of the two thunderbolt ports on right-hand side of the MacBook.

I have started seeing the issue while using my back-up flash drive (standard USB 3.0 Type-A) with Apple Type-C to USB adapter. The behaviour is the same for me, whether I use an old drive with the adapter or new type-C flash drive.

If this is a software/firmware issue, then its quite weird. I suspect some deeper issue, because of the different behaviour on the left and right side of the laptop. I will be returning mine and will go back to some older hardware until this is clearly resolved.

It is a big shame, I really love the form factor & power of the 13 inch MacBook Pro.

Good luck everyone...

Jan

crash again with macos mojave 10.14

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 3.0 (16P375)","timestamp":"2018-10-19 13:24:20.89 +0000","incident_id":"BF28627A-E9C3-4D1E-A03C-F1F6E9C52B7A"}

{

"build" : "Bridge OS 3.0 (16P375)",

"product" : "iBridge2,4",

"kernel" : "Darwin Kernel Version 18.0.0: Thu Sep 6 18:24:30 PDT 2018; root:xnu-4903.201.2~72\/RELEASE_ARM64_T8010",

"incident" : "BF28627A-E9C3-4D1E-A03C-F1F6E9C52B7A",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-10-19 13:24:20.69 +0000",

"panicString" : "panic(cpu 0 caller 0xfffffff0190e29f4): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 16P375\nKernel version: Darwin Kernel Version 18.0.0: Thu Sep 6 18:24:30 PDT 2018; root:xnu-4903.201.2~72\/RELEASE_ARM64_T8010\nKernelCache UUID: 834FD638CEB95664A35EB86DC49DF634\nKernel UUID: 4A1BD27F-3E02-3C61-8254-E173B853B18F\niBoot version: iBoot-4513.200.293\nsecure boot?: YES\nx86 EFI Boot State: 0xd\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x5\nx86 Previous Power Transitions: 0x405060400\nPCIeUp link state: 0x14\nPaniclog version: 11\nKernel slide: 0x0000000012a00000\nKernel text base: 0xfffffff019a04000\nEpoch Time: sec usec\n Boot : 0x5bc87c20 0x000c1dbb\n Sleep : 0x5bc8a96d 0x000a197d\n Wake : 0x5bc9ba8c 0x0009fdf9\n Calendar: 0x5bc9dae5 0x000c44ad\n\nPanicked task 0xffffffe0002b1680: 3224 pages, 208 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0005c9f20, backtrace: 0xffffffe016243530, tid: 381\n\t\t lr: 0xfffffff019c012ec fp: 0xffffffe016243670\n\t\t lr: 0xfffffff019add610 fp: 0xffffffe016243680\n\t\t lr: 0xfffffff019b11ce8 fp: 0xffffffe0162439f0\n\t\t lr: 0xfffffff019b12060 fp: 0xffffffe016243a30\n\t\t lr: 0xfffffff019b13c98 fp: 0xffffffe016243a50\n\t\t lr: 0xfffffff0190e29f4 fp: 0xffffffe016243ac0\n\t\t lr: 0xfffffff0190e4e7c fp: 0xffffffe016243b60\n\t\t lr: 0xfffffff0190e21c0 fp: 0xffffffe016243be0\n\t\t lr: 0xfffffff01909bab0 fp: 0xffffffe016243c10\n\t\t lr: 0xfffffff019f9c0fc fp: 0xffffffe016243c50\n\t\t lr: 0xfffffff019f9b964 fp: 0xffffffe016243c90\n\t\t lr: 0xfffffff019ae8614 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 105968 **\n",

"macOSPanicFlags" : "0x0",

"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",

"memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"pa geSize":16384,"memoryPressure":false,"memoryPages":{"active":8524,"throttled":0, "fileBacked":11792,"wired":5536,"purgeable":37,"inactive":5127,"free":7636,"spec ulative":3413}},

"processByPid" : {

"0" : {"timesThrottled":0,"pageIns":0,"waitInfo":["thread 445: kernel mutex 0xdd394b804d83b55b owned by thread 5053"],"timesDidThrottle":0,"procname":"kernel_task","copyOnWriteFaults":0,"thr eadById":{"372":{"continuation":[0,68842797344],"userTime":2.125e-06,"systemTime ":0,"id":372,"basePriority":81,"name":"AppleD2449PMU","user_usec":2,"schedPriori ty":81,"system_usec":0,"state":["TH_WAIT","TH_UNINT"],"waitEvent":[1,15940855370 478102611]},"445":

Some member stated that most KP's reported by BridgeOS as the T2 chip manages different things.

However, in most cases users report that the machine reboots instead of awakening and a KP pops up starting with:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 3.1 (16P1065)","timestamp":"2018-11-06 05:43:11.83 +0000","incident_id":"D66C632B-1EBC-471B-8696-6AC8377472DA"}

But what is about the rest of the report? In example some reports show:

1. "macOSPanicString" : "panic(cpu 0 caller 0xffffff7f976f3307): \"DSB0(MacBookPro15,2): thunderbolt power on failed 0xffffffff\n\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/IOPCIFamil y\/IOPCIFamily-330.200.11\/IOPCIBridge.cpp:1314\nBacktrace (CPU 0),
   
2. "macOSPanicString" : "panic(cpu 0 caller 0xffffff800fcc306f): UUID: 47D2BC26-0426-428C-A375-59C980C76CFE\nStackshot Reason: Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.driver.usb.AppleUSBXHCI. Thread 0x639c8.\
   
3. "macOSPanicString" : "panic(cpu 0 caller 0xffffff8006678792): \"Restart timed out in phase 'Quiescing PM'. Total 30000 ms:\nvfs_unmountall: 1214 ms\nif_down_all: 127 ms\nPowerOff\/Restart message to priority client: 362 ms @ 0x<ptr>, com.apple.driver.IOBluetoothHIDDriver(6.0.9f2)[C65C951F-5EA3-3567-888E-9426F9C6 C9CE]@0x<ptr>->0x<ptr>\nPowerOff\/Restart message to priority client: 220 ms @ 0x<ptr>, com.apple.driver.IOBluetoothHIDDriver(6.0.9f2)[C65C951F-5EA3-3567-888E-9426F9C6 C9CE]@0x<ptr>->0x<ptr>\nPowerOff\/Restart handler completed: 188 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<p tr>->0x<ptr>\nPowerOff\/Restart handler completed: 200 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<p tr>->0x<ptr>\nPowerOff\/Restart handler completed: 207 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<p tr>->0x<ptr>\nPowerOff\/Restart handler completed: 209 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<p tr>->0x<ptr>\nPowerOff\/Restart handler completed: 218 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<p tr>->0x<ptr>\nPowerOff\/Restart handler completed: 291 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<p tr>->0x<ptr>\nPowerOff\/Restart handler completed: 506 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<p tr>->0x<ptr>\nPowerOff\/Restart handler completed: 233 ms @ 0x<ptr>, com.apple.iokit.IOUSBHostFamily(1.2)[922E7520-229B-3C68-B232-A8727A20D44D]@0x<p tr>->0x<ptr>\n\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/xnu\/xnu- 4903.221.2\/iokit\/Kernel\/IOPMrootDomain.cpp:4804\n

But all start with

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 3.1 (16P1065)",...

In my case the most frequent KP is 1.)

What's about you guys?

Use the search option in "Console" to search for >macOSPanicString<.

Cheers

Well, I am crashing again.

As I said last, I wasn't sure if the PRAM clearing suggestion from Apple Support was the reason I was working again. I can definitely say now the PRAM clearing did not fix me.

I turned back on "POWER NAP" and "WAKEUP on WIFI", and I am back to crashing again. It is less frequent because my incremental backups are short now.

gchot20 has a machine check of some sort, while I have a timeout, so it's not obvious they are all exactly the same though. BUT, I really have no idea how to parse these Bridge OS panic reports.

My workaround is simply to turn off these power save features, and my unattended MacBook crashes seem to go away.

Have you tried to reset the SMC following this procedure ?

How to reset the System Management Controller (SMC) on your Mac - Apple Support

all ,

my mbp has fixed this issue whith a clean install os .(clean all files on SSD and re-install macOS)

This problem is occurring regularly for me. I have only had the laptop two days and it has crashed at least 6 times.

Mostly it just happens on wake from sleep with no peripherals attached.

"caused_by":"bridgeos","macos_system_state":"running","bug_type":"210","os_versi on":"Bridge OS 2.4.1 (15P6613)","timestamp":"2018-07-22 08:19:35.87 +0000","incident_id":"6EF39A3D-35F6-47FB-85DA-6AA87B321A12"}

{

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

"product" : "iBridge2,3",

"kernel" : "Darwin Kernel Version 17.7.0: Fri Jun 15 18:33:47 PDT 2018; root:xnu-4570.71.1~1\/RELEASE_ARM64_T8010",

"incident" : "6EF39A3D-35F6-47FB-85DA-6AA87B321A12",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-07-22 08:19:35.70 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff00e34a81c): ANS2 Recoverable Panic - assert failed: [11993], src\/drivers\/apple\/aspcore\/nandeng\/ans2\/pre_nand_eng.c:506:AXI_ERR F2H 0 SL[0] ERR 0x80000000 HIX 1 LBA 0x985dfaab secOffset 0x5 dp[41a70001, 6f0005, 985dfaab, a71] mmu[7752a38, 1348000, 8080c, 0, 41000700, 108d\n assert failed: [11993], src\/drivers\/apple\/aspcore\/nandeng\/ans2\/pre_nand_eng.c:506:AXI_ERR F2H 0 SL[0] ERR 0x80000000 HIX 1 LBA 0x985dfaab secOffset 0x5 dp[41a70001, 6f0005, 985dfaab, a71] mmu[7752a38, 1348000, 8080c, 0, 41000700, 108d00, 40f]\nRTKit:

Hello Andrew,

I have seen a couple of people report shutdown codes of -20 with machines that have the T2 chip. This thread is very similar: new Macbook pro 2018 random restarts

The machine restarts but there is no kernel panic. It looks like there is a kernel panic in the BridgeOS, but it doesn’t manifest itself like a traditional kernel panic.

Apple is not here. Apple Support Communities is a User-to-User support forum. If other users can not help you think of a fix, No further help is likely to be forthcoming using this medium. There are no standard mechanisms for escalating problems to Apple support from here, and Apple support does NOT monitor these forums looking for trends and outstanding issues.

DO NOT "wait for Apple to provide a fix". Unless and until a large number of users present their issues through standard problem-reporting channels, Apple does not know there is a problem, and is NOT working on a fix. Being selfish is the best policy, getting yours fixed helps everyone.

If advice supplied here does not provide resolution, You must take additional steps to resolve your issues. Contact Apple support directly through one of these methods:

• contact telephone support (free for 90 days with a new Mac, of for three years with AppleCare purchase)

• make an appointment at the genius bar at an Apple-owned store for hardware evaluation and advice (free anytime, but after five years parts may no longer be available).

• initiate an Online chat

• Visit an Apple Authorized Service Provider (there may be an "evaluation fee", but if they perform any service for a fee, ask for a rebate of the evaluation fee).

Just got off the phone with Phong at Apple Support.

They want me to try to get the sleep crash to happen again with just the Mac and Power Adapter. If it happens, I am to get a full System Diagnostics report archive (using the key stroke combo: Shift, Control, Option, Command, Period) and then send that to a log collector URL that will connect the log archive with my case number. I did send them a System Profiler log file earlier today. Then they will begin the process of a machine exchange where the one that fails goes to a specific tech support capture point AFTER I get a new one shipped to me with an identical configuration to the one I have. Perhaps that newer one will have updated T2 firmware.

The sleep restarts, for me, are rarer lately than they were at first but I did have one fairly recently after a several hour sleep period.

Phong said he would check in tomorrow to see what the status is.

I guess this problem is not universal affecting all 2018 machines but it is extremely annoying nonetheless. I really was looking forward to retiring my mid-2012 Retina Pro Mac for this new one...

I the same type of crash. And opened a case with Apple.

For me, the crash/reboot only happened when I leave the screen lid at least partially opened, and activate the screen saver, and leave it like that overnight. Most morning, it has rebooted and the dump is always the same, e.g. BridgeOS error: {"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_versio n":"Bridge OS 2.4.1 (15P6703)",...

So far, I did:

• First install, I had not migrated my old account, was manual setup of all my software and data.
• Crashes started one or two night after.
• Opened case with Apple, they asked if I was willing to gradually try re-install, erase-re-install, etc...
• Reinstall OS without erasing disk.
• Still crashes
• Erased disk and re-installed
• Left it running like that 24 hours, no crash (but that was short)
• Erased disk and re-installed again, but created account from backup (from preceding install)
• Crashed again.
• Left for the weekend, with the lid closed: during this time, no crashes each I opened the lid.
• Erased disk and re-installed.
• No data imported, only activated iCloud, used safari (Watched some of Marcella on Netflix 😉).
• Will let it run 2-3 days without anything else, sleeping with lid opened, and see.

I have 2 huge gmail accounts that I use in Mail, with a lot of activities, many automated emails. Mail is starting to be crappy handling that. I did not activate Mail on that latest install. Will wait a few days before I do it.

Other software that I will install gradually: Xcode, Brew, Tunnelblick, Slack (tones of notifications), Eclipse, 150GB photos library, same size iTunes lib.

It "feels" like this is a software problem, related to notifications and sleep. But hey... what do I know...

--

Claude

A little update on this topic.

Of course, that 24 hours are not an indicator, but anyway it worth to try.
Go to Settings->Energy Saver.
1. UNCHECK automatical switching between the GPUs (if exists of course)
2. CHECK prevent computer from sleeping automatically...
3. UNCHECK put hard disk to sleep

4. UNCHECK Power Nap (regarding)
5. Turn display off after: - NEVER

I will update this topic if everything is fine.