<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [TGL] media VME encoding GPU hang w/o i915 error state captured"
href="https://bugs.freedesktop.org/show_bug.cgi?id=112377#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [TGL] media VME encoding GPU hang w/o i915 error state captured"
href="https://bugs.freedesktop.org/show_bug.cgi?id=112377">bug 112377</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>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=112377#c5">comment #5</a>)
<span class="quote">> (In reply to Chris Wilson from <a href="show_bug.cgi?id=112377#c3">comment #3</a>)
> > Forced preemption occurs when a lower priority batch does not yield the GPU
> > to a higher preemption request [which is a denial-of-service from one and a
> > quality-of-service guarantee for the other], over a certain timeout.
>
> What is higher pre-emption request in this case?</span >
priority.
<span class="quote">> (Maybe dmesg output could identify also the higher priority process?)</span >
It's not the one at fault, it can be anything including the heartbeat.
<span class="quote">> (In reply to Chris Wilson from <a href="show_bug.cgi?id=112377#c1">comment #1</a>)
> > It's a forced preemption; reset from softirq context prohibits error capture
> > and would further compromise the QoS of the more important task.
>
> Is there some option to enable error capture also in that case?</span >
The option is to turn off this mode. The means to do that are likely to change
when we add more knobs other than modparams.
<span class="quote">> (Otherwise debugging those issues would become really hard...)</span ></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>