From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 221929] New: amdgpu flip_done timed out stills at ASUS ROG Strix 2022 laptop(G713RM)
Date: Fri, 28 Aug 2026 04:35:10 +0000 [thread overview]
Message-ID: <bug-221929-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=221929
Bug ID: 221929
Summary: amdgpu flip_done timed out stills at ASUS ROG Strix
2022 laptop(G713RM)
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: twyoda@gmail.com
Regression: No
Created attachment 310745
--> https://bugzilla.kernel.org/attachment.cgi?id=310745&action=edit
kernel config for version 7.0.12
The amdgpu flip_done timed out cause GUI hang starts from 7.1.x .
The last version I tried are 7.2 and 7.1.10 , the flip_done timed out happened
randomly.
I had 7.0.12 kernel which didn't cause "flip_done timed out" issue ever.
Until yesterday, I check the possible cause with Gemini. The Gemini suggest an
option setting is lower the screen fresh rate.
My laptop (ASUS G713RM) equipped with LCD screen which refresh rate up to
360Hz.
Normally I use the default refresh rate setting, that is at 360Hz refresh rate.
This high refresh rate did not cause any trouble, until I upgrade kernel to
7.1.x.
I tried almost every version of 7.1.x including 7.1.10, and the "flip_done
timed out" issue happened at random time while I was using after each boot.
Finally, I followed the suggestion of Gemini, I changed the screen refresh rate
from 360Hz to 60Hz. Using kernel 7.1.10, and it work flawlessly now.
I filed this as a bug is "Why does 7.0.12 work at 360Hz, but 7.1.x(including
7.2) doesn't".
BTW, the boot parameter for 7.0.12 is "amdgpu.dpm=1 amd_pmc.debug=1
pcie_aspm=off nvme_core.default_ps_max_latency_us=0 tpm_tis.interrupts=0
nmi_watchdog=1 mem_sleep_default=deep".
the same boot parameter set for 7.1.x always caused "flip_done timed out" issue
randomly. That including 7.1.10.
Yesterday, after I set refresh rate to 60Hz, I boot 7.1.10 with parameter
"amd_pmc.debug=1 nmi_watchdog=1" and it works perfect now. It seems the lower
refresh rate is the key.
Therefore, I think it is a regression of amdgpu related driver.
The attachment is my kernel config of version 7.0.12.
The kernel config I used for 7.1.10 is just a copy of version 7.0.12.
--
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:[~2026-08-28 4:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 4:35 bugzilla-daemon [this message]
2026-08-28 4:36 ` [Bug 221929] amdgpu flip_done timed out stills at ASUS ROG Strix G17 2022 laptop(G713RM) bugzilla-daemon
2026-08-28 5:39 ` bugzilla-daemon
2026-08-28 7:49 ` bugzilla-daemon
2026-08-28 9:09 ` bugzilla-daemon
2026-08-31 7:11 ` bugzilla-daemon
2026-08-31 7:12 ` bugzilla-daemon
2026-08-31 7:41 ` 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-221929-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox