1.40.5.8829 - Crash when transcoding HVEC on Intel Arc GPU

Plex Media Server
1

Server Version#: 1.40.5.8829
Player Version#: Web 4.135.2

Since upgrade to 1.40.5.8829, every time a user start transcoding a HEVC file, Plex Media Server crash. I see the process being restarting in systemctl and a Crash Report is generated within Plex.

h264 files are ok. It happens with all the client tested with latest player version(Web, iPad, AppleTV and Chromecast).

I have an Intel GPU (DG2 ARC 380).

I can’t find any error that seems to be related to the crash in either plex logs nor crash report. Both are attached to this topic.

Reverting back to previous version (1.40.4.8679) fixes the issue.

Please ask if you need any more informations.

Thank You

Logs.zip (71.8 KB)

2

I don’t know if it’s revelant (maybe since Intel driver are within Kernel but here is currently installed Kernel : Debian 6.9.12-1 (2024-07-27)

I am using deb package, no containerization is involve…

3

6.9 kernel is pushing it (out there) on the stability curve.

Kernels 6.5, with upcoming 6.8/6.8.1, are where the known stability is.

Whatever you get with ARC GPU , is what you get.

There is no official support for them at this time. It’s on the to-do list with the transcoder update (FFMPEG base will upgrade)

4

So Plex are recommending using EOL Kernels?

Even 6.9 will be EOL in 1 month, current non LTS Stable Kernel is 6.10.

I understand you maybe not able to test all version with all Kernels, but then you should recommend LTS’s one.

5

Plex largely follows the Ubuntu vetted LTS kernels.

AFAIK, 24.04.1 will be released with 6.8 or 6.8.1 kernel.
I apologize if that’s actually 6.9 (been OOO a few days).

You are correct, testing all the kernels is a logistic, impossible, nightmare.
We try to hit everything mainstream.

The logs you provided don’t show me anything related to playback.

The only things of value I see are:

  1. The PMS version
  2. The ARC gpu detected

The last lines are:

Aug 09, 2024 08:40:58.290 [140501648943928] DEBUG - [HttpClient/HCl#4] HTTP/2.0 (0.1s) 200 response from GET https://plex.tv/api/v2/server/users?auth_token=xxxxxxxxxxxxxxxxxxxx (reused)
Aug 09, 2024 08:40:58.291 [140501615389496] DEBUG - [HCl#6] HTTP requesting GET https://plex.tv/api/v2/server/users/subscriptions?auth_token=xxxxxxxxxxxxxxxxxxxx
Aug 09, 2024 08:40:58.325 [140501648943928] DEBUG - [HttpClient/HCl#5] HTTP/2.0 (0.1s) 200 response from GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (reused)
Aug 09, 2024 08:40:58.325 [140501653138232] DEBUG - [MediaProviderManager] discovered cloud provider (Metadata)
Aug 09, 2024 08:40:58.325 [140501653138232] DEBUG - [MediaProviderManager] loading cloud provider details (Metadata) (alive: 0)

Please forgive me but I’m not sure what I can/should do here.
ARC GPUs won’t be addressed until 1) this effort completes and 2) the transcoder upgrade (we’re currently v4 and need at least v5)

1 Like
6

TBH I didn’t even know Ubuntu vet their Kernel, I use Debian and stick to info given by The Linux Kernel Archives.

I will continue to use 1.40.4.8679 for now. It was more like a bug report than something else. But I understand, ARC is not officially supported and I should stick to LTS Kernels, it’s an understandable statement.

Thank You

7

@w1zz4

Sticking to what the Linux Kernel Archives considers EOL is usually a bit premature.

The distros always tend to run behind due to their pipeline.

The only time I advocate grabbing a specific kernel from kernel.org is if researching a specific bug. For GA stuff, it’s usually, unfortunately, above most skill levels.

If you can follow the Debian released kernel or the Ubuntu released kernel, we’ll be able to track with you.

Re the ARC, I expect the FFMPEG core in v6 to provide us what we need.
(we’ve only glimpsed at it so far and that’s premature in and of itself)

8

Oh no it’s not a self compiled Kernel from the archives, this is Debian current Kernel on Trixie,

I was talking about Kernel status (EOL, Stable, LTS) when I said I will stick to The Kernel Archives since they are the authority in this matter.

Anyway, as I said, I understand this is out of support scope and I use hardware not yet officially supported.

9

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