On Wed, 2012-12-05 at 14:58 -0700, Garry Anderson wrote: > Albert, > I munged the make files to build the code and it seems better, but not > sure about the PS. We have two of them and they are in a nominal > state. Here is the output: > > ./ipmi-sensors --interpret-oem-data -b > ID | Name | Type | Reading | Units | Event > 4 | CPU1 Temp | OEM Reserved | N/A | N/A | 'Low' > 71 | CPU2 Temp | OEM Reserved | N/A | N/A | 'Low' > 138 | System Temp | Temperature | 18.00 | C | 'OK' > 205 | Peripheral Temp | Temperature | 26.00 | C | 'OK' > 272 | PCH Temp | Temperature | 43.00 | C | 'OK' > 339 | FAN1 | Fan | 12450.00 | RPM | 'OK' > 406 | FAN2 | Fan | 13500.00 | RPM | 'OK' > 473 | FAN3 | Fan | 13350.00 | RPM | 'OK' > 540 | FAN4 | Fan | 13050.00 | RPM | 'OK' > 607 | FAN5 | Fan | N/A | RPM | N/A > 674 | FAN6 | Fan | N/A | RPM | N/A > 741 | FANA | Fan | N/A | RPM | N/A > 808 | FANB | Fan | N/A | RPM | N/A > 875 | VTT | Voltage | 1.04 | V | 'OK' > 942 | CPU1 Vcore | Voltage | 0.93 | V | 'OK' > 1009 | CPU2 Vcore | Voltage | 0.90 | V | 'OK' > 1076 | VDIMM AB | Voltage | 1.47 | V | 'OK' > 1143 | VDIMM CD | Voltage | 1.49 | V | 'OK' > 1210 | VDIMM EF | Voltage | 1.49 | V | 'OK' > 1277 | VDIMM GH | Voltage | 1.49 | V | 'OK' > 1344 | +1.1 V | Voltage | 1.09 | V | 'OK' > 1411 | +1.5 V | Voltage | 1.47 | V | 'OK' > 1478 | 3.3V | Voltage | 3.26 | V | 'OK' > 1545 | +3.3VSB | Voltage | 3.36 | V | 'OK' > 1612 | 5V | Voltage | 4.99 | V | 'OK' > 1679 | +5VSB | Voltage | 5.06 | V | 'OK' > 1746 | 12V | Voltage | 12.19 | V | 'OK' > 1813 | VBAT | Voltage | 3.17 | V | 'OK' > 1880 | Chassis Intru | Physical Security | N/A | N/A | > 'General Chassis Intrusion' > 1947 | PS Status | Power Supply | N/A | N/A | > 'Presence detected' 'Unrecognized Event = 0100h' 'Unrecognized Event = > 0200h' 'Unrecognized Event = 0400h' 'Unrecognized Event = 0800h' > 'Unrecognized Event = 1000h' 'Unrecognized Event = 2000h' > 'Unrecognized Event = 4000h'
This is a bug you can find in a few motherboards. Effectively the motherboard is returning illegal data. The --ignore-unrecognized-events option can help clear that up for you. Al > > sudo ./ipmi-sensors --interpret-oem-data -b -v -r 1947 > Record ID: 1947 > ID String: PS Status > Sensor Type: Power Supply (8h) > Sensor Number: 85 > IPMB Slave Address: 10h > Sensor Owner ID: 20h > Sensor Owner LUN: 0h > Channel Number: 0h > Entity ID: power supply (10) > Entity Instance: 1 > Entity Instance Type: Physical Entity > Event/Reading Type Code: 6Fh > Sensor Event: 'Presence detected' > Sensor Event: 'Unrecognized Event = 0100h' > Sensor Event: 'Unrecognized Event = 0200h' > Sensor Event: 'Unrecognized Event = 0400h' > Sensor Event: 'Unrecognized Event = 0800h' > Sensor Event: 'Unrecognized Event = 1000h' > Sensor Event: 'Unrecognized Event = 2000h' > Sensor Event: 'Unrecognized Event = 4000h' > > Thanks for looking into this. > > --Garry > > On Wed, Dec 5, 2012 at 11:40 AM, anonymous <[email protected]> wrote: > > Follow-up Comment #2, sr #108197 (project freeipmi): > > > > I pulled the source down, but get the following error: > > > > ./autogen.sh > > + aclocal -I config > > + autoheader > > + libtoolize --force --automake --copy > > + automake --gnu --include-deps --copy --add-missing > > doc/Makefile.am:16: `doc_DATA' is used but `docdir' is undefined > > Makefile.am:85: `doc_DATA' is used but `docdir' is undefined > > > > and ./configure does not exist. > > > > I was running 1.2.3 which I forgot to mention. > > > > Thanks for your quick response > > --Garry > > > > > > _______________________________________________________ > > > > Reply to this item at: > > > > <http://savannah.gnu.org/support/?108197> > > > > _______________________________________________ > > Message sent via/by Savannah > > http://savannah.gnu.org/ > > > > > -- Albert Chu [email protected] Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/freeipmi-devel
