From: Robert Hancock <hancockr@shaw.ca>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Gabriel C <crazy@frugalware.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Clocksource tsc is always unstable with 2.6.25-* kernels and CONFIG_NO_HZ=y on my box
Date: Sun, 24 Feb 2008 22:33:27 -0600 [thread overview]
Message-ID: <47C24517.7010204@shaw.ca> (raw)
In-Reply-To: <fa.FpheN5sIQ5rxoLHYuhxxf6uauVs@ifi.uio.no>
Gabriel C wrote:
> Hi,
>
> I noticed tsc is always marked unstable on my box with 2.6.25* , 2.6.24 is fine.
>
> ..
>
> [ 0.825760] ACPI: PCI Interrupt 0000:03:0e.0[A] -> GSI 22 (level, low) -> IRQ 22
> [ 0.805755] Switched to high resolution mode on CPU 1
> [ 0.794244] Switched to high resolution mode on CPU 2
> [ 0.766968] Switched to high resolution mode on CPU 3
> [ 1.083944] Switched to high resolution mode on CPU 0
> [ 15.388792] Clocksource tsc unstable (delta = 9373391604 ns)
> [ 15.714648] Time: acpi_pm clocksource has been installed.
>
> ..
>
> Booting nohz=off fixes that.
>
> Another strange thing is when I try to boot that kernel with clocksource=acpi_pm it just hangs.
>
> config is attached.
>
> Please let me know if you need more infos / want me to try patches or anything else.
Please post your full dmesg output.
next parent reply other threads:[~2008-02-25 4:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.FpheN5sIQ5rxoLHYuhxxf6uauVs@ifi.uio.no>
2008-02-25 4:33 ` Robert Hancock [this message]
2008-02-25 7:40 ` Clocksource tsc is always unstable with 2.6.25-* kernels and CONFIG_NO_HZ=y on my box Thomas Gleixner
2008-02-25 16:56 ` Gabriel C
2008-02-25 19:39 ` Thomas Gleixner
2008-02-25 20:48 ` Gabriel C
2008-03-12 7:11 ` Thomas Gleixner
2008-03-13 3:30 ` Gabriel C
2008-02-24 0:31 Gabriel C
2008-02-25 20:14 ` Andrew Morton
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=47C24517.7010204@shaw.ca \
--to=hancockr@shaw.ca \
--cc=crazy@frugalware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.com \
--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.