[Bug 295625] graphics/drm-612-kmod hangs on Alder Lake-S GT1 [UHD Graphics 770]

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 26 May 2026 21:15:53 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=295625

            Bug ID: 295625
           Summary: graphics/drm-612-kmod hangs on Alder Lake-S GT1 [UHD
                    Graphics 770]
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: x11@FreeBSD.org
          Reporter: jonc@chen.org.nz
             Flags: maintainer-feedback?(x11@FreeBSD.org)
          Assignee: x11@FreeBSD.org

I'm getting periodic hangs with drm-612-mod on a PC with "Alder Lake-S GT1".
The system start fine, but after using chrome for a while, the display will
hang.

The console reports:
May 27 08:37:28 stormbringer kernel: drmn0: [drm] Resetting rcs0 for preemption
time out
May 27 08:37:28 stormbringer kernel: drmn0: [drm] QSGRenderThread[102291]
context reset due to GPU hang
May 27 08:37:28 stormbringer kernel: drmn0: [drm] GPU HANG: ecode
12:1:85dffffb, in QSGRenderThread [102291]
May 27 08:37:29 stormbringer kernel: Fence expiration time out
i915-drmn0:MainThread[101912]:28!
...
May 27 08:37:32 stormbringer kernel: Fence expiration time out
i915-drmn0:MainThread[101912]:2e!
May 27 08:37:33 stormbringer kernel: Fence expiration time out
i915-drmn0:MainThread[101912]:30!
l: Fence expiration time out i915-drmn0:MainThread[101912]:3a!
May 27 08:37:36 stormbringer kernel: drmn0: [drm] Resetting rcs0 for preemption
time out


'pcicontrol -lv' reports:
...
vgapci0@pci0:0:2:0:     class=0x030000 rev=0x0c hdr=0x00 vendor=0x8086
device=0x4680 subvendor=0x1028 subdevice=0x0ac1
    vendor     = 'Intel Corporation'
    device     = 'Alder Lake-S GT1 [UHD Graphics 770]'
    class      = display
    subclass   = VGA

I reverted back to drm-66-kmod and that works without any issues.

-- 
You are receiving this mail because:
You are the assignee for the bug.