<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - System stall on Supermicro SKL boards on drm-tip" href="https://bugs.freedesktop.org/show_bug.cgi?id=105949#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - System stall on Supermicro SKL boards on drm-tip" href="https://bugs.freedesktop.org/show_bug.cgi?id=105949">bug 105949</a> from <a class="email" href="mailto:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> Imre Deak</a> <pre>(In reply to Dmitry Ermilov from <a href="show_bug.cgi?id=105949#c6">comment #6</a>) > > Or is there another scenario which you refer to as "can't be booted"? > Yes, the third scenario is SM boards can't boot at all without > "intel_pstate=disable i915.enable_rc6=0 intel_idle.max_cstate=1". > We plan to check which exact option among these helps to boot. > Actually this (the 3rd) scenario is the one we wanted to bring to you. > Presence of the warning is just an observation, I'm not sure if it's > relevant. If you're using the system without a display then I'm guessing the presence of this error shouldn't cause a boot failure. > > In the case where booting without the error messages, is there some other issue you see (system stall reported on <a class="bz_bug_link bz_status_NEW " title="NEW - System stall on Supermicro SKL boards on drm-tip" href="show_bug.cgi?id=105949">bug 105949</a>)? > Yes, it's <a class="bz_bug_link bz_status_NEW " title="NEW - System stall on Supermicro SKL boards on HEVC FEI workloads" href="show_bug.cgi?id=105955">bug 105955</a>. Generally at first we came across <a class="bz_bug_link bz_status_NEW " title="NEW - System stall on Supermicro SKL boards on HEVC FEI workloads" href="show_bug.cgi?id=105955">bug 105955</a>. And > after some experiments we discovered the problem described in the current > bug. Ok, so the lag happens even without the CDCLK PLL enabling issues reported here. > > Did you try to bisect the problem causing the above error messages (noting that you need several boots for each bisect step)? > Not yet. To get the ball rolling we can try to revert > <a href="https://patchwork.freedesktop.org/patch/65235/">https://patchwork.freedesktop.org/patch/65235/</a>. That one re-enabled display C (DC) states. Another way to test if DC states cause the problem is to boot with i915.enable_dc=0 kernel parameter. > > Specifically there's been a recent related WA, could you try if the problem persists reverting that on top of drm-tip? > Sure. Thank you. > > Regards, > Dmitry</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>