Bug #3245
closed
panic: free: guard1x fail, i915 load from loader.conf
Added by polachok about 4 years ago.
Updated 3 months ago.
Description
Same as https://bugs.dragonflybsd.org/issues/2837
It happened after I upgraded 2.8.1 release to master
DragonFly v5.9.0.756.g2e6c7-DEVELOPMENT #0: Fri Aug 21 19:51:28 MSK 2020 plhk@darkstar:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64
Files
- Status changed from New to Resolved
I'd say i915.ko is not supposed to be loaded by the loader, only afterwards. On FreeBSD it is the same (I vaguely remember there are technical reasons for this)
https://wiki.freebsd.org/Graphics says to load the module after the kernel is loaded by adding the module to kld_list in /etc/rc.comf which would become something like i915_load=YES in DragonFlyBSD.
When I tried last time to load i915, it paniced somewhere in the kernel linker, so I am assuming it's somehow related to that.
to clarify, I am talking here about the ELF loader at boot time: src/stand/boot/common/*_elf64.c. IIRC, loading i915 on FreeBSD (14) succeeded, and I've seen some updates on their boot-time ELF loader. Bringing these changes to DragonFly might fix that problem.
Also available in: Atom
PDF
Updated by 
Updated by 