<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [945gm regression] LVDS boots to blank screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=53926#c49">Comment # 49</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [945gm regression] LVDS boots to blank screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=53926">bug 53926</a> from <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>> --- <a href="show_bug.cgi?id=53926#c48">Comment #48</a> from Nathan Schulte <<a href="mailto:nmschulte@gmail.com">nmschulte@gmail.com</a>> --- > A few of the chosen bisection points would cause kernel panics from DRM/i915, > so I skipped these. At some point, much before the vanilla that the Debian 3.7 > kernel is built upon, the issue appears to have been fixed. How can that be? > Could there be multiple regressions causing and subsequently fixing this issue > throughout the history? Are you sure that the fixed versions are really included in 3.7? Since the drm-intel-next tree for e.g. 3.8 is usually based on some 3.6-rc kernel, git bisect can let you test kernel versions based on 3.6-rc kernels. But the actual set of patches is only included in 3.8, not 3.7. To check such a case run $ git tag --contains <commit-id> it'll list all the version tags which contain the given commit. If 3.7 is not among them, then it's just the branch-y nature of git messing around with you ;-) Can you please check that and if it's just that, continue the bisect?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>