dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 210683] Nasty amdgpu powersave regression Navi14
Date: Sun, 20 Dec 2020 03:26:23 +0000	[thread overview]
Message-ID: <bug-210683-2300-PdMMAtiZIq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210683-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=210683

David Mak (david.18.19.21@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |david.18.19.21@gmail.com

--- Comment #4 from David Mak (david.18.19.21@gmail.com) ---
Created attachment 294239
  --> https://bugzilla.kernel.org/attachment.cgi?id=294239&action=edit
dmesg outputs for 5.9.14 and 5.10.1.

I can reproduce the issue on the RX 6800 (Navi 21 XL).

I use Radeontop to inspect the memory/GPU clock of my GPU.

When using Linux 5.9.14:
- In both KDE Plasma and tty2, Memory Clock hovers at around 100MHz.
- GPU Power reported by lm_sensors is around 5-7W.

When using Linux 5.10.1:
- In tty2, Memory Clock hovers at around 100MHz and GPU Power reported by
lm_sensors is around 5-7W.
- In KDE Plasma, Memory Clock is usually around 1GHz (100%), although it can be
down to ~470MHz, and GPU Power reported by lm_sensors is around 30W.
- Disconnecting one of my two monitors does not change the memory clock.

I am trying to bisect the commit, but many revisions seem to give a blank
screen or the amdgpu module is not loaded. (I suspect I am not building the
kernel properly)

Tested linux-firmware versions: 20201120.bc9cd0b, 20201218.646f159

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-12-20  3:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 13:08 [Bug 210683] New: Nasty gpu powersave regression Navi14 bugzilla-daemon
2020-12-14 13:09 ` [Bug 210683] " bugzilla-daemon
2020-12-14 13:15 ` [Bug 210683] Nasty amdgpu " bugzilla-daemon
2020-12-14 13:22 ` bugzilla-daemon
2020-12-14 13:40 ` bugzilla-daemon
2020-12-14 13:41 ` bugzilla-daemon
2020-12-14 18:22 ` bugzilla-daemon
2020-12-20  3:26 ` bugzilla-daemon [this message]
2020-12-22  8:29 ` bugzilla-daemon
2020-12-24 11:25 ` bugzilla-daemon
2020-12-26 16:14 ` bugzilla-daemon
2020-12-26 16:15 ` bugzilla-daemon
2020-12-27 16:24 ` bugzilla-daemon
2020-12-27 16:26 ` bugzilla-daemon
2021-01-16  4:33 ` 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-210683-2300-PdMMAtiZIq@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