From the limited reading I've done in this thread, I have the same issue: Kernel panics where the
*.panic Logs start with these lines:
Code:
panic(cpu 0 caller 0xffffff7f9878c577): "displayModeDidChange failed: set_display_mode_and_vram failed!
"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/GPUDriversAMD/GPUDriversAMD-1.66.42/Common/GLKernel/ATI/Accel/AMDAccelDisplayMachine.cpp:299
As for others, the KP doesn't result in an automatic reboot, but freeze of the UI (including menu bar clock) with spinning beach ball. Connecting with SSH is still possible, and things looks pretty normal when doing that. I usually do a
sudo reboot via SSH when it happens.
I'm using a Mac Pro 6,1 at work for software development (mostly Java-based stuff). Config: quad-core, 16 GiB, 256 GB, D300s, latest macOS (v10.13.5), driving two displays (one Dell 5K and one Dell UHD).
I've experienced two KPs last Friday (2018-06-08) and two today (2018-06-11). Previously the KPs were much less frequent (say every few months) and thus easier to tolerate. But they've been increasing of late – previous two KPs were on 2018-05-22.
This is my
second Mac Pro. My
first one (bought June 2014) was replaced in December 2016 in a somewhat interesting way:
- As it no longer displayed anything (or was it distorted? I forgot) we weren't surprised by the "defective video card" diagnosis, nor by the estimated cost of ~400 bucks, which we were willing to pay (out of warranty).
- What was surprising was that they instead replaced the whole Mac Pro with a brand new one, for free.
Update: Old news, but I assume this explains why I got a free replacement:
Apple Launches Repair Program for Late 2013 Mac Pro Video Issues
Update 2: Because of the next post let me add that my 5K display needs
two DisplayPort (v1.2) connections, while the UHD display needs one. I connected them such that each of them uses a separate TB bus, so all three buses used. No other TB peripherals attached.