All of the mainline kernels are built with CONFIG_IPMI_HANDLER set to m, so I assume testing will not reproduce the bug for any of the upstream kernels. We now know that the change of CONFIG_IPMI_HANDLER from m to y in Trusty is what causes this bug.
All of the mainline kernels are built with CONFIG_IPMI_HANDLER set to m, so I assume testing will not reproduce the bug for any of the upstream kernels. We now know that the change of CONFIG_IPMI_HANDLER from m to y in Trusty is what causes this bug.