Closed zeising closed 5 years ago
Looking closer, it seems like the panic happens after the load of i915kms.ko, but before load of the firmware, or at least before load of the firmware the second time. The i915kms.ko module is loaded, but the switch from efifb to the new fb has not occurred.
Delaying the boot for a bit, by sleeping for 10 seconds in /etc/rc.d/kld after every kld is loaded makes the panic disappear, or at least happen much less often.
@zeising This was fixed, right?
This is believed to be fixed with the stolen memory handling. Closing this, it can be reopened if something happens.
I experience a panic somewhere in the VM subsystem when loading i915kms.ko on my kaby lake system. CPU: intel core i7 7600U Boot: UEFI boot Version: FreeBSD ALPHA 8
The panic occurs somewhere in the VM subsystem. I have either
panic: Bad link elm 0xfffff800165a12f8 prev->next != elm
orpanic: bad pte va 8002c8000 pte 0
The panic occurs almost always. The panic only occurs when loading from rc.conf with kld_list="", loading with kldload after the system is up and I can log in works.