<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - sna: (Haswell) X-server freezes when enabling DP at docking station" href="https://bugs.freedesktop.org/show_bug.cgi?id=71267#c148">Comment # 148</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - 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:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> Jani Nikula</a> <pre>(In reply to <a href="show_bug.cgi?id=71267#c147">comment #147</a>) > Created <a href="attachment.cgi?id=94007" name="attach_94007" title="dmesg with patch applied, old firmware">attachment 94007</a> <a href="attachment.cgi?id=94007&action=edit" title="dmesg with patch applied, old firmware">[details]</a> > dmesg with patch applied, old firmware > > I applied the patch on the FC20 3.12 kernel and although there was no > freeze, I got some scary error messages in my kernel logs. See attached > output. This is a Lenovo W540 laptop running Fedora 20 with the latest > laptop BIOS, but the old dock firmware. That is to be expected if the display port sink replies with repeated aux defer messages. Error for the retry limit first, then error for the modeset failing due to this. Don't worry about it. (The modeset failure message comes from the post-modeset state checker. We could handle this more gracefully, but there are scenarios where the failures we detect during modeset do not result in a non-working display... while bailing out early would definitely result in a non-working display.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>