public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marvin Justice <mjustice@austin.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Serverworks LE, 4GB RAM, and MTRR
Date: Mon, 30 Jul 2001 18:37:02 -0500	[thread overview]
Message-ID: <01073018370207.04012@bozo> (raw)

Slow performance on Serverworks LE boards with 4GB of RAM seem to be related 
to mtrr misconfiguration. Here is the /proc/mtrr for a Tyan 2510 ( 2.4.7-ac2):

reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg02: base=0xc0000000 (3072MB), size= 512MB: write-back, count=1
reg03: base=0xe0000000 (3584MB), size= 256MB: write-back, count=1
reg04: base=0xf0000000 (3840MB), size= 128MB: write-back, count=1
reg05: base=0xf8000000 (3968MB), size=  64MB: write-back, count=1
reg06: base=0xfc000000 (4032MB), size=  64MB: uncachable, count=1

Also, the framebuffer is 4MB starting at 0xfd000000 (4048MB) on this system.
The last entry seems to be the culprit. Why should there be 64MB uncachable
starting at 4032?

Back in April there was a thread concering the mtrr setup for the LE chipset.
A patch for mtrr.c was submitted (but never accepted, apparently) that allows 
write-combining (which is currently disabled for all Serverworks LE) for 
revisions >5.  If I modify mtrr.c to allow write-combining the system works 
normally with 4G. /proc/mtrr is unchanged but the following line shows up in 
the syslog when the X-server is started:

mtrr: type mismatch for fd000000,400000 old: uncachable new: write-combining

The slowness of the system without write-combining is independent of whether 
X is started.

Marvin Justice

             reply	other threads:[~2001-07-30 23:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 23:37 Marvin Justice [this message]
2001-07-31 17:29 ` Serverworks LE, 4GB RAM, and MTRR Marvin Justice

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=01073018370207.04012@bozo \
    --to=mjustice@austin.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    /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