Description of problem: Sometimes after rebooting, ipmievd reports threshold exceeded warnings for a non-existent fan sensor: Jan 26 19:56:06 testhost ipmievd: [ID local4.notice] Fan sensor FAN 3 Lower Non-critical going low (Reading 0 < Threshold 784 RPM) Jan 26 19:56:06 testhost ipmievd: [ID local4.notice] Fan sensor FAN 3 Lower Critical going low (Reading 0 < Threshold 576 RPM) Jan 26 19:56:06 testhost ipmievd: [ID local4.notice] Fan sensor FAN 3 Lower Non-recoverable going low (Reading 0 < Threshold 400 RPM) There is definitely nothing plugged into the "FAN3" header on the motherboard; there are blowers plugged into the FAN1 and FAN2 headers. Version-Release number of selected component (if applicable): ipmitool-1.8.11-1.fc11.x86_64 How reproducible: Not consistently. I haven't noticed whether the ipmitool "sdr list" and "sensor list" output (see below) always reports the presence of a FAN 3 sensor. Steps to Reproduce: 1. Reboot system 2. 3. Actual results: See above Expected results: No warnings Additional info: The motherboard is a Supermicro X8DTL-iF with an on-board IPMI module. ipmitool sel list: ... 71 | Pre-Init Time-stamp | Fan #0x43 | Lower Non-critical going low 72 | Pre-Init Time-stamp | Fan #0x43 | Lower Critical going low 73 | Pre-Init Time-stamp | Fan #0x43 | Lower Non-recoverable going low 74 | 01/26/2010 | 08:37:44 | Physical Security #0x54 | General Chassis intrusion | Asserted 75 | 01/26/2010 | 19:55:57 | Fan #0x43 | Lower Non-critical going low 76 | 01/26/2010 | 19:55:57 | Fan #0x43 | Lower Critical going low 77 | 01/26/2010 | 19:55:57 | Fan #0x43 | Lower Non-recoverable going low ipmitool sdr list: FAN 1 | 3025 RPM | ok FAN 2 | 3025 RPM | ok FAN 3 | 0 RPM | nr FAN 4 | disabled | ns FAN 5 | disabled | ns FAN 6 | disabled | ns CPU1 Voltage | disabled | ns CPU2 Voltage | 1 Volts | ok +1.5v Voltage | 1.51 Volts | ok +5 Voltage | 5.09 Volts | ok +5VSB Voltage | 5.09 Volts | ok +12 Voltage | 12.03 Volts | ok -12 Voltage | -11.80 Volts | ok +3.3 Voltage | 3.29 Volts | ok +3.3VSB Voltage | 3.26 Volts | ok Battery Voltage | 3.22 Volts | ok CPU1 Temp. | 0 unspecified | nr CPU2 Temp. | 0 unspecified | ok System Temp. | 35 degrees C | ok Chassis Intru | 0 unspecified | ok PS Status | 0 unspecified | nc ipmitool sensor list: FAN 1 | 3025.000 | RPM | ok | 400.000 | 576.000 | 784.000 | 7921.000 | 9025.000 | 10000.000 FAN 2 | 3025.000 | RPM | ok | 400.000 | 576.000 | 784.000 | 7921.000 | 9025.000 | 10000.000 FAN 3 | 0.000 | RPM | nr | 400.000 | 576.000 | 784.000 | 7921.000 | 9025.000 | 10000.000 FAN 4 | na | RPM | na | na | na | na | na | na | na FAN 5 | na | RPM | na | na | na | na | na | na | na FAN 6 | na | RPM | na | na | na | na | na | na | na CPU1 Voltage | na | Volts | na | na | na | na | na | na | na CPU2 Voltage | 1.024 | Volts | ok | 0.808 | 0.816 | 0.824 | 1.352 | 1.360 | 1.368 +1.5v Voltage | 1.512 | Volts | ok | 1.320 | 1.328 | 1.336 | 1.656 | 1.664 | 1.672 +5 Voltage | 5.088 | Volts | ok | 4.416 | 4.448 | 4.480 | 5.536 | 5.568 | 5.600 +5VSB Voltage | 5.088 | Volts | ok | 4.416 | 4.448 | 4.480 | 5.536 | 5.568 | 5.600 +12 Voltage | 12.031 | Volts | ok | 10.600 | 10.653 | 10.706 | 13.250 | 13.303 | 13.356 -12 Voltage | -11.804 | Volts | ok | -13.550 | -13.356 | -13.162 | -10.446 | -10.252 | -10.058 +3.3 Voltage | 3.288 | Volts | ok | 2.880 | 2.904 | 2.928 | 3.648 | 3.672 | 3.696 +3.3VSB Voltage | 3.264 | Volts | ok | 2.880 | 2.904 | 2.928 | 3.648 | 3.672 | 3.696 Battery Voltage | 3.216 | Volts | ok | 2.880 | 2.904 | 2.928 | 3.648 | 3.672 | 3.696 CPU1 Temp. | 0.000 | unspecified | nr | na | na | na | na | na | na CPU2 Temp. | 0.000 | unspecified | ok | na | na | na | na | na | na System Temp. | 35.000 | degrees C | ok | 13.000 | 16.000 | 18.000 | 77.000 | 82.000 | 90.000 Chassis Intru | 0.000 | unspecified | ok | na | na | na | na | na | na PS Status | 0.000 | unspecified | nc | na | na | na | na | na | na dmesg | grep -i ipmi: ipmi message handler version 39.2 IPMI System Interface driver. ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0 ipmi_si: Invalid return from get global enables command, cannot enable the event buffer. ipmi: Found new BMC (man_id: 0x0015d9, prod_id: 0x0006, dev_id: 0x20) IPMI kcs interface initialized ipmi device interface
I seriously doubt it's fault of ipmitool - it just shows info read from ipmi driver or remote machine, it should not invent new sensor... Can you try the same query with freeipmi's ipmi-sensors tool? If another implementation of ipmi front-end shows the same result, it's bug in kernel (ipmi driver) or in your HW. And, if possible, attach output of ipmitool -vvv sensor list or attach wireshark capture of the IPMI packets (it's easier for me to read packets in wireshark than hex output of ipmitool).
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.