11
29
Fork
You've already forked ipmitool
33

SEL: cannot display Sensor name when sensor owner lun1 #8

Closed
opened 2023年08月04日 07:44:01 +02:00 by XinyuLu · 2 comments

Describe the bug
SEL: cannot display SEL's SensorName when sensor owner lun1

IPMITOOL Version

ipmitool-Master % src/ipmitool -V
ipmitool version 1.8.19.13.gbe11d94

To Reproduce
Steps to reproduce the behavior:

  1. Using AMI/BMC to generate a sensor error event. The sensor belong to LUN1
    GPU1_MEM | 10h | ok | 11.1 | Uncorrectable ECC
    GPU2_MEM | 11h | ok | 11.2 | Uncorrectable ECC
    GPU3_MEM | 12h | ok | 11.3 | Uncorrectable ECC
    GPU4_MEM | 13h | ok | 11.4 | Uncorrectable ECC
    GPU5_MEM | 14h | ok | 11.5 | Uncorrectable ECC
    GPU6_MEM | 15h | ok | 11.6 | Uncorrectable ECC
    GPU7_MEM | 16h | ok | 11.7 | Uncorrectable ECC
    GPU8_MEM | 17h | ok | 11.8 | Uncorrectable ECC
  2. Run ipmitool sel elist
  3. Observe the abnormal reply:
    c5 | 2023年08月02日 | 17时17分24秒 CST | Memory | Uncorrectable ECC | Asserted
    c6 | 2023年08月02日 | 17时18分29秒 CST | Memory | Uncorrectable ECC | Asserted
    c7 | 2023年08月02日 | 17时18分29秒 CST | Memory | Uncorrectable ECC | Asserted
    c8 | 2023年08月02日 | 17时18分30秒 CST | Memory | Uncorrectable ECC | Asserted
    c9 | 2023年08月02日 | 17时18分30秒 CST | Memory | Uncorrectable ECC | Asserted
    ca | 2023年08月02日 | 17时19分34秒 CST | Memory | Uncorrectable ECC | Asserted
    cb | 2023年08月02日 | 17时19分34秒 CST | Memory INTEGRAL_DIMM | Uncorrectable ECC | Asserted
    cc | 2023年08月02日 | 17时19分34秒 CST | Memory | Uncorrectable ECC | Asserted
    SensorName is empty or wrong.(Expexct GPU1_MEM)

Expected behavior
A clear and concise description of what you expected to happen.

Additional context
Add any other context about the problem here.

**Describe the bug** SEL: cannot display SEL's SensorName when sensor owner lun1 **IPMITOOL Version** ipmitool-Master % src/ipmitool -V ipmitool version 1.8.19.13.gbe11d94 **To Reproduce** Steps to reproduce the behavior: 1. Using AMI/BMC to generate a sensor error event. The sensor belong to LUN1 GPU1_MEM | 10h | ok | 11.1 | Uncorrectable ECC GPU2_MEM | 11h | ok | 11.2 | Uncorrectable ECC GPU3_MEM | 12h | ok | 11.3 | Uncorrectable ECC GPU4_MEM | 13h | ok | 11.4 | Uncorrectable ECC GPU5_MEM | 14h | ok | 11.5 | Uncorrectable ECC GPU6_MEM | 15h | ok | 11.6 | Uncorrectable ECC GPU7_MEM | 16h | ok | 11.7 | Uncorrectable ECC GPU8_MEM | 17h | ok | 11.8 | Uncorrectable ECC 2. Run `ipmitool sel elist` 3. Observe the abnormal reply: c5 | 2023年08月02日 | 17时17分24秒 CST | Memory | Uncorrectable ECC | Asserted c6 | 2023年08月02日 | 17时18分29秒 CST | Memory | Uncorrectable ECC | Asserted c7 | 2023年08月02日 | 17时18分29秒 CST | Memory | Uncorrectable ECC | Asserted c8 | 2023年08月02日 | 17时18分30秒 CST | Memory | Uncorrectable ECC | Asserted c9 | 2023年08月02日 | 17时18分30秒 CST | Memory | Uncorrectable ECC | Asserted ca | 2023年08月02日 | 17时19分34秒 CST | Memory | Uncorrectable ECC | Asserted cb | 2023年08月02日 | 17时19分34秒 CST | Memory INTEGRAL_DIMM | Uncorrectable ECC | Asserted cc | 2023年08月02日 | 17时19分34秒 CST | Memory | Uncorrectable ECC | Asserted SensorName is empty or wrong.(Expexct GPU1_MEM) **Expected behavior** A clear and concise description of what you expected to happen. **Additional context** Add any other context about the problem here.

Unfortunately, I don't have any hardware that uses LUN1 for sensors, so I can't debug, and it's not obvious from the code why it behaves this way. If you could debug it and post a PR, I would gladly accept it.

Unfortunately, I don't have any hardware that uses LUN1 for sensors, so I can't debug, and it's not obvious from the code why it behaves this way. If you could debug it and post a PR, I would gladly accept it.

From the code of ipmitool it looks to me like it should work properly if your BMC sets the Generator ID field properly.
According to specification, it must be:
image

According to the code in ipmi_sdr_find_sdr_bynumtype(), the IPMB Slave Address is not checked and LUN is always extracted from bits [1:0] of Byte 2.

Most probably, your BMC doesn't specify LUN in the SEL records. Please check that by running ipmitool in verbose mode to see the actual bytes you get from your BMC. If you find out that the SEL records your BMC reports actually do contain a proper LUN in the Generator ID field, then feel free to reopen this bug (if available) or create new one with all that new debug info added.

From the code of `ipmitool` it looks to me like it should work properly if your BMC sets the Generator ID field properly. According to specification, it must be: ![image](/attachments/2f45e052-b25f-4550-8c06-8cea47d58e2d) According to the code in `ipmi_sdr_find_sdr_bynumtype()`, the `IPMB Slave Address` is not checked and LUN is always extracted from bits [1:0] of Byte 2. Most probably, your BMC doesn't specify LUN in the SEL records. Please check that by running `ipmitool` in verbose mode to see the actual bytes you get from your BMC. If you find out that the SEL records your BMC reports actually do contain a proper LUN in the Generator ID field, then feel free to reopen this bug (if available) or create new one with all that new debug info added.
Sign in to join this conversation.
No Branch/Tag specified
master
bugfix/43-Fix-timezone-and-DST-in-SEL
pages
bugfix/fix-ci-builds
feature/refactor-sdr-name-handling
cleanup/nm
feature/add-support-for-boot-mailbox
codefactor
bugfix/26
IPMITOOL_1_8_19
IPMITOOL_1_8_18
IPMITOOL_1_8_17
IPMITOOL_1_8_16
IPMITOOL_1_8_15
IPMITOOL_1_8_15RC1
IPMITOOL_1_8_14
IPMITOOL_1_8_14RC2
IPMITOOL_1_8_14RC1
ipmitool
IPMITOOL_1_8_13
IPMITOOL_1_8_13RC1
IPMITOOL_1_8_12
IPMITOOL_1_8_9
IPMITOOL_1_8_8
IPMITOOL_1_8_7
IPMITOOL_1_8_6
IPMITOOL_1_8_5
IPMITOOL_1_8_0
IPMITOOL_S10_U1
IPMITOOL_1_6_1
IPMITOOL_1_6_0
IPMITOOL_1_5_9
IPMITOOL_1_5_8
IPMITOOL_1_5_7
IPMITOOL_1_5_6
IPMITOOL_1_5_4
IPMITOOL_1_4_1_1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
IPMITool/ipmitool#8
Reference in a new issue
IPMITool/ipmitool
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?