All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209015] New: Clocks are no longer reported for R9 390 GPU
Date: Sun, 23 Aug 2020 20:45:33 +0000	[thread overview]
Message-ID: <bug-209015-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 209015
           Summary: Clocks are no longer reported for R9 390 GPU
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.8
          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: henryjm11106@gmail.com
        Regression: No

After updating to Linux 5.8, mclk and sclk are always reported as 0MHz on my
AMD R9 390. this is consistent after a couple of 5.8 kernel updates with both
linux-zen and generic linux. it was fine on the last 5.7 release, and going
back to 5.4 LTS clocks are reported correctly as of now. issue is present with
both AMDGPU and Radeon drivers

-- 
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

             reply	other threads:[~2020-08-23 20:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 20:45 bugzilla-daemon [this message]
2020-08-24 15:05 ` [Bug 209015] Clocks are no longer reported for R9 390 GPU bugzilla-daemon
2020-08-24 21:57 ` bugzilla-daemon
2020-08-24 21:59 ` bugzilla-daemon
2020-08-27 21:16 ` bugzilla-daemon
2020-08-27 21:20 ` bugzilla-daemon
2020-09-11  2:08 ` 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-209015-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.