<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> <span class="fn">Jani Nikula</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [byt] Linux console may not output after reboot."
href="https://bugs.freedesktop.org/show_bug.cgi?id=84309">bug 84309</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [byt] Linux console may not output after reboot."
href="https://bugs.freedesktop.org/show_bug.cgi?id=84309#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [byt] Linux console may not output after reboot."
href="https://bugs.freedesktop.org/show_bug.cgi?id=84309">bug 84309</a>
from <span class="vcard"><a class="email" href="mailto:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> <span class="fn">Jani Nikula</span></a>
</span></b>
<pre>(In reply to Rick from <a href="show_bug.cgi?id=84309#c2">comment #2</a>)
<span class="quote">> test 3.17.0-rc7, 30 times pass, occurrence 0/30
>
> How do I merge the change into 3.14 series?</span >
The first step is *finding* the change that makes the difference. It may be
it's not just one change, but a series of changes. To give you an idea what
kind of haystack you're looking for the needle in, there have been 1300+
changesets merged into the i915 driver alone between v3.14 and v3.17, with a
diffstat of: 67 files changed, 25925 insertions(+), 9362 deletions(-). That
doesn't even include the drm core changes.
You could try to do a reverse git bisect to find the commit that fixed the
issue for you. It's roughly 14 build/test steps. For example
<a href="https://wiki.ubuntu.com/Kernel/KernelBisection">https://wiki.ubuntu.com/Kernel/KernelBisection</a> has this explained.
Once you've found the commit(s), the next step is backporting the fixes back to
v3.14, preferrably contributing them to the longterm stable v3.14.
Unfortunately they may not be directly applicable to v3.14, and a lot of work
may be required.
Finally, this is upstream bugzilla, and we have fixed the issue upstream, thus
I'm closing the bug. We may be able to help if you identify the working commit.
HTH.</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>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>