[Bug 53926] [945gm regression] LVDS boots to blank screen

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=53926

--- Comment #65 from Nathan Schulte <nmschulte at gmail.com> ---
Hmm.  I have no idea, I'm not that familiar with the code base.

I would recommend you try performing the bisection as I did, and note the
commits that break/fix your issue in your bug report?  In hindsight, I probably
should have made a new bug report for my specific hardware.

One thing I want to note:  While I was testing each kernel, I noticed a sort of
pattern.

1) Boot 3.8-rc3 to build next bisected kernel.
2) Reboot into new kernel; would boot fine, no issue.
3) Reboot into new kernel again (via SysRq+REISUB); would boot fine, no issue.
3) Reboot into new kernel again (via SysRq+REISUB); would not boot fine, issue
present.
5) Boot 3.8-rc3 to build next bisected kernel.
6) Reboot into new kernel; would boot fine, no issue.
6) Reboot into new kernel again (via SysRq+REISUB); would boot fine, no issue.
7) Reboot into new kernel again (via SysRq+REISUB); would not boot fine, issue
present.

For every kernel that had the problem, it seems that every fourth boot (every
third of the kernel in question) would be the one that would cause the issue. 
I got into such a rhythm of building kernels (I did it over 100 times...), I
would be building a new kernel every fourth warm-boot.  I wonder if this
pattern is helpful at all to diagnose the issue.

Anyway, my point for Tomas: it seems as though if you get into a pattern like
that, you shouldn't have to test each kernel more than three times.  While I
was testing, for the kernels that did not have an issue on the third boot, I
would reboot them 10 times or more just to make sure.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130119/a9ff427c/attachment.html>