does someone know if this patch has been applied already to
I installed this image yesterday and had the idea to test the
drm.edid_strict=0 parameter on it today. - It works like a charm.
Dunno why my patch didn't work... (But I don't have the time nor the
mood to track this down atm.)
Nevertheless: Thank you for trying to help me. - And sorry for
bugreporting this twice and not cc-ing the last mail. Reason for the
first was that I never used reportbug on this machine before and
therefore had no .reportbugrc on it which caused in a nonexistent mail
address due to some circumstances.
On Tue, May 03, 2011 at 02:01:08PM -0500, Jonathan Nieder wrote:
> Thanks; cc-ing the bug log.
> So, my only other suggestion is a few rounds of bisection. It works
> like this:
> apt-get install git build-essential
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> cd linux-2.6
> git bisect start
> git bisect bad v2.6.37
> git bisect good v2.6.32; # or whichever was known to be good
> # now it checks out a version half-way between
> make localmodconfig; # minimal configuration
> make deb-pkg
> ... install the package, reboot, test ...
> git bisect good; # if it doesn't spam dmesg
> git bisect bad; # if it does
> git bisect skip; # if some other bug makes it hard to test
> # okay, next iteration...
> make oldconfig
> make deb-pkg
> At the end of this process, we would know what the "first bad commit"
> is, which can be very helpful for tracking it down. Just narrowing
> down the regression range with a few rounds is already useful; in that
> case, if you send "git bisect log" output at the end we should be able
> to use it to figure something out. If you are the visual sort of
> person like I am, "git bisect visualize" with gitk installed can show
> what's going on between steps.
> Thanks again for working on this, and sorry I don't have more useful