From: john stultz <johnstul@us.ibm.com>
To: Philippe Troin <phil@fifi.org>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: Clock incorrect on 2.6.31-rc2
Date: Wed, 15 Jul 2009 15:57:15 -0700 [thread overview]
Message-ID: <1247698635.7511.181.camel@localhost.localdomain> (raw)
In-Reply-To: <87hbxfxgct.fsf@old-tantale.fifi.org>
On Tue, 2009-07-14 at 11:35 -0700, Philippe Troin wrote:
> Stephen Hemminger <shemminger@vyatta.com> writes:
>
> > > I'm a little stumped. Does the problem occur on every reboot? How long
> > > does the box need to be up before you see an issue? Or does it go away
> > > after a little while?
> >
> > It seemed to take a while (several hours). I will leave it running overnight
>
> Interestingly, I am seeing the same problem on two boxes with
> 2.6.2{5,6}. I haven't checked yet more recent kernels.
I suspect your issue and Stephen's issue are separate.
> The odd thing was that booting with "nohz=off highres=off" did not
> help, the only cure was to recompile the kernel and disable
> CONFIG_HIGH_RES_TIMERS and CONFIG_NO_HZ.
>
> This is the thread back then:
> http://marc.info/?t=121563147700003&r=1&w=2
Thomas, did you ever take a look at this? It looks like something's off
w/ hrt.
thanks
-john
next prev parent reply other threads:[~2009-07-15 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 21:10 Clock incorrect on 2.6.31-rc2 Stephen Hemminger
2009-07-09 21:45 ` Thomas Gleixner
2009-07-09 21:58 ` john stultz
2009-07-09 22:38 ` Stephen Hemminger
2009-07-09 23:22 ` john stultz
2009-07-09 23:30 ` Stephen Hemminger
2009-07-14 18:35 ` Philippe Troin
2009-07-15 22:57 ` john stultz [this message]
2009-09-11 3:29 ` Philippe Troin
2009-07-15 22:58 ` john stultz
2009-07-16 15:08 ` Stephen Hemminger
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=1247698635.7511.181.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@fifi.org \
--cc=shemminger@vyatta.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.