<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Flickering Screen on Dell XPS13 9350"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94593#c45">Comment # 45</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Flickering Screen on Dell XPS13 9350"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94593">bug 94593</a>
from <span class="vcard"><a class="email" href="mailto:nhellwege@gmail.com" title="nhellwege@gmail.com">nhellwege@gmail.com</a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=123104" name="attach_123104" title="bisect log for underrun FIFO Error">attachment 123104</a> <a href="attachment.cgi?id=123104&action=edit" title="bisect log for underrun FIFO Error">[details]</a></span>
bisect log for underrun FIFO Error
Bisect log for the i915 Underrun FIFO ERROR. Since no clear method is known on
how to excite the error, the bisect might be unfinished. All bad commits did
show the FIFO error AND also the Flicker. All good ones did not within a
reasonable time (I testet each good Kernal at least 30 minutes). There are some
(many) skippes commits, which I was not able to build. The Faulty commit must
be somewhere in these skipped commits.</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>