Hide Forgot
Description of problem: there are really random numbers when running delloem command on s390x Version-Release number of selected component (if applicable): ipmitool-1.8.11-11.el6.ppc64 only ppc arch didnt try s390x i386 + x8664 works as expected How reproducible: deterministic Steps to Reproduce: # rpm -q ipmitool ipmitool-1.8.11-11.el6.ppc64 # ipmitool -y 0000000000000000 -H 1.3.4.2 -U root -P XXXXXX delloem powermonitor Actual results: Power Tracking Statistics Statistic : Cumulative Energy Consumption Start Time : Tue Jul 14 22:55:10 2071 Finish Time : Thu Oct 31 18:37:02 1991 Reading : 3640655.9 kWh Statistic : System Peak Power Start Time : Thu May 10 15:42:06 2085 Peak Time : Mon Jun 20 10:02:54 2061 Peak Reading : 42496 W Statistic : System Peak Amperage Start Time : Thu May 10 15:42:06 2085 Peak Time : Fri Sep 15 12:25:50 2023 Peak Reading : 204.8 A Expected results: same as fro x8664: # rpm -q ipmitool ipmitool-1.8.11-11.el6.x86_64 # ipmitool -y 0000000000000000 -H 1.3.4.2 -U root -P XXXXXX delloem powermonitor Power Tracking Statistics Statistic : Cumulative Energy Consumption Start Time : Thu Aug 18 11:47:10 2011 Finish Time : Thu Aug 18 13:14:34 2011 Reading : 0.2 kWh Statistic : System Peak Power Start Time : Thu Aug 18 11:47:36 2011 Peak Time : Thu Aug 18 12:59:24 2011 Peak Reading : 166 W Statistic : System Peak Amperage Start Time : Thu Aug 18 11:47:36 2011 Peak Time : Thu Aug 18 12:24:05 2011 Peak Reading : 0.8 A
'ipmitool delloem powermonitor' does not convert integers from network format (it's little endian in IPMI!) to native one -> problems on non-Intel platforms.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
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/RHBA-2011-1603.html