From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216917] hibernation regression since 6.0.18 (Ryzen-5650U incl. Radeon GPU)
Date: Mon, 16 Jan 2023 16:14:12 +0000 [thread overview]
Message-ID: <bug-216917-2300-457NFiS9S4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216917-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216917
Rainer Fiebig (jrf@mailbox.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jrf@mailbox.org
--- Comment #12 from Rainer Fiebig (jrf@mailbox.org) ---
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from
comment #9)
> FWIW, I just wanted to add this to the regression tracking, but 6.0.y is EOL
> now; and it seems 6.1.y works. Greg might do another fixup release, but
> maybe investigating this further is not worth it.
I beg to differ. Longterm kernels 5.15.87/88 and probably all other LTS kernels
to which commit 306df163069e78160e7a534b892c5cd6fefdd537 has been backported
are also affected. As "hibernate" is a basic, reliable feature and a hard reset
(as in my case) may result in data loss, I only see two possibilities: either
revert the commit in the longterm kernels or try to find out quickly what makes
it work for them.
The diff between 6.0.18 and 6.1.4 (where it was introduced) shows that only 86
files in /drivers/gpu/drm/amd/amdgpu have been modified. Probably only a few of
them are relevant in this matter. So for the experts it should not be too hard
to figure out a solution.
--
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:[~2023-01-16 16:14 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216917-2300@https.bugzilla.kernel.org/>
2023-01-11 21:37 ` [Bug 216917] hibernation regression since 6.0.18 (Ryzen-5650U incl. Radeon GPU) bugzilla-daemon
2023-01-11 21:45 ` bugzilla-daemon
2023-01-11 21:46 ` bugzilla-daemon
2023-01-11 22:23 ` bugzilla-daemon
2023-01-11 22:36 ` bugzilla-daemon
2023-01-11 23:19 ` bugzilla-daemon
2023-01-12 13:18 ` bugzilla-daemon
2023-01-12 17:24 ` bugzilla-daemon
2023-01-12 17:47 ` bugzilla-daemon
2023-01-13 9:16 ` bugzilla-daemon
2023-01-16 16:14 ` bugzilla-daemon [this message]
2023-01-16 16:15 ` bugzilla-daemon
2023-01-16 16:16 ` bugzilla-daemon
2023-01-16 16:16 ` bugzilla-daemon
2023-01-16 16:20 ` bugzilla-daemon
2023-01-16 16:21 ` bugzilla-daemon
2023-01-16 16:41 ` bugzilla-daemon
2023-01-16 17:02 ` bugzilla-daemon
2023-01-16 17:49 ` bugzilla-daemon
2023-01-16 18:12 ` bugzilla-daemon
2023-01-16 20:59 ` bugzilla-daemon
2023-01-16 21:02 ` bugzilla-daemon
2023-01-16 21:08 ` bugzilla-daemon
2023-01-17 7:43 ` bugzilla-daemon
2023-01-17 15:34 ` bugzilla-daemon
2023-01-17 15:46 ` bugzilla-daemon
2023-01-17 16:57 ` bugzilla-daemon
2023-01-11 18:04 [Bug 216917] New: " bugzilla-daemon
2023-01-11 18:50 ` [Bug 216917] " bugzilla-daemon
2023-01-11 19:18 ` bugzilla-daemon
2023-01-11 21:36 ` bugzilla-daemon
2023-01-11 21:37 ` 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-216917-2300-457NFiS9S4@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 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.