All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: x86-tip: cpufreq breakage - bisection fingers	89c9215165ca609096e845926d9a18f1306176a4
Date: Wed, 04 Mar 2009 10:59:19 +0900	[thread overview]
Message-ID: <49ADE077.1060606@kernel.org> (raw)
In-Reply-To: <1236098338.5926.0.camel@marge.simson.net>

Hello,

Mike Galbraith wrote:
> On Tue, 2009-03-03 at 15:31 +0100, Ingo Molnar wrote:
>> * Mike Galbraith <efault@gmx.de> 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

  reply	other threads:[~2009-03-04  1:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 13:07 x86-tip: cpufreq breakage - bisection fingers 89c9215165ca609096e845926d9a18f1306176a4 Mike Galbraith
2009-03-03 14:31 ` Ingo Molnar
2009-03-03 16:38   ` Mike Galbraith
2009-03-04  1:59     ` Tejun Heo [this message]
2009-03-04  3:43       ` Mike Galbraith
2009-03-04  6:14         ` Mike Galbraith
2009-03-04  6:31           ` Tejun Heo
2009-03-04  9:38             ` Tejun Heo
2009-03-04  9:43               ` Tejun Heo
2009-03-04 10:44                 ` Mike Galbraith
2009-03-04 13:58                   ` Tejun Heo
2009-03-04 14:35                     ` Mike Galbraith
2009-03-04 14:40                       ` Mike Galbraith
2009-03-04 17:08                       ` Ingo Molnar
2009-03-05  4:36                       ` Tejun Heo
2009-03-04 12:13               ` Mike Galbraith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49ADE077.1060606@kernel.org \
    --to=tj@kernel.org \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.