All of lore.kernel.org
 help / color / mirror / Atom feed
* systemctl start obmc-host-start@0.target fail
@ 2019-12-25 11:18 zhang_cy1989
  2019-12-26  1:34 ` CS20 CHLi30
  0 siblings, 1 reply; 6+ messages in thread
From: zhang_cy1989 @ 2019-12-25 11:18 UTC (permalink / raw)
  To: openbmc

[-- Attachment #1: Type: text/plain, Size: 3153 bytes --]




Dear All
   On ast2500+x86 platform, use the romulus bmc firmware, the detail information:
ID="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="2.7.0-0"
VERSION_ID="2.7.0-0-gcb91a7773-dirty"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 2.7.0-0"
BUILD_ID="2.7.0"
OPENBMC_TARGET_MACHINE="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 root -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-wait-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 On).
-- 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 obmc-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 Minimum.
-- 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-host-start@0.target has finished with a failure.

Nov 28 08:24:09 romulus systemd[1]: obmc-host-start@0.target: Job 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= 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= 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= 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 you give me some suggestions?


Best Regards
Felixzhang










[-- Attachment #2: Type: text/html, Size: 4593 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: systemctl start obmc-host-start@0.target fail
  2019-12-25 11:18 systemctl start obmc-host-start@0.target fail zhang_cy1989
@ 2019-12-26  1:34 ` CS20 CHLi30
  2019-12-26  2:21   ` zhang_cy1989
  0 siblings, 1 reply; 6+ messages in thread
From: CS20 CHLi30 @ 2019-12-26  1:34 UTC (permalink / raw)
  To: zhang_cy1989, openbmc

[-- Attachment #1: Type: text/plain, Size: 5991 bytes --]

Hi Felixzhang,

About this 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 obmc-host-start@0.target to get all related services.

For example for using x86-power-control:
systemctl list-dependencies obmc-host-start@0.target

obmc-host-start@0.target (Power ON)
-> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service
-> phosphor-reset-host-reboot-attempts@0.service
-> obmc-host-startmin@0.target
     -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service
     -> obmc-enable-host-watchdog@0.service
     -> phosphor-watchdog@poweron.service
     -> obmc-chassis-poweron@0.target
          -> intel-power-start@0.service
          -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service
          -> phosphor-fan-control-init@0.service
          -> phosphor-fan-monitor-init@0.service
          -> phosphor-fan-presence-tach@0.service

Then you should found that might some services doesn't start normally and cause your obmc-host-tart@0.target start fail.

Best regards,
Tim
From: openbmc [mailto:openbmc-bounces+chli30=nuvoton.com@lists.ozlabs.org] 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="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="2.7.0-0"
VERSION_ID="2.7.0-0-gcb91a7773-dirty"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 2.7.0-0"
BUILD_ID="2.7.0"
OPENBMC_TARGET_MACHINE="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 root -P 0penBmc power on

 And from the journalctl results, I found those infromations:
......
-- The unit op-wait-power-on@0.service<mailto: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<mailto: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-wait-power-on@0.service<mailto:op-wait-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 On).
-- Subject: A start job for unit obmc-chassis-poweron@0.target<mailto:obmc-chassis-poweron@0.target> has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit obmc-chassis-poweron@0.target<mailto:obmc-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 Minimum.
-- Subject: A start job for unit obmc-host-startmin@0.target<mailto: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<mailto: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<mailto: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-host-start@0.target<mailto:obmc-host-start@0.target> has finished with a failure.
Nov 28 08:24:09 romulus systemd[1]: obmc-host-start@0.target<mailto:obmc-host-start@0.target>: Job obmc-host-start@0.target<mailto:obmc-host-start@0.target>/start failed with result 'dependency'.
Nov 28 08:24:09 romulus systemd[1]: obmc-host-start@0.target<mailto:obmc-host-start@0.target>: Triggering OnFailure= dependencies.
Nov 28 08:24:10 romulus systemd[1]: obmc-host-startmin@0.target<mailto:obmc-host-startmin@0.target>: Job obmc-host-startmin@0.target<mailto:obmc-host-startmin@0.target>/start failed with result 'dependency'.
Nov 28 08:24:10 romulus systemd[1]: obmc-host-startmin@0.target<mailto:obmc-host-startmin@0.target>: Triggering OnFailure= dependencies.
Nov 28 08:24:10 romulus systemd[1]: obmc-chassis-poweron@0.target<mailto:obmc-chassis-poweron@0.target>: Job obmc-chassis-poweron@0.target<mailto:obmc-chassis-poweron@0.target>/start failed with result 'dependency'.
Nov 28 08:24:10 romulus systemd[1]: obmc-chassis-poweron@0.target<mailto:obmc-chassis-poweron@0.target>: Triggering OnFailure= dependencies.
......

I alse do the following action:
systemctl start obmc-host-start@0.target<mailto:obmc-host-start@0.target>
And alse get the similar fail result.

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

Best Regards
Felixzhang








________________________________
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.

[-- Attachment #2: Type: text/html, Size: 21506 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re:RE: systemctl start obmc-host-start@0.target fail
  2019-12-26  1:34 ` CS20 CHLi30
@ 2019-12-26  2:21   ` zhang_cy1989
  2019-12-26  2:32     ` CS20 CHLi30
  0 siblings, 1 reply; 6+ messages in thread
From: zhang_cy1989 @ 2019-12-26  2:21 UTC (permalink / raw)
  To: CS20 CHLi30; +Cc: openbmc

[-- Attachment #1: Type: text/plain, Size: 5872 bytes --]

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 another advice.

 

  I use the romulus recipes 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?
 
  Would you have better suggestion?


  Looking forward to your replay.


 Best Regards
 Felixzhang




At 2019-12-26 09:34:09, "CS20 CHLi30" <CHLI30@nuvoton.com> wrote:

Hi Felixzhang,

 

About this 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 obmc-host-start@0.target to get all related services.

 

For example for using x86-power-control:

systemctl list-dependencies obmc-host-start@0.target

 

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

-> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service

-> phosphor-reset-host-reboot-attempts@0.service

-> obmc-host-startmin@0.target

     -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service

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

     -> phosphor-watchdog@poweron.service

     -> obmc-chassis-poweron@0.target

          -> intel-power-start@0.service

          -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service

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

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

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

 

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

 

Best regards,

Tim

From: openbmc [mailto:openbmc-bounces+chli30=nuvoton.com@lists.ozlabs.org] 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="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="2.7.0-0"
VERSION_ID="2.7.0-0-gcb91a7773-dirty"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 2.7.0-0"
BUILD_ID="2.7.0"
OPENBMC_TARGET_MACHINE="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 root -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-wait-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 On).
-- 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 obmc-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 Minimum.
-- 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-host-start@0.target has finished with a failure.

Nov 28 08:24:09 romulus systemd[1]: obmc-host-start@0.target: Job 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= 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= 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= 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 you give me some suggestions?

 

Best Regards

Felixzhang

 

 

 

 

 

 

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.

[-- Attachment #2: Type: text/html, Size: 17993 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* RE: Re:RE: systemctl start obmc-host-start@0.target fail
  2019-12-26  2:21   ` zhang_cy1989
@ 2019-12-26  2:32     ` CS20 CHLi30
  2019-12-26  3:09       ` zhang_cy1989
  0 siblings, 1 reply; 6+ messages in thread
From: CS20 CHLi30 @ 2019-12-26  2:32 UTC (permalink / raw)
  To: zhang_cy1989; +Cc: openbmc

[-- Attachment #1: Type: text/plain, Size: 11366 bytes --]

Hi Felixzhang,

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

Example about using op-power-control:
systemctl list-dependencies obmc-host-start@0.target<mailto:obmc-host-start@0.target>

obmc-host-start@0.target (Power ON)
-> mapper-wait@-org-openbmc-control-chassis0.service
-> phosphor-reset-host-reboot-attempts@0.service
-> obmc-host-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_project-state-chassis0.service
          -> phosphor-fan-control-init@0.service
          -> phosphor-fan-monitor-init@0.service
          -> phosphor-fan-presence-tach@0.service

BTW, here is the list about the sequence of obmc-host-start@0.target<mailto:obmc-host-start@0.target> for you refer it.
When you presss 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.      obmc-chassis-poweron@0.target requires op-power-start@0.service and op-wait-power-on@0.service
5.      op-power-start@0.service is to call the PowerControl service to DC on. And op-wait-power-on@0.service is to wait for PGood after DC on.
6.      After that (DC is on and PGood is OK), start_host@0.service is to start the host CPU.

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<mailto:obmc-host-start@0.target>.
 @CS20 CHLi30
  I need ask you another advice.

  I use the romulus recipes 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?

  Would you have better suggestion?

  Looking forward to your replay.

 Best Regards
 Felixzhang


At 2019-12-26 09:34:09, "CS20 CHLi30" <CHLI30@nuvoton.com<mailto:CHLI30@nuvoton.com>> wrote:
Hi Felixzhang,

About this 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 obmc-host-start@0.target<mailto:obmc-host-start@0.target> to get all related services.

For example for using x86-power-control:
systemctl list-dependencies obmc-host-start@0.target<mailto:obmc-host-start@0.target>

obmc-host-start@0.target<mailto:obmc-host-start@0.target> (Power ON)
-> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service<mailto:mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service>
-> phosphor-reset-host-reboot-attempts@0.service<mailto:phosphor-reset-host-reboot-attempts@0.service>
-> obmc-host-startmin@0.target<mailto:obmc-host-startmin@0.target>
     -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service<mailto:mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service>
     -> obmc-enable-host-watchdog@0.service<mailto:obmc-enable-host-watchdog@0.service>
     -> phosphor-watchdog@poweron.service<mailto:phosphor-watchdog@poweron.service>
     -> obmc-chassis-poweron@0.target<mailto:obmc-chassis-poweron@0.target>
          -> intel-power-start@0.service<mailto:intel-power-start@0.service>
          -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service<mailto:mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service>
          -> phosphor-fan-control-init@0.service<mailto:phosphor-fan-control-init@0.service>
          -> phosphor-fan-monitor-init@0.service<mailto:phosphor-fan-monitor-init@0.service>
          -> phosphor-fan-presence-tach@0.service<mailto:phosphor-fan-presence-tach@0.service>

Then you should found that might some services doesn't start normally and cause your obmc-host-tart@0.target<mailto:obmc-host-tart@0.target> start fail.

Best regards,
Tim
From: openbmc [mailto:openbmc-bounces+chli30=nuvoton.com@lists.ozlabs.org] On Behalf Of zhang_cy1989
Sent: Wednesday, December 25, 2019 7:19 PM
To: openbmc@lists.ozlabs.org<mailto:openbmc@lists.ozlabs.org>
Subject: systemctl start obmc-host-start@0.target<mailto:obmc-host-start@0.target> fail



Dear All
   On ast2500+x86 platform, use the romulus bmc firmware, the detail information:
ID="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="2.7.0-0"
VERSION_ID="2.7.0-0-gcb91a7773-dirty"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 2.7.0-0"
BUILD_ID="2.7.0"
OPENBMC_TARGET_MACHINE="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 root -P 0penBmc power on

 And from the journalctl results, I found those infromations:
......
-- The unit op-wait-power-on@0.service<mailto: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<mailto:op-wait-power-on@0.service> has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_systemd-2Ddevel&d=DwMGbg&c=ue8mO8zgC4VZ4q_aNVKt8G9MC01UFDmisvMR1k-EoDM&r=_vvS1tH9U_15yp1--_mdcWxVamV74LY4Xz5Zy4-7UIo&m=EhLiDsjPMBS98eeZEQG2UAHMPrvbvGb_OublwmQy2uc&s=UO9vddeGuzrgEFSgZkdgqCUEsjWHcXBofqYYlHxCNkM&e=>
--
-- A start job for unit op-wait-power-on@0.service<mailto:op-wait-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 On).
-- Subject: A start job for unit obmc-chassis-poweron@0.target<mailto:obmc-chassis-poweron@0.target> has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_systemd-2Ddevel&d=DwMGbg&c=ue8mO8zgC4VZ4q_aNVKt8G9MC01UFDmisvMR1k-EoDM&r=_vvS1tH9U_15yp1--_mdcWxVamV74LY4Xz5Zy4-7UIo&m=EhLiDsjPMBS98eeZEQG2UAHMPrvbvGb_OublwmQy2uc&s=UO9vddeGuzrgEFSgZkdgqCUEsjWHcXBofqYYlHxCNkM&e=>
--
-- A start job for unit obmc-chassis-poweron@0.target<mailto:obmc-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 Minimum.
-- Subject: A start job for unit obmc-host-startmin@0.target<mailto:obmc-host-startmin@0.target> has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_systemd-2Ddevel&d=DwMGbg&c=ue8mO8zgC4VZ4q_aNVKt8G9MC01UFDmisvMR1k-EoDM&r=_vvS1tH9U_15yp1--_mdcWxVamV74LY4Xz5Zy4-7UIo&m=EhLiDsjPMBS98eeZEQG2UAHMPrvbvGb_OublwmQy2uc&s=UO9vddeGuzrgEFSgZkdgqCUEsjWHcXBofqYYlHxCNkM&e=>
--
-- A start job for unit obmc-host-startmin@0.target<mailto: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<mailto:obmc-host-start@0.target> has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_systemd-2Ddevel&d=DwMGbg&c=ue8mO8zgC4VZ4q_aNVKt8G9MC01UFDmisvMR1k-EoDM&r=_vvS1tH9U_15yp1--_mdcWxVamV74LY4Xz5Zy4-7UIo&m=EhLiDsjPMBS98eeZEQG2UAHMPrvbvGb_OublwmQy2uc&s=UO9vddeGuzrgEFSgZkdgqCUEsjWHcXBofqYYlHxCNkM&e=>
--
-- A start job for unit obmc-host-start@0.target<mailto:obmc-host-start@0.target> has finished with a failure.
Nov 28 08:24:09 romulus systemd[1]: obmc-host-start@0.target<mailto:obmc-host-start@0.target>: Job obmc-host-start@0.target<mailto:obmc-host-start@0.target>/start failed with result 'dependency'.
Nov 28 08:24:09 romulus systemd[1]: obmc-host-start@0.target<mailto:obmc-host-start@0.target>: Triggering OnFailure= dependencies.
Nov 28 08:24:10 romulus systemd[1]: obmc-host-startmin@0.target<mailto:obmc-host-startmin@0.target>: Job obmc-host-startmin@0.target<mailto:obmc-host-startmin@0.target>/start failed with result 'dependency'.
Nov 28 08:24:10 romulus systemd[1]: obmc-host-startmin@0.target<mailto:obmc-host-startmin@0.target>: Triggering OnFailure= dependencies.
Nov 28 08:24:10 romulus systemd[1]: obmc-chassis-poweron@0.target<mailto:obmc-chassis-poweron@0.target>: Job obmc-chassis-poweron@0.target<mailto:obmc-chassis-poweron@0.target>/start failed with result 'dependency'.
Nov 28 08:24:10 romulus systemd[1]: obmc-chassis-poweron@0.target<mailto:obmc-chassis-poweron@0.target>: Triggering OnFailure= dependencies.
......

I alse do the following action:
systemctl start obmc-host-start@0.target<mailto:obmc-host-start@0.target>
And alse get the similar fail result.

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

Best Regards
Felixzhang








________________________________
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.




________________________________
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.

[-- Attachment #2: Type: text/html, Size: 48600 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re:RE: Re:RE: systemctl start obmc-host-start@0.target fail
  2019-12-26  2:32     ` CS20 CHLi30
@ 2019-12-26  3:09       ` zhang_cy1989
  2020-01-06 13:20         ` Deng Tyler
  0 siblings, 1 reply; 6+ messages in thread
From: zhang_cy1989 @ 2019-12-26  3:09 UTC (permalink / raw)
  To: CS20 CHLi30; +Cc: openbmc

[-- Attachment #1: Type: text/plain, Size: 8660 bytes --]

Dear Tim
  Thanks a milion.
  The infromation is very useful for me.


  Thank you again for your prompt reply.

 

  Best Regards


Felix

在 2019-12-26 10:32:54,"CS20 CHLi30" <CHLI30@nuvoton.com> 写道:

Hi Felixzhang,

 

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

 

Example about using op-power-control:

systemctl list-dependencies obmc-host-start@0.target

 

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

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

-> phosphor-reset-host-reboot-attempts@0.service

-> obmc-host-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_project-state-chassis0.service

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

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

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

 

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

When you presss 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.      obmc-chassis-poweron@0.target requires op-power-start@0.service and op-wait-power-on@0.service

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

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

 

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 another advice.

 

  I use the romulus recipes 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?

 

  Would you have better suggestion?

 

  Looking forward to your replay.

 

 Best Regards

 Felixzhang

 

At 2019-12-26 09:34:09, "CS20 CHLi30" <CHLI30@nuvoton.com> wrote:

Hi Felixzhang,

 

About this 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 obmc-host-start@0.target to get all related services.

 

For example for using x86-power-control:

systemctl list-dependencies obmc-host-start@0.target

 

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

-> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service

-> phosphor-reset-host-reboot-attempts@0.service

-> obmc-host-startmin@0.target

     -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service

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

     -> phosphor-watchdog@poweron.service

     -> obmc-chassis-poweron@0.target

          -> intel-power-start@0.service

          -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service

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

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

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

 

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

 

Best regards,

Tim

From: openbmc [mailto:openbmc-bounces+chli30=nuvoton.com@lists.ozlabs.org] 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="openbmc-phosphor"
NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
VERSION="2.7.0-0"
VERSION_ID="2.7.0-0-gcb91a7773-dirty"
PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 2.7.0-0"
BUILD_ID="2.7.0"
OPENBMC_TARGET_MACHINE="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 root -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-wait-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 On).
-- 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 obmc-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 Minimum.
-- 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-host-start@0.target has finished with a failure.

Nov 28 08:24:09 romulus systemd[1]: obmc-host-start@0.target: Job 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= 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= 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= 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 you give me some suggestions?

 

Best Regards

Felixzhang

 

 

 

 

 

 

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.

 

 

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.

[-- Attachment #2: Type: text/html, Size: 41555 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: RE: Re:RE: systemctl start obmc-host-start@0.target fail
  2019-12-26  3:09       ` zhang_cy1989
@ 2020-01-06 13:20         ` Deng Tyler
  0 siblings, 0 replies; 6+ messages in thread
From: Deng Tyler @ 2020-01-06 13:20 UTC (permalink / raw)
  To: zhang_cy1989; +Cc: CS20 CHLi30, openbmc

[-- Attachment #1: Type: text/plain, Size: 15309 bytes --]

Hi all:
    Thanks for your sharing and that's really helpful. I still have a
question for chassis power on/off.  I add service to run poweron shell
while obmc-host-start@t0.target triggered and run poweroff shell while
obms-host-shutdown@0.target triggered. After issuing chassis power on
command, my platform can power on system but power off after few seconds. I
check journalctl as below:
Jan 06 11:05:39   systemd[1]: Starting Start Watchdog0...
Jan 06 11:05:39   systemd[1]: Starting Assert bmc_booted LED...
Jan 06 11:05:39   phosphor-watchdog[352]: watchdog: enabled and started
Jan 06 11:05:39   phosphor-ledmanager[222]: [[0;1;31m[[0;1;39m[[0;1;31mNo
service providers for physical LED[[0m
Jan 06 11:05:39   systemd[1]: Started Start Watchdog0.
Jan 06 11:05:39   systemd[1]: Started Assert bmc_booted LED.
Jan 06 11:05:39   systemd[1]: Reached target Start Host0 Minimum.
Jan 06 11:05:39   systemd[1]: Reached target Start Host0.
Jan 06 11:05:39   systemd[1]: Startup finished in 4.527s (kernel) + 1min
32.169s (userspace) = 1min 36.697s.
Jan 06 11:05:39   phosphor-host-state-manager[315]: Received signal that
host is running
Jan 06 11:05:39   phosphor-host-state-manager[315]: Change to Host State
Jan 06 11:05:39   phosphor-timemanager[320]: Changing time settings is
*deferred* now
Jan 06 11:06:09   phosphor-watchdog[352]: watchdog: Timed out
Jan 06 11:06:09   systemd[1]: unit_file_find_fragment:
obmc-host-timeout@.target+0
→ obmc-host-timeout@0.target
Jan 06 11:06:09   phosphor-watchdog[352]: watchdog: disabled
Jan 06 11:06:09   systemd[1]: Reached target Quiesce Target.
Jan 06 11:06:09   systemd[1]: Reached target Host instance 0 timed out
refreshing Watchdog.
Jan 06 11:06:09   systemd[1]: Stopping Phosphor poweron watchdog...
Jan 06 11:06:09   systemd[1]: phosphor-watchdog@poweron.service: Succeeded.
Jan 06 11:06:09   systemd[1]: Stopped Phosphor poweron watchdog.
Jan 06 11:06:09   phosphor-host-state-manager[315]: Auto reboot enabled,
rebooting
Jan 06 11:06:09   phosphor-host-state-manager[315]: Beginning reboot...
Jan 06 11:06:09   phosphor-host-state-manager[315]: Host State transaction
request
Jan 06 11:06:09   systemd[1]: unit_file_find_fragment:
obmc-host-reboot@.target+0
→ obmc-host-reboot@0.target
Jan 06 11:06:09   systemd[1]: unit_file_find_fragment:
obmc-host-shutdown@.target+0
→ obmc-host-shutdown@0.target
Jan 06 11:06:09   systemd[1]: unit_file_find_fragment:
obmc-host-stopping@.target+0
→ obmc-host-stopping@0.target
Jan 06 11:06:09   systemd[1]: unit_file_find_fragment:
obmc-host-stopped@.target+0
→ obmc-host-stopped@0.target
Jan 06 11:06:09   systemd[1]: unit_file_find_fragment:
obmc-power-stop-pre@.target+0
→ obmc-power-stop-pre@0.target
Jan 06 11:06:09   systemd[1]: unit_file_find_fragment:
obmc-host-stop-pre@.target+0
→ obmc-host-stop-pre@0.target
Jan 06 11:06:09   systemd[1]: Created slice
system-phosphor\x2dreboot\x2dhost.slice.
Jan 06 11:06:09   systemd[1]: Reached target Chassis0 (Power Off).
Jan 06 11:06:09   systemd[1]: Stopped target Start Host0.
Jan 06 11:06:09   systemd[1]: Stopped target Start Host0 Minimum.
Jan 06 11:06:09   systemd[1]: Reached target Stop Host0 (Pre).
Jan 06 11:06:09   systemd[1]: Stopped target Host instance 0 timed out
refreshing Watchdog.
Jan 06 11:06:09   systemd[1]: Stopped target Quiesce Target.
Jan 06 11:06:09   systemd[1]: Starting Configure GPIOs for Host Power
Control...
Jan 06 11:06:09   systemd[1]: Starting Wait for /org/openbmc/HostIpmi/1...
Jan 06 11:06:09   systemd[1]: Started Reboot host0.
Jan 06 11:06:09   init_once.sh[404]: init_once.sh
Jan 06 11:06:09   phosphor-chassis-state-manager[290]: Received signal that
power OFF is complete
Jan 06 11:06:09   phosphor-chassis-state-manager[290]: Change to Chassis
Power State
Jan 06 11:06:09   systemd[1]: Started Configure GPIOs for Host Power
Control.
Jan 06 11:06:09   systemd[1]: Starting Stop Host...
Jan 06 11:06:09   poweroff.sh[408]: out -> poweroff

The power on process suspended by phosphor-watchdog timeout. I have no idea
to clear watchdog timer. Could you provide any suggestion for this
situation? Thanks.

Tyler.

zhang_cy1989 <zhang_cy1989@163.com> 於 2019年12月26日 週四 上午11:11寫道:

> Dear Tim
>   Thanks a milion.
>   The infromation is very useful for me.
>
>   Thank you again for your prompt reply.
>
>   Best Regards
>
> Felix
> 在 2019-12-26 10:32:54,"CS20 CHLi30" <CHLI30@nuvoton.com> 写道:
>
> Hi Felixzhang,
>
>
>
> Yes, you can using op-power-control on X86 motherboard for sure.
>
>
>
> Example about using op-power-control:
>
> systemctl list-dependencies obmc-host-start@0.target
>
>
>
> obmc-host-start@0.target (Power ON)
>
> -> mapper-wait@-org-openbmc-control-chassis0.service
>
> -> phosphor-reset-host-reboot-attempts@0.service
>
> -> obmc-host-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_project-state-chassis0.service
>
>           -> phosphor-fan-control-init@0.service
>
>           -> phosphor-fan-monitor-init@0.service
>
>           -> phosphor-fan-presence-tach@0.service
>
>
>
> BTW, here is the list about the sequence of obmc-host-start@0.target for
> you refer it.
>
> When you presss 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.      *obmc-chassis-poweron@0.target* requires
> *op-power-start@0.service* and *op-wait-power-on@0.service*
>
> 5.      *op-power-start@0.service* is to call the PowerControl service to
> DC on. And *op-wait-power-on@0.service* is to wait for PGood after DC on.
>
> 6.      After that (DC is on and PGood is OK), *start_host@0.service* is
> to start the host CPU.
>
>
>
> 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 another advice.
>
>
>
>   I use the romulus recipes 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?*
>
>
>
>   Would you have better suggestion?
>
>
>
>   Looking forward to your replay.
>
>
>
>  Best Regards
>
>  Felixzhang
>
>
>
> At 2019-12-26 09:34:09, "CS20 CHLi30" <CHLI30@nuvoton.com> wrote:
>
> Hi Felixzhang,
>
>
>
> About this 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
> obmc-host-start@0.target <obmc-host-start@0.target>* to get all related
> services.
>
>
>
> For example for using x86-power-control:
>
> *systemctl list-dependencies obmc-host-start@0.target
> <obmc-host-start@0.target>*
>
>
>
> obmc-host-start@0.target (Power ON)
>
> -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service
>
> -> phosphor-reset-host-reboot-attempts@0.service
>
> -> obmc-host-startmin@0.target
>
>      -> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service
>
>      -> obmc-enable-host-watchdog@0.service
>
>      -> phosphor-watchdog@poweron.service
>
>      -> obmc-chassis-poweron@0.target
>
>           -> intel-power-start@0.service
>
>           ->
> mapper-wait@-xyz-openbmc_project-Chassis-Control-Power0.service
>
>           -> phosphor-fan-control-init@0.service
>
>           -> phosphor-fan-monitor-init@0.service
>
>           -> phosphor-fan-presence-tach@0.service
>
>
>
> Then you should found that might some services doesn’t start normally and
> cause your obmc-host-tart@0.target start fail.
>
>
>
> Best regards,
>
> Tim
>
> *From:* openbmc [
> mailto:openbmc-bounces+chli30=nuvoton.com@lists.ozlabs.org
> <openbmc-bounces+chli30=nuvoton.com@lists.ozlabs.org>] *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="openbmc-phosphor"*
> *NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"*
> *VERSION="2.7.0-0"*
> *VERSION_ID="2.7.0-0-gcb91a7773-dirty"*
> *PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)
> 2.7.0-0"*
> *BUILD_ID="2.7.0"*
> *OPENBMC_TARGET_MACHINE="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 root -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
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_systemd-2Ddevel&d=DwMGbg&c=ue8mO8zgC4VZ4q_aNVKt8G9MC01UFDmisvMR1k-EoDM&r=_vvS1tH9U_15yp1--_mdcWxVamV74LY4Xz5Zy4-7UIo&m=EhLiDsjPMBS98eeZEQG2UAHMPrvbvGb_OublwmQy2uc&s=UO9vddeGuzrgEFSgZkdgqCUEsjWHcXBofqYYlHxCNkM&e=>
> --
> -- A start job for unit op-wait-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
> On).
> -- 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
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_systemd-2Ddevel&d=DwMGbg&c=ue8mO8zgC4VZ4q_aNVKt8G9MC01UFDmisvMR1k-EoDM&r=_vvS1tH9U_15yp1--_mdcWxVamV74LY4Xz5Zy4-7UIo&m=EhLiDsjPMBS98eeZEQG2UAHMPrvbvGb_OublwmQy2uc&s=UO9vddeGuzrgEFSgZkdgqCUEsjWHcXBofqYYlHxCNkM&e=>
> --
> -- A start job for unit obmc-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
> Minimum.
> -- 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
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_systemd-2Ddevel&d=DwMGbg&c=ue8mO8zgC4VZ4q_aNVKt8G9MC01UFDmisvMR1k-EoDM&r=_vvS1tH9U_15yp1--_mdcWxVamV74LY4Xz5Zy4-7UIo&m=EhLiDsjPMBS98eeZEQG2UAHMPrvbvGb_OublwmQy2uc&s=UO9vddeGuzrgEFSgZkdgqCUEsjWHcXBofqYYlHxCNkM&e=>
> --
> -- 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
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_systemd-2Ddevel&d=DwMGbg&c=ue8mO8zgC4VZ4q_aNVKt8G9MC01UFDmisvMR1k-EoDM&r=_vvS1tH9U_15yp1--_mdcWxVamV74LY4Xz5Zy4-7UIo&m=EhLiDsjPMBS98eeZEQG2UAHMPrvbvGb_OublwmQy2uc&s=UO9vddeGuzrgEFSgZkdgqCUEsjWHcXBofqYYlHxCNkM&e=>
> --
> -- A start job for unit obmc-host-start@0.target has finished with a
> failure.
>
> Nov 28 08:24:09 romulus systemd[1]: obmc-host-start@0.target: Job
> 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= 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= 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= dependencies.
>
> ......
>
>
>
> I alse do the following action:
>
> *systemctl start obmc-host-start@0.target <obmc-host-start@0.target> *
>
> And alse get the similar fail result.
>
>
>
> I don't how to debug this isuue.Could you give me some suggestions?
>
>
>
> Best Regards
>
> Felixzhang
>
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------
>
> 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.
>
>
>
>
> ------------------------------
> 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.
>
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 40194 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2020-01-06 13:21 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-25 11:18 systemctl start obmc-host-start@0.target fail zhang_cy1989
2019-12-26  1:34 ` CS20 CHLi30
2019-12-26  2:21   ` zhang_cy1989
2019-12-26  2:32     ` CS20 CHLi30
2019-12-26  3:09       ` zhang_cy1989
2020-01-06 13:20         ` Deng Tyler

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.