-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kernel Panic in IONVMeFamily on BS11.3 beta and later #1577
Comments
I guess your hardware is no longer supported. |
That is strange as I t is an OWC Aura P2. |
@vit9696 Can I load from OC
Which one will the system use? Should I block first the kext in Kernel/Block? |
Currently there is no way to replace one kext with another. They will conflict. You will need to patch out the class name. Like CtlnaAHCI. CC @khronokernel @dhinakg |
Vit meant to rely here but accidentally replied in another thread it seems:
And yeah as Vit mentioned, injecting the kext won't work and currently blocking is unavailable as well (#1553). So currently the only way to get this to work is to patch out any conflicting symbols similar to what we've done for CtlnaAHCIPort.kext, IO80211Mojave, etc The main concern however is whether there's other dependancies that rely on IONVMeFamily so you may need to patch and inject them as well |
This is one of the issues related to the infamous intermittent 11.3/11.4 MacPro5,1/MacPro4,1 boot hang/kernel panic. I've seen this panic myself from time to time. Along with a few others and just random boot instability. I really wish i had the skills to get to the bottom of this, I've tried running the kasan kernel and it found an issue with PMLog (below), disabled that with io flags then the kasan kernel couldn't get past a kernel panic: HPET not assigned to cpu23. Then tried the development kernel, it's the best so far as long as my keyboard/mouse/hub is disconnect. It's a very odd bug and hard to track down. |
Nvmefix is loaded, but does not prevent panic. I had to revert back to 11.2.3 to be able to boot.
The text was updated successfully, but these errors were encountered: