From: Andreas Haumer <andreas@xss.co.at>
To: Andreas Haumer <andreas@xss.co.at>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: system clock speed too high?
Date: Tue, 03 Jun 2003 14:39:06 +0200 [thread overview]
Message-ID: <3EDC96EA.5020906@xss.co.at> (raw)
In-Reply-To: <3EDC8DC0.7090009@xss.co.at>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
Andreas Haumer wrote:
[...]
> *) Hyperthreading "disabled"
> *) MPS 1.4 Support "disabled"
> *) BIOS Update "disabled"
> *) Plug & Play "yes" (this makes it even worse: linux crashes
> eventually as it gets confused by IRQ setting)
>
I've found it:
It's BIOS setting "USB legacy support", which I had on
"Auto" (default setting).
As soon as I disable "USB legacy support", system time
is now in sync with wall clock time!
root@setup:~ {508} $ ntpdate ntp.xss.co.at; sleep 60; ntpdate ntp.xss.co.at
3 Jun 14:35:32 ntpdate[1141]: adjust time server 194.152.162.17 offset 0.005909 sec
3 Jun 14:36:32 ntpdate[1146]: adjust time server 194.152.162.17 offset -0.002158 sec
Uaaahhhhhhhh!!!!!
Linux also now reports an interesting error on bootup, which
isn't there when booting with "USB legacy support=Auto"
[...]
..MP-BIOS bug: 8254 timer not connected to IO-APIC
[...]
(This is 2.4.21-rc6-ac1 booting with "acpi=off")
What the hell does USB legacy support have to do with all this???
This is weird!
- - 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+3JbkxJmyeGcXPhERAmzLAJ48RMa7o6Zn0Ko6YxFn4y5UVeGl+wCgwQwN
DSjZtxe4QDEL8I812fz2h1U=
=8zBV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-06-03 12:25 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 [this message]
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
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=3EDC96EA.5020906@xss.co.at \
--to=andreas@xss.co.at \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.