Re: ibm 326m dual core opteron misreporting memory ?

"Bob Flynn (bobf)" <[email protected]>
Newsgroups gmane.linux.redhat.release.taroon.general
Message-ID <C611E2BD39743E4E81081CB440F0D0FF061BFE@exduba.dublin.ad.s3group.com>

Good_BOX> uname -a
Linux Good_BOX 2.4.21-32.ELsmp #1 SMP Fri Apr 15 21:03:28 EDT 2005 x86_64 x86_64 x8
6_64 GNU/Linux


Bad_Box> uname -a
Linux Bad_Box 2.4.21-47.EL #1 Wed Jul 5 20:39:00 EDT 2006 i686 athlon i386 GNU/Lin
ux

Looks like I installed the amd 64bit OS on the good box, but stuck a i386 32 bit on the bad box. I will redo and see what happens.

Thanks for the suggestion.

-Bob

Message: 2
Date: Wed, 04 Oct 2006 20:33:35 +0200
From: Arjan van de Ven <[email protected]>
Subject: Re: ibm 326m dual core opteron misreporting memory ?
To: "Discussion of Red Hat Enterprise Linux 3 (Taroon)"
	<[email protected]>
Message-ID: <1159986816.3000.36.camel-NIQFrBLA1CpScpXdPBN83iCwEArCW2h5@public.gmane.org>
Content-Type: text/plain

On Wed, 2006-10-04 at 19:16 +0100, bob flynn wrote:

> So, is the memory misreporting, something to do with the dual core, or
> is there something else I should be looking at.

most likely on the "broken" box you're using the athlon.rpm kernel,
while on the "good" box you're using the i686.rpm kernel.

.... you might want to fix that. Or use the 64 bit OS :)





The information contained in this e-mail and in any attachments is confidential and is designated solely for the attention of the intended recipient(s). If you are not an intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or any part thereof. If you have received this e-mail in error, please notify the sender by return e-mail and delete all copies of this e-mail from your computer system(s).
Please direct any additional queries to: [email protected]
Thank You.

--
Taroon-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/taroon-list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.