2018 MacBook Pros crashing with "Bridge OS" error

[Vegerot]

I have a similar issue as you guys. `/Library/Logs/DiagnosticReports/ProxiedDevice-Bridge/panic-f‌ull-2019-09-09-21382‌5.791.ips` has `x86 Shutdown Cause: 0x1` but `log show --predicate 'eventMessage contains "Previous shutdown cause"' --last 30m` has `Previous Shutdown Cause: -20`. Unfortunately I can't find any documentation for `-20`

Full crash log:

{"caused_by":"macos","macos_version":"Mac OS X 10.14.6 (18G95)","os_version":"Bridge OS 3.6 (16P6571)","macos_system_state":"running","incident_id":"F8547009-591F-4EFB-9CA0-4E4DEE985605","timestamp":"2019-09-09 21:38:25.79 +0000","bug_type":"210"}
{
  "build" : "Bridge OS 3.6 (16P6571)",
  "product" : "iBridge2,3",
  "kernel" : "Darwin Kernel Version 18.7.0: Tue Aug 20 15:27:14 PDT 2019; root:xnu-4903.271.2~1\/RELEASE_ARM64_T8010",
  "incident" : "F8547009-591F-4EFB-9CA0-4E4DEE985605",
  "crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
  "date" : "2019-09-09 21:38:25.55 +0000",
  "panicString" : "panic(cpu 1 caller 0xfffffff0101f8d18): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 16P6571\nmacOS version: 18G95\nKernel version: Darwin Kernel Version 18.7.0: Tue Aug 20 15:27:14 PDT 2019; root:xnu-4903.271.2~1\/RELEASE_ARM64_T8010\nKernelCache UUID: 885977DF2F52326CF4784472A3CF2590\nKernel UUID: DE3F494A-B901-34B4-9504-6454BC772145\niBoot version: iBoot-4513.270.14\nsecure boot?: YES\nx86 EFI Boot State: 0xe\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x1\nx86 Previous Power Transitions: 0x20002000200\nPCIeUp link state: 0x94721614\nPaniclog version: 13\nKernel slide:     0x0000000009b10000\nKernel text base: 0xfffffff010b14000\nmach_absolute_time: 0x4f88e2e2ff7\nEpoch Time:        sec       usec\n  Boot    : 0x5d701734 0x0001e1b0\n  Sleep   : 0x5d76bfed 0x0000938e\n  Wake    : 0x5d76c608 0x00094951\n  Calendar: 0x5d76c633 0x0008e053\n\nPanicked task 0xffffffe0002a9680: 3632 pages, 208 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0004be980, backtrace: 0xffffffe000163490, tid: 374\n\t\t  lr: 0xfffffff010c222a4  fp: 0xffffffe000163520\n\t\t  lr: 0xfffffff010d0f5a4  fp: 0xffffffe000163660\n\t\t  lr: 0xfffffff010bed610  fp: 0xffffffe000163670\n\t\t  lr: 0xfffffff010c21848  fp: 0xffffffe0001639e0\n\t\t  lr: 0xfffffff010c21bc0  fp: 0xffffffe000163a20\n\t\t  lr: 0xfffffff010c23a2c  fp: 0xffffffe000163a40\n\t\t  lr: 0xfffffff0101f8d18  fp: 0xffffffe000163ab0\n\t\t  lr: 0xfffffff0101fb14c  fp: 0xffffffe000163b50\n\t\t  lr: 0xfffffff0101f8278  fp: 0xffffffe000163be0\n\t\t  lr: 0xfffffff0101b1a98  fp: 0xffffffe000163c10\n\t\t  lr: 0xfffffff0110a8ac0  fp: 0xffffffe000163c50\n\t\t  lr: 0xfffffff0110a8334  fp: 0xffffffe000163c90\n\t\t  lr: 0xfffffff010bf8614  fp: 0x0000000000000000\n\n",
  "panicFlags" : "0x102",
  "otherString" : "\n** Stackshot Succeeded ** Bytes Traced 111024 **\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":8455,"throttled":0,"fileBacked":11331,"wired":5768,"purgeable":34,"inactive":4890,"free":7578,"speculative":3567}},

 

[slyooney]

Hi everybody,

I just bought second hand a Mac mini (I7/16Gb/128Gb) for audio purpose and I simply can not use it for the very same reason as most of you on this thread : It crashes and reboot all the time.
I boot from an external USB 3.1/1 Tb/SSD drive.
Bridge OS 3.6 involved, T2 ship J174P...

I tried to disconnect every USB peripheral, but crashes happen even with just the hard drive connected.
I bought it thinking it would be like all my old macs... Sooooooo frustrated right now...

What would you recommend ?

{"caused_by":"macos","macos_version":"Mac OS X 10.14.6 (18G95)","os_version":"Bridge OS 3.6 (16P6571)","macos_system_state":"running","incident_id":"2C8AD503-B11A-424C-8536-1A9B7A45FA78","timestamp":"2019-09-10 13:35:32.98 +0000","bug_type":"210"}

 

[xgman]

seems like after the last and likely final mojave update the bridge os crash is happening at every reboot almost.

 

[slyooney]

Hi everybody,

I just bought second hand a Mac mini (I7/16Gb/128Gb) for audio purpose and I simply can not use it for the very same reason as most of you on this thread : It crashes and reboot all the time.
I boot from an external USB 3.1/1 Tb/SSD drive.
Bridge OS 3.6 involved, T2 ship J174P...

I tried to disconnect every USB peripheral, but crashes happen even with just the hard drive connected.
I bought it thinking it would be like all my old macs... Sooooooo frustrated right now...

What would you recommend ?

{"caused_by":"macos","macos_version":"Mac OS X 10.14.6 (18G95)","os_version":"Bridge OS 3.6 (16P6571)","macos_system_state":"running","incident_id":"2C8AD503-B11A-424C-8536-1A9B7A45FA78","timestamp":"2019-09-10 13:35:32.98 +0000","bug_type":"210"}

Auto reply : It looks like the culprit was a defective Ram module. No more error to report for the moment!
Could it mean that Bridge OS KP are due to defective components ?

 

[gbert]

My brand new 2018 MacBook Air is having this BridgeOS crash and reboot. Although it is a 2018 model, it is brand new in the box, purchased during a recent Labor Day sale.

Is a forthcoming MacOS update expected to fix this? My return window is closing in a few days, so I appreciate any information on this.

I did try disabling several T2 related items. FileVault, SIP, Gateway, SecureBoot. It seems to have reduced the crashes, but I still had it happen again even so.

This MBA is spec’d out nicely for the price, so I’d rather keep it if this will be fixed by an upcoming software update. Thanks in advance for any information!

 

[mreg376]

My brand new 2018 MacBook Air is having this BridgeOS crash and reboot. Although it is a 2018 model, it is brand new in the box, purchased during a recent Labor Day sale.

Is a forthcoming MacOS update expected to fix this? My return window is closing in a few days, so I appreciate any information on this.

I did try disabling several T2 related items. FileVault, SIP, Gateway, SecureBoot. It seems to have reduced the crashes, but I still had it happen again even so.

This MBA is spec’d out nicely for the price, so I’d rather keep it if this will be fixed by an upcoming software update. Thanks in advance for any information!

Return it. This remains a chronic problem, even in the 2019 models. Apple has never really acknowledged it, or that they are even working on a fix. People have been hoping a software update would fix this for a year. There have been many software updates - no fix. The insidious part of it is that the problem will sometimes go away for weeks, and then return, or not appear at all until well after the return windows closes. Unless you can countenance spending lots of money for something that is unreliable, return it.
I bought a fully spec'd 13" incher last year, it crashed right out of the box, and I returned it. During the online return process Apple doesn't even ask the reason for the return, so how interested can they be in fixing this?

 

[Sonic]

3 times this week. after the first 2, i bought a Caldigit TS-3 Plus in the hope that the issues would be fixed by using a more reliable hub. it froze again last night. after 15 months of this it's getting to the point where the loss of work and time, and the constant worry about the integrity of my 8 year project, is causing me serious anxiety issues. despite paying for Applecare they no longer respond to me despite calmly listing all the issues i'm experiencing (audio related as well as freezing / kp related)

 

[spyros_mac]

The old 2018 13-inch MBP I had, and my new 2019 15-inch MBP both have crashed. The old one was a crash-heaven, the new one just did it once (fortunately).

But I found the reason in my case: when I have some particular USB devices (not all) connected and/or its own software running, and the computer goes to sleep. For example, when using the old 13-inch MBP, I had an RME Babyface Pro USB audio interface, and if the computer went to sleep, with its software ("TotalMix FX") running, it would crash at random. As soon as I began to quit the applications before sending my Mac to sleep, it would no longer crash (audio interface connected or not). Similarly, the crashes would also occur when I connected anything and If I had the RME device connected at the same time. Similar thing happened just once with my newer Mac, but only when connecting a Sandisk USB C drive for the first time. Never again.

So, I think this is a combination of: T2 equipped Mac + some very specific USB devices and/or its software + sleep mode (not sure about this though, because I think it did crash once with no sleep).

None of my Macs have crashed when alone (with nothing connected to its ports).

My Mac is rock solid now that I isolated the causes, in MY case.

Does anyone have experienced something similar?

I am sorry to inform that I cannot confirm that there is a pattern in the BrideOS crashes like the one described above.
I have also the babyface from RME (the old version), and I have not witnessed any crash after sleep with the Totalmix running or with the audio interface connected.
also I did not have so far any crashes with any USB device connected.

in my case, the two crashes I had were with nothing connected or after a full shutdown.

 

[solouki]

3 times this week. after the first 2, i bought a Caldigit TS-3 Plus in the hope that the issues would be fixed by using a more reliable hub. it froze again last night. after 15 months of this it's getting to the point where the loss of work and time, and the constant worry about the integrity of my 8 year project, is causing me serious anxiety issues. despite paying for Applecare they no longer respond to me despite calmly listing all the issues i'm experiencing (audio related as well as freezing / kp related)

Hi Sonic,

As you have discovered, the KPs are not necessarily caused by any particular USB connected device. KPs have been reported on 2018/9 MBPs with no USB devices attached and on pristine installs of macOS with no other software installed, and under different circumstances with different apps running, even after waking from sleep, etc.

Personally, I have experienced a plethora of errors on three different 2018 MBPs and now one 2019 MBP. Most recently I have experienced a number of WiFi disconnects on a 2019 MBP, found by various servers (VNC, ssh, rsync) timing out before connection is established even while signal-to-noise levels are greater than 50 dBm. Since these servers, as well as Safari, Time Machine, Software Update, etc., often report "Unknown host" errors, I had originally thought that the MBPs were losing DNS information. But now on the latest 2019 MBP I let it ping another computer during the times that rsync/ssh pipes were broken only to find that the a few of the pings would still get through --- ping packet losses of >99%, but still a few pings would be successful. So, the WiFi issues appear to be even more intermittent than I had thought before.

In addition, the last two machines, a 2018 MBP and 2019 MBP have suffered identical SSD corruption errors --- I can't now perform Disk Utility First Aids on the internal SSD of the 2019 MBP because they fail. The very first Disk Utility First Aid does not fail, but the 2nd and all subsequent First Aids fail with an error stating that the SSD needs to be repaired but First Aid does not repair the problem --- and this is after a clean install of the macOS and before any other software or files have been loaded onto the computer.

I can commiserate with your Apple Support experiences. Over the last year I have had two Senior Advisors that just stopped responding to my emails, one of whom I even emailed two months later but still with no reply. In addition, I've had two other Senior Advisors each fail to get back to me for over two weeks on communications that they had scheduled themselves. After several emails from me these last two advisors claimed that emergencies kept them from contacting me, and each expressed surprise that I had not been contacted by someone else during their emergencies. I, too, have been nothing but civil, courteous, and extremely patient with all of my communications with Apple Support/Customer Relations, so there were no causes on my part for Apple not to get back to me. EDIT: On the other hand, my latest Customer Relations person has been marvelously attentive and I feel he actually had my interests in mind.

And lastly, since I have documented proof of the macOS corrupting a file on its own SSD as well as the Disk Utility First Aid continuing failures, I too share your anxiety and worry about corrupting years-long projects.

Solouki

 

[avia_bdg]

I have been dealing with my MacBook Pro 15 inch 2018 for the past three days and I am having the exact same report as yours. Did you happen to know what’s wrong with it? Is it really just a software?

I was having crashes pretty regularly again, then I got a reply out of the blue from Apple Support saying I need to bring it into an Apple Store for repair (again). I brought it in, and one week later the Logic Board and Touch ID were replaced under warranty (£633). That was almost 2 weeks ago, and I haven't had any crashes recur yet *knock on wood*.

 

[solouki]

I was having crashes pretty regularly again, then I got a reply out of the blue from Apple Support saying I need to bring it into an Apple Store for repair (again). I brought it in, and one week later the Logic Board and Touch ID were replaced under warranty (£633). That was almost 2 weeks ago, and I haven't had any crashes recur yet *knock on wood*.

avia_bdg,

May I ask what version of the T2 chip you have on your replaced Logic Board and Touch ID board?

To find this, please run the following command in a Terminal window:

/usr/libexec/remotectl dumpstate | grep -i HWModel

and post the results.

Thanks,
Solouki

 

[avia_bdg]

avia_bdg,

May I ask what version of the T2 chip you have on your replaced Logic Board and Touch ID board?

To find this, please run the following command in a Terminal window:

/usr/libexec/remotectl dumpstate | grep -i HWModel

and post the results.

Thanks,
Solouki

J680AP

But I came to this thread because I just had another random kernel crash and restart. It lasted 2 weeks...

 

[solouki]

J680AP

But I came to this thread because I just had another random kernel crash and restart. It lasted 2 weeks...

Sorry to hear that your MBP just had another KP even after replacing the Logic Board and Touch ID board.

Actually, your T2 version of J680AP is not what I was expecting. May I ask just what the specifications are for your MBP, e.g., say 2019 MBP 15" i9 2.4 GHz, 32GB, 4TB, Vega 20.

Thanks,
Solouki

 

[avia_bdg]

Sorry to hear that your MBP just had another KP even after replacing the Logic Board and Touch ID board.

Actually, your T2 version of J680AP is not what I was expecting. May I ask just what the specifications are for your MBP, e.g., say 2019 MBP 15" i9 2.4 GHz, 32GB, 4TB, Vega 20.

Thanks,
Solouki

2018 MBP 15" i9 2.9 GHz, 32GB, 1TB, Radeon Pro 560X

 

[solouki]

2018 MBP 15" i9 2.9 GHz, 32GB, 1TB, Radeon Pro 560X

Okay, this make more sense to me. Again, sorry to hear that you're still having problems. I don't think these issues can be fixed.

 

[ThomasBPG]

I rolled Catalina on during the night and has so far had three times one hour Cisco WebEx conferences with webcam on, USB peripherals attached....and no crashes so far!

 

[chrfr]

I rolled Catalina on during the night and has so far had three times one hour Cisco WebEx conferences with webcam on, USB peripherals attached....and no crashes so far!

The T2/internal camera/Mojave panic is known to Apple and should be fixed in Catalina. Supposedly it may also be fixed even in Mojave if you install Catalina to another disk, thereby updating the T2 firmware. Another apparent workaround is to leave an external camera connected.

 

[kzoojason76]

The T2/internal camera/Mojave panic is known to Apple and should be fixed in Catalina. Supposedly it may also be fixed even in Mojave if you install Catalina to another disk, thereby updating the T2 firmware. Another apparent workaround is to leave an external camera connected.

Do you have a source for this information??? This is the first I've heard that it was "known" to be fixed with Catalina.

 

[chrfr]

Do you have a source for this information??? This is the first I've heard that it was "known" to be fixed with Catalina.

There's a chance that I'm misremembering, but it is a known issue with Apple and they are working on fixing it. It may be that it's getting fixed some time in the Catalina releases. (It may not have made it into the 10.15 release but I've seen reports from others running the betas that this particular crash went away after the betas were installed.)

 

[kzoojason76]

It has been reported to Apple, sure.. but Apple has never admitted to the issue, or a forth-coming fix.

 

[gyunter]

Crashes in Catalina.

 

[appleuser181]

Crashes in Catalina.

?‍♂️

 

[markwjr]

Hi all, I'm having horrendously frustrating crashes too.

I recently traded in my reliable (but aging) mid-2011 model MacBook Air for a 2019 MacBook Pro 15" that is crashing left and right. 4-8 times a day. I am at my wits end.

I've also experienced similar kernel crashes to what others are writing about here. But now the one that I get is this (and that's all it says in the report):

"BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available"

I have no been running any heavy duty apps, etc.

Anyone have any suggestions?

 

[gyunter]

Anyone have any suggestions?

File a complain to your country's Apple importer -> ask to conduct an independent examination of your macbook -> get a confirmation of hardware issues with your macbook -> get your money back or sue apple in your country of residence.

 

[markwjr]

Thanks for the response. I'm definitely getting this stupid thing looked at. Never has Microsoft crossed my mind, but I am pissed.

Does anyone think it's the custom touch bar on these machines?