From: Dan Kegel <dank@kegel.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 1.5 GB ram on system - only 900 MB shows
Date: Mon, 03 Sep 2001 10:42:28 -0700 [thread overview]
Message-ID: <3B93C104.AE8909C4@kegel.com> (raw)
In-Reply-To: <ffd4cdd8.0108271353.75476210@posting.google.com> <slrn9olo4b.u89.BigLar@leonardo.localdomain> <ffd4cdd8.0108281415.16a63a2d@posting.google.com>
natestone@hotmail.com (Nate Stone) wrote:
> > > We were able to address 1024 MB of ram on our previous machine using
> > > the append feature during boot up, but it doesn't seem to work any
> > > more. Is this a problem related to the new memory management system
> > > in kernel 2.4.xx? Any solutions?
> >
> > I think you must recompile your kernel with >1GB support. ...
>
> Actually, we already built the kernel with 4GB support enabled and the
> ram was still not recognized. We get the same exact problem.
>
> ... try running
> 40+million pageviews per month off a crippled server because you can't
> access all the ram and the shared memory utilization sucks in kernel
> 2.4.xx. Talk about nightmares.
>
> We probably will switch back to kernel 2.2.16 (which worked with 1GB
> of ram) and seemed way more efficient at memory management unless
> someone offers an alternative.
Going back to 2.2.x is probably a good idea for the moment, but
it's a bit suprising that the RAM isn't showing up in 2.4.
Is it possible you didn't boot with the kernel you thought you did?
I'm cc'ing this to linux-kernel, as this isn't really redhat specific,
and the people there may have suggestions for you.
- Dan
--
"I have seen the future, and it licks itself clean." -- Bucky Katt
parent reply other threads:[~2001-09-03 17:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ffd4cdd8.0108281415.16a63a2d@posting.google.com>]
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=3B93C104.AE8909C4@kegel.com \
--to=dank@kegel.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