<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - GPU lockups with kernel 3.11.0 / 3.12-rc1 when dpm=1 on r600g (Cayman)" href="https://bugs.freedesktop.org/show_bug.cgi?id=69723#c46">Comment # 46</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - GPU lockups with kernel 3.11.0 / 3.12-rc1 when dpm=1 on r600g (Cayman)" href="https://bugs.freedesktop.org/show_bug.cgi?id=69723">bug 69723</a> from <a class="email" href="mailto:alexandre.f.demers@gmail.com" title="Alexandre Demers <alexandre.f.demers@gmail.com>"> Alexandre Demers</a> <pre>(In reply to <a href="show_bug.cgi?id=69723#c45">comment #45</a>) > The windows driver should operate pretty much the same as the linux driver > as far as I know. I'm not really familiar with how gpu-z reads back the > clocks and voltages and that may have something to do with the differences. > Not all of the aspects of the level transition happen at the same time. > > You could try setting the vddc to 1060 and changing the mclk of level 1 (mid > level) to 650Mhz. Perhaps the jump from 150 to 1300 is too big and the pll > is not able to lock properly. I tried it, but I had the same result: a hang. However, I'd be curious to see the result on the ower con sumption. I'll keep that for another time. I'll try to follow Vddci under Windows with something like Afterburner.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>