From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201763] amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0!
Date: Thu, 28 Feb 2019 22:33:55 +0000 [thread overview]
Message-ID: <bug-201763-2300-qxqMZtxgoZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201763-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201763
--- Comment #6 from Rogério Brito (rbrito@ime.usp.br) ---
Oh, I forgot to say that the kernel that I am using is currently identified as:
Linux zatz 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64
GNU/Linux
I can report the versions of the graphics stack once I know what is relevant. I
can also try to stress test anything here.
Thanks once again,
Rogério Brito.
--
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 prev parent reply other threads:[~2019-02-28 22:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 6:41 [Bug 201763] New: amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency table. Using Memory DPM level 0! bugzilla-daemon
2018-11-22 6:46 ` [Bug 201763] " bugzilla-daemon
2018-11-22 15:52 ` bugzilla-daemon
2018-11-25 12:10 ` bugzilla-daemon
2018-11-25 12:11 ` bugzilla-daemon
2019-02-28 22:31 ` bugzilla-daemon
2019-02-28 22:33 ` bugzilla-daemon [this message]
2019-03-01 16:14 ` bugzilla-daemon
2019-03-30 2:22 ` bugzilla-daemon
2019-03-30 2:23 ` bugzilla-daemon
2019-03-30 2:24 ` bugzilla-daemon
2020-11-10 21:46 ` bugzilla-daemon
2020-11-19 10:43 ` bugzilla-daemon
2020-11-19 14:23 ` 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-201763-2300-qxqMZtxgoZ@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;
as well as URLs for NNTP newsgroup(s).