https://bugs.freedesktop.org/show_bug.cgi?id=36007
--- Comment #16 from Alex Deucher <[email protected]> 2011-04-09 08:42:19 PDT --- At this point it would be easiest to bisect your kernel. To do that, check out a git tree and then start bisecting. With bisect, you tell git the a known good and known bad commits, and then it check out a commit halfway between the two specified. you compile and test that commit and then tell it if it was good or bad ('git bisect good' or 'git bisect bad') and it will continue to bisect until the problematic commit is found. See: http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html # clone the git tree git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git # change to the newly checked out tree cd linux-2.6 # start bisecting git bisect start # specify the bad commit git bisect bad v2.6.38 # specify the good commit git bisect good v2.6.37 # ...built/test # if the commit is good git bisect good #if it's bad git bisect bad # if there is another problem (won't build/won't boot, etc. git bisect skip # at the end git will point you to the problematic commit. # to reset your git tree after you are done git bisect reset -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
