BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

Hey Oliver -- unfortunately I decided not to replace the machine. It simply is not worth the risk to my time and energy to deal with the problems.

I'm likely going to wait for the new laptops that are rumored to come out in October, and even then wait to make sure they're not collective lemons...

Me, too. It happened again and again within 10 days right after I bought this. Apple will replace my MBP soon. But I think They cannot provide us safe one. We may see the problem again. I hope Apple provide me the Mac that produced in the different lot. Very tough.

I use 2FA using with Yubico. I cannot use my Mac for three days at least even though I tried to login many times with making the break for the next time login. which means I tried to do it in the morning, noon, afternoon, evening and night. But Once I plugged my power cable into my Mac at Starbucks in the night, It worked. I was very lucky to move my table at Starbucks to charge the battery. And, It happened next morning again and so I left my Mac with the condition to show the issue at AppleStore. But It worked when I am about to show the issue to the staff. I don't know... I took a video that I can not use All USB Type-C port. Frequency : It happened almost everyday even though I could login once in a while and making it sleep then resume it and then happen. I can not figure out how/when to reproduce the issue. So, I removed the 2FA functionality from configuration file. But It happened again that I can not use LAN and others. But I could charge the battery. I hope your proactiveness will find a route cause of this and to fix.

Hi there folks,

This thread seems to have quietened down a lot. Does that mean the problem has been fixed for most people?

I ask because I returned two faulty machines a month or so ago and want to know if it's now safe to buy some new ones.

Cheers.

Hi Grum,

I bought my machine a month ago and since then I've only had the problem once (happen 16 September with high sierra).

I contacted apple support who advised me to do an SMC reset : I did it.

Now i'm on Mojave and for now all it's fine.

I hope it'll be good, I let you know.

What about all of you?

Regards,

Olivier

Hello GrumFromOz, It will be helpful for you to read below site which is posted by me a few days ago. https://www.digitaltrends.com/computing/apple-t2-chip-may-be-causing-imac-pro-ma cbook-problems/.
I got a customized MBP Touch ID model recently and secure enclave(T2) was enabled as default setting. I didn't change the setting even though I got Bridge OS issue. In fact, It was working for several days since I bought. But, Nobody in AppleStore or customer support told me about workaround even if there is. Hopefully, It might work well when someone did not use the feature. Also a patch is available except power-nap. I don't know I can get it via AppStore or not. Maybe not. I don't recommend anyone to buy this yet if they want to keep working smoothly or really want to use MBP securely with secure enclave. Touch ID is not for initial login.

Hi olivier300, Sorry to interrupt you. I could not do the SMC rest sometimes. Even though I could do it, Nothing to being improved. It depends on the condition and maybe the lot. It's complicated according to Apple Store Genius bar staff. Maybe 2019 model is the best...

GrumFromOz wrote:

[...]

This thread seems to have quietened down a lot. Does that mean the problem has been fixed for most people?

[...]

I can see too that it quietened as well. As I said in a previous post, mine has not crashed for a long time now. And not once since updating to Mojave.

The difficulty of your question is that most people that have no more problems are probably not monitoring this thread anymore, so you may not get as many positive answers as you should.

GrumFromOz wrote:

This thread seems to have quietened down a lot. Does that mean the problem has been fixed for most people?

Hi,

I've not had a crash since applying the patch for High Sierra; in the meantime, I've upgraded to Mojave (release & 10.14.1b1) and still no issues...

Philip

Hi folks,

Thank you for your updates.

It seems the problem has continued at a low frequency for some people, while there doesn't seem to be a growing number of people finding the problem.

So, I think I can interpret two things from this.

Firstly, for existing machine, Apple has been unable to find a definitive fix via software or resets, otherwise all problems would have ceased.

Secondly, Apple may have found and rectified a hardware or manufacturing fault as new devices do not have the problem, otherwise the number of people finding the problem would be increasing.

Given this, I'm thinking I'll wait another month or so to let all old inventory be sold and then pick up some new ones. Mind you, I'll be VERY cautious about how I migrate across this time! I'm mighty glad the Apple support people recommended I return the ones I had!

Cheers.

macbook pro 2018 13 also has this bug；

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 3.0 (16P375)","timestamp":"2018-10-05 10:26:01.51 +0000","incident_id":"3F3FE1BB-C5FD-45DF-8F91-FD4F73276623"}

{

"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" : "3F3FE1BB-C5FD-45DF-8F91-FD4F73276623",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-10-05 10:26:01.40 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff00fce29f4): macOS watchdog 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: 0x10001000100\nPCIeUp link state: 0x14\nPaniclog version: 11\nKernel slide: 0x0000000009600000\nKernel text base: 0xfffffff010604000\nEpoch Time: sec usec\n Boot : 0x5baa3a98 0x0007fdf5\n Sleep : 0x5bb70e25 0x000a1ad0\n Wake : 0x5bb7144c 0x00025e0a\n Calendar: 0x5bb73c1a 0x00076756\n\nPanicked task 0xffffffe00063d680: 3667 pages, 207 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0009c99f0, backtrace: 0xffffffe017323530, tid: 377\n\t\t lr: 0xfffffff0108012ec fp: 0xffffffe017323670\n\t\t lr: 0xfffffff0106dd610 fp: 0xffffffe017323680\n\t\t lr: 0xfffffff010711ce8 fp: 0xffffffe0173239f0\n\t\t lr: 0xfffffff010712060 fp: 0xffffffe017323a30\n\t\t lr: 0xfffffff010713c98 fp: 0xffffffe017323a50\n\t\t lr: 0xfffffff00fce29f4 fp: 0xffffffe017323ac0\n\t\t lr: 0xfffffff00fce4e7c fp: 0xffffffe017323b60\n\t\t lr: 0xfffffff00fce21c0 fp: 0xffffffe017323be0\n\t\t lr: 0xfffffff00fc9bab0 fp: 0xffffffe017323c10\n\t\t lr: 0xfffffff010b9c0fc fp: 0xffffffe017323c50\n\t\t lr: 0xfffffff010b9b964 fp: 0xffffffe017323c90\n\t\t lr: 0xfffffff0106e8614 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 107136 **\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":9435,"throttled":0, "fileBacked":13457,"wired":5999,"purgeable":34,"inactive":5526,"free":5400,"spec ulative":4023}},

"processByPid" : {

A few days ago updated my MBP to Mojave and today crash happened again.
But I realized one thing: every time I had the crashes after configuring the touchbar in different ways (in Safari, Chrome, IDEA)

MBP 2018 2.6Ghz, 16GB, 500GB, latest version of Mojave.

It just hung while I was in skype call. Had same issue first time like two weeks ago, but didn't pay attention.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 3.0 (16P375)","timestamp":"2018-10-13 21:03:49.84 +0000","incident_id":"B0D1641A-96C2-4D29-9492-DC6B3170A4F3"}

{

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

"product" : "iBridge2,3",

"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" : "B0D1641A-96C2-4D29-9492-DC6B3170A4F3",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-10-13 21:03:49.54 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff01a4e29f4): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0x6\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: 0x1\nx86 Previous Power Transitions: 0x20002000200\nPCIeUp link state: 0x14\nPaniclog version: 11\nKernel slide: 0x0000000013e00000\nKernel text base: 0xfffffff01ae04000\nEpoch Time: sec usec\n Boot : 0x5bb0ad90 0x00008a74\n Sleep : 0x5bc1f0c5 0x0006e7ee\n Wake : 0x5bc20737 0x000078bd\n Calendar: 0x5bc25d95 0x0001255d\n\nPanicked task 0xffffffe00022e1c0: 8332 pages, 208 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe00060e980, backtrace: 0xffffffe00ab73530, tid: 343\n\t\t lr: 0xfffffff01b0012ec fp: 0xffffffe00ab73670\n\t\t lr: 0xfffffff01aedd610 fp: 0xffffffe00ab73680\n\t\t lr: 0xfffffff01af11ce8 fp: 0xffffffe00ab739f0\n\t\t lr: 0xfffffff01af12060 fp: 0xffffffe00ab73a30\n\t\t lr: 0xfffffff01af13c98 fp: 0xffffffe00ab73a50\n\t\t lr: 0xfffffff01a4e29f4 fp: 0xffffffe00ab73ac0\n\t\t lr: 0xfffffff01a4e4e7c fp: 0xffffffe00ab73b60\n\t\t lr: 0xfffffff01a4e21c0 fp: 0xffffffe00ab73be0\n\t\t lr: 0xfffffff01a49bab0 fp: 0xffffffe00ab73c10\n\t\t lr: 0xfffffff01b39c0fc fp: 0xffffffe00ab73c50\n\t\t lr: 0xfffffff01b39b964 fp: 0xffffffe00ab73c90\n\t\t lr: 0xfffffff01aee8614 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 105712 **\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":7820,"throttled":0, "fileBacked":11224,"wired":10658,"purgeable":49,"inactive":3716,"free":4025,"spe culative":4105}},

"binaryImages" : [["834fd638-ceb9-5664-a35e-b86dc49df634",18446743936270598144,"U"],["00000000-0 000-0000-0000-000000000000",0,"A"],["f1e4e7eb-d326-3fe5-b9d5-78a7ef251f3e",64424 50944,"S"]],

"notes" : ["Source: \/dev\/rdisk1","31 unindexed user-stack frames from 19 pids: 25,26,27,28,29,36,37,38,40,41,45,49,50,51,52,53,64,65,72"]

I also got a bridge OS 3.0 crash, but it was not during normal operation -- I had let my battery completely drain and I tried to start the computer after it had gone to sleep, but without power connected yet.

When I plugged it into power and booted it up I was met with a "your computer restarted because of a problem" message.

I'll keep an eye out for more crashes like this.

It has now happened two more times, so it was not the drained battery's fault.

It's still only overnight / while the laptop lid is closed, however it's definitely a problem.

Since my last 2018 MBP started this way and eventually got to the point where it crashed 4 times a day, I called support right away this time.

Support recommended I start with a reinstall of the operating system to see if that fixes it; if not, then to do a complete wipe of all data and start from scratch. I'll do the baseline reinstall at some point and see if that fixes the issue.