Age | Commit message (Collapse) | Author | Files | Lines |
|
Matt Spinler (1):
control: Add a parameter store to Manager
Matthew Barth (4):
presence: Install JSON config files from repo
monitor: Install JSON config files from repo
control: Install JSON config files from repo
json: Remove extraneous try/catch
Change-Id: I475ce2394edf8a6a2f35f3bbe9e9e52fc82533b8
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Remove the unneeded obmc packages and add specific ones that are used.
Signed-off-by: Vivekanand Veeracholan <vveerach@google.com>
Change-Id: I80472124ec1af684ebbd502219c8ae6d9f8fcee9
|
|
Commit aff0243 added seccomp to the systemd PACKAGECONFIG. The
libseccomp recipe requires seccomp be a DISTRO_FEATURE.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Iee1d5e9b2efe8284454c0b5125d9de7b43c1bdb0
|
|
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Ia66f5b4a95f54f7e537d0f0fba1ac70009002de5
|
|
Update the build recipes for the GXP binary bootblock that runs before U-Boot.
The code has been restructured such that the DL360POC machine is the exception,
so this includes the overrides for the DL360POC.
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I507a6e32c7c72613dbd1239824f528f0f60d1f6f
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I4b2c1b2a5b02a241b106e6eb1dd377708c1c337e
|
|
This change required as a part of privilege separation work:
https://github.com/openbmc/openbmc/issues/3383
Seccomp support enables sandboxing in systemd:
https://www.freedesktop.org/software/systemd/man/systemd.exec.html#Sandboxing
Signed-off-by: Anton D. Kachalov <gmouse@google.com>
Change-Id: If7ff257103c4aa40dae5f64256bf60d8a30fbf59
|
|
The BMC on the AMD Ethanol CRB uses entity-manager for sensor
configuration. Therefore IPMI configuration YAML file should
use DBus paths to sensors based on the names from the entity-manager
JSON files.
Currently 'ethanolx-chassis.json' exports CPU fans on a DBus as
"P0_Fan"/"P1_Fan". Use these names to correctly populate CPU fans
to the IPMI.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I0425e42771e1bfb36ad067dfcad5a23e5f180d67
|
|
AMD EthanolX CRB is a board with x86-64 CPU, which means it can support
both EFI and Legacy boot.
Add 'boot_type' PACKAGECONFIG option for the phosphor-settings-manager
package to support EFI/Legacy selector in the BMC boot override feature.
This setting is designed for the possibility of setting boot override
as:
- "PC compatible" boot (legacy)
- Extensible Firmware Interface Boot (EFI)
Change-Id: I173c5b439b929e80f3a106f5e7775862f889ee16
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
|
|
Populate ADC sensor data to the system. This change make ADC data
accessible over DBus, IPMI, Redfish and webui-vue.
The threshold values were calculated as 10% from the target values.
The "PowerState: On" entity-manager parameter on the "*_RUN" channels
is used to make thresholds active only when the board is powered on.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I5322e83fdbfa0815bed454ea81b83725a2221d2c
|
|
Populate voltage regulator sensors to the system. This change make
voltage regulator data accessible over DBus, IPMI, Redfish and
webui-vue.
AMD EthanolX CRB has 4 voltage regulators per each of its CPUs (P0/P1):
-ISL69147 - Px VDD core regulator
-ISL69144 - Px VDD SoC regulator
-ISL68127 - Px VDD Mem / VPP ABCD regulator
-ISL68127 - Px VDD Mem / VPP EFGH regulator
All of these voltage regulators are 1st generation multiphase devices.
They can be covered with a ISL68137 Linux driver initialized with a
"isl68137" parameter, which would bring the necessary "raa_dmpvr1_2rail"
initialization.
The threshold values were spoofed from the original voltage regulators
configuration in the AMD EthanolX CRB.
The "PowerState: On" entity-manager parameter is used to make thresholds
active only when the board is powered on.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I123db2e356f525e0d269aef780d34d218209592a
|
|
Populate SB-TSI CPU sensors to the system.
This change make SB-TSI CPU sensors accessible over DBus, IPMI,
Redfish and webui-vue.
The entity-manager configuration make use of "PowerState: On"
parameter as SB-TSI sensors are active only with a powered on CPU.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I80390bb0baa291e7a9d5b49b2e9542cef719da69
|
|
On the AMD EthanolX CRB only few of the dbus-sensors apps are
relevant. The rest of them aren't needed and will only waste
cpu time and produce ambiguous fail messages at the initilization
stage.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I9ce01d93d79b40386a59757244e8b9b8a6008289
|
|
With the reshuffle that occurred in 38cfcc393d9e ("meta-aspeed:
u-boot-aspeed-sdk: Use provided signing key by default") we no-longer
need to specify these options in p10bmc.conf
Mistakenly, `SOCSEC_SIGN_ENABLE = "1"` was duplicated later in the file
by 699146128388 ("meta-ibm: p10bmc: Assert that we want the SPL signed
by socsec"). Removing the instance as done in this patch still leaves us
with the positive assertion that we want SPL signing enabled.
Change-Id: Iaa9cbe5b0ba4aaf69bb0fba1eb8f6bc62d085a33
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Building the SPL and "silently" leaving it unsigned gives us a build
that cannot be booted on systems that have secure-boot enabled.
Change-Id: Ie788a04ef35c7031897a2bfa7d348caa4292305d
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Include the socsec-sign class after the conditional assignments to
ensure the values we might assign are considered by the functions of
socsec-sign.
Without this, u-boot-aspeed-sdk do_deploy logs show:
```
DEBUG: Executing python function sstate_task_prefunc
DEBUG: Python function sstate_task_prefunc finished
DEBUG: Executing shell function do_deploy
Copying u-boot-nodtb binary...
Warning: Invalid socsec signing key - SPL verified boot won't be available
```
Adjusting the location of the include gives:
```
DEBUG: Executing python function sstate_task_prefunc
DEBUG: Python function sstate_task_prefunc finished
DEBUG: Executing shell function do_deploy
Copying u-boot-nodtb binary...
check header PASS
Found PEM header at position 381
check integrity PASS
```
Change-Id: I15cac4c315a6ceaeb69b0c02ba0b7d05e54f6e15
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Add DCMI sensor configuration for the Mt.Jade platform.
Tested:
1. root@mtjade:~# ipmitool dcmi sensors
Inlet: 2 temperature sensors found:
Record ID 0x00f3: PSU0_TEMP | 26 degrees C | ok
Record ID 0x00f4: PSU1_TEMP | 31 degrees C | ok
Baseboard: 6 temperature sensors found:
Record ID 0x0001: TS1_Temp | 31 degrees C | ok
Record ID 0x0002: TS2_Temp | 32 degrees C | ok
Record ID 0x0003: TS3_Temp | 31 degrees C | ok
Record ID 0x0004: TS4_Temp | 30 degrees C | ok
Record ID 0x0005: TS5_Temp | 35 degrees C | ok
Record ID 0x0006: TS6_Temp | 32 degrees C | ok
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Iff8a94e523346347b7e449522ab5a12b841aee9e
|
|
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I5cc4285e6a0459a8aab5bf8494c23d4235d43193
|
|
1. Update both primary and backup SCP EEPROMS when updating the BIOS
Modify the
2. Switch the SCP mux correctly on EVT and DVT hw
Signed-off-by: XP Chen <xiao-peng.chen@fii-na.com>
Change-Id: Idd07f4b57bfd2eaa13795f60b653915f1cf7c161
|
|
Add PREFERRED_PROVIDER_virtual/bmc-update in kudo.conf to fix
bmc_update build conflict with gbmc's bmc_update.
Signed-off-by: Mustafa Shehabi <mustafa.shehabi@fii-na.com>
Change-Id: Ideb5cbde0f4c94c7197984c1641223da1583111d
|
|
Arun P. Mohanan (1):
Add MTM BMC Feature Control IPMI command
Jason M. Bills (1):
Add PCIe scan option to BMC Feature Control command
P Dheeraj Srujan Kumar (1):
Fix Klocwork Issue: Uninitialized variable
Change-Id: Ic86a40a5f6e924624b7dcf02b599377d45300dc8
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Change-Id: I2784b1dcd95f5c5ee8bca14f89c509e7d70b4011
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
|
|
This tool allows for controlling fan speeds, viewing targets and
feedback values, and diagnostic info about fans and fan-control services.
Commands:
- status: print the RPM or PWM targets and view RPM feedback values for
each fan/rotor. Also shows the health of the fan-control service and
BMC power states.
- set <target> : sets the targets for all fans (if no additional args)
or for a list of one-or-more specific fans.
- get : gets the targets and prints rotor speeds for all fans
- reload: forces phosphor-fan-control to reload its configuration files
by sending the service an interrupt signal.
- resume: shortcut to restart phosphor-fan-control if it had been
stopped for maintenance.
Signed-off-by: Mike Capps <mikepcapps@gmail.com>
Change-Id: Iaa7e447d2d5aa977482663ef6dd45aadffc58f55
|
|
Patrick Williams (7):
lg2: introduce motivation and API
lg2: initial implementation of C++20 structured logging
lg2: support sdbusplus enum conversion
lg2: support exception conversion
lg2: compile time header format checking
lg2: compile time checking for reserved header names
log_manager: switch to lg2
Change-Id: I810fb1af065b2066a95b0d2446e48fc7b1d429ea
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
obmc-ikvm runs with two seprated thread to handle connection from user
(bmcweb::kvm_websocket) and video device (libvncserver), however both
these two thread access to rfb*() API. It leads to client socket double
free issue.
cl->sock has been set to RFB_INVALID_SOCKET(-1) with first clientClose
call.
And the second call to clientClose uses -1 in FD_CLR() generates buffer
overflow.
```
obmc-ikvm[672]: 24/08/2021 08:45:11 rfbClientConnectionGone: c1=75900748
obmc-ikvm[672]: 24/08/2021 08:45:11 rfbClientConnectionGone: c1=75900748
obmc-ikvm[672]: 24/08/2021 08:45:11 rfbSendUpdateBuf: write: Broken pipe
obmc-ikvm[672]: *** buffer overflow detected ***: terminated
systemd[1]: start-ipkvm.service: Main process exited, code=dumped,
status=6/ABRT
systemd[1]: start-ipkvm.service: Failed with result 'core-dump'.
systemd[1]: start-ipkvm.service: Scheduled restart job, restart counter
is at 1.
systemd[1]: Stopped OpenBMC ipKVM daemon.
```
Signed-off-by: Troy Lee <troy_lee@aspeedtech.com>
Change-Id: I4bbe69c6d7006e44c5f4a532fb54f9ae9c9cd52b
|
|
Since 29086950, phosphor-net-ipmid has updated the SOL parameters
by obtaining the attribute values of the
xyz.openbmc_project.Ipmi.SOL interface.
It is necessary to enable SOL by default on Mt.Jade with correct
parameters.
Tested:
1. ipmitool -I lanplus -H x -U x -P x -C 17 raw sol info
2. ipmitool -I lanplus -H x -U x -P x -C 17 sol activate
ipmitool -I lanplus -H x -U x -P x -C 17 sol deactivate
Use the above commands to successfully activate and deactivate SOL
3. Activate IPMI SOL and boot Host to Linux 5 times without
disconnected.
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: I8e4d0e06eaa9c8995cde27f17f0d0d274b553f0d
|
|
Fix missing Yocto syntax change in phosphor-hwmon append file which make
sensor configured not work correctly.
Tested:
1. Run "ipmitool sdr list" and check all sensors reported correctly
Signed-off-by: Thang Q. Nguyen <thang@os.amperecomputing.com>
Change-Id: Ia4653180ac1a66dac13ee6d7edf5c34a106967e9
|
|
Upstream supports zstd compression now as an alternative to zlib or xz.
zstd is only slightly larger than xz but is significantly faster. This
makes it a better candidate for the journal. Enable it in systemd
instead of xz.
Add an exemption for witherspoon to continue using xz instead. Having
both zstd and xz support built into the image puts us over the flash
limit and we currently need xz for phosphor-debug-collector.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I6fb55b96776aeeea1c544743b08bdbbc2853e7b7
|
|
Zane Shelley (2):
Moved Callout class logic to Resolution classes
Simplified Guard class and supporting functions
Change-Id: Iaeb06fb1cfdb3ba6127f6e45905b25e6e37bb88d
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Shawn McCarney (2):
regulators: Add phase fault detection to schema
regulators: Add device_id to validation tool
Change-Id: I8b282ecfde994a917c05a1d8447c4f644a11b04a
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Shantappa Teekappanavar (1):
watchdog: Create PEL when AutoReboot is false and watchdog times out
Change-Id: If2349e70cbe42036fb653df0153ac5d889f43252
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Matt Spinler (3):
PEL: Remove 'no_vpd_for_fru' maintenance procedure
PEL: Change BMCSP01 maint procedure to BMC0001
Stop emitting Entry propChanged before ifacesAdded
Change-Id: Ia9f4d338478e4449a123d1d94f7057b5849dfe79
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Matthew Barth (3):
presence: Add machine JSON config files
monitor: Add machine JSON config files
control: Add machine JSON config files
Change-Id: I66417400bf4b4547d6cc54f04b416714ddbcf913
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Ed Tanous (1):
Fix warning with clang
Joseph Reynolds (1):
Fix search for OEM privileges
Change-Id: Ia64a514f00cb79155a26923cc8c8fabf76a479ce
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Willy Tu (1):
watchdog: Add Watchdog Timeout signal
Change-Id: I51624d08c020cea1ba77f041c01da0287b0ae1a3
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Brad Bishop (1):
treewide: remove 'using namespace' from headers
George Liu (1):
libpldm: fix entity_association_tree_copy method
Isaac Salem (1):
pldmbios: Add BIOS attributes hb_key_clear_request
Sampa Misra (1):
pldmd: use async instead of event loop at start
Sridevi Ramesh (1):
BIOS: Add 5 new bios attributes in enum_attrs.json
Change-Id: If8110b2f79321986bdfb79c0566434e6317457a5
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Enable redfish response to contain EthernetInterface SpeedMbps
/redfish/v1/Managers/bmc/EthernetInterfaces/eth[x]
Signed-off-by: XP Chen <xiao-peng.chen@fii-na.com>
Change-Id: I0d4179935b37c8d7bd5d0c51b122851d4f81a99d
|
|
Testing:
Built image for p10bmc platform, installed on a test system,
and verified netipmid was started on both eth0 and eth1
interfaces. Also, verified that ipmitool commands work as
expected for IP addresses configured on eth0 and eth1 interfaces
Signed-off-by: Shantappa Teekappanavar <sbteeks@yahoo.com>
Change-Id: Ie8399ba1219dac2f9c4ac15b7dfcf7e746750f0d
|
|
Changes to support Yocto syntax changes and latest 'honister' release
Signed-off-by: Mike Garrett <mike.garrett@hpe.com>
Change-Id: I9cc4eb78b90d9b73bcd0440e6f6f6334fe459481
|
|
The meta-security layer requires the DISTRO_FEATURE 'security' set
otherwise it gives a warning:
WARNING: You have included the meta-security layer, but 'security'
has not been enabled in your DISTRO_FEATURES. Some bbappend files
and preferred version setting may not take effect. See the
meta-security README for details on enabling security support.
This DISTRO_FEATURE doesn't really seem to do anything except enable
an additional include file in the linux-yocto recipe (which itself
then checks other features). It seems entirely safe for us to enable
this feature everywhere to avoid the warning.
$ git grep -A4 "DISTRO_FEATURES" | grep "'security'"
meta-security/README:to have 'security' in DISTRO_FEATURES to have effect.
meta-security/README: 'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files
meta-security/classes/sanity-meta-security.bbclass: if 'security' not in e.data.getVar('DISTRO_FEATURES').split() and not skip_check:
meta-security/classes/sanity-meta-security.bbclass:'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files \
meta-security/recipes-kernel/linux/linux-yocto_5.%.bbappend:require ${@bb.utils.contains('DISTRO_FEATURES', 'security', '${BPN}_security.inc', '', d)}
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ife1549783b356f87f429466f260f34b9a41d002c
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I478258cbf55a66b5c93eca7a09b264e3a2325ca2
|
|
Some I2C addresses can't be probed for a FRU. For example,
device at this address can be already connected to a driver
or the I2C bus is not scannable like the APML bus.
In this case 'fru-device' app will be producing messages
like this:
'fru-device[XXX]: device at bus X address XX busy'
To avoid these unnecessary log messages add I2C bus blacklist
json file for the 'fru-device' app.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Change-Id: I0618943c9362117d9931defa1e17bcd999621197
|
|
Enable installing fan control's JSON config files into the image from
the repository by machine name.
Change-Id: I2d35783df55c5a154539972d70fb9564b5cb4038
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
Enable installing fan monitor's JSON config files into the image from
the repository by machine name.
Change-Id: I14f584c8aa24e18e5ffe9ab3eda8579edb9583c0
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
Add setting the `MACHINE` name to the recipe and pass it to the fan
presence package to use in installing its JSON config files for that
machine into the image from the repository.
Change-Id: Ib782d9013c5ad0cfc1b283563ef07dc812fb12f2
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
We've typically kept these LAYERSERIES_COMPAT to 2 releases: the current
and the upcoming. Remove 'gatesgarth' is it is now 2 releases back.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5e812a94fed1738898af75c0fdee81996a5bbf20
|
|
Patrick Williams (2):
log_manager: use sdbusplus enum directly
README: switch build to meson
Change-Id: Ibb0ad79b8ad2e948bf731c8fe336ca91a90f47d0
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Bruce Mitchell (1):
Corrects bug in using boost::container erase()
Change-Id: I7054ab9df096aa592aa0eaeb1c42a96b7803c976
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Lukasz Kazmierczak (1):
Modify severity text for discrete Triggers
Change-Id: Ie7ff5ae079c7830fdf7d8dd009175bc02b8ee189
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
Mansi Joshi (1):
[dimm] Added DDR5 and LPDDR5 Device Type support
Change-Id: Idd081770e98856ed653e4f86e905860cf1d17569
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|