<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - sna: (Haswell) X-server freezes when enabling DP at docking station" href="https://bugs.freedesktop.org/show_bug.cgi?id=71267#c24">Comment # 24</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - sna: (Haswell) X-server freezes when enabling DP at docking station" href="https://bugs.freedesktop.org/show_bug.cgi?id=71267">bug 71267</a> from <a class="email" href="mailto:consume.noise@gmail.com" title="Daniel Martin <consume.noise@gmail.com>"> Daniel Martin</a> <pre>I even tried this in ironlake_panel_vdd_work() before it locks mode_config.mutex: if (mutex_is_locked(&dev->mode_config.mutex)) mutex_unlock(&dev->mode_config.mutex); I know that's not atomic. But, in case of the bug it runs into the if-clause (so, the mutex is locked) and gives a warning about an unbalanced unlock. Then it moves on and ironlake_panel_vdd_work() gets stuck when trying to lock mode_config.mutex. I've also tested various module parameters (and combinations of), i.e. disabling rc6, powersave, fbc (as Chris mentioned) ... to see if they cause any side effects. For testing I've noticed that I don't need an X-server to trigger it. With those additional kernel messages I've sprinkled before, inside and when leaving a lock on mode_config.mutex I can see when it runs and get stuck in ironlake_panel_vdd_work(). For this I just need to boot without the monitor and plug it in when the system is up. Is there anything else I can provide or should test to help you with this bug?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>