Hello Peter, I'm seeing similar GCOV problems as with 2.6.26-rc5-mm1 that you fixed. This is the same x86_64 box and again it was unable to boot with gcov enabled. A quick look revealed that arch/x86/tsc_64.c and arch/x86/tsc_32.c code was unified. Unfortunately simple change of GCOV_tsc_32.o := n GCOV_tsc_64.o := n to GCOV_tsc.o := n did not help. Given the amount of combinations of which set of files with GCOV might cause failures I was rather fortunate and after a few hours I was able to pinpoint exactly two files which need GCOV disabled to make my x86_64 boot. If you want to try to figure out what is wrong with them please feel free to send me patches to test. If not then how about this patch? Compile and run tested. Signed-off-by: Mariusz Kozlowski <m.kozlowski@xxxxxxxxxx> --- linux-2.6.27-rc1-mm1/arch/x86/kernel/Makefile 2008-08-01 18:05:04.000000000 +0200 +++ linux-2.6.27-rc1-mm1-dirty/arch/x86/kernel/Makefile 2008-08-05 21:49:21.000000000 +0200 @@ -13,8 +13,8 @@ CFLAGS_REMOVE_rtc.o = -pg CFLAGS_REMOVE_paravirt.o = -pg endif -GCOV_tsc_32.o := n -GCOV_tsc_64.o := n +GCOV_vsyscall_64.o := n +GCOV_tsc.o := n # # vsyscalls (which work on the user stack) should have Mariusz -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
