Hi Felixzhan= g,

<= /o:p>

Yes, you can= using op-power-control on X86 motherboard for sure.

<= /o:p>

Example abou= t using op-power-control:

systemctl li= st-dependencies obmc-host-start@0.target

<= /o:p>

obmc-host-st= art@0.target (Power ON)

-> mapper= -wait@-org-openbmc-control-chassis0.service

-> phosph= or-reset-host-reboot-attempts@0.service

-> obmc-h= ost-startmin@0.target

= -> mapper-wait@-org-openbmc-control-chassis0.service

= -> obmc-enable-host-watchdog@0.service

= -> phosphor-watchdog@poweron.service

= -> obmc-chassis-poweron@0.target

= -> op-power-start@0.service

= -> mapper-wait@-xyz-openbmc_p= roject-state-chassis0.service

= -> phosphor-fan-control-init@= 0.service

= -> phosphor-fan-monitor-init@= 0.service

= -> phosphor-fan-presence-tach= @0.service

<= /o:p>

BTW, here is= the list about the sequence of obmc-host-start@0.target fo= r you refer it.

When you pre= sss Power ON button from WebUI the state RequestedHostTransition change to = ON, what happens behind that is done by systemd units, roughly described as below:

1.= Host= state manager starts obmc-host-start@0.target

2.= The = above target requires obmc-host-startmin@0.target

3.= The = above target requires obmc-chassis-poweron@0.target and start_host@0.service

4.= o= bmc-chassis-poweron@0.target requires op-power-start@0.service and op-wait-power-on@0.service=

5.= o= p-power-start@0.service is to call the PowerControl service to DC on. And op-wait-power-on@0.se= rvice is to wait for PGood after DC on.

6.= Afte= r that (DC is on and PGood is OK), start_host@0.service is to start the host CPU.

<= /o:p>

Best regards= ,

Tim

From: = zhang_cy1989 [mailto:zhang_cy1989@163.com]
Sent: Thursday, December 26, 2019 10:22 AM
To: CS20 CHLi30 <CHLI30@nuvoton.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re:RE: systemctl start obmc-host-start@0.target fail

Dear,Tim=

Thank you for= guidance.

I will study = the dbus-monitor and the dependencies of obmc-host-start@0.target.

@CS20 CHLi30

I need ask you anot= her advice.

I use the romulus r= ecipes to build BMC firmware. And use this fw to the X86 motherboard + = AST2500.

The romulus is base= on openpower. And my platform is X86 motherboard.

Is it feasible that using romulus BMC= firmware to X86 motherboard, specially the power control part?<= span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:"Arial"= ,sans-serif;color:black">

Would you have bett= er suggestion?

Looking forward to = your replay.

Best Regards

Felixzhang

At 2019-12-26 09:34:09, "CS20 CHLi30"= ; <CHLI30@nuvoton.com> wrot= e:

Hi Felixz= hang,

About thi= s kind of systemd target start fail, you can use dbus-monitor to check target dependency more detail.

BTW, you = can also use systemctl list-dependecies o= bmc-host-start@0.target to get all related services.

For examp= le for using x86-power-control:=

system= ctl list-dependencies obmc-host-start@0.target

obmc-host-start@0.target (Power ON)

-> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service<= span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:"Arial"= ,sans-serif;color:black">

-> phosphor-r= eset-host-reboot-attempts@0.service

-> obmc-host-startmin@0.target<= /a>

&nb= sp;   -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service<= span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:"Arial"= ,sans-serif;color:black">

&nb= sp;   -> obmc-enable-host-wat= chdog@0.service

&nb= sp;   -> phosphor-watchdog@powe= ron.service

&nb= sp;   -> obmc-chassis-poweron@0.tar= get

&nb= sp;        -> intel-power-start@0.service<= /a>

&nb= sp;        -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service<= span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:"Arial"= ,sans-serif;color:black">

&nb= sp;        -> phosphor-fan-control= -init@0.service

&nb= sp;        -> phosphor-fan-monitor= -init@0.service

&nb= sp;        -> phosphor-fan-presen= ce-tach@0.service

Then you = should found that might some services doesn’t start normally and cause your obmc-ho= st-tart@0.target start fail.

Best rega= rds,

Tim

From: openbmc [mailto:openbmc-bounces+chli30=3Dnuvoton.com@lists.ozlabs.or= g] On Behalf Of zhang_cy1989
Sent: Wednesday, December 25, 2019 7:19 PM
To: openbmc@lists.ozlabs= .org
Subject: systemctl start obmc-host-start@0.target fail

Dear All

   On ast2500+x86 platform= , use the romulus bmc firmware, the detail information:

ID=3D"openbmc-phosphor"
NAME=3D"Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro= )"
VERSION=3D"2.7.0-0"
VERSION_ID=3D"2.7.0-0-gcb91a7773-dirty"
PRETTY_NAME=3D"Phosphor OpenBMC (Phosphor OpenBMC Project Reference= Distro) 2.7.0-0"
BUILD_ID=3D"2.7.0"
OPENBMC_TARGET_MACHINE=3D"romulus"

The BMC ip: 192.168.0.1

Remote Computer ip: 192.168.0.2

I use the ipmitool to communicate= with BMC:

ipmitool -I lanplus -H 192.168.0.1 -U ro= ot -P 0penBmc power on

And from the journalctl results, I= found those infromations:

......

-- The unit op-wait-power-on@0.service has entered the 'failed' state with result 'timeout'.
Nov 28 07:55:47 romulus systemd[1]: Failed to start Wait for Power0 to turn= on.
-- Subject: A start job for unit op-wait-power-on@0.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit op-wa= it-power-on@0.service has finished with a failure.
--
-- The job identifier is 906 and the job result is failed.
Nov 28 07:55:47 romulus systemd[1]: Dependency failed for Chassis0 (Power O= n).
-- Subject: A start job for unit obmc-chassis-poweron@0.target has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit ob= mc-chassis-poweron@0.target has finished with a failure.
--
-- The job identifier is 886 and the job result is dependency.
Nov 28 07:55:47 romulus systemd[1]: Dependency failed for Start Host0 Minim= um.
-- Subject: A start job for unit obmc-host-startmin@0.target has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit obmc= -host-startmin@0.target has finished with a failure.
--
-- The job identifier is 752 and the job result is dependency.
Nov 28 07:55:47 romulus systemd[1]: Dependency failed for Start Host0.
-- Subject: A start job for unit obmc-host-start@0.target has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit obmc-ho= st-start@0.target has finished with a failure.

Nov 28 08:24:09 romulus systemd[1]: obmc-host-start@0.target: J= ob obmc-host-start@0.target/start failed with result 'dependency'.
Nov 28 08:24:09 romulus systemd[1]: obmc-host-start@0.target: Triggering OnFailure=3D dependencies. Nov 28 08:24:10 romulus systemd[1]: obmc-host-startmin@0.target: Job obmc-host-startmin@0.target/start failed with result 'dependency'.
Nov 28 08:24:10 romulus systemd[1]: obmc-host-startmin@0.target: Triggering OnFailure=3D dependencies.
Nov 28 08:24:10 romulus systemd[1]: obmc-chassis-poweron@0.target: Job obmc-chassis-poweron@0.target/start failed with result 'dependency'. Nov 28 08:24:10 romulus systemd[1]: obmc-chassis-poweron@0.target: Triggering OnFailure=3D dependencies.

......

I alse do the following action:

systemctl start obmc-host-start@0.target

And alse get the similar fail result.

I don't how to debug this isuue.Could yo= u give me some suggestions?

Best Regards

Felixzhang

The privileged confidential information cont= ained 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 deliv= ery of the email to such a person, please kindly reply to the sender indica= ting this fact and delete all copies of it from your computer and network s= erver immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confiden= tial information of Nuvoton is strictly prohibited; and any information in = this email irrelevant to the official business of Nuvoton shall be deemed a= s neither given nor endorsed by Nuvoton.