-
Notifications
You must be signed in to change notification settings - Fork 44
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
NVMeFix Kernel Panic #1803
Labels
Comments
Looks like dying NVMe or PCI slot to be honest. I see that ASPM is already disabled for this NVMe, so not much I can suggest. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
I get kernel panic when trying to work with a disk. The time before the kernel panic is always different.
My hardware:
An interesting point is that the specifications for the ssd indicate 3.3v 2.8a power, which gives the maximum theoretical power = 9.24w.
The smartmontools utility return the power state with a maximum power of 6w.
(With and without NVMeFIX)
I can also cause kernel panic by measuring the disk speed with the software Blackmagic Disk Speed Test.
If I measure the speed in a system installed on sata ssd, then nmve ssd simply turns off. And if I measure in a system installed on nvme ssd, then panic happens, and not always the same, examples of kernel panics in attachments).
Another confusing moment from the log is that NVMeFix cannot get the oem-product, oem-vendor, oem-board variables from Lilu.
I tried to include the ExposeSensitiveData(=8) setting in config.plist(opencore) - it didn't help, I can get the variables, but Lilu cannot detect them for transfer to NVMeFix.
I tried the solution described in #1193 - not work.(im used forceRenderStandby=0 argument in boot-args).
Also in the BIOS there is a setting RC6 (Render Standby) = Disable
I using last version of opencore and lilu kexts.
Attachments:
Lilu_1.5.6_20.5.txt
EFI.zip
smartctl_wd_sn_750.txt
panics.zip
ioreg.zip
Best regards,
Anton Zhivov.
The text was updated successfully, but these errors were encountered: