"iMac Pro" kernel crash

This is a known issue -- with no resolution or recognition that I can find. I, literally, created another post, moments before seeing your message. It appears to be related to the Apple T2 processor, which would only affect the new iMac Pro devices.

Reinstalling the OS via the repair partition, bootable-media, or web-repair methods DO NOT solve this problem. It appears to be a root/core MacOS/iMac Pro issue.

It's worth noting that through my testing, the computer does not expose this behavior when using Bootcamp and Windows 10. Though, if it is related to the encryption co-processor, this would make sense since it's not a feature/function that is exposed to Windows.

I have created another ticket for this issue, and I will ensure that I keep this thread posted.

Not sure where everyone is standing. I returned my iMac Pro in April but still have bug reports outstanding with Apple for the numerous hardware kernel panic issues.

Apple has closed the issue of iMac Pro kernel panic during SMC reset as "resolved in internal tests" and should be fixed in upcoming10.13.6. Not sure where that leaves sleep panics, though.

So here's one interesting thing I didn't notice before... I never tell iMac Pro to "Sleep". Today I went into the menu and clicked on "sleep". And it did. For about 30 seconds. Then not touching the machine or anything around it, I got a nasty "beep" and it sprang to life again. I tried it again and it took longer, but it woke back up the same way.

Can you folks put your machine to sleep and have it stay there or is it just me????

I tell my machine never to sleep or go to screen saver since it seemed this was issue for folks. My iMacPro still goes to screen saver and all my programs were closed. I have never had a crash while I am on the machine actively working. I am still anxiously waiting for others to get their diagnosis form the Apple engineers to see if they also say this is a hardware issue. The update to 10.13.5 did not stop my crashes.

MC

I also have issues w/ sleeping, similiar to what's been described. I've turned the features off (in Mac OS), due to the problem -- however, I have no issues w/ Windows sleeping/hibernating.

I can also confirm that the spontaneous "Bridge OS 2.x" crashing still exists (for me) in 10.13.5. I actually have had more crashes since the upgrade, however since it's ~random, I can't attribute them to the update. My ticket is still being worked by Apple engineers -- and I hope to hear more details/direction this weekend.

Once again, I expressed that I believe that it is somehow related/correlated to the new T2 co-processor (due to the ARM64 kernel reference, in the error message body), however they have not confirmed/denied anything at this time.

Nevertheless, I hope that we hear something soon... I've had these (volatile) issues for 6 months. 😕

Never got around to getting rid of the crypto val stuff, but I figured I'd do that tonight. re-formatted, reloaded from time machine, disk utility now runs clean, system still can't sleep. 30 seconds and the fan turns on, the screens come up and system beeps at me.

This is really getting old.

Not sure if you have a ticket with Apple support, it if not I would think you would want too. The only thing I can think of is whether or not you installed a new version of MacOS and then reloading all your other items from Time Machine or just reloaded everything from Time machine. The former is probably the better way to go. But even with that, i think you have something else going on. The beeping is concerning.

I have same problem, It seriously affected my work. 😰

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3.1 (15P5064)","timestamp":"2018-06-10 19:29:54.48 +0000","incident_id":"A6E6A47A-C0D1-4548-9846-B839CF4B"}

{

"build" : "Bridge OS 2.3.1 (15P5064)",

"product" : "iBridge2,1",

"kernel" : "Darwin Kernel Version 17.6.0: Sat May 5 19:46:24 PDT 2018; root:xnu-4570.60.21~23\/RELEASE_ARM64_T8010",

"incident" : "A6E6A94A-C0D1-45r8-98r6-B8394CF0B",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-06-10 19:29:54.41 +0000",

"panicString" : "panic(cpu 0 caller 0xfffffff014aae984): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 15P5064\nKernel version: Darwin Kernel Version 17.6.0: Sat May 5 19:46:24 PDT 2018; root:xnu-4570.60.21~23\/RELEASE_ARM64_T8010\nKernelCache UUID: 82688F4A0C28C17581768EF79472E265\niBoot version: iBoot-4076.60.11\nsecure boot?: YES\nx86 EFI Boot State: 0xd\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide: 0x000000000e200000\nKernel text base: 0xfffffff015204000\nEpoch Time: sec usec\n Boot : 0x5b1d599e 0x000b79e9\n Sleep : 0x00000000 0x00000000\n Wake : 0x00000000 0x00000000\n Calendar: 0x5b1d7c15 0x0007eca4\n\nPanicked task 0xffffffe0007c85c8: 2461 pages, 166 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe000b72370, backtrace: 0xffffffe01738b530, tid: 337\n\t\t lr: 0xfffffff0153f96bc fp: 0xffffffe01738b670\n\t\t lr: 0xfffffff0152e15f4 fp: 0xffffffe01738b680\n\t\t lr: 0xfffffff015313a44 fp: 0xffffffe01738b9f0\n\t\t lr: 0xfffffff015313dd4 fp: 0xffffffe01738ba50\n\t\t lr: 0xfffffff015315914 fp: 0xffffffe01738ba70\n\t\t lr: 0xfffffff014aae984 fp: 0xffffffe01738bae0\n\t\t lr: 0xfffffff014ab0bc8 fp: 0xffffffe01738bb80\n\t\t lr: 0xfffffff014aae13c fp: 0xffffffe01738bc00\n\t\t lr: 0xfffffff014a6daa4 fp: 0xffffffe01738bc30\n\t\t lr: 0xfffffff0157710b8 fp: 0xffffffe01738bc60\n\t\t lr: 0xfffffff015770a10 fp: 0xffffffe01738bc90\n\t\t lr: 0xfffffff0152ec500 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 76416 **\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":4806,"throttled":0, "fileBacked":7096,"wired":4084,"purgeable":20,"inactive":1389,"free":16903,"spec ulative":2696}},

This is still continuing for me as well. I am not super thrilled at the prospect of a full OS reinstall. I have a ton of challenge/response apps to deal with an this just *****. I did a few of the configuration changes mentioned in this thread,(disable powernap, unlock with watch) but I am noticing an uptick in kernel panics lately. I think Im going to have to return this one...

I'm still awaiting information from the engineers on my latest ticket (06/06/2018). It's been weeks, w/ no input -- though I've been keeping a pulse with the case worker. Nevertheless, I will say: I've reinstalled twice (via Repair Partition method) -- at the advisement of Apple Engineering -- and reinstalled a third time (via Internet Recovery method). Reinstalling the OS has not solved the problem. Removing 'legacy' external drives has not solved the problem. Uninstalling virus protection software has not solved the problem. I wouldn't advise anyone to reinstall their OS, without additional cause or a knowledge-base article (for this specific issue). As of this weekend, I've updated to the latest version of Mac OS (10.13.5), and I have experienced this issue three times since the update.

I just got this crash for the first time tonight. Twice in a row. Internet slowed down. Was playing hearthstone and I was seeing graphic glitches that I've never seen. Then boom, black screen. Held down power, and rebooted to the error message. This happened twice. I've not attempted to play another game. Wondering if it's a graphic card issue. But I've had the iMac Pro since day one, and never experienced this to date.

Has anybody in this thread had a credible fix for this issue? It sounds to me like this is a hardware problem with the custom T2 chip, and there isnt really a way to fix it. Can anyone else confirm this?

I placed a call into Apple (mostly to get it on record that I have this issue). They couldn't seem to find anything in their system relating to this issue, and the tech searched for about 20 minutes while I was on the phone. But I convinced him to keep the ticket open and escalate it. I sent him a collection of my error messages as part of the ticket, and now I'm in wait mode for the response to come back from them.

Incidentally after never having experienced this issue since the launch of the system, I've experienced it multiple times a day for the last week. During this time, I had iPhotos open restoring from iCloud because my iPhoto library had become corrupt on my hard drive. Since it completed restoring yesterday, I've gone a day and a half with no crashes. Not sure if the two are related, but that's really the only difference in the last two days I can think of.

Thanks Andrew. Initially I was getting the issue from day one with app nap, unlock with apple watch and all the energy saving options turned on. After disabling this functionality, it has gotten better and has only happened once or twice while sitting idle. HOWEVER, I am now running into the exact same crash when I launch a certain application- FL Studio. For anyone who's not heard of it, its a music app. The crash happens as it is trying to initialize the audio hardware which is connected via thunderbolt. I have a UAD apollo 8, and a UAD satellite quad dsp daisy chained to that. I think there is something to daisy chaining hardware. The odd thing is that FL Studio is the only application that does this. I also have Reason 10, Cubase 9, Logic Pro X and Korg Gadget. I would blame imageline(the vendor for FL Studio) but the crash is identical to the ones reported here. So they have developed a recipe to recreate it. haha

Interesting, I had the same issue when I was connecting two display port displays (one 4k & one 1440p) in the TB ports, albeit only once or twice a week.

I stopped doing two external screens because it was causing the iMac's Pro builtin display to stay off after coming back from sleep (so only the external screens were working and a reboot was needed to get back the builtin display), Apple support was useless...

So now I only use an additional screen, since then I also cant recall having a kernel crash either.