BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

A user suggested to do the SMC reset twice in a row.

Im free of kernel panics for more than 48hours!

I can only encourage you to try it out, but be aware of the new procedure for Macs with T2 chip!

Den System Management Controller (SMC) auf dem Mac zurücksetzen - Apple Support

(Hope you will be redirected to your country page 😁 )

I will keep you updated!

Hi @philthyPhil618,

I'm sorry to hear you're having similar problems. Thank you for contributing to the thread, your problem could well be pertinent to what we've all seen with with the MacBook Pro's. It may be unrelated given your machine was not asleep, but who knows?

It seems on macOS machines, a variety of functions run on the T1/T2 chip itself using it's own BridgeOS operating system. Given this, only machines that have a T1 or T2 chip can have kernel panics caused by BridgeOS. So, your new November 2018 MacBook Air with T2 chip may well be seeing the same issue. The new Mac Mini may also start seeing the same problems!

I had hoped Apple had silently found and fixed a hardware or manufacturing fault, however, if November MacBook Air's are having BridgeOS crashes, then that's not the case 😢. I read elsewhere a theory that Apple is doing more QA testing to weed out "bad" machines. However, if that is the case, then clearly the testing isn't perfect!

By the way, a bunch of other threads are actively tracking people with BridgeOS crashes;

• 2018 MacBook Pros crashing with "Bridge OS" error | MacRumors Forums
• "iMac Pro" kernel crash
• iMac Pro restarting because of a problem?

Yet again, I'm glad I returned my two MBP's. I'm sorry you're having to struggle through the same issues.

Cheers,

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:

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).

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.

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

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