| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Mihawk's GPU temperature exceeds 92 degrees Celcius should be shutsown
to avoid GPU damage.
Tested:
GPU temperature exceeds 92 degrees Celcius system will shutdown.
(From meta-ibm rev: 623eb4dda626dd3dfb3f14d9afa4e10c86d3bbca)
Change-Id: Id085afa2a7d7a29a42cd5d508a03fb64dd53c108
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
1. According to the thermal team test results, the cpu core should be
shutdown when it exceeds 95 degrees Celcius.
2.mihawk's ambient temperature exceeds 45 degrees Celcius should be
shutsown to avoid system damage.
Tested:
Cpu core exceeds 95 degrees Celcius or ambient exceeds 45 degrees
Celcius system will shutdown.
(From meta-ibm rev: 7f94a4b3a7c3d7346ae4b1bade6287ea1a70c41a)
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Change-Id: I303a5047dc0b29e46829f4b838eaa6f151b13735
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
IBMBASE is only used for pointing at licenses...point at the
licenses in oe-core in meta/files/common-licenses instead. to match the
defacto convention used in other oe layers like meta-openembedded.
(From meta-ibm rev: cbbb0e5b4e44d831fce5daafd13272d401440f40)
Change-Id: Ib214f92b2c384e3eb2a1f53ecf4b21034438d001
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Most of mihawk's sensors are different from witherspoon, so I temporarily
added the mihawk part and did not change the witherspoon.
Add mihawk version of fan control and d-bus monitor.
Mihawk does not have a water cooled mode, so another independent folder is added.
Tested: 1.Shut down the system if more than three cores
have a temperature greater than 100 degrees Celcius.
2.Fan control support cpu core, dimm, Onboard.
3.Confirm that sensor is able to return normally via REST.
(From meta-ibm rev: 949f91431bba2f0139cc823d674a741f9590c885)
Signed-off-by: Ben Pai <Ben_Pai@wistron.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: Icc401f32c67b622f0f1448e1166112e02c135a8f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Use an override in bbappends in meta-witherspoon as described and
recommended in the "following best practices when creating layers"
section of the the Yocto development tasks manual.
ibm-ac-server represents common machine configuration shared by all of
IBMs "Accelerated Compute" class of servers. Apply it wherever any
variables are un-bounded by any override.
This enables more flexible use of meta-witherspoon in build
configurations, and easy addition of machines to the layer.
(From meta-ibm rev: bb0e1d0699a4b9905c053c94af7d882cd71779fc)
Change-Id: I82f7338b0d7a64b5e7a67e19bcdff07f48a332d4
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
To better organize the policies(and the configurations) that are used by
phosphor-dbus-monitor, all of them are now located under the `dbus`
directory. This moves toward a more understandable and centralized
scheme for the recipe(s) used to configure and build
phosphor-dbus-monitor.
(From meta-ibm rev: 4b80c4f2b3a62d8084fc43f95177e299d53387ae)
Change-Id: Ie99c5dbe55c2295fc5cd7b5e7722cc10064e1b71
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Swift has two power supplies, same as Witherspoon, therefore will use
the same power supply policy configuration.
Swift and Witherspoon will also share the event policy configuration for
OCC throttling.
The thermal policy configuration will be shared between Swift and
Witherspoon, but may change for air cooled Swift to not also shutdown at
3 or more cores over 115C.
The fan policy configurations will be different for Swift, therefore
they will be separate. At this time, there are some areas unknown on how
fan presence and functional states will be handled for both air and
water cooled Swift machines, so these are configured to be the same.
Tested:
Built witherspoon phosphor-dbus-monitor resulting in no image change
Built swift phosphor-dbus-monitor resulting in correct policies
(From meta-ibm rev: fd06a2cbfd5f6e43aba4887ae1398984410d52cc)
Change-Id: I1125f00ecd51c23aac2da4cd2a47432ac3bc2de7
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Policy configurations will be loaded by machine within the system meta
layer (in this case meta-witherspoon). This allows different machines to
have different policies and/or different policy configurations.
The .bbappend can be used to alter which policies are used on a machine.
The thought here being that most machines within the same system meta
layer would use the same policies. However these policies would likely
have different configurations, this is where each machine would have its
own policy configuration which would be loaded per the policy recipe.
Tested:
Built witherspoon phosphor-dbus-monitor resulting in no image change
Built swift phosphor-dbus-monitor where no polices exist now
(From meta-ibm rev: 6275fda44b3fd1a039f6aef55e920b542b8135ef)
Change-Id: I9c86e9eb15756236e1e802f18345fb8c7ab5400a
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Remove `witherspoon` from recipe file names, which includes the
directory containing the policy configuration files.
Tested:
Built witherspoon phosphor-dbus-monitor resulting in no image change
(From meta-ibm rev: c8562bc0066f8657d2fbb5c1962826e686a7f652)
Change-Id: I7d7d247865bc2f8432e01a46caa43cc8770ae100
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The native recipes are no longer used after the switch to non-native
recipes in the meta-phosphor layer.
Tested:
Built witherspoon phosphor-dbus-monitor resulting in no image change
Built swift phosphor-dbus-monitor resulting in no image change
(From meta-ibm rev: c50b717ce219342c4730d3f029712d5a7d10da07)
Change-Id: I0026c06592921d0f1633bd3a24e6cd0530d3cc19
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Create the phosphor-dbus-monitor non-native recipes to allow the switch
from native to non-native within the meta-ibm layer. Upon switching to
the non-native recipe in meta-phosphor, these non-native recipes will
then replace the native recipes in providing the policy configuration
files(yaml).
Tested:
Built witherspoon phosphor-dbus-monitor resulting in no image change
(From meta-ibm rev: 0ca32c6b6d0566a29756ecd05ffb748764296a27)
Change-Id: Idf800c0d537b6051c3bc263908d9bbb2bc6ab2de
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
A number of bbappend wildcards matched more than what was desired.
Reduce the scope accordingly.
phosphor-dbus-monitor-config-native%.bbappend ->
phosphor-dbus-monitor-config-native.bbappend
phosphor-ipmi-fru-read-bmc-inventory%.bbappend ->
phosphor-ipmi-fru-read-bmc-inventory-native.bbappend
phosphor-ipmi-fru-read-bmc-inventory%/bmc-fru-config.yaml ->
phosphor-ipmi-fru-read-bmc-inventory-native/bmc-fru-config.yaml
phosphor-ipmi-fru-read-not-sent-by-host-inventory%.bbappend ->
phosphor-ipmi-fru-read-not-sent-by-host-inventory-native.bbappend
obmc-op-control-power%.bbappend ->
obmc-op-control-power_%.bbappend
(From meta-ibm rev: c828be02d177ece43006329ee99ca4d2ef733c58)
Tested: bitbake-layers show-appends still shows the witherspoon
bbappends
Change-Id: I5133261a33c4101d6d526355817a0adbac0ce0d9
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Drop symlink and rename bbappend for phosphor-dbus-monitor.
(From meta-ibm rev: b21533febcb99b14fc9d7c3817921bc4c0a3900c)
Change-Id: I85f2c2fd0b889de1ee77f5edd095b8a10e95aee9
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Set the wildcard for version for phosphor-dbus-monitor.bbappend
(From meta-ibm rev: dade96460c2ea6a377a95206ccb83ed2d955953e)
Change-Id: Ibf7d4999f74c7c997a68614037f5e06dc5ff1d2d
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This is a revert of eff3d02a180ef60102f1f25d765b2ddf72831be3
A direct revert is not possible due to our subtree refactoring
Prioritizing one application over another seems to cause more
problems then it solves. In this case it appears that mapper
can starve other process's in which mapper depends on responding.
So that dependent process times out, restarts, which then causes
the whole cycle to start over.
Hoping this is the fix to openbmc/openbmc#3369 but will require
some testing.
Tested: George was kind enough to run this through some BMC reboot
tests and a regression bucket. openbmc/openbmc#3369 did not recreate
but not willing to declare success yet with that bug.
(From meta-ibm rev: 9effdef83644fff90a2bcb6f4d6fb97ac28fcb28)
Change-Id: I9af8ab369966a69c09d807d888b0bf5a0f0b3e07
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
The new subtree model brings the subtrees up from the openbmc-machines
layer.
Change-Id: I58a03ae1be374bc79ae1438e65e888375d12d0c0
Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
