<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HAWAII] GPU doesn't reclock, poor 3D performance" href="https://bugs.freedesktop.org/show_bug.cgi?id=82201#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [HAWAII] GPU doesn't reclock, poor 3D performance" href="https://bugs.freedesktop.org/show_bug.cgi?id=82201">bug 82201</a> from <a class="email" href="mailto:kai@dev.carbon-project.org" title="Kai <kai@dev.carbon-project.org>"> Kai</a> <pre>(In reply to <a href="show_bug.cgi?id=82201#c11">comment #11</a>) > Created <a href="attachment.cgi?id=104101" name="attach_104101" title="enable dpm=1 debugging even when dpm is not forced">attachment 104101</a> <a href="attachment.cgi?id=104101&action=edit" title="enable dpm=1 debugging even when dpm is not forced">[details]</a> <a href='page.cgi?id=splinter.html&bug=82201&attachment=104101'>[review]</a> [review] > enable dpm=1 debugging even when dpm is not forced > > This patch enables the additional dpm debugging output even when it is not > explictly set on the command line. Does it help? The only thing I can > figure is that the debugging output adds a small delay that may have a > positive impact. You're not going to like this. But setting radeon.dpm=1 must have some other side effect. I booted each configuration represent by <a href="attachment.cgi?id=104103" name="attach_104103" title="dmesg output with attachment 104101 and no "radeon.dpm=1" set">attachment 104103</a> <a href="attachment.cgi?id=104103&action=edit" title="dmesg output with attachment 104101 and no "radeon.dpm=1" set">[details]</a> and <a href="attachment.cgi?id=104104" name="attach_104104" title="dmesg output with attachment 104101 and "radeon.dpm=1" set">attachment 104104</a> <a href="attachment.cgi?id=104104&action=edit" title="dmesg output with attachment 104101 and "radeon.dpm=1" set">[details]</a> two times. The first (104103) is the stack from <a href="show_bug.cgi?id=82201#c0">comment #0</a> plus the patch from <a href="attachment.cgi?id=104101" name="attach_104101" title="enable dpm=1 debugging even when dpm is not forced">attachment 104101</a> <a href="attachment.cgi?id=104101&action=edit" title="enable dpm=1 debugging even when dpm is not forced">[details]</a> <a href='page.cgi?id=splinter.html&bug=82201&attachment=104101'>[review]</a> applied to the kernel, then booted without radeon.dpm=1 (see the dmesg output for the kernel command line). When I start Portal 2 I stay at the numbers reported in <a href="show_bug.cgi?id=82201#c0">comment #0</a> (ie. at low FPS). If I boot the stack from <a href="show_bug.cgi?id=82201#c0">comment #0</a> with the patch from <a href="attachment.cgi?id=104101" name="attach_104101" title="enable dpm=1 debugging even when dpm is not forced">attachment 104101</a> <a href="attachment.cgi?id=104101&action=edit" title="enable dpm=1 debugging even when dpm is not forced">[details]</a> <a href='page.cgi?id=splinter.html&bug=82201&attachment=104101'>[review]</a> applied to the kernel and DO set radeon.dpm=1 on the kernel command line (see second dmesg output; 104104), then I get 60 FPS in Portal 2.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>