BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

Having received my new 15" MBP yesterday, incorporating the new T2 chip, I have experienced two BridgeOS crashes in the past 18 hours.


The most recent happened with a USB-C Samsung drive, an external keyboard and mouse as well as a Belkin USB-C ethernet adapter all connected directly into the USB-C ports on the device.


I did a straight-up Migration Assistant from my 2017 15" MBP with a Touch Bar and had to set up TouchID again on the new one!


The Crash Reporter error was in a completely different format from a normal Crash Report and is not documented on the Mac in the usual /Library places.


Due to fat fingers, I was unable to capture the latest log, but I will post again once I have some more detail.


Has anyone experienced the same thing?

MacBook Pro (15-inch, 2018), macOS High Sierra (10.13.6), 2.9Ghz i9, 32GB RAM, 1TB SSD

Posted on Jul 16, 2018 10:30 PM

Reply
Question marked as Top-ranking reply

Posted on Jul 25, 2018 6:00 PM

FYI, I was seeing the same issue: when I open the lid on the laptop, it would already have crashed/restarted and I'd see the Bridge OS crash report. It was easy to reproduce: close the lid, wait a bit, open it.


I wasn't able to reproduce the problem in Safe Mode. (Reboot, hold shift down while it is powering up.) That suggested to me that for me, at least, it is likely a software issue.


I looked for older kernel extensions I had installed that got copied into the new laptop by the migration tool. One stood out: I had an xbox360 controller extension installed, from when I was futzing around with that on my prior laptop. I removed the extension (removed it from /Library/Extensions -- I forget the names, but there were two .kext files associated with it -- something like xboxcontroller or similar), and rebooted.


Since I did that, I haven't seen a crash.

270 replies

Jul 25, 2018 12:19 AM in response to Andrew Zahra

I have been getting a different error:


{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-07-25 07:10:52.23 +0000","incident_id":"82D269F4-B1C5-465C-8338-A1F9DAC49648"}

{

"build" : "Bridge OS 2.4.1 (15P6703)",

"product" : "iBridge2,3",

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

"incident" : "82D269F4-B1C5-465C-8338-A1F9DAC49648",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-07-25 07:10:51.96 +0000",

"panicString" : "panic(cpu 0 caller 0xfffffff01eb73984): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 15P6703\nKernel version: Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010\nKernelCache UUID: 26CB7FFEC7AA68DD8FCEC101101C7E4E\niBoot version: iBoot-4076.75.2\nsecure boot?: YES\nx86 EFI Boot State: 0xd\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide: 0x0000000018400000\nKernel text base: 0xfffffff01f404000\nEpoch Time: sec usec\n Boot : 0x5b57f289 0x00042129\n Sleep : 0x5b57f3b5 0x000b1f72\n Wake : 0x5b57f3b7 0x00094313\n Calendar: 0x5b58225f 0x0008d400\n\nPanicked task 0xffffffe00057dce8: 3034 pages, 204 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe000754510, backtrace: 0xffffffe017513530, tid: 367\n\t\t lr: 0xfffffff01f5f88f0 fp: 0xffffffe017513670\n\t\t lr: 0xfffffff01f4e15f4 fp: 0xffffffe017513680\n\t\t lr: 0xfffffff01f513a44 fp: 0xffffffe0175139f0\n\t\t lr: 0xfffffff01f513dd4 fp: 0xffffffe017513a50\n\t\t lr: 0xfffffff01f515914 fp: 0xffffffe017513a70\n\t\t lr: 0xfffffff01eb73984 fp: 0xffffffe017513ae0\n\t\t lr: 0xfffffff01eb75bc8 fp: 0xffffffe017513b80\n\t\t lr: 0xfffffff01eb7313c fp: 0xffffffe017513c00\n\t\t lr: 0xfffffff01eb32aa4 fp: 0xffffffe017513c30\n\t\t lr: 0xfffffff01f970784 fp: 0xffffffe017513c60\n\t\t lr: 0xfffffff01f9700bc fp: 0xffffffe017513c90\n\t\t lr: 0xfffffff01f4ec500 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 93072 **\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":5600,"throttled":0, "fileBacked":7396,"wired":4985,"purgeable":14,"inactive":1584,"free":15265,"spec ulative":3007}},

Jul 26, 2018 4:46 AM in response to JMcKee

I also run clamshell mode, FWIW.


I woke up at 0400 to check on my backups this morning and it had indeed restarted again preventing the backups from completing.


After noting the restart at 0400, I used settings to prevent the MBP from sleeping at all and restarted an Acronis True Image backup to USB disk. No restart happened in the 2 1/2 hours, but the backup still failed near the end on drive not accessible. This highlights a second problem where my USB drives seem to want to disappear now, even when actively in use.


In my case, I replaced my older MBP 2016 and put down the new MBP 2018 in the same place with the same peripherals and connections. But in the same setup, I have the spontaneous restarts and can't reliably get full backups using either Acronis or TimeMachine without the disks going offline. I really should not have sold the MBP 2016 so quickly because my work feels at risk now. Lack of reliable backups and concerns about file system health from all the bouncing is keeping me awake at night.


I will continue to try different settings to find something helps and report if I stumble across something. Next up, I am going to try having the MBP never sleep and drives never sleep.

Jul 29, 2018 12:27 PM in response to Andrew Preece

Hey folks,


i have this problem since March/April this year ! (had the 15'' 2017 maxed out modell)

Now I am running the new 13" i7 Modell from 2018 and it happens over and over again.


Today I wiped everything once again, no migration, no backup - and it happend just seconds ago, while running - suddenly my external peripherals werent accepted anymore , so my external soundcard shut down -> no sound


I restarted the mac : right before it went completly off the FAN speed went to the MAX , after several seconds Log In window and again the kernal panic / memory stackshot bla bla :macos_system_state":"running","bug_type":"210"


I ll think im gonna return this little beast and wait for the iMac to come alive ... its sooo annoying

Aug 1, 2018 9:49 AM in response to Andrew Preece

If the panic crash is related to T2 chip, do you actively use touch bar? I’m wondering if someone who don’t get panic use less frequently the touch bar.

T2 does a lot more than touch bar. But my panic happened around the time when I modified the touch bar setting and used a lot. I also found a bug that sometimes icons are not aligned as I configured. Maybe this could be a triggering action of the panic crash?

Aug 2, 2018 2:05 PM in response to JMcKee

Having this issue, as well. Picked up my 2018 15-inch i9 on Tuesday, set up via Time Machine backup. CPU experienced kernel panic overnight while plugged in to an OWC Thunderbolt 3 dock, as I came back to find it had shut down. Brought the machine into work the past two days, where I've left it at the lock screen while connected to power, only to come back and find the same thing has happened two more times. Thought I was in the clear after turning off Power Nap after the second panic, but just experienced again about an hour ago.


Keeping an eye on this thread for the (hopefully) eventual fix.

Aug 2, 2018 3:50 PM in response to krypttic

My first machine was crashing on wake from sleep almost every time with nothing connected.


I received my replacement on Monday. It initially crashed 3 or 4 times but then just stopped crashing.


It has been running 3 days with no crashes now. I re-enabled powernap and hey siri yesterday and still no crashes.


I also should mention I registered a card for apple pay on Monday as well. No idea whether that contributed to anything, but there were no crashes since the registration.

Aug 6, 2018 4:04 PM in response to James Solderitsch

They asked the exact same thing of me. I already sent them logs of the first crashes (with stuff attached). Now they want me to see if it crashes with only the power adapter attached (which it did last night).


Did your Apple rep give you any indication that a replacement machine will fix the issue? Mine didn't seem optimistic that it would. I'm worried I'm setting myself up for another round of reinstalling and wasting my time.

Aug 6, 2018 5:46 PM in response to James Solderitsch

There's little doubt this will be fixed. How soon is the question. Based on what they wanted from me and what you see posted in forums, they are going about it the right way. They no doubt realize the pressure has just dialed up and resources are being applied. iMac Pro is probably a bit of a niche product but MacBook Pros aren't. So as the MBPs roll out, the visibility of the problem may start to ramp up. Like they say, "you always find it in the last place you look." An engineer may find a bad pointer tomorrow and suddenly we all have a fix. Or not. It seems clear there is no one-to-one correlation to a single factor like wake on watch, power nap or the other half dozen settings metioned. I've tried them all. Similarly none of the external device connections I've tried make it go away. The one correlation I can think of is that bare machines are better for everyone, but still don't prevent the occasional restart. This experience has taught me how much I am used to doing at night in terms of housekeeping tasks after I walk away. Things like backups and large file transfers that I routinely start, sleep the display and go to sleep knowing it will be doing something for a couple of hours and then sleep. If not for that, and the fact it does it to me at lunch once in a while, I would just shutdown at night and wait however long it takes. I am thankful that as long as the machine is awake and I am actually using it, I am good to go without a single restart, so far. I'll keep uploading crash reports and diagnostics, but I imagine they are pretty much the same and don't tell them much beyond a certain point. I'm still digging how noticeable the difference is of 6 cores and 32 GB in my work so that is some consolation for the time being.

Aug 8, 2018 5:10 PM in response to mlsfw

I just experienced Bridge OS crash for the first time last night. I did browse through this thread for any useful information and so far my crash appears to be the same as mlsfw.


It happened while the MacBook Pro was asleep. I was watching TV at the time so I wasn't paying attention. I only noticed after the fan started to spin very loudly. I looked at the display and saw user login screen with a message that I must enter password after a restart. That was when I realized that something had gone wrong (Bridge OS crashed).


Peripherals connected at the time of crash:

- Two external USB hard disks via USB-C to USB adapters (at left Thunderbolt 3 ports)

- Belkin Gigabit Ethernet Adapter (at right Thunderbolt 3 port)

- 87W USB-C Power Adapter (at right Thunderbolt 3 port)


I've had this MacBook Pro for 22 days without Bridge OS crash so I thought I was lucky, but I guess not. 😟


I contacted Apple Support and they will call me at 11 am today. They also gave me a case number (100608375220).

Aug 9, 2018 1:28 PM in response to wei292

A range of things... the first time, I had a couple of external devices attached (Samsung SSD, mouse, keyboard, all via a Apple USB-C AV Adapter), running VirtualBox with a couple of VMs and was testing some NetInstall processes (so lots of disk IO).


The second time, I was editing a document with Pages.


The third time, I was in bed asleep and it just did the "sleep crashing" thing that everyone has been talking about.


The single most significant thing: I haven't had a reoccurrence of the BridgeOS crash in more than 10 days.


I have only had to restart for some software changes involving kernel extensions, and the Mac has been fully functional. I have created a CCC disk image of it because I was getting nervous via a USB-C Samsung SSD and have been starting and stopping VMs, running Adobe Creative Suite, debugging an iPad app deployment issue with Xcode and my iPad attached in console mode... just about anything I could think of and the issue hasn't come back.


i have been speaking with JP @ Apple in the US; he has been great and I have also provided some "sysdiagnose" outputs to him and his team for them to example, but without a crash/kernel panic, they don't apparently don't provide a lot of detail to Apple.


I have asked for the support case to remain open, but I can't reproduce the issue.


It is still frustrating because I don't know why it has gotten better.

Aug 9, 2018 1:43 PM in response to Andrew Preece

Andrew,

the first time, I had a couple of external devices attached (Samsung SSD, mouse, keyboard, all via a Apple USB-C AV Adapter), running VirtualBox with a couple of VMs and was testing some NetInstall processes (so lots of disk IO).

The second time, I was editing a document with Pages.

-- you saw machine suddenly turn into black screen during normally using it in macOS?


The third time, I was in bed asleep and it just did the "sleep crashing" thing that everyone has been talking about.

-- after you woke up, you just opened the lid, found machine reboot and panic message in Finder?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.