Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Hotshoe

macrumors member
Oct 28, 2017
81
48
Seattle, WA
Hi choreo,

I experienced the same behavior you're describing with my previous system, where I was left with no choice but to cold boot the system (hung mouse, keyboard, etc). On one occasion I found myself booting into repair and needed to attach a wired keyboard and mouse to cleanly exit repair for the system to boot back to macOS. Not a good feeling.

As previously mentioned, I don't think the issue is specific to Adobe, but, naturally, you're more likely to encounter it in Adobe apps like AI that exercise the GPU function to accelerate rendering.

Sorry to hear 10.15.6 wasn't a silver bullet for the issue. My hunch (and that's all it is), is that the display stream compression that comes along with the W5700X adds an additional vector of complexity for the driver developer and the W5700X is a new GPU architecture w/o the bake time of the Pro Vega II -- so it's going to take some iterations to work out all the kinks. All I can say for certain is that since swapping my W5700X system for a Pro Vega II system I have not experienced a single hang, glitch, or panic after 5 full days working full time at the computer.

I think you'll need to decide if willing to wait it out or not for Apple to address the issue, or go my route.
 
  • Like
Reactions: choreo

choreo

macrumors 6502a
Jan 10, 2008
910
357
Midland, TX
Sorry to hear 10.15.6 wasn't a silver bullet for the issue. My hunch (and that's all it is), is that the display stream compression that comes along with the W5700X adds an additional vector of complexity for the driver developer and the W5700X is a new GPU architecture w/o the bake time of the Pro Vega II -- so it's going to take some iterations to work out all the kinks. All I can say for certain is that since swapping my W5700X system for a Pro Vega II system I have not experienced a single hang, glitch, or panic after 5 full days working full time at the computer.

I think you'll need to decide if willing to wait it out or not for Apple to address the issue, or go my route.

It would really be nice to at least know if it is the W5700X module itself that needs to be replaced at some point, a driver issue or something that has to be fixed in an OS update or on the computer itself. Or is the problem with Adobe software?

I also wonder just how many people are even using the Adobe Suite on the new Mac Pros with the W5700X?
 

Hotshoe

macrumors member
Oct 28, 2017
81
48
Seattle, WA
I tried two separate W5700X systems before throwing in the towel -- both experiencing the same symptoms you're describing. Hence, I think we can safely rule out a bad GPU module. The issue will need to be addressed in software (OS, driver, or firmware). It's anybody's guess how long it will take.

As a last ditch effort on the previous system, I installed Big Sur. I was encourage initially, but it turned out to be only marginally better (major rendering artifacts in AI depending on file, log-in progress bar rendering anomalies, etc.) and still the occasional system sputter, hang, and crash.

I tried to get Apple to send me a Pro Vega II card in exchange for W5700X (where I pay the difference in price) but they weren't willing to work with me on that, so I shipped the system back and ordered another. Total PITA, needless to say but worth it in the end.
 
  • Like
Reactions: choreo

daveedjackson

macrumors 6502
Original poster
Aug 6, 2009
401
262
London
I’ve been having the feezes. At least before the system would shut down. I find it impossible to get out of the freeze now. The mouse for me sometimes comes back for a split second but as soon as it moves freezes again.
 

th0masp

macrumors 6502a
Mar 16, 2015
848
514
You guys should probably try out the Affinity suite to check if you are looking at strictly Adobe issues. Looks like Affinity uses GPU acceleration more than those. Import some of your workfiles and play around?
 

choreo

macrumors 6502a
Jan 10, 2008
910
357
Midland, TX
Still having freezes usually right after I launch AI and now InDesign (3 times yesterday). Usually if they open and let me start work (without freezing in the first 30 seconds), I can usually work inside those documents for 1-2 hours and save without incident. So something is happening upon "launch" it seems.

Now that I am watching closely for it, I just wonder if it may not be related to auto-font-activation? I use Suitcase Fusion to manage my fonts and have their auto-activation plugins installed in all my Adobe apps. In particular, I was watching InDesign launch last night by double-clicking one of my documents and I noticed that some of the text in the document was highlighted when it first appeared on screen and it stayed highlighted as the spinning beachball appeared stuck in place (like it was searching the system for the missing fonts to activate)? [InDesign "highlights" text when a font is missing by default]. After about 30 seconds the computer did the usual auto-shutdown-restart routine.

After I logged back in, I double-clicked the same InDesign document. It opened in Indesign and for a couple seconds the highlighted text in the document appeared just as before and then quickly "resolved" to un-highlighted text as the correct font was found and loaded. I proceeded to work on the document without issues after that.

So, I was wondering if anyone else here having similar freezes/restarts in Adobe might be using Suitcase Fusion?

(Of course, this still may not explain why my machine restarted during sleep last night?)

Also I have not yet documented any freezes/restarts when working in my other apps with all Adobe apps closed.
 
Last edited:

Hotshoe

macrumors member
Oct 28, 2017
81
48
Seattle, WA
Sorry to hear about your woes, but I feel you're playing a game of whack-a-mole trying to diagnose and fix symptoms of a problem rooted in the graphics card / driver.

As you're aware, I experienced the same with a variety of apps that leveraged the GPU for rendering and the problem is most definitely not an Adobe issue. All such issues went away since swapping W5700X for Pro Vega II.

Far be it for me to recommend you do the same (there's a matter of $1,700 involved and sacrifice some nice features of W5700X to do so), but I think you're going to need to wait this one out if sticking with the W5700X.
 
  • Like
Reactions: choreo

flowrider

macrumors 604
Nov 23, 2012
7,317
2,998
So, I was wondering if anyone else here having similar freezes/restarts in Adobe might be using Suitcase Fusion

I used Suitcase years ago. Last used in 2003 while still using OS9 and transitioning to OSX. I decided during the transition that OSX handled fonts better than it had in previous OSs and I no longer needed the app. I still feel that way.

I have been following your tribulations with the NcMP and if it were me, at this point I would uninstall Suitcase and see what happens, can't hurt. You can always reinstall 1387914497.gif

Lou
 
  • Like
Reactions: choreo

bsbeamer

macrumors 601
Sep 19, 2012
4,313
2,713
Make SURE you're using the latest Creative Cloud app and logged into your account. It fixes a ton of issues with Adobe Fonts.


Screen Shot 2020-07-23 at 3.36.53 PM.png
 

bsbeamer

macrumors 601
Sep 19, 2012
4,313
2,713
Not the individual apps themselves, the actual Creative Cloud app needs to be on the latest version. Download and re-install the latest Creative Cloud app. The font-related issues are 100% resolved with the latest Creative Cloud app and are not MP7,1 specific.
 

choreo

macrumors 6502a
Jan 10, 2008
910
357
Midland, TX
Not the individual apps themselves, the actual Creative Cloud app needs to be on the latest version. Download and re-install the latest Creative Cloud app. The font-related issues are 100% resolved with the latest Creative Cloud app and are not MP7,1 specific.
This is what I have been running...

AdobeCC.png
 

eflx

macrumors regular
May 14, 2020
190
207
Interesting ... been following the thread here and while I ditched Adobe CC a while ago in favor of the Affinity apps (I'm a developer, so Affinity Designer & Photo covers my needs) I've always wondered about the W5700X and whether it was the best choice.

I have to admit I've not seen any real stability issues at all with my setup, but I have noticed what seems like sporadic graphic rendering errors sometimes around the corner of windows. Like two Safari windows open for instance, and switching back & fourth between the active and inactive window, every blue moon I spot what looks like a few pixels being rendered incorrectly around the corners of the window etc.

Always wondered if that had anything to do with the W5700X and the DSC (display stream compression). I'm running 2x Pro Display XDRs with the setup. Starting to wish or think I should've gotten the Vega II as it's a solid and proven card from the hardware and driver standpoint. Outside of the return window on mine so not much I can do at this point - but curious regardless.

Anyone switch from the W5700X for similar reason and notice any difference in render quality etc.?
 

choreo

macrumors 6502a
Jan 10, 2008
910
357
Midland, TX
Not sure it this has any meaning, but I special-ordered my Mac Pro with W5700X from B&H in June. It was shipped to me about 10 days later directly from Apple (in Texas). I noticed tonight that B&H no longer has that graphics card listed as a BTO option??
 
  • Like
Reactions: OkiRun

OkiRun

macrumors 65816
Oct 25, 2019
1,005
585
Japan
Not sure it this has any meaning, but I special-ordered my Mac Pro with W5700X from B&H in June. It was shipped to me about 10 days later directly from Apple (in Texas). I noticed tonight that B&H no longer has that graphics card listed as a BTO option??
It's sad to see all your difficulties. The Pro Vega II Duo Card has been trouble free with FCPX and Adobe CC apps along with all other standard music/video applications. The computer doesn't freeze or shut down unexpectedly.
 

choreo

macrumors 6502a
Jan 10, 2008
910
357
Midland, TX
Knocking on wood here, but I have made it 3 days now without any freezes or shutdowns. I did a few things - one of which was uninstall and reinstall all the Suitcase Fusion Adobe App Plugins. Keeping fingers crossed, but first time I have made it 3 days!
 

daveedjackson

macrumors 6502
Original poster
Aug 6, 2009
401
262
London
I've been having several crash issues. Usually when the Mac wakes up after sleeping. Sometimes it can just be moving the mouse across the screen which causes the crash. other times it can be launching an app. I spoke to support last week, we reset a couple of things but that was it. This morning after the system being a asleep, Adobe Premiere caused the crash. Forcing the machine to shut off, and create a panic, and it's laced with references to Premiere.

Not sure what I can do about this. I know as someone how spent over 8k on a system this shouldn't be happening.
will post the panic at the end of this.


Panic(CPU 16, time 33410225492447): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff819159a4e0, spinlock owner: 0xffffff81694dc520, current_thread: 0xffffff81694dc520, spinlock_owner_cpu: 0x10
RAX: 0x00000000000001cc, RBX: 0x0000000000000077, RCX: 0x0000000000000072, RDX: 0x000002d200000000
RSP: 0xffffff92e7c80de0, RBP: 0xffffff92e7c80e20, RSI: 0x0000000000000077, RDI: 0xffffff8003aa1780
R8: 0x0000000000000001, R9: 0x00000150c5001800, R10: 0x00001e62ec872dc7, R11: 0xffffff8003a5cdc0
R12: 0x000002d2270bc1a4, R13: 0xffffff81694dc520, R14: 0xffffff8003aa1780, R15: 0xffffff8003aa1780
RFL: 0x0000000000000093, RIP: 0xffffff800312eb36, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 16), Frame : Return Address
0xffffff92e7c80c90 : 0xffffff8003245dfb
0xffffff92e7c80ce0 : 0xffffff80030c0d47
0xffffff92e7c80e20 : 0xffffff800313f2eb
0xffffff92e7c80e50 : 0xffffff80031340be
0xffffff92e7c80e90 : 0xffffff8003164ffe
0xffffff92e7c80f20 : 0xffffff80032338e3
0xffffff92e7c80f60 : 0xffffff800324e663
0xffffff92e7c80f80 : 0xffffff8003245dfb
0xffffff92e7c80fd0 : 0xffffff80030c0bed
0xffffffd301f23e00 : 0xffffff8003620c79
0xffffffd301f23e40 : 0xffffff7f8593e725
0xffffffd301f23e70 : 0xffffff7f8593e615
0xffffffd301f23eb0 : 0xffffff7f8593e322
0xffffffd301f23f20 : 0xffffff8003621162
0xffffffd301f23f40 : 0xffffff8003784c37
0xffffffd301f23fa0 : 0xffffff80030c1206
Kernel Extensions in backtrace:
com.apple.kec.pthread(1.0)[C9486906-995B-3F43-A336-95AAF9FA5BA1]@0xffffff7f8593b000->0xffffff7f85944fff

BSD process name corresponding to current thread: Adobe Premiere P
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
19G73

Kernel version:
Darwin Kernel Version 19.6.0: Sun Jul 5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64
Kernel UUID: 783946EA-6F11-3647-BF90-787AEA14B954
Kernel slide: 0x0000000002e00000
Kernel text base: 0xffffff8003000000
__HIB text base: 0xffffff8002f00000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO

System uptime in nanoseconds: 33410225528949
last loaded kext at 28634028265013: >!UAudio 323.4 (addr 0xffffff7f8a178000, size 434176)
last unloaded kext at 27515425823257: |IOSCSIParallel!F 3.0.0 (addr 0xffffff7f8711a000, size 65536)
loaded kexts:

[removed list of drivers]

mp_kdp_enter() timed-out on cpu 23, NMI-ing
Panic(CPU 0, time 33410725588060): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff819159a4e0, spinlock owner: 0xffffff81694dc520, current_thread: 0xffffff815ea85000, spinlock_owner_cpu: 0x10
RAX: 0x0000000000000017, RBX: 0x0000000000000003, RCX: 0x0000000000000000, RDX: 0x0000000000000000
RSP: 0xffffff92c72b29d0, RBP: 0xffffff92c72b2a10, RSI: 0x0000000000000003, RDI: 0x0000000000000006
R8: 0xffffff815ea85000, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000003, R13: 0x0000000000000006, R14: 0x0000000000000000, R15: 0x0000000000000001
RFL: 0x0000000000000086, RIP: 0xffffff800311a20d, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 0), Frame : Return Address
0xffffff92c72b2880 : 0xffffff8003245dfb
0xffffff92c72b28d0 : 0xffffff80030c0d47
0xffffff92c72b2a10 : 0xffffff8003254a75
0xffffff92c72b2a50 : 0xffffff80032465fe
0xffffff92c72b2aa0 : 0xffffff80030c0a40
0xffffff92c72b2ac0 : 0xffffff8003119d27
0xffffff92c72b2bc0 : 0xffffff800311a117
0xffffff92c72b2c10 : 0xffffff80038c1abc
0xffffff92c72b2c80 : 0xffffff800312ebd8
0xffffff92c72b2cf0 : 0xffffff8003139fb7
0xffffff92c72b2d30 : 0xffffff800316ba27
0xffffff92c72b2d70 : 0xffffff800316e538
0xffffff92c72b2db0 : 0xffffff800315cdb4
0xffffff92c72b2dd0 : 0xffffff800315ccf4
0xffffff92c72b2df0 : 0xffffff800315b827
0xffffff92c72b2e60 : 0xffffff800316545c
0xffffff92c72b2f20 : 0xffffff8003233807
0xffffff92c72b2f60 : 0xffffff800324e663
0xffffff92c72b2f80 : 0xffffff8003245dfb
0xffffff92c72b2fd0 : 0xffffff80030c0bed
0xffffff92e7e53f40 : 0xffffff800313f7a7
0xffffff92e7e53f80 : 0xffffff800313f968
0xffffff92e7e53fa0 : 0xffffff80030c013e

BSD process name corresponding to current thread: kernel_task
Panic(CPU 1, time 33410725588232): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff819159a4e0, spinlock owner: 0xffffff81694dc520, current_thread: 0xffffff816306c520, spinlock_owner_cpu: 0x10
RAX: 0x0000000000000017, RBX: 0x0000000000000003, RCX: 0x0000000000000001, RDX: 0x0000000000000000
RSP: 0xffffff92feea3ad0, RBP: 0xffffff92feea3b10, RSI: 0x0000000000000003, RDI: 0x0000000000000006
R8: 0xffffff816306c520, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000003, R13: 0x0000000000000006, R14: 0x0000000000000000, R15: 0x0000000000000001
RFL: 0x0000000000000086, RIP: 0xffffff800311a20d, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 1), Frame : Return Address
0xffffff92e7ca0f80 : 0xffffff8003245dfb
0xffffff92e7ca0fd0 : 0xffffff80030c0bed
0xffffff92feea3b10 : 0xffffff8003254a75
0xffffff92feea3b50 : 0xffffff80032465fe
0xffffff92feea3ba0 : 0xffffff80030c0a40
0xffffff92feea3bc0 : 0xffffff8003119d27
0xffffff92feea3cc0 : 0xffffff800311a117
0xffffff92feea3d10 : 0xffffff80038c1abc
0xffffff92feea3d80 : 0xffffff800312ebd8
0xffffff92feea3df0 : 0xffffff800313b668
0xffffff92feea3e60 : 0xffffff800313acf6
0xffffff92feea3eb0 : 0xffffff80030c0d04
0xffffff92feea3fa0 : 0xffffff80030c0133

BSD process name corresponding to current thread: kernel_task
Panic(CPU 24, time 33410725589006): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff819159a4e0, spinlock owner: 0xffffff81694dc520, current_thread: 0xffffff8167da4a40, spinlock_owner_cpu: 0x10
RAX: 0x0000000000000017, RBX: 0x0000000000000003, RCX: 0x0000000000000018, RDX: 0x0000000000000000
RSP: 0xffffff92e7533a50, RBP: 0xffffff92e7533a90, RSI: 0x0000000000000003, RDI: 0x0000000000000006
R8: 0xffffff8167da4a40, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000003, R13: 0x0000000000000006, R14: 0x0000000000000000, R15: 0x0000000000000001
RFL: 0x0000000000000086, RIP: 0xffffff800311a20d, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 24), Frame : Return Address
0xffffff92e7c90f80 : 0xffffff8003245dfb
0xffffff92e7c90fd0 : 0xffffff80030c0bed
0xffffff92e7533a90 : 0xffffff8003254a75
0xffffff92e7533ad0 : 0xffffff80032465fe
0xffffff92e7533b20 : 0xffffff80030c0a40
0xffffff92e7533b40 : 0xffffff8003119d27
0xffffff92e7533c40 : 0xffffff800311a117
0xffffff92e7533c90 : 0xffffff80038c1abc
0xffffff92e7533d00 : 0xffffff800312ebd8
0xffffff92e7533d70 : 0xffffff800313b668
0xffffff92e7533de0 : 0xffffff800313acf6
0xffffff92e7533e30 : 0xffffff80030fc1e6
0xffffff92e7533e70 : 0xffffff800310dc7e
0xffffff92e7533f00 : 0xffffff800322c065
0xffffff92e7533fa0 : 0xffffff80030c1226

BSD process name corresponding to current thread: coreaudiod
Panic(CPU 12, time 33410725588176): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff819159a4e0, spinlock owner: 0xffffff81694dc520, current_thread: 0xffffff8167da4000, spinlock_owner_cpu: 0x10
RAX: 0xffffff8167da4a40, RBX: 0xffffff8167da4a90, RCX: 0x000000000000020c, RDX: 0x000002d200000000
RSP: 0xffffffd313a4bba0, RBP: 0xffffffd313a4bbe0, RSI: 0xffffff8167da4000, RDI: 0xffffff8167da4a90
R8: 0xffffffd313a4bd84, R9: 0x0000000000000000, R10: 0xffffffd313a4bdc0, R11: 0xffffffd313a4bdc0
R12: 0xffffff8167da4000, R13: 0x0000000000000000, R14: 0x000002d2e54f421e, R15: 0xffffff8167da4a40
RFL: 0x0000000000000087, RIP: 0xffffff800312afad, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 12), Frame : Return Address
0xffffff92e7c78f80 : 0xffffff8003245dfb
0xffffff92e7c78fd0 : 0xffffff80030c0bed
0xffffffd313a4bbe0 : 0xffffff800312b154
0xffffffd313a4bc10 : 0xffffff800323b9dd
0xffffffd313a4bc50 : 0xffffff800316ad30
0xffffffd313a4bcd0 : 0xffffff800316bb38
0xffffffd313a4bd60 : 0xffffff80030fbb1e
0xffffffd313a4bdb0 : 0xffffff80030fb881
0xffffffd313a4be10 : 0xffffff80030f6e60
0xffffffd313a4be70 : 0xffffff800310db22
0xffffffd313a4bf00 : 0xffffff800322c065
0xffffffd313a4bfa0 : 0xffffff80030c1226

BSD process name corresponding to current thread: Adobe Premiere P
Panic(CPU 20, time 33410725588988): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff819159a4e0, spinlock owner: 0xffffff81694dc520, current_thread: 0xffffff816d224a40, spinlock_owner_cpu: 0x10
RAX: 0x0000000000000017, RBX: 0x0000000000000003, RCX: 0x0000000000000014, RDX: 0x0000000000000000
RSP: 0xffffff92fcd73a60, RBP: 0xffffff92fcd73aa0, RSI: 0x0000000000000003, RDI: 0x0000000000000006
R8: 0xffffff816d224a40, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000003, R13: 0x0000000000000006, R14: 0x0000000000000000, R15: 0x0000000000000001
RFL: 0x0000000000000086, RIP: 0xffffff800311a20d, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 20), Frame : Return Address
0xffffff92e7c88f80 : 0xffffff8003245dfb
0xffffff92e7c88fd0 : 0xffffff80030c0bed
0xffffff92fcd73aa0 : 0xffffff8003254a75
0xffffff92fcd73ae0 : 0xffffff80032465fe
0xffffff92fcd73b30 : 0xffffff80030c0a40
0xffffff92fcd73b50 : 0xffffff8003119d27
0xffffff92fcd73c50 : 0xffffff800311a117
0xffffff92fcd73ca0 : 0xffffff80038c1abc
0xffffff92fcd73d10 : 0xffffff800312ebd8
0xffffff92fcd73d80 : 0xffffff800313b668
0xffffff92fcd73df0 : 0xffffff800313acf6
0xffffff92fcd73e40 : 0xffffff7f8593d7cd
0xffffff92fcd73e90 : 0xffffff7f8593f7fb
0xffffff92fcd73f00 : 0xffffff800362122c
0xffffff92fcd73f40 : 0xffffff8003784c37
0xffffff92fcd73fa0 : 0xffffff80030c1206
Kernel Extensions in backtrace:
com.apple.kec.pthread(1.0)[C9486906-995B-3F43-A336-95AAF9FA5BA1]@0xffffff7f8593b000->0xffffff7f85944fff

BSD process name corresponding to current thread: Adobe Premiere P
Panic(CPU 7, time 33410725588372): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff819159a4e0, spinlock owner: 0xffffff81694dc520, current_thread: 0xffffff8160cb1520, spinlock_owner_cpu: 0x10
RAX: 0x0000000000000017, RBX: 0x0000000000000003, RCX: 0x0000000000000007, RDX: 0x0000000000000000
RSP: 0xffffffd313c9bad0, RBP: 0xffffffd313c9bb10, RSI: 0x0000000000000003, RDI: 0x0000000000000006
R8: 0xffffff8160cb1520, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000003, R13: 0x0000000000000006, R14: 0x0000000000000000, R15: 0x0000000000000001
RFL: 0x0000000000000086, RIP: 0xffffff800311a20d, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 7), Frame : Return Address
0xffffff92e7cacf80 : 0xffffff8003245dfb
0xffffff92e7cacfd0 : 0xffffff80030c0bed
0xffffffd313c9bb10 : 0xffffff8003254a75
0xffffffd313c9bb50 : 0xffffff80032465fe
0xffffffd313c9bba0 : 0xffffff80030c0a40
0xffffffd313c9bbc0 : 0xffffff8003119d27
0xffffffd313c9bcc0 : 0xffffff800311a117
0xffffffd313c9bd10 : 0xffffff80038c1abc
0xffffffd313c9bd80 : 0xffffff800312ebd8
0xffffffd313c9bdf0 : 0xffffff800313b668
0xffffffd313c9be60 : 0xffffff800313acf6
0xffffffd313c9beb0 : 0xffffff80030c0d04
0xffffffd313c9bfa0 : 0xffffff80030c0133

BSD process name corresponding to current thread: Adobe Premiere P
Panic(CPU 29, time 33410725588879): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff819159a4e0, spinlock owner: 0xffffff81694dc520, current_thread: 0xffffff815fbcaa40, spinlock_owner_cpu: 0x10
RAX: 0x0000000000000017, RBX: 0x0000000000000003, RCX: 0x000000000000001d, RDX: 0x0000000000000000
RSP: 0xffffffd3139e3aa0, RBP: 0xffffffd3139e3ae0, RSI: 0x0000000000000003, RDI: 0x0000000000000006
R8: 0xffffff815fbcaa40, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000003, R13: 0x0000000000000006, R14: 0x0000000000000000, R15: 0x0000000000000001
RFL: 0x0000000000000086, RIP: 0xffffff800311a20d, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 29), Frame : Return Address
0xffffff92e7cd8f80 : 0xffffff8003245dfb
0xffffff92e7cd8fd0 : 0xffffff80030c0bed
0xffffffd3139e3ae0 : 0xffffff8003254a75
0xffffffd3139e3b20 : 0xffffff80032465fe
0xffffffd3139e3b70 : 0xffffff80030c0a40
0xffffffd3139e3b90 : 0xffffff8003119d27
0xffffffd3139e3c90 : 0xffffff800311a117
0xffffffd3139e3ce0 : 0xffffff80038c1abc
0xffffffd3139e3d50 : 0xffffff800312ebd8
0xffffffd3139e3dc0 : 0xffffff800313b668
0xffffffd3139e3e30 : 0xffffff800313acf6
0xffffffd3139e3e80 : 0xffffff800323e969
0xffffffd3139e3ec0 : 0xffffff800323e1cb
0xffffffd3139e3ef0 : 0xffffff7f83bd850c
0xffffffd3139e3f30 : 0xffffff800382be1e
0xffffffd3139e3f70 : 0xffffff800382b416
0xffffffd3139e3fa0 : 0xffffff80030c013e
Kernel Extensions in backtrace:
com.apple.driver.usb.AppleUSBCommon(1.0)[FD7E16C9-CC6D-3595-8E03-291F9DA0397E]@0xffffff7f83bd6000->0xffffff7f83be3fff

BSD process name corresponding to current thread: kernel_task
Panic(CPU 31, time 33410725589213): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff819159a4e0, spinlock owner: 0xffffff81694dc520, current_thread: 0xffffff8165809520, spinlock_owner_cpu: 0x10
RAX: 0x0000000000000017, RBX: 0x0000000000000003, RCX: 0x000000000000001f, RDX: 0x0000000000000000
RSP: 0xffffff92fc8e3a50, RBP: 0xffffff92fc8e3a90, RSI: 0x0000000000000003, RDI: 0x0000000000000006
R8: 0xffffff8165809520, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x0000000000000003, R13: 0x0000000000000006, R14: 0x0000000000000000, R15: 0x0000000000000001
RFL: 0x0000000000000086, RIP: 0xffffff800311a20d, CS: 0x0000000000000008, SS: 0x0000000000000010
Backtrace (CPU 31), Frame : Return Address
0xffffff92e7cdcf80 : 0xffffff8003245dfb
0xffffff92e7cdcfd0 : 0xffffff80030c0bed
0xffffff92fc8e3a90 : 0xffffff8003254a75
0xffffff92fc8e3ad0 : 0xffffff80032465fe
0xffffff92fc8e3b20 : 0xffffff80030c0a40
0xffffff92fc8e3b40 : 0xffffff8003119d27
0xffffff92fc8e3c40 : 0xffffff800311a117
0xffffff92fc8e3c90 : 0xffffff80038c1abc
0xffffff92fc8e3d00 : 0xffffff800312ebd8
0xffffff92fc8e3d70 : 0xffffff800313b668
0xffffff92fc8e3de0 : 0xffffff800313acf6
0xffffff92fc8e3e30 : 0xffffff80030fc1e6
0xffffff92fc8e3e70 : 0xffffff800310dc7e
0xffffff92fc8e3f00 : 0xffffff800322c065
0xffffff92fc8e3fa0 : 0xffffff80030c1226

BSD process name corresponding to current thread: WindowServer
mp_kdp_enter() NMI pending on cpus: 4 5 6 8 9 10 11 13 14 16 17 18 19 21 22 27 28 30
mp_kdp_enter() timed-out during locked wait after NMI;expected 32 acks but received 15 after 23940704 loops in 1596000000 ticks
panic(cpu 23 caller 0xffffff800323baa0): "Spinlock acquisition timed out: lock=0xffffff819159a4e0, lock owner thread=0xffffff81694dc520, current_thread: 0xffffff81680d0a40, lock owner active on CPU 0x10, current owner: 0xffffff81694dc520, time: 33410225556053"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.141.1/osfmk/i386/locks_i386.c:501
Backtrace (CPU 23), Frame : Return Address
0xffffff92fd823bc0 : 0xffffff800311a65d
0xffffff92fd823c10 : 0xffffff8003254a75
0xffffff92fd823c50 : 0xffffff80032465fe
0xffffff92fd823ca0 : 0xffffff80030c0a40
0xffffff92fd823cc0 : 0xffffff8003119d27
0xffffff92fd823dc0 : 0xffffff800311a117
0xffffff92fd823e10 : 0xffffff80038c1abc
0xffffff92fd823e80 : 0xffffff800323baa0
0xffffff92fd823ec0 : 0xffffff7f8593cd21
0xffffff92fd823f20 : 0xffffff8003621122
0xffffff92fd823f40 : 0xffffff8003784c37
0xffffff92fd823fa0 : 0xffffff80030c1206
Kernel Extensions in backtrace:
com.apple.kec.pthread(1.0)[C9486906-995B-3F43-A336-95AAF9FA5BA1]@0xffffff7f8593b000->0xffffff7f85944fff

BSD process name corresponding to current thread: Adobe Premiere P
 

OkiRun

macrumors 65816
Oct 25, 2019
1,005
585
Japan
Saw the 7,1 editor working in PP. Asked them to make a screen shot of the GPU usage for a minute. Here it is.
Looks like the Pro Vega II Duo doesn't really divide up the work evenly from a visual perspective. No idea about the technical argument.

Screen Shot 2020-07-28 at 9.44.43 PM.png
 

LeonPro

macrumors 6502a
Jul 23, 2002
933
510
But we already know that PP or After Effects doesn't make full use of the GPU. Which is why I only took one Vega II which even then doesn't make use of it fully. At this point I'd take more memory, but with my workflow I can't max out more than 60GB of RAM with both PP and AE already open. So for me 96GB Apple RAM at all 12 slots is just for buffer.
 

daveedjackson

macrumors 6502
Original poster
Aug 6, 2009
401
262
London
I guess what would be handy is if all 7,1 users owners of adobe can see if they can replicate it: I have narrowed it down to only crashing after the system has been asleep. Then it can take anywhere for a couple of seconds to minutes whilst using any adobe cc app to crash it.
 

OkiRun

macrumors 65816
Oct 25, 2019
1,005
585
Japan
But we already know that PP or After Effects doesn't make full use of the GPU. Which is why I only took one Vega II which even then doesn't make use of it fully. At this point I'd take more memory, but with my workflow I can't max out more than 60GB of RAM with both PP and AE already open. So for me 96GB Apple RAM at all 12 slots is just for buffer.
I posted another thread. One film in FCPX can easily reach from 110 to 130 gb RAM for the projects we do and easily higher - so I think it is definitely related to the workflow that you can expect to be performing. Yes - it is a great idea to have the RAM buffer for the future.
1595957307757.png
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.