ThunderX BMC initialization failure
itaru.kitayama at riken.jp
Thu Sep 14 16:17:40 PDT 2017
Thanks for the information. Will try to upgrade the kernel when I have
$ sudo dmidecode |grep IPMI
IPMI Device Information
Does the above something I should expect to see?
On 9/15/17 8:10 AM, dann frazier wrote:
> On Tue, Sep 12, 2017 at 2:55 AM, Itaru Kitayama <itaru.kitayama at riken.jp> wrote:
>> We're seeing below on our ThunderX
>> $ sudo systemctl start ipmi
>> Job for ipmi.service failed because the control process exited with error
>> code. See "systemctl status ipmi.service" and "journalctl -xe" for details.
>> $ sudo journalctl -xe
>> -- Unit ipmi.service has begun starting up.
>> Sep 12 15:54:52 satsuma kernel: ipmi message handler version 39.2
>> Sep 12 15:54:53 satsuma kernel: IPMI System Interface driver.
>> Sep 12 15:54:53 satsuma kernel: ipmi_si: probing via SMBIOS
>> Sep 12 15:54:53 satsuma kernel: ipmi_si: Unable to find any System
>> Sep 12 15:54:53 satsuma openipmi-helper: Startup failed.
>> Sep 12 15:54:53 satsuma systemd: ipmi.service: main process exited,
>> code=exited, status=1/FAILURE
>> Sep 12 15:54:53 satsuma systemd: Failed to start IPMI Driver.
>> -- Subject: Unit ipmi.service has failed
>> Is it caused by the IPMI driver that comes with CentOS 7 or the BIOS?
> There could be multiple things going on here. For one, I don't believe
> openipmi's upstream initscript knows about the ipmi_ssif driver yet.
> This issue may also impact CentOS (and probably needs fixing in
> upstream openipmi):
> And your kernel needs to be new enough and have the right drivers
> enabled to support it.
> v4.12 should be new enough. Tests for that are described here:
> Finally, your BIOS does need to have SMBIOS tables that describe the
> interface. Make sure this returns something:
> $ sudo dmidecode | grep IPMI
More information about the linux-arm-kernel