Attachment 123355 Details for Bug 89055 – attachment-32584-0.html

attachment-32584-0.html

attachment-32584-0.html (text/html), 1.77 KB, created by Prasad H L Bhat on 2016-04-29 17:41:02 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Prasad H L Bhat

Created: 2016-04-29 17:41:02 UTC

Size: 1.77 KB

patch

obsolete

><div dir="ltr">Could someone please let me know how to apply this patchwork to mainstream kernel source?Â <div><br></div><div>I tried on the latest 4.6-rc5 and it failed. It did work on drm-intel-nightly though which is a not mainstream branch.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 26 April 2016 at 07:45,  <span dir="ltr">&lt;<a href="mailto:bugzilla-daemon@freedesktop.org" target="_blank">bugzilla-daemon@freedesktop.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
>    
>      
>    
>    <div>
>      <p>
>        </p><div>
>            <b><a title="REOPENED - [SKL APL] WARN_ON(!wm_changed) hit in the WM code with multiple pipes enabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=89055#c52" target="_blank">Comment # 52</a>
>              on <a title="REOPENED - [SKL APL] WARN_ON(!wm_changed) hit in the WM code with multiple pipes enabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=89055" target="_blank">bug 89055</a>
>              from <span><a href="mailto:dwk128@gmail.com" title="dwk128@gmail.com" target="_blank">dwk128@gmail.com</a>
></span></b>
>        <pre>I can confirm that this works for me on SKL, i5-6200U dell xps 13 9350. There
>used to be a crash at every boot and two on suspend, with external HDMI plugged
>in. I patched the drm-nightly kernel and compiled it manually.</pre>
>        </div>
>      <p></p><span class="">
>      <hr>
>      <span>You are receiving this mail because:</span>
>      
>      <ul>
>          <li>You are on the CC list for the bug.</li>
>      </ul>
>    </span></div>
></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>~ Prasad Bhat<br></div></div></div>
></div>

<div dir="ltr">Could someone please let me know how to apply this patchwork to mainstream kernel source?Â <div><br></div><div>I tried on the latest 4.6-rc5 and it failed. It did work on drm-intel-nightly though which is a not mainstream branch.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 26 April 2016 at 07:45,  <span dir="ltr">&lt;<a href="mailto:bugzilla-daemon@freedesktop.org" target="_blank">bugzilla-daemon@freedesktop.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
    
      
    
    <div>
      <p>
        </p><div>
            <b><a title="REOPENED - [SKL APL] WARN_ON(!wm_changed) hit in the WM code with multiple pipes enabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=89055#c52" target="_blank">Comment # 52</a>
              on <a title="REOPENED - [SKL APL] WARN_ON(!wm_changed) hit in the WM code with multiple pipes enabled" href="https://bugs.freedesktop.org/show_bug.cgi?id=89055" target="_blank">bug 89055</a>
              from <span><a href="mailto:dwk128@gmail.com" title="dwk128@gmail.com" target="_blank">dwk128@gmail.com</a>
</span></b>
        <pre>I can confirm that this works for me on SKL, i5-6200U dell xps 13 9350. There
used to be a crash at every boot and two on suspend, with external HDMI plugged
in. I patched the drm-nightly kernel and compiled it manually.</pre>
        </div>
      <p></p><span class="">
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>~ Prasad Bhat<br></div></div></div>
</div>

Actions: View

Attachments on bug 89055: 113297 | 119531 | 121513 | 122960 | 123355 | 123545

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.