[Bug 110331] [CI][SHARDS] igt@* - incomplete - NMI backtrace for cpu \d skipped: idling at acpi_processor_ffh_cstate_enter

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=110331

Martin Peres <martin.peres at free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|high                        |highest

--- Comment #7 from Martin Peres <martin.peres at free.fr> ---
(In reply to Ville Syrjala from comment #6)
> (In reply to Ville Syrjala from comment #5)
> > (In reply to Martin Peres from comment #3)
> > > Let's monitor the failure rate now that the following commit has landed:
> > > 
> > > https://cgit.freedesktop.org/drm/drm-intel/commit/?h=topic/core-for-
> > > CI&id=b573fba52f339dc4fadef7282af4a9413fd6173d
> > > 
> > > CL HACK: Disable ACPI idle drivertopic/core-for-CI
> > > There were few system hung observed while running i915_pm_rpm igt test.
> > > FDO https://bugs.freedesktop.org/show_bug.cgi?id=108840
> > > Root cause is believed to due to page fault in ACPI idle driver.
> > > (FDO comment 18).
> > > It has been suggested by Daniel Vetter to disable ACPI idle
> > > driver for Core-for-CI, only for ICL.
> > > 
> > > This hacky patch is only for ICL processor and for Core-for-CI branch.
> > > 
> > > v2: Fixed compilation errors raised by lkp.
> > >     commit message improvement.
> > > 
> > > Cc: martin.peres at intel.com
> > > Cc: daniel.vetter at intel.com
> > > 
> > > Signed-off-by: Anshuman Gupta <anshuman.gupta at intel.com>
> > > Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
> > > Link:
> > > https://patchwork.freedesktop.org/patch/msgid/1554791361-27684-1-git-send-
> > > email-anshuman.gupta at intel.com
> > 
> > Ugh. I think this means we've effectively disabled all C-states in CI. Last
> > I looked intel_idle icl support wasn't upstream yet.
> 
> Yeah, no C-states visible on icl-u2. So low power watermarks and whatnot not
> getting tested at all currently.

Changing the priority to highest because of the testing gap that will
potentially lead to flickering screens.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190426/84a24f08/attachment.html>