<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [i915] kernel 3.11.2 intel_pipe_config_compare ERROR" href="https://bugs.freedesktop.org/show_bug.cgi?id=69875#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [i915] kernel 3.11.2 intel_pipe_config_compare ERROR" href="https://bugs.freedesktop.org/show_bug.cgi?id=69875">bug 69875</a> from <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>(In reply to <a href="show_bug.cgi?id=69875#c10">comment #10</a>) > Comment on <a href="attachment.cgi?id=86795" name="attach_86795" title="dmesg output">attachment 86795</a> <a href="attachment.cgi?id=86795&action=edit" title="dmesg output">[details]</a> > dmesg output > > This is on a headless home server, reproducible at every boot, error first > showed up in 3.11.2 when updating from 3.11.1 This is a dupe of <a class="bz_bug_link bz_status_VERIFIED bz_closed" title="VERIFIED FIXED - [GM45 Bisected]Boot system has <3>[ 1.894068] [drm:intel_pipe_config_compare] *ERROR* mismatch in adjusted_mode.flags(DRM_MODE_FLAG_NHSYNC) (expected 2, found 0)" href="show_bug.cgi?id=69791">bug #69791</a>. In general _please_ file new bug reports, it's much easier for us to mark a bug as a duplicate than to untangle a maze of me-too reports that effectively are all different bug reports. I know that bugzilla gives you a neat list of possible dupes, but ignoring that is usually the best option. Of course if an upstream dev told you (on irc or so) that there's a bug report already that's different.</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> <li>You are the assignee for the bug.</li> </ul> </body> </html>