mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: tglx@linutronix.de
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.13-rt14 fails to build (smp)
Date: Tue, 20 Sep 2005 13:34:11 -0700	[thread overview]
Message-ID: <1127248451.4623.4.camel@cmn3.stanford.edu> (raw)
In-Reply-To: <1127197575.24044.310.camel@tglx.tec.linutronix.de>

On Tue, 2005-09-20 at 08:26 +0200, Thomas Gleixner wrote:
> On Mon, 2005-09-19 at 18:05 -0700, Fernando Lopez-Lezcano wrote:
> > Hi Ingo, just hit this problem trying to build rt14, this is on the SMP
> > build, with 
> > # CONFIG_HIGH_RES_TIMERS is not set
> > Find the .config I used attached...
> > 
> > kernel/ktimers.c: In function 'migrate_ktimer_list':
> 
> Uuurg. HOTPLUG_CPU
> 
> tglx
> 
> Index: linux-2.6.13-rt12/kernel/ktimers.c
> ===================================================================
> --- linux-2.6.13-rt12.orig/kernel/ktimers.c
> +++ linux-2.6.13-rt12/kernel/ktimers.c
> @@ -865,11 +865,11 @@ static void migrate_ktimer_list(struct k
>  	struct ktimer *timer;
>  	struct rb_node *node;
>  
> -	while ((node = rb_first(&old_base->root))) {
> -		timer = rb_entry(node, struct ktimer, tnode);
> +	while ((node = rb_first(&old_base->active))) {
> +		timer = rb_entry(node, struct ktimer, node);
>  		remove_ktimer(timer, old_base);
>  		timer->base = new_base;
> -		enqueue_ktimer(timer, new_base, NULL);
> +		enqueue_ktimer(timer, new_base, NULL, KTIMER_RESTART);
>  	}
>  }

Compiles with the patch, thanks!
But depmod complains:

WARNING: /lib/modules/2.6.13-0.3.rdt.rhfc4.ccrmasmp/kernel/drivers/char/hangcheck-timer.ko needs unknown symbol monotonic_clock

-- Fernando



      reply	other threads:[~2005-09-20 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-20  1:05 Fernando Lopez-Lezcano
2005-09-20  6:26 ` Thomas Gleixner
2005-09-20 20:34   ` Fernando Lopez-Lezcano [this message]

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=1127248451.4623.4.camel@cmn3.stanford.edu \
    --to=nando@ccrma.stanford.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®