| commit | b485b1e67201597c2cbc9683892624304e442d32 | [log] [tgz] |
|---|---|---|
| author | Johnathan Mantey <johnathanx.mantey@intel.com> | Wed Jul 28 15:08:30 2021 -0700 |
| committer | Johnathan Mantey <johnathanx.mantey@intel.com> | Wed Jul 28 15:39:47 2021 -0700 |
| tree | df2e28224e16dad4250324fbad893df03cc6994d | |
| parent | 3694d07ae7e2841d80f501de229cc86c7c5fab55 [diff] |
Make sensor/sdr list commands work on systems with > 255 sensors The "ipmitool sdr elist" and "ipmitool sensor list" commands failed to operate correctly on systems that contain more than 255 sensors. A change made in the past assigned up to 255 sensors to LUN 0, 1, and 3. The code for iterating the SDR's did not get updated at the same time. The SDR record number acted as the sensor number. This incompatibility caused error response codes to be returned when sensor number 255 (which is reserved) was accessed. The change in this commit modifies the SDR access code to prevent using the reserved sensor number. SDR records are still assigned in order. The sensor number associated with the SDR are assigned to avoid the reserved value, and in the same manner as code previously submitted and merged. Tested: Installed the modified code on a SUT that enumerates more than 256 sensors. Issued "ipmitool sensor list" and confirmed all sensors were displayed. The "Get SDR 00ff command failed: Invalid data field in request" error message was not displayed. Issued "ipmitool sdr elist" and confirmed all sensors were displayed. The "Get SDR 00ff command failed: Invalid data field in request" error message was not displayed. Confirmed the sensor number/LUN guard code was not activated. Change-Id: I194a3116fdf255527a8c5036ee71b8b478c9b275 Signed-off-by: Johnathan Mantey <johnathanx.mantey@intel.com>
This component is intended to provide Intel-specific IPMI[3] command handlers for OpenBMC. These handlers are intended to integrate BMC with servers based on Intel architecture.
intel-ipmi-oem serves as an extension[1] to OpenBMC IPMI daemon[2]. It is compiled as a shared library and intended to both:
Related features provided by the library are grouped in separate source files. Main extensions to vanilla OpenBMC IPMI stack are the following:
[4]