Announcement: The Apple TV app is here

The new Apple TV app is available on iPhone, iPad, Apple TV 4K, and Apple TV HD. If you have a question or knowledge to share with the community, we want to hear from you.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Question:

Question: 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

Reply
Question marked as Helpful

Jul 22, 2018 2:14 AM in response to Andrew Preece In response to Andrew Preece

This problem is occurring regularly for me. I have only had the laptop two days and it has crashed at least 6 times.


Mostly it just happens on wake from sleep with no peripherals attached.


"caused_by":"bridgeos","macos_system_state":"running","bug_type":"210","os_versi on":"Bridge OS 2.4.1 (15P6613)","timestamp":"2018-07-22 08:19:35.87 +0000","incident_id":"6EF39A3D-35F6-47FB-85DA-6AA87B321A12"}

{

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

"product" : "iBridge2,3",

"kernel" : "Darwin Kernel Version 17.7.0: Fri Jun 15 18:33:47 PDT 2018; root:xnu-4570.71.1~1\/RELEASE_ARM64_T8010",

"incident" : "6EF39A3D-35F6-47FB-85DA-6AA87B321A12",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-07-22 08:19:35.70 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff00e34a81c): ANS2 Recoverable Panic - assert failed: [11993], src\/drivers\/apple\/aspcore\/nandeng\/ans2\/pre_nand_eng.c:506:AXI_ERR F2H 0 SL[0] ERR 0x80000000 HIX 1 LBA 0x985dfaab secOffset 0x5 dp[41a70001, 6f0005, 985dfaab, a71] mmu[7752a38, 1348000, 8080c, 0, 41000700, 108d\n assert failed: [11993], src\/drivers\/apple\/aspcore\/nandeng\/ans2\/pre_nand_eng.c:506:AXI_ERR F2H 0 SL[0] ERR 0x80000000 HIX 1 LBA 0x985dfaab secOffset 0x5 dp[41a70001, 6f0005, 985dfaab, a71] mmu[7752a38, 1348000, 8080c, 0, 41000700, 108d00, 40f]\nRTKit:

Question marked as Helpful

Jul 25, 2018 11:32 AM in response to Andrew Preece In response to Andrew Preece

Apple is not here. Apple Support Communities is a User-to-User support forum. If other users can not help you think of a fix, No further help is likely to be forthcoming using this medium. There are no standard mechanisms for escalating problems to Apple support from here, and Apple support does NOT monitor these forums looking for trends and outstanding issues.


DO NOT "wait for Apple to provide a fix". Unless and until a large number of users present their issues through standard problem-reporting channels, Apple does not know there is a problem, and is NOT working on a fix. Being selfish is the best policy, getting yours fixed helps everyone.


If advice supplied here does not provide resolution, You must take additional steps to resolve your issues. Contact Apple support directly through one of these methods:


• contact telephone support (free for 90 days with a new Mac, of for three years with AppleCare purchase)

• make an appointment at the genius bar at an Apple-owned store for hardware evaluation and advice (free anytime, but after five years parts may no longer be available).

• initiate an Online chat

• Visit an Apple Authorized Service Provider (there may be an "evaluation fee", but if they perform any service for a fee, ask for a rebate of the evaluation fee).

There’s more to the conversation

Read all replies
Question marked as Helpful

Jul 22, 2018 2:14 AM in response to Andrew Preece In response to Andrew Preece

This problem is occurring regularly for me. I have only had the laptop two days and it has crashed at least 6 times.


Mostly it just happens on wake from sleep with no peripherals attached.


"caused_by":"bridgeos","macos_system_state":"running","bug_type":"210","os_versi on":"Bridge OS 2.4.1 (15P6613)","timestamp":"2018-07-22 08:19:35.87 +0000","incident_id":"6EF39A3D-35F6-47FB-85DA-6AA87B321A12"}

{

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

"product" : "iBridge2,3",

"kernel" : "Darwin Kernel Version 17.7.0: Fri Jun 15 18:33:47 PDT 2018; root:xnu-4570.71.1~1\/RELEASE_ARM64_T8010",

"incident" : "6EF39A3D-35F6-47FB-85DA-6AA87B321A12",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-07-22 08:19:35.70 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff00e34a81c): ANS2 Recoverable Panic - assert failed: [11993], src\/drivers\/apple\/aspcore\/nandeng\/ans2\/pre_nand_eng.c:506:AXI_ERR F2H 0 SL[0] ERR 0x80000000 HIX 1 LBA 0x985dfaab secOffset 0x5 dp[41a70001, 6f0005, 985dfaab, a71] mmu[7752a38, 1348000, 8080c, 0, 41000700, 108d\n assert failed: [11993], src\/drivers\/apple\/aspcore\/nandeng\/ans2\/pre_nand_eng.c:506:AXI_ERR F2H 0 SL[0] ERR 0x80000000 HIX 1 LBA 0x985dfaab secOffset 0x5 dp[41a70001, 6f0005, 985dfaab, a71] mmu[7752a38, 1348000, 8080c, 0, 41000700, 108d00, 40f]\nRTKit:

Jul 22, 2018 2:14 AM

Reply Helpful (5)

Jul 22, 2018 4:37 PM in response to Andrew Preece In response to Andrew Preece

Same exact thing (Bridge OS 2.4.1 crash) here on my new 2018 i9 MBP. I've been reading similar threads from iMac Pro users.


It has happened twice in three days where the computer was asleep and I came back to find it restarted on its own "due to a problem."


Any suggestions?

Jul 22, 2018 4:37 PM

Reply Helpful (2)

Jul 22, 2018 5:00 PM in response to Andrew Preece In response to Andrew Preece

Hello Andrew,

I have seen a couple of people report shutdown codes of -20 with machines that have the T2 chip. This thread is very similar: new Macbook pro 2018 random restarts


The machine restarts but there is no kernel panic. It looks like there is a kernel panic in the BridgeOS, but it doesn’t manifest itself like a traditional kernel panic.

Jul 22, 2018 5:00 PM

Reply Helpful

Jul 25, 2018 12:19 AM in response to Andrew Zahra 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 25, 2018 12:19 AM

Reply Helpful

Jul 25, 2018 10:24 AM in response to Andrew Preece In response to Andrew Preece

I have MBP 2018 i9/32/500G. I got the same bug_type 210 as yours. But panicString and macOSPanicString appear different.


{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.4.1 (15P6613)","timestamp":"2018-07-25 03:54:35.87 +0000","incident_id":"2B7FD5FA-F3C3-4263-9CD1-9BBD6CBD53C4"}

{

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

"product" : "iBridge2,3",

"kernel" : "Darwin Kernel Version 17.7.0: Fri Jun 15 18:33:47 PDT 2018; root:xnu-4570.71.1~1\/RELEASE_ARM64_T8010",

"incident" : "2B7FD5FA-F3C3-4263-9CD1-9BBD6CBD53C4",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-07-25 03:54:35.78 +0000",

"panicString" : "panic(cpu 0 caller 0xfffffff01ad73984): x86 global reset detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 15P6613\nKernel version: Darwin Kernel Version 17.7.0: Fri Jun 15 18:33:47 PDT 2018; root:xnu-4570.71.1~1\/RELEASE_ARM64_T8010\nKernelCache UUID: 4BD537B3EB4924661E7DD2268EBDBDEF\niBoot version: iBoot-4076.75.2\nsecure boot?: YES\nx86 EFI Boot State: 0xe\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide: 0x0000000014600000\nKernel text base: 0xfffffff01b604000\nEpoch Time: sec usec\n Boot : 0x5b575de2 0x000e65ab\n Sleep : 0x5b57f46e 0x00016b6b\n Wake : 0x5b57f46e 0x000a99b5\n Calendar: 0x5b57f46e 0x000beef4\n\nPanicked task 0xffffffe0001fa2b0: 3253 pages, 207 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0004caf60, backtrace: 0xffffffe016f2b530, tid: 392\n\t\t lr: 0xfffffff01b7f88f0 fp: 0xffffffe016f2b670\n\t\t lr: 0xfffffff01b6e15f4 fp: 0xffffffe016f2b680\n\t\t lr: 0xfffffff01b713a44 fp: 0xffffffe016f2b9f0\n\t\t lr: 0xfffffff01b713dd4 fp: 0xffffffe016f2ba50\n\t\t lr: 0xfffffff01b715914 fp: 0xffffffe016f2ba70\n\t\t lr: 0xfffffff01ad73984 fp: 0xffffffe016f2bae0\n\t\t lr: 0xfffffff01ad75bc8 fp: 0xffffffe016f2bb80\n\t\t lr: 0xfffffff01ad7313c fp: 0xffffffe016f2bc00\n\t\t lr: 0xfffffff01ad32aa4 fp: 0xffffffe016f2bc30\n\t\t lr: 0xfffffff01bb70764 fp: 0xffffffe016f2bc60\n\t\t lr: 0xfffffff01bb700bc fp: 0xffffffe016f2bc90\n\t\t lr: 0xfffffff01b6ec500 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 97920 **\n",

"macOSPanicFlags" : "0x0",

"macOSPanicString" : "Global Reset\nGRC0 = 0x00010000\r\nGRC1 = 0x00000000\r\n",

"memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"pa geSize":16384,"memoryPressure":false,"memoryPages":{"active":9333,"throttled":0, "fileBacked":9997,"wired":5115,"purgeable":36,"inactive":2136,"free":10279,"spec ulative":3325}},

Jul 25, 2018 10:24 AM

Reply Helpful (1)
Question marked as Helpful

Jul 25, 2018 11:32 AM in response to Andrew Preece In response to Andrew Preece

Apple is not here. Apple Support Communities is a User-to-User support forum. If other users can not help you think of a fix, No further help is likely to be forthcoming using this medium. There are no standard mechanisms for escalating problems to Apple support from here, and Apple support does NOT monitor these forums looking for trends and outstanding issues.


DO NOT "wait for Apple to provide a fix". Unless and until a large number of users present their issues through standard problem-reporting channels, Apple does not know there is a problem, and is NOT working on a fix. Being selfish is the best policy, getting yours fixed helps everyone.


If advice supplied here does not provide resolution, You must take additional steps to resolve your issues. Contact Apple support directly through one of these methods:


• contact telephone support (free for 90 days with a new Mac, of for three years with AppleCare purchase)

• make an appointment at the genius bar at an Apple-owned store for hardware evaluation and advice (free anytime, but after five years parts may no longer be available).

• initiate an Online chat

• Visit an Apple Authorized Service Provider (there may be an "evaluation fee", but if they perform any service for a fee, ask for a rebate of the evaluation fee).

Jul 25, 2018 11:32 AM

Reply Helpful (5)

Jul 25, 2018 6:00 PM in response to JMcKee In response to JMcKee

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.

Jul 25, 2018 6:00 PM

Reply Helpful
User profile for user: Andrew Preece

Question: BridgeOS Crashes Happening on 2018 MacBook Pro with TouchBar