<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - DP MST problems with xrandr while re-docking" href="https://bugs.freedesktop.org/show_bug.cgi?id=80355#c31">Comment # 31</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - DP MST problems with xrandr while re-docking" href="https://bugs.freedesktop.org/show_bug.cgi?id=80355">bug 80355</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to <a href="show_bug.cgi?id=80355#c30">comment #30</a>) > Comment on <a href="attachment.cgi?id=101777" name="attach_101777" title="Kernel oops upon re-docking">attachment 101777</a> <a href="attachment.cgi?id=101777&action=edit" title="Kernel oops upon re-docking">[details]</a> > Kernel oops upon re-docking > > I got confused again; this OOPS seems relevant here. If I understood > correctly, this is what had happened: there were two crashes, one in X and > another one in the intel-dri kernel module. Should I file this OOPS as a > bug in intel-dri or send it to Airlie by some means? Doesn't look like his bug... Should be fixed by commit 5ea1f752ae04be403a3dc8ec876a60d7f5f6990a Author: Rob Clark <<a href="mailto:robdclark@gmail.com">robdclark@gmail.com</a>> Date: Fri May 30 12:29:48 2014 -0400 drm: add drm_fb_helper_restore_fbdev_mode_unlocked() All drm_fb_helper_restore_fbdev_mode() call sites, save one, do the same locking. Simplify this into drm_fb_helper_restore_fbdev_mode_unlocked(). Signed-off-by: Rob Clark <<a href="mailto:robdclark@gmail.com">robdclark@gmail.com</a>> Reviewed-by: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>> Signed-off-by: Dave Airlie <<a href="mailto:airlied@redhat.com">airlied@redhat.com</a>></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>