[Bug 108784] [CI][BAT] igt at i_suspend@shrink - dmesg-warn - (java|i915_suspend) invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null), order=0, oom_score_adj=(0|1000)

[bugzilla-daemon at freedesktop.org]

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

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #7 from Chris Wilson <chris at chris-wilson.co.uk> ---
I gave in and removed the test from CI:

commit 324ab48e67065f0cf67525b3ab9c44fd3dcaef0a (upstream/master,
origin/master, origin/HEAD)
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Fri Feb 15 19:09:10 2019 +0000

    intel-ci: Disable i915_suspend at shrink

    This test produces an awful, awful lot of redundant output as it tries
    to find just the right amount of memory pressure to cause an
    out-of-memory event in the middle of suspend. That is always quite a
    slow process, taking 90s on a normal machine and 500+s on skl-y.
    Furthermore, even when we do achieve the perfect setup, the test
    frequently locks up and fails to resume with no indication that it is a
    bug in the driver. The shrinker and oomkiller (plus i915) do not make for
    a pleasant time!

    Enough of Martin's whinging, I see no way of easily making this test
    quieter, quicker and more efficacious, relegate it to the masochist only
    stable.

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Martin Peres <martin.peres at free.fr>
    Cc: Petri Latvala <petri.latvala at intel.com>
    Reviewed-by: Martin Peres <martin.peres at free.fr>

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