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: Tue, 17 Jan 2023 15:34:06 +0000 [thread overview]
Message-ID: <bug-216917-2300-qN8GPvTybU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216917-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216917
--- Comment #25 from Rainer Fiebig (jrf@mailbox.org) ---
(In reply to Alex Deucher from comment #23)
> I'll just revert it. It is more important for kernels with the the
> drm_buddy changes.
Would the following be equivalent to what you intended with your commit?
Looks a bit awkward but hibernate/resume work with it for 6.0.19 (and a Ryzen
5600G):
uint32_t amdgpu_bo_get_preferred_domain(struct amdgpu_device *adev,
uint32_t domain)
{
if (domain == (AMDGPU_GEM_DOMAIN_VRAM | AMDGPU_GEM_DOMAIN_GTT)) {
domain = AMDGPU_GEM_DOMAIN_VRAM;
if ((adev->asic_type == CHIP_CARRIZO) || (adev->asic_type ==
CHIP_STONEY)) {
if (adev->gmc.real_vram_size <= AMDGPU_SG_THRESHOLD)
domain = AMDGPU_GEM_DOMAIN_GTT;
}
}
return domain;
}
Let me know whether this is worth persuing. I could then test it with 5.15.88
and 6.1.6.
--
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-17 15:34 UTC|newest]
Thread overview: 27+ 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
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 [this message]
2023-01-17 15:46 ` bugzilla-daemon
2023-01-17 16:57 ` 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-qN8GPvTybU@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox