From: Michael.W.Salo@valley.net (Michael W. Salo)
To: marco.roeland@xs4all.nl (Marco Roeland),
matt@denner.demon.co.uk (Matthew Denner)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 45 minute boot time with 2.6.4/2.6.6-mm5 kernel on 1.7GHz laptop
Date: 15 Jun 2004 11:09:25 EDT [thread overview]
Message-ID: <43332297@enfield.VALLEY.NET> (raw)
I recently had a similar experience installing fedora on a dell laptop.
In the interest of starting "fresh" I flashed the BIOS with the latest,
installed fedora, and the laptop was dog slow
I didn't realize that by flashing the BIOS, the BIOS processor setting was
changed to "compatibility" mode,
I had to manually change to "optimum" and all was well.
just something else to check if your BIOS offers this setting...
-mike salo
--- Marco Roeland wrote:
On Tuesday June 15th 2004 Matthew Denner wrote:
> [extremely slowly functioning laptop]
>
> Output from 'cat /proc/interrupts':
> CPU0
> ...
> 20: 270154 IO-APIC-level eth0
This seems perhaps quite high? On occasion I have to use a configuration
where the network interface is configured by DHCP. When I take the
interface down (ifdown eth0) but forget to assign it its usual network
address (when changing location to another network) some interaction
with the still running DHCP client (pump) makes my laptop crawl just like
you describe. So if all other suggested options fail, you might want to
check if you maybe have such a runaway DHCP client causing havoc.
--
Marco Roeland
--- end of quote ---
next reply other threads:[~2004-06-15 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 15:09 Michael W. Salo [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-15 13:41 45 minute boot time with 2.6.4/2.6.6-mm5 kernel on 1.7GHz laptop Matthew Denner
2004-06-15 13:53 ` Mikael Pettersson
2004-06-15 18:45 ` Matthew Denner
2004-06-15 22:06 ` Mikael Pettersson
2004-06-16 9:06 ` Matthew Denner
2004-06-15 14:29 ` Marco Roeland
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=43332297@enfield.VALLEY.NET \
--to=michael.w.salo@valley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.roeland@xs4all.nl \
--cc=matt@denner.demon.co.uk \
/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