Age | Commit message (Collapse) | Author | Files | Lines |
|
The phosphor-gpio-presence application is no longer needed for power
supply presence detection after the updates to using libgpiod in the
phosphor-psu-monitor application.
Remove the systemd parts of the bbappend, and remove the obmc conf
files.
Signed-off-by: B. J. Wyman <bjwyman@gmail.com>
Change-Id: I18a7f36e21d18a22f7625aadc3229ce5439c8d6a
|
|
Change Ie1a7c389edb6b7a048836a49283ceb62de51bba5 will be transitioning
the 'Type' property in Inventory.Item.Chassis to an enumeration.
In order to avoid crashing in PIM we need these default values in the
starting YAML to be fully-qualified enumeration names that will match
the values which will start in Ie1a7c.
This code is safe to merge as is without any PDI or PIM changes. Prior
to the PDI change, we must make a change to PIM that allows conversion
automatic from string->enum, leveraging library interfaces available in
sdbusplus. These will be submitted independently.
I checked the codebase for usage of this string. It appears that the
value is currently, effectively, write-only. There is code in bmcweb
that fills in the equivalent Redfish value but currently just hard-codes
the string 'RackMount'.
Tested: Booted Witherspoon in a QEMU model with this change and proposed
changes to sdbusplus + PIM. PIM no longer coredumps with the PDI change
and yields an expected persistence file:
```
$ pwd
/var/lib/phosphor-inventory-manager/xyz/openbmc_project/inventory/system/chassis
$ cat xyz.openbmc_project.Inventory.Item.Chassis
{
"value0": {
"cereal_class_version": 2,
"Type": 3
}
}
```
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Icaf9447f31ccdd945cdf74b3e017682e4aed686f
|
|
Change-Id: Iac6362f744113d9a405e4a4ec30077e513dda2d3
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
As for Rainier and Everest, use KCS2 as the debug-trigger interface.
Change-Id: I2614ffc3d97164658f2ad4fbb916cbf44be152e1
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Currently required for the debug-trigger application.
Change-Id: I585ccc5591b3f66db41bfd9799df05cec902403d
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Replaces the obsolete MCTP LPC driver.
Change-Id: Ic5f7f6ec796bff8f0628d53e09a7437a74399ef4
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
This sensor on the Op_Panel, one of them being a SI7020 type sensor
which needed to be enabled.
Signed-off-by: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com>
Change-Id: Ib6a86a6fae52414ad9c6901e5f6f8aa8c8a383c3
|
|
Witherspoon uses a specialized phosphor-fan-control@.service file and
uses the phosphor-fan-control-init@.service file still to just set the
fans ready target. To correctly be included in the FILES directive,
these services need to be explicitly added on wiherspoon machines.
Change-Id: I76129a7833337aaf74fd83b0e28f3083f1a41b0a
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
- ddimm
- capi connector
- nvme
- pcie slot
- pcie cable card top and bottom enclosures
- base op panel
Signed-off-by: Lakshminarayana R. Kammath <lkammath@in.ibm.com>
Change-Id: I7de498f83ab3bace4ce39deb98c31c71c40f2dd4
|
|
MaxBootCycleCount is a dbus property that is used to indicate
the maximum number of boot cycles that the post-code-manager
daemon can store the progress codes for, before it starts
wrapping.
Unlike Intel postcodes, IBM progress codes are huge and it is
possible to get close to 230+ progress codes per boot cycle, so
tweaking this value to 5 boot cycles for IBM systems so that
we can get less number of log entries on a redfish GET request.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: Ida10e73992b01535d57c844d83366d786cd448e2
|
|
The Altitude measurement is from the computation of
the DPS310 pressure sensor with this
"Expression": "44330.0 * (1.0 - ((P0/101325.0) ^ (1/5.255)))"
Tested: busctl introspect xyz.openbmc_project.VirtualSensor \
/xyz/openbmc_project/sensors/altitude/Altitude returned
results consistent with location of the Rainier system.
Signed-off-by: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com>
Change-Id: I07b83dd6b8f4ccf0755ccbdc81c40976a3e571cd
|
|
Phosphor logging PEL infrastructure provide supports to
process SBE chip-op failures and creating PEL.
PEL creation required to process SBE provided FFDC packets.
This FFDC is initially created by SBE using FAPI based
infrastructure for the hardware procedure execution failures.
To extract this data to convert into PEL required format
requires additional processing. This processing required
PHAL(Power Hardware Abstraction layer) based back-end
support.
Added required packages support for PHAL feature enabled
systems.
Test: verified build.
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I5cf1a30514aa0a5bfdf2fe3a288dac9d5a0b5b47
|
|
OpenBMC requires additional capabilities for the
OpenPOWER systems such as
- A common mechanism to access and control the host
hardware from the BMC.
- A storage mechanism to store the data that can be
used for initialize, control and access the CEC
hardware.
- An infrastructure to initialize the hardware using
the hardware procedures provided by the hardware team.
- Common mechanism to handle the hardware failures for
the host hardware.
These above features are essential for the BMC to provide
better RAS capability and to support lab debug for the
enterprise class systems.
The phal(POWER Hardware Abstraction Layer) aims to provide
a common layout such that the OpenPOWER application can
use this infrastructure to boot, enable RAS features like dump,
diagnostics, and lab debug tooling purpose.
The phal is a combination of open source packages that are
tailored/customised to use in OpenBMC. For instance POWER
hardware access and control is managed through pdbg and
host hardware data modelling is done via devicetree.
phal is group of libraries running in BMC. These libraries
are used by OpenPOWER specific application for host hardware
interactions, Hostboot and SBE initialization, diagnostics
and debugging.
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I187d9582598743871279a1e407451f4cf4f72668
|
|
Install the udev files to cover the transition between drivers and
devices.
Change-Id: I87ffe3ae82bb7a073a8140adcb308b09fc43c9b9
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
libmctp provides the MCTP implementation for communication between the
host and the BMC.
Change-Id: I6ae5a23fbb34c27db16a152afefb79ca6a649759
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
These were separated in a strange fashion. Perhaps we should reorganise
the whole file in platform-specific sections.
Change-Id: I51b8bb20060447c6e88557824e9465b1713f082f
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Currently /proc/sysrq-trigger is the only supported backend for
debug-trigger. Once we have kdump support, we'll add a kexec backend and
drop the magic sysrq.
Change-Id: I07dfa50474d9f6333428b6fb38020c7b7fd0adec
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Change-Id: Ic1cde1cd67fa6f8f68df80a1f327ace64a39d72b
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
Change-Id: I4453f9b01f986a529c76710d665ab57639232b2d
Signed-off-by: Anton D. Kachalov <gmouse@google.com>
|
|
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>
|
|
p10bmc systems have their own checkstop monitor, provided by the
openpower-hw-diags package. Having both installed on p10bmc systems is
wasteful and has shown some intermittent issues (checkstop-monitor
service core dumping when checkstops occur).
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I118b359bf551e6502086800a9081ca8856ecf4ae
|
|
This is apparently not actually working anymore and is removed in the
next poky update.
Change-Id: Ia1c6a258d124a4a30a14fc42e8e0bba95e64faeb
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
The IBM host firmware team has requested an initial timeout of 10
minutes for the host watchdog. The goal is to bring this down once
bringup is complete.
When inband IPMI was used, there was a mechanism for the host to adjust
this timeout so the BMC firmware would set the initial 30 second timeout
and the host firmware would change it to 10 minutes once they started.
With PLDM there is no way for the host to adjust this timeout so we need
to start with the larger value.
Tested:
- Verified a p10bmc image had the new poweron file installed with 10
minute timeout.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: If94766d5f2d62271c4adf366631f0b31a75ef8d0
|
|
Signed-off-by: Chris Cain <cjcain@us.ibm.com>
Change-Id: I2ce6a862e0d16fe8a67c9dc12ceacbc01d3a0b1b
|
|
This commit adds associations for all the inventory that
gets represented as Assemblies in Redfish.
Change-Id: Id4e9e4ac870e5bed665462d161abde00c4b85554
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
The rainier machine has been replaced with the generic p10bmc.
Change-Id: Ia7b6e8b6ad569d6f607d4a38318704fb402f2a1f
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Use the 'insecure/imprint' development key to sign the p10bmc SPL. The
key can be overriden for a production key if necessary.
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: I6e4abecb5859fb59c6185a097cf88bdcb958e207
|
|
Use the insecure key provided by commit '748d586bc1 meta-aspeed: Add
development key for Kernel sign' to sign both the Kernel as well as
U-Boot fitImages. This is used for U-Boot FIT Signature Verification
using a known key, fit for development purposes. For production
purposes, a secure private key must be used.
Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
Change-Id: If0c39f4aa17e6eaa5f6952a90283457f252a64d3
|
|
To support the new rainier 2U fan hardware, the fan monitor config needs
to be updated to reflect the factor/offset between the target and
feedback speeds of the new hardware.
Change-Id: Ic63d678e89b210da77d4681ad44a209dd2807836
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
The p10bmc system uses a MMC flash chip with much larger storage than
a NOR chip. Increase the current journal size allocation from 2MB to 16MB
so that p1bmc saves more data for debug.
Tested: Verified that a witherspoon and p10bmc image had the expected
journal size file (2MB for witherspoon and 16MB for p10bmc) under
rootfs/lib/systemd/journald.conf.d/
Change-Id: Idcdb01bbf017c411c7b97406191e90774e8a8753
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
We want to use packageconfig options instead of build system specific
ones.
Change-Id: I587d33e3dae82c4c9d85f59f4ee34618443f1dcb
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
Switch over to the 'count' method of determining fan faults. As a
starting point, use a count interval of 1 and a threshold of 30. This
is the preferred method as it is better at catching flakey fans.
See docs/monitor/method.md in the phosphor-fan-presence repo for more
info on how this works.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I153d05779a5a7af854f351c1be3a3448b85fc461
|
|
The fan presence detect application uses I2C device paths in its config
files to address the IO expanders that IBM systems use to monitor fan
presence detects.
Use the /sys/bus/i2c/devices/... paths in these config files instead of
the absolute paths. These new paths are links to the actual paths, and
shouldn't change even if some internal kernel change drives an actual
device path change. There are other config files today that do this the
same way.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I39ed9d703cf6bdc821a54c6d5d087f7fc080705b
|
|
This creates a new DISTRO_FEATURE "ibm-service-account-policy" which
- Adds an admin account which cannot SSH to the BMC's command shell.
- Adds a service account which can SSH and has passwordless sudo access.
This feature is applied to witherspoon-tacoma and p10bmc (rainier).
Tested:
The image behaves as before when the distro feature is not configured.
When the distro feature is configured:
The root user has the same access as before.
The admin user:
- Is not allowed to access the BMC's command shell.
- Console login gets: This account is currently not available.
- SSH login gets: Permission denied, please try again.
- Redfish and REST API access works with role=Administrator.
The service user:
- Console login to the BMC's command shell works. The home
directory is /. Passwordless sudo works.
- SSH login works and using sudo from a SSH session works.
- Redfish and REST API access works with role=Administrator.
Change-Id: Icac5ba7f4fa663047709ab55007bbcfec8158f5e
Signed-off-by: Joseph Reynolds <joseph-reynolds@charter.net>
|
|
Change-Id: Ib7a9802582e146b5e2e5edb7b2df1800dfe36b22
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Power supply, fans and pcie slots are tied to a particular
chassis and thus need the associations for redfish to use them.
Change-Id: I71b9596b811c910fac65c16af4f008954a934b30
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Rainier-4U systems have 4 power supply D-Bus objects and hence
updated the associations json to have a mapping for powersupply2
and powersupply3 led group D-Bus objects.
Change-Id: I21ea628928a5f6a7d2dc014eb25559c6d2e15722
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
The 'monitor' package provides a power supply monitor application that
uses an org.open_power phosphor-dbus-interface that is only used
on a subset of the OpenPower systems.
So that non OpenPower systems can use phosphor-power and not need to
include the org.open_power D-Bus interfaces, add a packageconfig option
for this application to turn off its compilation. It will then only be
enabled for certain machines.
Fixes openbmc/phosphor-power#6
Tested:
Built Witherspoon, application still built and installed.
Built Rainier, application not built.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ib7fca16217d93b7d021ba8fb6659e9ddca17d1d9
|
|
The repository supports it, so switch it over in bitbake.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I8d96c79b395ee2614ddd869091569f245426c5c7
|
|
Discord has more users. IRC traffic has ground to a halt.
Signed-off-by: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com>
Change-Id: Ifa5c04ae211a93ebac2b3a887656965db1e00942
|
|
This variable was added to bitbake.conf so lets use it. Using it is
best pratice and enables things like alternative base_libdir paths.
Change-Id: I9adcec7856c6242d86f0ffad8646a23219ccca21
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Starting with a link to the 4u file. The only difference between the two
is 2 less fans so there should be no real impact to the callout file.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Iae528ef6378fdcad524faeefcd6139a1d8223789
|
|
Now that entity manager provides the system name, name the Rainier 2U
device callouts file after it and add the Rainier 4U device callouts
file.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I95ba6cee167616ec01bd7779e88defc0e77810df
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Patrick Williams (2):
bootstrap: fix shellcheck warnings
MAINTAINERS: remove Deepak
Change-Id: Id06241aa091d2c8f16b0f18383e244924030b12f
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
|
|
The hostboot team has started utilizing VUART1 for extra debug data
during a boot. This extra debug data is enabled within the CI
infrastructure. This extra debug data causes the critical information
going to VUART0 to get wrapped out of the default
/var/log/obmc_console.log file. Redirect the VUART1 data to its own
/var/log/ file.
The only other user of VUART1 on p10bmc systems is the PHYP software.
That is mostly used for interactive purposes so writing its data to a
separate log file should be fine.
I will work with the test teams to ensure this new file is collected as
a part of the standard debug data collection process.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I248e5e8536e58e137b5de35d7572789215566763
|
|
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
|
|
Bad VPD plugin is an IBM specific plugin which collects all the
corrupted VPD files from /tmp/bad-vpd and puts it as a part of user
initiated BMC dump.
Openpower-vpd-parser makes a copy of the corrupted vpd's into
/tmp/bad-vpd at runtime, whenever there occurs a VPD ECC exception or
VPD record/keyword data exception.
Installed badvpd plugin in dreport via phosphor-debug-collector recipe.
Placed badvpd plugin in
openbmc/phosphor-debug-collector/tools/dreport/ibm.d directory as we
collect bad vpds' only when "ibm-parser" feature flag is enabled.
Tested on simics.
root@rainier:~# dreport -v
Wed Mar 3 04:43:18 UTC 2021 Name: obmcdump_00000000_1614746598.tar.xz
Wed Mar 3 04:43:18 UTC 2021 Epochtime: 1614746598
Wed Mar 3 04:43:18 UTC 2021 ID: 00000000
Wed Mar 3 04:43:18 UTC 2021 Type: user
Wed Mar 3 04:43:18 UTC 2021 INFO: Collected disk usage
Wed Mar 3 04:43:18 UTC 2021 INFO: Collected failed services
Wed Mar 3 04:43:19 UTC 2021 INFO: Collected Journal pretty log
Wed Mar 3 04:43:19 UTC 2021 INFO: Copied Memory info /proc/meminfo
Wed Mar 3 04:43:19 UTC 2021 INFO: Collected top
Wed Mar 3 04:43:19 UTC 2021 INFO: Copied Bad VPD /tmp/bad-vpd
Wed Mar 3 04:43:19 UTC 2021 INFO: Copied OS release info /etc/os-release
Wed Mar 3 04:43:19 UTC 2021 INFO: No elog entries
Wed Mar 3 04:43:19 UTC 2021 INFO: Collected inventory
Wed Mar 3 04:43:19 UTC 2021 INFO: Copied OBMC console log /var/log/obmc-console.log
Wed Mar 3 04:43:19 UTC 2021 INFO: Collected ip addr
Wed Mar 3 04:43:19 UTC 2021 INFO: Collected ip link
Wed Mar 3 04:43:19 UTC 2021 INFO: Collected PRI-Flash: U-Boot environment variables
Wed Mar 3 04:43:19 UTC 2021 INFO: Copied GUARD Records /var/lib/phosphor-software-manager/pnor/prsv/GUARD
Wed Mar 3 04:43:19 UTC 2021 ERROR: /etc/alt_fw_env.config does not exist
Wed Mar 3 04:43:19 UTC 2021 INFO: Copied CPU info /proc/cpuinfo
Wed Mar 3 04:43:19 UTC 2021 INFO: Collected uptime
Wed Mar 3 04:43:19 UTC 2021 INFO: Collected BMC State
Wed Mar 3 04:43:19 UTC 2021 INFO: Collected Chassis State
Wed Mar 3 04:43:19 UTC 2021 INFO: Collected hostnamectl
Wed Mar 3 04:43:19 UTC 2021 INFO: Collected Host State
Adding Dump Header :/usr/share/dreport.d/include.d/gendumpheader
Wed Mar 3 04:44:08 UTC 2021 Report is available in /tmp
Wed Mar 3 04:44:08 UTC 2021 Successfully completed
Check the dump tar file generated in /tmp directory.
After skipping 628 bytes of dump header in tar, untar it.
The files in /tmp/bad-vpd directory gets collected into the bmc dump.
Signed-off-by: PriyangaRamasamy <priyanga24@in.ibm.com>
Change-Id: Ifdbfa56b8c67263271059dbee390092b92977775
|
|
Specifically kdump is a product requirement; makedumpfile is required
to reduce the size of the crash dump image as well as not saving
unneeded data at some point it will be useful from a privacy
perspective by not saving "sensitive" information.
Smaller crash dumps are faster to save thus allowing the reboot
to normal BMC mode sooner.
Signed-off-by: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com>
Change-Id: Ib07690cd26e519e1e3e51013ac76e623a3dad6a9
|
|
Discord has more users. IRC traffic has ground to a halt.
Signed-off-by: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com>
Change-Id: I9e0a695ca5397cdad9489c63edd4f01d295c44a6
|
|
The OBMC_ORG_YAML_SUBDIRS variable is intended to be set system-wide
and not via bbappends. There was an existing 'ibm-distrovars.inc'
that was unused. Rename it as appropriate, add it to the machines,
and remove the bbappend files.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Id5acd359f41c17ec9e68d1f0717e2f5c1bf96dcf
|