From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 213561] New: [bisected] AMD GPU can no longer idle state after commit 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3
Date: Wed, 23 Jun 2021 14:41:10 +0000 [thread overview]
Message-ID: <bug-213561-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=213561
Bug ID: 213561
Summary: [bisected] AMD GPU can no longer idle state after
commit 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3
Product: Drivers
Version: 2.5
Kernel Version: 5.13rc7
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: untaintableangel@hotmail.co.uk
Regression: No
Nature of the problem: RX 5700 is unable to enter low power state at idle (see
below for usual behaviour)
Sensors at idle prior to the commit:
amdgpu-pci-0f00
Adapter: PCI adapter
vddgfx: 775.00 mV
fan1: 0 RPM (min = 0 RPM, max = 3200 RPM)
edge: +48.0°C (crit = +100.0°C, hyst = -273.1°C)
(emerg = +105.0°C)
junction: +48.0°C (crit = +110.0°C, hyst = -273.1°C)
(emerg = +115.0°C)
mem: +52.0°C (crit = +105.0°C, hyst = -273.1°C)
(emerg = +110.0°C)
power1: 8.00 W (cap = 165.00 W)
After the commit, the lowest is:
amdgpu-pci-0f00
Adapter: PCI adapter
vddgfx: 1.03 V
fan1: 0 RPM (min = 0 RPM, max = 3200 RPM)
edge: +54.0°C (crit = +100.0°C, hyst = -273.1°C)
(emerg = +105.0°C)
junction: +56.0°C (crit = +110.0°C, hyst = -273.1°C)
(emerg = +115.0°C)
mem: +52.0°C (crit = +105.0°C, hyst = -273.1°C)
(emerg = +110.0°C)
power1: 31.00 W (cap = 165.00 W)
This problem wasn't present in rc6 but is present in 5.13rc7 and bisects to:
1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3 is the first bad commit
commit 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3
Author: Yifan Zhang <yifan1.zhang@amd.com>
Date: Thu Jun 10 10:10:07 2021 +0800
drm/amdgpu/gfx10: enlarge CP_MEC_DOORBELL_RANGE_UPPER to cover full
doorbell.
If GC has entered CGPG, ringing doorbell > first page doesn't wakeup GC.
Enlarge CP_MEC_DOORBELL_RANGE_UPPER to workaround this issue.
Signed-off-by: Yifan Zhang <yifan1.zhang@amd.com>
Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org
The device is a Sapphire Pulse RX5700 and this problem is seen even with one
monitor set at 60Hz.
GPU: 0f:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev
c4)
--
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 reply other threads:[~2021-06-23 14:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 14:41 bugzilla-daemon [this message]
2021-06-23 14:41 ` [Bug 213561] [bisected] AMD GPU can no longer idle state after commit 1c0b0efd148d5b24c4932ddb3fa03c8edd6097b3 bugzilla-daemon
2021-06-23 14:41 ` [Bug 213561] [bisected] AMD GPU can no longer enter " bugzilla-daemon
2021-06-23 19:15 ` [Bug 213561] [bisected][regression] AMD GPU can no longer enter idle state after commit bugzilla-daemon
2021-06-24 2:57 ` bugzilla-daemon
2021-06-24 3:53 ` bugzilla-daemon
2021-06-24 11:19 ` bugzilla-daemon
2021-06-24 11:48 ` bugzilla-daemon
2021-06-24 12:14 ` bugzilla-daemon
2021-06-24 13:59 ` bugzilla-daemon
2021-06-24 14:06 ` bugzilla-daemon
2021-06-24 14:07 ` [Bug 213561] [bisected][regression] GFX10 AMDGPUs can no longer enter idle state after commit. Commit has been pushed to stable branches too bugzilla-daemon
2021-06-24 14:18 ` bugzilla-daemon
2021-06-24 18:16 ` bugzilla-daemon
2021-06-24 21:52 ` bugzilla-daemon
2021-06-24 22:53 ` bugzilla-daemon
2021-06-28 7:22 ` bugzilla-daemon
2021-06-28 11:10 ` bugzilla-daemon
2021-06-28 12:06 ` bugzilla-daemon
2021-06-28 16:05 ` bugzilla-daemon
2022-01-20 5:27 ` 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-213561-2300@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 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.