Jump to content

Persistent panic at login - Acer v5-571PG


kylon
 Share

15 posts in this topic

Recommended Posts

Hi,

 

this laptop is running sierra 10.12.5 and clover 4077 (now 4097) in uefi mode.

 

kexts (up to date): hwsensors kexts, applealc kexts, codec commander, voodoops2, realtekRTL, acpiBatteryManager, backlightInjector (L\E), patched atheros40 (S\L\E).

 

acpi files and config are attached.

 

There is a persistent panic after i type my password on every boot, i hope someone can help me to fix it.

I attached the panic log in panic.txt.

 

Also, if you find something wrong in my config please let me know.

 

thanks

  • Like 1
Link to comment
Share on other sites

because it does not work on this lap

there s a panic on 2nd stage boot with that value, i can only set 0x01660008 or 0x01660009

 

i have no log for that because it reboots after the panic, the flag "do not reboot on panic" seems useless for this

  • Like 1
Link to comment
Share on other sites

 

The latest versions of clover inject the correct FB

You can try with only inect intel 
Rebuild cache and reboot

 

 

No luck, shutdown on 2nd stage...

 

 

Can you add keepsyms=1 as a boot arg?

 

yea, what file do you need?

thanks

 

in many cases, hwsensors kexts cause many problems, panic at boot and others

use IntelPowerGadget

attachicon.gifIntel® Power Gadget SIERRA.zip

 

thanks

 

i never had problems with hwsensors and it was working in 10.11

 

anyway i also tried slice hwsensors3 kexts and the panic is the same

Link to comment
Share on other sites

seems the same

 

nvram is not working, i need emuVariable to boot os x.

how can i clear the nvram? deleting nvram.txt has no effect

 

with debug=0x144 the screen with a shutdown icon is shown

i press any key to skip and boot os x

 

i also had a fatal panic

panic(cpu 0 caller 0xffffff80003ff2dd): Kernel trap at 0xffffff8000083707f, type 13=general protection, registers:FakeSMC: 13 preconfigured keys addedFakeSMC: 5 keys exported by Clover EFISuperIODevice: [Fatal] Found unsupported chip! ITE sequence ID=0xffff, Windond sequence ID=0xfc11Kernel Extension in backtrace:org.netkas.driver.FakeSMC(1426.0)
Edit: seems the fakesmc error was caused by lpcsensors.

 

The Panic is not fixed.

Link to comment
Share on other sites

I just wiped my hdd and i installed el capitan with clover 3333 (this is the rev i was using an year ago to boot el capitan with no issues) and i have the old acpi+config files for el capitan.

 

The problem is that the panic is still there and the panic says macOS sierra.

 

This is nonsense.

 

Where are these panics stored?

I also cleared my nvram and i did a bios reset

 

Thanks

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

here the dump

i would like to know why you removed generate C/P states and drop ssdt.

i don t have a custom ssdt for the cpu and the oem ssdt are useless (nvidia optimus, cpu and ptid).

 

anyway in legacy mode i don t have the panic and i can t switch to uefi again without breaking my current installation.

 

thanks

Link to comment
Share on other sites

 Share

×
×
  • Create New...