Also no idea about that system, but you may want to try 'ipmitool fru'. I know at least our current systems will make the effort to make the DIMM SPD info queryable via FRU.
From: Albert Chu <ch...@llnl.gov>
To: Asif Iqbal <vad...@gmail.com>
Cc: "Ipmitool-devel@lists.sourceforge.net"
<Ipmitool-devel@lists.sourceforge.net>
Date: 01/14/2011 12:48 PM
Subject: Re: [Ipmitool-devel] ipmitool not reading dimms
On Thu, 2011-01-13 at 12:33 -0800, Asif Iqbal wrote:
> I have installed ipmitool version 1.8.11 on ubuntu 10.04 lts running
> on Sun Fire X4150
>
> It does show the status of the DIMMs. Is this a bug?
I can't say specifically for your motherboard, but on many motherboards
it's not a bug. The "sensor" listed below is more just an indication
that it exists, not that you can read from it. For example, the
"sensor" might only be an event sensor and can only report events in the
SEL.
Al
> $ sudo dmidecode | less
> iqbala@arl-splunk-01:~$ sudo ipmitool sdr
> CPU 0 Temp | 23 degrees C | ok
> CPU 1 Temp | 34 degrees C | ok
> Ambient Temp0 | 27 degrees C | ok
> Vcc 12V | 12.08 Volts | ok
> Vtt | 1.10 Volts | ok
> MCH 1.5V | 1.47 Volts | ok
> Vcc 3.3V | 3.29 Volts | ok
> Vcc 5V | 5.18 Volts | ok
> NIC Vtt 1.2V | 1.21 Volts | ok
> Vcc 3.3V STB | 3.25 Volts | ok
> Vcc 2.5V STB | 2.52 Volts | ok
> Vcc 1.8V | 1.82 Volts | ok
> Fanbd1/FM0 Fan1 | 10241 RPM | ok
> Fanbd1/FM0 Fan0 | 10703 RPM | ok
> Fanbd1/FM1 Fan1 | 10549 RPM | ok
> Fanbd1/FM1 Fan0 | 10934 RPM | ok
> Fanbd1/FM2 Fan1 | 10087 RPM | ok
> Fanbd1/FM2 Fan0 | 10549 RPM | ok
> Fanbd0/FM0 Fan1 | 10010 RPM | ok
> Fanbd0/FM0 Fan0 | 10087 RPM | ok
> Fanbd0/FM1 Fan1 | 9856 RPM | ok
> Fanbd0/FM1 Fan0 | 10395 RPM | ok
> Fanbd0/FM2 Fan1 | 10549 RPM | ok
> Fanbd0/FM2 Fan0 | 10164 RPM | ok
> Fanbd0/FM3 Fan1 | 10857 RPM | ok
> Fanbd0/FM3 Fan0 | 10934 RPM | ok
> Fanbd0/FM0 | 0x02 | ok
> Fanbd0/FM1 | 0x02 | ok
> Fanbd0/FM2 | 0x02 | ok
> Fanbd0/FM3 | 0x02 | ok
> Fanbd1/FM0 | 0x02 | ok
> Fanbd1/FM1 | 0x02 | ok
> Fanbd1/FM2 | 0x02 | ok
> PS0 Under Volt | 0x00 | ok
> PS1 Under Volt | 0x00 | ok
> PS0 OC Fault | 0x00 | ok
> PS1 OC Fault | 0x00 | ok
> CPU 0 | 0x80 | ok
> CPU 1 | 0x80 | ok
> Power Unit | Not Readable | ns
> Power Supply 0 | 0x00 | ok
> Power Supply 1 | 0x20 | ok
> DIMM-A0 | Not Readable | ns
> DIMM-A1 | Not Readable | ns
> DIMM-A2 | Not Readable | ns
> DIMM-A3 | Not Readable | ns
> DIMM-B0 | Not Readable | ns
> DIMM-B1 | Not Readable | ns
> DIMM-B2 | Not Readable | ns
> DIMM-B3 | Not Readable | ns
> DIMM-C0 | Not Readable | ns
> DIMM-C1 | Not Readable | ns
> DIMM-C2 | Not Readable | ns
> DIMM-C3 | Not Readable | ns
> DIMM-D0 | Not Readable | ns
> DIMM-D1 | Not Readable | ns
> DIMM-D2 | Not Readable | ns
> DIMM-D3 | Not Readable | ns
> POST Error | Not Readable | ns
> Eventlog | Not Readable | ns
> System Event | Not Readable | ns
> Critical INT | Not Readable | ns
> Watchdog | Not Readable | ns
>
> Please let me know how to get the status of the DIMMs.
>
> dmidecode showing all the physical memory
>
> Handle 0x001D, DMI type 16, 15 bytes
> Physical Memory Array
> Location: System Board Or Motherboard
> Use: System Memory
> Error Correction Type: Multi-bit ECC
> Maximum Capacity: 64 GB
> Error Information Handle: Not Provided
> Number Of Devices: 16
> Handle 0x001E, DMI type 19, 15 bytes
>
> Memory Array Mapped Address
> Starting Address: 0x00000000000
> Ending Address: 0x003FFFFFFFF
> Range Size: 16 GB
> Physical Array Handle: 0x001D
> Partition Width: 0
>
> Handle 0x001F, DMI type 17, 27 bytes
> Memory Device
> Array Handle: 0x001D
> Error Information Handle: Not Provided
> Total Width: 72 bits
> Data Width: 64 bits
> Size: 4096 MB
> Form Factor: FB-DIMM
> Set: None
> Locator: DIMM_A0
> Bank Locator: A
> Type: DDR2
> Type Detail: Other
> Speed: 667 MHz (1.5 ns)
> Manufacturer:
> Serial Number:
> Asset Tag:
> Part Number:
> .... stripped......
>
> I noticed dmidecode shows DIMM_A0 and ipmitool is showing DIMM-A0
>
>
>
> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
>
>
------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Ipmitool-devel mailing list
> Ipmitool-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
--
Albert Chu
ch...@llnl.gov
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
------------------------------------------------------------------------------
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can have on your business, and how you
can protect your company and customers by using code signing.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Ipmitool-devel mailing list
Ipmitool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
<<inline: graycol.gif>>
------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
