Serious Intel DRM issues

freezr

freezr

Hi guys, I opened a most focused thread because the issue is spread across the whole system.
With the latest update of drm-kmod the system is totally unstable and compromised, when the GPU hangs even rebooting becomes problematic. Now this is affecting my daily job and operations.

Here is the issue:
Code: 
[drm] Got Intel graphics stolen memory base 0x7c800000, size 0x3c00000
drmn0: <drmn> on vgapci0
vgapci0: child drmn0 requested pci_enable_io
vgapci0: child drmn0 requested pci_enable_io
drmn0: [drm] Found ALDERLAKE_P/ADL-N (device ID 46d1) display version 13.00 stepping D0
drmn0: successfully loaded firmware image 'i915/adlp_dmc.bin'
lkpi_iic0: <LinuxKPI I2C> on drmn0
lkpi_iic1: <LinuxKPI I2C> on drmn0
lkpi_iic2: <LinuxKPI I2C> on drmn0
lkpi_iic3: <LinuxKPI I2C> on drmn0
lkpi_iic4: <LinuxKPI I2C> on drmn0
lkpi_iic5: <LinuxKPI I2C> on drmn0
lkpi_iic6: <LinuxKPI I2C> on drmn0
lkpi_iic7: <LinuxKPI I2C> on drmn0
lkpi_iic8: <LinuxKPI I2C> on drmn0
drmn0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20)
[drm] Initialized i915 1.6.0 for drmn0 on minor 0
VT: Replacing driver "efifb" with new "drmfb".
name=drmn0 id=i915drmfb flags=0x0 stride=7680
drmn0: [drm] GPU HANG: ecode 12:1:85dfbfff, in Renderer [103421]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[103421] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:859ffffb, in Xvnc [100280]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Xvnc[100280] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:859ffffb, in Xvnc [100280]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Xvnc[100280] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:859ffffb, in python3.12 [102144]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] python3.12[102144] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:859ffffb, in Xvnc [100280]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Xvnc[100280] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:84df9ffc, in Renderer [101201]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[101201] context reset due to GPU hang
Fence expiration time out i915-drmn0:Renderer[101201]:1214!
Fence expiration time out i915-drmn0:Renderer[101201]:1216!
drmn0: [drm] GPU HANG: ecode 12:1:86d8ffe0, in python3.12 [102144]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] python3.12[102144] context reset due to GPU hang
Fence expiration time out i915-drmn0:python3.12[102144]:4!
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] inkscape[102148] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in inkscape [102148]
Fence expiration time out i915-drmn0:inkscape[102148]:ea!
Fence expiration time out i915-drmn0:inkscape[102148]:ec!
Fence expiration time out i915-drmn0:inkscape[102148]:ee!
drmn0: [drm] GPU HANG: ecode 12:1:859ffffb, in inkscape [102148]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] inkscape[102148] context reset due to GPU hang
Fence expiration time out i915-drmn0:Renderer[101201]:4!
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[101201] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in Renderer [101201]
drmn0: [drm] GPU HANG: ecode 12:1:85dfffff, in inkscape [102148]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] inkscape[102148] context reset due to GPU hang
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] inkscape[102148] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in inkscape [102148]
drmn0: [drm] GPU HANG: ecode 12:1:859ffffb, in python3.12 [102144]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] python3.12[102144] context reset due to GPU hang
Fence expiration time out i915-drmn0:python3.12[102144]:4!
Fence expiration time out i915-drmn0:python3.12[102144]:6!
Fence expiration time out i915-drmn0:Renderer[103421]:4!
Fence expiration time out i915-drmn0:Renderer[103421]:6!
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[103421] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in Renderer [103421]

These frequent blocks are affecting my schedules seriously, I wonder if I should try to install a newer version from the ports tree meanwhile.
I guess that I am not the only one with this issue.

Any help is really appreciated! 🙏
 
My settings:

Code: 
# System / kernel
uname -a
freebsd-version -kru
FreeBSD gpc 15.1-RELEASE-p5 FreeBSD 15.1-RELEASE-p5 releng/15.1-n283639-893c7c99b60d GENERIC amd64
15.1-RELEASE-p5

# GPU hardware
pciconf -lv | grep -A3 -i vga
vgapci0@pci0:0:2:0:    class=0x030000 rev=0x00 hdr=0x00 vendor=0x8086 device=0x46d1 subvendor=0x0301 subdevice=0x02f3
    vendor     = 'Intel Corporation'
    device     = 'Alder Lake-N [UHD Graphics]'
    class      = display
    subclass   = VGA
none0@pci0:0:10:0:    class=0x118000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x467d subvendor=0x0000 subdevice=0x0000
    vendor     = 'Intel Corporation'
    device     = 'Platform Monitoring Technology'

# Graphics stack packages
pkg info | grep -iE "mesa|picom|drm|libglvnd|xorg-server|xf86-video"
drm-612-kmod-6.12.85.1501000_2 Direct Rendering Manager (DRM) GPU drivers
drm-kmod-20260508              Direct Rendering Manager (DRM) GPU drivers metaport
gpu-firmware-kmod-20260519,1   Firmware modules for the drm-kmod drivers
libdrm-2.4.134,1               Direct Rendering Manager library and headers
libglvnd-1.7.0                 GL Vendor-Neutral Dispatch library
linux-rl9-dri-25.2.7           Mesa libGL runtime libraries (Rocky Linux 9.8)
linux-rl9-libdrm-2.4.128       Rocky Linux Direct Rendering Manager runtime
linux-rl9-libglvnd-1.3.4_1     GL Vendor-Neutral Dispatch library (Rocky Linux 9.6)
mesa-demos-9.0.0               OpenGL demos distributed with Mesa
mesa-dri-26.2.2                OpenGL hardware acceleration drivers for DRI2+
mesa-libs-26.2.2               OpenGL libraries that support GLX and EGL clients
picom-13                       Lightweight X11 compositor
xf86-video-scfb-0.0.7_2        X.Org syscons display driver
xf86-video-vesa-2.6.0          X.Org vesa display driver
xorg-server-21.1.25,1          X.Org X server and related programs

# OpenGL / renderer
glxinfo | grep -E "OpenGL vendor|OpenGL renderer|OpenGL version|direct rendering"
direct rendering: Yes
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) Graphics (ADL-N)
OpenGL version string: 4.6 (Compatibility Profile) Mesa 26.2.2

# Xorg
cat /usr/local/etc/X11/xorg.conf.d/20-intel.conf
 
Section "Device"
    Identifier "Card0"
    Driver     "intel"
    Option      "TearFree"        "false"
    Option      "TripleBuffer"    "false"
    Option      "SwapbuffersWait" "false"
#    Option      "AccelMethod"     "sna"
EndSection

# Loaded GPU kernel modules
kldstat | grep -iE "drm|i915|ttm"
10    1 0xffffffff85200000   24a410 i915kms.ko
11    2 0xffffffff8500f000    9f430 drm.ko
16    1 0xffffffff850c3000     c358 ttm.ko
 
freezr there have been multiple reports that point to an issue with the current build of drm-612-kmod for intel hardware. Most users seem fine with 66 (I think your hardware will be supported), if not try these commits for graphics/drm-612-kmod (from newest to oldest):
  • 7e420adaf6ef0f70fe2b05a4148490af41a0d707
  • e50c876e295af951485b605b8cb9bf567b6c23e1
The culprit appears to be some LinuxKPI code that moved around (maybe).
 
fahrenheit

Thanks, it is what I did, I installed drm-66-kmod, I hope everything is going fine now. 🤞🤞🤞
However drm-612-kmod is the default driver thus is a serious thing.
 
That's crazy. I upgraded, and it pulled drm-612-kmod, and KDE wouldn't load. I rolled to drm-61-kmod, and KDE loads again now. Cost me some headache :(
 
For me kmod 612 on 15-STABLE with intel Xe Alderlake on Wayland (sway) has been pretty solid. Transitioned to pkgbase so I can move between RELEASE and STABLE boot environments with ease.
 
Espionage724 said:
I've only been able to use 61 or 515 for a year UHD 630 and HD 530; 66+ randomly freezes on Xfce without composting, i915kms load before log-in, and Wine games (OGL and Wine + DXVK Vulkan)

I used kernel 7.0 and rolling stuff (Mesa + Wine staging) openSUSE TW same hardware, GNOME Wayland + Xfce Xorg no problem
Click to expand...
For all the good it may do, please at least open tickets on the drm-kmod github repo. Both 6.1 and 6.6 have same exact new commits since january and the same upstream version since then, so the differences are:

* actual differences in drm code between 6.1 and 6.6
* linuxkpi changes

I'm going with kpi changes.
 
hi

#1 on 2026-10-10 Quarterly repo was updated to 2026Q4 which is targeted on FreeBSD 15.1. If any of you are running 15.0 you need to upgrade to 15.1 to continue using Quarterly Repo. The installation of drm-612-kmod is one of the results of transitioning to 15.1. ( se /usr/ports/graphics/drm-kmod/Makefile )

#2 If you mix binary userland and KMODs thats been compiled with different O/S version . ( 15.0 = 1500068 , 15.1= 1501000 ) then you will have issues of some sort. Make sure that you dont mix kmods for diffrent Freebsd versions.

#3 pkg info | egrep "nvidia|drm" will list your graphics kmods , check that they are all for the same O/S version.

#4 if You are running Freebsd 15.1 and find an old KMOD branded 1500068, delete it and re-install it.
 
freezr said:
I am on PKGbase with default settings. The driver has issues and it is already reported on the Github page.
Click to expand...

Well, Im running 15-1-p5 with wayland and plasma which needs the DRM susbsystem to work
Im not using the Intel GPU , but using Nvidia . drm.ko is loaded int to the kernel and works.
Its possible ofcourse that the issues is with the Intel GPU .


$ uname -a
FreeBSD trx50 15.1-RELEASE-p5 FreeBSD 15.1-RELEASE-p5 releng/15.1-n283639-893c7c99b60d GENERIC amd64

$ pkg info | egrep "drm|nvidia"
drm-612-kmod-6.12.85.1501000_2 Direct Rendering Manager (DRM) GPU drivers
libdrm-2.4.134,1 Direct Rendering Manager library and headers
nvidia-driver-595.99.02_1 NVIDIA graphics driver userland
nvidia-drm-612-kmod-595.99.02.1501000_1 NVIDIA DRM Kernel Module
nvidia-drm-kmod-595.99.02 NVIDIA DRM kernel module
nvidia-kmod-595.99.02.1501000 NVIDIA graphics driver kernel module
nvidia-settings-595.99.02 Display Control Panel for NVIDIA graphics
nvidia-xconfig-595.99.02 NVIDIA graphics X configuration utility

$ kldstat | grep drm
7 1 0xffffffff83868000 14a20 nvidia-drm.ko
8 1 0xffffffff8387d000 9f430 drm.ko
 

Attachments

  • Screenshot_20261020_212036.png
    Screenshot_20261020_212036.png
    225.7 KB · Views: 26
After upgrading my desktop 2 days ago, I too started getting the GPU hang errors with my desktop grinding to a halt, requiring either a reboot or killing Xorg. I then reverted to drm-66 by running "pkg install drm-66-kmod" and I still get the GPU hangs. Have not had this happen before the update.
Code: 
$ uname -a
FreeBSD desktop 15.1-RELEASE-p6 FreeBSD 15.1-RELEASE-p6 releng/15.1-n283643-95719d8a895b GENERIC amd64

$ pkg info | egrep "drm|nvidia"
drm-66-kmod-6.6.25.1501000_11  Direct Rendering Manager (DRM) GPU drivers
gpu-firmware-kmod-20260519,1   Firmware modules for the drm-kmod drivers
libdrm-2.4.134,1               Direct Rendering Manager library and headers

$ kldstat | grep drm 
 4    2 0xffffffff83e4b000    9f430 drm.ko

$ doas dmesg|grep drm
[drm] Got Intel graphics stolen memory base 0x6c800000, size 0x3c00000
drmn0: <drmn> on vgapci0
vgapci0: child drmn0 requested pci_enable_io
vgapci0: child drmn0 requested pci_enable_io
lkpi_iic0: <LinuxKPI I2C> on drmn0
lkpi_iic1: <LinuxKPI I2C> on drmn0
lkpi_iic2: <LinuxKPI I2C> on drmn0
lkpi_iic3: <LinuxKPI I2C> on drmn0
lkpi_iic4: <LinuxKPI I2C> on drmn0
lkpi_iic5: <LinuxKPI I2C> on drmn0
lkpi_iic6: <LinuxKPI I2C> on drmn0
lkpi_iic7: <LinuxKPI I2C> on drmn0
lkpi_iic8: <LinuxKPI I2C> on drmn0
drmn0: successfully loaded firmware image 'i915/adls_dmc_ver2_01.bin'
drmn0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
lkpi_iic9: <LinuxKPI I2C> on drm1
lkpi_iic10: <LinuxKPI I2C> on drm3
lkpi_iic11: <LinuxKPI I2C> on drm5
lkpi_iic12: <LinuxKPI I2C> on drm7
[drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
VT: Replacing driver "efifb" with new "drmfb".
name=drmn0 id=i915drmfb flags=0x0 stride=7680
[drm] Got Intel graphics stolen memory base 0x6c800000, size 0x3c00000
drmn0: <drmn> on vgapci0
vgapci0: child drmn0 requested pci_enable_io
vgapci0: child drmn0 requested pci_enable_io
drmn0: [drm] Found ALDERLAKE_S (device ID 4690) display version 12.00 stepping C0
drmn0: [drm] *ERROR* Failed to disable qgv points (0xffffffdd) points: 0x30d
lkpi_iic0: <LinuxKPI I2C> on drmn0
lkpi_iic1: <LinuxKPI I2C> on drmn0
lkpi_iic2: <LinuxKPI I2C> on drmn0
lkpi_iic3: <LinuxKPI I2C> on drmn0
lkpi_iic4: <LinuxKPI I2C> on drmn0
lkpi_iic5: <LinuxKPI I2C> on drmn0
lkpi_iic6: <LinuxKPI I2C> on drmn0
lkpi_iic7: <LinuxKPI I2C> on drmn0
lkpi_iic8: <LinuxKPI I2C> on drmn0
drmn0: successfully loaded firmware image 'i915/adls_dmc_ver2_01.bin'
drmn0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
lkpi_iic9: <LinuxKPI I2C> on drm1
lkpi_iic10: <LinuxKPI I2C> on drm3
lkpi_iic11: <LinuxKPI I2C> on drm5
lkpi_iic12: <LinuxKPI I2C> on drm7
[drm] Initialized i915 1.6.0 for drmn0 on minor 0
VT: Replacing driver "efifb" with new "drmfb".
name=drmn0 id=i915drmfb flags=0x0 stride=7680
drmn0: [drm] GPU HANG: ecode 12:1:85df9fff, in MainThread [101086]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Xorg[101086] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85df9fff, in MainThread [101086]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] MainThread[101086] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:8698ffe0, in MainThread [101086]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] MainThread[101086] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dfbfff, in Renderer [102131]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[102131] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:87d7affe, in cool-retro-term [101317]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] cool-retro-term[101317] context reset due to GPU hang
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[102131] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in Renderer [102131]
drmn0: [drm] GPU HANG: ecode 12:1:85df9ffd, in Renderer [126825]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[126825] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dfffff, in MainThread [101257]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Xorg[101257] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dfffff, in MainThread [101257]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] MainThread[101257] context reset due to GPU hang
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[126825] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in Renderer [126825]
Fence expiration time out i915-drmn0:Renderer[126825]:4!
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in MainThread [101257]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] MainThread[101257] context reset due to GPU hang
[drm] Got Intel graphics stolen memory base 0x6c800000, size 0x3c00000
drmn0: <drmn> on vgapci0
vgapci0: child drmn0 requested pci_enable_io
vgapci0: child drmn0 requested pci_enable_io
drmn0: [drm] Found ALDERLAKE_S (device ID 4690) display version 12.00 stepping C0
drmn0: successfully loaded firmware image 'i915/adls_dmc_ver2_01.bin'
drmn0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
drmn0: [drm] *ERROR* Failed to disable qgv points (0xffffffc4) points: 0x30d
lkpi_iic0: <LinuxKPI I2C> on drmn0
lkpi_iic1: <LinuxKPI I2C> on drmn0
lkpi_iic2: <LinuxKPI I2C> on drmn0
lkpi_iic3: <LinuxKPI I2C> on drmn0
lkpi_iic4: <LinuxKPI I2C> on drmn0
lkpi_iic5: <LinuxKPI I2C> on drmn0
lkpi_iic6: <LinuxKPI I2C> on drmn0
lkpi_iic7: <LinuxKPI I2C> on drmn0
lkpi_iic8: <LinuxKPI I2C> on drmn0
lkpi_iic9: <LinuxKPI I2C> on drm1
lkpi_iic10: <LinuxKPI I2C> on drm3
lkpi_iic11: <LinuxKPI I2C> on drm5
lkpi_iic12: <LinuxKPI I2C> on drm7
[drm] Initialized i915 1.6.0 for drmn0 on minor 0
VT: Replacing driver "efifb" with new "drmfb".
name=drmn0 id=i915drmfb flags=0x0 stride=7680
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Xorg[101077] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in MainThread [101077]
drmn0: [drm] GPU HANG: ecode 12:1:85df9fff, in Renderer [112797]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[112797] context reset due to GPU hang
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] MainThread[101077] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in MainThread [101077]
drmn0: [drm] GPU HANG: ecode 12:1:85dfffff, in Renderer [111477]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[111477] context reset due to GPU hang
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] MainThread[101077] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in MainThread [101077]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[112797] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in Renderer [112797]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[111477] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in Renderer [111477]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[112797] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[111477] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in Renderer [111477]
drmn0: [drm] GPU HANG: ecode 12:1:85dfffff, in MainThread [102404]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Xorg[102404] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:84df9ffc, in Renderer [118696]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[118696] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dfffff, in MainThread [102404]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] MainThread[102404] context reset due to GPU hang
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[118696] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in Renderer [118696]
Fence expiration time out i915-drmn0:Renderer[118696]:4!
Fence expiration time out i915-drmn0:Renderer[118696]:6!
drmn0: [drm] GPU HANG: ecode 12:1:859ffffb, in Renderer [122094]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[122094] context reset due to GPU hang
Fence expiration time out i915-drmn0:Renderer[122094]:11a0!
Fence expiration time out i915-drmn0:MainThread[102404]:2!
Fence expiration time out i915-drmn0:MainThread[102404]:6!
Fence expiration time out i915-drmn0:MainThread[102404]:4!
Fence expiration time out i915-drmn0:MainThread[102404]:8!
Fence expiration time out i915-drmn0:MainThread[102404]:a!
Fence expiration time out i915-drmn0:MainThread[102404]:c!
Fence expiration time out i915-drmn0:MainThread[102404]:e!
Fence expiration time out i915-drmn0:MainThread[102404]:10!
Fence expiration time out i915-drmn0:MainThread[102404]:12!
Fence expiration time out i915-drmn0:MainThread[102404]:14!
Fence expiration time out i915-drmn0:MainThread[102404]:16!
Fence expiration time out i915-drmn0:MainThread[102404]:18!
Fence expiration time out i915-drmn0:MainThread[102404]:1a!
Fence expiration time out i915-drmn0:MainThread[102404]:1c!
drmn0: [drm] GPU HANG: ecode 12:1:86d8ffe0, in MainThread [102404]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] MainThread[102404] context reset due to GPU hang
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] Renderer[118696] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffffb, in Renderer [118696]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] MainThread[101546] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffdfb, in MainThread [101546]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] MainThread[101546] context reset due to GPU hang
drmn0: [drm] GPU HANG: ecode 12:1:85dffefb, in MainThread [101546]
drmn0: [drm] Resetting rcs0 for preemption time out
drmn0: [drm] GPU HANG: ecode 12:1:85dffdfb
 
Yes I had drm-612-kmod, presumably installed by updates.

Package repositories:
Code: 
FreeBSD-ports: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/quarterly",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}
FreeBSD-ports-kmods: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/kmods_quarterly_${VERSION_MINOR}",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}
FreeBSD-base: {
  url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_${VERSION_MINOR}",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkgbase-${VERSION_MAJOR}",
  enabled: no
}
 
On my secondary desktop (Intel Ivybridge), I was frequently experiencing hangs/freezes with drm-latest-kmod.

Apart from using an older version of the i915 driver, another suggestion I stumbled across was trying to disable rc6 power saving. It doesn't seem clear that this can be done on FreeBSD though. Unsure about the naming, I tried both of the following (separately) in /boot/loader.conf:

Code: 
#compat.linuxkpi.enable_rc6="0" # should the i915 prefix be used? Testing below
#compat.linuxkpi.i915_enable_rc6="0" # neither of these rc6 lines seems to have any effect

However, using the following compat.linuxkpi settings in /boot/loader.conf seems to have mitigated the issue. More time will tell...

Code: 
compat.linuxkpi.i915_enable_dc="0"
compat.linuxkpi.i915_enable_psr="0"
compat.linuxkpi.i915_enable_fbc="0"
compat.linuxkpi.i915_disable_power_well="1"
compat.linuxkpi.i915_modeset="1"
compat.linuxkpi.i915_verbose_state_checks="0"
compat.linuxkpi.i915_error_capture="0"

See this thread:

Intel i915 rc6 power saving enabled
 
My experience so far (on a 12th Gen Intel i5-12500T, GPU: Alder Lake-S GT1 [UHD Graphics 770] running LXQt 2.4.0) has been that the hangs happen during use (while a window is trying to show or close). GUI and mouse hang, or the mouse gets very choppy, and I have to drop to console (and wait a long time for this to happen) before being able to kill Xorg and restart. I think my hangs may be exacerbated by me using Cool Retro Term as my terminal app, it is running all the time and makes use of the GPU constantly to render it's effects. I once saw cool-retro-term mentioned in the GPU hang messages from dmesg. To be sure, cool-retro-term is not the cause of this problem, as it happens even after I switched to QTerminal, which I don't think makes use of GPU.
 
teekay said:
My experience so far (on a 12th Gen Intel i5-12500T, GPU: Alder Lake-S GT1 [UHD Graphics 770] running LXQt 2.4.0) has been that the hangs happen during use (while a window is trying to show or close). GUI and mouse hang, or the mouse gets very choppy, and I have to drop to console (and wait a long time for this to happen) before being able to kill Xorg and restart. I think my hangs may be exacerbated by me using Cool Retro Term as my terminal app, it is running all the time and makes use of the GPU constantly to render it's effects. I once saw cool-retro-term mentioned in the GPU hang messages from dmesg. To be sure, cool-retro-term is not the cause of this problem, as it happens even after I switched to QTerminal, which I don't think makes use of GPU.
Click to expand...

In my case (wayland, labwc and foot terminal), I would be dumped back into the console after a few seconds and when I ran a terminal "reset" command I could start labwc again.
 
Are you seeing this behaviour regardless of the compositor used (wlroots based vs plasma vs hyprland etc..) ?

In my loader.conf I only have this config hw.i915kms.disable_power_well=0 , no other tweaks with respect to i1915. The terminal app I use, alacritty , does GPU rendering , works on both X11 and Wayland.
 
siladi said:
Are you seeing this behaviour regardless of the compositor used (wlroots based vs plasma vs hyprland etc..) ?

In my loader.conf I only have this config hw.i915kms.disable_power_well=0 , no other tweaks with respect to i1915. The terminal app I use, alacritty , does GPU rendering , works on both X11 and Wayland.
Click to expand...

Have only used with labwc (wlroots-based) and the foot terminal emulator which is not gpu-accelerated. The compat.linuxkpi
tweaks I listed above seem to be helping so far.
 
paulw said:
Have only used with labwc (wlroots-based) and the foot terminal emulator which is not gpu-accelerated. The compat.linuxkpi
tweaks I listed above seem to be helping so far.
Click to expand...
if these settings help your igpu is bitten by one of the power bugs of intel hardware. those also happen on linux (which is obvious due the flags existence). Though on linux you get access to more recent kernel versions and don't also have to deal with the translation to the freebsd kernel.
while i like the handbook and the forum helps freebsd would benefit of a better wiki (at least at the gentoo level)
 
I had a very similar problem on a ThinkPad T470 (Intel HD 620, Kaby Lake) with FreeBSD 15.1 and drm-612-kmod. The picture would freeze while the cursor and audio kept working, and the kernel log showed the same "GPU HANG ... Resetting rcs0 for preemption time out" cascades. It happened under heavy memory use. Going back to drm-66-kmod fixed it for me.
 
teekay said:
After upgrading my desktop 2 days ago, I too started getting the GPU hang errors with my desktop grinding to a halt, requiring either a reboot or killing Xorg. I then reverted to drm-66 by running "pkg install drm-66-kmod" and I still get the GPU hangs. Have not had this happen before the update.
Click to expand...

I may have forgotten to reboot after reverting to drm-66-kmod. To be sure I rebooted and my machine has been fine for the last 2 days, so I think going back to drm-66-kmod worked for me.
 
You must log in or register to reply here.
Back
Top