From: Gabriel C <nix.or.die@googlemail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Robert Hancock <hancockr@shaw.ca>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Gabriel C <crazy@frugalware.org>
Subject: Re: Clocksource tsc is always unstable with 2.6.25-* kernels and CONFIG_NO_HZ=y on my box
Date: Mon, 25 Feb 2008 21:48:06 +0100 [thread overview]
Message-ID: <47C32986.8010206@googlemail.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0802252031180.7583@apollo.tec.linutronix.de>
Thomas Gleixner wrote:
> On Mon, 25 Feb 2008, Gabriel C wrote:
>>>>> Booting nohz=off fixes that.
>>>>>
>>>>> Another strange thing is when I try to boot that kernel with
>>>>> clocksource=acpi_pm it just hangs.
>
> What happens if you add clocksource=acpi_pm and nohz=off to the kernel
> commandline ?
>
Then the kernel boots and it seems to work.
http://frugalware.org/~crazy/dmesg/lara/dmesg2
>>>> Please post your full dmesg output.
>>> Yes please.
>> dmesg's from 2.6.25-rc3 witch nohz={on,off} , lspci , dmidecode and
>> the used config for this kernel can be found there :
>>
>> http://frugalware.org/~crazy/dmesg/lara/
>
> Hmm. Nothing really obvious.
If you want I can build an debug kernel and boot with initcall_debug or anything else may help to find the problem,
just let me know.
>
> Thanks,
> tglx
>
Gabriel
next prev parent reply other threads:[~2008-02-25 20:48 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 ` Clocksource tsc is always unstable with 2.6.25-* kernels and CONFIG_NO_HZ=y on my box Robert Hancock
2008-02-25 7:40 ` Thomas Gleixner
2008-02-25 16:56 ` Gabriel C
2008-02-25 19:39 ` Thomas Gleixner
2008-02-25 20:48 ` Gabriel C [this message]
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=47C32986.8010206@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=crazy@frugalware.org \
--cc=hancockr@shaw.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox