Created attachment 530662 [details] ipmitool sdr verbose bad performance fix Description of problem: Context : This bug has been detected with a DELL BMC Board on server PowerEdge 1950 and PowerEdge 2950. When using the verbose mode for getting the extended sensor informations with the command "ipmitool -v sdr", the command takes a very long time to retrieve the sensors data. A similar bug has been corrected for the non verbose mode (Command ipmitool sdr) upstream and in RedHat (https://bugzilla.redhat.com/show_bug.cgi?id=722462). However, in the verbose mode calls the functions "ipmi_sdr_get_sensor_event_status" and "ipmi_sdr_get_sensor_event_enable" in which the correction has not been reported and it seems that it is also needed in these functions. Version-Release number of selected component (if applicable): ipmitool 1.8.11 How reproducible: Execute the command ipmitool -v sdr on a PowerEdge Server 1950 or 2950. Actual results: The execution time is more than 10 minutes ! Expected results: The execution time should be about 2 seconds. Additional info: The bug has been raised upstream. Please see the bug report here : https://sourceforge.net/tracker/?func=detail&aid=3429710&group_id=95200&atid=610550. You'll find an attachement specfic for the RHEL RPM.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: same as #671059
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0123.html