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

[jjordanc90]

I woke up to another KP after the supplemental update and leaving my cMP on overnight. Just tried turning off hyperthreading. Hoping there isn't a significantly noticeable performance drop with this setting off. Of course it's an imperfect fix but might have to do for now.

 

[Nelly68]

I have a Mid 2012 Mac Pro 5,1 with 2x3.33 Ghz 6-core and a supported graphics card GeForce GTX 780. Boot ROM Version: 144.0.0.0.0. I have been using Mojave with no issues until I installed the supplemental 10.14.6 Build 18G87. After applying the update the Mac responded extremely slow (beach ball) and the finder kept freezing (Not responding). Lucky for me I have a clone of the whole system on a secondary HD which I recloned back to build 18G84. I tried several times to apply the update with different approaches like downloading the full install or just the regular update. Results were the same every time. I haven't tried to do a clean install yet. So for now I left my Mac with the previously build (18G84) Any suggestions? is anybody else experiencing issues? could it be a hardware or software that's causing the trouble?

 

[MIKX]

How many in this thread with the OP's problem have tried doing a clean, full ( 6.05gb ) install of 10.14.6 to a spare APFS SSD ? of course followed by a 3 chime NVRAM / PRAM reset.

I'm assuming that you're all on bootrom 144.0.0.0 and have a metal capable and preferably an EFI'd AMD GPU ( R9 280X - HD 7950 - HD 7970 ) GPU.

The latest release of the 10.14.6 FULL " 6.05gb ) installer is all you need - no combos, supplements - The first FULL 10.14.6 was 6.04gb .. .the latest is 6.05gb.

Could be worth a try.

 

[jjordanc90]

How many in this thread with the OP's problem have tried doing a clean, full ( 6.05gb ) install of 10.14.6 to a spare APFS SSD ? of course followed by a 3 chime NVRAM / PRAM reset.

I'm assuming that you're all on bootrom 144.0.0.0 and have a metal capable and preferably an EFI'd AMD GPU ( R9 280X - HD 7950 - HD 7970 ) GPU.

The latest release of the 10.14.6 FULL " 6.05gb ) installer is all you need - no combos, supplements - The first FULL 10.14.6 was 6.04gb .. .the latest is 6.05gb.

Could be worth a try.

I just had 2 KP's after waking my computer from sleep with hyperthreading disabled on 10.14.6 supplemental update 1. Once I get past a few projects I'm working on I'm going try your advice @MIKX with the clean, full install (6.05gb) and 3 chime NVRAM / PRAM reset. Can anyone give any recommendation on the best place to get this full downloader?

 

[tsialex]

I just had 2 KP's after waking my computer from sleep with hyperthreading disabled on 10.14.6 supplemental update 1. Once I get past a few projects I'm working on I'm going try your advice @MIKX with the clean, full install (6.05gb) and 3 chime NVRAM / PRAM reset. Can anyone give any recommendation on the best place to get this full downloader?

Use installinstallmacos.py, it's this one:

041-94412 10.14.6 18G87 2019-08-01 macOS Mojave

 

[visusest]

Has anyone confirmed a full reinstall will fix the issue? My system beach balls after waking up the display and it's been sitting for a few hours. 10.14.6 combo didn't fix it and I'm still on 140.0.0.0.0. Also is the USB installer still not working for Kepler cards (I have a MVC GT640)? I think I wiped the High Sierra drive I used to initially install Mojave so another reinstall will be a bit of a time commitment.

 

[tsialex]

Has anyone confirmed a full reinstall will fix the issue? My system beach balls after waking up the display and it's been sitting for a few hours. 10.14.6 combo didn't fix it and I'm still on 140.0.0.0.0. Also is the USB installer still not working for Kepler cards (I have a MVC GT640)? I think I wiped the High Sierra drive I used to initially install Mojave so another reinstall will be a bit of a time commitment.

USB installer won't work until you upgrade to 144.0.0.0.0 with the full installer, read the first post of the MP5,1: What you have to do to upgrade to Mojave (BootROM upgrade instructions).

 

[visusest]

Luckily I had not erased my High Sierra drive. Downloaded the 18G47 installer on it and the 144.0.0.0.0 update worked first try (did the 3x NVRAM reset first). Erased my NVMe drive, reinstalled Mojave from the HS drive and restored from a backup. Went out for dinner, came back to wake it up and no beach ball!

 

[visusest]

I spoke too soon. Looked over last night and saw a white screen KP (report below). The two other times I tried to wake up the machine it was completely unresponsive (display didn't wake up to mouse/keys). Any ideas?

Anonymous UUID:       32C9F6BC-6947-C324-34DD-17C1744F695F

Sun Aug 11 16:00:32 2019

*** Panic Report ***
panic(cpu 8 caller 0xffffff801a8bb0ef):  initproc exited -- exit reason namespace 2 subcode 0xa description: none

uuid info:
 0x113d9f000    uuid = <d3e77331-ace5-349d-a7cc-433d626d4a5b>
 0x10ccba000    uuid = <bbd445b6-fba9-3a9c-828f-a112f63e2080>

Thread 2 crashed

RAX: 0x0000000000000000, RBX: 0x000000010cd08068, RCX: 0x000000010cd05000, RDX: 0x000000010cd08088
RSP: 0x0000700000eab1a0, RBP: 0x0000700000eab240, RSI: 0x000000010cd08078, RDI: 0x000000010ccba000
R8:  0x000000010ccbaae8, R9:  0x0000000000000d0e, R10: 0x0000000000000010, R11: 0x0000000000000206
R12: 0x0000000100010ce3, R13: 0x0000000000001eb0, R14: 0x000000010cd0a748, R15: 0x000000010ccba000
RFL: 0x0000000000010246, RIP: 0x00007fff6cc6fb7f, CS:  0x000000000000002b, SS:  0x0000000000000023

Thread 0: 0xffffff803b1bc520
    0x00007fff6cdaa126
    0x00007fff6cc33ede
    0x0000000000000000

Thread 1: 0xffffff803f075520
    0x00007fff6cdc529e
    0x00007fff6cc26de6
    0x00007fff6cc35f42
    0x00007fff6cc2a792
    0x00007fff6cc2b396
    0x00007fff6cc336ed
    0x00007fff6ce64611
    0x00007fff6ce643fd
    0x0000000000070507

Thread 2: 0xffffff8040408000
    0x00007fff6cc6fb7f
    0x00007fff6cc6fa07
    0x00007fff6cc6f8d1
    0x00007fff6ccccb2a
    0x000000010cccace3
    0x000000010ccca324
    0x00007fff6cc2463d
    0x00007fff6cc26de6
    0x00007fff6cc35f42
    0x00007fff6cc2a792
    0x00007fff6cc2b396
    0x00007fff6cc336ed
    0x00007fff6ce64611
    0x00007fff6ce643fd
    0x00000000006d4005

Thread 3: 0xffffff803f861a40
    0x00007fff6cda7bfe
    0x00007fff6ce643fd
    0x0000000000000000

Thread 4: 0xffffff803dd3a520
    0x00007fff6cda7bfe
    0x00007fff6ce643fd
    0xffffffffffffff00


Mac OS version:
18G87

Kernel version:
Darwin Kernel Version 18.7.0: Thu Jun 20 18:42:21 PDT 2019; root:xnu-4903.270.47~4/RELEASE_X86_64
Kernel UUID: 982F17B3-0252-37FB-9869-88B3B1C77335
System model name: MacPro5,1 (Mac-F221BEC8)
Root disk errors: "CSTS=0xffffffff
"

EOF
Model: MacPro5,1, BootROM 144.0.0.0.0, 6 processors, 6-Core Intel Xeon, 3.33 GHz, 16 GB, SMC 1.39f5
Graphics: NVIDIA GeForce GT 640, NVIDIA GeForce GT 640, spdisplays_pcie_device, 1 GB
Memory Module: DIMM 1, 8 GB, DDR3 ECC, 1333 MHz, 0x0198, 0x393936353531362D3030332E4130304C4620
Memory Module: DIMM 2, 8 GB, DDR3 ECC, 1333 MHz, 0x0198, 0x393936353531362D3030332E4130304C4620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x111), Broadcom BCM43xx 1.0 (7.77.61.2 AirPortDriverBrcmNIC-1305.8)
Bluetooth: Version 6.0.14d3, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet 2, Ethernet, en1
Network Service: Wi-Fi, AirPort, en3
PCI Card: NVIDIA GeForce GT 640, Display Controller, Slot-1
PCI Card: NVIDIA GeForce GT 640, NVDA,Parent, Slot-1
PCI Card: PXS3, USB eXtensible Host Controller, Slot-3
PCI Card: pci10ec,5762, NVM Express Controller, Slot-4
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: WDC WD60EZRZ-00RWYB1, 6 TB
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB 2.0 Bus
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: Apple LED Cinema Display
USB Device: Display iSight
USB Device: Display Audio
USB Device: USB 3.0 Bus
USB Device: USB3.0 Hub
USB Device: USB2.0 Hub
FireWire Device: built-in_hub, Up to 800 Mb/sec
Thunderbolt Bus:

 

[MIKX]

KPs are often caused by OSX & 3rd. party software conflicts.

A clean, full 6.05gb install will at least rule out any 3rd. party apps causing KPs.

Think about it. . why did apple re-release a newer, 6.05 gb 10.14.6 installer so soon after the first release?

Were they also getting KPs from the combo/supplemental too ?

The first full installer was 6.04gb.

 

[reader50]

Update. For me, KPs on entering sleep mostly stopped after the 10.14.6 supplemental update. But ... it will do a KP perhaps 1x out of 30. Hyperthreading is enabled.

My force-quit trick still works. I've gone back to applying it.

 

[bsbeamer]

Maybe report that bug to Apple. HP disabled is Apple’s bandaid fix for Spectre/Meltdown and could be the only way they are testing. Do wonder if you disable HP if all issues go away.

 

[Kaiser Hanzi]

I too immediately had this issue with installing Mojave 10.14.6. From all I can see it is a Mac OS issue. I have reverted back to High Sierra which seems to like the Radeon RX 580 card just fine and have not encountered issues. I have sent several of the KP reports to Apple and hopefully they resolve this soon.

 

[jjordanc90]

At this point my best option on 10.14.6 has been to not shut down and not let my computer go to sleep. I can't imagine this is the greatest thing for my machine but I've gone on like this for about two weeks now and haven't had a KP. There's something wacky when I boot up. I get 1 or 2 KP's the first time I power on after shut down or sleep and then the machine will run fine if I keep it on/don't let it sleep. I can let the screensaver happen and I turn off my displays but if it shuts down or goes to sleep it's a wrap. Really hoping Apple puts an end to this madness soon.

 

[bsbeamer]

I've 100% disabled sleep on my MP5,1 for awhile and it's been fine. When it's on, it's running a task and shouldn't sleep. When it's off, the machine is most likely not going to be used for a few days. Monitor still sleeps and has never been an issue. Auto screen saver disabled, however. Just use hot corner or monitor sleep after XX minutes.

 

[R2K2]

I found someone on the Macnn forum saying this is a processor issue with MacPro's 4,1's, and can be solved by upgrading to an X-series Xeon (instead of E- or W-).
TS has a 5,1 MP, but I think his 2.4Ghz 6-core is also an E-series Xeon (E5645?).

Link here: https://forums.macnn.com/showthread.php?t=528054

 

[reader50]

R2K2, I thank you for finding my MacNN post. As I did much of my research by reading this thread, you are asking in the right place.

 

[fotmasta]

MacPro5,1
High Sierra 10.12.6

KP on sleep.
Last line on system.log was at 14:10:27
Last line on prmset log was 14.11:07
Somewhere between there, things went sour

2019-08-21 14:10:57 -0700 Sleep Entering Sleep state due to 'Software Sleep pid=118': Using AC (Charge:0%)
2019-08-21 14:11:07 -0700 Wake Requests [*proc=mDNSResponder request=Maintenance inDelta=3600]
2019-08-21 14:11:07 -0700 PM Client Acks Delays to Sleep notifications: [AirPort configd plug-in is slow(263 ms)] [com.apple.apsd is slow(2731 ms)] [mDNSResponder is slow(10011 ms)]
2019-08-22 12:20:32 -0700 HibernateStats hibmode=0 standbydelay=0 0

 

[R2K2]

R2K2, I thank you for finding my MacNN post. As I did much of my research by reading this thread, you are asking in the right place.

Do you have any explanation for why this should only happen on E- and W-series Xeons and not on X-series? Because jjordanc90 (reply #89) is having KP's on sleep and seems to be running X5680's.

 

[reader50]

Do you have any explanation for why this should only happen on E- and W-series Xeons and not on X-series? Because jjordanc90 (reply #89) is having KP's on sleep and seems to be running X5680's.

The generally accepted explanation is that Apple is no longer testing OS compatibility with the E- and W- series Xeons. Those were used in earlier MacPro models, which Apple has dropped OS support for. So they did something (probably an optimization) that caused issues on the earlier Xeons, but didn't catch it when the 2009 and 2010 MPs were not tested.

And Apple may or may not put effort into fixing these issues now for unsupported Mac Pros. It may depend on how much bad press they get. I've seen them fix bugs affecting unsupported Macs before, but it's uncommon.

note: this bug only seems to affect dual-CPU machines. Mactracker says E- and W- series CPUs were still used in 2012 MPs, but I assume they were limited to the single CPU models. X-series is definitely the safer choice, and fixes it for most users. I cannot speak for jjordanc90.

 

[jsts]

Same issue here. Started after 10.14.6 update.

My specs:
Mac Pro 4,1->5,1 (2009)
BootROM 144.0.0.0.0
2x Xeon X5690
4x SSD's HFS+ SM951 Amfeltec carrier board RAID0 (Slot2)
96GB RAM 1333Mhz
1x Flashed EVGA SC GTX680 4GB (Slot1)
1x Apple LED Cinema Display 1920х1200

Anonymous UUID:       885BE441-7624-14BC-BDEB-9E9275B0A3AD

Sat Sep  7 01:00:58 2019

*** Panic Report ***
Panic(CPU 0, time 111495791063250): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff80cf371048, spinlock owner: 0xffffff80cd98da40, current_thread: 0xffffff80cd98da40, spinlock_owner_cpu: 0x0
RAX: 0x00000000056fc1d4, RBX: 0xffffff80cda2a700, RCX: 0x0000000000000001, RDX: 0x000000000000002a
RSP: 0xffffff8a807fad00, RBP: 0xffffff8a807fad30, RSI: 0x000000499d5dcc4c, RDI: 0xffffff800c80ffa0
R8:  0x0000000000000001, R9:  0x0000000000001000, R10: 0xffffff80cddec000, R11: 0xffffff8a8082d000
R12: 0xffffff80ce050100, R13: 0xffffff8a7feaf8b0, R14: 0xffffff800c80ffa0, R15: 0xffffff80cf371000
RFL: 0x0000000000000002, RIP: 0xffffff7f8f2c120c, CS:  0x0000000000000008, SS:  0x0000000000000010
Backtrace (CPU 0), Frame : Return Address
0xffffff8a807faba0 : 0xffffff800c0db00b
0xffffff8a807fac00 : 0xffffff800bf5be47
0xffffff8a807fad30 : 0xffffff800c0e67e6
0xffffff8a807fad50 : 0xffffff800bfc9169
0xffffff8a807fad90 : 0xffffff800bfc902e
0xffffff8a807fadc0 : 0xffffff800bff71ed
0xffffff8a807fae80 : 0xffffff800c0c92b7
0xffffff8a807faea0 : 0xffffff800c0e4df3
0xffffff8a807faf10 : 0xffffff800c0e4ad3
0xffffff8a807faf50 : 0xffffff800c0e39d3
0xffffff8a807faf70 : 0xffffff800c0db00b
0xffffff8a807fafd0 : 0xffffff800bf5bced
0xffffff8ab5f03f30 : 0xffffff800bfd0287
0xffffff8ab5f03f80 : 0xffffff800bfd0470
0xffffff8ab5f03fa0 : 0xffffff800bf5b0ce
      Kernel Extensions in backtrace:
         com.apple.driver.AppleIntelCPUPowerManagement(220.0)[6703E7B6-EE67-3019-A4D7-5D5B239486AB]@0xffffff7f8f2be000->0xffffff7f8f2e6fff

BSD process name corresponding to current thread: kernel_task

Mac OS version:
18G95

Kernel version:
Darwin Kernel Version 18.7.0: Tue Aug 20 16:57:14 PDT 2019; root:xnu-4903.271.2~2/RELEASE_X86_64
Kernel UUID: C41337A1-0EC3-3896-A954-A1F85E849D53
Kernel slide:     0x000000000bc00000
Kernel text base: 0xffffff800be00000
__HIB  text base: 0xffffff800bd00000
System model name: MacPro5,1 (Mac-F221BEC8)

System uptime in nanoseconds: 111495791099720
last loaded kext at 111411002121324: com.apple.driver.usb.cdc    5.0.0 (addr 0xffffff7f8f91e000, size 28672)
last unloaded kext at 54019123281311: com.apple.driver.usb.cdc    5.0.0 (addr 0xffffff7f8f921000, size 28672)
loaded kexts:
com.parallels.kext.netbridge    15.0.0 46967
com.parallels.kext.hypervisor    15.0.0 46967
com.parallels.kext.vnic    15.0.0 46967
com.plantronics.driver.PlantronicsDriverShield    4.3
com.apple.fileutil    20.036.15
com.apple.driver.AGPM    110.25.11
com.apple.filesystems.autofs    3.0
com.apple.driver.AppleMikeyHIDDriver    131
com.apple.driver.AppleGraphicsDevicePolicy    3.50.12
com.apple.AGDCPluginDisplayMetrics    3.50.12
com.apple.driver.pmtelemetry    1
com.apple.iokit.IOUserEthernet    1.0.1
com.apple.driver.AppleHDA    282.54
com.apple.driver.AppleUpstreamUserClient    3.6.5
com.apple.driver.AppleMCCSControl    1.5.9
com.apple.iokit.IOBluetoothSerialManager    6.0.14d3
com.apple.driver.AppleMik



EOF

System Profile:
Bluetooth: Version 6.0.14d3, 3 services, 27 devices, 1 incoming serial ports
Model: MacPro5,1, BootROM 144.0.0.0.0, 12 processors, 6-Core Intel Xeon, 3,46 GHz, 96 GB, SMC 1.39f5
Thunderbolt Bus:
Boot Volume File System Type: hfs
Graphics: NVIDIA GeForce GTX 680, NVIDIA GeForce GTX 680, spdisplays_pcie_device, 4 GB
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: Bluetooth USB Host Controller
USB Device: USB Bus
USB Device: Razer Mamba
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Keyboard Hub
USB Device: Apple Keyboard
USB Device: Hub
USB Device: Apple LED Cinema Display
USB Device: Display iSight
USB Device: Display Audio
USB Device: USB 2.0 Bus
Memory Module: DIMM 1, 16 GB, DDR3 ECC, 1333 MHz, 0x02FE, 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Memory Module: DIMM 2, 16 GB, DDR3 ECC, 1333 MHz, 0x02FE, 0x45424A3137524734424657442D4A532D4620
Memory Module: DIMM 3, 16 GB, DDR3 ECC, 1333 MHz, 0x802C, 0x33364A534632473732505A2D3147394E3120
Memory Module: DIMM 5, 16 GB, DDR3 ECC, 1333 MHz, 0x02FE, 0x45424A3137524734424657442D4A532D4620
Memory Module: DIMM 6, 16 GB, DDR3 ECC, 1333 MHz, 0x02FE, 0x45424A3137524734424657442D4A532D4620
Memory Module: DIMM 7, 16 GB, DDR3 ECC, 1333 MHz, 0x802C, 0x33364A534632473732505A2D3147394E3120
FireWire Device: built-in_hub, Up to 800 Mb/sec
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x14A), Broadcom BCM43xx 1.0 (7.77.61.2 AirPortDriverBrcmNIC-1305.8)
Network Service: Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce GTX 680, Display Controller, Slot-1
PCI Card: NVIDIA GeForce GTX 680, NVDA,Parent, Slot-1
PCI Card: pci144d,a801, AHCI Controller, Slot-2@8,0,0
PCI Card: pci144d,a801, AHCI Controller, Slot-2@10,0,0
PCI Card: pci144d,a801, AHCI Controller, Slot-2@9,0,0
PCI Card: pci144d,a801, AHCI Controller, Slot-2@11,0,0
Serial ATA Device: SAMSUNG MZHPV512HDGL-00000, 512,11 GB
Serial ATA Device: SAMSUNG MZHPV512HDGL-00000, 512,11 GB
Serial ATA Device: SAMSUNG MZHPV512HDGL-00000, 512,11 GB
Serial ATA Device: SAMSUNG MZHPV512HDGL-00000, 512,11 GB
Serial ATA Device: HL-DT-ST DVD-RW GH41N

 

[eighteentee]

Same problem here. After the 10.14.6 supplemental update, KPs during sleep. Is it possible to roll-back with time machine even if I have no boot screens (Radeon R9 RX280 unflashed)?

 

[reader50]

The 10.14.6 Supplemental Update #2 made my force-quit hack unreliable. It's harder to apply (needs higher CPU usage now), and eventually fails with a KP on sleep. Might last up to a week, usually less. I'm waiting for the X56xx CPUs to get cheaper.

 

[reader50]

Correction, my force-quit trick does not work at all after the 10.14.6 Supplemental Update #2.

However, a new trick does. Load down all cores, then engage sleep. Tested extensively over the last 24 hours. No KPs, sleep engaged properly each time. I've never had trouble exiting sleep.

I'm using Handbrake with a video encode that loads up all cores. It has the added advantage of keeping its encoding queue when quit (after waking from sleep). So the next time you launch HandBrake, the encode is queued up and ready to start again.

Have not tested if a lesser load would do the trick. The only annoying point is you have to engage the multi-core load each time, before engaging sleep. It's more convenient that shutdown-reboot, but it's not actually convenient.

 

[tsialex]

Today's reissued 10.14.6 has build number 18G103 and a new full MAS installer, worth checking the new build for anyone having KPs.

All these updates released today:

061-21530 - Sierra Security Update 2019-005 - 937.2GB
061-21534 - High Sierra Security Update 2019-005 - 1.88GB
061-21545 - macOS Mojave 10.14.6 Supplemental Update 2 - 1.47GB
061-21549 - macOS 10.14.6 Update (combo) - 3.93GB
061-21551 - macOS Mojave (MAS full installer) - 6.52GB
061-21552 - BridgeOSUpdateCustomer - 366.8GB
061-21553 - macOS 10.14.6 Update (delta) - 2.61GB