From: john stultz <johnstul@us.ibm.com>
To: "Guilherme M. Schroeder" <guilherme@centralinf.com.br>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.21-rc7: HPET enabled freeze my machine at boot
Date: Mon, 23 Apr 2007 15:53:05 -0700 [thread overview]
Message-ID: <1177368785.12242.9.camel@localhost> (raw)
In-Reply-To: <1177367429.12242.7.camel@localhost>
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@centralinf.com.br> wrote:
> > >> Hi,
> > >>
> > >> 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.
> > >
> > > Hmmm.. What happens if you boot w/ clocksource=acpi_pm ?
> > >
> > >
> >
> > Boot ok with clocksource=acpi_pm and HPET enabled.
> > Any clue?
>
>
> 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?
thanks
-john
diff --git a/arch/i386/kernel/hpet.c b/arch/i386/kernel/hpet.c
index 17d7345..14e76a5 100644
--- a/arch/i386/kernel/hpet.c
+++ b/arch/i386/kernel/hpet.c
@@ -183,9 +183,6 @@ static void hpet_set_mode(enum clock_event_mode mode,
case CLOCK_EVT_MODE_UNUSED:
case CLOCK_EVT_MODE_SHUTDOWN:
- cfg = hpet_readl(HPET_T0_CFG);
- cfg &= ~HPET_TN_ENABLE;
- hpet_writel(cfg, HPET_T0_CFG);
break;
}
}
next prev parent reply other threads:[~2007-04-23 22:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 20:57 2.6.21-rc7: HPET enabled freeze my machine at boot guilherme
2007-04-20 21:53 ` john stultz
2007-04-21 23:07 ` Guilherme M. Schroeder
2007-04-23 22:30 ` john stultz
2007-04-23 22:53 ` john stultz [this message]
2007-04-24 12:26 ` Guilherme M. Schroeder
2007-04-24 12:33 ` Guilherme M. Schroeder
2007-04-24 12:18 ` Guilherme M. Schroeder
-- strict thread matches above, loose matches on Subject: below --
2007-04-20 12:23 guilherme
2007-04-20 14:08 ` Andi Kleen
2007-04-20 13:29 ` guilherme
2007-04-20 14:38 ` Andi Kleen
2007-04-20 15:11 ` guilherme
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=1177368785.12242.9.camel@localhost \
--to=johnstul@us.ibm.com \
--cc=guilherme@centralinf.com.br \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.