[Bug 82201] [HAWAII] GPU doesn't reclock, poor 3D performance

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Aug 9 04:53:36 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=82201

--- Comment #26 from Kai <kai at dev.carbon-project.org> ---
After observing, that setting radeon.dpm=1 all the time doesn't guarantee a
reclocking GPU all the time, I went back to looking, what I did *exactly* in
the cases, where I got a reclocking GPU. I found, that I either had a
reclocking GPU in the previous boot* or executed the VBIOS dump before. Doing
the VBIOS dump causes several lines of "radeon 0000:01:00.0: Invalid ROM
contents" appearing in dmesg's output and I get a reclocking GPU on the
subsequent boot (can be easily verified with a vblank_mode=0 glxgears run, just
look at the frames count, if it's in the 20k vicinity, the GPU reclocks; also,
you can hear the fan going up after a few seconds).

Not sure, what this means. I can only add, that booting with Catalyst gives me
a reclocking GPU all the time. So it doesn't sound like a defect graphics card.
But I hope it helps in tracking this issue down.

I haven't tried yet, whether this survives a suspend to disk or RAM.


* Using "poweroff" instead of "reboot" works as well, as long as you don't wait
too long (sounds a bit like some memory is kept alive by a capacitor for some
time after powering off). This explains my success of the run I detailed in
comment #17 AFAICT.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140809/8d309560/attachment.html>


More information about the dri-devel mailing list