Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 125128 - kcontrole shows wrong memory info >4GB
kcontrole shows wrong memory info >4GB
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kdebase (Show other bugs)
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2004-06-02 17:38 EDT by Gary Lerhaupt
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-12 13:38:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gary Lerhaupt 2004-06-02 17:38:36 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; 
H010818; .NET CLR 1.0.3705)

Description of problem:
For systems with >4GB of memory, kcontrol (KDE graphical memory 
display) only shows 3.5GB of total memory.  Likewise, other memory 
amounts are also wrong.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install KDE on system with >4GB RAM
2. run kcontrol
3. click on memory tab and note memory info is wrong

Actual Results:  3.5 GB total memory

Expected Results:  16GB memory

Additional info:

Interestingly, it appears the maintainer of this project did try to 
account for large memory systems.  In kcontrol/info/memory.h, it 

typedef unsigned long long t_memsize;
typedef unsigned long t_memsize;

Either HAVE_LONG_LONG is not defined or perhaps later something else 
is not properly reading the memory from the syscall in 
Comment 1 John Feeney 2007-07-12 13:38:46 EDT
With RHEL3 now in maintenance mode, where only critical customer issues
can be fixed, this bugzilla has been closed as wont fix due to its severity
level and a lack of recent activity. 

Note You need to log in before you can comment on or make changes to this bug.