iMac Pro restarting because of a problem?

That's extremely painful and I recognise a lot here. Especially how this issue is being dealt with by Apple.

In my case, my machine is not restarting (happened only once) because I didn't do anything with it, but because I AM doing something with it. It's now clear to me as well that Apple has no correct protocol for dealing with professional users. The kind people at Apple Care always give you the same scripted BS ("this is the first time we heard of this, it shouldn't be allowed to happen to such a beautiful machine", etc, etc) but they really seem te be quite powerless. In my case they even refuse to get back to me for an update on my status, probably because Apple is not giving them any feedback EITHER. I've been dealing with this for almost a month now, without any results or news.

My next step is to contact the supervisor of Apple Care in the Benelux (I'm from Belgium), but reading all of the above, I'm not convinced he will be able to change anything for me.

I mean, right now it seems that the only solution they can think of is shipping another iMac Pro and hoping this unit will work as advertised.

I still think they are STARTING to realise something is seriously wrong with the iMac Pro. They just don't know exactly what, so they don't communicate about it. Scared of this thing getting into the open?

Well, maybe we should get this thing into the open. We payed enough for these machines. If we are not treated as professionals, well, maybe we should let the pro-world know about this.

Right now, until this is resolved somehow, I ADVISE ANY COLLEAGUE OR PRO-USER I KNOW OR ENCOUNTER TO NOT PURCHASE AN IMAC PRO! Right now, this thing is like the gun in a Russian roulette.

So, if anybody at Apple is paying any attention, start treating me like a professional and not like an iPhone user!

Okay I have had my motherboard replace twice and third visit from "Apple Premium Service Partner" to try to get my iMacPro to boot up and after 3 home visits for 3 hours plus I still do not have a working iMac Pro. My computer is dead. The tech worked with online support and he could not get the computer to start up - "it needs firmware update to get it to fire up" and with multiple attempts he could not get it to work. So here I am with very expensive iMac Pro that does not work after two attempts to replace the motherboard and 3 rd attempt to try to get the motherboard to work. So disappointed in Apple.

I'm also sorry to say that Apple has totally FAILED in helping me with this problem. So far I had ZERO respons from the engineering team regarding the tests. And after putting a lot of pressure on the Apple Care team they finally told me that engineering wanted me to discuss it with Pro Applications. And then Pro Applications told Apple Care this was useless because they would not be able to help me anyway.

All I have left is an option for a refund, basically.

What strikes me the most is the shadiness, the way they're refusing to tell me what they have discovered (or not discovered). That makes it clear to me there IS something wrong with this machine and they DON'T WANT ANYBODY TO KNOW ABOUT IT.

The whole thing is bizarre. So many people with variations of the same problem. Some partially sorted with clean installs, others for whom this doesn’t solve anything. Noone who has been contacted by Apple (on this forum) seems to have had a solution or fix, and yet the iMac Pro is still on sale in stores ... no recalls etc. Is this only affecting a relatively small number of people?

I'd had a pretty good run of no kernel panics for a while until today. Now it's Bridge OS 2.3.1, otherwise it all looks the same. I'm hoping the silence means Apple's going to put out a fix any day now?

Not sure I understand your post. Do you mean that all was fine until Bridge OS 2.3.1?

Are you running 10.13.5 (17F77)?

Was there some kind of a supplemental update that triggered the new kernel panics?

How long had your system remained stable?

John

Ocean City, NJ

The last kernel panic log I posted was Bridge OS 2.3, now it's 2.3.1, that's all I was saying. Otherwise, at a brief glance, the kernel panic log looks the same. I'm not sure which update had 2.3.1, and yes I'm on 10.13.5 now. I've gone several weeks without a panic through a combination of always shutting the computer off when I'm done using it and just not using it as much recently. But I've been using it more the last few days and forgot to shut it off, and sometime when I was away from it, it had a kernel panic.

I'm having the exact same issue. iMac Pro 10-Core Vega 64GB RAM. I am also using a thunderbolt to TB3 adapter and interestingly the devices connected to it didn't start back up properly... This is my report...

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3.1 (15P5064)","timestamp":"2018-07-02 10:30:47.36 +0000","incident_id":"D1CEC7D6-E96A-4ABC-873A-9298F32326C2"}

{

"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" : "D1CEC7D6-E96A-4ABC-873A-9298F32326C2",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-07-02 10:30:47.28 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff01baae984): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0x6\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: 0x0000000015200000\nKernel text base: 0xfffffff01c204000\nEpoch Time: sec usec\n Boot : 0x5b31ea6a 0x0008cf17\n Sleep : 0x5b37646c 0x0001c272\n Wake : 0x5b39cbca 0x000669e9\n Calendar: 0x5b39febc 0x00019041\n\nPanicked task 0xffffffe0002a22b0: 2476 pages, 166 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe00066ea50, backtrace: 0xffffffe0167a3530, tid: 349\n\t\t lr: 0xfffffff01c3f96bc fp: 0xffffffe0167a3670\n\t\t lr: 0xfffffff01c2e15f4 fp: 0xffffffe0167a3680\n\t\t lr: 0xfffffff01c313a44 fp: 0xffffffe0167a39f0\n\t\t lr: 0xfffffff01c313dd4 fp: 0xffffffe0167a3a50\n\t\t lr: 0xfffffff01c315914 fp: 0xffffffe0167a3a70\n\t\t lr: 0xfffffff01baae984 fp: 0xffffffe0167a3ae0\n\t\t lr: 0xfffffff01bab0bc8 fp: 0xffffffe0167a3b80\n\t\t lr: 0xfffffff01baae13c fp: 0xffffffe0167a3c00\n\t\t lr: 0xfffffff01ba6daa4 fp: 0xffffffe0167a3c30\n\t\t lr: 0xfffffff01c7710b8 fp: 0xffffffe0167a3c60\n\t\t lr: 0xfffffff01c770a10 fp: 0xffffffe0167a3c90\n\t\t lr: 0xfffffff01c2ec500 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

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

"macOSPanicFlags" : "0x0",

"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",

"memoryStatus" :

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Apr 9 2018 19:30:51 version 9.130.18.10.32.3.0 FWID 01-ea787869

Bluetooth: Version 6.0.6f2, 3 services, 27 devices, 1 incoming serial ports

Network Service: Ethernet, Ethernet, en0

Network Service: Wi-Fi, AirPort, en1

PCI Card: pci17d3,1880, RAID Controller, Thunderbolt@67,0,0

PCI Card: UltraStudio Mini Monitor, Video, Thunderbolt@71,0,0

USB Device: USB 3.0 Bus

USB Device: 4-Port USB 3.0 Hub

USB Device: WorkflowCR2

USB Device: USB DONGLE

USB Device: USB 2.0 BILLBOARD

USB Device: Corsair Gaming M65 Pro RGB Mouse

USB Device: Magic Keyboard with Numeric Keypad

USB Device: 4-Port USB 2.0 Hub

USB Device: USB Audio Device

USB Device: XBOX ACC

USB Device: iBridge Bus

USB Device: Headset

USB Device: iBridge ALS

USB Device: iBridge FaceTime HD Camera (Built-in)

USB Device: iBridge

Thunderbolt Bus: iMac Pro, Apple Inc., 33.2

Thunderbolt Device: ARC8050, Areca, 3, 26.2

Thunderbolt Bus: iMac Pro, Apple Inc., 33.2

Wow, was doing fine there for about a month. No ReStarts.

No today, seemingly for no reason it happened again.

Getting ready to install the latest APPLE-SA-2018-7-9-4 macOS High Sierra 10.13.6 "security update" just released, but I'll wait a day or so just in case it ends up being buggy in and of itself, for good measure.

Was happy.

Now sad.

Here's the beginning of my crash report which I sent into Apple:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version ":"Bridge OS 2.3.1 (15P5064)","timestamp":"2018-07-09 21:26:27.02 +0000","incident_id":"FAC2411E-8E14-42C5-862E-E97CAD421D7F"}

{

"binaryImages" : [

[

"82688f4a-0c28-c175-8176-8ef79472e265",

18446743936270598144,

"U"

],

[

"00000000-0000-0000-0000-000000000000",

0,

"A"

],

[

"a577b904-cd85-3ba8-9b65-4d5a1d11128a",

6442450944,

"S"

]

],

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

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-07-09 21:26:25.26 +0000",

"incident" : "FAC2411E-8E14-42C5-862E-E97CAD421D7F",

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

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

"macOSPanicFlags" : "0x4",

"macOSPanicString" : "Panic(CPU 13, time 249756182142415): NMIPI for unresponsive processor: TLB flush timeout, TLB state:0x0\nRAX: 0x000000000000005f, RBX: 0xffffff8018699cb0, RCX: 0x00000000000005f0, RDX: 0x0000000000100005\nRSP: 0xffffff83c7113d90, RBP: 0xffffff83c7113dc0, RSI: 0x0000000000000000, RDI: 0xffffff80186996a0\nR8: 0xffffffffffffffff, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000000\nR12: 0xffffff805a40f4f0, R13: 0xffffff80567e8d28, R14: 0xffffff80186996a0, R15: 0xffffff8018699cb0\nRFL: 0x0000000000000086, RIP: 0xffffff8017e8e9de, CS: 0x0000000000000008, SS: 0x0000000000000010\nBacktrace (CPU 13), Frame : Return Address\n0xffffff83b2ce8f70 : 0xffffff8017f87314 \n0xffffff83b2ce8fd0 : 0xffffff8017e1f336 \n0xffffff83c7113dc0 : 0xffffff8017e877fb \n0xffffff83c7113e30 : 0xffffff8017e875c6 \n0xffffff83c7113e80 : 0xffffff8017e1f453 \n0xffffff83c7113fa0 : 0xffffff8017e1e3c8 \n\nBSD process name corresponding to current thread: kernel_task\n\nMac OS version:\n17F77\n\nKernel version:\nDarwin Kernel Version 17.6.0: Tue May 8 15:22:16 PDT 2018; root:xnu-4570.61.1~1\/RELEASE_X86_64\nKernel UUID: CC1699EE-71B5-3AF1-AAA3-6DBD16222B92\nKernel slide: 0x0000000017c00000\nKernel text base: 0xffffff8017e00000\n__HIB text base: 0xffffff8017d00000\nSystem model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)\n\nSystem uptime in nanoseconds: 249757497720689\nlast loaded kext at 192840133990187: $TMSafetyNet\t8 (addr 0xffffff7f9bbd5000, size 12288)\nlast unloaded kext at 192839424333168: $TMSafetyNet\t8 (addr 0xffffff7f9bbd5000, size 8192)\nloaded kexts:\n$TMSafetyNet\t8\n>!AUpstreamUserClient\t3.6.5\n@kext.AMDFramebuffer\t1. 6.6\n@kext.AMDRadeonX5000\t1.6.6\n>!AGraphicsDevicePolicy\t3.18.52\n@filesystems .autofs\t3.0\n@AGDCPluginDisplayMetrics\t3.18.52\n>!AHV\t1\n|IOUserEthernet\t1.0 .1\n|IO!BSerialManager\t6.0.6f2\n>AGPM\t110.23.37\n>!

John/newmediagroup - Please don't copy/paste public documents - all of us following this thread get an email with your entire post. Further, what you copy/pasted was only the security update content of the 10.13.6 release which wouldn't typically address any of the issues any here are experiencing... it is the bug fixes / updates that you/we are interested in.

lienffur - Thanks for letting us know that the brightness bug is fixed in 10.13.6. Saw that in the dedicated thread for that issue too. Yay. Small things. ;-) Good news on your external drives spinning down, too! Thanks!

The random shutdowns/restarts happen the majority of the time when exporting from Final Cut Pro. It's literally a crapshoot as to whether or not an export will succeed or cause the iMac Pro to reboot. Just the other day, I had over 10 random shutdowns during exporting in a 24-hour period. At this point, it's really hard to call them "random," because I know that exporting from FCPX is likely going to cause the system to shut down and reboot. Per Twitter, I'm not the only one experiencing this behavior during export.

That's not the impression I got from the Apple Support person I've been in contact with, but I have no idea how much he knows. It would be nice if Apple would make some official statement about this instead of leaving us all to trade rumors.

Been having several kernel panic reboots while exporting Final Cut master files. Considering the premium price for these machines, geared specifically to the professional market, you would think Apple would get off of their dead butts and fix this issue...it's a KNOWN problem. Getting commercials and tv shows to stations is always cutting it close because we never know if we'll be able to export the file.

One question or thought I've been having since these articles popped up is why isn't this getting more traction than it has? I noticed the articles state that this is not endemic or a pervasive issue and it seems to happen in a small fraction of machines. Which I find hard to believe considering it's happened on every single last IMPRO I've had and many others have reported the issue persisting after both machine and motherboard replacements.

This strongly suggests the issues is endemic and pervasive.

Is it just that the issue can be spurious and people haven't reported it? It's easier to put up and shut up.

Is it just getting traction and visibility now because the MBPRO market is so much bigger and more visible?

I have been having chronic kernel panic restarts and dropping of drive connections. Transferring data between drives each on their own port (not daisy chained) no adaptors. Read on the internet that it maybe related to the T2 chip. Super frustrating.