From: Andy Pfiffer <andyp@osdl.org>
To: john stultz <johnstul@us.ibm.com>
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: 24 Jun 2003 09:09:03 -0700 [thread overview]
Message-ID: <1056470943.1209.38.camel@andyp.pdx.osdl.net> (raw)
In-Reply-To: <1056415040.1028.82.camel@w-jstultz2.beaverton.ibm.com>
On Mon, 2003-06-23 at 17:37, john stultz wrote:
> 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.
Yeah, I saw that. Same time in my inbox, too. ;^)
> 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?
It says on the front of the case "IBM eserver", but the "e" sort of
looks like an "@". Also printed on the front of the case is "x220."
I have no idea if there is a service processor installed in the box.
Here is the output of lspci:
00:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06)
00:00.1 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06)
00:01.0 VGA compatible controller: S3 Inc. Savage 4 (rev 04)
00:09.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
(rev 08)
00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 50)
00:0f.1 IDE interface: ServerWorks OSB4 IDE Controller
00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev
04)
01:03.0 SCSI storage controller: Adaptec AIC-7892P U160/m (rev 02)
There is a 2nd Intel e100 interface on the motherboard ("planar" in
IBM-speak), but that has been set to "disabled" in the BIOS for some
reason. Re-enabling it has no effect on the time skew, nor does the USB
legacy support that worked for someone else on a different system.
Strange, huh?
prev parent reply other threads:[~2003-06-24 15:55 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
2003-06-24 16:09 ` Andy Pfiffer [this message]
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=1056470943.1209.38.camel@andyp.pdx.osdl.net \
--to=andyp@osdl.org \
--cc=andreas@xss.co.at \
--cc=johnstul@us.ibm.com \
--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®