<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - userptr deadlock in Vulkan CTS: mmu_notifier vs workers vs struct_mutex"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108456#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - userptr deadlock in Vulkan CTS: mmu_notifier vs workers vs struct_mutex"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108456">bug 108456</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=108456#c1">comment #1</a>)
<span class="quote">> The oom may be symptomatic of the same failure, if it is struggling to
> allocate memory, then it is entirely possible for the machine to be starved
> an no further progress made under the mutex for a long time.</span >
(In reply to Mark Janes from <a href="show_bug.cgi?id=108456#c5">comment #5</a>)
<span class="quote">> /proc/meminfo from hung system:
>
> MemTotal: 7848548 kB
> MemFree: 328460 kB
> MemAvailable: 6171272 kB</span >
...
<span class="quote">> SwapTotal: 8068092 kB
> SwapFree: 7879420 kB</span >
Memory usage at this point doesn't seem to be problem, but I think that's
because the OOM kill causing program may have already gone. You would need to
track memory usage before the OOM.
Btw. for i915, it's relevant to track also driver memory as that's not really
visible in meminfo until other things start getting pushed to swap:
sudo watch cat /sys/kernel/debug/dri/0/i915_gem_objects
<span class="quote">> VmallocTotal: 34359738367 kB</span >
34 TB allocated on machine with 8 GB of RAM. That's a lot of (currently)
unused memory...</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>
</ul>
</body>
</html>