From: Leo Li <sunpeng.li@amd.com>
To: Michele Palazzi <sysdadmin@m1k.cloud>
Cc: amd-gfx@lists.freedesktop.org, harry.wentland@amd.com,
alexander.deucher@amd.com, christian.koenig@amd.com,
siqueira@igalia.com, "Michel Dänzer" <michel.daenzer@mailbox.org>,
"Shengyu Qu" <wiagn233@outlook.com>
Subject: Re: [PATCH 1/1] drm/amd/display: complete cursor vblank events immediately
Date: Mon, 16 Mar 2026 14:39:04 -0400 [thread overview]
Message-ID: <7a148774-3364-4ce2-9f55-2e77889bfb53@amd.com> (raw)
In-Reply-To: <51219a7b-eeec-43f2-a335-06710809415c@m1k.cloud>
On 2026-03-16 11:17, Michele Palazzi wrote:
>> took me a while to get the umr output after the timeout (taken within 1 second from the flip timeout)
>>
>> https://pastebin.com/dz4tkfDV
>>
>>
>
> actually there were 3 dumps in rapid succession, here you have all 3 for completeness
>
> 16 mar 15.33 umr_dump_20260316_153356.txt https://pastebin.com/LvYrjw5y
> 16 mar 15.35 umr_dump_20260316_153540.txt https://pastebin.com/SmSvCXva
> 16 mar 15.35 umr_dump_20260316_153550.txt https://pastebin.com/BbsWbbTN
Thanks for the dumps, looks like interrupts were disabled, which is surprising
given drm_vblank_disable_and_save() was not called. OTG0 seems to be active as
the FRAME_COUNT is incrementing.
Does force-enabling the VSTARTUP interrupt on OTG0 revive the hanging display
once the timeout happens?
sudo umr --instance 1 -wb '*.dcn410.regOTG0_OTG_GLOBAL_SYNC_STATUS.VSTARTUP_INT_EN' 1
- Leo
next prev parent reply other threads:[~2026-03-16 18:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 19:16 [PATCH 1/1] drm/amd/display: complete cursor vblank events immediately Michele Palazzi
2026-02-23 15:27 ` Leo Li
2026-02-27 8:53 ` Michele Palazzi
2026-02-27 8:58 ` Michele Palazzi
2026-03-02 22:13 ` Leo Li
2026-03-03 8:17 ` Shengyu Qu
2026-03-03 19:07 ` Leo Li
2026-03-04 14:00 ` Michele Palazzi
2026-03-04 14:20 ` Leo Li
2026-03-05 22:30 ` Leo Li
2026-03-06 8:37 ` Michele Palazzi
2026-03-09 16:49 ` Michele Palazzi
2026-03-10 23:50 ` Leo Li
2026-03-11 10:16 ` Shengyu Qu
2026-03-11 10:38 ` Michele Palazzi
2026-03-11 17:56 ` Leo Li
2026-03-16 14:55 ` Michele Palazzi
2026-03-16 15:17 ` Michele Palazzi
2026-03-16 18:39 ` Leo Li [this message]
2026-03-16 18:48 ` Leo Li
2026-03-18 11:36 ` Michele Palazzi
2026-03-20 0:52 ` Leo Li
2026-03-20 1:33 ` Michele Palazzi
2026-03-31 12:57 ` Michele Palazzi
2026-02-27 19:43 ` Alex Deucher
2026-03-02 8:53 ` Michel Dänzer
2026-03-02 22:14 ` Leo Li
-- strict thread matches above, loose matches on Subject: below --
2026-02-18 0:31 Michele Palazzi
2026-02-18 9:41 ` Michel Dänzer
2026-02-18 10:09 ` Michele Palazzi
2026-02-19 11:09 ` Michel Dänzer
2026-02-19 13:08 ` Michele Palazzi
2026-02-19 13:59 ` Michel Dänzer
2026-02-19 15:56 ` Michele Palazzi
2026-02-19 16:02 ` Michel Dänzer
2026-02-20 11:10 ` Michele Palazzi
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=7a148774-3364-4ce2-9f55-2e77889bfb53@amd.com \
--to=sunpeng.li@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=harry.wentland@amd.com \
--cc=michel.daenzer@mailbox.org \
--cc=siqueira@igalia.com \
--cc=sysdadmin@m1k.cloud \
--cc=wiagn233@outlook.com \
/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