BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

Apple is not here. This is a User-to-User forum. Apple does not troll these forums looking for problems.

If you want Apple to notice, be selfish and present your computer at an Apple-owned store or Apple-Authorized Service Provider and ask them for relief. Or call AppleCare (free for 90 days). When the chorus of complaints gets loud enough, Apple will act.

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.

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

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"]

Hello slifty, Thank you for sharing the information with all.

By the way, Can you tell me whether you could use any devices via USB Type-C connector right after you got an issue? I saw this issue with High Sierra 10.13.6(without supplemental update) many times that may be related to power-nap and so on. At that time, I could not use any peripherals via all USB Type-C port before the BridgeOS Crashed or after the BridgeOS crashed. But I can charge the battery. It was like nightmare for me. I think everyone wants to know what you could not do after you got an issue.

Please kindly provide the information if you remember. It's important for all.

Hi @GrumFromOZ,

Looks like it was manufactured at 29 July 2018

Production week: -29- (July)

Production year: -2018-

Model introduced: -2018-

Nice Name: MacBook Pro 13-Inch Touch/Mid-2018

Machine Model: MacBookPro15,2

Family name: A1989

Group1: MacBook

Group2: Pro

http://www.chipmunk.nl/cgi-fast/applemodel.cgi

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

That is true for me, I had this problem only when MBP was closed but I don't have clear steps to reproduce this problem

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,

I'm sorry to hear that. I got same issue when I used High Sierra on MBP2018 Touch bar model. I found the issue(message) when I finally logged in MBP after resuming or power on after using MBP with peripherals (ANKER's network interface) and power cable. Also, I don't remember exactly whether MBP was connected to outlet or not. But, I got the crash message when I was using MBP. It was tough week for me and our AppleCare was not proactively help me out. But, I got help from US directly. I was very glad that.

However, Even though I've kept the condition by sleeping after I cannot use any peripherals using with all USB port, It worked when I visited at Apple Store. I'm doubt T2(SMC(lid, power, misc)) and BridgeOS.

By the way, Did you use any peripherals(any USB interface devices) before sleeping? And, Did you connect MBP to outlet to use your MBP before you get the issue? Please kindly let me know.

I've returned my MBP already. I've been waiting to be fixed the issue by Apple's smart creatives. My current MBP is very heavy... getting tired every day.

I posted this on other threads, but I can tell you this problem has not been fixed at least on the latest brand new imac pro custom order, and with the latest mojave or even the betas. I have frequent crash to power off ("bridge OS" cited in the crash report) during startup only (or reboot) with all T2 chip functions turned off that I can do myself incl the secure boot setting off. I do not use sleep or filevault etc, so it only happens during startup so far. I have done a fair amount of, so far ineffective, troubleshooting and have a case with Apple, but Apple is still hare triggered for only to advise to do a clean install. Obviously not the solution. Unfortunately I don't feel much hope here until they replace the T2 chip hardware entirely. It has been a year since these problems started appearing on the forums and the situation isn't any better. I have limited the functionality of my computer so as to reduce, but not eliminate the problem. So in effect I have a $7000 crippled product waiting for a fix which may never come. That is the sobering bottom line.

part of one of the reports:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 3.2 (16P52540a)","timestamp":"2018-11-24 17:17:32.92 +0000","incident_id":"324AD759-2B36-40F0-9F64-D852A528AF5A"}

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

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-11-24 17:17:32.79 +0000",

"incident" : "324AD759-2B36-40F0-9F64-D852A528AF5A",

"kernel" : "Darwin Kernel Version 18.2.0: Mon Nov 12 20:25:54 PST 2018; root:xnu-4903.231.4~4\/RELEASE_ARM64_T8010",

"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 293920 **\n",

"macOSPanicFlags" : "0x4",

"macOSPanicString" : "panic(cpu 2 caller 0xffffff801e0da1ed): Kernel trap at ...

JMcKee,

Do you get the crypto val errors when running Disk Utility as well?

Hi JMcKee,

After wiping the drive, I chose to "restore from Time Machine" on a backup I made just before wiping the drive. After that I re-installed the OS again. I never used Migration Assistant.

today I plugged it in, hit the 'lock screen' Touch Bar icon, and boom.

-- Now are you seeing the same "macOS watchdog detected" panic in in /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge?

Since installing the patch, and Mojave, I did not have a single crash. Very happy with my MacBook Pro now.