"iMac Pro" kernel crash

MFASM wrote:

Should I be concerned?

Yes. I have had countless Macs in my time and if you have a problem in a brand new purchase, take the problem to Apple either at an Apple Store or via telephone support.

If the problem persists or gets worse you have established that it was from the start and puts you in a much stronger position with Apple. If you simply put up with issues you may have them permanently.

Apple generally has good support and you have paid for it. Make sure that they take the responsibility for their products. There have been cases where there were serious flaws in Apple's designs and they chose to not reveal that because of the number of customers affected. Don't be one of the bunnies, always make it Apple's concern, not yours.

The good news, sort of, is that if there is a serious problem and Apple fixes it, it stays fixed. My 2011 27" iMac was one of those and I have been very happy with it after initial serious problems were fixed. I had previous 24" iMacs that also had serious problems and because I was unrelenting Apple finally bit the bullet and replaced them with reliable versions and checked that everything was running OK after the exchange. Never had an issue with them again. It is like my models have had a triple check to make sure they are OK. My two sons had problems with their white 24" iMacs, apparently a known overheating issue. One did nothing, the younger one I took it in hand and made sure it was repaired under warranty and it stayed fixed up until quite recently, so had a good long life. The other son had to eventually toss his out after over a year of putting up with incessant crashes and screen artefacts.

Peter

iMac Pros have USB 3.1 which has ample power to run almost anything, I shouldn't think an external hub would have any effect, but anything is possible with electronics.

One way to find out is detach everything that Apple didn't send you.

If it crashes then it is definitely Apple's doing.

If it comes back and still has the problem I'd escalate it with Apple.

I had an iMac quite a few years ago that underwent two major repairs in a row. I made it very clear that I was not happy that it was obviously a lemon and that I did not want to see that Mac ever again and demanded a replacement, and got it. Again Apple really followed that one up, but I have an inkling that Apple has a play book. They test how far they have to go with you to fix an issue, or whether they can leave you holding the baby. Show them you will not take sh*t and they pull out all stops to fix the problem so they do not have to deal with it again.

As I said after my replacement the iMac was golden, probably my most reliable Mac ever.

Peter

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!

OK you're not going to believe this. Here's the "reason" for my crashes. One of my Thunderbolt channels was configured:

1. Apple Thunderbolt 3 to Thunderbolt 2 Adapter

2. LaCie Little Big Disk Thunderbolt 1 1TB SSD

3. LaCie D2 3TB Thunderbolt 2 HDD

No problem, right? Well up to the point that the Thunderbolt D2 started to break down. We'll never know if it was a crash or a component failure or all this mis-matched Thunderbolt channel stuff, or what's reported earlier in this thread (don't daisy-chain). In any case, by the time we figured it out, my drive was toast. Couldn't bring it back even with DiskWarrior on a native Thunderbolt 2 iMac. Ran for 2 days and just threw Bad Blocks. So I killed it. Now when I took the disk off the iMac Pro and moved it to the iMac to run DiskWarrior (and turned off Power Nap) the reboots completely stopped.

Here's what's bad. Whether the iMac Pro killed my disk or not, we don't know. But what we do know is that no amount of bad disk should cause a "PANIC!!! BAD MAGIC!!!" exception and just roll over. So Apple says they're all over this and we should see some updates coming out shortly. My supporter has been added to the notify queue and she will alert me when the fix goes into a production state. Because I want to daisy-chain like normal.

Good luck, all!

Interesting - I'm still having panics but I'm not daisychaining any drives at all, there's a daisychain connected to 1 of the ports on my iMac Pro but 95% of the time only the 1st device on the chain is actually turned on, and I've definitely had panics when just that device has been on.

Any chance you can let us know your case number with Apple? The guy assigned to my case seems adamant that the next step for me will be a full reformat & reinstall, which I'd prefer not to do if Apple have already recognised a cause

Does anyone on this thread have panic logs, crash logs or similar diagnostic information? Without looking at those, hard to say if these are all the same issue, such as a pagefault at the same address with the same stack trace, or a collection of disparate issues. These crash logs may have clues as to whether any third party drivers are implicated, they may show up in the stack traces.

I think these files get saved to /Library/Logs/DiagnosticReports, or show up in the "send to Apple" dialog box which appears after a restart, from where they can be cut and pasted.

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.

Good question! Thunderbolt 3 to Thunderbolt 2 adaptor initially to transfer files off one of my G-Tech Studio RAIDs, but as the errors continued, I removed all the adaptors. Even with just the NIC connected and nothing else (and copying files off the SSD to the SSD on my server) the same kind of crashes happened.

Nikki.

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

Or flip that on its ear, does it still crash turning off WiFi? I've looked in /Var/Log and there's a boatload of WIFi logs with all kinds of errors... apparently there's a lot of reconnects on my AirPort Extreme, there are messages that are not being authenticated, etc etc. All of them could cause issues between the Ethernet and the WiFi, and a garbled packet that has to retransmit over a link that just went down and now has to shift to a different route... you can guess where that's going...

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...