Kernel Panic on update to Sequoia

blitzdose

New member
AMD OS X Member
Jun 6, 2022
7
0
1
CPU:
AMD Ryzen 5 1500X
Hi,
Updated every Kext in my EFI, Updated Opencore, applied new AMD Patches, Reboot and everything still works in my 14.6 install. Tried the update to 15.4 trough system settings and when booting the installer I get the following Kernel Panic:

Code:
panic(cpu 2 caller 0xffffff8011d3ce7a): Kernel trap at 0xffffff8015804131, type = 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffff8015803fca, CR3: 0x00000001ce822000, CR4: 0x00000000003406e0
RAX: 0xffffff8015803fca, RBX: 0xfffffffb005d6f60, RCX: 0xfffffffb005d6820, RDX: 0xfffffffb005d67c0
RSP: 0xfffffffb005d6808, RBP: 0xfffffffb005d68b0, RSI: 0xfffffffb005d6f60, RDI: 0x0000000000000000
R8:  0xfffffffb005d67a0, R9:  0x0000007fed6e4000, R10: 0x000000000000000f, R11: 0xc265a0fef9ee0e7f
R12: 0x0000000000000000, R13: 0x0000000000000002, R14: 0xfffffffb005d6f60, R15: 0xfffffffb005d6f88
RFL: 0x0000000000010246, RIP: 0xffffff8015804131, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0xffffff8015803fca, Error code: 0x0000000000000003, Fault CPU: 0x2, PL: 0, VF: 2

Panicked task 0xffffff905bd03988: 1 threads: pid 1: init
Backtrace (CPU 2), panicked thread: 0xffffff905bb55598, Frame : Return Address
0xfffffffb005d60a0 : 0xffffff8011bda401 mach_kernel : _handle_debugger_trap + 0x4c1
0xfffffffb005d60f0 : 0xffffff8011d4d686 mach_kernel : _kdp_i386_trap + 0x126
0xfffffffb005d6130 : 0xffffff8011d3c81c mach_kernel : _kernel_trap + 0x75c
0xfffffffb005d61f0 : 0xffffff8011b6f971 mach_kernel : _return_from_trap + 0xc1
0xfffffffb005d6210 : 0xffffff8011bda6f7 mach_kernel : _DebuggerTrapWithState + 0x67
0xfffffffb005d6310 : 0xffffff8011bd9d7b mach_kernel : _panic_trap_to_debugger + 0x1fb
0xfffffffb005d6380 : 0xffffff80123cdccd mach_kernel : _panic + 0x81
0xfffffffb005d6470 : 0xffffff8011d3ce7a mach_kernel : _sync_iss_to_iks + 0x3fa
0xfffffffb005d6630 : 0xffffff8011d3ca29 mach_kernel : _kernel_trap + 0x969
0xfffffffb005d66f0 : 0xffffff8011b6f971 mach_kernel : _return_from_trap + 0xc1
0xfffffffb005d6710 : 0xffffff8015804131 as.vit9696.Lilu : __ZN13KernelPatcher20tempExecutableMemoryE + 0x1f1
0xfffffffb005d68b0 : 0xffffff80137d4d3e com.apple.kext.CoreTrust : _X509ChainCheckPathWithOptions + 0x1a8
0xfffffffb005d6960 : 0xffffff80137cf672 com.apple.kext.CoreTrust : _validateSignerInfoAndChain + 0x3e
0xfffffffb005d6990 : 0xffffff80137ce49f com.apple.kext.CoreTrust : _CMSParseSignerInfos + 0x3ca
0xfffffffb005d6b10 : 0xffffff80137d10eb com.apple.kext.CoreTrust : _CTParseSignerInfos + 0x64
0xfffffffb005d6b50 : 0xffffff80137d0e97 com.apple.kext.CoreTrust : _CTEvaluateAMFICodeSignatureCMS_MaxDigestType + 0x120
0xfffffffb005d71f0 : 0xffffff80137d112d com.apple.kext.CoreTrust : _CTEvaluateAMFICodeSignatureCMS + 0x29
0xfffffffb005d7240 : 0xffffff80132e08c1 com.apple.driver.AppleMobileFileIntegrity : __ZL22_vnode_check_signatureP5vnodeP5labeliP7cs_blobPjS5_ijPPcPm + 0xe80
0xfffffffb005d7500 : 0xffffff80123a585e mach_kernel : _mac_vnode_check_signature + 0xfe
0xfffffffb005d75b0 : 0xffffff8012151bc9 mach_kernel : _ubc_cs_blob_add + 0x159
0xfffffffb005d7980 : 0xffffff801219239e mach_kernel : _load_machfile + 0x227e
0xfffffffb005d7a30 : 0xffffff8012190e73 mach_kernel : _load_machfile + 0xd53
0xfffffffb005d7b50 : 0xffffff80121903cf mach_kernel : _load_machfile + 0x2af
0xfffffffb005d7c10 : 0xffffff80120e283d mach_kernel : _kctl_fill_socketinfo + 0x4cd
0xfffffffb005d7d90 : 0xffffff80120ea4d5 mach_kernel : _posix_spawn + 0x3aa5
0xfffffffb005d7e10 : 0xffffff80120ec08f mach_kernel : ___mac_execve + 0x21f
0xfffffffb005d7ea0 : 0xffffff80120ec873 mach_kernel : _load_init_program + 0x203
0xfffffffb005d7f10 : 0xffffff80120b3304 mach_kernel : _bsdinit_task + 0x84
0xfffffffb005d7f30 : 0xffffff8011bcf98c mach_kernel : _ast_taken_user + 0x10c
0xfffffffb005d7f60 : 0xffffff8011b6f93d mach_kernel : _return_from_trap + 0x8d
      Kernel Extensions in backtrace:
         com.apple.kext.CoreTrust(1.0)[F7B3FBDC-1844-332A-ADBC-8B279CC8623F]@0xffffff80137cc000->0xffffff80137d6fff
            dependency: com.apple.kec.corecrypto(14.0)[F3FAD83F-B866-3435-B339-D577046E6FDB]@0xffffff80149d4000->0xffffff8014a55fff
         com.apple.driver.AppleMobileFileIntegrity(1.0.5)[E22A51B7-37BA-3F19-B3AE-01F9128A0A9C]@0xffffff80132d0000->0xffffff801330afff
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[3F4EA64D-04C9-35D2-8CEF-7A0FBA056AD2]@0xffffff80136f0000->0xffffff80136fafff
            dependency: com.apple.kec.corecrypto(14.0)[F3FAD83F-B866-3435-B339-D577046E6FDB]@0xffffff80149d4000->0xffffff8014a55fff
            dependency: com.apple.kext.CoreTrust(1)[F7B3FBDC-1844-332A-ADBC-8B279CC8623F]@0xffffff80137cc000->0xffffff80137d6fff
            dependency: com.apple.security.AppleImage4(7.0.0)[04BF7034-A8F3-3905-AEB0-91A5C0117290]@0xffffff801315a000->0xffffff801317efff
         as.vit9696.Lilu(1.7)[DC312317-616B-357B-94C4-D54BED870339]@0xffffff80157f8000->0xffffff801587ffff

Process name corresponding to current thread (0xffffff905bb55598): init
Boot args: agdpmod=pikera debug=0x100 keepsyms=1 -amfipassbeta -v -lilubetaall -no_panic_dialog -restore -logOnCrash -rootdmg-ramdisk auth-root-dmg=file:///com.apple.installer/x86_64SURamDisk.dmg

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 24.4.0: Wed Mar 19 21:16:31 PDT 2025; root:xnu-11417.101.15~1/RELEASE_X86_64
Kernel UUID: [...]
roots installed: 0
KernelCache slide: 0x0000000011800000
KernelCache base:  0xffffff8011a00000
Kernel slide:      0x00000000118e4000
Kernel text base:  0xffffff8011ae4000
__HIB  text base: 0xffffff8011900000
System model name: [...]
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization
Hibernation exit count: 0

System uptime in nanoseconds: 1393763924
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00000000535c2f2d
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x0000001746c61035 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: 0xffffff8059d4c000 - 0xffffffa059d4c000
  . PGZ   : 0xffffff8059d4c000 - 0xffffff805dd4d000
  . VM    : 0xffffff805dd4d000 - 0xffffff852a07f000
  . RO    : 0xffffff852a07f000 - 0xffffff86c36ef000
  . GEN0  : 0xffffff86c36ef000 - 0xffffff8b8fa21000
  . GEN1  : 0xffffff8b8fa21000 - 0xffffff905bd53000
  . GEN2  : 0xffffff905bd53000 - 0xffffff9528085000
  . GEN3  : 0xffffff9528085000 - 0xffffff99f43b8000
  . DATA  : 0xffffff99f43b8000 - 0xffffffa059d4c000
  Metadata: 0xfffffffad9fee000 - 0xfffffffaf9fee000
  Bitmaps : 0xfffffffaf9fee000 - 0xfffffffafffee000
  Extra   : 0 - 0

Looks like some integrity/singature issue but tbh I have absoluetly no Idea whats wrong. Doesn't seem to come from a outdated kext or something. Also set SecureBootModel to Disabled and disabled secure boot in my Bios. If any more information is needed just tell me I will add them
 
Solution
Why are you using -lilubetaall?.
 
Apple Mobile File Integrity (AMFI) issue shown in the spoiler.

Try adding AMFIPass.kext to you /EFI/OC/Kexts folder and config.plist, use v1.4.1 or newer when installing/running Sequoia.

The kext can be downloaded from this link over at Dortania OCLP.

 
Solution
Further to @craighazan comment, remove these Boot Arguments.

-amfipassbeta -lilubetaall -no_panic_dialog -restore -logOnCrash

If they are present in your config.plist, as you don't need any of them for running macOS Sequoia.

The AMFIPass.kext is much newer and better option than using the -amfipass or -amfipassbeta boot argument.

Sequoia has been out of Beta since last September, so there is no need for you to use any beta boot arguments, if you are using a Public release version of macOS Sequoia such as 15.4.
 
  • Like
Reactions: craighazan
Try adding AMFIPass.kext to you /EFI/OC/Kexts folder and config.plist, use v1.4.1 or newer when installing/running Sequoia.

The kext can be downloaded from this link over at Dortania OCLP.
I'm an idiot :) I went and updated all my Kexts and when I googled "AMFIPass kext" I only clicked on the first link which was a forum entry with the same version I already had, so I thought there was no update. I see I was wrong, that actually fixed it, thanks!

Why are you using -lilubetaall?.
Further to @craighazan comment, remove these Boot Arguments.

-amfipassbeta -lilubetaall -no_panic_dialog -restore -logOnCrash
I was quite frustrated and tried everything the internet was suggesting, thats why the lilubetaall was still there. Remove this and amfipassbeta, the other are not in my config.plist, I'm assuming they are there because of the update install process
 
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.