<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:przanoni@gmail.com" title="Paulo Zanoni <przanoni@gmail.com>"> <span class="fn">Paulo Zanoni</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - [HSW AIO] i915 oops during suspend/hibernate"
href="https://bugs.freedesktop.org/show_bug.cgi?id=61508">bug 61508</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>WONTFIX
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - [HSW AIO] i915 oops during suspend/hibernate"
href="https://bugs.freedesktop.org/show_bug.cgi?id=61508#c25">Comment # 25</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - [HSW AIO] i915 oops during suspend/hibernate"
href="https://bugs.freedesktop.org/show_bug.cgi?id=61508">bug 61508</a>
from <span class="vcard"><a class="email" href="mailto:przanoni@gmail.com" title="Paulo Zanoni <przanoni@gmail.com>"> <span class="fn">Paulo Zanoni</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=61508#c24">comment #24</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=61508#c23">comment #23</a>)
> > I don't object dropping 0CXX. I just want to preserve 04XX.
>
> 0x04xx are the release pciids and also used by later sdvs. 0x0cxx is used by
> really early sdvs and we've already started to remove specific hacks for
> them. So I think we can drop the 0x0cxx ids without upsetting anyone.</span >
Patch merged: "drm/i915: print a message when we detect an early Haswell SDV".
So now we print a dmesg message whenever someone is using the 0x0CXX machines.
The driver still loads, but at least we tell the users to expect problems, and
when they report bugs we'll be able to look at dmesg, find the message and tell
them to try to reproduce the bug on real-world hardware.
<a href="http://cgit.freedesktop.org/~danvet/drm-intel/commit/?h=drm-intel-next-queued&id=175d3c1b176af5ad2196064a66a45e97582239d5">http://cgit.freedesktop.org/~danvet/drm-intel/commit/?h=drm-intel-next-queued&id=175d3c1b176af5ad2196064a66a45e97582239d5</a>
Closing bug. If you can still reproduce the bug on other Haswell machines with
a recent BIOS, please reopen this bug or open a new bug report.
Thanks,
Paulo</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>