BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

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.

I just read a few interesting posts in another thread (iMac Pro).

Some claim that their kernel panics are related to Apple TB3->TB2 adapter. This is similar to my experience. The difference is that my MBP 2018 should have not been in an active transfer. While my kernel panic was definitely BridgeOS and bug type 210, it's not clear whether their TB adapter kernel panics are the same as mine and most MBP 2018 users'.

Anyway, for cross reference, let me link my post of the thread here. You will find those posts a few above the following link: Re: "iMac Pro" kernel crash

I received my brand new Macbook Pro yesterday and after letting it sleep overnight, I unfortunately ran into the same BridgeOS error when I opened it this morning. Specs: i7/32GB RAM/1TB SSD. No accessories connected via USB or Bluetooth except for USB-C power chord. Computer lid was shut overnight. This is a clean re-install with option command R combo and formatted with APFS (case sensitive, encrypted).

After a bit of digging, I believe in this particular case, the blame falls to AppleSMC. How? If you look at the panic string, you will observe:

"Panicked thread: 0xffffffe0009706e0, backtrace: 0xffffffe016b3b530, tid: 337"

ref: https://gist.github.com/sdebnath/fab15b864c09fb70312f9c13c06e03c3#file-gistfile1 -txt-L38

tid: 337 in this case refers to thread ID 337. The stack frame right below it is unfortunately undecipherable as I don't have the symbols to match the addresses to function names, however, the full report does list out the processes and associated threads under "processByPid" and "threadById" respectively. You can search for the tid and in my case:

"name": "AppleSMC"

ref: https://gist.github.com/sdebnath/fab15b864c09fb70312f9c13c06e03c3#file-gistfile1 -txt-L2009

I will try to reset the SMC using the instructions at https://support.apple.com/en-us/HT201295 and see if that improves anything. Very curios if others are observing failures with AppleSMC as well. Would help narrow down this issue for sure!

Full panic report: https://gist.github.com/sdebnath/fab15b864c09fb70312f9c13c06e03c3

I upload related information about T2 issue. https://www.digitaltrends.com/computing/apple-t2-chip-may-be-causing-imac-pro-ma cbook-problems/ the update that many not be worked for the issue occurred when you resume. https://support.apple.com/kb/DL1973?locale=en_US I've not tried this yet. F.Y.I.

Hello 湖北武汉, Kindly tell me which secure boot mode do you use? https://support.apple.com/en-us/HT208330 Did you try to install below update? I'm not sure it will fix your problem or not. https://support.apple.com/en-us/HT209081

Hi 卓,

Take a look the below site link. Hopefully you can find the workaround. I returned my MBP 2018 Touch Bar(High Sierra without supplemental update) to Apple already. The severity is marked as Critical for me. I cannot use this for my business.

https://www.digitaltrends.com/computing/apple-t2-chip-may-be-causing-imac-pro-ma cbook-problems/

Apple security updates - Apple Support

The same problem with MBP 13' 2018 with Touch Bar

MacBook Pro (13-inch, 2018, 4 TBT3), macOS Mojave (10.14.1)

I don't have any peripheral devices only the charger but when it happened I have used the charger from Google Pixel 2 xl and in macOSPanicString "thunderbolt power on failed" maybe this caused the problem.

Very disappointed by this device

Re: Kernel panic on wake

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 3.1 (16P1065)","timestamp":"2018-11-02 17:45:28.78 +0000",

...

"build" : "Bridge OS 3.1 (16P1065)",

"date" : "2018-11-02 17:45:28.31 +0000",

"kernel" : "Darwin Kernel Version 18.2.0: Fri Oct 5 20:16:59 PDT 2018; root:xnu-4903.221.2~4\/RELEASE_ARM64_T8010",

"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 941088 **\n",

"macOSPanicFlags" : "0x4",

"macOSPanicString" : "panic(cpu 0 caller 0xffffff7f88cf3307): \"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),

Hi philthyPhil618,

There is a supplemental update at "https://support.apple.com/kb/DL1983?locale=en_US". Have you installed it? I think it won't be appeared on AppStore window automatically. So, It's necessary to install it from the URL manually.

And, Did you use MBA(MacBook Air 2018) by connecting the outlet when you got the issue? I really want to know. Please kindly let me know.

Hi jttaggart,

Thank you very much for the information. I can understand how you feel. If I were you I cannot accept for the condition. I will refund immediately. There is a return policy. And it's within 14 days.

Returns & Refunds - Shopping Help - Apple

Same here. Purchased a 2018 i9,32GB, Vega 20 about a month ago, and lately it has been crashing when going to sleep.

I do have a Satechi hub for my usb's attached to the computer

Yes, I encountered the same bug with my brand new 2018 15' macbook pro. Kept crashing when connected to an external display. It has been 7 months and still not fixed? Come on, Apple.

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.