Hello Corey,
I am sorry for late reply. I have pasted one of reply by you.
I was doing some investigation on DIMM SPDs and hardware topology.
Finally on one machine, I was successfully able to print DIMM sizes and more
information. Then after analyzing more on my target hardware and reading your
email more carefully, I had three questions/doubts -
(a) You have mentioned that i need to have proper memory entities in SDR. Do
does it mean that if i am able to print all DIMM entity names in FRU record, I
have proper entities? (As i have given in the email below). Am i right?
(b) you mentioned that DIMM SPD need to be tied into BMC's I2C.For the target
hardware, which i am using, DIMM SPD is connected to BMC's I2C bus, but not
directly. The I2C bus for BMC goes through a Mux (PCA9548 I2C switch). Is it
possible to tell ipmitool somehow read DIMM SPD via I2C switch?
(c) I tried using Raw commands also in meantime (As per IPMI specification
v2.0). I can read Fan speed and sensor information successfully but i fail to
read DIMM information using Raw commands. Any pointers in this direction?
Thanks and Sorry for long email,
Regards
Amit
-----------------------------------------------------------
----------------------------------------------------------
It works fine for me. If I do that command on one of my systems that
has the proper data, I get:
FRU Device Description : DIMM 1B SPD (ID 7)
Memory Size : 512 MB
Memory Type : DDR
Voltage Intf : SSTL 2.5V
Error Detect/Cor : ECC
Manufacturer : Xerox
Part Number : MALABS
for every DIMM slot that is present.
For this to work properly, the manufacturer of your system has to set up
everything properly, and it's common to not have it set up right. You
have to have proper memory entities in the SDRs, the DIMM SPD tied into
the BMC's I2C, and DIMMs that have this information. I have another
system, for instance, that has all this except DIMMs that don't have the
proper SPD tie-ins. So they time out when I access them.
-corey
On Mon, 03 Dec 2007 Corey Minyard wrote :
>Yes, so it's finding the FRU data but doesn't print all the information. It
>sounds like you have the skills to create a patch that will add the
>information you need then submit it back to the mailing list. That's my
>suggestion on the best route to go.
>
>-corey
>
>Amit Kumar wrote:
>>
>> When i try -
>>ipmitool -I bmc fru
>>
>>I get output something like -
>>
>>FRU Device Description : p1.d0.fru (ID 12)
>>Product Manufacturer : SAMSUNG
>>Product Name : 1024MB DDR 400 (PC3200) ECC
>>Product Part Number : M3 12L2920CZ3-CCC
>>Product Version : 3343
>>Product Serial : 0629A437
>>
>>FRU Device Description : p1.d1.fru (ID 13)
>>Product Manufacturer : SAMSUNG
>>Product Name : 1024MB DDR 400 (PC3200) ECC
>>Product Part Number : M3 12L2920CZ3-CCC
>>Product Version : 3343
>>Product Serial : 0629A3A8
>>
>>I have gone thgrough the code ipmitool and i observe that it's not printing
>>DIMM sizes. The reason as it appears to me is that modifier_type for all the
>>FRU records is 0x02. There is dimm_spd.c file in lib directory where DIMM
>>information is printed, but it never enters there because modifier type is
>>never 1.
>>
>>Is this what you asked for?
>>
>>Thanks
>>Amit
>>
>
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Ipmitool-devel mailing list
Ipmitool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
