On my ThinkPad X201 (i915kms, i5 integrated) and ThinkPad x120e (radeonkms, Wrestler Radeon HD 6310), loading the ports drm modules via kld_list in rc.conf causes a panic during boot.
Legacy modules in /boot/kernel works fine.
This is a regression in 12.2-RC1. Using kld_list worked fine on both machines with 12.1-RELEASE.
Can you show us the kld_list lines you have in each instance of /etc/rc.conf please?
What happens if you build the modules locally?
(In reply to Niclas Zeising from comment #2)
Both work fine with kmods built from source. Do we have a KBI compatibility issue from 12.1 to 12.2? If not, why don't the binary packages work on 12.2-RC1?
(In reply to Jason W. Bacon from comment #4)
I can confirm that this also happens on my Core-2 Quad system, with a Radeon HD-6450 based graphics card.
When using the drm-fbsd12.0-kmod-4.16.g20200221 package on 12.1-RELEASE-p10 everything works as usual. After upgrading to 12.2-RC3 the system panics immediately on loading radeonkms.ko. I still get a stacktrace, but it is followed by a hard hangup, so no core dump is made.
It does not matter whether I put
in /etc/rc.conf or run
directly from the shell.
When I build drm-fbsd12.0-kmod-4.16.g20200221 locally from ports, the problem does not occur and the systems functions normally.
I wonder what an end user gets to see when installing 12.2-RELEASE once it is available and then attempts to use the package.
I think I ruled out a discrepancy in "pkg" vs "make install" behavior by generating and installing my own package:
pkg remove drm-kmod
pkg install /usr/ports/packages/all/drm-kmod*
Works fine with my package and I have no tweaks in my build env.
So it seems likely that the 12.1 package is incompatible with 12.2 and we're going to have a problem until bulk builds switch over to 12.2 unless this is corrected. That would mean 3 months that 12.2 users can't install drm-kmod via pkg or freebsd-update.