public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefano Brivio <stefano.brivio@polimi.it>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dave Jones <davej@redhat.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org, Michael Buesch <mb@bu3sch.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Len Brown <lenb@kernel.org>
Subject: Re: [BUG] jiffies counter leaps in 2.6.24-rc3
Date: Thu, 29 Nov 2007 21:12:40 +0100	[thread overview]
Message-ID: <20071129211240.007fb459@morte> (raw)
In-Reply-To: <20071129193624.GA15245@elte.hu>

On Thu, 29 Nov 2007 20:36:24 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> just to make sure there is no tsc impact, does booting with "notsc" 
> change anything?

No, it doesn't.

> if not, does booting with idle=halt or idle=poll help? [your power usage 
> will go up so it's not very useful - but it could help exclude a few 
> sources of trouble.]

With idle=poll nothing changes, except that - as soon as I switch the CPU
frequency - I get this in the logs:

[  297.562722] Marking TSC unstable due to: cpufreq changes.
[  297.566677] Time: acpi_pm clocksource has been installed.

With idle=halt, changing frequency just freezes the system. I can't even use
the magic Sys Rq keys then.

I observed another thing. When I don't use any of the parameters you
suggested for debugging, I get this at boot:

[    6.530752] Marking TSC unstable due to: possible TSC halt in C2.
[    6.530761] Time: acpi_pm clocksource has been installed.
[    6.620700] Clocksource tsc unstable (delta = -456217276 ns)


-- 
Ciao
Stefano

  reply	other threads:[~2007-11-29 20:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-24 16:51 [BUG] jiffies counter leaps in 2.6.24-rc3 Stefano Brivio
2007-11-24 17:56 ` Frans Pop
2007-11-24 18:09   ` Stefano Brivio
2007-11-24 18:48 ` Rafael J. Wysocki
2007-11-24 18:46   ` Stefano Brivio
2007-11-24 19:31     ` Rafael J. Wysocki
2007-11-26 18:00       ` Stefano Brivio
2007-11-29  7:20       ` Stefano Brivio
2007-11-29 10:33         ` Ingo Molnar
2007-11-29  8:50       ` Stefano Brivio
2007-11-29 10:35         ` Ingo Molnar
2007-11-29 17:45           ` Dave Jones
2007-11-29 17:57             ` Stefano Brivio
2007-11-29 18:24               ` Dave Jones
2007-11-29 19:25                 ` Stefano Brivio
2007-11-29 19:36                   ` Ingo Molnar
2007-11-29 20:12                     ` Stefano Brivio [this message]
2007-11-29 20:04                   ` Dave Jones

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=20071129211240.007fb459@morte \
    --to=stefano.brivio@polimi.it \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --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