linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
	Matthias-Christian Ott <ott@mirix.org>,
	Dominik Brodowski <linux@brodo.de>
Subject: Re: linux-next: cpufreq tree build failure
Date: Tue, 24 Feb 2009 22:45:04 -0500	[thread overview]
Message-ID: <20090225034504.GA25446@redhat.com> (raw)
In-Reply-To: <20090225142955.1104d5bc.sfr@canb.auug.org.au>

On Wed, Feb 25, 2009 at 02:29:55PM +1100, Stephen Rothwell wrote:
 > Hi Dave,
 > 
 > On Tue, 24 Feb 2009 11:51:03 -0500 Dave Jones <davej@redhat.com> wrote:
 > >
 > > On Tue, Feb 24, 2009 at 05:21:12PM +1100, Stephen Rothwell wrote:
 > >  > 
 > >  > Today's linux-next build (x86_64 allmodconfig) failed like this:
 > >  > 
 > >  > ERROR: "recalibrate_cpu_khz" [arch/x86/kernel/cpu/cpufreq/p4-clockmod.ko] undefined!
 > >  > 
 > >  > Caused by commit f20b61aa18b99d91c2a08f8863409bb8002d87fb ("[CPUFREQ] p4-clockmod reports wrong frequency").
 > >  > 
 > >  > I have dropped the cpufreq tree for today.
 > >  
 > > Odd. I fixed that up, as I noticed it when I first merged the diff.
 > > 
 > > Can you check that your tree has this bit..
 > > 
 > > diff --git a/arch/x86/include/asm/timer.h b/arch/x86/include/asm/timer.h
 > > index 2bb6a83..4f5c247 100644
 > > --- a/arch/x86/include/asm/timer.h
 > > +++ b/arch/x86/include/asm/timer.h
 > > @@ -11,8 +11,8 @@ unsigned long native_calibrate_tsc(void);
 > >  
 > >  #ifdef CONFIG_X86_32
 > >  extern int timer_ack;
 > > +#endif
 > >  extern int recalibrate_cpu_khz(void);
 > > -#endif /* CONFIG_X86_32 */
 > 
 > It does have that bit.  It failed to build again today.

oh hell, the function itself is guarded by an ifdef too.
for speed, my checking scripts only do the equivalent of building p4-clockmod.o,
so I missed this.

 > > It's possible you cloned it just before I rebased it with that fix.
 > There were no updates when I fetched you tree today.
 > 
 > Note that the error points to a modular build problem.  Maybe as
 > (Matthias-Christian Ott pointed out) this should not even be being built
 > for x86_64?

There were a bunch of 64bit Xeons made that lacked P-states.
Though using p4-clockmod as a replacement isn't a good idea, but we should
still allow it for thermal protection.
Also some of the Atoms are 64bit capable, but also lack P-states.

I'll nix the ifdefs and regenerate the tree.

thanks

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2009-02-25  3:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-24  6:21 linux-next: cpufreq tree build failure Stephen Rothwell
2009-02-24 16:51 ` Dave Jones
2009-02-25  3:29   ` Stephen Rothwell
2009-02-25  3:45     ` Dave Jones [this message]
2009-02-25  4:23       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-08-03  2:28 Stephen Rothwell
2009-08-03 23:22 ` Thomas Renninger
2009-08-03 23:44   ` Dave Jones
2009-02-05  7:54 Stephen Rothwell
2009-02-05  9:33 ` Thomas Renninger
2009-02-05  9:47 ` Thomas Renninger
2009-02-05 17:45   ` Dave Jones
2009-02-05 20:57     ` Thomas Renninger
2009-02-05 21:34       ` Dave Jones
2009-01-20  2:50 Stephen Rothwell
2009-01-20  5:30 ` Dave Jones
2009-01-20  6:23   ` Stephen Rothwell

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=20090225034504.GA25446@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@brodo.de \
    --cc=ott@mirix.org \
    --cc=sfr@canb.auug.org.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).