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

kkinto

macrumors regular
Original poster
Apr 29, 2011
228
63
Hi.

I'm having a random freeze/silent restart issue with my MacPro. No fans come on, nothing even prior (I am using Macs fans) so it doesn't seems heat related. No chime on restart.

I've just updated to Monterey 12.7.1 and since that process finished this new problem appeared. Maybe they are not related, but maybe they are. Twice since the update complete the Mac has just frozen for like 10-15 secs or so and then quietly (no chime) rebooted itself with a kernel panic warning. Until now, no issues whatsoever for months.

I have include the two reports and they seem almost identical except for the CPU number.

Any insight appreciated, thanks!

Panic(cpu 2 caller 0xffffff8012bcaf19): "kind == NEW && refcnt = -1\n" @jobj.c:4068
Panicked task 0xffffff90adc43670: 295 threads: pid 0: kernel_task
Backtrace (CPU 2), panicked thread: 0xffffff95793adaa0, Frame : Return Address
0xffffffc12f93b770 : 0xffffff800f879a3d
0xffffffc12f93b7c0 : 0xffffff800f9dca16
0xffffffc12f93b800 : 0xffffff800f9cbd83
0xffffffc12f93b850 : 0xffffff800f819a90
0xffffffc12f93b870 : 0xffffff800f879e0d
0xffffffc12f93b990 : 0xffffff800f8795c6
0xffffffc12f93b9f0 : 0xffffff8010114a83
0xffffffc12f93bae0 : 0xffffff8012bcaf19
0xffffffc12f93bb50 : 0xffffff8012bca39e
0xffffffc12f93bd00 : 0xffffff8012b9c1f8
0xffffffc12f93bfa0 : 0xffffff800f81919e
Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1934.141.2)[721020CF-BF5F-3DEF-9F3A-AFE4205CD53E]@0xffffff8012b0d000->0xffffff8012c8bfff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[6E6AB947-75F7-344F-97FE-F1A9A803D2F2]@0xffffff8010db2000->0xffffff8010dbbfff
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[DCCE5AA9-462A-34BB-A905-A4CEB8DF45E2]@0xffffff8010dc8000->0xffffff8010dcdfff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[0BBEF1B6-3879-3835-9993-30FB5B22F3A7]@0xffffff80112d4000->0xffffff80112dbfff
dependency: com.apple.iokit.IOStorageFamily(2.1)[63189A2A-E19C-3F1E-96EF-95B7DB154785]@0xffffff801257c000->0xffffff8012592fff
dependency: com.apple.kec.corecrypto(12.0)[5C997179-2E95-341F-A88B-07977BCCB606]@0xffffff8012cc5000->0xffffff8012d45fff
dependency: com.apple.security.AppleImage4(4.2.0)[8E7BE283-81FC-3565-A114-F692370A8969]@0xffffff8010e4f000->0xffffff8010e67fff

Process name corresponding to current thread (0xffffff95793adaa0): kernel_task
Boot args: -no_compat_check agdpmod=pikera chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21G920

Kernel version:
Darwin Kernel Version 21.6.0: Wed Oct 4 23:55:28 PDT 2023; root:xnu-8020.240.18.704.15~1/RELEASE_X86_64
Kernel UUID: CA525A92-20FF-38D2-AB16-E64095531D5A
KernelCache slide: 0x000000000f600000
KernelCache base: 0xffffff800f800000
Kernel slide: 0x000000000f610000
Kernel text base: 0xffffff800f810000
__HIB text base: 0xffffff800f700000
System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 3525863372067
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000334edd57f07
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000028aa7e1cee 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff80a9d4b000 - 0xffffffa0a9d4b000
. PGZ : 0xffffff80a9d4b000 - 0xffffff80b1d4c000
. VM : 0xffffff80b1d4c000 - 0xffffff857d6e5000
. RO : 0xffffff857d6e5000 - 0xffffff8716a18000
. GEN0 : 0xffffff8716a18000 - 0xffffff8be23b1000
. GEN1 : 0xffffff8be23b1000 - 0xffffff90add4a000
. GEN2 : 0xffffff90add4a000 - 0xffffff95796e3000
. GEN3 : 0xffffff95796e3000 - 0xffffff9a4507d000
. DATA : 0xffffff9a4507d000 - 0xffffffa0a9d4b000
Metadata: 0xffffff8071d3b000 - 0xffffff8091d3b000
Bitmaps : 0xffffff8091d3b000 - 0xffffff80a9d3b000
panic(cpu 17 caller 0xffffff801ddcaf19): "kind == NEW && refcnt = -1\n" @jobj.c:4068
Panicked task 0xffffff954c810670: 290 threads: pid 0: kernel_task
Backtrace (CPU 17), panicked thread: 0xffffff8bb4db5aa0, Frame : Return Address
0xffffffcb8ee03770 : 0xffffff801aa79a3d
0xffffffcb8ee037c0 : 0xffffff801abdca16
0xffffffcb8ee03800 : 0xffffff801abcbd83
0xffffffcb8ee03850 : 0xffffff801aa19a90
0xffffffcb8ee03870 : 0xffffff801aa79e0d
0xffffffcb8ee03990 : 0xffffff801aa795c6
0xffffffcb8ee039f0 : 0xffffff801b314a83
0xffffffcb8ee03ae0 : 0xffffff801ddcaf19
0xffffffcb8ee03b50 : 0xffffff801ddca39e
0xffffffcb8ee03d00 : 0xffffff801dd9c1f8
0xffffffcb8ee03fa0 : 0xffffff801aa1919e
Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1934.141.2)[721020CF-BF5F-3DEF-9F3A-AFE4205CD53E]@0xffffff801dd0d000->0xffffff801de8bfff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[6E6AB947-75F7-344F-97FE-F1A9A803D2F2]@0xffffff801bfb2000->0xffffff801bfbbfff
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[DCCE5AA9-462A-34BB-A905-A4CEB8DF45E2]@0xffffff801bfc8000->0xffffff801bfcdfff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[0BBEF1B6-3879-3835-9993-30FB5B22F3A7]@0xffffff801c4d4000->0xffffff801c4dbfff
dependency: com.apple.iokit.IOStorageFamily(2.1)[63189A2A-E19C-3F1E-96EF-95B7DB154785]@0xffffff801d77c000->0xffffff801d792fff
dependency: com.apple.kec.corecrypto(12.0)[5C997179-2E95-341F-A88B-07977BCCB606]@0xffffff801dec5000->0xffffff801df45fff
dependency: com.apple.security.AppleImage4(4.2.0)[8E7BE283-81FC-3565-A114-F692370A8969]@0xffffff801c04f000->0xffffff801c067fff

Process name corresponding to current thread (0xffffff8bb4db5aa0): kernel_task
Boot args: -no_compat_check agdpmod=pikera chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21G920

Kernel version:
Darwin Kernel Version 21.6.0: Wed Oct 4 23:55:28 PDT 2023; root:xnu-8020.240.18.704.15~1/RELEASE_X86_64
Kernel UUID: CA525A92-20FF-38D2-AB16-E64095531D5A
KernelCache slide: 0x000000001a800000
KernelCache base: 0xffffff801aa00000
Kernel slide: 0x000000001a810000
Kernel text base: 0xffffff801aa10000
__HIB text base: 0xffffff801a900000
System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 3679939410763
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000358cd7b4021
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000001fc00947ae 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff807cf70000 - 0xffffffa07cf70000
. PGZ : 0xffffff807cf70000 - 0xffffff8084f71000
. VM : 0xffffff8084f71000 - 0xffffff855090a000
. RO : 0xffffff855090a000 - 0xffffff86e9c3d000
. GEN0 : 0xffffff86e9c3d000 - 0xffffff8bb55d6000
. GEN1 : 0xffffff8bb55d6000 - 0xffffff9080f6f000
. GEN2 : 0xffffff9080f6f000 - 0xffffff954c908000
. GEN3 : 0xffffff954c908000 - 0xffffff9a182a2000
. DATA : 0xffffff9a182a2000 - 0xffffffa07cf70000
Metadata: 0xfffffff553149000 - 0xfffffff573149000
Bitmaps : 0xfffffff573149000 - 0xfffffff58b149000
 

flat4

Contributor
Jul 14, 2009
290
84
Mine started to do the same an eventually it would not post. thru the help of the forum and spare cpu tray i was able to get it back

I cleaned the board every little spot and re pasted everything including the north bridge.
 
  • Like
Reactions: kkinto

kkinto

macrumors regular
Original poster
Apr 29, 2011
228
63
Ok thanks. It’s just constantly rebooting now in a loop.



EDIT -SOLVED OK finally seem to have solved the problem. Somehow the boot (sata) SSD got corrupted and became a mac killer. I pulled all drives out to take it to service technician and realised that it started just fine without them! No more restart loop. I couldnt see video but it was probably flashing the ? folder. Anyway. The moment I put the system SSD in I was back to restart loop. I put all other drives back, no problem. Got OC running again via Mojave and now on my backup Moneterey on NVMe its all good again. Tried putting the SSD in a dock to see if I could diagnose it with drive-dx but aas soon as I powered up the dock it killed the Mac - screen lost power and had to hard restart. Even though dock is via USB3 card it will kill the Mac anytime Ihave that ssd in there and create a reboot loop if its there on startup. So the SSD is a mac killer and I guess it needs to be replaced. Never had a problem like this before where an HD being connected would not allow Mac to startup! Anyway, I had thought I had mac board/ram/CPU/PSU type hardware issues but fortunately something easily replaced.
 
Last edited:

tsialex

Contributor
Jun 13, 2016
13,454
13,601
Ok thanks. It’s just constantly rebooting now in a loop.



EDIT -SOLVED OK finally seem to have solved the problem. Somehow the boot (sata) SSD got corrupted and became a mac killer. I pulled all drives out to take it to service technician and realised that it started just fine without them! No more restart loop. I couldnt see video but it was probably flashing the ? folder. Anyway. The moment I put the system SSD in I was back to restart loop. I put all other drives back, no problem. Got OC running again via Mojave and now on my backup Moneterey on NVMe its all good again. Tried putting the SSD in a dock to see if I could diagnose it with drive-dx but aas soon as I powered up the dock it killed the Mac - screen lost power and had to hard restart. Even though dock is via USB3 card it will kill the Mac anytime Ihave that ssd in there and create a reboot loop if its there on startup. So the SSD is a mac killer and I guess it needs to be replaced. Never had a problem like this before where an HD being connected would not allow Mac to startup! Anyway, I had thought I had mac board/ram/CPU/PSU type hardware issues but fortunately something easily replaced.

Some people doubt that it's even possible, but happens. I've had the same issue three or four times in the last 13 years, only once with a DVD and the rest with HDD and SSDs.

The first thing that I check when the Mac Pro starts to misbehave and KP right after POST are the DIMMs LEDs and then the SATA devices. Usually one of the two devices is defective.
 
  • Like
Reactions: kkinto

kkinto

macrumors regular
Original poster
Apr 29, 2011
228
63
Some people doubt that it's even possible, but happens. I've had the same issue three or four times in the last 13 years, only once with a DVD and the rest with HDD and SSDs.

The first thing that I check when the Mac Pro starts to misbehave and KP right after POST are the DIMMs LEDs and then the SATA devices. Usually one of the two devices is defective.
Thanks.

Yes, its real! I tested it by plugging the ssd into a usb adapter and connected it to a mac mini and a macbook pro. It killed both of them as well. Immediate video loss and reboot with KP warning.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.