latze Posted October 9, 2022 Share Posted October 9, 2022 Hi, I upgraded OC from 0.6.7 to 0.8.5 and I get a panic towards the end of the boot process panic(cpu 4 caller 0xffffff801d367dbd): "System KC UUID 8DC90C99-87DE-7113-2733-C6A761606774 linked against 75887627-2022-F3DE-C4DC-44B2796340ED, but 87CD49D0-7C25-4E09-5A52-10C9FE5E491A is loaded"@/System/Volumes/Data/SWE/macOS/BuildRoots/37599d3d49/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.141.39/libkern/c++/OSKext.cpp:12953 Backtrace (CPU 4), Frame : Return Address 0xffffffc120aab4f0 : 0xffffff801cc8a21d mach_kernel : _handle_debugger_trap + 0x3fd 0xffffffc120aab540 : 0xffffff801cdd1f43 mach_kernel : _kdp_i386_trap + 0x143 0xffffffc120aab580 : 0xffffff801cdc253a mach_kernel : _kernel_trap + 0x55a 0xffffffc120aab5d0 : 0xffffff801cc2ea2f mach_kernel : _return_from_trap + 0xff 0xffffffc120aab5f0 : 0xffffff801cc89a3d mach_kernel : _DebuggerTrapWithState + 0xad 0xffffffc120aab710 : 0xffffff801cc89d33 mach_kernel : _panic_trap_to_debugger + 0x273 0xffffffc120aab780 : 0xffffff801d49beaa mach_kernel : _panic + 0x54 0xffffffc120aab7f0 : 0xffffff801d367dbd mach_kernel : __ZN6OSKext29validateKCUUIDfromPrelinkInfoEPA16_h7kc_kindP12OSDictionaryPKc + 0x47d 0xffffffc120aab910 : 0xffffff801d3658af mach_kernel : __ZN6OSKext21validateKCFileSetUUIDEP12OSDictionary7kc_kind + 0x2f 0xffffffc120aab940 : 0xffffff801d365100 mach_kernel : __ZN6OSKext12mapKCFileSetEPvmPP14mach_header_64xPmbS0_ + 0xaf0 0xffffffc120aab9c0 : 0xffffff801d37266c mach_kernel : __ZN6OSKext13loadKCFileSetEPKc7kc_kind + 0x26c 0xffffffc120aabbe0 : 0xffffff801d371e3c mach_kernel : __ZN6OSKext16loadFileSetKextsEP12OSDictionary + 0x2ec 0xffffffc120aabc40 : 0xffffff801d3703b9 mach_kernel : __ZN6OSKext13handleRequestEP4hostjPcjPS2_PjS3_S4_ + 0x13f9 0xffffffc120aabcc0 : 0xffffff801d38343b mach_kernel : _kext_request + 0x1ab 0xffffffc120aabd40 : 0xffffff801ccf3e1b mach_kernel : _host_priv_server_routine + 0x209b 0xffffffc120aabd90 : 0xffffff801cc8f89d mach_kernel : _ipc_kobject_server + 0x2fd 0xffffffc120aabe00 : 0xffffff801cc65d05 mach_kernel : _ipc_kmsg_send + 0x115 0xffffffc120aabe60 : 0xffffff801cc7d362 mach_kernel : _mach_msg_overwrite_trap + 0x2d2 0xffffffc120aabef0 : 0xffffff801cda660d mach_kernel : _mach_call_munger64 + 0x29d 0xffffffc120aabfa0 : 0xffffff801cc2f216 mach_kernel : _hndl_mach_scall64 + 0x16 Process name corresponding to current thread: kernelmanagerd Boot args: -v keepsyms=1 npci=0x2000 debug=0x100 alcid=1 Mac OS version: 20G165 Kernel version: Darwin Kernel Version 20.6.0: Mon Aug 29 04:31:06 PDT 2022; root:xnu-7195.141.39~2/RELEASE_X86_64 Kernel UUID: 36422EC9-C3B4-3EEC-AE96-AADD49023F13 KernelCache slide: 0x000000001ca00000 KernelCache base: 0xffffff801cc00000 Kernel slide: 0x000000001ca10000 Kernel text base: 0xffffff801cc10000 __HIB text base: 0xffffff801cb00000 System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94) System shutdown begun: NO Panic diags file available: YES (0x0) Hibernation exit count: 0 System uptime in nanoseconds: 31377832959 Last Sleep: absolute base_tsc base_nano Uptime : 0x00000007504eeaa1 Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000 Wake : 0x0000000000000000 0x000004e8aab290e5 0x0000000000000000 I am running on Big Sur 11.7. Any idea what my cause this? I checked and re-checked the config file, also updated the kexts. Link to comment Share on other sites More sharing options...
Allan Posted October 10, 2022 Share Posted October 10, 2022 Check your config.plist using OCValidate Take a good read here on 5T33Z0's guide: https://github.com/acidanthera/OpenCorePkg/tree/master/Utilities/ocvalidate#readme After following those instructions, put the EFI folder on a USB stick and try to boot. If it works, great! Copy/paste to your EFI partition 😃 Link to comment Share on other sites More sharing options...
latze Posted October 10, 2022 Author Share Posted October 10, 2022 Thanks for the reply @Allan, I did check it and it shows no issue. From what I understand there is a problem related to Kexts although it is strange that I can still boot with 0.6.7 just fine. Link to comment Share on other sites More sharing options...
Allan Posted October 10, 2022 Share Posted October 10, 2022 Post your EFI folder here, and we can take a look at it. Such as: PlatformInfo/Generic/MLB PlatformInfo/Generic/ROM PlatformInfo/Generic/SystemSerialNumber PlatformInfo/Generic/SystemUUID There's a tool that can made this for ya! OC Anonymizer Link to comment Share on other sites More sharing options...
latze Posted October 11, 2022 Author Share Posted October 11, 2022 Sorry, it was my mistake, I had authenticated-root disabled before and I was sure that I disabled it again after the update but somehow it was re-enabled again. The previous version of MacOs there was an option when clicking on the bluetooth icon to enable debugging and that created a file in /System/Library/LaunchDaemons to load the debug reporter. I upgraded MacOs with that option enabled but they removed it in the next versions and I had no way to disable it anymore and I was getting the disk full with bluetooth logs. So I disabled it in order to delete that file to prevent the reporter to load. Thanks for the support. Link to comment Share on other sites More sharing options...
Recommended Posts