[phosphor-state-manager] Error reading HostFirmware condition, error: sd_bus_call: org.freedesktop.DBus.Error.ServiceUnknown
Jordan Chang
jordan.chang at ufispace.com
Tue Apr 26 20:32:14 AEST 2022
Hi Tim,
My busctl commands of Control.Host service are shown in below.
root at siad:~# busctl introspect xyz.openbmc_project.Control.Host
/xyz/openbmc_project/control/host0
*Failed to get all properties on interface
xyz.openbmc_project.Condition.HostFirmware: The name is not activatable*
root at siad:~# busctl get-property xyz.openbmc_project.Control.Host
/xyz/openbmc_project/control/host
xyz.openbmc_project.Condition.HostFirmware CurrentFirmwareCondition
*Failed to get property CurrentFirmwareCondition on interface
xyz.openbmc_project.Condition.HostFirmware: The name is not activatable*
I will keep tracing the process of how xyz.openbmc_project.Control.Host
works. if there is any further progress I will let you know. Thanks for
sharing.
Best regards,
Jordan
CHLI30 at nuvoton.com <CHLI30 at nuvoton.com> 於 2022年4月26日 週二 下午12:19寫道:
> Hi Jordan,
>
> May I know your busctl introspect about Control.Host?
>
>
>
> I try my platform to introspect Control.Host and I got failed to get
> property on interface Condition.HostFirmware.
>
> root at olympus-nuvoton-spi:~# busctl introspect
> xyz.openbmc_project.Control.Host /xyz/openbmc_project/control/host0
>
> *Failed to get all properties on interface
> xyz.openbmc_project.Condition.HostFirmware: The name is not activatable*
>
>
>
> However, I also try to get property CurrentFirmwareCondition, but result
> is fail as below:
>
> busctl get-property xyz.openbmc_project.Control.Host
> /xyz/openbmc_project/control/host0
> xyz.openbmc_project.Condition.HostFirmware CurrentFirmwareCondition
>
> *Failed to get property CurrentFirmwareCondition on interface
> xyz.openbmc_project.Condition.HostFirmware: The name is not activatable*
>
>
>
> Seems need to implement oem mechanism to handle the interface
> xyz.openbmc_project.Condition.HostFirmware then fix this error.
>
> xyz.openbmc_project.Control.Host is implemented in phosphor-host-ipmid.
> Might be need to implement oem in this repo.
>
> I still try to find more. If there is any finding, I will update it.
> Thanks.
>
>
>
> Best regards,
>
> Tim
>
>
>
> *From:* Jordan Chang <jordan.chang at ufispace.com>
> *Sent:* Tuesday, April 26, 2022 9:44 AM
> *To:* CS20 CHLi30 <CHLI30 at nuvoton.com>
> *Cc:* openbmc at lists.ozlabs.org
> *Subject:* Re: [phosphor-state-manager] Error reading HostFirmware
> condition, error: sd_bus_call: org.freedesktop.DBus.Error.ServiceUnknown
>
>
>
> Hi Tim,
>
> Thank you for your reply. Actually, I am wondering how did
> *xyz.openbmc_project.Control.Host* service get the HostFirmwareCondition.
> How could I get the
>
> HostFirmwareCondition via this service? Any comments or suggestions would
> be appreciated.
>
>
>
> Best regards,
>
> Jordan
>
>
>
> CHLI30 at nuvoton.com <CHLI30 at nuvoton.com> 於 2022年4月26日 週二 上午8:06寫道:
>
> Hi Jordan,
>
> According your busctl test command that you can get
> CurrentFirmwareCondition property currently.
>
> Here, the service is xyz.openbmc_project.State.HostCondition.Gpio and path
> is /xyz/openbmc_project/Gpios/host0.
>
>
>
> root at siad:~# busctl get-property *xyz.openbmc_project.State.HostCondition.Gpio
> * */xyz/openbmc_project/Gpios/host0*
> xyz.openbmc_project.Condition.HostFirmware CurrentFirmwareCondition
>
> s "xyz.openbmc_project.Condition.HostFirmware.FirmwareCondition.Running"
>
>
>
> However, your error log seems using wrong service and path to get this
> CurrentFirmwareCondition property.
>
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
> *path=/xyz/openbmc_project/control/host0*
>
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
> *services=xyz.openbmc_project.Control.Host*
>
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Error reading
> HostFirmware condition, error: sd_bus_call:
> org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable,
> service: xyz.openbmc_project.Control.Host path:
> /xyz/openbmc_project/control/host0
>
>
>
> If you change path and services as your busctl test command that might be
> fixed your issue.
>
> Hopefully, I didn’t misunderstand your question. Thanks.
>
>
>
> Best regards,
>
> Tim
>
>
>
> *From:* openbmc <openbmc-bounces+chli30=nuvoton.com at lists.ozlabs.org> *On
> Behalf Of *Jordan Chang
> *Sent:* Monday, April 18, 2022 6:31 PM
> *To:* openbmc at lists.ozlabs.org
> *Subject:* [phosphor-state-manager] Error reading HostFirmware condition,
> error: sd_bus_call: org.freedesktop.DBus.Error.ServiceUnknown
>
>
>
> Hi Sir/Madam,
> I am implementing the power control mechanisms for my platform, and
> encounter the problem in below:
> *phosphor-host-state-manager[341]: Error reading HostFirmware condition,
> error: sd_bus_call: org.freedesktop.DBus.Error.ServiceUnknown: The name is
> not activatable, service: xyz.openbmc_project.Control.Host path:
> /xyz/openbmc_project/control/host0*
>
>
>
> I am using the host0-ready gpio pin to determine the HostFirmwareCondition
> is running or not. However, the service
> *xyz.openbmc_project.State.Host.HostState* could not be established since
> the dbus call method of *xyz.openbmc_project.Control.Host *returns an
> error. Therefore, I have printed some debug messages starting with Ufi to
> ensure the xyz.openbmc_project.State.HostCondition.Gpio service is involved
> in phosphor-host-state-manager. Not sure why the bus call function of *xyz.openbmc_project.Control.Host
> service* failed. Which packages or settings should I configure to enable
> this service? Could someone give me some instructions or suggestions?
> Thank you!
>
>
> ```
>
> root at siad:~# obmcutil state
> CurrentBMCState : xyz.openbmc_project.State.BMC.BMCState.NotReady
> CurrentPowerState : xyz.openbmc_project.State.Chassis.PowerState.On
> Error finding '/xyz/openbmc_project/state/host0' service: Input/output
> error
>
>
>
>
> ---------------------------------------------------------------------------------------------------------------------------
>
> root at siad:~# busctl call xyz.openbmc_project.ObjectMapper
> /xyz/openbmc_project /object_mapper xyz.openbmc_project.ObjectMapper
> GetSubTree sias "" 0 1 "xyz.op enbmc_project.Condition.HostFirmware"
> a{sa{sas}} 2 "/xyz/openbmc_project/Gpios/host0" 1
> "xyz.openbmc_project.State.Hos tCondition.Gpio" 4
> "org.freedesktop.DBus.Introspectable" "org.freedesktop.DBus.P eer"
> "org.freedesktop.DBus.Properties" "xyz.openbmc_project.Condition.HostFirmwa
> re" "/xyz/openbmc_project/control/host0" 1
> "xyz.openbmc_project.Control.Host" 5 "org.freedesktop.DBus.Introspectable"
> "org.freedesktop.DBus.Peer" "org.freedeskt op.DBus.Properties"
> "xyz.openbmc_project.Condition.HostFirmware" "xyz.openbmc_pr
> oject.Control.Host"
>
>
>
>
> ---------------------------------------------------------------------------------------------------------------------------
>
> root at siad:~# busctl get-property
> xyz.openbmc_project.State.HostCondition.Gpio
> /xyz/openbmc_project/Gpios/host0
> xyz.openbmc_project.Condition.HostFirmware CurrentFirmwareCondition
> s "xyz.openbmc_project.Condition.HostFirmware.FirmwareCondition.Running"
>
>
>
>
> ---------------------------------------------------------------------------------------------------------------------------
>
> root at siad:~# journalctl | grep -i phosphor-host-state-manager
> Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Check if host is
> running
> Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Ufi:
> mapper1=/xyz/openbmc_project/Gpios/host0
> Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Ufi:
> mapper1=/xyz/openbmc_project/control/host0
> Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Ufi:
> mapper2=xyz.openbmc_project.State.HostCondition.Gpio
> Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Ufi:
> mapper2=xyz.openbmc_project.Control.Host
> Apr 18 08:19:14 siad phosphor-host-state-manager[341]: terminate called
> after throwing an instance of 'sdbusplus::exception::SdBusError'
> Apr 18 08:19:14 siad phosphor-host-state-manager[341]: what():
> sd_bus_call: org.freedesktop.DBus.Error.ServiceUnknown: The name is not
> activatable
> Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Ufi:
> path=/xyz/openbmc_project/control/host0
> Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Ufi:
> services=xyz.openbmc_project.Control.Host
> Apr 18 08:19:14 siad phosphor-host-state-manager[341]: Error reading
> HostFirmware condition, error: sd_bus_call:
> org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable,
> service: xyz.openbmc_project.Control.Host path:
> /xyz/openbmc_project/control/host0
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Check if host is
> running
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
> mapper1=/xyz/openbmc_project/Gpios/host0
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
> mapper1=/xyz/openbmc_project/control/host0
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
> mapper2=xyz.openbmc_project.State.HostCondition.Gpio
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
> mapper2=xyz.openbmc_project.Control.Host
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: terminate called
> after throwing an instance of 'sdbusplus::exception::SdBusError'
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: what():
> sd_bus_call: org.freedesktop.DBus.Error.ServiceUnknown: The name is not
> activatable
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
> path=/xyz/openbmc_project/control/host0
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
> services=xyz.openbmc_project.Control.Host
> Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Error reading
> HostFirmware condition, error: sd_bus_call:
> org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable,
> service: xyz.openbmc_project.Control.Host path:
> /xyz/openbmc_project/control/host0
>
>
>
> ```
>
> Best regards,
> Jordan Chang
>
>
>
> ******************************
>
> This e-mail is confidential. If you are not the intended recipient, you
> must not disclose, distribute or use the information in it as this could be
> a breach of confidentiality.If you have received this message in error,
> please advise us immediately by return e-mail and delete the document. The
> address from which this message has been sent is strictly for business mail
> only and the company reserves the right to monitor the contents of
> communications and take action where and when it is deemed necessary.
>
> Thank you for your co-operation.
> ------------------------------
>
> The privileged confidential information contained in this email is
> intended for use only by the addressees as indicated by the original sender
> of this email. If you are not the addressee indicated in this email or are
> not responsible for delivery of the email to such a person, please kindly
> reply to the sender indicating this fact and delete all copies of it from
> your computer and network server immediately. Your cooperation is highly
> appreciated. It is advised that any unauthorized use of confidential
> information of Nuvoton is strictly prohibited; and any information in this
> email irrelevant to the official business of Nuvoton shall be deemed as
> neither given nor endorsed by Nuvoton.
>
>
>
> ******************************
>
> This e-mail is confidential. If you are not the intended recipient, you
> must not disclose, distribute or use the information in it as this could be
> a breach of confidentiality.If you have received this message in error,
> please advise us immediately by return e-mail and delete the document. The
> address from which this message has been sent is strictly for business mail
> only and the company reserves the right to monitor the contents of
> communications and take action where and when it is deemed necessary.
>
> Thank you for your co-operation.
> ------------------------------
> The privileged confidential information contained in this email is
> intended for use only by the addressees as indicated by the original sender
> of this email. If you are not the addressee indicated in this email or are
> not responsible for delivery of the email to such a person, please kindly
> reply to the sender indicating this fact and delete all copies of it from
> your computer and network server immediately. Your cooperation is highly
> appreciated. It is advised that any unauthorized use of confidential
> information of Nuvoton is strictly prohibited; and any information in this
> email irrelevant to the official business of Nuvoton shall be deemed as
> neither given nor endorsed by Nuvoton.
>
--
******************************
This e-mail is confidential. If you are not
the intended recipient, you must not disclose, distribute or use the
information in it as this could be a breach of confidentiality.If you have
received this message in error, please advise us immediately by return
e-mail and delete the document. The address from which this message has
been sent is strictly for business mail only and the company reserves the
right to monitor the contents of communications and take action where and
when it is deemed necessary.
Thank you for your co-operation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20220426/42b73231/attachment-0001.htm>
More information about the openbmc
mailing list