| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Change-Id: I8dece8c720fd520de7a6857a7311b62a65c054ba
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The meta-ibm layer supported two different DISTROs depending on the
machine being built. This caused complexity since the user needed to
remember to specify the DISTRO name, in addition to the CI build scripts
needed to check for the machine name being built to override the default
DISTRO.
For simplification, remove the openbmc-witherspoon DISTRO, which is the
openpower DISTRO plus additional features, and move these features to
the machine configuration files. Make the openpower DISTRO the default.
Tested: Built witherspoon and p10bmc using "source setup <machine> build"
followed by "bitbake obmc-phosphor-image" without specifying the
DISTRO. Verified witherspoon built a ubi image and p10bmc built
a emmc image.
Change-Id: If33441ab4ad2dc0fbedde09f0db91d691d2da4f7
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Commit f7b1f26 removed fru-fault-monitor from Rainier since the
idea then was to have PEL daemon set the Asserted property of
LED Group Object that is mapping to the Inventory D-Bus object.
However, that was not accepted by the community and we now have
a new way of monitoring faults.
With the new way, when monitor-operational-status feature is
enabled, fru-fault-monitor will watch Functional property of
xyz.openbmc_project.State.Decorator.OperationalStatus interface
and sets the Asserted property of appropriate LED Group D-Bus
objects that is mapped via "fault_led_group" association with
the Inventory D-Bus object.
When monitor-operational-status feature is enabled,
fru-fault-monitor will not monitor the OBMC events and would
only watch OperationalStatus. This is done because these 2
features will result in conflicting end result on the LEDs.
Change-Id: I739b5fc261b0c79d50a8dc34ab19a3e108e84edc
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Currently, the phosphor-fru-fault-monitor updates the Asserted
property of the Led Group D-Bus object by monitoring the
`/xyz/openbmc_project/logging` object path.
The intent behind this commit is to add another way to monitor the
`xyz.openbmc_project.State.Decorator.OperationalStatus` interface
of the Inventory D-Bus object, and check whether the Inventory
D-Bus object is associated with the LED group D-Bus object, and
then update the Asserted property of the LedManager.
Since both these methods handle the faults differently,
Only ONE of these 2 methods can be enabled and NOT both.
The first way is supported by default. To turn OFF the default way
AND turn ON this second way, Enable monitor-operational-status.
Change-Id: I03701e599b6a120bc1f83da6f473b12f38660d64
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
This allows a power button press to power on the system. Rainier and
Everest use the same GPIO.
Tested: Button was pressed and the system booted.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ib8f373dda2adb5575f2a0001d986962e5430fba5
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Tested: Verified the rainier build included the expected service files
and LED override file, example:
- rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-led-manager/lamp-test-led-overrides.json
Change-Id: I8f9ecbc6ebe1d320a649b24bf71c5023cfc035c8
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Replace rainier with p10bmc as build target. Keep the rainier.conf as a
symlink to p10bmc.conf to allow the transition. Remove the rainier.conf
and the machine override from p10bmc.conf in a later commit to complete
the replacement.
Tested: Built rainier and p10bmc and checked for some files/service
units to exist on both.
Change-Id: Ic8c8c6ffbc3507fbd9c692da259e37ae695359a6
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier system is being replaced with the generic p10bmc name.
Since the rainier.conf file will be renamed p10bmc.conf, add the device
tree files for all p10 systems that will be supported with the p10bmc
name (rainier, everest).
Change-Id: I10983b913d8a2ae98ed4d327131b864f2df96a0c
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Tested: Built rainier and verified files were installed:
rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-inventory-manager/ibm,everest_associations.json
rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-inventory-manager/ibm,rainier-4u_associations.json
rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-inventory-manager/ibm,rainier-2u_associations.json
Change-Id: I422374d25966e731147eebd1772d5cfc4f62f9d9
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Tested: Built rainier and verified the fan files were installed, ex:
obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-fan-presence/control/ibm,rainier-4u/zones.json
obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-fan-presence/control/ibm,rainier-2u/zones.json
obmc-phosphor-image/1.0-r0/rootfs/usr/share/phosphor-fan-presence/control/ibm,everest/zones.json
Change-Id: I10edb9e30716cffa3f510fe94822eadb08326912
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
Latest upstream yocto has moved on to the 3.3 hardknott release
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ieae36798d66d21c2c642931f06407d3bb2acf163
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Change-Id: I0a265a7eb9d763a8385a7139dae47bf2f475c672
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Change-Id: I0ab8ca402117e6eae8508d3f27cac7ad8c8b8aca
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Tested: Built a rainier image and verified the journal config files were
present under:
rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/lib/systemd/
Change-Id: Ia5c1de23fdbf7b8aeed70bd450cb72254542eb41
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Tested: Built rainier and verified that the mboxd service file had 64M:
$ cat tmp/work/rainier-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/lib/systemd/system/mboxd.service
..
ExecStart=/usr/bin/env mboxd --flash 64M --window-size 1M
Change-Id: I7c5bf66ac38ab0b97efa1eba7ceccba86565ed85
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Change-Id: Ic76f6202f9ae43440e5e6a793ca835a45d6ab088
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Change-Id: I5e0b884b405f56da7aa746b059d2490a1de2caab
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Change-Id: I5b7b173bd0255fcbe1956042cc365bf1fb6c7520
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Change-Id: I43d08c3be45d8cc8b03914b9bc257df2668e9fe0
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The IBM rainier machine name is being replaced with the generic p10bmc.
Change-Id: If32498a59ce621b1e456fdf0ec965c92d646ab86
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
