From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 215436] admgpu: suspend and resuming from suspend don't work
Date: Mon, 03 Jan 2022 17:49:28 +0000 [thread overview]
Message-ID: <bug-215436-2300-3vRmAXrVj2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215436-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215436
mario.limonciello@amd.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #300214|0 |1
is obsolete| |
--- Comment #17 from mario.limonciello@amd.com ---
Created attachment 300215
--> https://bugzilla.kernel.org/attachment.cgi?id=300215&action=edit
Possible patch that ignores WA in s0ix w/ debugging statements (v2)
OK thanks for trying it! Here's an updated patch, to try to give an extra
explicit call to update the clocks again during the suspend path. Also
included a debugging statement so we can see the state of the variables that
matter in each call to update_clocks.
If you can please share the output from your kernel log again with it applied.
--
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 prev parent reply other threads:[~2022-01-03 17:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 12:28 [Bug 215436] New: admgpu: suspend and resuming from suspend don't work bugzilla-daemon
2021-12-29 15:08 ` [Bug 215436] " bugzilla-daemon
2021-12-29 15:10 ` bugzilla-daemon
2021-12-30 13:03 ` bugzilla-daemon
2021-12-30 13:16 ` bugzilla-daemon
2021-12-30 14:33 ` bugzilla-daemon
2021-12-31 0:17 ` bugzilla-daemon
2021-12-31 0:22 ` bugzilla-daemon
2021-12-31 15:10 ` bugzilla-daemon
2021-12-31 16:14 ` bugzilla-daemon
2022-01-01 1:42 ` bugzilla-daemon
2022-01-03 9:29 ` bugzilla-daemon
2022-01-03 9:35 ` bugzilla-daemon
2022-01-03 9:36 ` bugzilla-daemon
2022-01-03 10:20 ` bugzilla-daemon
2022-01-03 10:29 ` bugzilla-daemon
2022-01-03 15:48 ` bugzilla-daemon
2022-01-03 17:12 ` bugzilla-daemon
2022-01-03 17:49 ` bugzilla-daemon [this message]
2022-01-03 17:51 ` bugzilla-daemon
2022-01-04 10:17 ` bugzilla-daemon
2022-01-04 10:25 ` bugzilla-daemon
2022-01-04 11:15 ` bugzilla-daemon
2022-01-04 11:27 ` bugzilla-daemon
2022-01-04 14:14 ` bugzilla-daemon
2022-01-04 14:59 ` bugzilla-daemon
2022-01-04 15:03 ` bugzilla-daemon
2022-01-04 15:27 ` bugzilla-daemon
2022-01-04 15:28 ` bugzilla-daemon
2022-01-24 22:45 ` bugzilla-daemon
2022-01-25 20: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-215436-2300-3vRmAXrVj2@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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;
as well as URLs for NNTP newsgroup(s).