This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial ** Tags added: verification-needed-yakkety -- 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: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Released 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
