Created attachment 255593 [details] Screenshot of crash dump Hi, I have a fresh 14.2-RELEASE install (technically just upgraded from 14.1-RELEASE - where the same problem happened). On booting, when I `kldload i915kms` the kernel panics immediately. I can't find the crash dump information in /var/crash or dmesg after reboot so only have the screenshot attached - also shown in this forum post where I posted about the issue: https://forums.freebsd.org/threads/crash-on-loading-i915kms-fresh-14-1-install.95927/ The key-looking part is: Fatal trap 12: page fault while in kernel mode The hardware is 13900K on an MSI Z790 board, with integrated UHD770 graphics plus 2 x Intel ARC 380 graphics cards. This happens every time, on booting up I log in as root and run `kldload i915kms` and the crash happens instantly. The install is fresh and unmodified besides installing the package system, installing drm-61-kmod, and also installing gpu-firmware-kmod (despite the error message not being able to find the firmware file). X11/Wayland/etc are not installed. The issue [on 14.1-RELEASE] first happened 22nd Nov (which was when I installed it). Happy to provide any other diagnostic information I can (may just need to know how) (NB I also had a very similar-looking crash on the same hardware with 15.0-CURRENT, some details in a post I wrongly hijacked thinking OP had the same issue; https://forums.freebsd.org/threads/latest-update-gives-fatal-trap-12-page-fault-while-in-kernel-mode-when-i915kms-ko-is-loaded.95732/#post-680420 ).
14.2 incompatibility issue with drm-kmod is noted in the 14.2 errata (but not release notes, unfortunately) https://www.freebsd.org/releases/14.2R/errata/: > drm-kmod packages compiled on FreeBSD 14.1 result in the text console being > inoperative when the kernel module is loaded. Recompiling the package from the > ports tree will restore the lost functionality. This issue will also resolve itself > after the FreeBSD 14.1 EoL, when packages for 14-STABLE will start being built on > FreeBSD 14.2-RELEASE. Can you please try rebuilding graphics/drm-kmod against your updated kernel source, and let us know if that resolves the issue. We do need to solve this in a better / holistic way, but this will hopefully get things working for you in the short term.
Back in issue 264114 - comment 8, in 2022, Kyle Evans said > I wish we had known this was an issue back in neta/rc... > we put time into diagnosing an issue with binary compatible > with the drm ports this cycle, we would have done the same for wireguard. So, not much has changed since 13.1/2 I guess. I still don't see why the ports that are sensitive to the kernel minor version number can't be tagged so that the package code can select the correct version and not have this period between version X release and EOL of version X-1 where things break in obscure ways.
(In reply to Ed Maste from comment #1) Hi, thank you. I had seen the posts about the 14.2 issues and didn't think it would apply - given I had the same crash on 14.1 before updating (before 1.42 was released); 14.1 was the vanilla unmodified install before upgrading to 14.2 to see if that would solve the problem (not realising at the time that this may further break things given the .X/EOL thing). I'll try it though, in case that's a later version of drm-kmod and perhaps the issue is solved there. Will report back.