"iMac Pro" kernel crash

I have a new iMac Pro 8core 32gb ram 1tb SSD and Pro Vega 64

(attached are a usb hub, usb audio speakers, usb trackball, thunderbolt 3 raid with a thunderbolt 2 raid chained to it via thunderbolt 3 to thunderbolt 2 adapter)


I am looking for input


Within the first 8hours I had two kernel Panics but now seem ok...my iMac shut off and rebooted by itself...both logs have {"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_versio n":"Bridge OS 2.0 .....


To note my Logitech software wasn't recognizing my trackball but it worked ...after crashes I unplugged and replugged the trackball and the software was able to see it.


Should I be concerned?

iMac Pro (2017), macOS High Sierra (10.13.2), null

Posted on Jan 9, 2018 7:25 PM

Reply
Question marked as Top-ranking reply

Posted on Apr 4, 2018 5:12 AM

So my problem has been temporary solved these are the step I took


1) I erased my hard drive and reloaded mac os

2) i disabled sleep and power nap

3) I removed a sonnet chassis on the the thunderbolt drive that contained a PCIe card ( this seemed to be the solution)

It seems when this card was on the thunderbolt connection to the computer at the same time my la cie hard drive was on thunderbolt crashes occurred frequently. they were never daisy chained and had their own port. Disconnecting either seemed to solve random crashes.The card inside was a universal audio card.

the crashes that happened overnight stopped when I disabled power nap.

4) As others thought the crash is related to daisy chaining I disagree as on another thunderbolt port i have several hard drives daisy chained. It seems certain devices are not playing well together on the thunderbolt data pipe wether or not they are on the same port or not.


I will update if I have any more crashes. The problem is now I can't use my Universal audio PCIe card 😟

277 replies

Dec 19, 2018 10:19 AM in response to MFASM

Same problem here. iMac Pro 8core 32gb Vega64.

It happens when I am away from the computer for some time. When I come back, it restarted with this message in the logfile.

Interestingly the timestamp is one hour BEFORE it the last Time Machine backup (maybe only because crash reporter uses a different timezone.) I will disconnect my USB-C LaCie Harddrive and see if it still happens. I have no Thunderbolt Devices. Filevault and Powernap is on.


{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.2 (16P2542)","timestamp":"2018-12-18 08:01:52.55 +0000","incident_id":"2BAEDD31-E93F-4378-8A1C-27E599B2B528"}

{

"build" : "Bridge OS 3.2 (16P2542)",

"product" : "iBridge2,1",

"kernel" : "Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:14 PST 2018; root:xnu-4903.231.4~3\/RELEASE_ARM64_T8010",

"incident" : "2BAEDD31-E93F-4378-8A1C-27E599B2B528",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2018-12-18 08:01:52.51 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff025e1ab14): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 16P2542\nKernel version: Darwin Kernel Version 18.2.0: Mon Nov 12 20:24:14 PST 2018; root:xnu-4903.231.4~3\/RELEASE_ARM64_T8010\nKernelCache UUID: CFF13C89BB4B5456C40AFD66512D8AD8\nKernel UUID: 4BC02A8F-ECD4-37DE-8656-F4FCB742B8C4\niBoot version: iBoot-4513.230.5\nsecure boot?: YES\nx86 EFI Boot State: 0x16\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0xec\nx86 Previous Power Transitions: 0x70707060400\nPCIeUp link state: 0x89271611\nPaniclog version: 11\nKernel slide: 0x000000001f600000\nKernel text base: 0xfffffff026604000\nEpoch Time: sec usec\n Boot : 0x5c18a755 0x0003c761\n Sleep : 0x00000000 0x00000000\n Wake : 0x00000000 0x00000000\n Calendar: 0x5c18a95d 0x0009200f\n\nPanicked task 0xffffffe000195680: 2627 pages, 171 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0004b0f90, backtrace: 0xffffffe0167ab520, tid: 357\n\t\t lr: 0xfffffff026800a08 fp: 0xffffffe0167ab660\n\t\t lr: 0xfffffff0266dd610 fp: 0xffffffe0167ab670\n\t\t lr: 0xfffffff026711ce4 fp: 0xffffffe0167ab9e0\n\t\t lr: 0xfffffff02671205c fp: 0xffffffe0167aba20\n\t\t lr: 0xfffffff026713c94 fp: 0xffffffe0167aba40\n\t\t lr: 0xfffffff025e1ab14 fp: 0xffffffe0167abab0\n\t\t lr: 0xfffffff025e1cf9c fp: 0xffffffe0167abb50\n\t\t lr: 0xfffffff025e1a1d0 fp: 0xffffffe0167abbe0\n\t\t lr: 0xfffffff025dd3ab0 fp: 0xffffffe0167abc10\n\t\t lr: 0xfffffff026b9afa4 fp: 0xffffffe0167abc50\n\t\t lr: 0xfffffff026b9a834 fp: 0xffffffe0167abc90\n\t\t lr: 0xfffffff0266e8614 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x102",

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

"macOSPanicFlags" : "0x0",

"macOSPanicString" : "CPU Machine Check Architecture Error Dump (CPU: UNKNOWN, CPUID: 0x8000000900050654)\r\nCore: 0 \r\n IA32_MC4_STATUS=0xBA00000059000402\r\n IA32_MC4_CTL=0x0\r\n IA32_MC4_MISC=0x0\r\n",

"memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"pageSize":16384,"memoryPressure":false,"memoryPages":{"active":5224,"throttled":0,"fileBacked":9500,"wired":4384,"purgeable":47,"inactive":3080,"free":13422,"speculative":3695}},

"processByPid" : {

(and much more infos…)

Jan 20, 2019 2:55 PM in response to radman

Yes I am using a Universal Arrow Thunderbolt 3 audio interface. Am testing my iMac Pro 9128GB RAM, 10 Cores) now with audio interface unplugged, running the same project to see if I get the kernel panic, finder crashes and computer restart where I have to completely reinstall OS. At least when I reinstall OS, I don't have to install from back up, everything is as is before the crash. Interestingly, seems to only happen when I run projects that use Hollywood Strings Diamond edition. I get the "cannot find XXX samples" message in Play plugin then the finder crashes, then WW3 starts as the atomic bomb goes off and I take a deep breath, get the Apple support number ready, do a fresh install, try again, and wait. I will update to see if it is the Arrow Audio interface but from reading forums here I am guessing it is a T2 bridge issue.

Jan 22, 2019 6:14 AM in response to MFASM

iMac Pro( base model with the 8 core and Vega 56 )

I had a replacement iMac Pro under warranty with similar problem , the first iMac locks up and reboots , and the second IMac crash freezes (only mouse moves). in both cases, this happens mostly during exporting in Final Cut Pro X.


Sat Jan 12 23:19:23 2019


Event: GPU Reset

Date/Time: Sat Jan 12 23:19:23 2019

Application: Final Cut Pro Tr

Path:

Tailspin: /Library/Logs/DiagnosticReports/gpuRestart2019-01-12-231923.tailspin

GPUSubmission Trace ID: 0

OS Version: Mac OS X Version 10.14.2 (Build 18C54)

Graphics Hardware: Radeon Pro Vega 56

Signature: 0


Report Data:


GPU Log Version: 1


Restart Channel: VCELLQ


---THE STATE OF THE DRIVER---


AMDRadeonX5000_AMDVega10GraphicsAccelerator PCIe Device: [243:0:0] State: ENABLED

TotalVideoRAMBytes: 0x00000001ff000000 (8573157376)


[00] Channel: GFX

ConsumedTS = 0x0148bde3, LastSubmitTS = 0x0148bde3

Ring: ENABLED

GPUAddress = 0x000000feff53b000, Size = 0x20000, ReadPtr = 0x0000f180, WritePtr = 0x0000f180

PendingEvent: NO

NumberOfPendingCB = 0


[01] Channel: C0

ConsumedTS = 0x00000000, LastSubmitTS = 0x00000000

Ring: ENABLED

GPUAddress = 0x000000feff5bb000, Size = 0x4000, ReadPtr = 0x00000000, WritePtr = 0x00000000

PendingEvent: NO

NumberOfPendingCB = 0


[02] Channel: C1

ConsumedTS = 0x0003ce7e, LastSubmitTS = 0x0003ce7e

Ring: ENABLED

GPUAddress = 0x000000feff5cb000, Size = 0x4000, ReadPtr = 0x00003f00, WritePtr = 0x00003f00

PendingEvent: NO

NumberOfPendingCB = 0


[03] Channel: C2

ConsumedTS = 0x00000006, LastSubmitTS = 0x00000006

Ring: ENABLED

GPUAddress = 0x000000feff5db000, Size = 0x4000, ReadPtr = 0x00000300, WritePtr = 0x00000300

PendingEvent: NO

NumberOfPendingCB = 0


[05] Channel: sDMA0

ConsumedTS = 0x0019b92d, LastSubmitTS = 0x0019b92d

Ring: ENABLED

GPUAddress = 0x000000feff5fb000, Size = 0x10000, ReadPtr = 0x00009680, WritePtr = 0x00009680

PendingEvent: NO

NumberOfPendingCB = 0


[06] Channel: sDMA1

ConsumedTS = 0x000d0f46, LastSubmitTS = 0x000d0f46

Ring: ENABLED

GPUAddress = 0x000000feff63b000, Size = 0x10000, ReadPtr = 0x00002080, WritePtr = 0x00002080

PendingEvent: NO

NumberOfPendingCB = 0


[07] Channel: UVDDec

ConsumedTS = 0x00078707, LastSubmitTS = 0x00078707

Ring: ENABLED

GPUAddress = 0x000000feff67b000, Size = 0x8000, ReadPtr = 0x000041c0, WritePtr = 0x000041c0

PendingEvent: NO

NumberOfPendingCB = 0


[08] Channel: UVDEnc

ConsumedTS = 0x00000000, LastSubmitTS = 0x00000000

Ring: ENABLED

GPUAddress = 0x000000feff69b000, Size = 0x8000, ReadPtr = 0x00000000, WritePtr = 0x00000000

PendingEvent: NO

NumberOfPendingCB = 0


[09] Channel: UVDEncLLQ

ConsumedTS = 0x00000000, LastSubmitTS = 0x00000000

Ring: ENABLED

GPUAddress = 0x000000feff6bb000, Size = 0x8000, ReadPtr = 0x00000000, WritePtr = 0x00000000

PendingEvent: NO

NumberOfPendingCB = 0


[10] Channel: VCE

ConsumedTS = 0x00000000, LastSubmitTS = 0x00000000

Ring: ENABLED

GPUAddress = 0x000000feff6db000, Size = 0x8000, ReadPtr = 0x00000000, WritePtr = 0x00000000

PendingEvent: NO

NumberOfPendingCB = 0


[11] Channel: VCELLQ

ConsumedTS = 0x00078ef6, LastSubmitTS = 0x00078ef7

Ring: ENABLED

GPUAddress = 0x000000feff6fb000, Size = 0x8000, ReadPtr = 0x00005f60, WritePtr = 0x00005f80

PendingEvent: YES

NumberOfPendingCB = 1, FirstPendingTS = 0x00078ef7, LastPendingTS = 0x00078ef7

FirstPendingCB:

ProcessID = 630, ProcessName = Final Cut Pro Tr, SubmitContext = VideoCtx (0xffffff8056ebc800)

NumberOfWaits = 1

1 - Channel sDMA0, TS = 0x0019b8dd


Jan 23, 2019 12:10 PM in response to dfpsmith

That sounds like rubbish. I have LS and have not had one in OS panick like this. Only on boot up before LS or any apps load. In any case if an OS crashes because you won't let it connect, then I don't want any part of that computer. in your case I see a case of coincidence, or maybe some trigger happy Adobe crap that caused your panic. I have removed all instances of adobe anything from my lanuch daemons and agents and have no issues with adobe connections. that said, Adobe is notorious for being overly invasive with crap running needlessly. Still I'm glad you are having better luck now.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

"iMac Pro" kernel crash

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.