my experience (may be useful)No problems with macOS 12.4 so far on my purist's setup. Tested Siri without any related issues. Sleep and wake work perfectly fine as always.
my experience (may be useful)No problems with macOS 12.4 so far on my purist's setup. Tested Siri without any related issues. Sleep and wake work perfectly fine as always.
Anonymous UUID: 5AF5F9A8-1EDC-07B8-BFC6-84B11B127A96
Thu May 19 23:20:40 2022
panic(cpu 6 caller 0xffffff801d7b3e54): System KC UUID 0CDF77CA-1424-F9F4-FA07-E29395DA2222 linked against 1F381DC9-0429-2E71-F677-73CDBA95EC09, but E9DCAC16-794F-5BF8-8BAB-24D8490C1570 is loaded @OSKext.cpp:13029
Panicked task 0xffffff905735c3b0: 4 threads: pid 105: kernelmanagerd
Backtrace (CPU 6), panicked thread: 0xffffff9522b2a000, Frame : Return Address
0xffffffb0c375b4c0 : 0xffffff801d081c8d mach_kernel : _handle_debugger_trap + 0x41d
0xffffffb0c375b510 : 0xffffff801d1e1596 mach_kernel : _kdp_i386_trap + 0x116
0xffffffb0c375b550 : 0xffffff801d1d0963 mach_kernel : _kernel_trap + 0x4d3
0xffffffb0c375b5a0 : 0xffffff801d021a70 mach_kernel : _return_from_trap + 0xe0
0xffffffb0c375b5c0 : 0xffffff801d08205d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffb0c375b6e0 : 0xffffff801d081816 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffb0c375b740 : 0xffffff801d915163 mach_kernel : _panic + 0x84
0xffffffb0c375b830 : 0xffffff801d7b3e54 mach_kernel : __ZN6OSKext29validateKCUUIDfromPrelinkInfoEPA16_h7kc_kindP12OSDictionaryPKc + 0x484
0xffffffb0c375b950 : 0xffffff801d7b19ef mach_kernel : __ZN6OSKext21validateKCFileSetUUIDEP12OSDictionary7kc_kind + 0x2f
0xffffffb0c375b980 : 0xffffff801d7b13d5 mach_kernel : __ZN6OSKext12mapKCFileSetEPvmPP14mach_header_64xPmbS0_ + 0xa55
0xffffffb0c375b9f0 : 0xffffff801d7bf286 mach_kernel : __ZN6OSKext13loadKCFileSetEPKc7kc_kind + 0x246
0xffffffb0c375bc10 : 0xffffff801d7bea05 mach_kernel : __ZN6OSKext16loadFileSetKextsEP12OSDictionary + 0x2e5
0xffffffb0c375bc70 : 0xffffff801d7bce32 mach_kernel : __ZN6OSKext13handleRequestEP4hostjPcjPS2_PjS3_S4_ + 0x13b2
0xffffffb0c375bcf0 : 0xffffff801d7d08bc mach_kernel : _kext_request + 0x1ac
0xffffffb0c375bd80 : 0xffffff801d0fa8eb mach_kernel : _host_priv_server_routine + 0x209b
0xffffffb0c375bdd0 : 0xffffff801d05c9ab mach_kernel : _ipc_kmsg_send + 0x46b
0xffffffb0c375be60 : 0xffffff801d0731f9 mach_kernel : _mach_msg_overwrite_trap + 0x2c9
0xffffffb0c375bef0 : 0xffffff801d1b35aa mach_kernel : _mach_call_munger64 + 0x1ea
0xffffffb0c375bfa0 : 0xffffff801d022256 mach_kernel : _hndl_mach_scall64 + 0x16
Process name corresponding to current thread (0xffffff9522b2a000): kernelmanagerd
Boot args: keepsyms=1 debug=0x100 ipc_control_port_options=0 -revasset
Mac OS version:
21F79
Kernel version:
Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:22 PDT 2022; root:xnu-8020.121.3~4/RELEASE_X86_64
Kernel UUID: 3C587984-4004-3C76-8ADF-997822977184
KernelCache slide: 0x000000001ce00000
KernelCache base: 0xffffff801d000000
Kernel slide: 0x000000001ce10000
Kernel text base: 0xffffff801d010000
__HIB text base: 0xffffff801cf00000
System model name: MacPro5,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0
System uptime in nanoseconds: 10890300100
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000002891cd48f
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000001b899c2fa7 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: 0xffffff80561bf000 - 0xffffffa0561bf000
. PGZ : 0xffffff80561bf000 - 0xffffff80571c0000
. VM : 0xffffff80571c0000 - 0xffffff8523c26000
. RO : 0xffffff8523c26000 - 0xffffff86bd4f2000
. GEN0 : 0xffffff86bd4f2000 - 0xffffff8b89f58000
. GEN1 : 0xffffff8b89f58000 - 0xffffff90569be000
. GEN2 : 0xffffff90569be000 - 0xffffff9523424000
. GEN3 : 0xffffff9523424000 - 0xffffff99efe8b000
. DATA : 0xffffff99efe8b000 - 0xffffffa0561bf000
Metadata: 0xffffffb09ad91000 - 0xffffffb0bad91000
Bitmaps : 0xffffffb0bad91000 - 0xffffffb0bdd91000
Model: MacPro5,1, BootROM 144.0.0, 4 processors, Quad-Core Intel Xeon, 2.8 GHz, 8 GB, SMC 1.39f11
Graphics: AMD Radeon R9 280X, AMD Radeon R9 280X, PCIe, 3072 MB
Memory Module: DIMM 1, 2 GB, DDR3 ECC, 1066 MHz, 0x0198, 0x393930353437322D3030322E4130314C4620
Memory Module: DIMM 2, 2 GB, DDR3 ECC, 1066 MHz, 0x0198, 0x393930353437322D3030322E4130314C4620
Memory Module: DIMM 3, 2 GB, DDR3 ECC, 1066 MHz, 0x0198, 0x393930353437322D3030322E4130314C4620
Memory Module: DIMM 4, 2 GB, DDR3 ECC, 1066 MHz, 0x0198, 0x393930353437322D3030322E4130314C4620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 5.2.7f4 15858, 3 services, 23 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en3
PCI Card: AMD Radeon R9 280X, Display Controller, Slot-1
PCI Card: AMD Radeon R9 280X, ATY,HamachiParent, Slot-1
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: Samsung SSD 860 EVO 500GB, 500,11 GB
Serial ATA Device: ST3500312CS, 500,11 GB
USB Device: Hub
USB Device: Keyboard Hub
USB Device: Apple Optical USB Mouse
USB Device: Apple Keyboard
USB Device: Apple Cinema HD Display
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
FireWire Device: built-in_hub, Up to 800 Mb/sec
Thunderbolt Bus:
Interesting, I also had weird crashes/boot loop today while testing OCLP 0.4.5 and High Sierra with my single CPU tray with a W3565 while with my X5690 tray I didn't had the crashes/boot loop. Lost my lunch time trying to track what was going on - when I was too hungry, I just nuked the ESP.Today I set up a pretty basic MP5.1 (2.8x4) and R9/280X. Clean 12.4 on
1st boot was fine, 2nd I got a boot loop with this kernel panic:
Code:Anonymous UUID: 5AF5F9A8-1EDC-07B8-BFC6-84B11B127A96 Thu May 19 23:20:40 2022 panic(cpu 6 caller 0xffffff801d7b3e54): System KC UUID 0CDF77CA-1424-F9F4-FA07-E29395DA2222 linked against 1F381DC9-0429-2E71-F677-73CDBA95EC09, but E9DCAC16-794F-5BF8-8BAB-24D8490C1570 is loaded @OSKext.cpp:13029 Panicked task 0xffffff905735c3b0: 4 threads: pid 105: kernelmanagerd Backtrace (CPU 6), panicked thread: 0xffffff9522b2a000, Frame : Return Address 0xffffffb0c375b4c0 : 0xffffff801d081c8d mach_kernel : _handle_debugger_trap + 0x41d 0xffffffb0c375b510 : 0xffffff801d1e1596 mach_kernel : _kdp_i386_trap + 0x116 0xffffffb0c375b550 : 0xffffff801d1d0963 mach_kernel : _kernel_trap + 0x4d3 0xffffffb0c375b5a0 : 0xffffff801d021a70 mach_kernel : _return_from_trap + 0xe0 0xffffffb0c375b5c0 : 0xffffff801d08205d mach_kernel : _DebuggerTrapWithState + 0xad 0xffffffb0c375b6e0 : 0xffffff801d081816 mach_kernel : _panic_trap_to_debugger + 0x2b6 0xffffffb0c375b740 : 0xffffff801d915163 mach_kernel : _panic + 0x84 0xffffffb0c375b830 : 0xffffff801d7b3e54 mach_kernel : __ZN6OSKext29validateKCUUIDfromPrelinkInfoEPA16_h7kc_kindP12OSDictionaryPKc + 0x484 0xffffffb0c375b950 : 0xffffff801d7b19ef mach_kernel : __ZN6OSKext21validateKCFileSetUUIDEP12OSDictionary7kc_kind + 0x2f 0xffffffb0c375b980 : 0xffffff801d7b13d5 mach_kernel : __ZN6OSKext12mapKCFileSetEPvmPP14mach_header_64xPmbS0_ + 0xa55 0xffffffb0c375b9f0 : 0xffffff801d7bf286 mach_kernel : __ZN6OSKext13loadKCFileSetEPKc7kc_kind + 0x246 0xffffffb0c375bc10 : 0xffffff801d7bea05 mach_kernel : __ZN6OSKext16loadFileSetKextsEP12OSDictionary + 0x2e5 0xffffffb0c375bc70 : 0xffffff801d7bce32 mach_kernel : __ZN6OSKext13handleRequestEP4hostjPcjPS2_PjS3_S4_ + 0x13b2 0xffffffb0c375bcf0 : 0xffffff801d7d08bc mach_kernel : _kext_request + 0x1ac 0xffffffb0c375bd80 : 0xffffff801d0fa8eb mach_kernel : _host_priv_server_routine + 0x209b 0xffffffb0c375bdd0 : 0xffffff801d05c9ab mach_kernel : _ipc_kmsg_send + 0x46b 0xffffffb0c375be60 : 0xffffff801d0731f9 mach_kernel : _mach_msg_overwrite_trap + 0x2c9 0xffffffb0c375bef0 : 0xffffff801d1b35aa mach_kernel : _mach_call_munger64 + 0x1ea 0xffffffb0c375bfa0 : 0xffffff801d022256 mach_kernel : _hndl_mach_scall64 + 0x16 Process name corresponding to current thread (0xffffff9522b2a000): kernelmanagerd Boot args: keepsyms=1 debug=0x100 ipc_control_port_options=0 -revasset Mac OS version: 21F79 Kernel version: Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:22 PDT 2022; root:xnu-8020.121.3~4/RELEASE_X86_64 Kernel UUID: 3C587984-4004-3C76-8ADF-997822977184 KernelCache slide: 0x000000001ce00000 KernelCache base: 0xffffff801d000000 Kernel slide: 0x000000001ce10000 Kernel text base: 0xffffff801d010000 __HIB text base: 0xffffff801cf00000 System model name: MacPro5,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: YES (0x0) Hibernation exit count: 0 System uptime in nanoseconds: 10890300100 Last Sleep: absolute base_tsc base_nano Uptime : 0x00000002891cd48f Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000 Wake : 0x0000000000000000 0x0000001b899c2fa7 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: 0xffffff80561bf000 - 0xffffffa0561bf000 . PGZ : 0xffffff80561bf000 - 0xffffff80571c0000 . VM : 0xffffff80571c0000 - 0xffffff8523c26000 . RO : 0xffffff8523c26000 - 0xffffff86bd4f2000 . GEN0 : 0xffffff86bd4f2000 - 0xffffff8b89f58000 . GEN1 : 0xffffff8b89f58000 - 0xffffff90569be000 . GEN2 : 0xffffff90569be000 - 0xffffff9523424000 . GEN3 : 0xffffff9523424000 - 0xffffff99efe8b000 . DATA : 0xffffff99efe8b000 - 0xffffffa0561bf000 Metadata: 0xffffffb09ad91000 - 0xffffffb0bad91000 Bitmaps : 0xffffffb0bad91000 - 0xffffffb0bdd91000 Model: MacPro5,1, BootROM 144.0.0, 4 processors, Quad-Core Intel Xeon, 2.8 GHz, 8 GB, SMC 1.39f11 Graphics: AMD Radeon R9 280X, AMD Radeon R9 280X, PCIe, 3072 MB Memory Module: DIMM 1, 2 GB, DDR3 ECC, 1066 MHz, 0x0198, 0x393930353437322D3030322E4130314C4620 Memory Module: DIMM 2, 2 GB, DDR3 ECC, 1066 MHz, 0x0198, 0x393930353437322D3030322E4130314C4620 Memory Module: DIMM 3, 2 GB, DDR3 ECC, 1066 MHz, 0x0198, 0x393930353437322D3030322E4130314C4620 Memory Module: DIMM 4, 2 GB, DDR3 ECC, 1066 MHz, 0x0198, 0x393930353437322D3030322E4130314C4620 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.22) Bluetooth: Version 5.2.7f4 15858, 3 services, 23 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en3 PCI Card: AMD Radeon R9 280X, Display Controller, Slot-1 PCI Card: AMD Radeon R9 280X, ATY,HamachiParent, Slot-1 Serial ATA Device: HL-DT-ST DVD-RW GH41N Serial ATA Device: Samsung SSD 860 EVO 500GB, 500,11 GB Serial ATA Device: ST3500312CS, 500,11 GB USB Device: Hub USB Device: Keyboard Hub USB Device: Apple Optical USB Mouse USB Device: Apple Keyboard USB Device: Apple Cinema HD Display USB Device: BRCM2046 Hub USB Device: Bluetooth USB Host Controller FireWire Device: built-in_hub, Up to 800 Mb/sec Thunderbolt Bus:
any insights?
This is literally the same Kernel panic I'm experiencing.I have a problem with 'Voice Control' on my macPro with 12.4 on my macPro 5,1 with OpenCore 0.8.0
I updated to 12.4 two days ago. It seemed to be a perfect update on each of my macs, however this morning I discovered that I could not select 'Voice Control' in System Preferences without triggering an immediate shutdown, followed by a pause of about 5 minutes, then a reboot.
(My intention was to go on to check the box to enable text editing with speech - which has been working well on previous versions of Monterey)
Voice control is working on my M1 mba running 12.4 and on my Z77MX-QUO-AOS Hackintosh; just not on my OpenCore 0.8.0 macPro 5,1
Firstly has anyone else suffered this? (before I post my plist or any other files).
I just tried enabling Voice Control and can confirm the issue.Firstly has anyone else suffered this? (before I post my plist or any other files).
Thanks for getting back to me ... at least I know I haven't done something to cause it.I just tried enabling Voice Control and can confirm the issue.
I've never used Voice Control. Are you saying that Voice Control used to work in macOS up to Monterey 12.3.x but, all of a sudden, will cause a kernel panic on a cMP after the 12.4 update? If so, I guess an OpenCore tweak or kext should fix the situation in a few weeks?I just tried enabling Voice Control and can confirm the issue.
The report does not really say it's being caused by Siri; just that the running process when the crash happened was related to Siri. I've had multiple similar panics (all of them type 6 - invalid opcode) on my 5,1 since installing 12.4, some with that "com.apple.siri.embeddedspeech" process, others with mdworker processes, and the common thread in all of them is the kernel extensions in the backtrace. They're always the same, starting with "com.apple.filesystems.apfs" and ending with "com.apple.AppleFSCompression.AppleFSCompressionTypeZlib". If I had to guess, I'd guess that something was changed in the filesystem code in 12.4 that causes it to, under some circumstances, execute an instruction that's unsupported on the 5,1.I am getting the same issue, it goes dark before Kernel Panic.
It's random, most of the time I'm able to use it normally so I'm unsure what's exactly triggering this
Report says it's being caused by siri. Attaching my log
I also decided to check,I just tried enabling Voice Control and can confirm the issue.
As to me, Siri is off,The report does not really say it's being caused by Siri; just that the running process when the crash happened was related to Siri. I've had multiple similar panics (all of them type 6 - invalid opcode) on my 5,1 since installing 12.4, some with that "com.apple.siri.embeddedspeech" process, others with mdworker processes, and the common thread in all of them is the kernel extensions in the backtrace. They're always the same, starting with "com.apple.filesystems.apfs" and ending with "com.apple.AppleFSCompression.AppleFSCompressionTypeZlib". If I had to guess, I'd guess that something was changed in the filesystem code in 12.4 that causes it to, under some circumstances, execute an instruction that's unsupported on the 5,1.
The only time I've ever turned on Voice Control was to confirm this issue. According to @David403, Voice Control worked properly in previous versions of Monterey (does that include 12.3.1?). Coming up with a fix will depend on how deep the issue is and how important the feature is for people.I've never used Voice Control. Are you saying that Voice Control used to work in macOS up to Monterey 12.3.x but, all of a sudden, will cause a kernel panic on a cMP after the 12.4 update? If so, I guess an OpenCore tweak or kext should fix the situation in a few weeks?
Just to confirm it was working in 12.3.1.The only time I've ever turned on Voice Control was to confirm this issue. According to @David403, Voice Control worked properly in previous versions of Monterey (does that include 12.3.1?). Coming up with a fix will depend on how deep the issue is and how important the feature is for people.
Getting the same. I have a theory that my Time Machine backup volume is in the mix somewhere. KP twice this evening since I reattached and used my external TM volume.I also decided to check,
But curiosity killed the cat
As to me, Siri is off,
VoiceControl drivers were not installed, the download and installation went on,
and suddenly I got multiple panics and reboots, "No but compatible" and so on,
which, as it seemed to me, were eliminated by resetting SMC and NVRAM twice,
but after total reset and reboot with VoceControl OFF, after the end of the mds process and etc,
there was a panic and a reboot -
probably the installed drivers conflict with the hardware cMP 5.1, with Mac os 12.4 and with OpenCore.
so far I decided not to reinstall the system,
I just rewrote the efi opencore again,
after that, for an hour the computer has been working with running benchmarks
and does not go into reboot
random reboots are happening
I need to reinstall mac os to remove harmful drivers VoseControl!
EDITED
I deleted AVAST security (one of panic reason)
My current OC 0.8.0 with edited cdf config +TBOLT3+radeonsensor
My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w5700, nvme crucial 2tb, evo plus 1tb, TB3 alpine ridge, oc 0.8.0, mac os 12.4
No. You'll need to back up your data and reinstall a lower version of macOS to revert to 12.3.1. Maybe you have a Time Machine backup that was completed on 12.3.1 prior to upgrading to 12.4. You'd have to use that.Other than resorting to a backup, is there a recommended way to go back to Monterey 10.3.1?
Are you also experiencing kernel panics now (even without using Voice Control, Siri, or Time Machine)?Other than resorting to a backup, is there a recommended way to go back to Monterey 10.3.1?
EDIT: Naturally, I meant Monterey 12.3.1. My bad.
The way I did it was time consuming but relatively straight forward.Other than resorting to a backup, is there a recommended way to go back to Monterey 10.3.1?
EDIT: Naturally, I meant Monterey 12.3.1. My bad.
I don't use Voice Control or Siri, but do use Time Machine... however, the panics I'm seeing don't seem to implicate my Time Machine usage, as they're mostly occurring in spotlight indexing (mdworker_shared). As I mentioned further up, they always have the "com.apple.filesystems.apfs" and "com.apple.AppleFSCompression.AppleFSCompressionTypeZlib" kexts in their backtraces.Are you also experiencing kernel panics now (even without using Voice Control, Siri, or Time Machine)?
Yes, for the last two days!Are you also experiencing kernel panics now (even without using Voice Control, Siri, or Time Machine)?
OK. Something is certainly going on. But in my case (and perhaps for others as well), 12.4 has been fine so far, complicating the task. I did manage to triggering a panic by turning on Voice Control, so that is obviously something to look into. We'd have to identify the changes in 12.4 that could be causing these panics. Given the current logs, APFS could be the cause, but it seems that APFS always gets pointed at when issues come up (notably the Big Sur race condition). Any additional panic logs would be helpful.Yes, for the last two days!