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

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

MacGarage

MacGarage

macrumors regular
Jun 18, 2017
197
102
Ohio
MacGarage said:
Thanks...was able to upgrade to 144.0.0.0. Will let it sleep overnight and see what happens.
Click to expand...

Unfortunately, after the upgrade and leaving it asleep for over a day, had the crash again.

Lastest.

Anonymous UUID: AF64C102-BCDE-47D2-D6C0-4375DAAB7CA9

Sun May 26 18:58:50 2019

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8ca969f0): pmLock: waited too long, held by 12@0xffffff8009add929
Backtrace (CPU 0), Frame : Return Address
0xffffff8744e03920 : 0xffffff80099aea2d
0xffffff8744e03970 : 0xffffff8009ae9e95
0xffffff8744e039b0 : 0xffffff8009adb70a
0xffffff8744e03a20 : 0xffffff800995bb40
0xffffff8744e03a40 : 0xffffff80099ae447
0xffffff8744e03b60 : 0xffffff80099ae293
0xffffff8744e03bd0 : 0xffffff7f8ca969f0
0xffffff8744e03c10 : 0xffffff8009ae7fad
0xffffff8744e03c80 : 0xffffff7f8bcae185
0xffffff8744e03cd0 : 0xffffff7f8bcb24bf
0xffffff8744e03cf0 : 0xffffff800a07c298
0xffffff8744e03d70 : 0xffffff800a0af997
0xffffff8744e03de0 : 0xffffff800a03f62f
0xffffff8744e03e40 : 0xffffff800a03c29d
0xffffff8744e03ea0 : 0xffffff800a038cf3
0xffffff8744e03ef0 : 0xffffff800a038b90
0xffffff8744e03f30 : 0xffffff800a056362
0xffffff8744e03f70 : 0xffffff800a0558bc
0xffffff8744e03fa0 : 0xffffff800995b0ce
Kernel Extensions in backtrace:
com.apple.driver.AppleACPIPlatform(6.1)[AE00900F-6E82-31C1-82E7-23005F4219A4]@0xffffff7f8bca2000->0xffffff7f8bd3dfff
dependency: com.apple.iokit.IOACPIFamily(1.4)[D039545F-9B61-3B0D-8F90-CCCAE5BD7A52]@0xffffff7f8a311000
dependency: com.apple.iokit.IOPCIFamily(2.9)[CC6A465F-5A24-304D-B9DF-8C27819CC214]@0xffffff7f8a295000
dependency: com.apple.driver.AppleSMC(3.1.9)[A20E3E30-0CB9-3E88-9B52-F65FE643BCCF]@0xffffff7f8a31a000
com.apple.driver.AppleIntelCPUPowerManagement(220.0)[1556F86B-CAA3-32C6-9426-5D21BC673189]@0xffffff7f8ca93000->0xffffff7f8cabbfff

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: 0x0000000009600000
Kernel text base: 0xffffff8009800000
__HIB text base: 0xffffff8009700000
System model name: MacPro5,1 (Mac-F221BEC8)
 
D

dgarratt

macrumors member
Original poster
Jul 16, 2012
42
8
cheezegrate said:
The symptoms seem to be the same like in my case. Do you have hyper-threading still enabled?

Cheers
[doublepost=1557989947][/doublepost]

Could you please add "on sleep" (or similar) to the thread title? Would make it easier for people to find and distinguish this problem from other kernel panics.

Cheers
Click to expand...
Good idea, thread title updated.
 
MacGarage

MacGarage

macrumors regular
Jun 18, 2017
197
102
Ohio
After reading the above nMP link...has there any luck for the cMP?

Once this started happening to me, it started doing every time I sleep...odd that it just popped up well after the latest OS update.
 
MacGarage

MacGarage

macrumors regular
Jun 18, 2017
197
102
Ohio
Franckymrs said:
someone found the solution to the problem ?
thank you
Click to expand...

The only thing that has helped me was to disable hyper-threading via X-Code and never put it to sleep.

Once or twice, or perhaps I let it sleep, I had the same panic, hence disable hyper-threading.
 
F

Franckymrs

macrumors member
Apr 24, 2019
40
3
MacGarage said:
The only thing that has helped me was to disable hyper-threading via X-Code and never put it to sleep.

Once or twice, or perhaps I let it sleep, I had the same panic, hence disable hyper-threading.
Click to expand...

thank you for your reply
I did a test with only the Apple Ram no problem !! I think Ram non Apple is not tolerated ?
today I did a clean instal 10.14.5 formatting with terminal of my SSD NVM terminal "
diskutil eraseDisk" for the moment no problem .
I'll keep you informed
 
MacGarage

MacGarage

macrumors regular
Jun 18, 2017
197
102
Ohio
Has anyone tried the beta 2 of 10.14.6 to see if it solves the issue? Seems like some are having luck with it on their nMPs.
 
F

Franckymrs

macrumors member
Apr 24, 2019
40
3
two kernal panic in 48 hours !
MacGarage said:
Has anyone tried the beta 2 of 10.14.6 to see if it solves the issue? Seems like some are having luck with it on their nMPs.
Click to expand...
for me the clean instal with the 10.14.5 did not work
I test the public beta 1 of the 10.14.6 for the moment no kernal
 
Last edited:
R

reader50

macrumors member
Apr 9, 2003
37
20
California
I had Adobe PS Elements 6 get stuck. Apparently shut down, but the system believed otherwise, and would not shut down due to PSE not responding. No Adobe process visible in Activity Monitor.

Put it to sleep to force a crash. Unexpectedly, my MP went to sleep. Awoke normally. Tried it a 2nd time, same result. I finally did a forced shutdown and rebooted (i needed PSE to reopen). Now it's back to crash-on-entering-sleep.

Mac Pro 4,1 -> 5,1 with W5580 CPUs. I haven't identified anything else unusual abut my config at the time.
[doublepost=1560843678][/doublepost]Further testing, trying to recreate the accident.

All the same apps open -> trigger sleep -> kernel panic.

Open PSE6, try to recreate crash (unsuccessful), force-quite PSE6. Trigger sleep -> normal sleep. Tested sleep 2x, both successful. About to let it sleep overnight.

Could it be that simple? Open PSE6 (or perhaps other apps), force-quit, and sleep works until the next reboot?
 
R

reader50

macrumors member
Apr 9, 2003
37
20
California
Update. My MP slept the night away without issue. Has slept several times this morning. No kernel panics.

I'd like to reboot, then test if force-quitting *any* app beats the dreaded pmLock. But I really like my sleeping Mac, and don't want to jinx it. So it might be awhile before I reboot again.

btw, machine specs:
MacPro 4,1 -> 5,1 with dual CPUs 3.2 GHz (W5580)
macOS 10.14.5 booting from 1TB Mushkin SSD (apfs volume)
bootrom 144.0.0.0.0
SMC 1.39f5
64 GB RAM
Radeon HD 7970 (with Mac EFI)
 
R

reader50

macrumors member
Apr 9, 2003
37
20
California
My fix stopped working about 12 hours after first applying it. Since then it's been inconsistent, KPs more often than success. I'm back to trial-and-error, trying to work out the exact sequence to enable sleep.
 
R

reader50

macrumors member
Apr 9, 2003
37
20
California
Here is what I do. Force-quit PSE6 while it is busy. Specifically, I open four random pictures, begin creating a photomerge panorama from those 4, and force-quit while PSE6 is thinking about it. Before it finishes creating the end result.

The system sleeps normally afterwards. No apparent time limit on the hack.

Force-quitting PSE6 while it is idle does not consistently work. Likewise, force-quitting Preview (again while it was idle) did nothing.

Assumption: force-quitting any multi-threaded app while it's busy will do the trick.

So I rebooted. Confirmed we were back to KP-on-sleep. Then opened VLC and played a video file large enough to force multithreaded playback. Where Activity Monitor shows it using more than 100%.

Force-quit VLC while it was playing. Tested sleep - and it worked fine. No kernel panic.

Any 1080p (or larger) video file should be enough to force VLC to multithread the decode. I used a 4K trailer file from hd-trailers.

When it stopped working last time, I think I had opened PSE6 again for some photo work, then quit it the normal way. But when I retested those steps (after using PSE6 to create the hack) it did not produce a crash. So I'm unclear on how the hack stops working.

I'd love to know if this works for anyone else.
 
Last edited:
R

reader50

macrumors member
Apr 9, 2003
37
20
California
It's been 10 days. At least 7 since my last reboot. Sleep has worked every time - no panics. Mojave 10.14.5

So force-quitting VLC while playing a "large" video fixes things until the next reboot. Probably can be fixed by force-quitting any multithreaded app while it's busy.

Maybe 10.14.6 will fix it entirely. Until that happens, this is a good workaround.
 
MacGarage

MacGarage

macrumors regular
Jun 18, 2017
197
102
Ohio
I noticed my 2012 MacBook Pro is having the same issue after it sleeps more than a couple of days...never had a KP since new...so both my cMP and MacBook have the same issue.
 
jjordanc90

jjordanc90

macrumors newbie
Jul 29, 2019
4
0
crjackson2134 said:
I don’t personally have this problem but it’s obviously fairly widespread. I encourage all of you to file a bug report on this (not feedback).
Click to expand...

I'm having the same issue after upgrading my 4,1>5,1 to 10.14.6.
Having one about 1 KP per day.
The latest KP report seemed to indicate some issue with "AppleIntelCPUPowerManagement (220.0)":

Anonymous UUID: 2670AF2B-A1CB-62D9-8D51-40B022F9AABA

Mon Jul 29 09:16:19 2019

*** Panic Report ***
Machine-check capabilities: 0x0000000000001c09
family: 6 model: 44 stepping: 2 microcode: 31
signature: 0x206c2
Intel(R) Xeon(R) CPU X5680 @ 3.33GHz
9 error-reporting banks
Processor 12: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f
IA32_MC1_ADDR(0x406): 0x000000e1e7e1e000
IA32_MC1_MISC(0x407): 0x0000000001000000
Processor 13: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f
IA32_MC1_ADDR(0x406): 0x000000e1e7e1e000
IA32_MC1_MISC(0x407): 0x0000000001000000
Processor 14: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f
IA32_MC1_ADDR(0x406): 0x000000e1e7e1e000
IA32_MC1_MISC(0x407): 0x0000000001000000
Processor 15: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f
IA32_MC1_ADDR(0x406): 0x000000e1e7e1e000
IA32_MC1_MISC(0x407): 0x0000000001000000
Processor 16: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f
IA32_MC1_ADDR(0x406): 0x000000e1e7e1e000
IA32_MC1_MISC(0x407): 0x0000000001000000
Processor 17: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f
IA32_MC1_ADDR(0x406): 0x000000e1e7e1e000
IA32_MC1_MISC(0x407): 0x0000000001000000
Processor 18: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f
IA32_MC1_ADDR(0x406): 0x000000e1e7e1e000
IA32_MC1_MISC(0x407): 0x0000000001000000
Processor 19: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f
IA32_MC1_ADDR(0x406): 0x000000e1e7e1e000
IA32_MC1_MISC(0x407): 0x0000000001000000
Processor 20: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f
IA32_MC1_ADDR(0x406): 0x000000e1e7e1e000
IA32_MC1_MISC(0x407): 0x0000000001000000
Processor 21: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f
IA32_MC1_ADDR(0x406): 0x000000e1e7e1e000
IA32_MC1_MISC(0x407): 0x0000000001000000
Processor 22: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f
IA32_MC1_ADDR(0x406): 0x000000e1e7e1e000
IA32_MC1_MISC(0x407): 0x0000000001000000
Processor 23: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC1_STATUS(0x405): 0xbe00000000400e0f
IA32_MC1_ADDR(0x406): 0x000000e1e7e1e000
IA32_MC1_MISC(0x407): 0x0000000001000000
mp_kdp_enter() timed-out on cpu 8, NMI-ing
mp_kdp_enter() NMI pending on cpus: 0 1 2 3 4 5 6 7 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
mp_kdp_enter() timed-out during locked wait after NMI;expected 24 acks but received 1 after 17314416 loops in 1662499788 ticks
panic(cpu 8 caller 0xffffff801d4db51a): "Machine Check at 0xffffff7fa04da4f0, registers:\n" "CR0: 0x000000008001003b, CR2: 0x000000017a7f5058, CR3: 0x00000000225b2000, CR4: 0x00000000000226e0\n" "RAX: 0x0000000000000001, RBX: 0xffffff80aa57c400, RCX: 0x0000000000000001, RDX: 0x0000000000000000\n" "RSP: 0xffffff8759b7bd50, RBP: 0xffffff8759b7bd80, RSI: 0x0000000000000001, RDI: 0xffffff80aab63260\n" "R8: 0xffffff80aabb2d00, R9: 0xffffff80b822dc90, R10: 0xffffff801dc0dc78, R11: 0x00000000225b2000\n" "R12: 0xffffff7fa04f6630, R13: 0xffffff80a9d75800, R14: 0x0000000000000148, R15: 0x0000000000000001\n" "RFL: 0x0000000000000046, RIP: 0xffffff7fa04da4f0, CS: 0x0000000000000008, SS: 0x0000000000000010\n" "Error code: 0x0000000000000000\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4903.270.47/osfmk/i386/trap_native.c:168
Backtrace (CPU 8), Frame : Return Address
0xffffff801d155330 : 0xffffff801d3ad6ed
0xffffff801d155380 : 0xffffff801d4e9185
0xffffff801d1553c0 : 0xffffff801d4da8ba
0xffffff801d155430 : 0xffffff801d35ab40
0xffffff801d155450 : 0xffffff801d3ad107
0xffffff801d155570 : 0xffffff801d3acf53
0xffffff801d1555e0 : 0xffffff801d4db51a
0xffffff801d1556d0 : 0xffffff801d35b39f
0xffffff8759b7bd80 : 0xffffff7fa04d2b89
0xffffff8759b7be60 : 0xffffff7fa04d1dce
0xffffff8759b7bf10 : 0xffffff801d4dc8ec
0xffffff8759b7bf30 : 0xffffff801d3cf287
0xffffff8759b7bf80 : 0xffffff801d3cf470
0xffffff8759b7bfa0 : 0xffffff801d35a0ce
Kernel Extensions in backtrace:
com.apple.driver.AppleIntelCPUPowerManagement(220.0)[E0712C0E-0EEB-3164-9DB2-2452905AC25D]@0xffffff7fa04d0000->0xffffff7fa04f8fff

BSD process name corresponding to current thread: kernel_task

Mac OS version:
18G84

Kernel version:
Darwin Kerne



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.33 GHz, 64 GB, SMC 1.39f5
Thunderbolt Bus:
Boot Volume File System Type: apfs
Graphics: Radeon RX 580, Radeon RX 580, spdisplays_pcie_device, 8 GB
USB Device: USB 2.0 Bus
USB Device: DataTraveler 2.0
USB Device: Scarlett 18i20 USB
USB Device: USB 2.0 Bus
USB Device: USB 3.0 FD
USB Device: Keyboard Hub
USB Device: Apple Keyboard
USB Device: ASM107x
USB Device: ASMT1153e
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB 3.0 Bus
USB Device: OWC Express USB3.0
USB Device: OWC Mercury On-The-Go
USB Device: YAMAHA MOTIF XS8
USB Device: Hub
USB Device: Hub
USB Device: iLok
USB Device: eLicenser
USB Device: USB Axiom 61
Memory Module: DIMM 1, 8 GB, DDR3 ECC, 1333 MHz, 0x80CE, 0x4D33393342314B37304348302D5948392020
Memory Module: DIMM 2, 8 GB, DDR3 ECC, 1333 MHz, 0x80CE, 0x4D33393342314B37304348302D5948392020
Memory Module: DIMM 3, 8 GB, DDR3 ECC, 1333 MHz, 0x80CE, 0x4D33393342314B37304348302D5948392020
Memory Module: DIMM 4, 8 GB, DDR3 ECC, 1333 MHz, 0x80CE, 0x4D33393342314B37304348302D4348392020
Memory Module: DIMM 5, 8 GB, DDR3 ECC, 1333 MHz, 0x80CE, 0x4D33393342314B37304348302D5948392020
Memory Module: DIMM 6, 8 GB, DDR3 ECC, 1333 MHz, 0x80CE, 0x4D33393342314B37304348302D5948392020
Memory Module: DIMM 7, 8 GB, DDR3 ECC, 1333 MHz, 0x80CE, 0x4D33393342314B37304348302D5948392020
Memory Module: DIMM 8, 8 GB, DDR3 ECC, 1333 MHz, 0x80CE, 0x4D33393342314B37304348302D4348392020
FireWire Device: built-in_hub, Up to 800 Mb/sec
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.102.31)
Network Service: Wi-Fi, AirPort, en2
PCI Card: pci2646,10, AHCI Controller, Slot-1
PCI Card: Radeon RX 580, Display Controller, Slot-2
PCI Card: pci1002,aaf0, Audio Device, Slot-2
PCI Card: PXS4, USB eXtensible Host Controller, Slot-4
Serial ATA Device: Kingston SHPM2280P2H/960G, 960.2 GB
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: Hitachi HUA722020ALA330, 2 TB
Serial ATA Device: ST3300631AS, 300.07 GB
Serial ATA Device: SAMSUNG HD204UI, 2 TB
Serial ATA Device: HDS724040KLSA80, 400.09 GB
 
R

reader50

macrumors member
Apr 9, 2003
37
20
California
10.14.6 did not fix it for me, I had to reapply my hack.

However, the 10.14.6 Supplemental Update appears to have fixed it. About a dozen sleep cycles since applying the update, with no KPs. Have not rebooted since, and it's only been a day, so it's hardly a full test. But I'm hopeful.
 
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