Bug 11464 - kernel compiled for 2GB RAM won't run executables over 400Mb
kernel compiled for 2GB RAM won't run executables over 400Mb
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jakub Jelinek
Depends On:
Blocks: 11928
  Show dependency treegraph
Reported: 2000-05-17 06:00 EDT by wpk20
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-08-08 17:33:11 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 wpk20 2000-05-17 06:00:56 EDT
default kernel for machine uses 1Gb system RAM. this kernel will happily
run executables up to around 1Gb size, as you might expect. these
executables are from fortran77 source, on f77 compiler or pgf77 compiler.

however with a kernel compiled for 2Gb RAM in xconfig, linux runs OK and
recognises that it has 2GB system RAM but will only run executables of up
to around 400Mb. this isn't a fortran problem, all programs have the same
error, and i've checked the code and debug reports with xxgdb.
Comment 1 Doug Ledford 2000-05-22 14:43:59 EDT
Please update to the latest kernel release.  The 400MB application size limit is
partly due to library mapping locations and other similar fixed address
allocations.  The latest Red Hat kernels include the 4GB BIGMEM patch so that
they can access 4GB of RAM *and* still provide a 3-1 split of virtual address to
kernel mapped memory space.  This should solve your problem.  The issue you are
reporting isn't actually a bug, it's a side effect of the 2-2 split option in
the kernel.
Comment 2 wpk20 2000-06-23 09:25:15 EDT
bigmem patch in 2.2.12-5.0 seems to not solve this problem. compiles & boots OK, 
same memory error.
Comment 3 wpk20 2000-07-17 06:40:26 EDT
bigmem patch in 2.2.14-12 still not solving problem.  machine memory recognised
OK, memory split only slightly improved (can now run up to about 600Mb).
Comment 4 Alan Cox 2000-08-08 17:32:36 EDT
C library issue
Comment 5 wpk20 2000-08-09 04:38:00 EDT
in kernel 2.4.0-test4, with HIGHMEM support enabled, the problem solved by
adjusting the TASK_UNMAPPED_BASE definition line in processor.h. normally
defined as 'TASK_SIZE/3', i set to 'TASK_SIZE/1.5'. i would expect HIGHMEM patch
to do this anyway though, patch doesn't solve problem without this fix. (fix
discussed with ingo molnar mingo@redhat.com).

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