Comment # 34
on bug 111482
from Dieter Nützel
(In reply to Shmerl from comment #33) > (In reply to Dieter Nützel from comment #32) > > > > Hello 'Shmerl', > > > > can you (and the other) please recheck with 'auto', too? > > I think we have the 'same' problem with Polaris, too. > > Can you clarify please, what scenario exactly do you want me to test? When > computer boots (or resumes), the value is "auto" by default. Expected. > On "auto" after > boot, idle power consumption is high (30+W). To high. With 1 or more identical monitors? Compare Alex's latest >=2 identical monitor patches. I get the same even on Polaris (Alex?). > After resume, with that "auto" > value, the screen starts flickering, That is currently the expected 'auto' clk transition bug. If someone set the clks to low/high flickering can't happen. > I'll check what power consumption it > has at that point a bit later. That's the 'new' interesting part that Andrew, Robert and you find with Navi. The suspend / resume (with later high/low) 'cycle' which led to much lower power consumption. Which I couldn't verify on my Polaris system (with 2 identical HDMI monitors) currently. With 'low' and 2 identical HDMI displays I get the below under 'amd-staging-drm-next': GFX Clocks and Power: 300 MHz (MCLK) 300 MHz (SCLK) 600 MHz (PSTATE_SCLK) 1000 MHz (PSTATE_MCLK) 750 mV (VDDGFX) 32.174 W (average GPU) PSTATE_SCLK and PSTATE_MCLK do NOT drop and much to high W. NO flickering due to 'low'. I'll point Alex to this thread.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
