summaryrefslogtreecommitdiff
path: root/meta-phosphor/recipes-core/systemd
AgeCommit message (Collapse)AuthorFilesLines
2019-04-16Remove waits on chassis-control in host targetsMatt Spinler4-8/+0
The org.openbmc.control.Chassis service is no longer used for anything and is being removed, so remove the waits on it. (From meta-phosphor rev: 0603d1636896adce54710c3658dcd9f701d97b77) Change-Id: I03872ee827562be1d7e6d06d6503545ad1d38af6 Signed-off-by: Matt Spinler <spinler@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-06update upstream subtreesBrad Bishop24-37/+37
A number of corequisites exist so squashing these all into one patch. meta-ingrasys - refresh master bc513127f4..67bcaf389f meta-hxt - refresh master 86a4df514f..8fe0d38bbb meta-phosphor - refresh master 06c09d7cce..df6ddae3d2 meta-quanta - refresh master 4f126361a1..53f3025271 Change-Id: I3daeef2a0467d8ea4f1fd1c617e526f8b11258af Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-05reset upstream subtrees to HEADBrad Bishop8-1173/+4
Reset the following subtrees on HEAD: poky: 8217b477a1(master) meta-xilinx: 64aa3d35ae(master) meta-openembedded: 0435c9e193(master) meta-raspberrypi: 490a4441ac(master) meta-security: cb6d1c85ee(master) Squashed patches: meta-phosphor: drop systemd 239 patches meta-phosphor: mrw-api: use correct install path Change-Id: I268e2646d9174ad305630c6bbd3fbc1a6105f43d Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-03-29meta-phosphor: Drop recipe for phosphor-restBrad Bishop2-3/+0
This application doesn't have any in-tree users. As such, drop the recipe and its dependencies. (From meta-phosphor rev: 296cc521f5a1c8c87c63a5b475b23c876241bf22) Change-Id: Ie0ce809f84a133c023f96b4727550690583cb9df Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-23systemd: pick upstream fixes for timedatedLei YU4-0/+278
There are several fixes related to systemd/systemd#11420, which affects openbmc/openbmc#3459 Pick the related changes to fix the issue. Partially resolves openbmc/openbmc#3459. Tested: Run below script to make sure setting time eventually succeeds. timedatectl set-ntp 1 sleep 10 # Wait for a while for NTP service to start timedatectl set-ntp 0 until busctl call org.freedesktop.timedate1 /org/freedesktop/timedate1 org.freedesktop.timedate1 SetTime xbb 1487304700000000 0 0 do echo "Try again..." done (From meta-phosphor rev: 076771ae7363a3342fe45f7f8f6b383811c8677e) Change-Id: I453cff9224721052a1ed000fa4ded1d4858dcde1 Signed-off-by: Lei YU <mine260309@gmail.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-16systemd: Add support for static neighborsWilliam A. Kennington III4-0/+805
These are backports of changes I contributed to systemd v240. We need these until we get v240 from oe core. Tested: Ran a romulus image and provisioned static neighbors with systemd networkd. (From meta-phosphor rev: 8b84385e3c40d1827b06d0612def2275d3ad4faf) Change-Id: I5720a3b1626e15d4e4cfc630ce24f5818b294d8a Signed-off-by: William A. Kennington III <wak@google.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-09reset upstream subtrees to yocto 2.6Brad Bishop1-22/+44
Reset the following subtrees on thud HEAD: poky: 87e3a9739d meta-openembedded: 6094ae18c8 meta-security: 31dc4e7532 meta-raspberrypi: a48743dc36 meta-xilinx: c42016e2e6 Also re-apply backports that didn't make it into thud: poky: 17726d0 systemd-systemctl-native: handle Install wildcards meta-openembedded: 4321a5d libtinyxml2: update to 7.0.1 042f0a3 libcereal: Add native and nativesdk classes e23284f libcereal: Allow empty package 030e8d4 rsyslog: curl-less build with fmhttp PACKAGECONFIG 179a1b9 gtest: update to 1.8.1 Squashed OpenBMC subtree compatibility updates: meta-aspeed: Brad Bishop (1): aspeed: add yocto 2.6 compatibility meta-ibm: Brad Bishop (1): ibm: prepare for yocto 2.6 meta-ingrasys: Brad Bishop (1): ingrasys: set layer compatibility to yocto 2.6 meta-openpower: Brad Bishop (1): openpower: set layer compatibility to yocto 2.6 meta-phosphor: Brad Bishop (3): phosphor: set layer compatibility to thud phosphor: libgpg-error: drop patches phosphor: react to fitimage artifact rename Ed Tanous (4): Dropbear: upgrade options for latest upgrade yocto2.6: update openssl options busybox: remove upstream watchdog patch systemd: Rebase CONFIG_CGROUP_BPF patch Change-Id: I7b1fe71cca880d0372a82d94b5fd785323e3a9e7 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-01-08phosphor: systemd: add init alternativeBrad Bishop1-0/+5
This is removed upstream in thud (poky rev: ada8a5d) but we have a recipe that depends on it (preinit-mounts). preinit-mounts is only added to the rootfs when DISTRO_FEATURES contains obmc-ubi-fs. preinit-mounts might be a bit of a hack; getting filesystems mounted just right is typically the role of an initramfs. It may make sense to (re)visit how that is done and at that time we can drop this support. (From meta-phosphor rev: 2fb0a1b55ce9d4f133f34eda6e6df0aead585fef) Change-Id: Iac2acd7e2f23055387a3250392461a78ec361da8 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-11-28meta-phosphor: systemd: rework PACKAGECONFIGBrad Bishop1-4/+3
Phosphor removes a number of systemd packageconfigs that are enabled by default in oe-core. Sort the removal list alphabetically. Remove networkd. It is now selected by default in oe-core. Remove vconsole. Typically vconsoles aren't needed on a BMC and vconsole support has significant footprint cost. Remove ldconfig. The base recipe controls this via distro feature; don't override. Remove kdbus and bootchart. They aren't options anymore. (From meta-phosphor rev: 65ae799165fce6e5b50c68e32d20a09d2cdbd52f) Change-Id: Ieefd0d0d13cfdc65debbfdd3ab9ecdbc4154d28a Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-11-20Revert "Don't return the error if unable to create the network namespace"Brad Bishop2-42/+0
This reverts commit 87497e8ebce78079ea5423ecb6080e82cfa36106. systemd-hostnamed no longer hangs without network namespace support: PrivateNetwork=yes is configured, but the kernel does not support network namespaces, ignoring. (From meta-phosphor rev: 3b6dd35154ba5e105ad1d4b65746711654ed34b0) Change-Id: I41b5e1ae952b8bc3bc07819d7ab7e0fffd3629c7 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-11-20Revert "Cherry-pick systemd mangle-escape patch"Brad Bishop3-174/+0
This reverts commit 8ef5fd21107625d7480346318cb858759e61ee66. The pull request referenced in the original commit was never merged into systemd. Support for properly using /sys/devices paths as template instances has been added to systemd in the meantime. It probably didn't/doesn't make sense to use device tree paths when launching applications via udev+system (applications to use /sys/devices paths instead). Given all these reasons, drop these two systemd patches. (From meta-phosphor rev: ee22593ddc009cda7aad28bf1311f1a26047fc97) Change-Id: Ic10e0abc8c112e7e6bd62bc346857cf4194dbe50 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-11-06meta-phosphor: master refresh 3026b0fa5a..d76a657a63Brad Bishop1-1/+2
Update meta-phosphor to master HEAD. Patrick Venture (52): meta-phosphor: obmc-console: set LICENSE field meta-phosphor: dbus-interfaces: set LICENSE field meta-phosphor: rest-dbus: set LICENSE field meta-phosphor: slpd-lite: set LICENSE field meta-phosphor: ipmi-host: set LICENSE field meta-phosphor: ipmi-net: set LICENSE field meta-phosphor: network: inarp: set LICENSE field meta-phosphor: network: set LICENSE field meta-phosphor: logging: set LICENSE field meta-phosphor: ipmi-tool: fixup LICENSE meta-phosphor: clear-once: set LICENSE field meta-phosphor: preinit-mounts: set LICENSE field meta-phosphor: systemd: obmc-targets: set LICENSE field meta-phosphor: dbus: perms: set LICENSE field meta-phosphor: dbus-interfaces-mapper-config-native: set LICENSE field meta-phosphor: dbus-monitor-config-native: set LICENSE field meta-phosphor: legacy-namespace-mapper-config-native: set LICENSE field meta-phosphor: mapper-config-native: set LICENSE field meta-phosphor: obmc-host-failure-reboots: set LICENSE field meta-phosphor: fan-control-events-config-native: set LICENSE field meta-phosphor: fan-control-fan-config-native: set LICENSE field meta-phosphor: fan-control-zone-conditions-config-native: set LICENSE field meta-phosphor: fan-control-zone-config-native: set LICENSE field meta-phosphor: fan-monitor-config-native: set LICENSE field meta-phosphor: fan-presence-config-native: set LICENSE field meta-phosphor: image-signing: set LICENSE field meta-phosphor: insecure-signing-key-native: set LICENSE field meta-phosphor: inventory-manager-assettag-native: set LICENSE field meta-phosphor: inventory-manager-config-native: set LICENSE field meta-phosphor: ipmi-channel-inventory-native: set LICENSE field meta-phosphor: ipmi-config: set LICENSE field meta-phosphor: ipmi-fru-merge-config-native: set LICENSE field meta-phosphor: ipmi-fru-properties-native: set LICENSE field meta-phosphor: ipmi-fru-read-bmc-inventory-native: set LICENSE field meta-phosphor: ipmi-fru-read-not-sent-by-host-inventory-native: set LICENSE field meta-phosphor: ipmi-fru-whitelist-native: set LICENSE field meta-phosphor: ipmi-inventory-sel-native: set LICENSE field meta-phosphor: ipmi-sensor-config-native: set LICENSE field meta-phosphor: ipmi-sensor-inventory-native: set LICENSE field meta-phosphor: logging-callouts-example-native: set LICENSE field meta-phosphor: logging-error-logs-native: set LICENSE field meta-phosphor: settings-defaults-native: set LICENSE field meta-phosphor: fan-presence-mrw-native: set LICENSE field meta-phosphor: fan-control-fan-config-mrw-native: set LICENSE field meta-phosphor: ipmi-fru-properties-mrw-native: set LICENSE field meta-phosphor: ipmi-inventory-sel-mrw-native: set LICENSE field meta-phosphor: ipmi-sensor-inventory-mrw-config-native: set LICENSE field meta-phosphor: ipmi-sensor-inventory-mrw-native: set LICENSE field meta-phosphor: led-manager-config-mrw-native: set LICENSE field meta-phosphor: logging-callouts-mrw-native: set LICENSE field meta-phosphor: hwmon-config-mrw: set LICENSE field meta-phosphor: settings-read-settings-mrw-native: set LICENSE field Change-Id: Ibe919c3f1a748fae67b45ff6908a236b08902450 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-10-30Disable systemd-coredump from phosphor layerAndrew Geissler1-1/+1
Continue to hit two major issues with having coredumps enabled in OpenBMC: 1. Filesystem space for coredumps Systemd writes the core files to /var/lib/systemd/coredump/ This is a persistent filesystem so space is very limited. There is currently no way to configure this location (would need upstream work). Due to issue #2 below, when a single application fails, it starts to cause other services to coredump which results in the available space quickly filling up. This can result in the UBI kernel driver remounting the filesystem read-only. 2. CPU utilization When an application fails, and causes a coredump, it is restarted by systemd. The restart causes mapper to fire up and introspect the restarted application. In parallel the coredump is being generated and collected. These two things heavily load the CPU. If this occurs during the initial startup of the BMC, where lots of other services are also starting and being introspected by mapper, then those services can start hitting their systemd timeout limit. This then results in core dumps being collected for them and mapper instrospects being called on their restarts. This causes a snowball affect where the system just continues to restart services and collect core dumps. The systemd restart policy can not account for these long delays between restart (due to the CPU load) so the limit is never hit within the time limit, resulting in an infinite restart loop. There is upstream work that could be done with systemd to make the core dump function more embedded system friendly. This would be a long term solution but may become a moot point as performance improvmenents come in (c++ mapper), more powerful CPU's are used, and more flash space is allocated in future systems. Personally, I've never used a core dump to debug an issue and have dealt with the above issues multiple times so I'm probably a bit biased. This could definitely be a meta-ibm layer type change if others in the community prefer this enabled as the default. resolves openbmc/openbmc#3379 (From meta-phosphor rev: dde999f1076f571a1760c9e5e536e63796749e57) Change-Id: Ib229d8bf58aa075926fd302a0139a042d069f446 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-09-25systemd: fix noisy messages about eBPFAlexander Filippov2-0/+65
Patch systemd sources to fix detection of availability of the kernel CONFIG_CGROUP_BPF option. Resolves openbmc/linux#159 (From meta-phosphor rev: 7fbc79b12dc5e137830ffd35c0be839fe77b6699) Change-Id: I82cd227cb6e14ca57a373b1c6a100a98cff799af Signed-off-by: Alexander Filippov <a.filippov@yadro.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-09-06meta-phosphor: Move layer content from common/Brad Bishop42-0/+637
Adopt a more conventional directory hierarchy. meta-phosphor is still a _long_ way from suitable for hosting on yoctoproject.org but things like this don't help. (From meta-phosphor rev: 471cfcefa74b8c7ceb704cb670e6d915cf27c63b) Change-Id: I3f106b2f6cdc6cec734be28a6090800546f362eb Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
generated by cgit v1.2.3 (git 2.39.0) at 2024-08-25 09:00:41 +0300