<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Display freezes after login with kernel 3.11.0-rc5 on Cayman with dpm=1" href="https://bugs.freedesktop.org/show_bug.cgi?id=68235#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Display freezes after login with kernel 3.11.0-rc5 on Cayman with dpm=1" href="https://bugs.freedesktop.org/show_bug.cgi?id=68235">bug 68235</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=68235#c16">comment #16</a>) > (In reply to <a href="show_bug.cgi?id=68235#c14">comment #14</a>) > > Created <a href="attachment.cgi?id=85578" name="attach_85578" title="disable various dpm features">attachment 85578</a> <a href="attachment.cgi?id=85578&action=edit" title="disable various dpm features">[details]</a> <a href='page.cgi?id=splinter.html&bug=68235&attachment=85578'>[review]</a> [review] [review] > > disable various dpm features > > > > I would suggest disabling various dpm features and see if you can narrow > > down which, if any, help. This patch disables just about everything. > > > > ni_dpm_force_performance_level(rdev, RADEON_DPM_FORCED_LEVEL_AUTO) is what > > actually sets the dynamic performance switching into motion. Prior to that > > the hw is locked into the low performance level. I sounds like there is > > some bad parameter that is causing a lock up when the smc enables state > > switching. > > > > Separate from the patch can you also try changing the > > ni_dpm_force_performance_level(rdev, RADEON_DPM_FORCED_LEVEL_AUTO) call in > > ni_dpm_set_power_state() to low (RADEON_DPM_FORCED_LEVEL_LOW) or high > > (RADEON_DPM_FORCED_LEVEL_HIGH) rather than auto? See if you still get a > > lock up. > > I'll try it later today. I had time for now to play with forcing RADEON_DPM_FORCED_LEVEL_LOW and RADEON_DPM_FORCED_LEVEL_HIGH. The first one works fine, the second triggers the problem. I'm about to play with the suggested patch.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>