<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bisected] G69/nv50 DisplayPort dual-head fails to switch to KMS" href="https://bugs.freedesktop.org/show_bug.cgi?id=63135#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bisected] G69/nv50 DisplayPort dual-head fails to switch to KMS" href="https://bugs.freedesktop.org/show_bug.cgi?id=63135">bug 63135</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>[ 11.902160] RIP: 0010:[<ffffffffa0570160>] [<ffffffffa0570160>] drm_fb_helper_hotplug_event+0x10/0x100 [drm_kms_helper] That seems to imply that drm->fbcon->helper == NULL. But that's not what you're seeing on recent kernels, so the implication is that there's some sort of second concurrency bug in the rev you identified that got fixed later on.... I don't think that your bisect results are valid as a result :( Was the original problem 100% reproducible? If so, you should mark any kernel that works sometimes as "good" (even if it's not really *that* good). Also, the original problem is just monitors not working, but you can ssh in/etc, right? Or does the system totally hang? (Doesn't seem that way given that logs showed up in systemd...)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>