<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - VulkanCTS 1.1.2 Kernel error: dEQP-VK.pipeline.render_to_image.core.cube_array.huge.width_height_layers"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108456#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - VulkanCTS 1.1.2 Kernel error: dEQP-VK.pipeline.render_to_image.core.cube_array.huge.width_height_layers"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108456">bug 108456</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>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.
For a report like this, a "cat /proc/*/stack" is useful to see what might be
holding the struct_mutex.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>