All of lore.kernel.org
 help / color / mirror / Atom feed
From: Landon <cld795@163.com>
To: "patrick@stwcx.xyz" <patrick@stwcx.xyz>,
	 "jason.m.bills@linux.intel.com" <jason.m.bills@linux.intel.com>,
	 "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	 "a.kartashev@yadro.com" <a.kartashev@yadro.com>,
	 "fercerpav@gmail.com" <fercerpav@gmail.com>
Subject: OpenBMC state manager problem
Date: Wed, 15 Jun 2022 15:42:08 +0800 (GMT+08:00)	[thread overview]
Message-ID: <6535c860.faad.18166500335.Coremail.cld795@163.com> (raw)
In-Reply-To: <7064f556.7192.1815fef31c6.Coremail.cld795@163.com>

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





---- Replied Message ----
| From | Landon<cld795@163.com> |
| Date | 6/14/2022 09:58 |
| To | patrick@stwcx.xyz<patrick@stwcx.xyz> ,
jason.m.bills@linux.intel.com<jason.m.bills@linux.intel.com> ,
openbmc@lists.ozlabs.org<openbmc@lists.ozlabs.org> |
| Subject | OpenBMC state manager problem |


hello~
now I use aspeed ast2600 openbmc.
At first, I set pwer state command: but failed!

root@ast2600-emmc:~# busctl set-property xyz.openbmc_project.State.Host /xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host CurrentHostState s "xyz.openbmc_project.State.Host.HostState.Off" Failed to set property CurrentHostState on interface xyz.openbmc_project.State.Host: The name is not activatable
root@ast2600-emmc:~# busctl set-property xyz.openbmc_project.State.Host /xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host CurrentHostState s "xyz.openbmc_project.State.Host.HostState.Running" Failed to set property CurrentHostState on interface xyz.openbmc_project.State.Host: The name is not activatable
so I modify the "\meta-aspeed-sdk\meta-ast2600-sdk\conf\machine\ast2600-emmc.conf", remove the "x86-power-control"...  :
PREFERRED_PROVIDER_virtual/obmc-system-mgmt = "packagegroup-aspeed-obmc"
PREFERRED_PROVIDER_virtual/obmc-host-ipmi-hw = "phosphor-ipmi-kcs"
# I remove the 2 lines :
#VIRTUAL-RUNTIME_obmc-host-state-manager ?= "x86-power-control"
#VIRTUAL-RUNTIME_obmc-chassis-state-manager ?= "x86-power-control"
EXTRA_IMAGEDEPENDS:append = "\
   aspeed-image-recoveryuart \
   aspeed-image-emmcboot \


After,  I set pwer state command OK :
root@ast2600-emmc:~# busctl set-property xyz.openbmc_project.State.Host /xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host CurrentHostState s "xyz.openbmc_project.State.Host.HostState.Off" root@ast2600-emmc:~# busctl set-property xyz.openbmc_project.State.Host /xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host CurrentHostState s "xyz.openbmc_project.State.Host.HostState.Running"
but, after I update openbmc for the lastest the version, it can't enter the system :
[    8.025630] systemd[1]: Hostname set to .
[    8.034897] systemd[1]: Initializing machine ID from random generator.
[    8.182435] systemd-sysv-generator[179]: SysV service '/etc/init.d/bmc-watchdog' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    8.210534] systemd-sysv-generator[179]: SysV service '/etc/init.d/ipmidetectd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    8.238552] systemd-sysv-generator[179]: SysV service '/etc/init.d/ipmiseld' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    8.783127] systemd[1]: Failed to put bus name to hashmap: File exists
[    8.790587] systemd[1]: xyz.openbmc_project.State.Host@0.service: Two services allocated for the same bus name xyz.openbmc_project.State.Host0, refusing operation.
[    9.136389] systemd[1]: /lib/systemd/system/host-poweron.service:3: Failed to add dependency on obmc-chassis-poweroff@0.target.requires, ignoring: Invalid argument
[    9.155891] systemd[1]: /lib/systemd/system/host-reset.service:3: Failed to add dependency on obmc-chassis-poweroff@0.target.requires, ignoring: Invalid argument
[    9.689673] systemd[1]: /lib/systemd/system/phosphor-ipmi-net@.socket:3: Invalid interface name, ignoring: sys-subsystem-net-devices-%i.device
[    9.711232] systemd[1]: /lib/systemd/system/phosphor-ipmi-net@.socket:3: Invalid interface name, ignoring: sys-subsystem-net-devices-%i.device
[    9.770316] systemd[1]: Failed to isolate default target: Unit xyz.openbmc_project.State.Host@0.service failed to load properly, please adjust/correct and reload service manager: File exists
[!!!!!!] Failed to isolate default target.
[    9.954507] systemd[1]: Freezing execution.
[   35.674323] SDHCI0 Vcc: disabling
[   35.678049] SDHCI1 Vcc: disabling
[   35.681750] SDHCI1 VccQ: disabling


and I open the 2 lines :
VIRTUAL-RUNTIME_obmc-host-state-manager ?= "x86-power-control"
VIRTUAL-RUNTIME_obmc-chassis-state-manager ?= "x86-power-control"
the system is OK.
but, the "x86-power-control" is disable, I set pwer state command is failed !
root@ast2600-emmc:~# busctl set-property xyz.openbmc_project.State.Host /xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host CurrentHostState s "xyz.openbmc_project.State.Host.HostState.Off"

Failed to set property CurrentHostState on interface xyz.openbmc_project.State.Host: The name is not activatable 
root@ast2600-emmc:~# busctl set-property xyz.openbmc_project.State.Host /xyz/openbmc_project/state/host0 xyz.openbmc_project.State.Host CurrentHostState s "xyz.openbmc_project.State.Host.HostState.Running" 
Failed to set property CurrentHostState on interface xyz.openbmc_project.State.Host: The name is not activatable
so how to solve the problem for the set pwer state command ?
Thank you very much !

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

      reply	other threads:[~2022-06-15  7:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1637828525.15424.openbmc@lists.ozlabs.org>
2021-11-25  8:29 ` openBMC pwm-fan control policy Landon
2021-11-25  8:46   ` Paul Fertser
2021-11-26  5:26     ` Landon
2021-11-26  5:55       ` Landon
2021-11-26 21:57         ` Paul Fertser
2021-11-29  9:43           ` Landon
2021-11-29 10:22             ` Andrei Kartashev
2021-12-02  9:11               ` Landon
2021-12-07  1:45                 ` Landon
2021-12-07  7:37                   ` Landon
2021-12-07  8:05                     ` Andrei Kartashev
2021-12-15  2:39                       ` Landon
2021-12-15  3:21                       ` OpenBMC web sometimes jump back to the login screen problem Landon
2021-12-15  3:46                         ` OpenBMC appear SQUASHFS error problem Landon
2021-12-15  5:36                           ` Landon
2021-12-16  3:19                           ` Landon
2021-12-17  6:39                           ` Landon
2021-12-17 13:09                           ` Patrick Williams
2021-12-15 18:51                         ` OpenBMC web sometimes jump back to the login screen problem Bills, Jason M
2021-12-16  7:05                       ` Landon
2021-12-17 13:10                         ` Patrick Williams
2022-01-21  3:12                           ` OpenBMC Switching function of web Landon
2022-01-21  4:24                           ` Landon
2022-01-24  8:24                             ` Landon
2022-06-13  7:49                               ` OpenBMC state manager problem Landon
2022-06-16  7:34                                 ` CHLI30
2022-06-13  8:13                               ` Landon
2022-06-14  1:58                                 ` Landon
2022-06-15  7:42                                   ` Landon [this message]

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=6535c860.faad.18166500335.Coremail.cld795@163.com \
    --to=cld795@163.com \
    --cc=a.kartashev@yadro.com \
    --cc=fercerpav@gmail.com \
    --cc=jason.m.bills@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    /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.