"iMac Pro" kernel crash

Try a hammer

My iMac Pro crashes rarely, now. It does yet, but less often than a few months ago. This leads me to think of a software issue, partially solved either by Apple or by a third-party developer...

More or less the same here on startup I saw the bridge os crash to need to restart. new imac pro 10/18 vintage with latest mojave. External TB3 chassis that gave zero issues on imac 2017.

I had to run that tool and upload too. Their big helpful answer was wipe and try again. Sheesh...

I like that they call it a gpu "tailspin".

Based on seeing my posts here an AppleCare Specialist reached out to me today via phone to collect some more details about the problems I've been experiencing. We gathered some logs from my system, and they are going to send them up to some Apple Engineers for review. The AppleCare Specialist said that it would be helpful to run a sysdiagnose right after a crash.

I have yet to experience another crash since running the diagnostics thus far. We did go into terminal and exported a log of reboots for the engineers to narrow down the times the kernel panics were happening on my system. If you are unfamiliar with running the sysdiagnose, you can just open up a new terminal window and type sudo sysdiagnose and submit them the file on your open ticket.

Keeping my fingers crossed this problem gets resolved soon for everyone!

Ever since our new iMac Pro arrived (BTC, 10-core, 128 GB RAM, Vega 64, 2TB SSD) we've been hit with crash after crash after crash.

In every case (maybe with one exception) the crashes have occurred when transferring files either to or from the iMac Pro using the 10 gigabit connection between the iMac Pro and our unRAID server.

I've done extensive troubleshooting and diagnostics, and spent 4+ hours on the phone to Tier 2 support.

Issues include: complete kernel panic after transferring 200+ GB of files (smaller file transfers work just fine, but after a total of between 200 and 400 GB of copied files the system just fails, leading me to believe it's an overheating component).

All network ports dying at the same time (there's a video I captured of this happening) followed by a kernel panic or needing a complete reboot to bring the ports back up... but ONLY after transferring files on 10GBe.

When the T2 tech and I tried to nuke the SSD and reinstall OS X 10.13.3, the iMac Pro initially refused to initialize the drive, throwing up all kinds of weird errors when booted through Internet Recovery mode. ,

Eventually (on the third or fourth attempt) it worked, but the symptoms remained even when using a completely clean install with no personal time machine restore.

One such panic starts :

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.0.1 (15P2542)","timestamp":"2018-01-28 03:28:07.99 +0000","incident_id":"xxxxxyyyyyyzzzzz"}

{

"build" : "Bridge OS 2.0.1 (15P2542)",

"product" : "iBridge2,1",

"kernel" : "Darwin Kernel Version 17.4.0: Tue Dec 19 11:34:42 PST 2017; root:xnu-4570.47.16~2\/RELEASE_ARM64_T8010",

"incident" : "<<Incident Key >>> ,

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-01-28 03:28:06.73 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff0076fb3ec): macOS panic detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 15P2542\nKernel version: Darwin Kernel Version 17.4.0: Tue Dec 19 11:34:42 PST 2017; root:xnu-4570.47.16~2\/RELEASE_ARM64_T8010\nKernelCache UUID: 3cxxxxxxxxxxxxxxxxx\niBoot version: iBoot-4076.47.12\nsecure boot?: YES\nx86 EFI Boot State: 0xd\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide: 0x0000000000e00000\nKernel text base: 0xfffffff007e04000\nEpoch Time: sec usec\n Boot : 0x5a6b8d3e 0x0003a939\n Sleep : 0x00000000 0x00000000\n Wake : 0x00000000 0x00000000\n Calendar: 0x5a6d4335 0x000d0b46\n\nPanicked task 0xffffffe0003ccbb0: 2552 pages, 154 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe00077a880, backtrace: 0xffffffe011e93550, tid: 317\n\t\t lr: 0xfffffff007ff322c fp: 0xffffffe011e93690\n\t\t lr: 0xfffffff007edd588 fp: 0xffffffe011e936a0\n\t\t lr: 0xfffffff007f0dcf8 fp: 0xffffffe011e93a10\n\t\t lr: 0xfffffff007f0e008 fp: 0xffffffe011e93a50\n\t\t lr: 0xfffffff007f0f888 fp: 0xffffffe011e93a70\n\t\t lr: 0xfffffff0076fb3ec fp: 0xffffffe011e93ae0\n\t\t lr: 0xfffffff0076fd674 fp: 0xffffffe011e93b80\n\t\t lr: 0xfffffff0076fabac fp: 0xffffffe011e93c00\n\t\t lr: 0xfffffff0076bab08 fp: 0xffffffe011e93c30\n\t\t lr: 0xfffffff00835621c fp: 0xffffffe011e93c60\n\t\t lr: 0xfffffff008355b68 fp: 0xffffffe011e93c90\n\t\t lr: 0xfffffff007ee84e0 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

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

"macOSPanicFlags" : "0x4",

"macOSPanicString" : "panic(cpu 0 caller 0xffffff800f524769): \"userspace panic: remoted connection watchdog expired, no updates from remoted monitoring thread in 76 seconds\"@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/xnu\/xnu-4570.4 7.16\/bsd\/kern\/kern_shutdown.c:249\nBacktrace (CPU 0), Frame : Return Address\n0xffffffce4f3cba70 : 0xffffff800f04f606 \n0xffffffce4f3cbac0 : 0xffffff800f17c744 \n0xffffffce4f3cbb00 : 0xffffff800f16e159 \n0xffffffce4f3cbb80 : 0xffffff800f001120 \n0xffffffce4f3cbba0 : 0xffffff800f04f03c \n0xffffffce4f3cbcd0 : 0xffffff800f04edbc \n0xffffffce4f3cbd30 : 0xffffff800f524769 \n0xffffffce4f3cbdf0 : 0xffffff800f53b7ef \n0xffffffce4f3cbf40 : 0xffffff800f5fa788 \n0xffffffce4f3cbfa0 : 0xffffff800f001906 \n\nBSD process name corresponding to current thread: watchdogd\n\nMac OS version:\n17D2047\n\nKernel version:\nDarwin Kernel Version 17.4.0: Tue Dec 19 10:52:05 PST 2017; root:xnu-4570.47.16~1\/RELEASE_X86_64\nKernel UUID: 29EF1F85-10C5-3F25-AED6-5529E5948D42\nKernel slide: 0x000000000ec00000\nKernel text base: 0xffffff800ee00000\n__HIB text base: 0xffffff800ed00000\nSystem model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)\n\nSystem uptime in nanoseconds: 112104521319652\nlast loaded kext at 107711979353914: @filesystems.smbfs\t3.2.1 (addr 0xffffff7f94364000, size 434176)\nlast unloaded kext at 305498954135: @filesystems.msdosfs\t1.10 (addr 0xffffff7f92f60000, size 61440)\nloaded kexts:\n@filesystems.smbfs\t3.2.1\n>!AUpstreamUserClient\t3.6.4\n@kext.AMDFrame buffer\t1.6.4\n@kext.AMDRadeonX5000\t1.6.4\n>!AGraphicsDevicePolicy\t3.16.21\n@A GDCPluginDisplayMetrics\t3.16.2\n>!AHV\t1\n|IOUserEthernet\t1.0.1\n|IO!BSerialMa nager\t6.0.4f1\n>AGPM\t110.23.31\n>!APlatformEnabler\t2.7.0d0\n>X86PlatformShim\ t1.0.0\n>pmtelemetry\t1\n@kext.AMD10000!C\t1.6.4\n@Dont_Steal_Mac_OS_X\t7.0.0\n> !AThunderboltIP\t3.1.1\n>!AGFXHDA\t100.1.4\n>!ABridgeAudio!C\t3.98\n>BridgeAudio Communication\t3.98\n>!AOSXWatchdog\t1\n>!A!ISlowAdaptiveClocking\t4.0.0\n>!A!IP CHPMC\t2.0.1\n>!AMCCSControl\t1.5.3\n@filesystems.autofs\t3.0\n>!AHIDALSService\ t1\n>!UCardReader\t439.47.2\n@filesystems.apfs\t748.47.11\n@filesystems.hfs.kext \t407.30.1\n@BootCache\t40\n@!AFSCompression.!AFSCompressionTypeDataless\t1.0.0d 1\n@!AFSCompression.!AFSCompressionTypeZlib\t1.0.0\n>!ABCMWLANBusInterfacePCIe\t 1\n>!AACPIButtons\t6.1\n>!ASMBIOS\t2.1\n>!AACPIEC\t6.1\n>!AAPIC\t1.7\n@nke.appli cationfirewall\t183\n$TMSafetyNet\t8\n$quarantine\t3\n@IOBufferCopyEngineTest\t1 \n|IOAccelerator!F2\t376.6\n@kext.AMDRadeonX5000AccelLibs\t1.4.4\n>!AGraphicsCon trol\t3.16.21\n>!ASSE\t1.0\n|IOSurface\t209.2.2\n@kext.AMDRadeonX5100HWLibs\t1.0 \n@kext.AMDSupport\t1.6.4\n@!AGPUWrangler\t3.16.2\n@!AGraphicsDeviceControl\t3.1 6.21\n|IOAudio!F\t206.5\n@vecLib.kext\t1.2.0\n|IONDRVSupport\t517.22\n|IO!BHost! CUARTTransport\t6.0.4f1\n|IO!BHost!CTransport\t6.0.4f1\n>!A!ILpssUARTv1\t3.0.60\ n>!A!ILpssUARTCommon\t3.0.60\n>!AOnboardSerial\t1.0\n|IOSkywalk!F\t1\n@kext.AMDR adeonX5000HWServices\t1.6.4\n>X86PlatformPlugin\t1.0.0\n|IOSlowAdaptiveClocking! F\t1.0.0\n>IOPlatformPlugin!F\t6.0.0d8\n>!ASMBus!C\t1.0.18d1\n|IOGraphics!F\t517 .22\n@kext.triggers\t1.0\n>usb.IOUSBHostHIDDevice\t1.2\n>usb.cdc.ncm\t5.0.0\n>us b.cdc\t5.0.0\n>usb.networking\t5.0.0\n>usb.!UHostCompositeDevice\t1.2\n@filesyst ems.hfs.encodings.kext\t1\n>!AThunderboltDPInAdapter\t5.0.2\n>!AThunderboltDPAda pter!F\t5.0.2\n>!AThunderboltPCIDownAdapter\t2.1.3\n>!AHPM\t3.1.3\n>!A!ILpssI2C! C\t3.0.60\n>!A!ILpssDmac\t3.0.60\n>!A!ILpssI2C\t3.0.60\n>!AThunderboltNHI\t4.5.6 \n|IOThunderbolt!F\t6.6.4\n>!UVHCI\t1.2\n>usb.!UVHCICommon\t1.0\n>!AEffaceableNO R\t1.0\n|IOBufferCopy!C\t1.0.0\n|IONVMe!F\t2.1.0\n>!ABCMWLANCore\t1.0.0\n>IOImag eLoader\t1.0.0\n|IOSerial!F\t11\n|IO80211!FV2\t1200.12.2\n>corecapture\t1.0.4\n> !AEthernetAquantiaAqtion\t1.2.46\n>mDNSOffloadUserClient\t1.0.1b8\n>!UMergeNub\t 900.4.1\n>!UHostMergeProperties\t1.2\n>usb.!UXHCIPCI\t1.2\n>usb.!UXHCI\t1.2\n>us b.!UHostPacketFilter\t1.0\n|IOUSB!F\t900.4.1\n>!AEFINVRAM\t2.1\n>!AEFIRuntime\t2 .1\n>!ASMCRTC\t1.0\n|IOHID!F\t2.0.0\n|IOSMBus!F\t1.1\n$sandbox\t300.0\n@kext.!AM atch\t1.0.0d1\n|IOBufferCopyEngine!F\t1\n>!AKeyStore\t2\n>!UTDM\t439.47.2\n>!AMo bileFileIntegrity\t1.0.5\n|IOUSBMass!SDriver\t140.30.1\n|IOSCSIBlockCommandsDevi ce\t404.30.2\n|IOSCSIArchitectureModel!F\t404.30.2\n>!ACredentialManager\t1.0\n> KernelRelayHost\t1\n>!ASEPManager\t1.0.1\n>IOSlaveProcessor\t1\n>!AFDEKeyStore\t 28.30\n>!AEffaceable!S\t1.0\n|IOTimeSync!F\t653.2\n|IONetworking!F\t3.4\n>DiskIm ages\t480.30.2\n|IO!S!F\t2.1\n|IO!B!F\t6.0.4f1\n|IOUSBHost!F\t1.2\n>usb.!UCommon \t1.0\n>!ABusPower!C\t1.0\n|IOReport!F\t31\n>!AACPIPlatform\t6.1\n>!ASMC\t3.1.9\ n|IOPCI!F\t2.9\n|IOACPI!F\t1.4\n@kec.Libm\t1\n@kec.pthread\t1\n@kec.corecrypto\t 1.0\n",

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

I've also got this video to share (watch the crash occur around the 2 minute mark) My Brand-New iMac Pro Constantly Crashes! - (iMac Pro Network woes on 10.13.3) - YouTube

As a side note, I recently purchased a Sanlink 3 T1, and succeeded in using it to transfer files to and from my server at 400-500 MB/s, which while half the speed of the built-in port, is helping me get work done while I wait for my RMA...

That video shows the same type of crash I've had a couple of times on mine - doing some kind of file transfer over the network creates a long hang where the network becomes unresponsive. I ended up trying to restart in the middle of the issue occurring, and the machine just wouldn't actually restart even after I force quit everything. I had to physically hold down the power button to manually power it off, and then power it back on again. Once it booted up I got a "Your Mac has restarted because of an error" message, but no crash log was generated.

At this stage, I've completely disabled both aspects of Secure Boot - it's set to No Security (no boot OS requirements enforced), and booting from external media is allowed. I also uninstalled a couple of other apps that I thought might have been a possible cause of the crashes, and so far I haven't had another crash or panic.

But I'm also not moving as much data over the network connection now as I was when it was crashing, so it's possible that my crashes were also related to the same thing you're seeing - crashes after a certain amount of data has been moved over the network.

I just had the same thing - after many days without a crash, bam just had one out of the blue. Proper kernel panic, generating a "Your Mac restarted because of an error" message, crash report says BridgeOS is the culprit once again.

This s_u_c_k_s

Yup. Still crashes. I don't know what's causing it, but I do know that Apple are going to take the machine back and look at it. I suspect it's a system issue with the new T2 chip, but I'm no expert.

Crashes happened again today, with just Airport enabled. Sadly, I'm at home all week with a kiddo, so I can't get to the office to check. I can however confirm several crashes have happened...

On my entry level iMacPro i started to get nearly daily kernel panics starting on Jan 22nd. (also Bridge O2 2.01) First two weeks (from Jan 9th to Jan 22nd) i had no problems. All crashes happened while i was away from the iMac. Started to slowly disconnect all devices (Now only a Scanner conneted to a USB3 Port remains). Will turn off PowerNap and disconnect the scanner next).

Am also having strange network hiccups, where it looks like the network connection is lost, but comes back after a couple of minutes.

Since i had no crashes when due to the migration to the new mac a lot more devices were attached to the iMac i suspect, that some system software update introduced the problems.

we also turned of the new boot security via recovery mode/security. also no display sleep mode. no screensaver.

we use storage over 10GbE ethernet server. sonnet thunderbolt 3 to DisplayPort adapter to power two external 4K Computer displays.. one apple tb 3 to 2 adapter with Blackmagic ultra studio 4k to video monitor. focusrite usb audio interface. but it kept crashing after without any external devices, just after leaving it alone for some minutes. now without power nap, its gone.

So here's something new. I have an old game, RollerCoaster Tycoon 3 Pro, from the App Store, that runs fine on iMac 2011 but fails on iMac Pro, about 70% of the time, in the first 60 seconds after launch. The other 30% it runs without failing. I started tracing the crash report back, and I ran into an error some people are having with their iMac Pro SSDs - when you run a disk check on the SSD you get this error:

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Apple can only tell people to reformat, reload and in most cases this solved the problem. Pretty drastic and really bad... I haven't done that yet, but am hoping to find out why iMac Pro users are getting this error and what it is. I mention this because it ties back into disk I/O issues I mentioned earlier... and of course because its another Apple failure with the iMac Pro!

I'm having this issue as well. The first occurrence was after the second-most recent OS update. I disabled power nap and unplugged thunderbolt 2-to-thunderbolt 3 adapters (which I had two plugged in). I just installed the most recent update last night (10.13.3) and when I came into work this morning the error came back again.

So I called Apple Support this morning and the agent had me reset the SMC and NVRAM, booted in safe mode, and ran a hard disk first aid. She provided me a case number in case the issue comes back again.

PS. Computer specs attached...

As far as I know I’ve not had a kernel panic since, but it’s possible I had one the other night. I just can’t remember if I turned it off or not. Either way I’m pretty disappointed by this problem. This is probably my 7th Mac and by far the most expensive Mac I’ve purchased. This has had more kernel panics than all my other macs combined.