From: William Lee Irwin III <wli@holomorphy.com>
To: Jan Panteltje <panteltje@yahoo.com>
Cc: linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: 2.6.9 slows down everything
Date: Mon, 6 Dec 2004 12:01:19 -0800 [thread overview]
Message-ID: <20041206200119.GR2714@holomorphy.com> (raw)
In-Reply-To: <41B463BA.5080008@yahoo.com>
On Mon, Dec 06, 2004 at 02:50:50PM +0100, Jan Panteltje wrote:
> Slow slow slow, compile takes looooong time..../
> even with all modules removed.
> Even the mouse becomes sluggy
> top shops no excessive CPU usage.
> I am back to 2.4.25,
I've heard of several MTRR issues with 2.6.x, of which this is likely
an instance.
The pattern seemed to involve attempts to cover the final portion of
RAM with numerous fragments decreasing in size with ascending
physical address, and failure to cover the final 4-8MB RAM. Odder
still, the affected systems seemed to only have 1GB RAM, and for some
reason 2.4.x was not affected.
I've walked about 3 or 4 users through manually correcting the MTRR
settings over the past 2 weeks.
-- wli
prev parent reply other threads:[~2004-12-06 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 13:50 2.6.9 slows down everything Jan Panteltje
2004-12-06 14:00 ` Bartlomiej Zolnierkiewicz
2004-12-06 20:01 ` William Lee Irwin III [this message]
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=20041206200119.GR2714@holomorphy.com \
--to=wli@holomorphy.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=panteltje@yahoo.com \
/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