Bug 173950 - The SMP and Hugemem descriptions are wrong.
Summary: The SMP and Hugemem descriptions are wrong.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rhel-sag
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike Behm
QA Contact: John Ha
URL: http://www.redhat.com/docs/manuals/en...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-11-22 21:43 UTC by Johnray Fuller
Modified: 2014-08-04 22:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-11-22 23:14:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Johnray Fuller 2005-11-22 21:43:48 UTC
Description of problem:

Description of problem:

At this URL the kernel-hugemem and kernel-smp statements are confusing:

http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/ch-kernel.html

For kernel-hugemem, it states:

"kernel-hugemem â (only for i686 systems) In addition to the options enabled for
the kernel package. The key configuration options are as follows:

    *      Support for more than 4 GB of RAM (up to 16 GB for x86)"

The first bullet point needs to read:

"Support for more than 4 GB of RAM (up to 64 GB for x86)"

It would be useful to put a footnote stating:

"Note, kernel-hugemem is required for memory configurations higher than 16 GB."

**********


For kernel-smp, it states:

"kernel-smp â contains the kernel for multi-processor systems. The following are
the key features:

    *      Multi-processor support
    *      Support for more than 4 GB of RAM (up to 64 GB for x86)"

This is in fact, not true. Red Hat will not support greater the 16G of RAM. The
second bullet point needs to read:

"Support for more than 4 GB of RAM (up to 16 GB for x86)"

Comment 1 John Ha 2005-11-22 23:14:41 UTC
Thanks for the report. Upon further discussion outside of this bugzilla report,
we will rebuild the manual with these fixes included as soon as possible. Thanks
again for your report!

Cheers,
John


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