BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

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

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.

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",

Connected directly to the computer:

• CalDigit TS3+ Dock
• LG 27" UltraFine 5K Monitor

Connected to the LG Monitor USB-C Hub through adapter cables:

• Plantronics Savi W740 Headset Cradle
• Logitech Unifying Receiver for KB and Mouse

Connected to CalDigit TS3+ Dock

• Two 14 year old NEC 1600x1200 LCD Monitors
  • One via USB-C to DVI
  • One via DisplayPort to DVI
• USB3 drive for TimeMachine
• USB3 drive for Acronis True Image backups
• USB Samson Go Mic Connect
• Speakers via analog headphone port
• Wired Ethernet

The computer sleeps each night and intermittently during the day, but is always on. Using FileVault, Boot Camp, Power Nap, Wake for Network Access and Hard Disks sleep when idle. Mostly default settings, I think.

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

Same exact thing (Bridge OS 2.4.1 crash) here on my new 2018 i9 MBP. I've been reading similar threads from iMac Pro users.

It has happened twice in three days where the computer was asleep and I came back to find it restarted on its own "due to a problem."

Any suggestions?

I have MBP 2018 i9/32/500G. I got the same bug_type 210 as yours. But panicString and macOSPanicString appear different.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.4.1 (15P6613)","timestamp":"2018-07-25 03:54:35.87 +0000","incident_id":"2B7FD5FA-F3C3-4263-9CD1-9BBD6CBD53C4"}

{

"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" : "2B7FD5FA-F3C3-4263-9CD1-9BBD6CBD53C4",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-07-25 03:54:35.78 +0000",

"panicString" : "panic(cpu 0 caller 0xfffffff01ad73984): x86 global reset detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 15P6613\nKernel version: Darwin Kernel Version 17.7.0: Fri Jun 15 18:33:47 PDT 2018; root:xnu-4570.71.1~1\/RELEASE_ARM64_T8010\nKernelCache UUID: 4BD537B3EB4924661E7DD2268EBDBDEF\niBoot version: iBoot-4076.75.2\nsecure boot?: YES\nx86 EFI Boot State: 0xe\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide: 0x0000000014600000\nKernel text base: 0xfffffff01b604000\nEpoch Time: sec usec\n Boot : 0x5b575de2 0x000e65ab\n Sleep : 0x5b57f46e 0x00016b6b\n Wake : 0x5b57f46e 0x000a99b5\n Calendar: 0x5b57f46e 0x000beef4\n\nPanicked task 0xffffffe0001fa2b0: 3253 pages, 207 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0004caf60, backtrace: 0xffffffe016f2b530, tid: 392\n\t\t lr: 0xfffffff01b7f88f0 fp: 0xffffffe016f2b670\n\t\t lr: 0xfffffff01b6e15f4 fp: 0xffffffe016f2b680\n\t\t lr: 0xfffffff01b713a44 fp: 0xffffffe016f2b9f0\n\t\t lr: 0xfffffff01b713dd4 fp: 0xffffffe016f2ba50\n\t\t lr: 0xfffffff01b715914 fp: 0xffffffe016f2ba70\n\t\t lr: 0xfffffff01ad73984 fp: 0xffffffe016f2bae0\n\t\t lr: 0xfffffff01ad75bc8 fp: 0xffffffe016f2bb80\n\t\t lr: 0xfffffff01ad7313c fp: 0xffffffe016f2bc00\n\t\t lr: 0xfffffff01ad32aa4 fp: 0xffffffe016f2bc30\n\t\t lr: 0xfffffff01bb70764 fp: 0xffffffe016f2bc60\n\t\t lr: 0xfffffff01bb700bc fp: 0xffffffe016f2bc90\n\t\t lr: 0xfffffff01b6ec500 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

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

"macOSPanicFlags" : "0x0",

"macOSPanicString" : "Global Reset\nGRC0 = 0x00010000\r\nGRC1 = 0x00000000\r\n",

"memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"pa geSize":16384,"memoryPressure":false,"memoryPages":{"active":9333,"throttled":0, "fileBacked":9997,"wired":5115,"purgeable":36,"inactive":2136,"free":10279,"spec ulative":3325}},

FYI, I was seeing the same issue: when I open the lid on the laptop, it would already have crashed/restarted and I'd see the Bridge OS crash report. It was easy to reproduce: close the lid, wait a bit, open it.

I wasn't able to reproduce the problem in Safe Mode. (Reboot, hold shift down while it is powering up.) That suggested to me that for me, at least, it is likely a software issue.

I looked for older kernel extensions I had installed that got copied into the new laptop by the migration tool. One stood out: I had an xbox360 controller extension installed, from when I was futzing around with that on my prior laptop. I removed the extension (removed it from /Library/Extensions -- I forget the names, but there were two .kext files associated with it -- something like xboxcontroller or similar), and rebooted.

Since I did that, I haven't seen a crash.

Not yet, especially if I might have to turn in this machine for a different one. I did look those errors up and convinced myself it was nothing to worry about, but really don’t know for sure. I’m going to wait and see for now...

I've been running 8 days now on MBP 2018. I get the crash (Bridge OS 2.4.1 Panic) a little more than once a day. Always when waking from sleep. I see that it rebooted sometime earlier. I turned off power nap in settings as a test and have had one failure since.

Put the laptop to sleep last night. Woke it up this morning and sure enough, it had restarted and I was staring at the login screen. No Crash Reporter this time however. Also, I've been running it in clamshell mode, but I know I had this happen at least once, if not more, when I was using it normally while setting it up.

I also run clamshell mode, FWIW.

I woke up at 0400 to check on my backups this morning and it had indeed restarted again preventing the backups from completing.

After noting the restart at 0400, I used settings to prevent the MBP from sleeping at all and restarted an Acronis True Image backup to USB disk. No restart happened in the 2 1/2 hours, but the backup still failed near the end on drive not accessible. This highlights a second problem where my USB drives seem to want to disappear now, even when actively in use.

In my case, I replaced my older MBP 2016 and put down the new MBP 2018 in the same place with the same peripherals and connections. But in the same setup, I have the spontaneous restarts and can't reliably get full backups using either Acronis or TimeMachine without the disks going offline. I really should not have sold the MBP 2016 so quickly because my work feels at risk now. Lack of reliable backups and concerns about file system health from all the bouncing is keeping me awake at night.

I will continue to try different settings to find something helps and report if I stumble across something. Next up, I am going to try having the MBP never sleep and drives never sleep.

Happening to me as well. Just happened a few minutes ago after about 30 minutes of sleep and a re-wake where I am told that there had been a shutdown.

Have a support ticket and I am supposed to get a follow up call this morning from Apple Support.

Shows abnormal shutdown.

Here is my etrecheck report:

EtreCheck version: 4.3.6 (4D041)

Report generated: 2018-07-26 09:24:51

Download EtreCheck from https://etrecheck.com

Runtime: 2:00

Performance: Excellent

Problem: Computer is restarting

Description:

Crashed when in sleep mode. Saw bridgeOS kernel panic

Major Issues:

Anything that appears on this list needs immediate attention.

No Time Machine backup- Time Machine backup not found.

Minor Issues:

These issues do not need immediate attention but they may indicate future problems.

32-bit Apps- This machine has 32-bits apps that may have problems in the future.

Abnormal shutdown- Your machine shut down abnormally.

Hardware Information:

15" MacBook Pro with Thunderbolt 3 and Touch ID (Mid 2018)

MacBook Pro Model: MacBookPro15,1

1 2.9 GHz Intel Core i9 (i9-8950HK) CPU: 6-core

32 GB RAM - Not upgradeable

BANK 0/ChannelA-DIMM0 - 16 GB DDR4 2400 ok

BANK 2/ChannelB-DIMM0 - 16 GB DDR4 2400 ok

Battery: Health = Normal - Cycle count = 1

Video Information:

Intel UHD Graphics 630 - VRAM: 1536 MB

Color LCD

Radeon Pro 560X - VRAM: 4096 MB

Drives:

disk0 - APPLE SSD AP2048M 2.00 TB (Solid State - TRIM: Yes)

Internal PCI-Express 8.0 GT/s x4 NVM Express

disk0s1 - EFI [EFI] 315 MB

disk0s2 2.00 TB

disk1s1 - Macintosh HD (APFS) 2.00 TB (31.73 GB used)

disk1s2 - Preboot (APFS) [APFS Preboot] 2.00 TB (23 MB used)

disk1s3 - Recovery (APFS) [Recovery] 2.00 TB (516 MB used)

disk1s4 - VM (APFS) [APFS VM] 2.00 TB (1.07 GB used)

Mounted Volumes:

disk1s1 - Macintosh HD 2.00 TB (1.97 TB free)

APFS

Mount point: /

Encrypted

disk1s4 - VM [APFS VM] 2.00 TB (1.97 TB free)

APFS

Mount point: /private/var/vm

Encrypted

Network:

Interface en0: Wi-Fi

802.11 a/b/g/n/ac

One IPv4 address

Interface en6: Bluetooth PAN

Interface bridge0: Thunderbolt Bridge

iCloud Quota: 36.89 GB available

System Software:

macOS High Sierra 10.13.6 (17G2208)

Time since boot: Less than an hour

System Load: 1.93 (1 min ago) 1.26 (5 min ago) 0.56 (15 min ago)

Security:

32-bit Applications:

One 32-bit app

System Launch Agents:

System Launch Daemons:

Launch Daemons:

User Login Items:

iTunesHelper Application (Apple - installed 2018-07-20)

(/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)

Internet Plug-ins:

QuickTime Plugin: (installed 2018-07-04)

Time Machine:

Time Machine Not Configured!

Top Processes by CPU:

Top Processes by Memory:

Top Processes by Network Use:

Top Processes by Energy Use:

Virtual Memory Information:

Software Installs (past 30 days):

Diagnostics Information (past 7 days):

2018-07-26 09:15:43 Last Shutdown Cause: -20 - Unknown

End of report

Argh; so, I had thought getting rid of the xbox360 controller extension had solved this crash problem for me. It only seems to have reduce the frequency. I saw the crash come back after the laptop had been sleeping overnight and I opened the lid in the morning. 😟