public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hamza Mahfooz <someguy@effective-light.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: dri-devel@lists.freedesktop.org,
	"Timur Kristóf" <timur.kristof@gmail.com>,
	"Michel Dänzer" <michel.daenzer@mailbox.org>,
	"Xaver Hugl" <xaver.hugl@kde.org>,
	"Harry Wentland" <harry.wentland@amd.com>,
	"Leo Li" <sunpeng.li@amd.com>,
	"Rodrigo Siqueira" <siqueira@igalia.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"Kenneth Feng" <kenneth.feng@amd.com>,
	"Ivan Lipski" <ivan.lipski@amd.com>,
	"Alex Hung" <alex.hung@amd.com>,
	"Tom Chung" <chiahsuan.chung@amd.com>,
	"Melissa Wen" <mwen@igalia.com>,
	"Michel Dänzer" <mdaenzer@redhat.com>,
	"Fangzhi Zuo" <Jerry.Zuo@amd.com>,
	amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] drm/amdgpu: implement page_flip_timeout() supporty
Date: Mon, 9 Feb 2026 17:53:23 -0500	[thread overview]
Message-ID: <aYplYyf6Pp20lOAD@hal-station> (raw)
In-Reply-To: <8c5ed6e7-e2e3-4aba-9b3c-bc1609765d14@amd.com>

On Mon, Feb 09, 2026 at 10:36:23AM +0100, Christian König wrote:
> Well that might work but is even worse than a GPU reset.
> 
> Have you tried to just signal the page flip as done?
> 

I have tried that actually and it didn't work in my case (outside of
your contrived scenario [1], though forcing a full modeset should take
care of that case regardless).

Though, I strongly suspect a firmware hang with the issue that I'm
seeing since I get DMCUB errors before the timeout. i.e.:

amdgpu 0000:06:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
[...]
amdgpu 0000:06:00.0: [drm] *ERROR* [CRTC:364:crtc-0] flip_done timed out


[1] https://lore.kernel.org/r/30f2480d-016f-417e-9ddf-7805e4943e7b@amd.com/

  reply	other threads:[~2026-02-09 23:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 23:58 [PATCH v2 1/2] drm: introduce KMS recovery mechanism Hamza Mahfooz
2026-02-06 23:58 ` [PATCH v2 2/2] drm/amdgpu: implement page_flip_timeout() support Hamza Mahfooz
2026-02-09  9:36   ` Christian König
2026-02-09 22:53     ` Hamza Mahfooz [this message]
2026-02-09  9:35 ` [PATCH v2 1/2] drm: introduce KMS recovery mechanism Christian König
2026-02-09 23:04   ` Hamza Mahfooz
2026-02-10  8:26     ` Christian König

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=aYplYyf6Pp20lOAD@hal-station \
    --to=someguy@effective-light.com \
    --cc=Jerry.Zuo@amd.com \
    --cc=airlied@gmail.com \
    --cc=alex.hung@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=chiahsuan.chung@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=ivan.lipski@amd.com \
    --cc=kenneth.feng@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mdaenzer@redhat.com \
    --cc=michel.daenzer@mailbox.org \
    --cc=mripard@kernel.org \
    --cc=mwen@igalia.com \
    --cc=simona@ffwll.ch \
    --cc=siqueira@igalia.com \
    --cc=sunpeng.li@amd.com \
    --cc=timur.kristof@gmail.com \
    --cc=tzimmermann@suse.de \
    --cc=xaver.hugl@kde.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