<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [gm45/ivb fastboot sna] HDMI connection hidden behind dock during boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=66494#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [gm45/ivb fastboot sna] HDMI connection hidden behind dock during boot" href="https://bugs.freedesktop.org/show_bug.cgi?id=66494">bug 66494</a> from <a class="email" href="mailto:consume.noise@gmail.com" title="Daniel Martin <consume.noise@gmail.com>"> Daniel Martin</a> <pre>(In reply to <a href="show_bug.cgi?id=66494#c22">comment #22</a>) > Created <a href="attachment.cgi?id=81892" name="attach_81892" title="Listen for ACPI dock events and">attachment 81892</a> <a href="attachment.cgi?id=81892&action=edit" title="Listen for ACPI dock events and">[details]</a> <a href='page.cgi?id=splinter.html&bug=66494&attachment=81892'>[review]</a> [review] > Listen for ACPI dock events and > > Can you please try this kernel patch and see what happens? The logging > requires drm.debug=6. It doesn't change anything and the ...event=... message doesn't show up. I've added debug messages to see when the introduced functions get called and if register_dock_notifier() fails. With that, at least a message shows up that intel_dock_register() gets called, register_dock_notifier() doesn't fail. So, I wondered if it makes a difference if the thinkpad_acpi module is compiled in or not. It doesn't, no ...event=... message. These tests have been made with kernel 3.10 (+ drm.debug=6) and xf86-video-intel (+enable-debug=full) including commit 158095ff2b2d38f54ca91d2a728f919cd705ff62 sna/gen2: Fix alpha replication in the copy pipeline Additionally, I've booted into the X server, waited a few seconds, removed the monitor cable and connected it after a few seconds again. The log messages (dmesg and Xorg.0.log) for both tests (thinkpad_acpi+video compiled in or not) will float in ...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>