<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - /dev/fb0 ioctl operation switches X11 display to old console display"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68231">68231</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>chris@chris-wilson.co.uk
</td>
</tr>
<tr>
<th>Summary</th>
<td>/dev/fb0 ioctl operation switches X11 display to old console display
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>horsley1953@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>Driver/intel
</td>
</tr>
<tr>
<th>Product</th>
<td>xorg
</td>
</tr></table>
<p>
<div>
<pre>All the info is attached to this redhat bugzilla:
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=958326">https://bugzilla.redhat.com/show_bug.cgi?id=958326</a>
Turns out that running mplayer (at least on one particular video file) with no
$DISPLAY tries (I think) to fallback on the low level frame buffer device. When
it does a couple of ioctl calls on /dev/fb0, the X11 display gets hidden and
replaced with the old contents of the VT1 console buffer (but I'm not actually
switched to that console, typing has no effect).
Doing Ctrl-Alt-F2 then Ctrl-Alt-F1 gets the X11 display back to normal and
nothing except my eyeballs seems to be aware that anything unusual happened. No
log entries are made of any kind.
This is on a fedora 19 system with this version of the intel drivers from the
fedora repos. I have no idea how to correlate this with the driver versions
here at freedesktop :-).
xorg-x11-drv-intel-2.21.12-2.fc19.x86_64
I also have a long description of finding this bug at:
<a href="http://home.comcast.net/~tomhorsley/game/heisenbug.html">http://home.comcast.net/~tomhorsley/game/heisenbug.html</a>
This seems like a real bug to me. I wouldn't think this should happen
(especially with all the mode setting code now residing in kernel drivers), but
maybe you will disagree.
It is simple to work around once found, just add the "-vo null" argument to the
mplayer command like so it doesen't try to talk to any video device.</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>