From: "John L. Males" <software_iq@TheOffice.net>
To: linux-kernel@vger.kernel.org
Subject: Linux Kernel 2.2.19 Available Memory Bug
Date: Fri, 20 Jul 2001 03:47:43 -0500 [thread overview]
Message-ID: <3B57A9DF.10547.A92B31@localhost> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
Please note I am not on the Kernel Mailing List so do try to copy me
in with any reply, questions, clarifications, confirmations, et al on
this bug report.
Before I forget I am using SuSE 6.4 with most of the updates from the
base applied, most meaning I generally lag a bit behind at times. I
am NOT using the SuSE kernel due to bugs introduced into the SuSE
kernel with the SuSE patches/enhancements. I am using the Linus
2.2.19 Kernel with the OpenWall patches. System is AMD K6-2 500
based system. The version of gcc was 2.95.2 to compile the kernel.
The bug I am reporting is that when one sets the amount of memory,
i.e. 128M, 256M; at the time of booting the 2.2.19 kernel the "Total
Memory" as reported by KDE, "free", etc is short by a important
amount. To be more specific I will detail the results of "free"
below against the "mem" value passed to the kernel. Please note for
the purposes of this test I always had 256MB or ram (2x128MB)
installed in my system. The BIOS reports total system memory as
262144K.
"mem=256m"
***************
KDE reports 251.09 Total System memory, or 263290880 bytes.
"free -m" indicates "Total Memory" as 251
"free -k" indicates "Total Memory" as 257120
"free -k" indicates "Total Memory" as 263290880
The exact same vaules as noted above are indicated for "mem=262144k",
and "mem=268435546" (256 X 1024 x 1024).
"mem=128m"
***************
"free -m" indicates "Total Memory" as 124
"free -k" indicates "Total Memory" as 127344
"free -k" indicates "Total Memory" as 130400256
Regards,
John L. Males
Software I.Q. Consulting
Toronto, Ontario
Canada
20 July 2001 03:47
mailto:software_iq@TheOffice.net
mailto:jlmales@softhome.net
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use
<http://www.pgp.com>
iQA/AwUBO1fwKPLzhJbmoDZ+EQKQowCfcqeGPdpduaFpTQO1P9XaOlJccHEAn20p
v0V59vV7rrFEvMQCLwzXyO2V
=Ezn3
-----END PGP SIGNATURE-----
next reply other threads:[~2001-07-20 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-20 8:47 John L. Males [this message]
2001-07-20 13:56 ` Linux Kernel 2.2.19 Available Memory Bug Doug McNaught
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=3B57A9DF.10547.A92B31@localhost \
--to=software_iq@theoffice.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.