Just FYI, some occasional image corruption in LibreOffice/Firefox and occasional gpu_hang/frozen display. Only occurs if "AccelMethod" "sna" is set, so the default is probably uxa.
Which version of FreeBSD, which version of drm-*-kmod? What happens if you use modesetting instead of xf86-video-intel?
Also, try upgrading to -CURRENT because drm-fbsd11.2-kmod and drm-fbsd12.0-kmod are unlikely to be fixed unless you provide a patch. According to the manpage SNA stands for Sandybridge's New Acceleration. GM45 (Gen4) predates Sandybridge (Gen6). Upstream has a lot of code to support gen4 and gen >= 045 in particular. However, bug 214593 disabled SNA by default due to crashes on pre-Sandybridge. If drm-kmod made SNA work but has graphical glitches then it's an improvement. This is why trying newer DRM drivers (i915kms, radeonkms, etc) even on old handware is important.
(In reply to Niclas Zeising from comment #1) In reply to Jan Beich from comment #2) Sorry for the missing info, FreeBSD 12.2-STABLE #0 r366183 amd64 $ pkg info *kmod* drm-fbsd12.0-kmod-4.16.g20200221 drm-kmod-g20190710 gpu-firmware-kmod-g20200920 $ pkg info *intel* libva-intel-driver-2.4.1 xf86-video-intel-2.99.917.909,1 SNA was very much usable for me (ioquake3 and glxgears ran fine, glxgears quite faster) since trying newer driver (thanks!), but graphical glitches in Firefox (file save menu) and LibreOffice just proved to be too much in the long run. I will try SNA with graphics/drm-current-kmod, thoght iirc it was the same behaviour. Regarding modesetting, should I just set Driver "modesetting"? If I understand correctly, it does not use intel driver, so what I would achieve by that? Should I test that?
Are you using packages or compiling drm-fbsd12.0-kmod locally? If you are using the official packages, please try to compile it locally instead. You can change the driver to modesetting, or simply remove xf86-video-intel. This snippet should work: Section "Device" Identifier "card0" Driver "modesetting" EndSection drm-current-kmod is only for use on FreeBSD current, so you need to update to that as well.
(In reply to Niclas Zeising from comment #4) Compiling. I reckon there was a time you could install current kmod on top? Sadly, this is not a system I can upgrade to -CURRENT (thought it was -CURRENT, long time ago).
(In reply to jakub_lach from comment #5) There has never been any posibility to install drm-current-kmod on systems not running CURRENT.
(In reply to Niclas Zeising from comment #6) Maybe I've thought of /usr/ports/graphics/mesa-devel then or drm-next-kmod
After upgrade from 12-STABLE to 13-STABLE, I am yet to experience any graphical glitches.
FreeBSD 13.0-ALPHA3 #0 stable/13-bb8fa72da $ pkg info *kmod* drm-fbsd13-kmod-5.4.62.g20210122_3 drm-kmod-g20190710_1 gpu-firmware-kmod-g20201213 $ pkg info *intel* libva-intel-driver-2.4.1 xf86-video-intel-2.99.917.916,1 $ pkg info *drm* drm-fbsd13-kmod-5.4.62.g20210122_3 drm-kmod-g20190710_1 libdrm-2.4.104,1
Switching to 13.0 fixed the problem, it's unlikely to have any update on drm-kmod for 12.X so closing this bug.
(In reply to Emmanuel Vadot from comment #10) Just an update - Switching to 13-STABLE did not in fact resolve the problem - commenting out Option "AccelMethod" "sna" in xorg.conf did though (whatever the default is, currently).