public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: John Stultz <john.stultz@linaro.org>
Cc: Fedora Kernel Team <kernel-team@fedoraproject.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: WARNING: Adjusting tsc more then 11%
Date: Mon, 5 Mar 2012 14:23:38 -0500	[thread overview]
Message-ID: <20120305192338.GA30491@redhat.com> (raw)
In-Reply-To: <1330972323.2191.74.camel@work-vm>

On Mon, Mar 05, 2012 at 10:32:03AM -0800, John Stultz wrote:
 > On Mon, 2012-03-05 at 10:44 -0500, Dave Jones wrote:

 > > any idea what could have changed to start tripping that up ?
 > > 
 > > The reports seem to have started around 3.3-rc4.
 > 
 > Huh. No I don't know what would have started causing such a warning. I
 > had expected that there would be some edge hardware that might trip that
 > warning, but I'd expect the noise to start there w/ 3.2 after it was
 > introduced. There's only been spelling & comment changes to the
 > timekeeping core in the 3.3-rc series.

thinking about this some more, while the reports starts around rc4, this
may have been caused by something prior to that, as anyone moving from
Fedora 16 or earlier to F17 alpha would have jumped quite a kernel version or two.

 > Do you know if this is an occasional thing on any of the affected
 > hardware, or if it happens after every reboot?

Out of all the people running the Fedora 17 alpha, this has only shown
up those four times, so it does seem to be a rare thing.
I suspect we'll get more instances of it as more people start testing.

Three of the reporters noted that it happened on boot.

 > Are any of the reported boxes systems you have access to in order to
 > reproduce?

unfortunately not.

	Dave


  reply	other threads:[~2012-03-05 19:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 15:44 WARNING: Adjusting tsc more then 11% Dave Jones
2012-03-05 18:32 ` John Stultz
2012-03-05 19:23   ` Dave Jones [this message]
2012-03-05 19:50     ` John Stultz
2012-03-05 19:56       ` Josh Boyer
2012-03-05 20:24         ` John Stultz
2012-03-05 20:28           ` Josh Boyer
2012-03-05 20:41             ` John Stultz
2012-03-05 19:57       ` Dave Jones
2012-03-05 20:16         ` Sasha Levin
2012-03-05 20:27           ` John Stultz
2012-03-05 20:36             ` Sasha Levin
2012-03-07  1:13               ` John Stultz
2012-03-22 19:11                 ` Sasha Levin
2012-03-22 19:21                   ` John Stultz
2012-03-22 15:28     ` 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=20120305192338.GA30491@redhat.com \
    --to=davej@redhat.com \
    --cc=john.stultz@linaro.org \
    --cc=kernel-team@fedoraproject.org \
    --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