linux-kernel - Re: 2.6.19-rt11 boot failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 10 Dec 2006 09:02:15 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Rui Nuno Capela <rncbc@...bc.org>
Cc:	tglx@...utronix.de, linux-kernel@...r.kernel.org,
	linux-rt-users@...r.kernel.org
Subject: Re: 2.6.19-rt11 boot failure


* Rui Nuno Capela <rncbc@...bc.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/