Re:RE: systemctl start obmc-host-start@0.target fail

[zhang_cy1989 <zhang_cy1989@163.com>]

[-- 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 --]