| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
It's been found that the processors are generating more preheat than
anticipated and the rainier 4u systems currently being built may not
have the baffles available to be installed. Increasing the poweron fan
speed to overcome this preheat affect to the PCIE area so PCIE cards do
not overtemp.
Change-Id: I03414fc4cc9cd3aa8d248c4b1408bab658978f48
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
The 1s4u hardware is configured with fans at 0,1,2, and 4 locations.
Tested:
- Verified that we can now power on a 1s4u machine with this change plus
a kernel device tree change to move to fan 4.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ic1415da9ab900c0e553600df89a1e26893f8b0bd
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Tested: Built rainier and verified the fan files were installed, ex:
obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-fan-presence/control/ibm,rainier-4u/zones.json
obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-fan-presence/control/ibm,rainier-2u/zones.json
obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-fan-presence/control/ibm,everest/zones.json
Change-Id: I10edb9e30716cffa3f510fe94822eadb08326912
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The 1s4u is just like the 2s4u except it has two less fans.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I56ed73ee573df250072bd014a0e4c8a4072e974e
|
|
The 1s4u is just like the 2s4u except it has two less fans.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I35333e49c883fb9ac8c84223545fe3b903a66d7d
|
|
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>
|
|
It was found that the fan control services were constantly getting
restarted due to not failing within the previous start limits. After
experimenting with different combinations of limits, using the default
values for StartLimitBurst and StartLimitIntervalSec is sufficient.
Tested:
Changed limits, powered on, watched service fails in journal until
fan watchdog monitor started
Resolves: https://github.com/openbmc/phosphor-fan-presence/issues/23
(From meta-ibm rev: b8a65368cb39d6d82c4b025b25fdbe868dbbfe89)
Change-Id: Ibcb35028e8dbc67d7df70dfeee25d098e6041fe8
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Remove the use of `witherspoon` in the names of the recipe, config
files, and services of the fan watchdog. This is in prep to use this
same fan watchdog on other machines within meta-ibm that have different
configurations.
Tested:
Witherspoon image matches image prior to change
Flash image to Witherspoon and force watchdog to trip
(From meta-ibm rev: 80f819efec08f7cc7de6988f64c0c77e20990f05)
Change-Id: I77295974397cd4903cd1a723b9ef97ee744d2557
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The metadata common to all IBM systems is confusingly split between
meta-ibm and meta-witherspoon. Move everything to meta-ibm.
The meta-ibm README is re-written to more accurately reflect the scope
of the layer.
Allow the configuration samples (bblayers.conf.sample,
local.conf.sample) to be sourced from either meta-ibm or
meta-witherspoon until such a time that any workflows and tooling have
had the opportunity to move to meta-ibm.
(From meta-ibm rev: 6e05ef2e90b214eaf4e43ee7027bbbb1d8d09442)
Change-Id: I3ec890d5300f9649c974ea6b9dca93a2e8a889ab
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
