BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

crash again with macos mojave 10.14

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 3.0 (16P375)","timestamp":"2018-10-19 13:24:20.89 +0000","incident_id":"BF28627A-E9C3-4D1E-A03C-F1F6E9C52B7A"}

{

"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" : "BF28627A-E9C3-4D1E-A03C-F1F6E9C52B7A",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-10-19 13:24:20.69 +0000",

"panicString" : "panic(cpu 0 caller 0xfffffff0190e29f4): x86 CPU CATERR 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: 0x405060400\nPCIeUp link state: 0x14\nPaniclog version: 11\nKernel slide: 0x0000000012a00000\nKernel text base: 0xfffffff019a04000\nEpoch Time: sec usec\n Boot : 0x5bc87c20 0x000c1dbb\n Sleep : 0x5bc8a96d 0x000a197d\n Wake : 0x5bc9ba8c 0x0009fdf9\n Calendar: 0x5bc9dae5 0x000c44ad\n\nPanicked task 0xffffffe0002b1680: 3224 pages, 208 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0005c9f20, backtrace: 0xffffffe016243530, tid: 381\n\t\t lr: 0xfffffff019c012ec fp: 0xffffffe016243670\n\t\t lr: 0xfffffff019add610 fp: 0xffffffe016243680\n\t\t lr: 0xfffffff019b11ce8 fp: 0xffffffe0162439f0\n\t\t lr: 0xfffffff019b12060 fp: 0xffffffe016243a30\n\t\t lr: 0xfffffff019b13c98 fp: 0xffffffe016243a50\n\t\t lr: 0xfffffff0190e29f4 fp: 0xffffffe016243ac0\n\t\t lr: 0xfffffff0190e4e7c fp: 0xffffffe016243b60\n\t\t lr: 0xfffffff0190e21c0 fp: 0xffffffe016243be0\n\t\t lr: 0xfffffff01909bab0 fp: 0xffffffe016243c10\n\t\t lr: 0xfffffff019f9c0fc fp: 0xffffffe016243c50\n\t\t lr: 0xfffffff019f9b964 fp: 0xffffffe016243c90\n\t\t lr: 0xfffffff019ae8614 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 105968 **\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":8524,"throttled":0, "fileBacked":11792,"wired":5536,"purgeable":37,"inactive":5127,"free":7636,"spec ulative":3413}},

"processByPid" : {

"0" : {"timesThrottled":0,"pageIns":0,"waitInfo":["thread 445: kernel mutex 0xdd394b804d83b55b owned by thread 5053"],"timesDidThrottle":0,"procname":"kernel_task","copyOnWriteFaults":0,"thr eadById":{"372":{"continuation":[0,68842797344],"userTime":2.125e-06,"systemTime ":0,"id":372,"basePriority":81,"name":"AppleD2449PMU","user_usec":2,"schedPriori ty":81,"system_usec":0,"state":["TH_WAIT","TH_UNINT"],"waitEvent":[1,15940855370 478102611]},"445":

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.

Well I also got a 2018 13inch macbook pro with Touch Bar 16Gb memory and 2.7 GHZ i7 processor. My computer doesn't crash but it sometimes just froze randomly and I need to wait about 1 minute until it is awake

My new MacBook Pro 2018 13” i7 is having this exact issue. Kernel Panic when waking from sleep, all updates installed, atttempted to reinstall OS, no change. Very frustrating for a brand new computer.

Hello Russ, I can imagine how you feel. Please let all us confirm in below.
1. Do you use Mojave same as Andrew? Or Do you use High Sierra 10.16.3 with Supplemental update 2?
2. Do you see the report of issue when you login right after opening the shell from closed clamshell style?

Please kindly let all us know. Thank you.

Heya -- sorry for my delay in responding.

The only peripheral I have is an iPhone, and even then just to charge it. I didn't notice any issues connecting to it.

Also just wanted to reiterate that the crashes when the clamshell is closed continue to happen. It is not 100% of the time, but I would say a few times a week.

Mojave 10.14.1 was released Tuesday after the new products announcements, and accompanied shortly thereafter by a Security Update for Mojave, High Sierra, and Sierra (but NOT El Capitan).

Have you tried the new updates to see if they snuck in any improvements?

Hello slifty,

Thank you so much for your information. It was really helpful for me. Almost there, maybe.
However same issue as me exists still when use external devices to supply the power according to him maksimrv. Let me see two more weeks whether the issue occur in new model that has T2 security chip.

To All,
Please Kindly provide me whether you can use peripherals without any issue especially BridgeOS issue. I really need two functionality. The one of them is to supply electric power to the device and the other ons is possible to transfer data(communicate). In my case and most of scenario, I saw BridgeOS crash report after logging in after I opened a lid. But I maybe seen when I use a device after login. When I got this issue, I could not use all USB Type C port. But After I moved to other desk with my Mac by changing the angle of the lid a little bit and the connect to power cable, It worked with my devices that did not work several days. It was very tough week.

Well, Apple can fix this issue on High Sierra 10.13.6 and Mojave.

Thank you.

Hi @maksimrv,

I'm wondering when your MBP was manufactured? I have a hunch that Apple fixed a manufacturing fault that causes this issue. If your MBP was made recently, then my hunch would be wrong. I returned two with the same fault about 4 months ago and I'm hoping new machines are good and I can re-purchase.

By the way, Apple support engineers recommended I return the machines, and they guessed it would be a hardware fault that would get ironed out at some stage. I really hope I don't have to wait for a whole new MBP refresh!

Cheers,

Hi @LoveSteveJobs365,

I had two MBP's with the T2 security chips, which both had the BridgeOS issue. I returned them both.

One was only ever connected to the supplied Apple charger (i.e. it was never connected to any other peripherals). The other MBP had a variety of connected peripherals; USB-C hub, USB-C monitor, HDMI monitor (via hub), USB-3.0 HDD's (via hub), USB-C SSD.

Both only ever showed the problem after waking up. When the problem occurred, I was back at the login screen. On logging in, the crash reporter displayed the problem.

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 (i.e. sometime after the machines had gone to sleep). No machines crashed with the problem while they were awake. Some customers tried keeping their machines awake at all times, which reportedly stopped the crashes for them. This workaround is only useful if you don't need to run on battery for long periods.

You can determine when a crash occurred by looking at the top of the crash log (e.g. "timestamp":"2018-11-05 07:59:42.73 +0000"), which according to what Apple was seeing will be some time before you woke the machine up, and at a time you would expect the machine to be sleeping.

At the time they were tracking a large number of customers and they found no other factors had any correlation with the crashes (e.g. numbers and types of peripherals connected, types of applications installed and used, charging and not charging, etc.).

I was hoping the support engineer would let me know when they had identified the cause of the problem and when I could go and re-purchase. However, I haven't heard from him since I returned my machines.

I hope this sheds some light on the problem for you.

Cheers,

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

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

That fits with what the engineer told me. Machines that went to sleep by closing the lid, or by inactivity, were both having crashes. Also, they had no way to reproduce the problem at will. It happened intermittently, with some machines having the problem multiple times per day, while others could go a week or more with no issues. My two machines had very different frequency of crashes. The first was 3-4 times per week, and the other was less than once per week.

According to the engineer, only a very small percentage of machines sold were reporting the problem, however, if users pressed "cancel", rather than "report problem" in the crash reporter app on reboot, then Apple wouldn't know there had been an issue. Given the variability in frequency, and users not reporting crashes, they were unable to know what percentage of machines sold had the problem.

The lack of reproducibility was also making it hard for the engineers to determine the cause. With no definite cause, they were guessing what was wrong, so while they put together software patches for possible causes, they couldn't know if it had worked until a large number of people with the problem tried the patch and reported back. I used to be a support engineer for NCR Unix systems, and that kind of situation was both rare and a complete nightmare. Until a definite cause was known, rushed fixes were a stab in the dark, very rarely paid off, and sometimes introduced new problems. In fact, it was much smarter to carefully add instrumentation to try and diagnose the problem, rather than to try to actually fix it.

I'm guessing there was a manufacturing fault, for which a software fix has not yet been found. If the problem was still there, then as more machines are sold, I'd expect more and more people contributing to this thread, but the thread isn't getting more active over time. On the other hand, if a software fix had been found, then the thread would die out completely. So, my hunch is they found a manufacturing fault and addressed it (hence the thread is not getting more active), but have yet to find a software fix for the pre-hardware-fix machines (hence the thread is still active, but not growing).

Anyway, that's my 2 cents worth. I'm glad I returned my machines while still under the 12 month warranty. I just wish I could find out if the new machines were any better, so I could get on with upgrading again. My 2009 & 2012 MBPs are seriously struggling. 😟

Hi @GrumFromOz,

Thank you so much for your valuable information.

I was expecting the information. It's surely same issue. It makes me sure that It's really difficult problem to be fixed. Well, I usually take my old MBP somewhere to working on my project. But, I cannot say there is an outlet there. Which means, I should wait for buying MBP2018 touch bar until I will get the good news from you or this thread.

It was really helpful information for all. Thank you so much!

I had MBP 2018 Touch bar model, was according to above tool;

Production week : -34- (August)

Production year : -2018-

Factory: C0 (Quanta Computer (Subsidiary = Tech Com) China)

Anyway, My old MBP Mid-2012 "13(Not Retina Display) has more than 8GB memory and SSD. So, I can still survive except the resolution. But, I really need T2 security chip and high resolution.