[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 bugzilla-daemon at freedesktop.org
Fri Dec 7 13:29:55 UTC 2018


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

--- Comment #4 from Martin Peres <martin.peres at free.fr> ---
(In reply to Chris Wilson from comment #3)
> (In reply to Martin Peres from comment #2)
> > (In reply to Chris Wilson from comment #1)
> > > The oomkiller is being invoked on purpose as part of the test and there is
> > > no way to suppress the error messages. Of course, sometimes, oomkiller fails
> > > and the test fails in which case the error is significant...
> > 
> > This is new though. 70 machines hitting this at the same time, and having
> > enormous logs filing up the DB...
> 
> It was only new due to the test name change (drv_suspend -> i915_suspend).
> There appears to be no way from userspace to suppress the
> warn_alloc_show_mem()

Thanks for the explanation.

Could we add a kernel parameter to hide this? It could land in core-for-CI, and
we could even try to upstream it.

Generating this warning in every run on every machine just fills the database,
and adds noise to results which confuse people (dmesg-warn is not an acceptable
status).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee 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/20181207/99ee1f69/attachment-0001.html>


More information about the intel-gfx-bugs mailing list