| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Requirements have arisen for OpenBMC firmware to run
certain services only during fresh power on operations.
To achieve that, break the obmc-host-start action target into
two targets. The existing obmc-host-start target will now
call the new obmc-host-startmin target. The startmin target
will be the minimum services required to start the host.
The obmc-host-start target is where services that should
only be called during a fresh power on can be placed.
The initial use case for this is the obmc-host-reboot target.
It will call this new obmc-host-startmin target to do the bare
minimum on a reboot operation.
This then allows the use case for OpenBMC to only reset the host
reboot count on a fresh power on operation. A new service will
be added to the obmc-host-start target to do this. If a reboot
operation is issued, or a host watchdog is triggered to cause a
reboot, this service would not be started, ensuring the reboot
count is properly decremented.
Tested: Verified on/off/reboot and ran CT regression suite.
https://gerrit.openbmc-project.xyz/#/c/9821/ is required
for reboots to work properly.
Change-Id: I86df03e6d671178c1525f852e196c4102bb73cb6
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
|
|
|
|
|
| |
Added "mutability" flag to indicate if a sensor is READ/WRITE/RW.
Change-Id: I69d3683bacae80b96cf57ce1b7b5d875c425d3a8
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This service file needs to be started only for
witherspoon.
This is used to stop the ethernet port failover
on the system.
Resolves openbmc/openbmc#2931
Change-Id: I0f144942df1d77de4d990a4aad8d9764d8455251
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
|
|
|
|
|
|
|
| |
Added "mutability" flag to indicate if a sensor is READ/WRITE/RW.
Change-Id: Ifd13c0573abfbee23f99d11e0362cdaf9bea1eb5
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
|
|
|
|
|
|
|
| |
Added "mutability" flag to indicate if a sensor is READ/WRITE/RW.
Change-Id: I4bfcde7f09183cf3a4df94d1a6f7bd5d90502275
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
|
|
|
|
|
|
|
| |
Added "mutability" flag to indicate if a sensor is READ/WRITE/RW.
Change-Id: If52ae660431a40e256380271f8b7fc22dc63549e
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Added a POWER8 Barreleye README with a line about POWER8 Barreleye
no longer being a supported machine. This can up updated in the
future if POWER8 Barreleye becomes supported again. Calling this
"POWER8 Barreleye" to differentiate from the POWER
Barreleye/Zaius system.
Change-Id: Ia5738cc7a34f96657307322cd924ad71d9e3cc40
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
|
|
|
|
|
|
| |
FFS is the BMC Flash File Structure which is currently used on
OpenPOWER machines for the flash layout.
Change-Id: I2549828a0f0ea070c77316a3f7fd56ec9fbe5bf8
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
| |
Added a Firestone README with a line about Firestone no longer
being a supported machine. This can up updated in the future
if Firestone becomes supported again.
Change-Id: I9b845b56e57333323a119250a775a378d9a10955
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
|
|
|
|
|
|
|
| |
Added a Garrison README with a line about Garrison no longer
being a supported machine. This can up updated in the future
if Garrison becomes supported again.
Change-Id: Ib3040500ed8b634b1fb0f5ce1b3156f7885d49aa
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In phosphor-hwmon, the config "--enable-negative-errno-on-fail" is
introduced for sensors that should return errno instead of failing and
exiting.
Enable this config for Romulus so the fan sensors are working, otherwise
hwmon will fail and exit when fans are not working.
Tested: Verify that the fan_tach sensors return -ETIMEOUT when host is
powered off and do not exit with failure.
Change-Id: I0d52a2b1a7fb4bf9fc542de6a88823b36bd2bc48
Signed-off-by: Lei YU <mine260309@gmail.com>
|
|
|
|
|
| |
Change-Id: I0bb8820aacd3fe879daeccfe61899216ab558d71
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
|
|
|
| |
Change-Id: Ifb3e2c178829397812e72be68e42f364dad2bd76
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
|
|
|
| |
Change-Id: I277ff0cfd9c60f28a924419d3cb46a0c86e05c1a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
|
|
|
|
|
|
| |
After updated to kernel dev-4.13, Romulus needs to pick latest
phosphor-hwmon to make hwmon work.
Change-Id: I7a911ad6d4dc464471e75f69963bad7e419fe198
Signed-off-by: Lei YU <mine260309@gmail.com>
|
|
|
|
|
| |
Change-Id: I5066b97f4c19b606d95cb8594eb4f3c02446b86a
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
IPMI command get device id supports auxiliary firmware version field
in the response. This field is 4 bytes and the first 2 bytes would
contain the count from the version tag in BCD format, the next 2 bytes
would represent the release version in BCD format. This change can
support the VERSION_ID format of IBM enterprise build and a build
from the master.
Resolves openbmc/openbmc#2972
Change-Id: I4f4e23a3be687b814cef51b1b96c7b97778bcb16
Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
|
|
|
|
|
| |
Change-Id: I3d19c686e14eb8c00ea963dbd90ee68c58ef319c
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We have 236 commits, 127 files changed, 17766 insertions(+), 2128
deletions(-). Some of these are backports from upstream. This list
does not include patches from the 4.13 stable releases, but we do
include those in the dev-4.13 branch.
1 Alexey Khoroshilov
34 Andrew Jeffery
1 Arnd Bergmann
1 Benjamin Herrenschmidt
1 Bhumika Goyal
1 Brad Bishop
1 Brendan Higgins
11 Christopher Bostic
1 Cyril Bur
14 Cédric Le Goater
49 Edward A. James
3 Gavin Shan
1 Guenter Roeck
8 Ivan Mikhaylov
1 Jacek Anaszewski
1 James Feist
7 Jeremy Kerr
72 Joel Stanley
2 Julia Lawall
1 Ken Chen
6 Lei YU
3 Milton Miller
1 Mykola Kostenok
1 Patrick Venture
2 Philipp Zabel
1 Rick Altherr
11 Samuel Mendoza-Jonas
2 Wei Yongjun
1 Xo Wang
1 Yong Li
Note that the 4.13 branch is EOL'd by the Linux community, and as such
should not be used for any products beyond development.
React to removal of occ hwmon instances from device trees with a
new startup/shutdown mechanism for phosphor-hwmon.
To fix this, a helper script will be used to start the service that
will pass the service the device tree name if it is present, or the
udev device path if it isn't. This script will still run from the
udev rule as before, but it will stop and start the service itself
without using the SYSTEMD_WANTS attribute.
As the path to the hwmon environment file matches the service
template argument, the paths for the OCC .conf files need to change
to match the device path instead of the previous device tree path.
Note that the pure device path would have the hwmon instance number
in it, but since that can't be known ahead of time it is stripped
off by the script that starts the service.
In addition, the pure device path for the OCCs contain several
':'s, meaning the associated environment files would also need to.
However, Yocto/Bitbake cannot handle a ':' in a file path, so they
are converted to '--'s by the script that starts the service and
phosphor-hwmon will convert them back internally when it starts.
The service file also needed some changes now that the service
lifetime is no longer controlled by systemd via SYSTEMD_WANTS.
This script will be called by a udev rule to start and
stop phosphor-hwmon when the hwmon device driver is started
and stopped.
It is passed both the device path and the OF_FULLNAME device
tree attribute. If OF_FULLNAME is present, it will start the
service with that as its template argument, otherwise it will
use the device path. This is to handle devices that aren't in
the device tree so they won't have OF_FULLNAME.
If a '/hwmon/hwmonN' is in the path it is removed, as this path
is also used as a path to an environment file and so must be
known ahead of time, which the hwmon instance N is not.
If there is a ':' in the path name, it is converted to a '--'.
Yocto/Bitbake cannot handle a ':' in file paths.
Resolves openbmc/openbmc#2953
Change-Id: I815be4d6d9e1cbea8428bb1bb8c332776ee71ece
Signed-off-by: Joel Stanley <joel@jms.id.au>
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Missing the ${D} on the install command - this still
managed to work on the older versions of yocto but
not with the latest one.
Also removed the PROVIDES=<recipe-name> line since
it's redundant.
Change-Id: I83127f0c457ec31bd99311371ec76abaf6fbc76a
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
|
|
|
|
|
|
|
| |
Adding power supply to BMC accessible FRUs.
Partially Resolves openbmc/openbmc#2984
Change-Id: Ib4af12f281f433ecac727324ec75e95fd62b8714
Signed-off-by: Nagaraju Goruganti <ngorugan@in.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added temperature sensors to input config YAML to auto generate output
YAML entries by parsing the MRW
Removed temperature sensors from the handcoded sensor YAML file
Resolves openbmc/openbmc#2942
Resolves openbmc/openbmc#2982
Change-Id: I7ac43bdf51e37c78b66c57bbe0cba9cbef2c5e2e
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. The config follows Witherspoon's and remove water-cool/gpu/pcie
related configs.
2. Uses FanPwm interface instead of FanSpeed.
3. Removed zone_condition related config which is optional. Romulus is
always air cooled.
4. Updated to use groups for events.
Tested: Verified that fan control automatically adjust fan speeds based
on temperatures.
Change-Id: I386c7e921557ef53b445cafe504d2927a76e8e38
Signed-off-by: Lei YU <mine260309@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
There were a number of places that inherited this class but did not
use it. A number of classes that did use it did not inherit it.
This was possible because the class was pulled in by the distro
configuration but that has been removed here as well.
Tested: Built and verified a witherspoon image
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I73511cdcc609875b4fe016967c1b84c5200fb703
|
|
|
|
|
| |
Change-Id: I49cf198df342873cad4ce6fa720edab1b120ed21
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the BMC sends a system power cap to the host, the host
validates it is in a certain range or it will reject it. So,
the BMC also checks the range before sending it at all.
This range comes out of the MRW (machine readable workbook)
XML, and is stored as output power. The user, however,
inputs the power cap value as input power, and so the range
the BMC code checks it against must also be in input power.
To support this, the script that pulls the power cap min
and max values out of the MRW for use in settings validation
will now convert those output power values into input power
by applying the power supply derating factor.
Resolves openbmc/openbmc#2944
Tested: Check that the power cap range that the settings manager
uses is now the input power versions.
Change-Id: Id5c5851d081ad706fda73054b49e67a93d57f76e
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The openpower-occ-control code needs to know the power
supply derating factor, but will default to a value if
one isn't supplied externally in do_configure.
Since other will also need to use that same value, use
a common variable for it defined in openpower.inc, and
now pass it into the configure step.
This derating factor is an OpenPower concept used by the
Power processor's OCC thermal control subsystem.
Tested: Check that the derating factor variable in config.h
in the openenpower-occ-control repo follows the
variable in openpower.inc.
Change-Id: I259b6086ebe70b2ac6eccdd244e43a7d36a28a77
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update to list groups per event along with not requiring the zone
conditions be defined for an event that should be generated for all.
Tested:
Generated code contains events in correct conditions
Single group event generation remains unchanged
Two groups within event included in same generated event
Resolves openbmc/openbmc#2630
Change-Id: I35502f7fa361c93f367f940c260a160742f160b1
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
| |
All existing functions have been moved to phosphor-state-manager
repository
Resolves openbmc/openbmc#1666
Change-Id: Iaec1e6b647d12ae31b633e9a84d3b6e2a8eca370
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This config file would be used to create the events when
configured property gets changed.
This config file would be used by the phosphor-event-manager
process.
Resolves openbmc/openbmc#2399
Change-Id: Ib933d720cd81313caf025c35074304f55fac401d
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The openpower layer supports a usage pattern of building non
openpower systems with the openpower layer included in the layer
configuration (introduced with 008b81bb).
As a part of 008b81bb a number of distro and machine features
were added. As with MRW and UBI before it, these features
are distro policy and not machine features. As such remove the
machine features.
Additionally converge the three feature variants down to a single
openpower feature since there aren't any in-tree systems that don't
enable all three.
Add a distro override and fix up combined feature checks to use
this override instead for improved readability.
Add a new distro configuration that enables these features and
point all Openpower sample local.conf files to this new distro
config.
Tested: Built and validated Witherspoon, Palmetto images
Change-Id: Ifa3df61fbe1803f00c38956c265604ba91d7d127
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As with MRW the use of the UBI image scheme is distro policy.
Convert the existing machine feature to a distro feature.
Enable the new distro feature on the systems that use
it(Witherspoon).
Add a distro override and fix-up MF checks to use this override
instead for improved readability.
Change-Id: I57f3bc244523eff5bc043caff8365e334d98cb30
Tested: Built a witherspoon image and validate manifest
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As with MRW the use of the UBI image scheme is distro policy.
Convert the existing machine feature to a distro feature.
Enable the new distro feature on the systems that use
it(Witherspoon).
Add a distro override and fix-up MF checks to use this override
instead for improved readability.
Tested: Built a Witherspoon image and validated image
Change-Id: I8ab03115bbfc2ecc77cff5c9eb8628903ae88051
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that obmc-mrw is no longer a machine feature we can organize
a bit and enable MRW providers off to the side with a disto override,
de-cluttering wherever non-MRW defaults are specified.
No functional impact but slightly easier for humans to parse.
Change-Id: If2731206b94e16e0b0132a385756eb11178118f2
Tested: Built a Witherspoon image and validated manifest
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using MRW or not is distro policy. As such remove the obmc-mrw
machine feature.
Do not enable the remaining obmc-mrw distro feature in the base
phosphor distro configuration.
Create new distro configs for the systems that use MRW today
(i.e. Witherspoon) that enables the obmc-mrw distro feature and point
the local.conf.sample at the new distro configuration.
Change-Id: If4cedc745b3ee942518fbfd4d5cf2cd5b60f346d
Tested: Built a Witherspoon image and validate the manifest
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add MRW distro policy includes to prepare for removing the
obmc-mrw feature from the default distro policy. Custom distros
can enable MRW by including the MRW include(s) from their distro
configuration.
The content is a little light at the moment but it is anticipated
it will grow in subsequent patches.
Tested: No functional changes
Change-Id: I9120662618b45f0b73902edc666c7684b499a40c
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
| |
These _appends can potentially crowd their neighboring entries.
Change-Id: I1dae77f9a17744110175916935c01773708652b0
Tested: Built a witherspoon image
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Enable fan monitor;
2. Add FanPwm interface;
3. Set the factor, offset for calculation from pwm to rpm
Tested: Verifid fan monitor works fine;
Manually change pwm, fan monitor will set fan non-functional
after a while; change pwm back, it will set fan functional
again, as expected.
Change-Id: Ic56cbe291959368218b60c4a5b8e305f39ff7edb
Signed-off-by: Lei YU <mine260309@gmail.com>
|
|
|
|
|
| |
Change-Id: I0064c7475ed7f6b1d6509ab76d0f01683f9c7889
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The MAX31785revA specification does not match how it functions.
The MAX31785revA's functionality reports the rotor feedback speeds in a
slow/fast relationship instead of rotor positions, therefore the fan*_0
object will always represent the slowest rotor. In combination with how
the MAX31785revA latches its TACHSEL = 0 during a speed transition, it
made it difficult to fault isolate the rear rotor of a fan.
Using a combination of the fan monitor trust groups on all fan rotors
and enabling a delay timer to determine when a fan rotor becomes
functional, fan monitor is able to correctly reflect each fan rotor and
fan enclosure's functional state in inventory.
Fan faults are unable to be monitored on all fans when transitioning to
a target speed.
Tested:
Each fan rotor's functional state is updated when blocked
Correct amount of time to mark a fan nonfunctional is still honored
A fan is functional after remaining in spec for 5 seconds
Resolves openbmc/openbmc#2798
Change-Id: I834d63f6082eae4cb03ec501f0fb8272a9f5b673
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
| |
This tells phosphor-hwmon to create FanPwm interface for the fan
sensors.
Tested: Verified it is able to set Target to change the fan pwm.
Change-Id: I79c4cb8fe00812659a2c536d9d2e328b5438e0c6
Signed-off-by: Lei YU <mine260309@gmail.com>
|
|
|
|
|
|
|
|
| |
This revision adds the FanPwm interface support which is used by Romulus
as well.
Change-Id: I44c7ba66028eb54630268019acc78a9e3720e621
Signed-off-by: Lei YU <mine260309@gmail.com>
|
|
|
|
|
| |
Change-Id: I1e9e01dd769c29a13b078d84a10792401b2f32c9
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The default size of the UBI read-write volume is currently set to 4MB.
There are no plans to store more than one BMC rootfs image on the chip
so in a 32MB flash chip, accounting for the current rootfs image size
of ~15MB with plans to grow to ~20MB with the addition of redfish and
other packages, it is safe to increase the read-write volume size to
6MB since the current size is already almost completely taken up if
there are multiple error logs / dumps on the system.
In addition, make the size configurable from a recipe so that the
size can be changed in a per-system basis. And during code update,
check the current size and update it if it's different, this allows
systems to be able to be resized to a new size by performing factory
reset after a code update that sets the new size.
Tested:
- Booted on QEMU and verified non-ubi system (romulus) retains the
current 4MB read-write volume, and ubi system (witherspoon) has a
6MB volume.
- Code updated to an image that has these changes and verified the
rwfs_size env variable changes to 6MB, and that a subsequent factory
reset rebuilds the volume with size 6MB.
Change-Id: I995eb560c1bd87ee95712c731e3d6e55bc0b2735
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The handcoded harware sensor yaml file is merged with the final
sensor yaml file.
phosphor-ipmi-sensor-inventory native recipe finds all the
yaml files with extension ".hardcoded.yaml" and merges them
to the final sensor yaml file
Resolves openbmc/openbmc#2613
Change-Id: I3e25f1312a813fcba0070a3e778915f52edba7aa
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
In migrating to support better fan failure/missing shutdown scenarios,
currently defined shutdown scenarios should monitor the functional
states of the fan enclosures and do a soft poweroff.
A system hard poweroff will occur for the following condition:
- More than two fan rotors are nonfunctional
Change-Id: Ie5c769f6b4f272f4ff39c7f3ca036db275723997
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
An increase to the fan watchdog timeout was done to mediate a BMC
performmance issue, which has now been resolved, so reducing the fan
watchdog timeout. The timeout should be set to 5 seconds (instead of
originally 3 seconds) to functionally align with the 5 second timer that
fan control uses in adjusting fan speeds.
The fan watchdog timeout increase was done under:
https://gerrit.openbmc-project.xyz/#/c/8398/
The performance issue with the OCC patches:
http://patchwork.ozlabs.org/project/openbmc/list/
(Series = Locking fixes for FSI, SBEFIFO, OCC)
Tested:
The fan-watchdog.conf file in BMC image contains 5 second timeout
Change-Id: I1f99cf33ce3f17b291bf0997f792e2409ec5fb2b
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
|
|
|
|
|
|
|
| |
xyz.openbmc_project.Settings has replaced this function
Resolves openbmc/openbmc#2339
Change-Id: Ifec6a2fda088c4631e3835d3276a54e09b5d7147
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make these changes in the phosphor-dbus-monitor rules that
run when 3 processor cores reach 115C, resulting in a system
shutdown:
* Create the same CriticalHigh error, but now store the sensor
paths and values of the cores that went over 115 in the metadata.
* Remove the callback that makes journal entries, as the above
change will now log which sensors/values went too high in the
error log metadata which also shows up in the journal anyway.
* Make this condition be a oneshot, meaning it will only do the
callbacks once as long as 3 processors are over threshold, not
on every properties changed call by any processor.
Resolves openbmc/openbmc#2560
Change-Id: Iaa5207a80ca251c927ecb96b98c41adcb173175e
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
|
|
|
| |
Change-Id: I74beb8b664bf16dfa94a316f8405a3a808f8be2b
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|