Age | Commit message (Collapse) | Author | Files | Lines |
|
Both rainier and witherspoon-tacoma systems support the mpreboot
feature.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ieeb4724a5cf5678ba0f6ab950b5403db5aebcd88
|
|
The memory preserving reboot is a feature utilized on IBM systems which
allows a system to be rebooted with its memory preserved. This is
utilized in situations where the host firmware has crashed and put the
processor in an unusable state. The processors are put back in a good
state by rebooting the system. Memory is preserved though so host
firmware can capture the relevant data from memory needed to debug the
cause of the failure.
This feature is implemented across a few different repositories within
OpenBMC so lets create a distro feature to enable it across all of the
software stacks.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ia16626ba6e46aa8de642abef677735ed957f9f9e
|
|
The ibmtpm2tss tools are required to use the Nuvoton NPCT750A TPM
from userland.
The ibmtpm2tss package also required OpenSSL camellia support, so
remove the override disabling that for those two machines.
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: Ifc0afc58f4a31ea4b6d1750d470738d0d0e82754
|
|
There are some machines (Witherspoon-Tacoma and Rainier) that
have a TPM device, which will be used eventually. We need
access to the recipes in this layer.
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: I3b10ee4d39a69e651a790ae3238e39c45e21ce72
|
|
- This commit would package the biosconfig-manager for both
tacoma & rainier machines.
Tested By :
- With the changes booted the tacoma machine & observed that the
biosconfig-manager services are up & runnning
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I90542368a70284c97e1f33d29770c751a61631ca
|
|
The squashfs tools are used by PLDM during inband update.
Reference: https://gerrit.openbmc-project.xyz/c/openbmc/pldm/+/37510
Tested: Verified that the rootfs/usr/sbin/mksquashfs existed.
Change-Id: Id8d00765e72ce04bc8f039403a570aa7dca98b26
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Instead of using phosphor-dbus-monitor to create errors and handle power
offs for fan errors, use phosphor-fan-monitor instead, now that it has
the functionality. To do this, add the new rules to the fan monitor
config files, and remove the phosphor-dbus-monitor fan rules files.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ia03186132f04087be76d2fd43412c37698407f60
|
|
The VERSION_ID may not have a commit number for the cases a tag
is created, ex: 2.10.1. Since the code is expecting a commit
number of 1-4 digits, use a '0' if no commit number exists.
Tested: Created a tag 2.10.99 which sets VERSION_ID=2.10.99.
Without this change, build fails with:
"Exception: IndexError: list index out of range"
With this change there are no build errors.
Change-Id: I3b56ebc1844ec6748b92cca3484f9aa1f4d983f8
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
I've been utilizing my gerrit admin abilities to merge autobumps and
backup Brad in these meta layers. The OWNERS plugin disabled this
path for me. My intention is to keep with this same workflow. I'll merge
autobumps and backup Brad as needed.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ib248c6122644dbbd4b024ed07eb7259db85daf1e
|
|
(From meta-ibm rev: c203fa3d1ca3de7d61b3c06a22dbf4385202cc78)
Change-Id: Iab1adeab9ff493e05e26f31f72c9cb708f28e73e
Signed-off-by: Rashmica Gupta <rashmica.g@gmail.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Please see https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/39379
for details about why this is necessary.
(From meta-ibm rev: 501f9fd6b63c8b11c0ae0f6268a98c33b764caa0)
Signed-off-by: Ed Tanous <ed@tanous.net>
Change-Id: I05862abb52f7fac1bcf4fdd939a1101aa2431f9d
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The rule of thumb within OpenBMC is to utilize a wants relationship with
targets, especially the multi-user.target. This follows the general
design of always allowing the system to continue whenever possible.
For example I'm doing some bringup in simulation where these services
are not required, but their failure is impacting my ability to reach
a successful multi-user.target state which impacts other targets that
depend on it.
Tested:
- Verified multi-user.target completes successfully now on my bringup
system
(From meta-ibm rev: f2f6d38efdfa1a88a5f41b9871e0d3aa76f193d1)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I687fbbb7006a3d9b9abe1d308802914d64224410
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Everest has the max31785 at a different i2c address that is behind a
mux, so install its hwmon config at that associated location.
Tested:
Hwmon instance for the max31785 starts successfully on Everest
(From meta-ibm rev: cd84eb53a79edcabddd5e7720f9e0389f4e96151)
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Ide9ca8bd76d708ef9453dc7d02526dfbb1dd8a30
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Rainier does not need/want the old PSU monitor.
(From meta-ibm rev: eba91da180e9ec5b7260aebb87fb05ab1e48c930)
Change-Id: I6c9e58257cd7a8b3a675b69ae3d88603a8fb0e94
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Corrected the gpio pins and paths for detecting fans wired to a PCA9552
behind a mux according to the Everest schematics. Fan presence will fail
to access these gpios until the Everest dts is updated to expose them.
(From meta-ibm rev: 072949a9b84112572559baa76d12b9a7c77f8547)
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I9456ff8bd4298f3414f41180732e8e17b738acfa
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Temporarily remove detecting fan presence by gpio on Everest until the
gpios are added within the dts and accessible in userspace.
(From meta-ibm rev: 7c4944f2dfd2ce5ab811f7e07a5a4d8de5949ee4)
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: I62f80e494a9d0feffa45cc3a1e08f0a859fca35b
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Remove extraneous commas from the Everest fan monitor JSON config so it
can be loaded/parsed.
(From meta-ibm rev: 84d05fda258fbd02650d859f6fe9a77a6e5ef7a6)
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Ib0b044f8657593137d67cec036ab615e265398e3
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
openbmc master has exceeded the available flash space on witherspoon.
Remove LDAP so it fits again and we can continue to use witherspoon for
HW CI validation of openbmc master commits.
IBM has forked off its own openbmc repo for maintenance of customer
witherspoon systems. Therefore it is not necessary for openbmc
master to continue to support everything.
Tested:
- Verified generated image flashes on witherspoon and HW CI tests passed
- obmc-phosphor-image-witherspoon.squashfs-xz 19.27MB -> 18.53MB
(From meta-ibm rev: 6390f0999f00b1cdfe19daf2d7e8868c25808497)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I39b5d785919bdcd54b6bcf04217439050442f119
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The phosphor-debug-collector renamed "host-dump-offload-transport" build
option into "host-transport" to make generic for supporting other host
dump action (i.e create,delete) not only offload so, changed build option
here as well based on phosphor-debug-collector.
phosphor-debug-collector patch:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-debug-collector/+/38792
(From meta-ibm rev: eb951216a95e360431644dba46f04fc0541fb608)
Signed-off-by: Ramesh Iyyar <rameshi1@in.ibm.com>
Change-Id: I4466896b67cb7490b13e6c32113bb59651fbcdb3
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
led-set-all-groups-asserted.sh needs to be called with "false"
as part of below transitions to turn off all indicator LEDs
- BMC booting to standby and staying at standby
- BMC starting to power on
(From meta-ibm rev: e784b71c2d625b4507758df4bb5743fc678251f3)
Change-Id: If248220964c65e91e9382504b1a7095cc5cec26b
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Install all the fan application config files into a rainier image
(From meta-ibm rev: dd3117e5c3b6768ca6975b04ebc70f8e716529b2)
Change-Id: I51d017b3a6ad34595bc9dce0fd1693c0012fc52e
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This commit adds the fan control config files for the rainier type
machines. The recipe updates to install these files into a rainier image
will collectively be done after all fan application config files are
added.
(From meta-ibm rev: 5d8b514768c45eee76bd19bffc432dc5778ca075)
Change-Id: I5fa1f5cc879d7f3a951f7972ac391767de3647f3
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This commit adds the fan monitor config files for the rainier type
machines. The recipe updates to install these files into a rainier image
will collectively be done after all fan application config files are
added.
(From meta-ibm rev: b28c40c5cb1eeec7239f39cbf7bb0e901340b501)
Change-Id: I445d141de53577e0c151ece3e258752814a631b4
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This commit adds the fan presence config files for the rainier type
machines. The recipe updates to install these files into a rainier image
will collectively be done after all fan application config files are
added.
(From meta-ibm rev: f131f38e89da79848595670af0d150e01aaa664a)
Change-Id: I514589fcde2a7d500e272b7d45ac90961bb46368
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add the max31785 fan controller device to hwmon.
(From meta-ibm rev: 71404ba4966e32bb4ed9a120062d669ed642d851)
Change-Id: I4b2cd1c5379e76ccf40f52dc6ceca6a98f931f40
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This reverts commit 3a70e470e8ec8239e27db9b7361f568cebd5ef72.
The health monitor code has fixed openbmc/phosphor-health-monitor#1
so we can put this back in.
(From meta-ibm rev: fc48727d30a75aa9c12d0f49d8a4124202a995ff)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I3b5e1ca730af0a06c94291e84397e24d6b2bb83d
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The max31785-msl application is now a package within the phosphor-hwmon
recipe, so that package needs to be enabled and installed on
`ibm-ac-server` alias of machines which have a max31785 chip. These
machines require that the minimum ship level(msl) be verified on them
using this application.
Tested:
Built phosphor-hwmon package after enabling max31785-msl package
Verified application, config file, and service existed in image
(From meta-ibm rev: 33184059fa07ca12e11fb9e8dde2d6a31e1f029e)
Change-Id: I186fb6ca930e4107738d4ed90d31b6233be3d6f2
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Use the latest bumped upstream commit of the phosphor-fan-presence repo.
(From meta-ibm rev: a5824115356901e363c55f0d013a9821a51eba1b)
Change-Id: Ib5f3e4718de3f288bf71321680d42234512d1be9
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The next release of Yocto is soon and most of the upstream
layers have switched support strings for it. Support layer
compat for gatesgarth (current) and dunfell (previous).
(From meta-ibm rev: 284e2ad06544f567582b2732a22e052190b5b95a)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ic1cb74ebd387715b08feccd8b94bfd0be7d35205
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The phosphor-health-monitor package added some code recently that only
supports a mtdblock based filesystem. This causes issues with the HW CI
machine, witherspoon, documented in openbmc/phosphor-health-monitor#1.
Time permitting, IBM should come back to the phosphor-health-monitor and
figure out if it makes sense within it's products. If it does, then the
appropriate bmc_health_config.json should be created for IBM systems.
(From meta-ibm rev: 3a70e470e8ec8239e27db9b7361f568cebd5ef72)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I02dff59cade863d287919a01d0b1f93f67661279
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This commit adds the system_dump_policy object to the
xyz.openbmc_project.Settings. This is used to enable or disable
the system dump. Default value is true
Tested by:
busctl tree xyz.openbmc_project.Settings
└─/xyz
└─/xyz/openbmc_project
├─/xyz/openbmc_project/dump
│ └─/xyz/openbmc_project/dump/system_dump_policy
busctl introspect xyz.openbmc_project.Settings /xyz/openbmc_project/dump/system_dump_policy
(From meta-ibm rev: ad88bbcbbd01d92773f61b1712f5e458f1b661bd)
Signed-off-by: Sunitha Harish <sunharis@in.ibm.com>
Change-Id: Ieae8a01a266ba8ff2d984b1a1b2ea9ada243d439
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Witherspoon should still use YAML based configs for fan control instead
of JSON. Once all of fan control's JSON support is available and
witherspoon's YAML fan configs are converted to JSON, this can be
removed to enable JSON.
*Temporarily pin to 8e1b382122fed73e788d44f3a67cecbfbcc6972e to pass CI
(From meta-ibm rev: 7ec9b860b5ea1d986702bb978b528ddcd28f2ce5)
Change-Id: Ic31f5ab915d5478b9a2027732bd3ffd44f50b02f
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The phosphor-virtual-sensor code recently started checking the values of
the upper/lower warning/critical thresholds for the virtual sensors and
prints to the journal if they are exceeded. If the threshold values to
use aren't specified in the JSON file, it will just set them to zero so
any nonzero sensor value will trigger the trace.
So, even though code will not use the threshold values for the virtual
ambient temperature sensor, put some into the JSON anyway that should
never be exceeded to avoid these traces. If the temperature does happen
to go outside the range of between 0 and 100, then seeing the trace may
be interesting anyway.
(From meta-ibm rev: 9fdb9598d0eee4d9820962320391bb9f7e4568ea)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I1c6c5f1faaaf58599a3840eed6ec4749a70a1364
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
No need to use _append and +=
(From meta-ibm rev: 72b20dddfcd790a0a0398ec4c16e76b54866b989)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ibcbd5c83a137799f4f80d017e19a8d9b9a9f681f
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Rainier is only using the hwmontempsensor dbus-sensors service for now,
so remove the other ones. Without this, 8 other services would be
running at BMC ready state.
(From meta-ibm rev: b51345ced440ca935f8678d8521a690301e63db5)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: If60d9a0ba585c029877c5fda77b5085cec394d04
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Ben Pai (1):
Add wistron oem command to switch 250 soc image
(From meta-ibm rev: 3aa9904064a954031fac32b462c26c0b6d541ef1)
Change-Id: I6cc97288c35a1ac1f97f55ad0fe179dce9636bb0
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Use the virtual-sensor application to put a virtual ambient temperature
sensor on D-Bus. Currently, it just mirrors the value of the TMP275
ambient temperature sensor, but in the future the output will be based
on all three temp sensors on the panel after the remaining two show up
on D-Bus.
(From meta-ibm rev: f43eab1e5637cf87a38ca2e9a6acc33e5db3a0c3)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I187d88c7e1245c7014aee8b9b6c0840daf1e622d
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Add dbus-sensors to the Rainier flash image. This repository holds a
suite of applications for managing various types of sensors. It uses
D-Bus interfaces provided by entity-manager to know which sensors to
monitor. Rainier will use it for at least some of the temperature
sensors.
(From meta-ibm rev: 29cc525d9cb736f4cfa0bc17bb45771fd812234e)
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I81f9311adb9d72de1b04f9aed0a2d9e778b3e03a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The AST2600 systems booted from NOR during bringup, but now that we have
eMMC support in u-boot they can run from eMMC.
(From meta-ibm rev: 46419c51c3bd3d43873ecbab7fbbb6f1d6c54de4)
Signed-off-by: Joel Stanley <joel@jms.id.au>
Change-Id: Idd2389ab62e1b7cc32639f5547f1f1098631654f
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The next release of Yocto is soon and most of the upstream
layers have switched support strings for it. Support layer
compat for gatesgarth (current) and dunsfell (previous).
(From meta-ibm rev: 00e954d3100bb932d154273376620b40d6b8cad3)
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iffd47517e7b9e85597fe97478375a48d0c2db927
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
As we add support for a new series, remove support for the oldest.
Little to no testing is done with older ones.
(From meta-ibm rev: 6255d23fd68023fdc838d0a2262b43883b86be58)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Id63754bdc8ec82628cad23427bfdadafca380c15
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This reverts commit 5ef58e42bd2c27605cd952bf590b2879759425d8.
There is a unknown issue with Tacoma hardware in which the CP0 reset
needs to happen within the power_control.exe. The theory is it is timing
related (i.e. the CP0 reset needs to occur extremely close to the power
being turned on). Given that Tacoma is a development system, time has not
been allotted to getting to the bottom of this.
It works fine on some systems, but fails catastrophically on others with
an assortment of power fault errors.
Due to this issue, we can not utilize the new kernel mechanism for
controlling CP0 on Tacomas.
(From meta-ibm rev: 4bc5a4720757e6aa8b349869adc2dceb53a8b9f1)
Change-Id: Ib0afbfc4386bf74ffa264c1e0ac3aaa04016a040
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Dbus sensor interface 'xyz.openbmc_project.Sensor.Value' migrated
from int to double. Therefore all old 'int64_t' types in
"*-ipmi-sensor*.yaml" files for this interface should be changed to
'double'.
(From meta-ibm rev: c769f790e14b9caa4fc842dc1e2035378de6ae60)
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: Id8e164203541550eb19301ca429702cbf7d4b2f8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
At a high level, the purpose of this feature was to utilize the BMC
hardware watchdogs to switch the BMC boot flash when certain errors were
hit which were preventing the BMC from booting.
At a high level, this worked but some critical issues were found with
this:
- No failure data is gathered to understand why the boot flash was
switched
- No event or error is logged to notify the user of the system that the
boot flash has switched
- At times, switching sides didn't help because the BMC network
information was not properly copied to the other boot flash which
caused even more confusion for the user
Give the above, this patch proposes a reset on this logic until we can
come back and address the above issues and get this working end to end.
(From meta-ibm rev: d5069cffe865ea104915d8e0fdbe8d7d145644fc)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8c8d2b30c80940f4674e6c6848bd22f759e943a5
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- This commit would enable the ibm-management-console compile-time
option for all the ibm machines.
(From meta-ibm rev: 9831b3a45141d4dc08b2624f07059299d65a9d7f)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I69abd87d28903d27d2390f20153d730f658f8068
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Remove executable permissions from the `70-max31785-hwmon.rules` file to
eliminate the systemd-udevd warning that its marked executable.
(From meta-ibm rev: 46984b5eda5c40e63cb9fab6aa5e667cec7f5b68)
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Change-Id: Ic7405ed73f2d7875c57696ae4e5b30e380502fd6
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
this commit is to enable hypervisor certficate manager feature
and install service for rainier and tacoma
(From meta-ibm rev: cf7a5811a21645a556b5e66433ce08ff67cf7cb2)
Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>
Change-Id: Ia38083851444134a55ff1b488f921b75cbd0d2e8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Enable OpenPower dumps on Tacoma and Rainier
(From meta-ibm rev: 0ce518f660df9490da3373dd64b580ea8672c93d)
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
Change-Id: Ic756ecbd793ca465ce3d6dc31ad93ac5170654d0
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Similar to commit 567a8d for witherspoon, this issue has now popped
up on Romulus hardware.
The concept of warm reboot (reboot the host without removing chassis
power) was added a while back as a part of clarifying support for
the Redfish ComputerSystem.Reset Action. It has since been found that
some IBM hardware, including Romulus, do not support warm reboots.
The issue is intermittent and depends on the reboot being requested
while the host is in the middle of some i2c transactions. If a warm
reboot occurs during this window, then on the subsequent boot the i2c
hardware will be in a bad state and the host firmware is unable to
recover it.
Given this issue, it has been requested that BMC software go back to
doing cold reboots (cycling power to the chassis during any reboot
request) on this hardware.
(From meta-ibm rev: 718f2b5405c2c1f000cc0ccbf2860a283997c08a)
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I31810e89977532d4368050871aba03d78deb9c59
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
- This commit would switch the bmcweb options to meson
(From meta-ibm rev: fea636a8486e20e8ccd865670f56d34c9700a043)
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Ieda83403ff381c616664170462915198fdf30507
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|