Age | Commit message (Collapse) | Author | Files | Lines |
|
Phosphor specific overrides to systemd should be stored
within its own recipe and pulled in via the phosphor layer.
This helps distinguish systemd specific overrides with
phosphor overrides.
Tested: Verified service-restart-policy.conf was still
pulled in as expected in witherspoon QEMU
Change-Id: I32110fc2edd3abd2bb0008c63dd4ad7828b762b8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Tested: Performed system boots and reboots.
Change-Id: I1052cb4cd86a5815df1f1021a37f539184078d82
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
Move OpenBMC to Yocto 2.5(sumo)
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I5c5ad6904a16e14c1c397f0baf10c9d465594a78
|
|
1e4452449 added a systemd tmpfile config file for the software image
upload path but the config file was added to the systemd recipe.
tmpfile config files should be added to the recipes/config files that
use them. For example on an RPM based distro:
$ rpm -qf /usr/lib/tmpfiles.d/samba.conf
samba-common-4.7.7-0.fc27.noarch
Tested: Validated software.conf present in Witherspoon rootfs
Change-Id: I47e8c8c44eb19440cc98d0380e9634f688eccb21
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Somewhere between systemd 234 and 237 the install process stopped making
/usr/lib/systemd/network for us. When we move to Yocto 2.5 this will
result in an install failure.
bitbake.conf provides a variable for /lib/systemd. Use it, as it's the
correct location for these configuration/unit files anyhow.
Tested: Booted QEMU witherspoon image to shell
Change-Id: Ia863473539378ef07f652ae3820b9c22ce5f6900
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This reverts commit bbf2cb8e1e4d490acf80ce3a5b162d7db5f3e4e2.
This change doesn't seem to be required anymore.
Tested: Booted Palmetto system in QEMU
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I34b3dd17d1fe7427ec12f84c6ad9bb5367f73cf6
|
|
These were removed from SRC_URI with the bump to Yocto 2.4, which bumps
systemd to v234, which contains said patches.
Change-Id: If0584df10a028b444e49ca0fb7d7a9ca2e66dc3e
Fixes: d7bf8c17eca8 ("Yocto 2.4")
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
|
|
The BMC CPU performance is already challenged. When a service is
failing and a core dump is being generated and collected into a dump,
it's even more challenged. Recent failures have shown situations where
the service does not fail again until 15-20 seconds after the initial
failure which means the default of 10s for this results in the service
being restarted indefinitely. Change this to 30s to only allow a
service to be restarted StartLimitBurst times within a 30s interval
before being put in a fail state.
Testing: Verified that killing an application 3 times within 30 seconds
results in the service being in a fail state (and not restarted).
Resolves openbmc/openbmc#3131
Change-Id: I58c874c1c5b618c147946195af65f42371d683c8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
The phosphor-logging interface has been updated to call a local interface to
sync the journal instead of making a D-Bus call:
https://gerrit.openbmc-project.xyz/#/c/9910/
Delete the journald patches since they're not needed anymore.
Tested: Built witherspoon image.
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Change-Id: Ie6b4387bf53ea4c29a7bbef6483ef723c333dfdf
|
|
upstream: https://github.com/systemd/systemd/pull/7352
Change-Id: I62df65eeec786890c0a7b923fd0455f7869f38b9
Signed-off-by: Edward A. James <eajames@us.ibm.com>
|
|
Requirements have arisen for OpenBMC firmware to run
certain services only during fresh power on operations.
To achieve that, break the obmc-host-start action target into
two targets. The existing obmc-host-start target will now
call the new obmc-host-startmin target. The startmin target
will be the minimum services required to start the host.
The obmc-host-start target is where services that should
only be called during a fresh power on can be placed.
The initial use case for this is the obmc-host-reboot target.
It will call this new obmc-host-startmin target to do the bare
minimum on a reboot operation.
This then allows the use case for OpenBMC to only reset the host
reboot count on a fresh power on operation. A new service will
be added to the obmc-host-start target to do this. If a reboot
operation is issued, or a host watchdog is triggered to cause a
reboot, this service would not be started, ensuring the reboot
count is properly decremented.
Tested: Verified on/off/reboot and ran CT regression suite.
https://gerrit.openbmc-project.xyz/#/c/9821/ is required
for reboots to work properly.
Change-Id: I86df03e6d671178c1525f852e196c4102bb73cb6
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Move OpenBMC to Yocto 2.4(rocko)
Tested: Built and verified Witherspoon and Palmetto images
Change-Id: I12057b18610d6fb0e6903c60213690301e9b0c67
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
As with MRW the use of the UBI image scheme is distro policy.
Convert the existing machine feature to a distro feature.
Enable the new distro feature on the systems that use
it(Witherspoon).
Add a distro override and fix-up MF checks to use this override
instead for improved readability.
Tested: Built a Witherspoon image and validated image
Change-Id: I8ab03115bbfc2ecc77cff5c9eb8628903ae88051
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
All the fan services associated with controlling, monitoring and
presence detection of fans need to remain active until a poweroff
completes. This helps ensure thermal safety while a system is in
transition to a powered off state.
With the introduction of this new target (which runs last in
the power off path), need to move the host reset service to
running after it to ensure the power on in the reboot path
does not start until the last power off target runs.
Resolves openbmc/openbmc#2762
Change-Id: I4ca671d2c7de66e8bfa4bba607b06c88c0a6e7f9
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
|
We carry a systemd patch that adds a new systemd configure option
--enable-journald-dbus. Add it to PACKAGECONFIG and select it.
Previously the patch selected the option by default.
Add new files that are installed by the patch to FILES_${PN} to
avoid unpackaged files errors from bitbake due to upstream systemd
recipe changes in Rocko.
Tested: Built and verified witherspoon and palmetto images
Change-Id: Iaf72c2b039706287a00126035eafe2f8631ca473
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
This saves the download and building of the following packages:
libxslt
xmlto
docbook-xml-dtd4
docbook-xsl-stylesheets
Change-Id: Ib2488375f642ce72e18c57ee6b77cdb71251d7c6
Signed-off-by: Joel Stanley <joel@jms.id.au>
|
|
The current uuid generation method just export the machine-id,
it does not match the systemd description
(https://www.freedesktop.org/software/systemd/man/machine-id.html):
This ID uniquely identifies the host. It should be considered
"confidential", and must not be exposed in untrusted environments,
in particular on the network. If a stable unique identifier that is
tied to the machine is needed for some application, the machine ID
or any part of it must not be used directly.
Backport the new sd_id128_get_machine_app_specific from systemd 233,
to replace the old uuid generation method.
Change-Id: I44e7b32ca951a9fa591761c3a3e4f27da04d2b6f
Signed-off-by: Yong Li <yong.b.li@linux.intel.com>
|
|
Further testing has shown that with core files enabled,
it's possible to exceed the 10s default interval time
when doing 3 restarts. Since all testing has shown
either 1 restart fixing the issue, or no restarts fixing
the issue, reduce the restart limit from 3 to 2 to
ensure even if the service is core dumping, the restart
limit will be hit within the 10s.
Resolves openbmc/openbmc#2559
Change-Id: Ie1dac96eb1b4ced0bf166c12419db26924104ab4
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
/tmp is deleted every 10 days
/usr/lib/tmpfiles.d/tmp.conf does this cleanup with this entry,
"q /tmp 1777 root root 10d".
Exclude /tmp/images from the cleanup, by adding "x /tmp/images"
to /usr/lib/tmpfiles.d/software.conf, if a feature of the machine is
obmc-ubi-fs or openpower-ubi-fs.
Resolves openbmc/openbmc#2544
Change-Id: I3ead88724adcd63ebfd809d310109a19232b1def
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
Change-Id: Icd951d2ed4075b7b04393157b3c420ef644b3bc5
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
This reverts commit 2a284a012d902bfa399bc14309337c3c1fe1a8ff.
Change-Id: I88f1cc9275d9dd1c39fda7e4fe218941fd5ddd42
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
|
|
Reduce number of service restarts and increase wait
time between restarts.
- Change the StartLimitBurst to 3
Five just seems excessive for our services in openbmc. In all fail
scenarios seen so far (other then with phosphor-hwmon), either
restarting once does the job or restarting all 5 times does not help
and we just end up hitting the 5 limit anyway.
- Change the RestartSec from 100ms to 1s.
When a service hits a failure, our new debug collection service kicks
in. When a core file is involved, it's been found that generating 5 core
files within ~500ms puts a huge strain on the BMC. Also, if the bmc is
going to get a fix on a restart of a service, the more time the better
(think retries on device driver scenarios).
Change-Id: I0e5bb3f32022cdb72d00f1a861a69653ef937cf1
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
This reverts commit 3b900a42acf55606bf28d7e83cabe1a545e9178d.
Change-Id: Ia19c92e6724068e84989f62d1673c9effb287f83
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
|
|
Resolves openbmc/openbmc#1938
This reverts commit 45af9a22aabf38474a00698f511e334c14d84c76.
Change-Id: I482d8b14ce1cfcb9022973a9412adff46f458f5f
Signed-off-by: Charles Paul Hofer <Charles.Hofer@ibm.com>
|
|
Package includes systemd tools for storing and retrieving
coredumps.
Change-Id: I7d71b9a0f055213c6293c3cbd1af26a662e87e2a
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
|
|
The Synchronize method would be called when an error log is
committed to get all the entries flushed into the journal.
These patches have been submitted upstream and can be removed
once the changes are integrated into systemd.
Change-Id: I89059d438870803b41bafdb4de3fb11eba3c5fd2
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
The state management code on the BMC is designed to
utilize systemd targets as much as possible. The host
reboot was always the odd duck that had some special
code written to support it. This special code would
basically issue a power off, look for it to complete
and then issue a power on. This is very error prone
code and has resulted in a few issues.
Moving to a single systemd target (the new reboot target)
defined here will allow the host reboots to occur
solely through a single systemd target now.
openbmc/openbmc#2032 is one of those bugs being
addressed with this change.
Change-Id: If33454aa4f15580e45f888a9b1602dec24a46fca
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
If the chassis poweroff target is running at the same
time as the host stop target, ensure the host does
not consider itself complete until the chassis
is fully off. This ensures host reboots will
wait for the chassis to be fully off before starting
the next boot.
Resolves openbmc/openbmc#2026
Change-Id: Iefcbb6435cc81393d0591cf4c7bb4eceeef906f0
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
With the recent refactor to the shutdown targets,
need to ensure the obmc-chassis-poweroff target is
called if the host-shutdown times out so that
the system properly shuts down
Resolves openbmc/openbmc#2027
Change-Id: I8b1374611776a4027beaa7646862dc4be51df838
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
On systems where kernel is not configured with namespace support
then don't return error during setting up network namespace.
Rationale to not enable the kernel with namespace support
as it brings lot of unnecessary code.
Resolves openbmc/openbmc#1949
Change-Id: I3b52a8c61b9bd3e3fff02cfab998c3746b8b72c6
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
|
|
This target will allow the user to do an immediate
power off of the system without waiting for the host.
It can also be used to cause an immedate power off
if the host is hung during the normal power off
process.
The chassis poweroff target will now require the
host off target to ensure everything is properly
stopped when the chassis is powered off.
Change-Id: I8430d895ae5498d2e451aaf07480b0cf9550e8f2
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
When this target is started, the fan watchdog will
take over fan speed control and move fans to full speed.
This will be done by having other services conflict with
this target.
Change-Id: I00c00a835cc2f7087baa1649d582287628b01401
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
This target gets executed when the host watchdog times out.
Change-Id: Id6711a1b7eab784189daf46bc225398b5cc1790f
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
As a part of the soft power off (host-shutdown) ensure
that the host-stop target always gets called. Updated the
involved services to ensure they are run in the correct order.
Change-Id: I7e9113631786f0d0cb0f89b94c4b97fdc0328e7b
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
When GPIO monitor sees that a particular line is asserted,
it calls into one of the configured systemd targets and this
is one such. For now, the target just has host-quiesce and
will be enhanced to contain a service that logs an error.
Change-Id: I09afea5fcab3efce7bbfa5124af9b8cb2e0594bf
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
Add a dependency to the power on target so that it waits to
start until the ActivationBlocksTransition interface is not
present on any of the Software subtrees, which would indicate
that a code update is in progress.
Closes openbmc/openbmc#1344
Change-Id: I926d209ce4d3106e09e35a35c1e9cfde1ec2f613
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
|
This target is started after fans have had time to
ramp up to full speed, and will start the fan monitor
and control services.
Change-Id: I99c1125f038071f56612859d976d5fba3fe9ffd6
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
The obmc-host-stop@.target will always be called on host shutdowns
but the inverse is not always true. This commit ensures everything
conflicts with the target that is always called in this path.
Change-Id: Ic680ef96b1d6e2aec844a9c619928b7014fe7450
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
The target change is:
obmc-stop-host -> obmc-host-shutdown
obmc-quiesce-host -> obmc-host-quiesce
Updated skeleton-rev.bbclass to have
correct commit id.
Change-Id: Ida47f8709622d98129c0fe00c86bad77d8d76dfb
Signed-off-by: Josh D. King <jdking@us.ibm.com>
|
|
The target change is:
obmc-chassis-stop -> obmc-host-stop
obmc-chassis-start -> obmc-host-start
Removed CHASSIS_FMT and CHASSIS_LINK_FMT
because they are no longer needed.
CHASSIS_POWER_FMT_2 did not change because
its used for obmc-chassis-reset.
Deleted files obmc-chassis-start@.target and
obmc-chassis-stop@.target because they are
no longer needed. I moved over their contents
to obmc-host-start and obmc-host-stop.
Updated phosphor-state-manager.bb and
skeleton-rev.bbclass to have correct commit
id.
Change-Id: I26cba4153038f39d60e8d450a05969a216848abe
Signed-off-by: Josh D. King <jdking@us.ibm.com>
|
|
The target change is:
obmc-power-chassis-on -> obmc-chassis-poweron
obmc-power-chassis-off -> obmc-chassis-poweroff
Also updated phosphor-state-manager.bb to now
have correct commit id.
Change-Id: I15aae803e5f0d44d4e6a137278f93e91f848b2c0
Signed-off-by: Josh D. King <jdking@us.ibm.com>
|
|
The point of this new target is to support getting
the systemd targets which boot the host into the
running state (without actually running the associated
services) when the BMC is rebooted and the host is
up and running. This will ensure that systemd
and its targets match with the state of the system
without affecting the running host.
This commit will run the new target but nothing will
happen yet due to the discovery service being a noop.
Once the application is in for the service to call,
it will be added to the service which will enable this
new host running with bmc reset support.
Change-Id: Ia29e53de58ea7530941341b0e515e4d8fa49be6c
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
Makefile.
Note: This is part of the change required to
upgrade systemd to version 232.
Resolves openbmc/openbmc#932
Change-Id: Ia529e301c63938a68e1acd3eb74242c2dd92ba3d
Signed-off-by: Saqib Khan <khansa@us.ibm.com>
|
|
Start fsi-disable.service to unbind the FSI Driver.
Start fsi-enable.service to bind it again and rescan.
Also added a fsi-bind@.service so we can ensure the
driver is bound each power on.
Change-Id: I5fa62b44994aea3bb645e755187f29e720bf3bce
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
Run the obmc-chassis-reset@.target:
- Check if pgood is on
- If it is, create the file in /run/openbmc/chassis@%i-on and
- Run the systemctl command to start the chassis power on target
Resolves openbmc/openbmc#1094
Change-Id: I93f94fc1b75e35fd353387d0bed5569e07615171
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
Once enabled these targets and services will be run after
a BMC reboot to check if pgood is on and if so, to create
a file which will be used by other power on services
to know whether they need to run or not.
Change-Id: Id2e75f9bce20f362d2f57a79e91ece1eaf7d7c45
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
When services associated with a target fail, the
target should go to the quiesce state for error
gathering and policy checks on automated recovery.
Use the OnFailureJobMode=flush to ensure all queued
services are cancelled when entering quiesce.
Change-Id: I4023a9c842500bb57013196aefbded533131ef00
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
This will be the target that all other critical targets go to when
a service within it fails. Automated recovery and stay-in-fail-state
logic will be built on top of entry into this new target.
Change-Id: Ibdf2e823cf372916c61ef5a8375c4faf8a928119
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
Change-Id: I5e4a0da68bfcebb12f3ac4161e63c145f9f73b0a
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
Change-Id: I42049c092e4a852b94b6d3f96b9dea3884c21333
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|