mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Eugene Chupkin <ace@credit.com>
Cc: linux-kernel@vger.kernel.org, tmeagher@credit.com
Subject: Re: 2.4.x ram issues?
Date: Thu, 14 Feb 2002 20:13:58 +0100	[thread overview]
Message-ID: <20020214191356.GB160@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.10.10202121726530.683-100000@mail.credit.com>
In-Reply-To: <Pine.LNX.4.10.10202121726530.683-100000@mail.credit.com>

Hi!

> I have a problem with high ram support on 2.4.7 to 2.4.17 all behave the
> same. I have a quad Xeon 700 box with 16gb of ram on an Intel SKA4 board.
> The ram is all the same 16 1gb PC100 SDRAM modules from Crucial. If I
> compile the kernel with high ram (64gb) support, my system runs very slow,
> it takes about 15 minutes for make menuconfig to come up. If I  recompile
> the kernel with 4gb support, it runs perfectly normal and very fast, but I
> have 12 gigs that I can't use. Is this a known issue? Is there a fix? I
> tried just about everything and I am all out of options. Please help!

What happens with 8GB?
									Pavel
-- 
(about SSSCA) "I don't say this lightly.  However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa

  parent reply	other threads:[~2002-02-14 20:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13  1:40 Eugene Chupkin
2002-02-13  2:00 ` Alan Cox
2002-02-13  2:52   ` Eugene Chupkin
2002-02-13  4:31   ` Andreas Dilger
2002-02-13 19:05     ` Eugene Chupkin
2002-02-13 19:21       ` Andreas Dilger
2002-02-13 20:33         ` Eugene Chupkin
2002-02-13 22:29           ` Mike Fedyk
2002-02-21 23:09           ` Eugene Chupkin
2002-02-14 19:13 ` Pavel Machek [this message]
2002-02-14 20:54   ` Eugene Chupkin

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=20020214191356.GB160@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=ace@credit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmeagher@credit.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

all inboxes | Powered by JetHome®