entity-manager take up too many resources about entity-manager HOT 8 OPEN

The background log keeps scrolling

from entity-manager.

root@BMC:~# time busctl tree xyz.openbmc_project.EntityManager | cat
└─/xyz
└─/xyz/openbmc_project
├─/xyz/openbmc_project/EntityManager
└─/xyz/openbmc_project/inventory
└─/xyz/openbmc_project/inventory/system
├─/xyz/openbmc_project/inventory/system/chassis
│ └─/xyz/openbmc_project/inventory/system/chassis/BMC
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/BOARD_CURRENT2
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_P0V6_VTT
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_P1V05
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_P1V2_VDDQ
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_P1V2_VDDQ_V
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_P1V8
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_P1V8_AUX
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_P2V5_VPP
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_P3V3_AUX
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_P3V3_STBY
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_P5V_AUX
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_TEMP
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_V1P8_EMMC_O
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_V3P3_EMMC_O
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_VCCIN
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_VCC_ANA
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_VNN_NAC
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_VNN_PCH
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_XDPE_P1V05_V
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_XDPE_P1V8_V
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_XDPE_PCH_V
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_XDPE_VCCIN_V
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_XDPE_VCC_V
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/CPU_XDPE_VNN_V
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/FAN_OUTLET_TEMP0
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/FAN_OUTLET_TEMP1
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_TEMP
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDD12V
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDD12V_1
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDD1V0_FPGA
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDD1V2
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDD1V2_FPGA
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDD1V8_CLK
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDD1V8_FPGA
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDD3V3
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDD3V3_CLK
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDD3V3_STBY
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDD5V_VR
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDDO1V2
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDDO1V8
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MAC_VDD_CORE
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MGMT_INLET_TEMP0
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/MGMT_INLET_TEMP1
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN1_1
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN1_2
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN2_1
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN2_2
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN3_1
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN3_2
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN4_1
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN4_2
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN5_1
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN5_2
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN6_1
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN6_2
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN7_1
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN7_2
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN8_1
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/ODM_FAN8_2
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/PSU1
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/PSU2
│ ├─/xyz/openbmc_project/inventory/system/chassis/BMC/PSU3
│ └─/xyz/openbmc_project/inventory/system/chassis/BMC/PSU4
└─/xyz/openbmc_project/inventory/system/powersupply
├─/xyz/openbmc_project/inventory/system/powersupply/CRPS1600W_1
├─/xyz/openbmc_project/inventory/system/powersupply/CRPS1600W_2
├─/xyz/openbmc_project/inventory/system/powersupply/CRPS1600W_3
└─/xyz/openbmc_project/inventory/system/powersupply/CRPS1600W_4

real 3m9.069s
user 0m0.490s
sys 0m0.123s

from entity-manager.

What hardware are you running this on? Is the EM JSON all upstreamed or do you have your own JSON you are loading? Are you able to share it if it isn’t upstreamed?

from entity-manager.

AST2500,the EM file is:
bmc_chassis.json
crps1600w_psu.json
fan12k8080_fan.json

from entity-manager.

oem_xxx type You can interpret it as xxx type

from entity-manager.

I see a number of logs, but given you're using a non upstreamed system on a fork, it's nearly impossible for anyone to debug this for you. One possibility is that something on your system is repeatedly calling the DBus ReScan() method, which is causing EM to rescan over and over. It's difficult to make any more guesses without being able to see the complete code, and being based on a fork.

from entity-manager.

AST2500,the EM file is:
bmc_chassis.json
crps1600w_psu.json
fan12k8080_fan.json

I don’t see anything obviously wrong here that would have itself cause performance issues as you’ve described. I will say that the probe statement in the chassis object is far too unspecified. Just looking for “BMC” is a lot less than desirable; certainly this never could be upstreamed in its current state. I would suggest you get your backplane eeprom to have more specific details in it.

from entity-manager.

I am based on that commit：
commit b0c7bd1 (tag: devtool-base, master)
Author: Zev Weiss [email protected]
Date: Tue Apr 19 17:58:01 2022 -0700

romed8hm3: add VDDCR_CPU warning & critical thresholds

These had been omitted initially while we were sorting out some
confusion with the VRM that provides this supply rail, but I forgot to
go back and add them after that was resolved.

Tested: warning & critical thresholds appear as expected on dbus and in
webui-vue on romed8hm3.

Signed-off-by: Zev Weiss <[email protected]>
Change-Id: I605c7813f70b5004f50be831eea4746e48a4a5bd

from entity-manager.