BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

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.

OK, back from the Apple service centre and Apple store. A bit of a run around but in the end Apple did what Apple does best and they worked hard to give the customer a great experience, even when we are all experiencing issues like this one. Long story but in the end Apple provided a new Mac for me. I have reloaded it but this time I formatted the disk first, re-installed the OS from the recovery partition, booted and installed MacOS WITHOUT FILEVAULT and finally restored from my Time Machine backup. Main purpose for the re-install without FileVault was to eliminate the error I mentioned in my post. I have subsequently enabled FileVault after the restore. System has been running for the past 15 hours. Connected to power but lid closed overnight. No issues so far. Disk Utility runs health check/first aid with no errors now. The Mac has been busy doing Photo's background work - seems like it was comparing/uploading the restored Photos library to the iCloud Photos Library. Will continue monitoring over the next week. First system crashed within 4-5 days. I think this thread serves as a group therapy session more than problem solving forum as we all patiently wait for Apple to fix this issue.

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

Just a note. This was run from battery. The charger wasn't plugged in...

...................

I Have just tested it with the charger plugged in and that seems to be working fine. On battery power I can reproduce it every single time...

Hi @LoveSteveJobs365,

I had two MBP's with the T2 security chips, which both had the BridgeOS issue. I returned them both.

One was only ever connected to the supplied Apple charger (i.e. it was never connected to any other peripherals). The other MBP had a variety of connected peripherals; USB-C hub, USB-C monitor, HDMI monitor (via hub), USB-3.0 HDD's (via hub), USB-C SSD.

Both only ever showed the problem after waking up. When the problem occurred, I was back at the login screen. On logging in, the crash reporter displayed the problem.

I spoke with an Apple support engineer, who was part of the team dedicated to investigating the issue. At the time in August, the only consistent factor for customers was all the crashes occurred while the machines were asleep (i.e. sometime after the machines had gone to sleep). No machines crashed with the problem while they were awake. Some customers tried keeping their machines awake at all times, which reportedly stopped the crashes for them. This workaround is only useful if you don't need to run on battery for long periods.

You can determine when a crash occurred by looking at the top of the crash log (e.g. "timestamp":"2018-11-05 07:59:42.73 +0000"), which according to what Apple was seeing will be some time before you woke the machine up, and at a time you would expect the machine to be sleeping.

At the time they were tracking a large number of customers and they found no other factors had any correlation with the crashes (e.g. numbers and types of peripherals connected, types of applications installed and used, charging and not charging, etc.).

I was hoping the support engineer would let me know when they had identified the cause of the problem and when I could go and re-purchase. However, I haven't heard from him since I returned my machines.

I hope this sheds some light on the problem for you.

Cheers,

I contacted Apple Support and they have advised me to return the laptop as they believe it is a hardware fault.

It's been about 6 hours since I erased the disk, reinstalled the latest High Sierra, then installed the Supplemental update. This was recommended by Apple tech support.

Since then I have tried 10 or more sleep/wake executions and so far no recurrence of the BridgeOS panic. I have power nap and wake with Apple Watch enabled. I am not connected to any peripheral devices -- just the computer and power cable.

Of course I probably jinxed it by posting this...

Turning off power nap reduced the issue (crashes in stand by) from 10/10 to 2/10.

Called Apple Germany last saturday and talked to second level support. Quite a nice guy I'm talking to. Today he told me that the T2 team is actively investigating this. They answered his ticket very quickly which makes him think they are already on to something. Just uploaded the system report they asked for.

After I started collecting and analyzing of the crash logs I found that crashes happened on:
"name" : "idle #0" and

"name":"AppleSMC"

But after I modified the configurations - the issue disappeared:

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.

I'll start off by pointing out that this is the second MacBook Pro in the last 3 weeks which has the same issue. The first MacBook Pro (2018 15'/16GB/1TB) started crashing a few days after using it. At one point crashing 4 times in a single hour. After working with the Apple support team it was determined this was a hardware issue. The crash occurs anytime my computer goes to sleep with a bridge OS failure when it starts back up. Rather than replacing it I returned it since it was still under the 14 day policy (which I found out is actually 30 days but thats a separate story).

I received my new MacBook Pro order Tuesday with the same spec computer. Almost out of the box it kept crashing with the same issue which is what lead me to the Apple store today.

After waiting the "Apple Store Minute" I met with a Genius Bar tech who ran a system test on my computer to test the battery, keyboard and other general hardware things. Then he tested the Touch Bar specifically to better understand my issue and my computer started to act up.

My computer started having trouble connecting to his system and he kept having to restart the test to have it only fail or not connect at all. THEN my computer started to overheat in the area where the Touch Bar was. My computer then display an error on my computer screen that stated my computer was overheating and thats when the tech had to cancel the test.

He said there was definitely a hardware issue with my computer (mind you this is my second one) and recommended a replacement or return.

I spent the rest of the evening on the phone with Apple trying to find out what the heck is going on with their computers. I didn't get much help in that area and everyone keeps giving me the run around.

I just received a new Macbook Pro in the holidays and it has crashed 5 times now, with 10.14.2, inb a manner pretty close to the Bridge Crash here. In all 5 cases, there was a Timecapsule backup going on, but there were no other external devices plugged into USB/C ports except for the power convertor. I presume it has something to do with going to sleep. I may force the laptop to stay awake during backups and see if that makes a difference. I have never experienced such an unstable Macbook Pro before.

If it helps, I used the migration assistant to setup the MacBook from a 2015 model.

I have reporterd all 5 crashes in the last 10 days with a Kernel Probem Report. I am sorry about the length of the following string, but I didn't really know where to cut it off.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.2 (16P2542)","timestamp":"2019-01-06 17:58:52.78 +0000","incident_id":"AC9AF040-2EC4-4B9A-A469-077F066E8771"}

{

"build" : "Bridge OS 3.2 (16P2542)",

"product" : "iBridge2,3",

"kernel" : "Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:14 PST 2018; root:xnu-4903.231.4~3\/RELEASE_ARM64_T8010",

"incident" : "AC9AF040-2EC4-4B9A-A469-077F066E8771",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2019-01-06 17:58:52.59 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff0092dab14): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 16P2542\nKernel version: Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:14 PST 2018; root:xnu-4903.231.4~3\/RELEASE_ARM64_T8010\nKernelCache UUID: 9B431313847263DE7B6685D864932934\nKernel UUID: 4BC02A8F-ECD4-37DE-8656-F4FCB742B8C4\niBoot version: iBoot-4513.230.5\nsecure boot?: YES\nx86 EFI Boot State: 0x16\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0xc0\nx86 Previous Power Transitions: 0x70707060400\nPCIeUp link state: 0x1614\nPaniclog version: 11\nKernel slide: 0x0000000002c00000\nKernel text base: 0xfffffff009c04000\nEpoch Time: sec usec\n Boot : 0x5c31b846 0x00073d44\n Sleep : 0x00000000 0x00000000\n Wake : 0x00000000 0x00000000\n Calendar: 0x5c3241ba 0x0004b1c0\n\nPanicked task 0xffffffe000542760: 3073 pages, 206 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe00085c000, backtrace: 0xffffffe016803520, tid: 369\n\t\t lr: 0xfffffff009e00a08 fp: 0xffffffe016803660\n\t\t lr: 0xfffffff009cdd610 fp: 0xffffffe016803670\n\t\t lr: 0xfffffff009d11ce4 fp: 0xffffffe0168039e0\n\t\t lr: 0xfffffff009d1205c fp: 0xffffffe016803a20\n\t\t lr: 0xfffffff009d13c94 fp: 0xffffffe016803a40\n\t\t lr: 0xfffffff0092dab14 fp: 0xffffffe016803ab0\n\t\t lr: 0xfffffff0092dcf9c fp: 0xffffffe016803b50\n\t\t lr: 0xfffffff0092da1d0 fp: 0xffffffe016803be0\n\t\t lr: 0xfffffff009293ab0 fp: 0xffffffe016803c10\n\t\t lr: 0xfffffff00a19afa4 fp: 0xffffffe016803c50\n\t\t lr: 0xfffffff00a19a834 fp: 0xffffffe016803c90\n\t\t lr: 0xfffffff009ce8614 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 103408 **\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,"pageSize":16384,"memoryPressure":false,"memoryPages":{"active":6598,"throttled":0,"fileBacked":10660,"wired":5162,"purgeable":47,"inactive":3143,"free":11309,"speculative":4015}},

[MUCH DELETED]

Model: MacBookPro15,1, BootROM 220.230.16.0.0 (iBridge: 16.16.2542.0.0,0), 6 processors, Intel Core i7, 2.2 GHz, 32 GB, SMC

Graphics: Intel UHD Graphics 630, Intel UHD Graphics 630, Built-In

Graphics: Radeon Pro 555X, Radeon Pro 555X, PCIe

Memory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2400 MHz, Micron, 16ATS2G64HZ-2G6B1 16ATS2G64HZ-2G6B1

Memory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2400 MHz, Micron, 16ATS2G64HZ-2G6B1 16ATS2G64HZ-2G6B1

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Sep 18 2018 16:24:57 version 9.130.86.7.32.6.21 FWID 01-83a3fe91

Bluetooth: Version 6.0.9f2, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

USB Device: USB 3.1 Bus

USB Device: iBridge Bus

USB Device: iBridge DFR brightness

USB Device: iBridge Display

USB Device: Apple Internal Keyboard / Trackpad

USB Device: Headset

USB Device: iBridge ALS

USB Device: iBridge FaceTime HD Camera (Built-in)

USB Device: iBridge

Thunderbolt Bus: MacBook Pro, Apple Inc., 34.6

Thunderbolt Bus: MacBook Pro, Apple Inc., 34.6

I just wanted to followup on my posting. As you guys suggested I did contact Apple support. And I have good news and bad news.

The good news is that my problem is no longer occurring. The bad news is that I changed two things at once, so I am not certain which solved my problem: Thing 1, suggested by Apple Support was just to CLEAR the PRAM. Thing 2, because I was dubious the PRAM settings were the cause, I also TURNED OFF POWER NAP (and TURNED OFF WAKEUP on WIFI). Once I did both of these things, I could do a terabyte backup over a day or two without crashing. So I don't know if clearing the PRAM made any difference. I really would guess this is some odd race condition with power napping.

For what it's worth, I did turn power napping/WoW back on now, and I don't crash. BUT the complicating news is that I can't easily recreate the conditions for the crashes anymore because my backups are now just incremental and short. The crashes only came when I had that long initial 1.5sh TB that stretched over days. SO I can't quickly figure out if the PRAM made any difference.

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.

I’ve had two nights without a crash now after support asked me to disconnect everything but power. Interesting. When I finish working, I shut down and disconnect everything, move it to a desktop, start back up and let it sleep. I have power nap on and wake with watch on FWIW.

FWIW, I'm using a USB-C/Thunderbolt 3 to Thunderbolt 2 adaptor to connect to an OWC Thunderbolt 2 hub. And again, ever since disabling Power Nap in Energy Saver System Preferences 5 days ago, I have not experienced the crash. And even though I reenabled Power Nap yesterday to try to make it crash, despite multiple "sleeps" since then, it has not crashed. Go figure.