From: "Randy.Dunlap" <rddunlap@osdl.org>
To: venom@sns.it
Cc: andreas@xss.co.at, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: system clock speed too high?
Date: Tue, 3 Jun 2003 08:47:37 -0700 [thread overview]
Message-ID: <20030603084737.33a5f817.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.43.0306031742530.24604-100000@cibs9.sns.it>
Hi,
Did you check to see if USB is enabled in your BIOS setup?
Nothing to do with Linux USB kernel support....
~Randy
On Tue, 3 Jun 2003 17:43:42 +0200 (CEST) venom@sns.it wrote:
|
| No, I do not have USB enabled at all.
| anyway I see exactly the same results, also if the problem could be somewhere
| else.
|
| Luigi
|
| On Tue, 3 Jun 2003, Andreas Haumer wrote:
|
| > Date: Tue, 03 Jun 2003 17:38:09 +0200
| > From: Andreas Haumer <andreas@xss.co.at>
| > To: venom@sns.it
| > Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
| > Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
| > Subject: Re: system clock speed too high?
| >
| > -----BEGIN PGP SIGNED MESSAGE-----
| > Hash: SHA1
| >
| > Hi!
| >
| > venom@sns.it wrote:
| > > I reported this same problem for kernel 2.5.69/70 on pentiumIII with chipset
| > > i810, but it seems the reports has been unnoticed.
| > >
| > > I replicated your tests with 2.5.70 without acpi, same results here.
| > >
| > Hm, do you have "USB legacy support" enabled on your
| > system, too? Does the problem go away if you disable it?
| >
| > What motherboard and BIOS does your computer have (manufacturer,
| > version numbers)?
| >
| > (This is a totally different chipset, so the problems
| > might be completely unrelated)
| >
| > - - 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
next prev parent reply other threads:[~2003-06-03 15:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 19:40 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 [this message]
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=20030603084737.33a5f817.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andreas@xss.co.at \
--cc=linux-kernel@vger.kernel.org \
--cc=venom@sns.it \
/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®