<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - xorg-server 1.18.2 freeze desktop on i915"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94515#c42">Comment # 42</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - xorg-server 1.18.2 freeze desktop on i915"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94515">bug 94515</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 Leho Kraav (:macmaN :lkraav) from <a href="show_bug.cgi?id=94515#c40">comment #40</a>)
<span class="quote">> I got the freeze and I'm on UXA GLAMOR, not SNA. Are we sure this patch is
> related?</span >
Yes. The bug is the client is requesting a target_msc that wraps around onto
the current msc. No backend handled that overflow and so all are susceptible.
The patch adds a check for the overflow when casting from the 64bit target_msc
into the 32bit hardware sequence number and reporting the error from the
driver.
The bug as far as I can tell so far is that the requested divisor received from
the Client is 1<<32 rather than 1. That suggests that the two CARD32 in the
protocol have been swapped, but that seems unlikely...</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>