From: Jeff Golds <jgolds@resilience.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.4 kernel reports wrong amount of physical memory
Date: Mon, 14 May 2001 12:09:21 -0700 [thread overview]
Message-ID: <3B002D61.191C03C@resilience.com> (raw)
Hi folks,
I installed the 2.4.4 kernel on a dual P3-733 system with 1 GB of ECC RAM and found that /proc/meminfo reports back only 899MB of RAM. The 2.4.2 kernel (with RedHat patches from the 7.1 release) worked fine as did the 2.4.0 kernel (with RedHat patches from the 7.0 release).
Anyone know what is going on with 2.4.4? At POST, the BIOS reports 1024MB.
-Jeff
--
Jeff Golds
jgolds@resilience.com
next reply other threads:[~2001-05-14 19:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 19:09 Jeff Golds [this message]
2001-05-14 19:29 ` 2.4.4 kernel reports wrong amount of physical memory Alan Cox
2001-05-14 20:01 ` Rik van Riel
2001-05-14 22:50 ` Wayne Whitney
2001-05-14 23:25 ` Rik van Riel
2001-05-14 23:39 ` Jeff Golds
2001-05-14 23:41 ` Jeff Golds
2001-05-15 0:44 ` Rik van Riel
2001-05-15 1:00 ` Mohammad A. Haque
2001-05-15 1:07 ` Jeff Golds
2001-05-15 2:32 ` Rik van Riel
2001-05-15 4:19 ` [PATCH] " Wayne Whitney
2001-05-15 0:25 ` H. Peter Anvin
2001-05-15 1:57 ` Brian Gerst
2001-05-15 1:46 ` H. Peter Anvin
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=3B002D61.191C03C@resilience.com \
--to=jgolds@resilience.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;
as well as URLs for NNTP newsgroup(s).