Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2039621
| Summary: | 5.15.14 kernel doesn't sleep properly on a laptop with an integrated Radeon R5 GPU | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Matt Fagnani <matt.fagnani> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 35 | CC: | acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, jarodwilson, jeremy, jforbes, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | kernel-5.15.16-100.fc34 kernel-5.15.16-200.fc35 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-01-22 01:18:23 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Matt Fagnani
2022-01-12 05:56:56 UTC
I bisected between 5.15.13 and 5.15.14. git bisect gave the following final output for the first bad commit which involved amdgpu and suspend.
3c196f05666610912645c7c5d9107706003f67c3 is the first bad commit
commit 3c196f05666610912645c7c5d9107706003f67c3
Author: Alex Deucher <alexander.deucher>
Date: Fri Nov 12 11:25:30 2021 -0500
drm/amdgpu: always reset the asic in suspend (v2)
[ Upstream commit daf8de0874ab5b74b38a38726fdd3d07ef98a7ee ]
If the platform suspend happens to fail and the power rail
is not turned off, the GPU will be in an unknown state on
resume, so reset the asic so that it will be in a known
good state on resume even if the platform suspend failed.
v2: handle s0ix
Acked-by: Luben Tuikov <luben.tuikov>
Acked-by: Evan Quan <evan.quan>
Signed-off-by: Alex Deucher <alexander.deucher>
Signed-off-by: Sasha Levin <sashal>
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3c196f05666610912645c7c5d9107706003f67c3
Thank you very much for bisecting your kernel bug, that is always really helpful in getting things fixed. In case you haven't done so already can you please report this directly to the upstream amdgpu developers, including Alexs Deucher, the author of the problematic patch? Since you can clearly build your own kernels, they can then interact with you directly and give you patches which may fix this for you to test. (In reply to Hans de Goede from comment #2) > Thank you very much for bisecting your kernel bug, that is always really > helpful in getting things fixed. > > In case you haven't done so already can you please report this directly to > the upstream amdgpu developers, including Alexs Deucher, the author of the > problematic patch? > > Since you can clearly build your own kernels, they can then interact with > you directly and give you patches which may fix this for you to test. Alex Deucher wrote a patch at https://gitlab.freedesktop.org/drm/amd/-/issues/1858#note_1217823 I built 5.15.14 after applying 0001-drm-amdgpu-don-t-do-resets-on-APUs-which-don-t-suppo.patch, and that kernel slept and woke up normally. Thanks. Thanks for doing all of this. The patch was posted on the 12th and hasn't made it to any of the next trees yet, but I will pull it in once it does. FEDORA-2022-6352c313b7 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6352c313b7 FEDORA-2022-6d4082d590 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6d4082d590 FEDORA-2022-6d4082d590 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-6d4082d590` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-6d4082d590 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-6352c313b7 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-6352c313b7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-6352c313b7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-6d4082d590 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-6352c313b7 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |