Contribute
Register

Solved: Need NVRAM to store kernel panic info?

Status
Not open for further replies.
Joined
Dec 14, 2012
Messages
5
Motherboard
Gigabyte Z690 UD DDR4 V2
CPU
i7-13700K
Graphics
RX 6600 XT
So it seems I need working NVRAM to store any kernel panic info until such time as the machine can reboot and write it to a file on disk. And my machine doesn't have working NVRAM so I have EmuVariableUefi-64.efi loaded. I currently don't have the hooks in the OS setup (just got it to boot again) so that is not persisted over reboots properly. However I very much doubt that those hooks (launchd right?) would be working if the kernel has panic'ed. Which it's doing quite regularly. My GPU is working with the nvidia web drivers. I'm running 10.12.6 on the hardware in my .sig

Config.plist

What's in my clover currently:

D:\EFI\CLOVER\kexts\10.12:
15/09/2018 10:39 PM <DIR> WhateverGreen.kext
15/09/2018 10:39 PM <DIR> Lilu.kext
15/09/2018 10:39 PM <DIR> USBInjectAll.kext
15/09/2018 10:40 PM <DIR> FakeSMC.kext
15/09/2018 10:40 PM <DIR> FakeSMC_ACPISensors.kext
15/09/2018 10:40 PM <DIR> FakeSMC_CPUSensors.kext
15/09/2018 10:40 PM <DIR> FakeSMC_LPCSensors.kext

D:\EFI\CLOVER\drivers64UEFI:
24/08/2018 04:38 AM 17,216 AppleImageCodec-64.efi
24/08/2018 04:38 AM 5,280 AppleKeyAggregator-64.efi
24/08/2018 04:38 AM 2,400 AppleUITheme-64.efi
24/08/2018 04:38 AM 5,696 DataHubDxe-64.efi
24/08/2018 04:38 AM 22,528 EmuVariableUefi-64.efi
24/08/2018 04:38 AM 7,200 FirmwareVolume-64.efi
24/08/2018 04:38 AM 21,920 FSInject-64.efi
24/08/2018 04:38 AM 23,808 OsxAptioFix3Drv-64.efi
15/09/2018 11:18 AM 24,900 HFSPlus.efi
24/08/2018 04:38 AM 4,480 SMCHelper-64.efi


Not sure how to debug these panics when the dump isn't written anywhere?
 
So it seems I need working NVRAM to store any kernel panic info until such time as the machine can reboot and write it to a file on disk. And my machine doesn't have working NVRAM so I have EmuVariableUefi-64.efi loaded. I currently don't have the hooks in the OS setup (just got it to boot again) so that is not persisted over reboots properly. However I very much doubt that those hooks (launchd right?) would be working if the kernel has panic'ed. Which it's doing quite regularly. My GPU is working with the nvidia web drivers. I'm running 10.12.6 on the hardware in my .sig

Config.plist

What's in my clover currently:

D:\EFI\CLOVER\kexts\10.12:
15/09/2018 10:39 PM <DIR> WhateverGreen.kext
15/09/2018 10:39 PM <DIR> Lilu.kext
15/09/2018 10:39 PM <DIR> USBInjectAll.kext
15/09/2018 10:40 PM <DIR> FakeSMC.kext
15/09/2018 10:40 PM <DIR> FakeSMC_ACPISensors.kext
15/09/2018 10:40 PM <DIR> FakeSMC_CPUSensors.kext
15/09/2018 10:40 PM <DIR> FakeSMC_LPCSensors.kext

D:\EFI\CLOVER\drivers64UEFI:
24/08/2018 04:38 AM 17,216 AppleImageCodec-64.efi
24/08/2018 04:38 AM 5,280 AppleKeyAggregator-64.efi
24/08/2018 04:38 AM 2,400 AppleUITheme-64.efi
24/08/2018 04:38 AM 5,696 DataHubDxe-64.efi
24/08/2018 04:38 AM 22,528 EmuVariableUefi-64.efi
24/08/2018 04:38 AM 7,200 FirmwareVolume-64.efi
24/08/2018 04:38 AM 21,920 FSInject-64.efi
24/08/2018 04:38 AM 23,808 OsxAptioFix3Drv-64.efi
15/09/2018 11:18 AM 24,900 HFSPlus.efi
24/08/2018 04:38 AM 4,480 SMCHelper-64.efi


Not sure how to debug these panics when the dump isn't written anywhere?

You cannot get KP reports in NVRAM with EmuVariableUefi-64.efi.
It requires native NVRAM.
Try removing EmuVariableUefi-64.efi.
 
You cannot get KP reports in NVRAM with EmuVariableUefi-64.efi.
It requires native NVRAM.
Try removing EmuVariableUefi-64.efi.

I've removed that and now it hasn't KP'd all night. Hmmmm. I think I'll wait and see. Hopefully it just runs stable.
 
Try removing EmuVariableUefi-64.efi.

This indeed fixes the NVRAM so I get panic reports on reboot. Seems the kernel is very sensitive to which USB port I plug the wifi adapter into.
 
Status
Not open for further replies.
Back
Top