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

Kernel Panic after 10.14.5

natjonesart

natjonesart

macrumors member
Original poster
Jan 22, 2017
94
26
Canada
Hi guys, after upgrading to 144.0.0.0.0 and 10.14.5 I am getting shutdowns and Kernel panics when my cMP is asleep. I find the notice when I return to my computer. Otherwise, I haven't noticed any issues.

Here is the first part of the log. Any idea what might be happening?

Thanks!




*** Panic Report ***
panic(cpu 0 caller 0xffffff7f996d79f0): pmLock: waited too long, held by 12@0xffffff80166dd929
Backtrace (CPU 0), Frame : Return Address
0xffffff8056c53920 : 0xffffff80165aea2d
0xffffff8056c53970 : 0xffffff80166e9e95
0xffffff8056c539b0 : 0xffffff80166db70a
0xffffff8056c53a20 : 0xffffff801655bb40
0xffffff8056c53a40 : 0xffffff80165ae447
0xffffff8056c53b60 : 0xffffff80165ae293
0xffffff8056c53bd0 : 0xffffff7f996d79f0
0xffffff8056c53c10 : 0xffffff80166e7fad
0xffffff8056c53c80 : 0xffffff7f98e9c185
0xffffff8056c53cd0 : 0xffffff7f98ea04bf
0xffffff8056c53cf0 : 0xffffff8016c7c298
0xffffff8056c53d70 : 0xffffff8016caf997
0xffffff8056c53de0 : 0xffffff8016c3f62f
0xffffff8056c53e40 : 0xffffff8016c3c29d
0xffffff8056c53ea0 : 0xffffff8016c38cf3
0xffffff8056c53ef0 : 0xffffff8016c38b90
0xffffff8056c53f30 : 0xffffff8016c56362
0xffffff8056c53f70 : 0xffffff8016c558bc
0xffffff8056c53fa0 : 0xffffff801655b0ce
Kernel Extensions in backtrace:
com.apple.driver.AppleACPIPlatform(6.1)[AE00900F-6E82-31C1-82E7-23005F4219A4]@0xffffff7f98e90000->0xffffff7f98f2bfff
dependency: com.apple.iokit.IOACPIFamily(1.4)[D039545F-9B61-3B0D-8F90-CCCAE5BD7A52]@0xffffff7f979d7000
dependency: com.apple.iokit.IOPCIFamily(2.9)[CC6A465F-5A24-304D-B9DF-8C27819CC214]@0xffffff7f96ead000
dependency: com.apple.driver.AppleSMC(3.1.9)[A20E3E30-0CB9-3E88-9B52-F65FE643BCCF]@0xffffff7f979e0000
com.apple.driver.AppleIntelCPUPowerManagement(220.0)[1556F86B-CAA3-32C6-9426-5D21BC673189]@0xffffff7f996d4000->0xffffff7f996fcfff

BSD process name corresponding to current thread: kernel_task

Mac OS version:
18F132

Kernel version:
Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64
Kernel UUID: 7C8BB636-E593-3CE4-8528-9BD24A688851
Kernel slide: 0x0000000016200000
Kernel text base: 0xffffff8016400000
__HIB text base: 0xffffff8016300000
System model name: MacPro5,1 (Mac-F221BEC8)

System uptime in nanoseconds: 5727025343689
last loaded kext at 4160313848236: com.getdropbox.dropbox.kext 1.9.3 (addr 0xffffff7f99d26000, size 49152)
last unloaded kext at 314086286619: com.apple.driver.AppleUSBMergeNub 900.4.2 (addr 0xffffff7f98dc6000, size 12288)
loaded kexts:
com.getdropbox.dropbox.kext 1.9.3
com.nvidia.CUDA 1.1.0
com.realtek.driver.RtWlanU 1830.10.b2
com.innieteam.Innie 1.0.9
as.vit9696.AppleALC 1.3.2
as.vit9696.WhateverGreen 1.2.3
 
natjonesart said:
Hi guys, after upgrading to 144.0.0.0.0 and 10.14.5 I am getting shutdowns and Kernel panics when my cMP is asleep. I find the notice when I return to my computer. Otherwise, I haven't noticed any issues.

Here is the first part of the log. Any idea what might be happening?

Thanks!




*** Panic Report ***
panic(cpu 0 caller 0xffffff7f996d79f0): pmLock: waited too long, held by 12@0xffffff80166dd929
Backtrace (CPU 0), Frame : Return Address
0xffffff8056c53920 : 0xffffff80165aea2d
0xffffff8056c53970 : 0xffffff80166e9e95
0xffffff8056c539b0 : 0xffffff80166db70a
0xffffff8056c53a20 : 0xffffff801655bb40
0xffffff8056c53a40 : 0xffffff80165ae447
0xffffff8056c53b60 : 0xffffff80165ae293
0xffffff8056c53bd0 : 0xffffff7f996d79f0
0xffffff8056c53c10 : 0xffffff80166e7fad
0xffffff8056c53c80 : 0xffffff7f98e9c185
0xffffff8056c53cd0 : 0xffffff7f98ea04bf
0xffffff8056c53cf0 : 0xffffff8016c7c298
0xffffff8056c53d70 : 0xffffff8016caf997
0xffffff8056c53de0 : 0xffffff8016c3f62f
0xffffff8056c53e40 : 0xffffff8016c3c29d
0xffffff8056c53ea0 : 0xffffff8016c38cf3
0xffffff8056c53ef0 : 0xffffff8016c38b90
0xffffff8056c53f30 : 0xffffff8016c56362
0xffffff8056c53f70 : 0xffffff8016c558bc
0xffffff8056c53fa0 : 0xffffff801655b0ce
Kernel Extensions in backtrace:
com.apple.driver.AppleACPIPlatform(6.1)[AE00900F-6E82-31C1-82E7-23005F4219A4]@0xffffff7f98e90000->0xffffff7f98f2bfff
dependency: com.apple.iokit.IOACPIFamily(1.4)[D039545F-9B61-3B0D-8F90-CCCAE5BD7A52]@0xffffff7f979d7000
dependency: com.apple.iokit.IOPCIFamily(2.9)[CC6A465F-5A24-304D-B9DF-8C27819CC214]@0xffffff7f96ead000
dependency: com.apple.driver.AppleSMC(3.1.9)[A20E3E30-0CB9-3E88-9B52-F65FE643BCCF]@0xffffff7f979e0000
com.apple.driver.AppleIntelCPUPowerManagement(220.0)[1556F86B-CAA3-32C6-9426-5D21BC673189]@0xffffff7f996d4000->0xffffff7f996fcfff

BSD process name corresponding to current thread: kernel_task

Mac OS version:
18F132

Kernel version:
Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64
Kernel UUID: 7C8BB636-E593-3CE4-8528-9BD24A688851
Kernel slide: 0x0000000016200000
Kernel text base: 0xffffff8016400000
__HIB text base: 0xffffff8016300000
System model name: MacPro5,1 (Mac-F221BEC8)

System uptime in nanoseconds: 5727025343689
last loaded kext at 4160313848236: com.getdropbox.dropbox.kext 1.9.3 (addr 0xffffff7f99d26000, size 49152)
last unloaded kext at 314086286619: com.apple.driver.AppleUSBMergeNub 900.4.2 (addr 0xffffff7f98dc6000, size 12288)
loaded kexts:
com.getdropbox.dropbox.kext 1.9.3
com.nvidia.CUDA 1.1.0
com.realtek.driver.RtWlanU 1830.10.b2
com.innieteam.Innie 1.0.9
as.vit9696.AppleALC 1.3.2
as.vit9696.WhateverGreen 1.2.3
Click to expand...
If it’s a MP4,1>5,1 still using the original Nehalem Xeons, you are not alone.

There are one thread about audio stuttering and another about sleep. Seems using the same Xeons used with mid-2010 and mid-2012 Mac Pros solves at least the audio problems.

https://forums.macrumors.com/threads/mac-pro-5-1-kernal-panic-since-10-14-4-update.2176692/

https://forums.macrumors.com/threads/strange-audio-issue-on-mp-4-1-5-1-mojave-10-14-4.2176792/
 
It is a 4,1>5,1 I am using delidded X5675,

note- the upgrade was done years ago with no issues
 
natjonesart said:
It is a 4,1>5,1 I am using delidded X5675,

note- the upgrade was done years ago with no issues
Click to expand...
Apple is not supporting Nehalem/Gainestown Xeons from 10.14.4, but X5675 it’s a Westmere Xeon, so you shouldn’t have any problems.
 
Thanks, Alex.
Yeah, I'm not sure if there is any connection between the updates and the issue, but it did appear immediately after they were done. I want to get ahead of any problems if it is hardware related. I am not educated enough to fully understand the panic report, so I wasn't sure if there was something there that would help diagnose the issue.
 
natjonesart said:
Thanks, Alex.
Yeah, I'm not sure if there is any connection between the updates and the issue, but it did appear immediately after they were done. I want to get ahead of any problems if it is hardware related. I am not educated enough to fully understand the panic report, so I wasn't sure if there was something there that would help diagnose the issue.
Click to expand...
Did you checked your Northbridge heatsink? #15

AppleIntelCPUPowerManagement and NMI errors makes me check the Northbridge heatsink instantly.
 
cheezegrate said:
Hi Alex,

Can you elaborate on this?
Thanks
Click to expand...
Seems that starting with 10.14.4 Apple implemented changes that do not work correctly with those Nehalem/Gainestown Xeon processors from MP4,1. No officially supported Macs have these processors since El Capitan.

The problems are clearly showed with dual CPU trays that have Gainestown Xeons and magically stops when you upgrade to Westmere Xeons. You can read the audio thread that I linked earlier and see exactly what I'm talking about.
 
Ah, apparently I missed that entirely :( That might explain the "sudden" issue with 10.14.4 then. OTOH, this particular "sleep panic" doesn't seem to be remedied by using Westmeres (see X5675 above).

Sigh, hope my beloved cMP will last some longer... somehow.

Cheers
 
cheezegrate said:
Ah, apparently I missed that entirely :( That might explain the "sudden" issue with 10.14.4 then. OTOH, this particular "sleep panic" doesn't seem to be remedied by using Westmeres (see X5675 above).

Sigh, hope my beloved cMP will last some longer... somehow.

Cheers
Click to expand...
Audio problem affected everyone with dual CPU trays with the Gainestown Xeons, sleep problem seems to affect a lot less Mac Pros - we still don't know what causes it.
 
tsialex said:
Audio problem affected everyone with dual CPU trays with the Gainestown Xeons
Click to expand...
Not me (so far), but I'm using an external USB audio interface (for music production!) and haven't yet fully read the thread you mentioned.

Update: I stand corrected. I did indeed suffer from the audio issue but had just increased the buffer size in my DAW from 128 to 1024 samples. I've now upgraded my CPUs to 2x 5675 and I'm able to reduce the buffer size to 64 samples - yeah!

Up next: check whether disabling HT/SMT still causes kernel panics on sleep...

Cheers
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back