[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#624549: bug in radeon driver module of linux 2.6.38 (since 2.6.35)

Martin Teufel wrote:

> *g* - yes, I know that drm_kms_helper.poll=0 != drm.edid_strict=0.
> I temporarily removed drm_kms_helper.poll=0 and added drm.edid_strict=0
> to the linux kernel parameters (replaced it).
> Hm, I will try it a second time and see what happens (but don't think it
> will change something).
> Strange thing...

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


Reply to: