Re: x86-tip: cpufreq breakage - bisection fingers 89c9215165ca609096e845926d9a18f1306176a4

From: Tejun Heo
Date: Tue Mar 03 2009 - 20:59:42 EST


Hello,

Mike Galbraith wrote:
> On Tue, 2009-03-03 at 15:31 +0100, Ingo Molnar wrote:
>> * Mike Galbraith <efault@xxxxxx> wrote:
>>
>>> Box is Q6600, X86_64. I haven't poked at it other than to
>>> verify the bisection result via patchlet below data.
>>>
>>> [ 1.672700] overflow in relocation type 11 val 3a000f06b588
>>> [ 1.681051] `processor' likely not compiled with -mcmodel=kernel
>> btw., the .config you used, and the output of ld -v and gcc -v
>> would be nice as well.
>
> GNU ld (GNU Binutils; openSUSE 11.0) 2.18.50.20080409-11.1
>
> Using built-in specs.
> Target: x86_64-suse-linux
> Configured with: ../configure --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.3 --enable-ssp --disable-libssp --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --with-slibdir=/lib64 --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --program-suffix=-4.3 --enable-version-specific-runtime-libs --enable-linux-futex --without-system-libunwind --with-cpu=generic --build=x86_64-suse-linux
> Thread model: posix
> gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux)

I can't reproduce the problem here. My tool chains are newer tho
(11.1). Hmmm... I really don't see how calling a function or not can
cause relocation overflow in other places. For the linker, all three
setup_pcpu functions aren't that different.

I'll set up a 11.0 system and see whether I can reproduce the problem.
Just in case, can you please try to rebuild after mrproper?

--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/