<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BSW] image corruption issue after edd849e5448c4f6ddc04a5fa1ac5479176660c27"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102818#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BSW] image corruption issue after edd849e5448c4f6ddc04a5fa1ac5479176660c27"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102818">bug 102818</a>
from <span class="vcard"><a class="email" href="mailto:freedesktop@nmacleod.com" title="freedesktop@nmacleod.com">freedesktop@nmacleod.com</a>
</span></b>
<pre>I used git to bisect between v4.12-rc1 (BAD) and v4.11.10 (GOOD).
Unfortunately git identified a merge commit as the BAD commit:
<a href="https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/patch/?id=edd849e5448c4f6ddc04a5fa1ac5479176660c27">https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/patch/?id=edd849e5448c4f6ddc04a5fa1ac5479176660c27</a>
and would not bisect any further. I decided to "bisect" manually, and having
done so the first BAD commit is:
<a href="https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/patch/?id=608b20506941969ea30d8c08dc9ae02bb87dbf7d">https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/patch/?id=608b20506941969ea30d8c08dc9ae02bb87dbf7d</a>
By reverting 608b20506941969ea30d8c08dc9ae02bb87dbf7d from 4.13.3 (see attached
patch), the user has confirmed that 4.13.3 is now GOOD, while the normal 4.13.3
(without the revert) is still BAD.
I'll attach the "revert" patch (which is just for test purposes), and also my
steps taken to confirm this conclusion (just for completeness)</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 the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>