[Bug]: Transcoding using jellyfin-ffmpeg5 causes a system crash about media-driver HOT 5 CLOSED

I reinstalled my entire setup with Ubuntu LTS instead and the problem is gone.

from media-driver.

How about the ffmpeg transcoding? Could it reproduce by ffmpeg-vaapi or ffmpeg-qsv?

from media-driver.

Transcoding in Jellyfin using hardware acceleration causes a system crash that requires a hard reboot.

What exactly is meant by system crash?

If you mean that UI is not any more usable, that could also be a bug somewhere in the graphics stack.

If your machine stops responding e.g. to SSH, that's likely a kernel crash i.e. nothing to do with any user-space driver, like this one.

Which kernel version you're using and does it have any drivers in it that are not from your distribution?

Does crash happen also with the latest kernel?

dmesg doesn't seem to have any hardware specific information about any crashes, neither does journalctl.

dmesg is only from current boot, so it will not have anything from before reboot. If this is hard kernel crash, one may need network (or serial) console to catch kernel error messages.

from media-driver.

Transcoding in Jellyfin using hardware acceleration causes a system crash that requires a hard reboot.

What exactly is meant by system crash?

If you mean that UI is not any more usable, that could also be a bug somewhere in the graphics stack.

If your machine stops responding e.g. to SSH, that's likely a kernel crash i.e. nothing to do with any user-space driver, like this one.

The machine stops responding to SSH and the connection terminates after a short while. All running CLI applications also stop responding - btop, intel_gpu_top (I used them to monitor if the hardware acceleration is working properly). If it's not the driver's fault, then that doesn't sound too good for me..

Which kernel version you're using and does it have any drivers in it that are not from your distribution?

It's running Debian Bookworm stable using kernel version 6.1.0-20-amd64.

Does crash happen also with the latest kernel?

It's already on the latest kernel.

dmesg doesn't seem to have any hardware specific information about any crashes, neither does journalctl.

dmesg is only from current boot, so it will not have anything from before reboot. If this is hard kernel crash, one may need network (or serial) console to catch kernel error messages.

How can I record those error messages if that's the case?

from media-driver.

The machine stops responding to SSH and the connection terminates after a short while.

Ok, that's a kernel, not a user-space media driver bug. You need to report this against kernel driver.

Assuming it is indeed Intel driver bug, the correct project is this one: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues

It's running Debian Bookworm stable using kernel version 6.1.0-20-amd64.

Does crash happen also with the latest kernel?
It's already on the latest kernel.

From kernel developers point of view, 6.1 is rather old, latest upstream kernel is 6.8, with 6.9 being released soon.

from media-driver.