summaryrefslogtreecommitdiff
path: root/meta-phosphor/recipes-devtools/i2c-tools
diff options
context:
space:
mode:
authorAndrew Geissler <geissonator@yahoo.com>2018-09-26 00:12:14 +0300
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2018-09-26 22:43:49 +0300
commit469e377d6e39fd8f82e221a3e9c555808fcc926b (patch)
tree8487dd22a1c05d6997c943666aac202279880a59 /meta-phosphor/recipes-devtools/i2c-tools
parent862e477bfd365df3919b84929561259c51480e34 (diff)
downloadopenbmc-469e377d6e39fd8f82e221a3e9c555808fcc926b.tar.xz
Remove mapper nice priority
This is a revert of eff3d02a180ef60102f1f25d765b2ddf72831be3 A direct revert is not possible due to our subtree refactoring Prioritizing one application over another seems to cause more problems then it solves. In this case it appears that mapper can starve other process's in which mapper depends on responding. So that dependent process times out, restarts, which then causes the whole cycle to start over. Hoping this is the fix to openbmc/openbmc#3369 but will require some testing. Tested: George was kind enough to run this through some BMC reboot tests and a regression bucket. openbmc/openbmc#3369 did not recreate but not willing to declare success yet with that bug. (From meta-ibm rev: 9effdef83644fff90a2bcb6f4d6fb97ac28fcb28) Change-Id: I9af8ab369966a69c09d807d888b0bf5a0f0b3e07 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-phosphor/recipes-devtools/i2c-tools')
0 files changed, 0 insertions, 0 deletions