Mohd Irwan Jamaluddin wrote: > On 7/8/07, Christian Pazmiño <[EMAIL PROTECTED]> wrote: >> Friends, >> >> our server has 4GB physical memory but RHEL 5 only detects 3GB, we >> have been >> looking for a solution but nothing actually has worked, also where is >> hugemem kernel?? Please help. >> Here some output info. >> > > Do you enable Kdump? I afraid you've been spending 1GB of RAM for Kdump.
This one sounds like a BIOS issue and you'd have to be crazy to have assigned 1GB of RAM to kdump :), but that's worth double-checking. grep crashkernel /proc/cmdline - and - grep "Crash kernel" /proc/iomem ...should give you an idea of how much memory is being used by kdump[1]. If its not turned on, the first should return nothing, the second should return[2]: 00000000-00000000 : Crash kernel And let it be noted that for x86_64, you should be fine with only 128MB for the default kdump setup, even less for advanced setups (which dump the core from the kdump initrd, rather than in user-space, so less memory required). [1] The cmdline check may not return anything if you're running a xen kernel that supports kdump, but that feature doesn't exist in the rhel5.0 xen kernels [2] Except on ppc64, which doesn't seem to list the crashkernel region in /proc/iomem for some reason. -- Jarod Wilson [EMAIL PROTECTED]
signature.asc
Description: OpenPGP digital signature
_______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list
