Age | Commit message (Collapse) | Author | Files | Lines |
|
Per association document[1], add/update the association between
PowerSupply and Chassis.
[1] https://github.com/openbmc/phosphor-dbus-interfaces/commit/11efbb3c856af9d760e2d27ff276090d7b3510d5
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ia7e40b67c13f2900a4d91d7f911f47c15b12b6c5
|
|
Since the accuracy of power supply input power sensors is 1% on IBM's
p10bmc system, add `ACCURACY=1` to the power supply configuration of
p10bmc.
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: If143a61e44936fbd758d556575c250bc6ea501b2
|
|
A fork of it is maintained but its upstream layer has largely been
unmaintained.
No future products are planned to be based on this layer.
Mihawk is similar to Witherspoon.
Signed-off-by: Myung Bae <myungbae@us.ibm.com>
Change-Id: I82f7d777b78cd126237d51e42f1e11abdf80ae68
|
|
The content in this repository has been moved to
phosphor-dbus-interfaces, and ibm-dbus-interfaces has been deprecated.
Remove the recipe.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I36edf4743ed6a79c610a78eab84926de1d681818
|
|
All of these abstractions have exactly one implementation. Remove the
indirection to improve at a glance comprehension.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I5d701aff6d0876fa3b2d16c841cbdcb0433b221f
|
|
Big cleanups to the phosphor-mapper/phosphor-objmgr recipe.
- Remove all "mapper-config-native" constructs as the underlying
repository has no such support.
- Remove all mapper-related bbclasses as they are no longer relevant.
- Remove environment support in service file as the mapper executable
no longer supports any arguments.
- Greatly simplify the 'libmapper' packaging to avoid stray python
in the recipe.
- Update all recipes to use `DEPENDS += "libmapper"` where appropriate
for clarity if they use libmapper.
- Rename the recipe from phosphor-mapper to phosphor-objmgr to match
the repository name, which allows simpler devtool invocations.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5a64e2feddd1a7919813e007411f9c28b6c9a330
|
|
Witherspoon is getting short on flash space, remove rsync as it's not
required in the image.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I40260b5b0f246db5bbc07a41457b0dee2d412efe
|
|
* Adds callouts for the TMP435s on the cable cards plus a few other
devices that were missing.
* Handles devices behind muxes by using the BMC's I2C alias bus number.
* A few other miscellaneous fixes.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Iae4f862ec70891c6ccba463d7faaa7a183b99cc0
|
|
Running out of space on witherspoon, so removing some ibm functionality.
The ibm-logging package is already removed from witherspoon-tacoma.
Tested: The obmc-phosphor-image-witherspoon.squashfs-xz image file size
was reduced from 20807680 to 20692992.
Change-Id: Ia94e7145da785f444ed919b3811e0b454c0eba82
Signed-off-by: Adriana Kobylak <anoo@linux.ibm.com>
|
|
Added do_install in base recipe for phosphor-health-monitor to
copy the json file from WORKDIR to target for monitoring the CPU
and Memory usage of BMC. Therefore, this can be removed in each
bbappend files.
Tested: Tested in Facebook YosemiteV2 platform.
Signed-off-by: Jayashree Dhanapal <jayashree-d@hcl.com>
Change-Id: I78eed7efb3e0be81a952c4bc3c3ae64579a48f7d
|
|
This is a dummy recipe which points to the existing pldm
repository but enables only building the libpldm shared library.
This recipe would point to the libpldm.git once the migration
is complete.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I1aef3702b5b05f389c6a24e752e44daff57afd6e
|
|
The latest pldm code removed the phyla nvram reset services as they are
No longer controlled via BMC, rather they are controlled by the ibm
hypervisor using a bios attribute.
pldm bump contains the following commits :
Jayashankar Padath (1):
oem-ibm: Remove extra bytes in resource dump request
Manojkiran Eda (3):
oem_ibm: Move the NVRAM files to the hostfw directory
oem_ibm : Add HRESET state setid & various states
oem_ibm: Add new file type for Running lids
Pavithra Barithaya (1):
PLDM:OEM Pass service authorization credentials to PHYP
Change-Id: I91ada72493f6d934cdb52e23e88783bcaae853e5
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Added p10bmc specific dev_id.json file to support IPMI IANA number
Testing:
Used curl command to verify IANA number
$ ipmitool -I lanplus -C 17 -p 623 -U user -P password -H host raw 0x06
0x01
00 80 0f 32 02 8d 41 a7 00 4f 42 00 00 00 00
Signed-off-by: Shantappa Teekappanavar <shantappa.teekappanavar@ibm.com>
Change-Id: I6ca8f343c06aac2303137aa5d78145b59d7099ce
|
|
```
WARNING: EXTRA_OEMESON:append:p10bmc += is not a recommended operator combination, please replace it.
WARNING: EXTRA_OEMESON:append:witherspoon-tacoma += is not a recommended operator combination, please replace it.
```
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5dc503b322d6cb90feb6d6261802fd50ebca31b2
|
|
IBM systems utilize /tmp and /var for a variety of purposes so setup the
health monitor to look at the remaining space in these file systems. No
action at this time other then a log in the journal to provide a clue
when looking at an issue.
Tested:
- Filled up /tmp and verified this log:
“Aug 19 19:59:43 p10bmc health-monitor[326]: ASSERT: sensor Storage_TMP is above the upper threshold critical high”
- Removed big file from /tmp and verified this log:
"Aug 19 20:01:34 p10bmc health-monitor[326]: DEASSERT: sensor Storage_TMP is under the upper threshold critical high”
Signed-off-by: NodeMan97 <corey.hardesty@icloud.com>
Change-Id: I8a7921dffa6b756a4ab19a0e807e558ccd35f996
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The p10bmc machines require the phal and op-fsi features to be enabled
to function properly.
Tested:
- Confirmed both features enabled on p10bmc machine
- Confirmed only op-fsi was enabled on witherspoon
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Id01cae6246204a025f4401d0d2c26ccda78d7d77
|
|
The phosphor-fan-presence repository added meson support, so start using
it.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: If850d3d379ad82dc8f9691efd7a0561f350543dc
|
|
Adding telemetry bbappend to customize telemetry meson options
for IBM. IBM has different needs than upstream for telemetry capacity
in terms of numbers of sensors readings and rate of requests.
bbappend file allows IBM to stay up to date with upstream Telemetry
while maintain custom build options more suited to IBM's usecases.
Increase meson option for total maximum Metrics/MetricProperties
limit from 200 to 300. For IBM management agent use cases (HMC), the max
number of Metrics needs to greater than 200.
Also for IBM management agent use cases, telemetry reports need a higher
append limit for metric readings. 32768 was determined as
1) a power of 2,
2) higher than HMC's current usage,
3) Ability to collect one hour of data for 250 sensors reading
once every 30 seconds ==> a general guess as to maximum readings
needed in one report.
Testing for maximum metrics increase:
- Monitored CPU usage of bmcweb for both rainier and
everest systems. bmcweb usage spiked for around 2 seconds with 300
MetricProperty MRD.
- MRD was periodic on 15 interval with 300 MetricProperties averaged
over 30 seconds on everest system with 360 sensors. Max bmcweb usage
was 9% for brief instant when MRD post call is made.
Testing for appendLimit increase:
- Set AppendLimit up to 11000 with 150 sensors on 400+ sensor system.
- Monitored 'top' CPU usage for telemetry binary and bmcweb binary
which never ran above 5%. AppendLimit generated new metric entries
for the report.
- Retrieve report did seem to take a little longer as report grew but
not significantly.
- Tested various other lower limits and sensors
Signed-off-by: Ali Ahmed <ama213000@gmail.com>
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
Change-Id: I418c3e90c565770cd59b02c294754ff98df29a55
|
|
The bmcweb bummp adding this meson option merged so this can go.
IBM does not use phosphor-pid-control instead using phosphor-fan-presence
and such.
This Redfish OEM fan data includes PATCHing. Turn this PATCHing off and
the whole Manager OEM Fan data. This has been done downstream already.
We have also observed 500 errors with getting the thermalMode.
"Jan 24 16:34:57 rain534 bmcweb[435]: (2022-01-24 16:34:57) [ERROR
"managers.hpp":1196] GetPIDValues: Can't get thermalModeIface
/xyz/openbmc_project/control/thermal/0"
Tested: No longer see this InternalErrors. Been running with this
downstream.
Tested on a Tacoma.
Before on a PATCH:
curl -k -X PATCH https://$bmc/redfish/v1/Managers/bmc -d '{"Oem":{"OpenBmc":{"Fan":{"Profile":"Acoustic"}}}}'
{
"error": {
"@Message.ExtendedInfo": [
{
"@odata.type": "#Message.v1_1_1.Message",
"Message": "The request failed due to an internal service...
With this change and the bmcweb change (instead see a PropertyUnknown)
curl -k -X PATCH https://$bmc/redfish/v1/Managers/bmc -d '{"Oem":{"OpenBmc":{"Fan":{"Profile" : "Acoustic"} }}}'
{
"error": {
"@Message.ExtendedInfo": [
{
"@odata.type": "#Message.v1_1_1.Message",
"Message": "The property %1 is not in the list of valid properties for the resource.",
"MessageArgs": [
"Oem"
],
"MessageId": "Base.1.13.0.PropertyUnknown",
...
Change-Id: Ic988e2949ad65b31eb0b9bc6ecbdceb997d8cdda
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
Note: for witherspoon systems these options are still enabled
Tested:
1) Build works for both p10bmc and tacoma
2) Web sockets did not appear and Redfish output was as desired
Signed-off-by: Ali Ahmed <ama213000@gmail.com>
Change-Id: I0aa710433455b4ca5f17012ecd867846d87a3cfb
|
|
Yocto append syntax should use assignment only and not `+=`.
Adjust this to fix the warning:
```
WARNING: ... :append:p10bmc += is not a recommended operator
combination, please replace it.
```
Fixes 6b7c28775d91c65816b1716edefe4e3299e1aa50.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I90ca66a4651b843e3fe96c13ba0242f7b6fca58d
|
|
These are some defaults IBM has been carrying downstream. Send upstream
since they are in the meta-ibm layer.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I239f0cbe29a118f51143974fc9bfaeaeffe80070
|
|
The power supply INPUT_HISTORY is only supported on certain power
supplies. The power supplies that ship with Rainier 2S2U, Rainier 4U,
and Everest support the INPUT_HISTORY.
The MEX I/O drawer power supplies do not support INPUT_HISTORY.
Use associations from Rainier/Everest power supply inventory entries to
the input history aggregation interfaces to facilitate Redfish filtering
of PowerSupplyMetrics for input history.
Change-Id: I9afb2e57fefbf0cc10378bffe2efe4f4548920ca
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
|
|
Patrick Williams (1):
MAINTAINERS: remove file
Change-Id: I28fe4fffae8f0f8fe459b995cad6e404684095d8
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
phosphor-defaults.inc now automatically inherits extrausers and
configures the default root/0penBmc account, so individual platforms no
longer need to specify either explicitly.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ic2b725f0eaadfafef67069449497e57438fa0fba
|
|
Change the power-on dependency of the fan watch and fan watchdog reset
services to a wants instead of requires so the system isn't powered off
if they were to fail with power on.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I603747083567c1b3335c640b70da97ed7fac5332
|
|
For the moment, phosphor-webui is deprecated and unmaintained. The
replacement for it is webui-vue, which already has feature parity, and
many more features than its predecessor. Several calls have been made
asking if there is anyone still using phosphor-webui and would like to
maintain it into the future, but no such volunteer has stepped up.
Moving to webui-vue is the recommended option these days, and this
patchset is done under the assumption that these platforms would
actually like to move off the deprecated UI, and just don't have patches
to that effect. For the machine maintainers reading this, if you would
like to stay on phosphor-webui, please start that discussion here about
who would like to maintain it.
This commit ports the last few platforms over to webui-vue.
Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I9c74442b850aceca130545f37d5bc694a4f4424d
|
|
Default was initially set to represent seconds. The interface
documentation says that the value is representative of microseconds
,as well as, the corresponding code in phosphor-state-manager.
Change-Id: I183c5a248748589e172df58d07f2b2c2ed0f554c
Signed-off-by: Corey Hardesty <corey.hardesty@icloud.com>
|
|
Fan/NIC sensor values crossed thresholds
Added support to trigger hard shutdown alarms and power off the
slots of the platform if the Fan/NIC sensors values getting low
compared to threshold values.
Added platform specific service file and script to take
platorm specific actions.
TESTED : Verified all the slots getting powered Off when fan/nic
sensor
values crossed threshold values.
Signed-off-by: Kumar Thangavel <thangavel.k@hcl.com>
Change-Id: I6deb6707e574a375fac8f2379f47661a5a0ed332
|
|
Patrick Williams (2):
OWNERS: switch 'matches' to 'matchers'
sdbusplus: use shorter type aliases
Change-Id: I9e015a77580779f881057fe6969f6608f2a374c3
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Jiaqing Zhao (1):
Network: Remove deprecated properties in SystemConfiguration
Remove deprecated properties from meta-ibm.
Change-Id: I99464a4737edaa177f51344701e5c578c106c2bd
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
IBM systems should default to "Restore" for RestorePolicy. This will
ensure a system is automatically restored to the last state prior to the
power loss.
Tested:
- Built p10bmc image and verified generated source file had correct
default in it.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I2bf890b22545665097c678ca52a8b3cd77e9f5b3
|
|
Commit 7298b24 introduced the concept of a phosphor-settings file that
supported multiple hosts. Adapt the meta-ibm override of host settings
to utilize this new concept.
Tested:
- Verified expected PowerCap settings were in generated
settings_manager.hpp file
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Iacccb71c09970d55cfc44deecb40e15782e98c1a
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Id772552ca99651c47778ee2c04ba7f5ce187ec0b
|
|
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I4e9748641b861f194c66a8fd168901e73c09a51f
|
|
New yocto has gotten more strict (and found some bugs in our recipes)
that require correct FILESEXTRAPATHS and correct machine installs.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I5511d543be0d2d17eba88ca63afa5372b8fda3a4
|
|
New yocto has gotten more strict and requires the specific paths be set
for machines.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: If7fb3410c2c513b355260ed28869822741b9d344
|
|
This change will disable the IPMI network interface by default on the
first boot of a p10bmc system after a factory reset. After the first
boot the service is prevented from running again and from there on
adheres to the customers settings.
It is necessary that IPMI network services are started for a brief
moment in time to ensure they show up in the systemd service list.
This is important to ensure that the service-config-manager, which is
responsible for enabling/disabling these services can properly locate
them in the systemd service list.
Tested:
- Issued 5 mini-factory resets to mimic a fresh system boot
Verified service-config-manager identified both IPMI service and
socket files for eth0 and eth1
Verified IPMI was disabled by default
Verified could enable IPMI via the web UI and could issue IPMI
commands using ipmitool with a user that was in the IPMI group
Verified that once IPMI was enabled, it stayed enabled through BMC
reboots
Verified when IPMI was disabled via the GUI, it stayed disabled
through BMC reboots
Signed-off-by: Corey Hardesty <corey.hardesty@icloud.com>
Change-Id: Idad03366c1eb11cbfd7f4ad700976c177eb0121f
|
|
Harvey.Wu (2):
dbus-sdr: fix SEL record Generator ID to fit SPEC
dbus-sdr: fix the vector size in sdrWriteTable and sdrStatsTable
Jian Zhang (1):
Add data types to Value to extend setDbusProperty
Vernon Mauery (1):
fix header install
Willy Tu (4):
cleanup: Remove all warning errors for the Meson build support
build: Add meson build for phosphor-host-ipmi
build: move all shared_library/module to library with version suffix
build: Remove dynamicsensor library if it is not enabled
Change-Id: I92503c6625d1ec2bf88c0a28afac9b4eeb8fbd75
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Willy Tu <wltu@google.com>
|
|
This commits provides an option to override
the softoff timeout value from 120 minutes to
45 minutes.
Signed-off-by: Sagar Srinivas <sagar.srinivas@ibm.com>
Change-Id: I2c425a97179d425b3bc9d5e59a431f046456e1d9
|
|
Matt Spinler (1):
Fix typo
Change-Id: I1b1b75dd92fa3bcba7126f4ba9f11c6787b201e4
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Don't use /usr/bin/env, it's an antipattern.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: If388f5427bb2ca45718d0ca99452bf3f147861dd
|
|
/usr/bin/env is now an antipattern.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I7e8488b984db0258f68107b23a0e3a7ed149f763
|
|
It's time to require this for p10 based machines now
Tested:
- Confirmed by default it is now "Required"
root@p10bmc:~# pldmtool bios GetBIOSAttributeCurrentValueByHandle -a hb_tpm_required
{
"CurrentValue": "Required"
}
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I0959ffad3d4a38b542087be4a6ca6949ff1b4356
|
|
The dbus sink actions will cause phosphor-dump-manager to take a full
BMC dump if the debug action is received on the trigger source.
Change-Id: If57612a75ca7f68ed2636c9b23dc04972d99626d
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
For the same reason as supply-monitor (a dependency on org.open_power
dbus interfaces).
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: Ibcf52fc180da744cced04d4720036d8bc84bf89c
|
|
This is the recommended keyword to use and it appears to fix a subtle
bug of some sort where the new secure-check is overriding other
features.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ic724ec7611741d6286926e96cb0b61530cdcf638
|
|
IBM manufacturing has requested this new feature be enabled on p10bmc
machines.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I47fcc24667dfcccc4314548b29772227280eef4c
|
|
Patrick Williams (1):
build: enable C++20
Change-Id: Ib2bc73d1f7227f9a8494598be123eac66c2f8ace
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
phosphor-dbus-monitor still uses autoconf and has a hard dependency on
phosphor-snmp, causing phosphor-snmp to be brought in on systems that
have no interest in using SNMP. The vast majority of systems do not
supply any config for phosphor-dbus-monitor, so the usage of it does not
seem wide enough to enable the IMAGE_FEATURE by default.
- Remove 'obmc-dbus-monitor' from IMAGE_FEATURE by default.
- Clean up all systems that manually remove the dbus-monitor feature or
package.
- Explicitly add the 'obmc-dbus-monitor' to the following systems:
- meta-ibm: all
- meta-inspur: fp5280g2
- meta-quanta: s6q
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Iad6c4104466e21d1b9843dac964a634019eb6935
|