-
Notifications
You must be signed in to change notification settings - Fork 85
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
NVME controller randomly locking shutdowns and generating slowdowns #53
Comments
I need to have an identical EFI as yours, specially the kexts. Cuz I might be a few commits behind in regards to the kexts you use. Unlikely that would be an issue but I rather use the exact same kexts. I've got some Crucial and Corsair ones and didn't experience any issues with them. I did a few shutdowns on my test NUC just now that has a Crucial in there, no panics. How can I reproduce the load that causes it? Maybe that can trigger the panic. This might be a combination of the NVMe fix-up kext or incompatibility. Not all NVMe will work with macOS, even with the NVMe fix-up kext. I've not had any other issues where people got panics caused by NVMe stuff when shutting down their machine. |
Just noticed you downgraded kexts, not upgraded them. I'm compiling everything from source based on the current sources. Like AppleALC and others are one version ahead of yours. When you download a release version from the official repo's you will get older versions compared to a release here. If you must change the kexts yourself (I don't understand why) then use Dortania builds, they have the latest builds based on the latest sources like I do. Or, replace everything with release builds. Don't mix it up. Weird things can happen when you run older kexts and newer kexts and a newer/older OpenCore build together as they interact a lot with each other. Most kexts we use are made by the same team of people. You can't just upgrade or downgrade one or two kexts without also doing the rest. Some newer function or bug fix may depend on other kexts being up to date too. Please try the release from the repo so I can use that release too and we're sure to use the same stuff when trying to reproduce. |
It happens with the latests repo EFI too, I noticed that CPU usage gets really high too just scrolling on web content on Safari. |
Is there any way to get a system trace while logged in? |
Not sure if I understand correctly, but if it doesn't happen with the fix-up kext disabled you can leave it disabled. If you get panics with it enabled and disabled then I'm afraid there's nothing to be done. Here's an issue with a very similar panic to yours: acidanthera/bugtracker#1286 Your Intel 600p is on the known troublemakers list: https://dortania.github.io/Anti-Hackintosh-Buyers-Guide/Storage.html -- removing it or disabling it in ACPI might be the only way to stop the panics. Not sure if it can be fixed but the ticket suggests they would need a drive to test with themselves. If you'd want to collect logs you'll need to download a debug version of the kext from their repo or Dortania site. But it might not be enough for the programmers to fix things. NVMeFix repo: https://github.com/acidanthera/nvmefix |
Please provide the follow information:
Mount latest EFI; Shutdown the os or set heavy load
BigSur 11.4 20F71
Removed std verbose and installed latest kexts from official repos (See log)
The text was updated successfully, but these errors were encountered: