Xe driver crash how to contribute if possible

English Hardware
1

This crash happened (randomly?), and I would like if possible to help with a bug report or at least provide some information, but I wouldn’t know where to even start. I guess maybe submit the core dump somewhere (however I don’t know where it is…).

Aug 23 17:57:01 merlin kernel: xe 0000:00:02.0: [drm] GT0: Engine reset: engine_class=rcs, logical_mask: 0x1, guc_id=9
Aug 23 17:57:01 merlin kernel: xe 0000:00:02.0: [drm] GT0: Timedout job: seqno=2296802, lrc_seqno=2296802, guc_id=9, flags=0x0 in kwin_wayland [2979]
Aug 23 17:57:01 merlin kernel: xe 0000:00:02.0: [drm] Xe device coredump has been created
Aug 23 17:57:01 merlin kernel: xe 0000:00:02.0: [drm] Check your /sys/class/drm/card0/device/devcoredump/data

❯ inxi -GSaz
System:
  Kernel: 6.16.1-6-default arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.16.1-6-default
    root=/dev/mapper/system-root mitigations=auto security=apparmor
    xe.force_probe=a7a1 i915.force_probe=!a7a1 iommu.passthrough=1
  Desktop: KDE Plasma v: 6.4.4 tk: Qt v: N/A info: frameworks v: 6.17.0
    wm: kwin_wayland tools: avail: xscreensaver vt: 3 dm: SDDM Distro: openSUSE
    Tumbleweed 20250820
Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] vendor: Dell driver: xe
    v: kernel alternate: i915 arch: Xe process: Intel 7 (10nm) built: 2022+
    ports: active: DP-5,eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1
    bus-ID: 0000:00:02.0 chip-ID: 8086:a7a1 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
    alternate: fbdev,intel dri: iris gpu: xe d-rect: 3840x1200 display-ID: 0
  Monitor-1: DP-5 pos: right model: Samsung S24E450 serial: <filter>
    built: 2018 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 92 gamma: 1.2
    size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: eDP-1 pos: primary,left model: HKC OVERSEAS eDP-1-0x36BB
    built: 2022 res: mode: 1920x1200 hz: 60 scale: 100% (1) dpi: 161 gamma: 1.2
    size: 302x189mm (11.89x7.44") diag: 356mm (14") ratio: 16:10
    modes: 1920x1200
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.1.7 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel Iris Xe Graphics (RPL-U)
    device-ID: 8086:a7a1 memory: 30.01 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.321 layers: 1 device: 0 type: integrated-gpu name: Intel
    Iris Xe Graphics (RPL-U) driver: N/A device-ID: 8086:a7a1 surfaces: N/A
    device: 1 type: cpu name: llvmpipe (LLVM 20.1.8 256 bits) driver: N/A
    device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
2

Bugs can be reported at openSUSE Bugzilla. To login use the same credentials as for the forum.

1 Like
3

Thank you, what about the core dump? Where do I find it? I don’t think I’ll be of much help if I don’t have it.

4

Did you have a look?

5

Yes:

$ sudo file /sys/class/drm/card0/device/devcoredump/data
/sys/class/drm/card0/device/devcoredump/data: cannot open `/sys/class/drm/card0/device/devcoredump/data' (No such file or directory)
6

Hello, perhaps you could change into the directory of this path /sys/class/drm/card0/device/devcoredump/datawith the cd command one directory at a time. For instance cd sys then list it’s contents with ls -lahand if the directory named class is then shown you may proceed into that directory with cd classnext and so on.

Once in the /sys/class/drm/card0/device/devcoredump/data directory you could list the contents with ls -lah and if there are files with content you can then use an appropriate program such as kate or cat, whatever to view the content.

I am not certain of the use of the file command in this situation is necessary. Looking at manual page for file command on machine here man file

Name
file - determine file type

7

The directory can be simply browsed with a file manager…much more quicker.

8

Thank you however that path doesn’t exist…

More generally (no results):

$ sudo find /sys/class/drm/card0/device -name '*dump*'
$ sudo find /sys/class/drm/card0/device -name '*core*'
$ sudo find /sys/class/drm/card0/device -name '*xe*'

Is there a specific pattern I should be looking for the coredump’s file name?

9

I looked here Xe Device Coredump — The Linux Kernel documentation

I found the following which may help.
Coredump release:

After a coredump is generated, it stays in kernel memory until released by userspace by writing anything to it, or after an internal timer expires. The exact timeout may vary and should not be relied upon. Example to release a coredump:

$ > /sys/class/drm/card0/device/devcoredump/data
1 Like
10

Ah that explains it. I hard rebooted not long after my system froze. I was not able to switch to the TTY and didn’t know what to do.

If it was only in memory I assume the dump is gone.

I’ll keep using xe and will try waiting longer if the crash reproduces. Thank you!

11

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.