MP 1,1-5,1 Mac Pro 5,1 kernal panic on sleep since 10.14.4, 10.14.5, 10.14.6 updates

[gadgetfreak98]

I have experienced this issue. You can see in my (still to be re-updated) signature my setup. Of note, though, is I had to do a clean install after my backplane failed and I had moved my primary hard drive to my Mac Mini. So within the last week, I got this machine started from scratch. And all seems to be well, except for the sleep issue and kernel panics. Today I turned sleep to "never" and the machine has hummed along just fine.

I'm on 10.14.6 with all available updates loaded. I do not have the Northbridge flag in the kernel panic.

 

[MIKX]

I have experienced this issue. You can see in my (still to be re-updated) signature my setup. Of note, though, is I had to do a clean install after my backplane failed and I had moved my primary hard drive to my Mac Mini. So within the last week, I got this machine started from scratch. And all seems to be well, except for the sleep issue and kernel panics. Today I turned sleep to "never" and the machine has hummed along just fine.

I'm on 10.14.6 with all available updates loaded. I do not have the Northbridge flag in the kernel panic.

Which Mojave Build No. do you have installed ?

You probably are aware of how to find the build No. but just in case . . .

There were so many builds released shortly after the first 10.14.6 release.

Before the last Security update my Build No. was 18G103.

I did a clean install of Build 18G103 to a spare APFS formatted SSD with NO 3rd party apps,

I cloned this drive to ANOTHER SSD formatted to HFS+.

I then shut down, removed the power cord for 15 mins.
Re-seated all my RAM & GPU did the THREE CHIME NVRAM reset.

Re-booted to the HFS+ SSD and let the cMP sleep for an hour .. . several times.

Woke from sleep without issue every time.

I have since cloned this install to a HFS+ Samsung 970 EVO.

I have had zero sleep or other issues since.

NOTE : The last Mojave Security Update changed my Build No. to 18G1012.


No idea if all of this negates the sleep - kernel panics but my cMP seems to have escaped these problems and I do have put "drives to sleep whenever possible" set.

Hope this is informative.

 

[MacGarage]

I am still having the sleep issues as well with 10.14.16 build (18G2022). Over time, I have done all of the resets, etc. minus the reformat and reinstall.

There was an update that worked but the last several OS updates and security updates brought back the issue.

 

[startergo]

I am still having the sleep issues as well with 10.14.16 build (18G2022). Over time, I have done all of the resets, etc. minus the reformat and reinstall.

There was an update that worked but the last several OS updates and security updates brought back the issue.

The thing is this might be related to a failing PSU as well. Especially if it does not fail consistently with the same software across similar hardware.

 

[gadgetfreak98]

Which Mojave Build No. do you have installed ?

I too am on 18G2022. This is using a brand new out of the box Radeon 580 by the way.

 

[haralds]

I noticed these always indicating failure in disk drivers in the panic log. Just ran into the same on my older Mac mini running as server using Sierra!

It looks like it might actually be caused by DropBox. I turned it off and have been ok since. It's only been three days, but looking ok so far.

 

[tommy chen]

yes, dropbox and macOS server can not together

 

[MacGarage]

I noticed these always indicating failure in disk drivers in the panic log. Just ran into the same on my older Mac mini running as server using Sierra!

It looks like it might actually be caused by DropBox. I turned it off and have been ok since. It's only been three days, but looking ok so far.

Thanks for the heads-up about Dropbox. I get the pmLock panic.

I quit Dropbox and removed it from the start-up items. After two days, no panics.

 

[MacGarage]

Thanks for the heads-up about Dropbox. I get the pmLock panic.

I quit Dropbox and removed it from the start-up items. After two days, no panics.

I spoke too soon!

Thu Jan 16 00:20:49 2020

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f9f2419f0): pmLock: waited too long, held by 12@0xffffff801c2df9b9

 

[tsialex]

I spoke too soon!

Thu Jan 16 00:20:49 2020

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f9f2419f0): pmLock: waited too long, held by 12@0xffffff801c2df9b9

Maybe it will be easier to find what is going on with the kernel panic if you enable debug and print the symbols with boot-args options below:

To enable:

sudo nvram boot-args="debug=0x14e keepsyms=1"

To disable:

sudo nvram boot-args=""

Post the full KP here for us to take a look.

 

[iChan]

Hello all, I was dealing with Kernal Panics since I got my 4,1 Mac Pro in early 2019. My model had dual 2.26Ghz E5520s and the bahaviour of my machine echoed the same problems that have been outlined in this thread and others. Mainly with sleep, but also the audio crackling.

I tried purchasing two X5680s from AliExpress on two occassions, but both time they got lost in the mail so i bit the bullet and bought and bought a couple of them on Ebay instead.

The delidding process was super simple and installing them was really easy too.

I'd like to report that not only is my system way, way, way faster in general tasks but I'm no longer getting kernel panics when sleeping and restarting. It's basically working flawlessly. A difference I have noticed is that the fans go full blast for a couple of seconds when I wake from sleep, but I kind of like that, because before, I never heard the fans kick in at all.


I will do further testing as I've only had the CPUs installed for an hour now, but 10+ sleep/wake cycles and I've yet to experience any kernel panics. Next I'll test the audio. I have high hopes.

 

[romaric17]

Replacing the dual E5520s solved the KP issue for me as well.

 

[Taipan]

Add me to the list of people with the problem. Mac Pro 4,1 > 5,1, X5570 CPUs

I have thought about upgrading the CPUs due to the audio and sleep issues, but I'm somewhat hesitant, since the machine is more or less on its last leg, not being able to run Catalina...

Question: Should I expect fan noise to increase if I upgrade to X5690s?

 

[Taipan]

So, I did it and upgraded to X5690s. Sleep does work now, but the power LED stays off during sleep. Is that something I should worry about?
Edit: It was my own fault. During troubleshooting the sleep issues I had activated hibernating, apparently the LED doesn‘t pulsate during hibernating.

 

[CrispyDog]

Hello all, I was dealing with Kernal Panics since I got my 4,1 Mac Pro in early 2019. My model had dual 2.26Ghz E5520s and the bahaviour of my machine echoed the same problems that have been outlined in this thread and others. Mainly with sleep, but also the audio crackling.

I tried purchasing two X5680s from AliExpress on two occassions, but both time they got lost in the mail so i bit the bullet and bought and bought a couple of them on Ebay instead.

The delidding process was super simple and installing them was really easy too.

I'd like to report that not only is my system way, way, way faster in general tasks but I'm no longer getting kernel panics when sleeping and restarting. It's basically working flawlessly. A difference I have noticed is that the fans go full blast for a couple of seconds when I wake from sleep, but I kind of like that, because before, I never heard the fans kick in at all.


I will do further testing as I've only had the CPUs installed for an hour now, but 10+ sleep/wake cycles and I've yet to experience any kernel panics. Next I'll test the audio. I have high hopes.

Hi @iChan, is your computer continuing to operate as intended after changing CPUs? I have tried everything under the sun short of buying new CPUs.... Also running E5520s... I need to delid my PC's cpu as well so i could do all 3 at one time...

Thanks!

 

[Itconnects]

I'm having a clicking noise and a fan starting up and stopping over and over again during sleep mode, anyone run into this issue?

 

[Macschrauber]

Just in process building up a 4.1 Dual, still on his original 2.26 processors (5680s are in the mail)

GPU is a GTX680 with Mac Firmware, no sata drives in at the moment.

Built a clean 144 Firmware from MP41.0081.B07
Put in 6x8GB 10600R
Put in a Crucial P1 NVMe with 10.14.6 18G5033
Ran Memtest
Box restarted after a few minutes (forgot to switch off Energy Saver)
Got kernel panic "pmLock: waited too long!"

Manually put box to sleep, Power button snoring, but fans were alive, box is not at deep sleep, got not up as well, needed hard shutdown by a long press of the power button.

Did SMC Reset (Power Cord off) and triple nvram reset immediately.

Box did deep Sleep and woke up correctly

hope that helps

 

[Pete_202]

I have a MP 4,1 flashed to 5,1 2x2.26 processors (5520's) and a flashed video card. I'm also getting the sleep/wakeup issues with Mojave.

Sorry to ask a stupid question but is a triple NVRAM reset where you carry on holding the keys down after the second startup chime to get a third?

 

[tsialex]

I have a MP 4,1 flashed to 5,1 2x2.26 processors (5520's) and a flashed video card. I'm also getting the sleep/wakeup issues with Mojave.

Sorry to ask a stupid question but is a triple NVRAM reset where you carry on holding the keys down after the second startup chime to get a third?

Yes, you keep CMD-Option-P-R continuously pressed until you hear the fourth chime.

 

[Pete_202]

Great! Many thanks for the reply. I will put Mojave back on (currently on High Sierra) and give this a try.

 

[PlatypusRex]

Just as an idea: Since there are people who use even AMD cpus for their hackintoshes (and I would expect an AMD cpu to be more problematic than just our old mp4,1 ones) is there any hope to solve the problem just by a modified kernel instead of upgrading the cpus? Does there maybe in this context (AMD hackintoshes) even already some patch exist (like maybe they patch 50 things, and we would require only one or two of those 50).

I fully admit that I have no idea what would have to be done, or if it's even possible at all. But I really don't want to get new cpus just to have sleep working. And hackintoshes seem to care about a lot of things, but I never heard of caring much about the cpus when going for Mojave (but this might be wrong - I'm not really into this topic).

 

[Pete_202]

Just an update to post #145.

I reinstalled Mojave and performed a SMC reset followed by a triple NVRAM reset but it made no difference. Mojave still not sleeping properly - power light pulses but fan(s) running. Had to to a hard shutdown. I have gone back to High Sierra again.

 

[CrispyDog]

Is X5690 the only route? Or would X5670 work as well? Being i dont use this machine much (not having sleep makes me use it even less), not sure im wanting to shell out the $150 for the X5690s (vs $40 for a pair of X5670s). I have E5520s at the moment and they are just awful.

Been following this issue for probably a year or so now. Shame there isnt another workaround.

Edit: Phrased differently, is anyone using a machine that has X5670s in it that doesn't crash on Mojave?

 

[R2K2]

I've replace the dual E5520's in my upgraded 4,1->5,1 with X5650's and they work just fine. No more sleep problems and even with the X5650's there's a noticeable speed increase.

 

[tsialex]

Is X5690 the only route? Or would X5670 work as well? Being i dont use this machine much (not having sleep makes me use it even less), not sure im wanting to shell out the $150 for the X5690s (vs $40 for a pair of X5670s). I have E5520s at the moment and they are just awful.

Any Westmere Xeon will solve the sleep and the audio problems of Mojave, people usually go for X5680/X5690 because it's the fastest supported Xeons on a MP5,1.

Been following this issue for probably a year or so now. Shame there isnt another workaround.

Edit: Phrased differently, is anyone using a machine that has X5670s in it that doesn't crash on Mojave?

Hey, your Xeons were officially supported up to El Capitan, remember? It's very nice that it worked perfectly up to High Sierra.