<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> <span class="fn">Daniel Vetter</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [i915GM regression] black screen after blank when LID is closed on Linux >= 3.1"
href="https://bugs.freedesktop.org/show_bug.cgi?id=57434">bug 57434</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>NEW
</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 - [i915GM regression] black screen after blank when LID is closed on Linux >= 3.1"
href="https://bugs.freedesktop.org/show_bug.cgi?id=57434#c15">Comment # 15</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [i915GM regression] black screen after blank when LID is closed on Linux >= 3.1"
href="https://bugs.freedesktop.org/show_bug.cgi?id=57434">bug 57434</a>
from <span class="vcard"><a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> <span class="fn">Daniel Vetter</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=57434#c14">comment #14</a>)
<span class="quote">> There is still that small regression, probably caused by your "drm/i915:
> force restore on lid open" patch, with enabling display after lid is opened
> when console is blanked. The console still thinks that display is disabled
> and
> the cursor is disabled and console braking does not work until any key is
> pressed. After that the cursor is enabled and console blanking starts
> working because now console knows that display is enabled. In Linux 3.0
> display was restored later, after key was pressed, not after lid open.</span >
That smells more like the fbcon getting confused about things - the force
restore only ensures that the hw state still matches what the driver thinks it
should be, undoing any damage the bios has done. So if fbcon blanks the screen,
we'll restore the blanked state, it doesn't just blindly enable outputs. Hence
I think all drm/i915 bugs are now fixed, and the remaining issues are either
fbcon or acpi related.
Thanks a lot for digging into this and coming up with the patch.</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 the assignee for the bug.</li>
</ul>
</body>
</html>