All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 10 Nov 2020 21:46:42 +0000	[thread overview]
Message-ID: <bug-201763-2300-34uoEWBcRB@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 #11 from Rogério Brito (rbrito@ime.usp.br) ---
Dear Michel and other people,

Since the last time that I reported this bug, the lock ups have not happened
anymore.

OTOH, the messages on the dmesg log persist. I can include newer logs (but I
don't think that many things have changed since then). Just as a reminder, here
is what I'm getting:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(...)
[468341.815312] amdgpu: can't get the mac of 5
[468341.816323] amdgpu: VBIOS did not find boot engine clock value in
dependency table. Using Memory DPM level 0!
[468347.792326] amdgpu: VI should always have 2 performance levels
(...)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Of course, the cause may be another thing ealier in the logs. Since the first
time that I reported the issue, I upgraded the BIOS/Firmware from Dell's site,
but I'm guessing that it is very conservative and only includes an "updated"
(not so much) microcode for the CPU vulnerabilities of all these years.

I'm running an up-to-date Debian testing distribution, but I can perform any
(non-destructive :-)) tests that you want me to.


Thanks,

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

  parent reply	other threads:[~2020-11-10 21:46 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
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 [this message]
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-34uoEWBcRB@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.