Bug 57164 - kernel 2.4.9 doesn't boot with mem=1024M
kernel 2.4.9 doesn't boot with mem=1024M
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.1
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-12-06 04:16 EST by Willi N|_er
Modified: 2007-03-26 23:50 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-03-13 08:54:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
The corresponding oops (12.31 KB, text/plain)
2001-12-06 04:26 EST, Nils Philippsen
no flags Details

  None (edit)
Description Willi N|_er 2001-12-06 04:16:49 EST
Description of Problem:
on our DELL server, 4 way, 4 GB RAM, kernel 2.4.9 does not boot with
mem=1024 M. mem=896 M works.

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

How Reproducible:
always

Steps to Reproduce:
1. boot ;-)

 

Actual Results:
oops

Expected Results:
it should boot ....

Additional Information:
worked with kernel 2.4.9-6enterprise
Comment 1 Nils Philippsen 2001-12-06 04:26:43 EST
Created attachment 39847 [details]
The corresponding oops
Comment 2 Arjan van de Ven 2001-12-06 04:43:53 EST
Megaraid 1.18 has 1 known highmem bug; the "896M works 1024M doesn't" sort of
points in that direction. Does SAP have access to the beta site so I can send a
kernel with that bug fixed ?
Comment 3 Nils Philippsen 2001-12-06 06:50:20 EST
NB: It worked flawlessly without any mem= option (using the full 4GB).
Comment 4 Nils Philippsen 2002-03-13 08:54:35 EST
Apparently is fixed in current kernels, please close.

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