From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 212077] New: AMD GPU at highest frequency even not in use
Date: Fri, 05 Mar 2021 19:44:20 +0000 [thread overview]
Message-ID: <bug-212077-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=212077
Bug ID: 212077
Summary: AMD GPU at highest frequency even not in use
Product: Drivers
Version: 2.5
Kernel Version: 5.11.3
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: bat_malin@abv.bg
Regression: No
Created attachment 295677
--> https://bugzilla.kernel.org/attachment.cgi?id=295677&action=edit
Dmesg
1.240847] amdgpu: Clock is not in range of specified clock range for watermark
from DAL! Using highest water mark set.
[ 1.240850] amdgpu: Clock is not in range of specified clock range for
watermark from DAL! Using highest water mark set.
[ 1.240851] amdgpu: Clock is not in range of specified clock range for
watermark from DAL! Using highest water mark set.
[ 1.240852] amdgpu: Clock is not in range of specified clock range for
watermark from DAL! Using highest water mark set.
[ 1.240853] amdgpu: Clock is not in range of specified clock range for
watermark from DAL! Using highest water mark set.
[ 1.240854] amdgpu: Clock is not in range of specified clock range for
watermark from DAL! Using highest water mark set.
[ 1.240855] amdgpu: Clock is not in range of specified clock range for
watermark from DAL! Using highest water mark set.
[ 1.240856] amdgpu: Clock is not in range of specified clock range for
watermark from DAL! Using highest water mark set.
[ 1.240857] amdgpu: Clock is not in range of specified clock range for
watermark from DAL! Using highest water mark set.
[ 1.240858] amdgpu: Clock is not in range of specified clock range for
watermark from DAL! Using highest water mark set.
Dmesg attached
--
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
next reply other threads:[~2021-03-05 19:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 19:44 bugzilla-daemon [this message]
2021-03-05 19:47 ` [Bug 212077] AMD GPU discrete card memory at highest frequency even not in use bugzilla-daemon
2021-03-05 19:47 ` [Bug 212077] AMD GPU discrete card memory at highest frequency even while " bugzilla-daemon
2021-03-05 19:50 ` bugzilla-daemon
2021-03-05 19:51 ` bugzilla-daemon
2021-03-06 19:45 ` bugzilla-daemon
2021-03-08 19:43 ` bugzilla-daemon
2021-03-10 20:44 ` bugzilla-daemon
2021-03-10 20:55 ` bugzilla-daemon
2021-03-13 20:05 ` bugzilla-daemon
2021-03-17 19:11 ` bugzilla-daemon
2021-03-17 19:19 ` bugzilla-daemon
2021-03-17 19:21 ` bugzilla-daemon
2021-03-17 19:23 ` bugzilla-daemon
2021-03-19 19:44 ` bugzilla-daemon
2021-03-24 21:32 ` bugzilla-daemon
2021-03-26 20:25 ` bugzilla-daemon
2021-04-07 18:21 ` bugzilla-daemon
2021-04-08 18:31 ` 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-212077-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.