[rhn-users] grub does not honor mem=xxxMrequest
Benj FitzPatrick
benjfitz at uchicago.edu
Tue Jan 17 23:08:39 UTC 2006
I believe that x86_64 is the same no matter whether AMD or
Intel is used. AMD started x86_64 with its opteron and
athlon64 procs, and Intel added 64bit extensions to its xeons
and dubbed it EMT64. To the best of my knowledge there is no
distinction, and on the install CDs it has them listed for
either 32bit x86 or 64bit AMD64/EMT64.
Benj
---- Original message ----
>Date: Tue, 17 Jan 2006 11:26:23 -0600
>From: Alfred Hovdestad <alfred.hovdestad at usask.ca>
>Subject: Re: [rhn-users] grub does not honor mem=xxxMrequest
>To: Red Hat Network Users List <rhn-users at redhat.com>
>
>You have the Intel 64 bit version installed:
>
> > [benjfitz at haplo ~]$ rpm -q --qf "RPM:
> > %{NAME}-%{VERSION}-%{RELEASE} Arch:%{ARCH}\n" kernel
> > RPM: kernel-2.6.9-5.EL Arch:x86_64
>
>
>But you have AMD processors:
> > model name : Dual Core AMD Opteron(tm) Processor 275
>
>
> Alfred
>
>
>Benj FitzPatrick wrote:
>> Thanks for all of the replies everybody. I do have the 64bit
>> version installed, or so it seems.
>>
>> ----------------------------------------
>> [benjfitz at haplo ~]$ uname -a
>> Linux haplo.uchicago.edu 2.6.9-22.0.1.ELsmp #1 SMP Tue Oct 18
>> 18:39:02 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux
>>
>> -------------------------------------------
>> [benjfitz at haplo ~]$ cat /proc/cpuinfo
>> processor : 0
>> vendor_id : AuthenticAMD
>> cpu family : 15
>> model : 33
>> model name : Dual Core AMD Opteron(tm) Processor 275
>> stepping : 2
>> cpu MHz : 2205.044
>> cache size : 1024 KB
>> physical id : 0
>> siblings : 2
>> core id : 0
>> cpu cores : 2
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 1
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep
>> mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht
>> syscall nx mmxext lm 3dnowext 3dnow pni ts fid
>> bogomips : 4325.37
>> TLB size : 1088 4K pages
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 40 bits physical, 48 bits virtual
>> power management: ts fid vid ttp
>>
>> processor : 1
>> vendor_id : AuthenticAMD
>> cpu family : 15
>> model : 33
>> model name : Dual Core AMD Opteron(tm) Processor 275
>> stepping : 2
>> cpu MHz : 2205.044
>> cache size : 1024 KB
>> physical id : 0
>> siblings : 2
>> core id : 1
>> cpu cores : 2
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 1
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep
>> mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht
>> syscall nx mmxext lm 3dnowext 3dnow pni ts fid
>> bogomips : 4407.29
>> TLB size : 1088 4K pages
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 40 bits physical, 48 bits virtual
>> power management: ts fid vid ttp
>>
>> processor : 2
>> vendor_id : AuthenticAMD
>> cpu family : 15
>> model : 33
>> model name : Dual Core AMD Opteron(tm) Processor 275
>> stepping : 2
>> cpu MHz : 2205.044
>> cache size : 1024 KB
>> physical id : 1
>> siblings : 2
>> core id : 2
>> cpu cores : 2
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 1
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep
>> mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht
>> syscall nx mmxext lm 3dnowext 3dnow pni ts fid
>> bogomips : 4407.29
>> TLB size : 1088 4K pages
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 40 bits physical, 48 bits virtual
>> power management: ts fid vid ttp
>>
>> processor : 3
>> vendor_id : AuthenticAMD
>> cpu family : 15
>> model : 33
>> model name : Dual Core AMD Opteron(tm) Processor 275
>> stepping : 2
>> cpu MHz : 2205.044
>> cache size : 1024 KB
>> physical id : 1
>> siblings : 2
>> core id : 3
>> cpu cores : 2
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 1
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep
>> mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht
>> syscall nx mmxext lm 3dnowext 3dnow pni ts fid
>> bogomips : 4407.29
>> TLB size : 1088 4K pages
>> clflush size : 64
>> cache_alignment : 64
>> address sizes : 40 bits physical, 48 bits virtual
>> power management: ts fid vid ttp
>>
>> ------------------------------------------------
>> [benjfitz at haplo ~]$ rpm -q --qf "RPM:
>> %{NAME}-%{VERSION}-%{RELEASE} Arch:%{ARCH}\n" kernel
>> RPM: kernel-2.6.9-5.EL Arch:x86_64
>> ----------------------------------------------
>>
>> Back to the drawing board I suppose.
>> Benj
>>
>>
>>
>>
>> ---- Original message ----
>>
>>>Date: Tue, 17 Jan 2006 12:07:25 -0500
>>>From: "Lazarev, Roman" <Roman.Lazarev at FMR.COM>
>>>Subject: RE: [rhn-users] grub does not honor mem=xxxMrequest
>>>To: "Red Hat Network Users List" <rhn-users at redhat.com>
>>>
>>>What you might have bumped into something we dealt with. You
>>
>> installed a
>>
>>>32-bit version of RHEL4 onto AMD processor. Anaconda tried to
>>
>> be too
>>
>>>smart and detected your stone as Athlon, rather than Opteron
>>
>> and the
>>
>>>wrong kernel got installed, since Athlons don't support more
>>
>> than 4GB by
>>
>>>definition hence your situation. You can inspect what
>>
>> architecture your
>>
>>>kernel was compiled for using:
>>>
>>>rpm -q --qf "RPM: %{NAME}-%{VERSION}-%{RELEASE}
>>
>> Arch:%{ARCH}\n" kernel
>>
>>>(just if you didn't know `rpm --querytags`)
>>>
>>>Also look in `cat /proc/cpuinfo` - how was your stone detected?
>>>
>>>Then re-install kernel for 64-bit AMD proc and you should be
>>
>> all set.
>>
>>>Roman Lazarev
>>>Fidelity Investment Management Technology
>>>245 Summer Street V2E
>>>Boston, MA 02210
>>>(617) 563-1173
>>>
>>>
>>>-----Original Message-----
>>>From: rhn-users-bounces at redhat.com
>>
>> [mailto:rhn-users-bounces at redhat.com]
>>
>>>On Behalf Of Benj FitzPatrick
>>>Sent: Tuesday, January 17, 2006 11:53 AM
>>>To: Red Hat Network Users List
>>>Subject: Re: [rhn-users] grub does not honor mem=xxxMrequest
>>>
>>>
>>>I believe bigmem is the default for AMD64 SMP, just like NUMA
>>>is. Also, as I said, I have 4 other computers which work just
>>>fine with 4+ GB, so it is something with the memory remapping
>>>on this mobo and the kernel.
>>>
>>>---- Original message ----
>>>
>>>>Date: Tue, 17 Jan 2006 05:27:01 -0800
>>>>From: "Brian T. Brunner" <brian.t.brunner at gai-tronics.com>
>>>>Subject: Re: [rhn-users] grub does not honor mem=xxxMrequest
>>>>To: <rhn-users at redhat.com>
>>>>
>>>>
>>>>IIRC the 3GB limit is there unless you're using a
>>>
>>>BIGMEM-enabled kernel.
>>>
>>>>More than 3GB may be seen by various places but won't be used
>>>
>>>by the kernel.
>>>
>>>>Brian Brunner
>>>>brian.t.brunner at gai-tronics.com
>>>>(610)796-5838
>>>>
>>>>
>>>>>>>benjfitz at uchicago.edu 01/16/06 06:10PM >>>
>>>>
>>>>Okies, perhaps I should give a little more info. I have 4
>>>>other computers running RHEL 4. 1 with 8GB and 3 with 4GB,
>>>>and none of these has this problem. I looked at cat
>>>>/proc/meminfo and it is seeing the same amount of RAM that
>>>>grub is. Any ideas?
>>>>
>>>>---- Original message ----
>>>>
>>>>>Date: Sat, 14 Jan 2006 08:12:01 -0500
>>>>>From: jludwig <wralphie at comcast.net>
>>>>>Subject: Re: [rhn-users] grub does not honor mem=xxxM
request
>>>>>To: Red Hat Network Users List <rhn-users at redhat.com>
>>>>>
>>>>>On Thursday 12 January 2006 17:14, Benj FitzPatrick wrote:
>>>>>
>>>>>>I have a dual opteron 275 box (iwill dk8x and 8x512MB of
>>>>>>reg/ecc pc3200) with RHEL 4 AS installed. I have the latest
>>>>>>kernel (2.6.9-22.0.1.ELsmp. It shows 3.09GB of RAM in
>>
>> top. I
>>
>>>>>>have changed the software and hardware memory remap
functions
>>>>>>in the BIOS and software on/hardware off gives 4096MB of
>>
>> NVRAM
>>
>>>>>>during POST. However, top still shows 3.09GB (with and
>>>>>>without mem=4096M in the boot line). Am I using this option
>>>>>>incorrectly or is there something else I can do?
>>>>>>
>>>>>>_______________________________________________
>>>>>>rhn-users mailing list
>>>>>>rhn-users at redhat.com
>>>>>>https://www.redhat.com/mailman/listinfo/rhn-users
>>>>>
>>>>>Apologies wrong icon -- mad mouse loose --
>>>>>Had to check, but, /proc/meminfo should tell what the kernel
>>>>
>>>>is actually
>>>>
>>>>>seeing.
>>>>>
>>>>>I did not look at top but suspect it may have some
>>>>
>>>>limitations on its memory
>>>>
>>>>>display unless it gets the information from /proc.
>>>>>
>>>>>_______________________________________________
>>>>>rhn-users mailing list
>>>>>rhn-users at redhat.com
>>>>>https://www.redhat.com/mailman/listinfo/rhn-users
>>>>
>>>>_______________________________________________
>>>>rhn-users mailing list
>>>>rhn-users at redhat.com
>>>>https://www.redhat.com/mailman/listinfo/rhn-users
>>>>
>>>>*******************************************************************
>>>>This email and any files transmitted with it are
>>
>> confidential and
>>
>>>>intended solely for the use of the individual or entity to
>>>
>>>whom they
>>>
>>>>are addressed. If you have received this email in error
>>>
>>>please notify
>>>
>>>>the system manager.
>>>>
>>>>This footnote also confirms that this email message has been
>>>
>>>swept
>>>
>>>>for the presence of computer viruses.
>>>>
>>>>www.hubbell.com - Hubbell Incorporated
>>>>
>>>>_______________________________________________
>>>>rhn-users mailing list
>>>>rhn-users at redhat.com
>>>>https://www.redhat.com/mailman/listinfo/rhn-users
>>>
>>>_______________________________________________
>>>rhn-users mailing list
>>>rhn-users at redhat.com
>>>https://www.redhat.com/mailman/listinfo/rhn-users
>>>
>>>_______________________________________________
>>>rhn-users mailing list
>>>rhn-users at redhat.com
>>>https://www.redhat.com/mailman/listinfo/rhn-users
>>
>>
>> _______________________________________________
>> rhn-users mailing list
>> rhn-users at redhat.com
>> https://www.redhat.com/mailman/listinfo/rhn-users
>
>_______________________________________________
>rhn-users mailing list
>rhn-users at redhat.com
>https://www.redhat.com/mailman/listinfo/rhn-users
More information about the rhn-users
mailing list