summaryrefslogtreecommitdiffstats
path: root/types.hpp
diff options
context:
space:
mode:
authorJoel Stanley <joel@jms.id.au>2018-02-09 17:18:46 +1030
committerTom Joseph <tomjoseph@in.ibm.com>2018-02-28 04:40:39 +0000
commit82feb17d0c244ed04b82b0fbed3c0a9456986a86 (patch)
tree7c575a0589f44319a2b1679dce3401f6114b1a68 /types.hpp
parent2e12a31f39d95c381a466e277e510faa02c351fb (diff)
downloadphosphor-host-ipmid-82feb17d0c244ed04b82b0fbed3c0a9456986a86.tar.gz
phosphor-host-ipmid-82feb17d0c244ed04b82b0fbed3c0a9456986a86.zip
Revert "Add chassis identify ipmi command."
This reverts commit 5bfbde351aabe2096de99ee959a8a2e50edcf84c. See https://github.com/openbmc/openbmc/issues/2740 for details. This commit causes ipmid to fail to load. From github user artemsen: > ipmid[995]: ERROR opening [/usr/lib/host-ipmid/libapphandler.so.0]: > /usr/lib/host-ipmid/libapphandler.so.0: undefined symbol: _ZTINSt13__future_base12_Result_baseE As reported by Lei: > This issue prevent all P8 systems (with ast2400) booting with latest > OpenBMC, because ipmid fails to load libapphandler.so and cause watchdog > will not be kicked and always timeout on power on. As suggested by James Feist: > We probably should just revert the changes until we update to yocto > 2.4 which has the newer version of GCC with the fix for armv5 futures > as the backport seemed to fail. Change-Id: I0059cc3f939c1e3e5f88531fcb14ae3faa451387 Tested: Booted a ast2400 machine and checked journal Signed-off-by: Joel Stanley <joel@jms.id.au>
Diffstat (limited to 'types.hpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud