From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 220642] New: amdgpu: Vblank missed when playing video using GBM on AMD Ryzen APU
Date: Wed, 08 Oct 2025 09:19:17 +0000 [thread overview]
Message-ID: <bug-220642-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220642
URL: https://github.com/xbmc/xbmc/issues/26167
Bug ID: 220642
Summary: amdgpu: Vblank missed when playing video using GBM on
AMD Ryzen APU
Product: Drivers
Version: 2.5
Kernel Version: at least 6.8.x up to current
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: eric@w-id.eu
Regression: No
Created attachment 308777
--> https://bugzilla.kernel.org/attachment.cgi?id=308777&action=edit
Screenshot of kodi with the 5fps issue
#### Description:
First, this problem is **NOT** due to kodi, I only use it to explain the
problem.
When kodi GBM plays a video, the rendering speed is always 5 fps lower than
screen framerate which causes stuttering. The problem occurs whatever the
framerate is, it is always 5 fps lower.
#### Steps to Reproduce:
1. use an AMD Ryzen APU (confirmed for AMD 5xxx/7xxx/8xxx/HX 370)
1. use a distro known to have the problem: at least ubuntu 24.04, archlinux,
gentoo. The problem occurs probably on all distros.
1. start kodi using GBM rendering (both opengl and gles versions have the
problem)
1. start playing a video (any resolution and framerate)
1. press O (uppercase o) to open debug overlay and press right to choose
system
#### Actual Results:
System rendering speed is 5 fps lower than Screen resolution framerate
#### Expected Results:
Rendering speed matchs screen resolution framerate
#### Build:
1. CPU: AMD 5xxx/7xxx/8xxx/HX 370
1. kernel version: at least since 6.8.x up to now
1. firmware: at least since 20250211 up to now
1. cpu governor and frequency: occurs on both performance and powersave, from
400MHz to 3600MHz
#### Additionnal informations:
A whole description of the problem with various tests performed by several
users can be found on issue 26167 on kodi's github
When the issue occurs, DRM debug messages always contains for each second
several lines like this one
> [drm:amdgpu_dm_crtc_vblank_control_worker [amdgpu]] Allow idle optimizations
(MALL): true
> [drm:amdgpu_dm_crtc_vblank_control_worker [amdgpu]] Allow idle optimizations
(MALL): false
The problem disappears as soon as the value remains "stuck" on true.
In the same way, when the issue is here, periodically, DRM log contains lines
like this one:
> [drm:drm_calc_timestamping_constants [drm]] crtc 79: hwmode: htotal 2750,
vtotal 1125, vdisplay 1080
> [drm:drm_calc_timestamping_constants [drm]] crtc 79: clock 74176 kHz
framedur 41708234 linedur 37073
A workaround seems to exist.
1. enable DRM debug using *echo 0xf > /sys/module/drm/parameters/debug*
1. Wait until the rendering speed is *fixed*. Each time I tried, it took less
than 10 seconds
1. Stop DRM debug using *echo 0 > /sys/module/drm/parameters/debug*
For an unknown reason, libreelec (kodi's JEOS) does not have the problem
despite using the same unpatched kernel, the same firmware and the same .config
(more details in XBMC issue)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2025-10-08 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 9:19 bugzilla-daemon [this message]
2025-10-08 15:47 ` [Bug 220642] amdgpu: Vblank missed when playing video using GBM on AMD Ryzen APU bugzilla-daemon
2025-10-08 16:25 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-220642-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.