** Description changed: [Impact] - Just loading the necessary modules is not enough to get a working IPMI system interface (/dev/ipmi0) on Cavium ThunderX CRBs, and other ThunderX-based Gigabyte servers. You have to do some magic: - - echo ipmi_ssif 0x12 >/sys/bus/i2c/devices/i2c-4/new_device - or maybe: - echo ipmi_ssif 0x12 >/sys/bus/i2c/devices/i2c-5/new_device - - Loading the modules should be enough. + The IPMI system interface (/dev/ipmi0) is unavailable on Cavium ThunderX-based systems. This prevents various in-band management tasks, including auto-enlistment using MAAS. [Test Case] sudo modprobe ipmi_ssif sudo modprobe ipmi_devintf Do you have a working /dev/ipmi0? sudo ipmitool lan print [Regression Risk] - The driver being fixed is only used on ThunderX-based systems, and is currently not usable w/o the above manual config. + For hwe-z, this is a small fix to a driver that is only used on ThunderX-based systems, and is currently not usable w/o magic manual steps. + + For hwe-x and hwe-y, this also impacts the i2c-octeon driver. After + hwe-y, upstream split that driver into 2 pieces to factor out code that + could be shared with i2c-thunderx, and then i2c-thunderx was added. i2c- + octeon is a driver for Cavium OCTEON systems, which are MIPS64 - an + architecture unsupported by Ubuntu, so regression risk is negligible. + i2c-thunderx is a new driver that is only loaded on ThunderX-based + systems, so the testing we've performed on ThunderX should mitigate that + regression risk. + + Note: there are issues with older firmware (version varies depending on + platform) where the IPMI device can vanish between reboots, requiring a + BMC reset to recover. This doesn't cause any other problem - drivers + don't load, and it's as if this driver was never added. However, it is + worth noting here in case people google it. Please upgrade your firmware + if you run into this.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1688132 Title: Support IPMI system interface on Cavium ThunderX Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Status in linux source package in Zesty: Fix Committed Bug description: [Impact] The IPMI system interface (/dev/ipmi0) is unavailable on Cavium ThunderX-based systems. This prevents various in-band management tasks, including auto-enlistment using MAAS. [Test Case] sudo modprobe ipmi_ssif sudo modprobe ipmi_devintf Do you have a working /dev/ipmi0? sudo ipmitool lan print [Regression Risk] For hwe-z, this is a small fix to a driver that is only used on ThunderX-based systems, and is currently not usable w/o magic manual steps. For hwe-x and hwe-y, this also impacts the i2c-octeon driver. After hwe-y, upstream split that driver into 2 pieces to factor out code that could be shared with i2c-thunderx, and then i2c-thunderx was added. i2c-octeon is a driver for Cavium OCTEON systems, which are MIPS64 - an architecture unsupported by Ubuntu, so regression risk is negligible. i2c-thunderx is a new driver that is only loaded on ThunderX-based systems, so the testing we've performed on ThunderX should mitigate that regression risk. Note: there are issues with older firmware (version varies depending on platform) where the IPMI device can vanish between reboots, requiring a BMC reset to recover. This doesn't cause any other problem - drivers don't load, and it's as if this driver was never added. However, it is worth noting here in case people google it. Please upgrade your firmware if you run into this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
