On Mon, 2007-04-23 at 15:30 -0700, john stultz wrote:-On Sat, 2007-04-21 at 20:07 -0300, Guilherme M. Schroeder wrote:john stultz wrote:On 4/19/07, guilherme <guilherme@xxxxxxxxxxxxxxxxx> wrote:Boot ok with clocksource=acpi_pm and HPET enabled.Hi,Hmmm.. What happens if you boot w/ clocksource=acpi_pm ?
If i enable "High Resolution Timer Support", my machine stops here at boot:
Clocksource tsc unstable (delta = -297340790165 ns)
Time: hpet clocksource has been installed.
If i disable HPET, it boots fine.
I'm suspecting that your HPET counter is being stopped for some reason,
although why I have no idea.
Just to get a clear picture, does this happen w/ "Tickless System
(Dynamic ticks)" disabled in the menuconfig?
Thomas, might we be actually stopping the HPET counter instead of
disabling the HPET interrupt w/ dynticks?
Just a shot in the dark, but does this patch affect the behavior?
diff --git a/arch/i386/kernel/hpet.c b/arch/i386/kernel/hpet.c
index 17d7345..14e76a5 100644
@@ -183,9 +183,6 @@ static void hpet_set_mode(enum clock_event_mode mode,
- cfg = hpet_readl(HPET_T0_CFG);
- cfg &= ~HPET_TN_ENABLE;
- hpet_writel(cfg, HPET_T0_CFG);