From: Andreas Haumer <andreas@xss.co.at>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: system clock speed too high?
Date: Tue, 03 Jun 2003 16:23:29 +0200 [thread overview]
Message-ID: <3EDCAF61.3060202@xss.co.at> (raw)
In-Reply-To: <1054645247.9359.12.camel@dhcp22.swansea.linux.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
Alan Cox wrote:
> USB legacy generates SMI events. It could be that something
> the BIOS SMI magic is doing is disrupting the system clock
> or causing extra interrupts
>
Thanks for your support.
The "USB legacy support" settings slipped through when
I was preparing the system. I was too much concentrated
on the ACPI/Fusion MPT problems...
But something must be wrong in this area, as the kernel prints
this "..MP-BIOS bug: 8254 timer not connected to IO-APIC"
message when USB legacy support is disabled.
Anyway, I'll have this system available for tests in the
next few days (it is to be installed as production server
next week), and it _will_ suffer a lot from the stress tests
I've planned... ;-)
So if you want me to test anything (ACPI patches, perhaps?)
you're very welcome!
- - 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+3K9fxJmyeGcXPhERAsqfAJkBJS/W5DxjPLYh2f7795j9Xx2pDACfcFXG
rAKbPhQrxpGnAW3xFv1G3u4=
=J0bc
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-06-03 14:10 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 [this message]
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=3EDCAF61.3060202@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox