From: john stultz <johnstul@us.ibm.com>
To: Andy Pfiffer <andyp@osdl.org>
Cc: Andreas Haumer <andreas@xss.co.at>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.7[23]: wall-clock time advancing too rapidly?
Date: 23 Jun 2003 17:37:20 -0700 [thread overview]
Message-ID: <1056415040.1028.82.camel@w-jstultz2.beaverton.ibm.com> (raw)
In-Reply-To: <1056413771.1209.14.camel@andyp.pdx.osdl.net>
On Mon, 2003-06-23 at 17:16, Andy Pfiffer wrote:
> Hmmm... I tried the patch in 2.5.73 and it appeared to have no effect.
Ah, just when I sent it off to Andrew. Well, I've been getting a number
of successful reports, so its still good to give it further testing.
> The system continues to advance what it thinks is wall-clock time by
> about 7.25 seconds for every 15 seconds actual wall-clock time:
[snip]
>
> None of the printk's in the patch have been printed on the console.
Yea, it clearly isn't triggering the code.
> Adding "clock=pit" continues to work as a workaround.
>
> I have attached the output of dmesg from the boot of the kernel with the
> patch present.
Looking over it again you're still not showing any of the signs of
changing cpu-frequency. But the symptoms are very similar. I'm curious,
this is the x220? Do you have a service processor installed in that box?
Maybe we're running into some sort of SMI trouble?
thanks
-john
next prev parent reply other threads:[~2003-06-24 0:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 16:10 2.5.72: " Andy Pfiffer
2003-06-19 21:30 ` john stultz
2003-06-20 14:01 ` Wiktor Wodecki
2003-06-20 18:09 ` john stultz
2003-06-20 15:02 ` Andreas Haumer
2003-06-20 23:28 ` Andy Pfiffer
2003-06-20 23:31 ` john stultz
2003-06-21 0:07 ` john stultz
2003-06-24 0:16 ` 2.5.7[23]: " Andy Pfiffer
2003-06-24 0:37 ` john stultz [this message]
2003-06-24 16:09 ` Andy Pfiffer
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=1056415040.1028.82.camel@w-jstultz2.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=andreas@xss.co.at \
--cc=andyp@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®