Mac Pro 2013 Mojave kernel panic "AppleIntelCPUPowerManagement(220.0) after activating sleep mode

Yours is the twin of most of the ones previously posted with the firmware/software combination issue, with one exception. Before the old report could be processed, the end of it was overwritten with another, similar report.

Kernel Panic after upgrading to 10.14.4 - Apple Community

.

You have a wonky multiple-processor problem, possibly including the GPUs as processors. Somebody Locked a Lock Byte signal and never came back to unlock it. These sorts of issues always surface in CPU Power Management, and seeing it happen there tells you nothing.

You have MANY invasive kernel extensions present:

loaded kexts:

org.dungeon.driver.SATSMARTDriver 0.8.1

com.vmware.kext.vmioplug.18.1.2 18.1.2

com.vmware.kext.vmx86 1366.85.89

com.vmware.kext.vmnet 1366.85.89

com.vmware.kext.vmci 90.8.2

net.pulsesecure.PulseSecureFirewall 9.0.3f4

com.paragon-software.kext.VDMounter 1370.2

com.paragon-software.filesystems.ntfs 41.5.15

You appear to be running 10.14.4 to 10.14.5 on a Mac Pro 2013 model. This combination has been difficult for some users, especially those running firmware 130.0.0.0.0. The complaints are wonky multiple-processor problems. Rolling back to 10.14.3 solves the problem for some -- IF this is the same problem as others are seeing.

eullin--

I suggest you remove all non-Apple extensions, or un in Safe mode to see if the problem occurs with no third-party extensions present. If it does not panic in the same way, the problem is in something you added.

If the problem continues, even with no third-party extensions added, you will need to avoid the deadly combination of firmware and software mentioned on the discussion thread I posted above.

Some readers found relief by gong back to 10.14.3. Others found:

<<the issues are resolved in 10.14.6 Beta2. With the latest update the Boot ROM is updated to 131.0.0.0.0, and since that update people are not experiencing panics anymore.>>

Or you can wait until it is actually released, not Beta software any more.

I made a text file list of the panic message. (copy paste to Text Edit)

I then installed Mojave 10.14.3 on a drive.

I made a dmg file of the System Library Extensions and Library Extensions with Disk Utility.

Using the panic error file... I copied the 10.14.3 extensions one at a time into the 10.14.5 installed drive.

A real pain requiring multiple drives.

Suggestion, try the AppleIntelCPUPowerManagement kext from 10.14.3 first. (dated Dec 20 2018)

com.apple.driver.AppleACPIPlatform(6.1)

com.apple.iokit.IOACPIFamily(1.4)

com.apple.iokit.IOPCIFamily(2.9)

com.apple.driver.AppleSMC(3.1.9)

 com.apple.driver.AppleIntelCPUPowerManagement(220.0)

as I said above:

These sorts of issues always surface in CPU Power Management, and seeing it happen there tells you nothing.

Apple CPU power management is not the source of the problem, only the messenger.

Version 130.0.0.0.0 of the firmware is the problem with 10.14.4 and 10.14.5, and if you can do one of:

• return to 10.14.3

• upgrade to a later version of the firmware by installing 10.14.6, currently only available as beta software.

... your problems are likely to subside, according to other users in a similar situation.

For those who pathologically argue then simply turn the com.apple.driver.AppleIntelCPUPowerManagement kext from 14.3 and 14.5 into text files and see for yourself that the instructions have been altered for no good reason since the Nehalem Mac Pro has not been altered for almost a decade and other Macs that have this problem have no change for over 6 years.

There is no reason for these power management extensions to be altered.

This Mac has run OSX 10.5 through 10.13 without any problems regarding sleep or power management.

The software installed is 100% identical to 10.13.

The drive with 10.14.3 runs flawlessly.

The drive(s) with 10.14.4 and 10.14.5 ALL fail with this no sleep restart problem. (ALL FAIL)

Only a politician, or shrink who believe in AI would claim that the problem is the computer or the applications installed.

30+ years of systems analysis in hardware leaves no possibility that the problem is not an Apple provided extension.

Seeing an alteration in a power management kext file responsible for sleep tells me everything.

Hi Grant,

Thanks for the quick reply! No, I tried to answer jw-sadler who said he is using Parallels. And that's what I do, too. Perhaps I should try the Catalina Beta, but this will be more risky than just the Kernel Panics after sleep mode! ;-)

Andy

I had the same issue. Maybe related to Parallels? Any help would be much appreciated.

Thanks,

James.

Please note, after one extension copy test for boot and sleep cycle before you proceed or you may end up with a drive that will not boot.

Same problem on my MacPro 2013 and Parallels running...

Same problem as above?

Same solution as posted above: drop back to 10.14.3, or forward to 10.14.6 issued 22 July 2019.

Funnily enough if I ensure all my vms are shut down/suspended the issue doesn’t happen.