<html><body><p><tt><font size="2">David Müller (ELSOFT AG) <d.mueller@elsoft.ch> wrote on 08/11/2017 09:47:42 AM:<br><br>> From: David Müller (ELSOFT AG) <d.mueller@elsoft.ch></font></tt><br><tt><font size="2">> To: Chris Austen <austenc@us.ibm.com></font></tt><br><tt><font size="2">> Cc: Andrew Jeffery <andrew@aj.id.au>, openbmc@lists.ozlabs.org</font></tt><br><tt><font size="2">> Date: 08/11/2017 09:47 AM</font></tt><br><tt><font size="2">> Subject: Re: Crashing Phosphor Settings Manager</font></tt><br><tt><font size="2">> <br>> Hello<br>> <br>> Thanks for the hint.<br>> <br>> Chris Austen wrote:<br>> <br>> > I don't think there is any one process that is responsible for <br>> > /org/openbmc/control. It is a parent of other processes though.<br>> > <br>> > org.openbmc.control.Bmc /org/openbmc/control/bmc0 <br>> > org.openbmc.control.Power /org/openbmc/control/power0 <br>> > org.openbmc.control.Chassis /org/openbmc/control/chassis0 <br>> > org.openbmc.control.BmcFlash /org/openbmc/control/flash<br>> > <br>> > So it appears not 1 of the 4 processes is starting up on the<br>> > evb-ast2500 build. That is not a bad thing though. The<br>> > org.openbmc.control (any org.openbmc really) is in violation of the<br>> > dbus spec and as such we have moved most services over to <br>> > xyz.openbmc_project. Seems like the evb-ast2500 is ready to have<br>> > the settings_manager.py from phosphor/settingd repository fixed up.<br>> > <br>> > So you can ignore that message and focus on the /xyz/openbmc/control <br>> > interfaces<br>> <br>> This should be "/xyz/openbmc_project/control", isn't it?<br></font></tt><br><tt><font size="2">oops yes... openbmc_project </font></tt><br><br><tt><font size="2">Chris </font></tt><br><br><tt><font size="2">> <br>> <br>> Dave<br>> <br></font></tt><BR>
</body></html>