All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhang_cy1989 <zhang_cy1989@163.com>
To: openbmc@lists.ozlabs.org
Subject: systemctl start obmc-host-start@0.target fail
Date: Wed, 25 Dec 2019 19:18:49 +0800 (CST)	[thread overview]
Message-ID: <6d26931a.d7c4.16f3cc7df52.Coremail.zhang_cy1989@163.com> (raw)

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

             reply	other threads:[~2019-12-25 11:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-25 11:18 zhang_cy1989 [this message]
2019-12-26  1:34 ` systemctl start obmc-host-start@0.target fail 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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6d26931a.d7c4.16f3cc7df52.Coremail.zhang_cy1989@163.com \
    --to=zhang_cy1989@163.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.