From: Helge Hafting <helge.hafting@hist.no>
To: Yaroslav Halchenko <yoh@psychology.rutgers.edu>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: alienware hardware - memory problem?
Date: Fri, 25 Jun 2004 10:54:43 +0200 [thread overview]
Message-ID: <40DBE853.4050707@hist.no> (raw)
In-Reply-To: <20040625000102.GI728@washoe.rutgers.edu>
Yaroslav Halchenko wrote:
>because slow down seems to be linked to memory: brk(0) takes on average
>0.5-1.5 second, I've decided to run silly memtest...
>I have around 1GB total on that beast, I turned off swap and did memtest
>1G
>
>
Memory. Could it be the good old MTRR problem?
Try "cat /proc/mtrr" and check that _all_ ordinary memory
is covered by a write-back mtrr.
Having most of the memory covered lacking a little at the top only
is not good enough - you'll see a major slowdown as linux tend to
use the topmost memory most and that will be very slow without
a MTRR.
If it indeed is a mtrr problem, confirm it by booting with mem=<low number>
and see that the machine is faster when not using the "slow" memory.
After that, get a bios upgrade or echo something useable
into /proc/mtrr
Helge Hafting
next prev parent reply other threads:[~2004-06-25 8:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 19:10 alienware hardware Yaroslav Halchenko
[not found] ` <200406242315.56213.vda@port.imtp.ilyichevsk.odessa.ua>
2004-06-24 20:26 ` Yaroslav Halchenko
[not found] ` <200406242358.55782.vda@port.imtp.ilyichevsk.odessa.ua>
2004-06-24 21:09 ` Yaroslav Halchenko
2004-06-24 21:26 ` Yaroslav Halchenko
2004-06-24 21:58 ` Yaroslav Halchenko
2004-06-25 0:01 ` alienware hardware - memory problem? Yaroslav Halchenko
2004-06-25 8:54 ` Helge Hafting [this message]
2004-06-25 16:20 ` Yaroslav Halchenko
2004-06-26 12:07 ` Helge Hafting
2004-06-26 15:45 ` Yaroslav Halchenko
2004-06-26 18:41 ` Helge Hafting
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=40DBE853.4050707@hist.no \
--to=helge.hafting@hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=yoh@psychology.rutgers.edu \
/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.