<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Blank screen after locking and vt-switch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110863#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Blank screen after locking and vt-switch"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110863">bug 110863</a>
from <span class="vcard"><a class="email" href="mailto:corsac@debian.org" title="Yves-Alexis <corsac@debian.org>"> <span class="fn">Yves-Alexis</span></a>
</span></b>
<pre>(In reply to Jyoti Yadav from <a href="show_bug.cgi?id=110863#c12">comment #12</a>)
<span class="quote">> @Yves-Alexis, In dmesg logs, we could see
> [drm:intel_cpu_fifo_underrun_irq_handler] *ERROR* CPU pipe B FIFO underrun
>
> error only just once. After that looks like display has recovered this
> underrun issue and this is seen when we are plugging DP display.
>
> Can you please explain this locking scenario? What is exactly you
> hotplugging in?</span >
This is totally unrelated to hotplugging. It happens on a laptop with no
attached screen. By “locking” I mean “locking the screen”, so I have to enter a
password to gain access to my desktop.
Is there something else confusing?
<span class="quote">>
> And this blank screen persists?</span >
Until I manually do a vt-switch, yes. And a lot of people don't know about this
workaround and desperately try to access their computer once locked (see the
downstream bug reports).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>