BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

Latest panic string:

panic(cpu 0 caller 0xfffffff00e773984): x86 global reset detected

Debugger message: panic

Memory ID: 0xff

OS version: 15P6703

Kernel version: Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010

KernelCache UUID: 26CB7FFEC7AA68DD8FCEC101101C7E4E

iBoot version: iBoot-4076.75.2

secure boot?: YES

x86 EFI Boot State: 0xe

x86 System State: 0x0

x86 Power State: 0x0

Paniclog version: 9

Kernel slide:

0x0000000008000000

Kernel text base: 0xfffffff00f004000

Epoch Time: sec usec

Boot : 0x5b6cc01e 0x000833e9

Sleep : 0x5b6d0f05 0x000

3b7e4

Wake : 0x00000000 0x00000000

Calendar: 0x5b6d0f05 0x0004bcd2

Panicked task 0xffffffe0001ed720: 3205 pages, 204 threads: pid 0: kernel_task

Panicked thread: 0xffffffe000383cc0, backtrace: 0xffffffe012383530, tid: 384

lr: 0xfffffff00f1f88f0 fp: 0xffffffe012383670

lr: 0xfffffff00f0e15f4 fp: 0xffffffe012383680

lr: 0xfffffff00f113a44 fp: 0xffffffe0123839f0

lr: 0xfffffff00f113dd4 fp: 0xffffffe012383a50

lr: 0xfffffff00f115914 fp: 0xffffffe012383a70

lr: 0xfffffff00e773984 fp: 0xffffffe012383ae0

lr: 0xfffffff00e775bc8 fp: 0xffffffe012383b80

lr: 0xfffffff00e77313c fp: 0xffffffe012383c00

lr: 0xfffffff00e732aa4 fp: 0xffffffe012383c30

lr: 0xfffffff00f570784 fp: 0xffffffe012383c60

lr: 0xfffffff00f5700bc fp: 0xffffffe012383c90

lr: 0xfffffff00f0ec500 fp: 0x0000000000000000

I get logs in the /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge/Retired section. Last one was 8/11 but all the previous ones don't show up - perhaps they were cleared.

Have an appointment with apple today - hoping to have the machine replaced even though I am a few days out of the 14 day return policy. Also need to fix that " warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)" error I see on disk health check. Sad experience with this macbook really. Previous was the mid 2012 Mac book Pro retina and it was an awesome machine. Still is today ! Was only just able to justify an upgrade with the 32GB RAM and i9 being available. Its a noticeable upgrade but hey - six years later !

Quick update from my side:

Called with Apple Support today and spent some time doing the standard resets (NVRAM/PRAM, SMC) and they advised me to do a clean install of Mac OS. So, following their advice I erased my disk and started doing a clean install.

After about 3 minutes into the installation process my MacBook crashed and restarted, corrupting the installation.

Now the laptop has no OS installed and I can't get it installed either, since the laptop keeps rebooting during installation.

Guess I'll have to get it replaced now...

Also seeing AppleSMC crash. (below)

Energy Saver settings are everything checked except

[Power Adapter]

prevent from sleeping

[Battery]

Power Nap

Graphics switching is enabled

I use my i9 MBP as a desktop replacement. It's connected to a StarTech TB3 dock, which provides power.

The lid is only open when I have to login after a crash so, in my case, it isn't related to transition from lid open to lid closed.

It crashes once every 72 hours or so from the day I got it on 19 July.

Panicked task 0xffffffe000111ce8: 10358 pages, 203 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0003f2540, backtrace: 0xffffffe016bab530, tid: 336\n\t\t

"336" : {

"basePriority" : 81,

"id" : 336,

"kernelFrames" : [

[

0,

68838046276

],

[

0,

68838047188

],

[

0,

68838054164

],

[

0,

68827953540

],

[

0,

68827962312

],

[

0,

68827951420

],

[

0,

68827687588

],

[

0,

68842620804

],

[

0,

68842619068

],

[

0,

68837885184

]

],

"name" : "AppleSMC",

"schedPriority" : 81,

"state" : [

"TH_RUN"

],

"system_usec" : 0,

"systemTime" : 0,

"user_usec" : 119849895,

"userTime" : 119.849895416

},

Sadly, 5 times in less than one week.

MacBook Pro13" 2018/i7/16GB-RAM, completely new installed (no immigration).

I bought it, so I can send my MBP15" 2017 to repair - that one also has some problems.

So the situation now is:
My MBP2011 died a year ago on the known GPU-Issue.

So I spend a lot of money to buy the best config of the MBP15" 2017.
Then after a few weeks, some issues started (speaker problems, key problems, some times also the GPU.

But I waited, because I need my MBP for work. BTW my backup-computer is a MBA11" 2011.
I waited to buy a new MacBook Air, but Apple sells only an old tec-MBA.
O.k. I spend more than 3000 CHF/USD on a MBP13" 2018...
So I spend almost 9000 and have no really reliable mac! :-(

I just had my first reset with the machine awake and working on something. The error report was for BridgeOS. My resets had calmed down to less than one per week when sleeping.

I had a horrible lapse in judgement after loading the second supplemental update and also noticing that the Bootcamp drivers are now available. So, I attempted to create a Bootcamp partition and install Windows on it. Somewhere during the partitioning, close to the end I think, the machine spontaneously restarted. Now my partition map is "broken" and I am unable to get rid of the Windows partition that it was creating and is now marked as free space but somehow inaccessible to either use or delete. My Mac partition returns errors during first aid that won't clear. <<inode_val: object (oid 0x3) invalid nchildren (-1) fsroot tree is invalid. The volume could not be verified completely.>> I've worked on that for a day and a half trying to get the volume back to normal. I won't even bother calling support and am preparing to rebuild the machine once I am sure I am backed up redundantly.

Yes. I have the supplemental updates loaded and latest re-downloaded version of High Sierra.

I just happened to rebuild mine from scratch about 36 hours ago. My first act was to load the supplemental updates. My second act was to use Bootcamp Assistant to create a Windows partition just in case it were to fail and force me to rebuild the machine again. But all went smoothly.

Mine doesn't need to be connected to anything. It happens most often when the wifi tries to attach to my 5G main network and the 5G extender. Sometimes, for whatever reason it will have problem and wifi will turn on and off repeatedly and eventually crashes.

I wish I could say for sure that it was the rebuild that helped. I had nightly restarts in the beginning but was fairly stable immediately before this rebuild. I went at least a week without restart. The reason for the rebuild was a Boot Camp partitioning that failed in the middle and left me unable to straighten out the partitions. That said, I have my fingers crossed now that it stays stable for a while. BTW, I attempted the Boot Camp partition immediately after the rebuild and it went flawlessly. So, for the moment everything is as it should be.

In my opinion, there is still no recipe for getting rid of those crashes when you have them. In my experience, re-installing clean (did it many times) has not been the solution (had one the following morning a while back after doing that). The 2nd update seems to have reduced occurrences, but not totally. Having plugged or not different USB devices or adapters did not make any difference in my case. Changing the unit was not the total solution neither (finally had a one wake-up crash a couple of weeks after that).

I personnally can live with those rare crashes, while being optimistic that this is probably software-related and fixable. Overall, very happy with my MacBook Pro 2018.

Happens today again.

BUT! Caused by "macos"{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.4.1 (15P6805)","timestamp":"2018-09-18 18:35:53.08 +0000","incident_id":"A8AFEAD0-EAB4-4450-860F-0A4CC97EF052"}

And

"macOSPanicString" : "panic(cpu 6 caller 0xffffff7f97a4787b):

instead of

"macOSPanicString" : "panic(cpu 0 caller 0xffffff8004699995):

Apple! Take a look at this.

Apple called me after I posted in this exact thread, actually. Blew me away.

...and I hope they'll call again, because my replacement MBP just did this today for the first time. :/

The Stackshot trace is over a megabyte. Ouch.

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.

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.