Skip to contentSkip to conversation

ipmi kcs problem

DISCUSSION Erhan Y. 2 participants 2 messages Oct 7, 2022 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Erhan Y.

author
#1 lore raw

Hi,We are trying to get SMBIOS tables from host on BMC (ast-2500). KCS#3 is enabled in DTS (with address CA2) and on the host side IPMI_SI driver initialization fails.What can be wrong in our setup? What are to required steps to get the SMBIOS tables from the host?
Host Logs:[    7.796852] ipmi_si: IPMI System Interface driver[    7.796893] ipmi_si dmi-ipmi-si.0: ipmi_platform: probing via SMBIOS[    7.796900] ipmi_platform: ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0[    7.796905] ipmi_si: Adding SMBIOS-specified kcs state machine[    7.797140] ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca2, slave address 0x20, irq 0[    7.797152] ipmi_si dmi-ipmi-si.0: Interface detection failed

BMC Logs: [    0.301014] ast-kcs-bmc 1e78902c.kcs: Initialised IPMI client for channel 3[    0.301085] ast-kcs-bmc 1e78902c.kcs: Initialised channel 3 at 0xca2[   22.521031] systemd[1]: Created slice Slice /system/phosphor-ipmi-kcs.

 systemctl status phosphor-ipmi-kcs@ipmi-kcs3● [email protected] - Phosphor IPMI KCS DBus Bridge     Loaded: loaded (/lib/systemd/system/[email protected]; enabled; vendor preset: disabled)     Active: active (running) since Thu 1970-01-01 00:01:54 UTC; 24min ago   Main PID: 443 (kcsbridged)     CGroup: /system.slice/system-phosphor\x2dipmi\x2dkcs.slice/[email protected]             └─ 443 /usr/libexec/kcsbridged -c ipmi-kcs3

Jan 01 00:01:53 Aselsan-Server systemd[1]: Starting Phosphor IPMI KCS DBus Bridge...Jan 01 00:01:54 Aselsan-Server systemd[1]: Started Phosphor IPMI KCS DBus Bridge.
#2 lore raw

Hi,

Quoted 1 line · Erhan Y.

We are trying to get SMBIOS tables from host on BMC (ast-2500).

What tools are you going to use for that once you get IPMI exchange working? On our Tioga Pass system it's performed by UEFI on startup using MDRv1 protocol.

Quoted 1 line

KCS#3 is enabled in DTS (with address CA2)

&kcs3 { 
        // BMC KCS channel 3
        status = "okay";
        aspeed,lpc-io-reg = <0xca2>;
};

is what works for us.

Quoted 5 lines

[    7.796852] ipmi_si: IPMI System Interface driver
[    7.796893] ipmi_si dmi-ipmi-si.0: ipmi_platform: probing via SMBIOS
[    7.796900] ipmi_platform: ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
[    7.796905] ipmi_si: Adding SMBIOS-specified kcs state machine
[    7.797140] ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca2, slave address 0x20, irq 0

This looks correct.

Quoted 3 lines

BMC Logs:
[    0.301014] ast-kcs-bmc 1e78902c.kcs: Initialised IPMI client for channel 3 [    0.301085] ast-kcs-bmc 1e78902c.kcs: Initialised channel 3 at 0xca2

This too, 1e78902c.kcs is created and used.

So everything looks proper so far.

Do you know if LPC communication between your host and BMC works at all? Apart from KCS it's also often used for 16550A serial ports (with BMC being an LPC slave).

Do you have appropriate confguration for ipmi_kcs3 in /usr/share/ipmi-providers/channel_config.json?

Signature · 2 lines
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:[email protected]