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: Sat, 30 Mar 2019 02:22:07 +0000	[thread overview]
Message-ID: <bug-201763-2300-rN3VCYgTjm@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 #8 from Rogério Brito (rbrito@ime.usp.br) ---
Dear Michel,

(In reply to Michel Dänzer from comment #7)
> (In reply to Rogério Brito from comment #5)
> > First of all, sorry for the late reply. I had really a really bad start of
> > the year (death in family, complications caused by that, health problems,
> > fire at home and also recovering from that hard hit etc.)
> 
> Nothing to apologize for, I hope things are (getting) better for you now!

Things are slowly getting better now (still working on fixing things related to
the fire at home).

> > (In reply to Michel Dänzer from comment #2)
> > > From the dmesg output, it looks like the AMD GPU is powered off most of
> the
> > > time. Do the freezes happen when you explicitly use it for something,
> e.g.
> > > for a game via DRI_PRIME=1?
> > 
> > I never play games (really, the only game that I played in the last few
> > years was 2048 on a browser), but I guess that other applications may use
> > the discrete AMD GPU that this notebook has.
> 
> The AMD GPU should only be used if you explicitly choose to, by setting
> DRI_PRIME=1 or maybe using a corresponding setting of your desktop
> environment. Maybe the AMD GPU is only getting powered up accidentally, and
> the freezes happen due to something going wrong while powering it up/down.

Nice to know that. I may have mentioned before, but I put DRI_PRIME=1 on my
bash_profile file. I notice that when I open/close Firefox, then I get one
instance of:

------------
[drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
amdgpu: [powerplay] can't get the mac of 5
amdgpu: [powerplay] VBIOS did not find boot engine clock value in dependency
table. Using Memory DPM level 0!
------------

> Please attach the corresponding Xorg log file, preferably captured after
> dmesg has at least two instances of
> 
>  [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).

OK, I am attaching both a dmesg log and the corresponding Xorg log of this
moment that I am writing (just performed a cold boot, to rule things out), but
the Xorg log doesn't contain anything after the first 50 seconds or so...

I can turn on some debug options, if you want me to.

> You could also try modprobe.blacklist=amdgpu on the kernel command line, to
> see if the freezes happen even if the amdgpu driver never initializes the
> AMD GPU.

OK, I will do that after I finish this message.


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:[~2019-03-30  2:22 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 [this message]
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-rN3VCYgTjm@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.