Age | Commit message (Collapse) | Author | Files | Lines |
|
phosphot-dump-monitor adds watch on systemd core dump path to
detect any new core files created to initiate a dump. On some
systems systemd core dump package is not pulled, due to this
phosphor-dump monitor service logs error and tries retry for 3 times.
Modified to start phosphor-dump-monitor service only when the
systed core dump path exists.
Tried to add Requires on systedm core dump service but as it is
a template version going with path approach.
Tested:
1) Removed systemd dump folder and restarted dump-monitor service
and ensured that there are no errors logged
(From meta-phosphor rev: 7a99220eaae763113372477c3d25039284802ef7)
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
Change-Id: Ibeb83cde454bf4c6fc6c6827a25705649ceaabe5
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
PHOSPHORBASE is only used for pointing at licenses...point at the
licenses in oe-core in meta/files/common-licenses instead. to match the
defacto convention used in other oe layers like meta-openembedded.
(From meta-phosphor rev: a1cee09419cb1467c3d2b7bf996b40089f0d06f4)
Change-Id: If136d24638a8022671988cf0a01620e7fffc545f
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Marri Devender Rao (1):
Fix dreport os-release script point to a symbolic link
Patrick Venture (1):
build: install into bin instead of sbin
(From meta-phosphor rev: f09b8a81b8c35dd4c48219ffe0651b7dfba9b4ae)
Change-Id: I51ebae43f3db8f7f2ace5e5ae17d53fadf13dd70
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
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>
|
|
Out of the box bitbake examines built applications, automatically adds
runtime dependencies and thus ensures any library packages dependencies
are automatically added to images, sdks, etc. There is no need to list
them explicitly in a recipe.
Dependencies change over time, and listing them explicitly is likely
prone to errors - the net effect being unnecessary shared library
packages being installed into images.
Consult
https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-RDEPENDS
for information on when to use explicit runtime dependencies.
(From meta-phosphor rev: 26873c99d30b55e21a920c9851f21c3e2eab19f7)
Change-Id: I38640d75a2d834c07d45ddcdb0162f1a23f848d9
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Patrick Venture (1):
build: pkg anti-pattern: use defaults
(From meta-phosphor rev: 8f64091684be16f5b3cf404e1a3a4fef849d4025)
Change-Id: Ic5107fc354fdd4dd90cf1aacd0efef75f5db220e
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
Artem Senichev (1):
Add phosphor-hostlogger plugin to dreport
Marri Devender Rao (2):
Refactor to pass errors to watch through config YAML
Specify plugins to be invoked for chekstop error
(From meta-phosphor rev: 8e57223281d135269e90337cabff891e5737a898)
Change-Id: I0e72044fa616f8f8a71ea513b6093b7e44c16a18
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Refactored code to pass error objects to watch through YAML file
Dump will be created when an error object created matches
the error object path specified in the YAML file.
(From meta-phosphor rev: ae622549f4947084e549ec5cfc40f88daa5c4ae6)
Change-Id: I9eb1c53ee4e1580d903e1004009d7595fb7811a6
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Brad Bishop (1):
internal: Add missing Manager forward declaration
Jayanth Othayoth (2):
Enable clang code format
MAINTAINERS: Updated reviewers
Vernon Mauery (1):
phosphor-debug-collector: use c++17
(From meta-phosphor rev: b1868a209d97a5657bc6dbc26d8959d140f766cd)
Change-Id: I52ef66da22801e12f6bde0eb3d8244b1ddc2f3b9
Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Drop symlink and rename bb for phosphor-debug-collector.
(From meta-phosphor rev: 32f84232355ef16ec5af36a87bead81634bb1b9e)
Change-Id: I9a90de31e0fdfc35ce7d8acfbd7556525556bf22
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
In the five step sequence of transitioning an unversioned recipe to
a versioned one, PV cannot be explicitly set to 1.0+git${SRCPV} set
until the last step.
With PV set, _both_ the unversioned recipe and the versioned recipe
end up with PV = 1.0 and bitbake will continue to use the unversioned
file. This means that when the unversioned bbappends are removed in
step 4, the bbappend does not occur.
This commit can be reverted once the five step process is complete.
For reference, the five step process is:
1.
Create a temporary recipe symlink:
foo.bb -> foo_git.bb
This results in two available PVs for foo: "1.0" (the bitbake default
for unversioned recipes) and "git".
Further, set the preferred version for foo to "1.0" in the distro
configuration otherwise bitbake will choose PV = "git" and existing
(unversioned) bbappends will not apply and the build will break.
2.
Create a temporary bbappend symlink:
foo.bbappend -> foo_%.bbappend
This allows the manual override of the preferred version introduced in
step 1 to be removed from the distro configuration.
3.
Remove the preferred version override introduced in step 1 from the
distro configuration. At this point the versioned recipe is now being
used.
4.
Remove the unversioned bbappends.
5.
Remove the unversioned recipe.
(From meta-phosphor rev: 883e0238adc8543b28cce8a5d283d2092026da54)
Change-Id: I3c5248a41b064462d5a34a7bc6e5438acc107a32
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Change version in phosphor-debug-collector.bb
(From meta-phosphor rev: 70852f2a95f956da81f43410c625427cb632c09c)
Change-Id: Ic5e2695d86c57caa50fbbce830abe2f39fc2de60
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Add a symbolic link to phosphor-debug-collector.bb named _git.bb and sets the
preferred version for the recipe.
(From meta-phosphor rev: 87491e53e44a00d3eb85883091213a43df43fca6)
Change-Id: I7d23561f7e13879e7e1fc896a10d950bb68f44c4
Signed-off-by: Patrick Venture <venture@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
It is observed that systemd-coredump has the capability to remove
the older dumps which are having the naming style mentioned in
/proc/sys/kernel/core_pattern, But will not remove any other files
present in the coredump directory.
It can happen that, while processing a dump the BMC Crashes and there
by leaving the partial dumps in the coredump directory and these will
be hidden and will not be removed by systemd-coredump service.These
files can get piled up and the BMC can run into OOM condition.So idea
of this commit is to make sure that , we remove all the temporary
hidden files in the coredump directory during the next BMC boot.
- Made a rule and placed it in /usr/lib/tmpfiles.d/*.conf which will
be used by systemd-tmpfiles to remove the hidden files in coredump
directory during boot.
Partially Resolves openbmc/openbmc#2826
(From meta-phosphor rev: 9fe03c666476de51ab75904f008f45f8485ac9b2)
Change-Id: Iff96b3880ebdeccb842e6aa7ff9807fcd451fb5a
Signed-off-by: manojeda <manojeda@in.ibm.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
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>
|