Date: Sun, 10 Dec 2006 09:02:15 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Rui Nuno Capela <rncbc@rncbc.org>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
       linux-rt-users@vger.kernel.org
Subject: Re: 2.6.19-rt11 boot failure
Message-ID: <20061210080215.GA12359@elte.hu>
References: <60535.192.168.1.8.1165699722.squirrel@www.rncbc.org> <1165700275.24604.350.camel@localhost.localdomain> <457B5ABE.4080709@rncbc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <457B5ABE.4080709@rncbc.org>
User-Agent: Mutt/1.4.2.2i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1127
Lines: 31


* Rui Nuno Capela <rncbc@rncbc.org> wrote:

> >> Sorry for the interrupt, but all my 2.6.19-rt11 builds very fail 
> >> early on boot. It doesn't matter if its UP or SMP. This is a sample 
> >> of what I could capture on one case via serial console:
> > 
> > Can you please disable CONFIG_HPET_TIMER ?
> 
> Yes, sorry :) now it boots and runs apparently fine.
> 
> I always had HPET_TIMER enabled until now. Ok, last time I tried was 
> on 2.6.19-rt6.  Somehow I've failed to know or simply missed whether 
> HPET it's supposed to be off on PREEMPT_RT kernels. Maybe some simple 
> heads-up would be welcome :)

by -rt12 time we'll hopefully be able to get HPET back into working 
order again.

> Notice that lately I have both HIGH_RES_TIMERS and NO_HZ enabled. Is 
> there any sense on having those options mutually exclusive with 
> HPET_TIMER ?

nope, it's a regression.

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