#
4639e550 |
| 05-Apr-2024 |
Adriana Kobylak <anoo@us.ibm.com> |
vpnor: updatesymlinks: Disable rate limiting
This service can be restarted multiple times in a row after a BMC reboot due to its WantedBy dependencies, causing this service to fail with a start-limi
vpnor: updatesymlinks: Disable rate limiting
This service can be restarted multiple times in a row after a BMC reboot due to its WantedBy dependencies, causing this service to fail with a start-limit-hit systemd error because it exceeds the default burst limit. Disable the rate limiting to avoid this error since this service is designed to be started as many times as required.
Tested: Restarted pldmd and mboxd multiple times and the start-limit-hit error is not seeing anymore.
Change-Id: I437cc70d3cf70cd8d59d17b7cb2f4b8995a278c8 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
show more ...
|
#
67dbb254 |
| 08-May-2023 |
Andrew Geissler <geissonator@yahoo.com> |
systemd: no installation in templated targets
Upstream yocto introduced a change via e510222 (systemd-systemctl: fix instance template WantedBy symlink construction).
This fixes a bug that we in Op
systemd: no installation in templated targets
Upstream yocto introduced a change via e510222 (systemd-systemctl: fix instance template WantedBy symlink construction).
This fixes a bug that we in OpenBMC had been taking advantage of in that we were able to document our templated target dependencies without it actually doing anything. The real installation of services within targets occurs in our bitbake recipes due to the complexity of chassis and host instances on a per machine basis.
Leave the dependency information in the service files but comment them out. It's useful to be able to look at a service and understand which targets it's going to be installed into by the bitbake recipes.
In some cases, we had hard coded the target instance, which does install the service correctly, but only in that one target. All services should be installed via the bitbake recipe to ensure the service is properly installed in all instances of the target (or service). Once the bump for this commit goes into openbmc/openbmc, I will ensure the recipe is updated to install all services correctly.
Change-Id: I6b1b3ebb9c1c3c2c5c03cf02ec5b74b9c2bcae2a Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
show more ...
|
#
6fa12d3d |
| 26-Jan-2023 |
Andrew Geissler <geissonator@yahoo.com> |
update service file deps in accordance with recent refactoring
As noted in the following mailing list thread: https://lists.ozlabs.org/pipermail/openbmc/2022-November/032457.html
and implemented vi
update service file deps in accordance with recent refactoring
As noted in the following mailing list thread: https://lists.ozlabs.org/pipermail/openbmc/2022-November/032457.html
and implemented via this series of commits: https://gerrit.openbmc.org/q/topic:op-power-control-ref
Some systemd services had their names changed. Update the service files in this repo to reflect this.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: I07e1d18a098398bca1038fd9012e53162846303d
show more ...
|
#
8652eb9b |
| 20-May-2022 |
Adriana Kobylak <anoo@us.ibm.com> |
mmc: Add nvram hostfw directory
Created an nvram directory to store the hypervisor's NVRAM files. Create a symlink to that directory for apps like PLDM to access it. Add a dependency to the symlink
mmc: Add nvram hostfw directory
Created an nvram directory to store the hypervisor's NVRAM files. Create a symlink to that directory for apps like PLDM to access it. Add a dependency to the symlink service to start before the PLDM services that would make use of the new NVRAM directory start.
Tested: Verified the directory and symlink got created. Verified the PLDM services started after the symlink one.
Change-Id: I8cdef7cc2176ed10096712918a743efd304df6c1 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
show more ...
|
#
98f22326 |
| 20-Jul-2020 |
Adriana Kobylak <anoo@us.ibm.com> |
mmc: Add read-only directory to support mboxd
The mboxd implementation assumes that there is a read-only and read-write directory. During a write request, mboxd copies the contents of the read-only
mmc: Add read-only directory to support mboxd
The mboxd implementation assumes that there is a read-only and read-write directory. During a write request, mboxd copies the contents of the read-only to the read-write directory. To continue to support mboxd, mount a read-only directory of the hostfw image for mboxd to use. Otherwise the write command fails (can't copy the file to itself) and mboxd exits.
Tested: Verified mboxd didn't fail and system powered on.
Change-Id: Idcb8ff0c5eee0179d5d70e60e5e01c7d0f76b880 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
show more ...
|
#
0e0a3b1a |
| 15-Jul-2020 |
Adriana Kobylak <anoo@us.ibm.com> |
vpnor: Add hostfw symlinks
On eMMC, in addition to the PNOR files, there are hostfw files. Create symlinks for the 2 versions on flash, so that pldm (which will replace mboxd) can read/write.
Teste
vpnor: Add hostfw symlinks
On eMMC, in addition to the PNOR files, there are hostfw files. Create symlinks for the 2 versions on flash, so that pldm (which will replace mboxd) can read/write.
Tested: Both pnor and hostfw links are created: root@rainier:~# ls -l /var/lib/phosphor-software-manager/* /var/lib/phosphor-software-manager/hostfw: lrwxrwxrwx 1 root root 23 Jul 16 20:37 alternate -> /media/hostfw/alternate lrwxrwxrwx 1 root root 21 Jul 16 20:37 running -> /media/hostfw/running
/var/lib/phosphor-software-manager/pnor: lrwxrwxrwx 1 root root 21 Jul 16 20:37 prsv -> /media/hostfw/running lrwxrwxrwx 1 root root 21 Jul 16 20:37 ro -> /media/hostfw/running lrwxrwxrwx 1 root root 21 Jul 16 20:37 rw -> /media/hostfw/running
Change-Id: I2fe726641611112bc7a447eed5c2d64db268ce8e Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
show more ...
|
#
f3dfe65d |
| 08-Oct-2019 |
Adriana Kobylak <anoo@us.ibm.com> |
Move updatesymlinks to new vpnor feature
The updatesymlinks functionality is to support virtual pnor and it does not depend on the filesystem type. Move it to a new vpnor feature so that users can m
Move updatesymlinks to new vpnor feature
The updatesymlinks functionality is to support virtual pnor and it does not depend on the filesystem type. Move it to a new vpnor feature so that users can make use of this feature without being tied to UBI, for example on a eMMC that has a combined BMC+PNOR image.
Tested: Verified that the witherspoon image contained the new script and service file and that it powered on to the host.
Change-Id: Ic5e51dfde81718e5e285f010be67afbd58eac2e1 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
show more ...
|