<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 --- - After 3-4 hours of use any new window is completely black"
href="https://bugs.freedesktop.org/show_bug.cgi?id=61717">61717</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>chris@chris-wilson.co.uk
</td>
</tr>
<tr>
<th>Summary</th>
<td>After 3-4 hours of use any new window is completely black
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jake@lwn.net
</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>Created <span class=""><a href="attachment.cgi?id=75809" name="attach_75809" title="trace-cmd report run after the problem occurred.">attachment 75809</a> <a href="attachment.cgi?id=75809&action=edit" title="trace-cmd report run after the problem occurred.">[details]</a></span>
trace-cmd report run after the problem occurred.
Running Fedora 18, I updated on Feb 25 and started noticing that new windows
were completely black after a few hours of use. I generally first notice it
from tooltips, menus, or other popup windows, but quitting firefox and
restarting results in a fully black window once I hit the bug. I am using
xorg-x11-drv-intel-2.21.2-1.fc18.x86_64 <--- buggy
but when I downgraded to:
xorg-x11-drv-intel-2.20.14-1.fc18.x86_64
everything seems to work just fine for as many hours as I have tried (probably
2-3 days iirc). fwiw, I did downgrade some KDE packages and some other X
packages (not mesa btw, X server and X server common iirc) that were updated on
Feb 25, but was able to narrow it down to the driver.
In #intel-gfx IRC, ickle asked that I do a 'trace-cmd record -e i915' until it
failed, then a 'trace-cmd report', which is attached (it was only 15 minutes or
something after I started the record that it failed -- it was due as I had put
in 3 hours or so earlier in the day). Also attached is my Xorg.0.log from that
run ...</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>