public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Haumer <andreas@xss.co.at>
To: george anzinger <george@mvista.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: system clock speed too high?
Date: Tue, 03 Jun 2003 12:04:35 +0200	[thread overview]
Message-ID: <3EDC72B3.9040109@xss.co.at> (raw)
In-Reply-To: <3EDBB4B0.6070601@mvista.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

george anzinger wrote:
> Andreas Haumer wrote:
>
[...]
>> I have a quite strange phenomenon here: I see a ~2.5 times
>> speed up of system time on a Asus AP1700-S5 server with
>> Linux-2.4.21-rc6-ac1.
>> Simple proof: a "sleep 300" command terminates after exactly
>> 120 seconds of wall clock time.
>
>
> Just as a wild shot in the dark, what speed does the kernel think the
> cpu is running at and does this match what the BIOS thinks?
>
> It sounds like the CLOCK_TICK_RATE is wrong.  This would show up as the
> kernel thinking the cpu was fast also.
>
Hm, I don't think this is the case.
BIOS reports (correctly) a single, hyperthreaded Xeon CPU
with 2.4GHz

Kernel reports the same:
root@setup:~ {503} $ uname -a
Linux setup 2.4.21-rc6-ac1 #2 SMP Tue Jun 3 09:45:13 CEST 2003 i686 unknown

root@setup:~ {504} $ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Xeon(TM) CPU 2.40GHz
stepping        : 7
cpu MHz         : 2392.065
cache size      : 512 KB
physical id     : 0
siblings        : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips        : 4771.02

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Xeon(TM) CPU 2.40GHz
stepping        : 7
cpu MHz         : 2392.065
cache size      : 512 KB
physical id     : 0
siblings        : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips        : 4771.02

root@setup:~ {505} $ ntpdate ntp.xss.co.at; sleep 500; ntpdate ntp.xss.co.at
 3 Jun 11:58:16 ntpdate[1118]: step time server 194.152.162.17 offset -177.268071 sec
 3 Jun 12:01:36 ntpdate[1120]: step time server 194.152.162.17 offset -300.106769 sec

(Sleeping 500 "system seconds" takes 200 "wall clock seconds")

> You pin this to a particular kernel version.  Do other kernel versions
> do a better job?
>
So far I tried with:

2.4.21-rc2-ac2 (ACPI compiled as module)
2.4.21-rc4 (ACPI compiled as module)
2.4.21-rc6-ac1 (ACPI compiled as module)
2.4.21-rc6-ac1 (no ACPI comiled at all)

Time acceleration is the same for all kernels.

I'll try it with some older kernels, too.

- - andreas

- --
Andreas Haumer                     | mailto:andreas@xss.co.at
*x Software + Systeme              | http://www.xss.co.at/
Karmarschgasse 51/2/20             | Tel: +43-1-6060114-0
A-1100 Vienna, Austria             | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+3HKxxJmyeGcXPhERAkZ/AJ9tjgI6K2HtM/tL15nKDFIKzdcvQgCfYOGY
i96/o6Nyxlem5yOp1A2Q//s=
=plFh
-----END PGP SIGNATURE-----


  reply	other threads:[~2003-06-03  9:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02 19:40 system clock speed too high? Andreas Haumer
2003-06-02 19:36 ` Alan Cox
2003-06-03  9:54   ` Andreas Haumer
2003-06-03 12:00     ` Andreas Haumer
2003-06-03 12:17       ` Zephaniah E. Hull
2003-06-03 12:39       ` Andreas Haumer
2003-06-03 13:00         ` Alan Cox
2003-06-03 14:23           ` Andreas Haumer
2003-06-03 14:49             ` Martin Schlemmer
2003-06-03 15:31               ` Andreas Haumer
2003-06-04  5:44                 ` Martin Schlemmer
2003-06-04  8:49                   ` Andreas Haumer
2003-06-03 15:17     ` venom
2003-06-03 15:38       ` Andreas Haumer
2003-06-03 15:43         ` venom
2003-06-03 15:47           ` Randy.Dunlap
2003-06-03 16:12             ` venom
2003-06-02 20:33 ` george anzinger
2003-06-03 10:04   ` Andreas Haumer [this message]
2003-06-03 19:12     ` system clock speed too high? hyperthread problem? george anzinger
2003-06-04  9:47 ` system clock speed too high? Herbert Xu
2003-06-04 13:02   ` Herbert Xu

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=3EDC72B3.9040109@xss.co.at \
    --to=andreas@xss.co.at \
    --cc=george@mvista.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