From: "Marvin Justice" <mjustice@austin.rr.com>
To: "'Matthias Schniedermeyer'" <ms@citd.de>,
"'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Strange Slowdown
Date: Sun, 19 Aug 2001 14:53:46 -0500 [thread overview]
Message-ID: <000001c128e8$a8f31070$36481c18@ujx7u> (raw)
In-Reply-To: <20010818182300.A15860@citd.de>
> > > After i switched "High Memory-Support" to "OFF"(4GB
> Before) the speed went
> > > to normal, but now less than half RAM is used.
> > > Any suggestions?
> >
> > This sounds like the top of memory is running uncached due
> to wrong mtrr
> > settings from the BIOS. Can you post your /proc/mtrr
>
> Because of other reasons i'm back to 2.2.19
>
> /proc/mtrr from 2.2.19 show this
> -- /proc/mtrr --
> reg00: base=0x00000000 ( 0MB), size=1024MB: write-back, count=1
> reg01: base=0x40000000 (1024MB), size= 512MB: write-back, count=1
> reg02: base=0x60000000 (1536MB), size= 256MB: write-back, count=1
> reg03: base=0x70000000 (1792MB), size= 128MB: write-back, count=1
> reg04: base=0x78000000 (1920MB), size= 64MB: write-back, count=1
> reg05: base=0x7c000000 (1984MB), size= 32MB: write-back, count=1
> -- end --
> (32MB "missing". Seems like Linux uses these "missing" MBs.)
>
> For the 2.4.X-Kernel i had switched off the MTRR-Kernel-Option!
>
> Maybe i should try it another time with MTRR-Support switched on.
> Or i should use "mem=2016M".
>
I had a similar problem which could be solved by either passing the "mem="
option at boot time as you suggest(in which case you permanently lose the
upper 32MB) or by using the /proc/mtrr interface ( as described in
Documentation/mtrr.txt) to assign the "missing" region. For your system you
might try something like:
echo "base=0x7e000000 size=0x2000000 type=write-back" >| /proc/mtrr
Marvin Justice
prev parent reply other threads:[~2001-08-19 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-18 10:02 Matthias Schniedermeyer
2001-08-18 12:57 ` Alan Cox
2001-08-18 16:23 ` Matthias Schniedermeyer
2001-08-19 19:53 ` Marvin Justice [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='000001c128e8$a8f31070$36481c18@ujx7u' \
--to=mjustice@austin.rr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@citd.de \
/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®