<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [BDW]Igt/gem_pwrite subcase huge-gtt causes Call trace"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90254#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [BDW]Igt/gem_pwrite subcase huge-gtt causes Call trace"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90254">bug 90254</a>
from <span class="vcard"><a class="email" href="mailto:huax.lu@intel.com" title="lu hua <huax.lu@intel.com>"> <span class="fn">lu hua</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=90254#c1">comment #1</a>)
<span class="quote">> The test checks that the object fits into ram (run with --debug to verify
> that the size is indeed valid). It is probable that the huge-cpu would also
> fail given enough time to allocate the full object. But it's the spurious
> oom that kills us:
>
> [ 100.627668] 0 pages in swap cache
> [ 100.627670] Swap cache stats: add 550, delete 550, find 0/0
> [ 100.627671] Free swap = 1950564kB
> [ 100.627673] Total swap = 1952764kB
> [ 100.627674] 1028502 pages RAM
>
> Why are we not pushing others out to swap in get_pages_gtt()?</span >
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [BDW]igt/gem_pwrite/huge-cpu causes oom killer"
href="show_bug.cgi?id=90395">bug 90395</a> track the oom killer issue.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>