<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - [945gm regression] LVDS boots to blank screen"
href="https://bugs.freedesktop.org/show_bug.cgi?id=53926#c53">Comment # 53</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - [945gm regression] LVDS boots to blank screen"
href="https://bugs.freedesktop.org/show_bug.cgi?id=53926">bug 53926</a>
from <span class="vcard"><a class="email" href="mailto:nmschulte@gmail.com" title="Nathan Schulte <nmschulte@gmail.com>"> <span class="fn">Nathan Schulte</span></a>
</span></b>
<pre>I don't think I've marked any commits improperly. I skipped the ones
that caused kernel panics, though I suspect I could include those data
points and possibly speed up the process. I'm not sure, so I'll leave
them out.
One question: right now I'm bisecting for a bug fix rather than a bug
regression. Would it be wiser to instead bisect for a regression from
say 3.0 (or similar, where the bug does not exist, if such a commit
exists) to 3.2?
Another question: git bisect can narrow down commits to those that
affect a certain part of the tree. Do you think it's safe to narrow
this down to the DRM or even i915 portion? That might speed up the
process tremendously if so.</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>