From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: Mario Limonciello <superm1@kernel.org>
Cc: amd-gfx@lists.freedesktop.org,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH 0/3] Handle aborted suspend better
Date: Mon, 2 Jun 2025 13:22:40 +0100 [thread overview]
Message-ID: <aD2XkPjk6OfEDz2-@debian.local> (raw)
In-Reply-To: <20250602014432.3538345-1-superm1@kernel.org>
On Sun, Jun 01, 2025 at 08:44:29PM -0500, Mario Limonciello wrote:
> From: Mario Limonciello <mario.limonciello@amd.com>
>
> Chris Bainbridge reported some list corruption occurring around the
> suspend sequence when an aborted suspend occurs.
>
> I couldn't reproduce this specific problem, but when I tried I found
> some other issues where the cached DM state isn't properly destroyed.
>
> This is because there isn't a complete() callback to match the prepare()
> callback used by amdgpu. Normally the PM core will call complete() after
> every suspend attempt (succesful or not).
>
> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/4280
>
> Mario Limonciello (3):
> drm/amd: Add support for a complete pmops action
> drm/amd/display: Stop storing failures into adev->dm.cached_state
> drm/amd/display: Destroy cached state in complete() callback
>
> drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 +
> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 22 +++
> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 2 +-
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 125 +++++++++++-------
> drivers/gpu/drm/amd/include/amd_shared.h | 1 +
> 5 files changed, 103 insertions(+), 48 deletions(-)
>
> --
> 2.43.0
>
I tested with 30 suspends and the dm_prepare_suspend /
amdgpu_device_prepare error did not appear. The list corruption error
remain but that bisects to:
aa7a9275ab81 ("PM: sleep: Suspend async parents after suspending children").
I applied your patch series to the parent of that commit, tested, and
there were no errors. So this issue looks fixed but the other issue
remains, email sent: https://lore.kernel.org/all/aD2U3VIhf8vDkl09@debian.local/
next prev parent reply other threads:[~2025-06-03 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 1:44 [PATCH 0/3] Handle aborted suspend better Mario Limonciello
2025-06-02 1:44 ` [PATCH 1/3] drm/amd: Add support for a complete pmops action Mario Limonciello
2025-06-02 1:44 ` [PATCH 2/3] drm/amd/display: Stop storing failures into adev->dm.cached_state Mario Limonciello
2025-06-02 1:44 ` [PATCH 3/3] drm/amd/display: Destroy cached state in complete() callback Mario Limonciello
2025-06-02 12:22 ` Chris Bainbridge [this message]
2025-06-10 20:11 ` [PATCH 0/3] Handle aborted suspend better Alex Hung
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=aD2XkPjk6OfEDz2-@debian.local \
--to=chris.bainbridge@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=mario.limonciello@amd.com \
--cc=superm1@kernel.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.