<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 - resume from S3 slightly broken since kernel 3.10"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=77768">bug 77768</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 - resume from S3 slightly broken since kernel 3.10"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=77768#c9">Comment # 9</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - resume from S3 slightly broken since kernel 3.10"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=77768">bug 77768</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=77768#c8">comment #8</a>)
<span class="quote">> That patch masks the bug. But it still is a _kernel_ bug and not a bug of
> the xorg driver code. Wouldn't it be a better idea to fix the root cause?

> I wonder if only my special hardware is affected. I assume that this is not
> the case ...</span >

This really is a userspace bug imo - if we declare this a kernel bug we _must_
force a full detect cycle after suspend before userspace wakes up, which: a)
isn't how this stuff is supposed to work really b) pessimizes everyone else for
the sake of a few funky setups.

I know that upstream linux kernel has a hard "no regressions" rule, but
occasionally we need to bend this a bit.

Closing this since Chris patched the ddx, thanks a lot for your bug report.

commit aec3cbb1aba8bae5537534754ea57d21896d591b                                 
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>                                 
Date:   Wed Apr 23 09:17:22 2014 +0100                                          

    sna: Reuse any output not explicitly disconnected</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 on the CC list for the bug.</li>
      </ul>
    </body>
</html>