Intel ARC Transcoding failure

[viggy96]

GPU's GuC/HuC firmware loading has failed.

Check https://jellyfin.org/docs/general/admini...pu-support

https://jellyfin.org/docs/general/admini...e-on-linux

I've already checked GuC and HuC. When I run the commands to check the status, they appear to be running correctly.
sudo cat /sys/kernel/debug/dri/1/gt0/uc/guc_info

GuC firmware: i915/dg2_guc_70.bin
status: RUNNING
version: found 70.20.0
uCode: 409856 bytes
RSA: 384 bytes
GuC status 0x8002f034:
Bootrom status = 0x1a
uKernel status = 0xf0
MIA Core status = 0x2
Scratch registers:
0: 0x0
1: 0xb03d7
2: 0x42c800
3: 0x4
4: 0x40
5: 0x3a0
6: 0x56a50005
7: 0x0
8: 0x0
9: 0x0
10: 0x0
11: 0x0
12: 0x0
13: 0x0
14: 0x0
15: 0x0

GuC logging stats:
Relay full count: 0
DEBUG: flush count          0, overflow count          0
CRASH: flush count          0, overflow count          0
CAPTURE: flush count        74, overflow count          0
CT enabled
H2G Space: 2852
Head: 306
Tail: 306
G2H Space: 12284
Head: 320
Tail: 320
GuC Submission API Version: 1.9.0
GuC Number Outstanding Submission G2H: 0
GuC tasklet count: 0
Requests in GuC submit tasklet:

Global scheduling policies:
  DPC promote time  = 500000
  Max num work items = 15
  Flags              = 0

sudo cat /sys/kernel/debug/dri/1/gt0/uc/huc_info

HuC firmware: i915/dg2_huc_gsc.bin
status: RUNNING
version: found 7.10.3
uCode: 0 bytes
RSA: 0 bytes
HuC status: 0x00164001

---

I do see these errors repeating in dmesg | grep "i915":

[369568.292626] Fence expiration time out i915-0000:83:00.0:vf#0:0[172986]:4!
[369575.839717] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:10:e75ffefe, in vf#0:0 [172986]
[369575.839745] i915 0000:83:00.0: [drm] vf#0:0[172986] context reset due to GPU hang
[369581.302844] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:4:a77ffefe, in av:h264:df0 [173341]
[369581.302872] i915 0000:83:00.0: [drm] av:h264:df0[173341] context reset due to GPU hang
[369587.254425] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:4:a77ffefe, in av:h264:df0 [173341]
[369587.254453] i915 0000:83:00.0: [drm] av:h264:df0[173341] context reset due to GPU hang
[369593.270410] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:4:a77ffefe, in av:h264:df0 [173341]
[369593.270439] i915 0000:83:00.0: [drm] av:h264:df0[173341] context reset due to GPU hang
[369612.534503] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:4:a77ffefe, in av:h264:df0 [173697]
[369612.534532] i915 0000:83:00.0: [drm] av:h264:df0[173697] context reset due to GPU hang
[369618.551027] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:4:a77ffefe, in av:h264:df0 [173697]
[369618.551056] i915 0000:83:00.0: [drm] av:h264:df0[173697] context reset due to GPU hang
[369624.502370] i915 0000:83:00.0: [drm] GPU HANG: ecode 12:4:a77ffefe, in av:h264:df0 [173697]
[369624.502399] i915 0000:83:00.0: [drm] av:h264:df0[173697] context reset due to GPU hang

---

It appears that the file you intend to play contains unusual data that the hardware decoder encounters an issue with.

This happens with many files though, not just the one I've shown as an example.