Unable to integrate amd-power-control for Daytonax Server.

AMDESE / amd-power-control

OpenBMC power control for AMD CRBs.

Apache License 2.0

9 stars 2 forks source link

Unable to integrate amd-power-control for Daytonax Server. #2

Closed jdhanasekar closed 3 years ago

jdhanasekar commented 3 years ago

Hi AMD,

I have used this amd-power-control in openbmc code to power on AMD Daytonax server. But, I am getting build error. What are the steps or changes , I have to do before building the openbmc code.

Please help me on this.

I have removed x86-power-control.bb and I have crated amd-power-control.bb and having contents like this,

SRC_URI_daytonax = "git://github.com/AMDESE/amd-power-control.git;protocol=git;"

PV = "1.0+git${SRCPV}"

S = "${WORKDIR}/git"

LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=86d3f3a95c324c9479bd8986968f4327"

my ``daytonax.conf``` file will look like this,


KMACHINE = "aspeed"
KERNEL_DEVICETREE = "${KMACHINE}-bmc-amd-${MACHINE}.dtb"

UBOOT_MACHINE_daytonax = "ast_g5_phy_config"

require conf/machine/include/ast2500.inc
require conf/machine/include/obmc-bsp-common.inc

SERIAL_CONSOLES = "115200;ttyS4"

FLASH_SIZE = "32768"

OBMC_MACHINE_FEATURES += "\
        obmc-bmc-state-mgmt \
        obmc-chassis-state-mgmt \
        obmc-host-state-mgmt \
        obmc-phosphor-chassis-mgmt \
        obmc-host-ipmi \
        obmc-phosphor-fan-mgmt \
        obmc-phosphor-flash-mgmt \
        "

OBMC_ORG_YAML_SUBDIRS += " org/open_power"

VIRTUAL-RUNTIME_skeleton_workbook = "${MACHINE}-config"
VIRTUAL-RUNTIME_obmc-host-state-manager ?= "amd-power-control"
VIRTUAL-RUNTIME_obmc-chassis-state-manager ?= "amd-power-control"

PREFERRED_PROVIDER_virtual/obmc-chassis-mgmt = "packagegroup-amd-apps"
PREFERRED_PROVIDER_virtual/obmc-fan-mgmt = "packagegroup-amd-apps"
PREFERRED_PROVIDER_virtual/obmc-flash-mgmt = "packagegroup-amd-apps"
PREFERRED_PROVIDER_virtual/obmc-host-ipmi-hw ?= "phosphor-ipmi-kcs"
PREFERRED_PROVIDER_virtual/obmc-inventory-data ?= "${VIRTUAL-RUNTIME_skeleton_workbook}"
PREFERRED_PROVIDER_virtual/obmc-system-mgmt = "packagegroup-amd-apps"
PREFERRED_PROVIDER_virtual/obmc-host-ctl ?= "obmc-op-control-host"
PREFERRED_PROVIDER_virtual/phosphor-led-manager-config-native = ""

OVERRIDES .= ":amd"

Please correct me, if any mistakes in my implementations.

supven01 commented 3 years ago

you would have to packagegroups.bb file to include amd-power-control. What is the error message you are getting?

jdhanasekar commented 3 years ago

I have modified meta-amd/recipes-amd/packagegroups/packagegroups-amd-apps.bb, like this,

SUMMARY = "OpenBMC for AMD - Applications"
PR = "r1"

inherit packagegroup

PROVIDES = "${PACKAGES}"
PACKAGES = " \
        ${PN}-chassis \
        ${PN}-fans \
        ${PN}-flash \
        ${PN}-system \
        "

PROVIDES += "virtual/obmc-chassis-mgmt"
PROVIDES += "virtual/obmc-fan-mgmt"
PROVIDES += "virtual/obmc-flash-mgmt"
PROVIDES += "virtual/obmc-system-mgmt"

RPROVIDES_${PN}-chassis += "virtual-obmc-chassis-mgmt"
RPROVIDES_${PN}-fans += "virtual-obmc-fan-mgmt"
RPROVIDES_${PN}-flash += "virtual-obmc-flash-mgmt"
RPROVIDES_${PN}-system += "virtual-obmc-system-mgmt"

SUMMARY_${PN}-chassis = "AMD Chassis"
RDEPENDS_${PN}-chassis = " \
        amd-power-control \
        obmc-host-failure-reboots \
        "

SUMMARY_${PN}-fans = "AMD Fans"
RDEPENDS_${PN}-fans = ""

SUMMARY_${PN}-flash = "AMD Flash"
RDEPENDS_${PN}-flash = " \
        phosphor-software-manager \
        "

SUMMARY_${PN}-system = "AMD System"
RDEPENDS_${PN}-system = " \
        bmcweb \
        entity-manager \
        ipmitool \
        phosphor-hostlogger \
        phosphor-webui \
        phosphor-post-code-manager \
        phosphor-host-postd \
        phosphor-power \
        "

I am getting error like this,

ERROR: obmc-phosphor-image-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/daytonax-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/recipe-sysroot-native/usr/bin/dnf -v --rpmverbosity=info -y -c /home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/daytonax-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/daytonax-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/etc/yum.repos.d --installroot=/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/daytonax-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs --setopt=logdir=/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/daytonax-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/temp --repofrompath=oe-repo,/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/daytonax-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/oe-rootfs-repo -x shared-mime-info,udev-hwdb --nogpgcheck install base-passwd dbus-broker packagegroup-base-extended packagegroup-core-boot packagegroup-core-ssh-dropbear packagegroup-obmc-apps-bmc-state-mgmt packagegroup-obmc-apps-bmcweb packagegroup-obmc-apps-chassis-state-mgmt packagegroup-obmc-apps-console packagegroup-obmc-apps-dbus-monitor packagegroup-obmc-apps-debug-collector packagegroup-obmc-apps-devtools packagegroup-obmc-apps-extras packagegroup-obmc-apps-fan-control packagegroup-obmc-apps-fru-ipmi packagegroup-obmc-apps-health-monitor packagegroup-obmc-apps-host-state-mgmt packagegroup-obmc-apps-ikvm packagegroup-obmc-apps-inventory packagegroup-obmc-apps-leds packagegroup-obmc-apps-logging packagegroup-obmc-apps-network packagegroup-obmc-apps-remote-logging packagegroup-obmc-apps-rng packagegroup-obmc-apps-sensors packagegroup-obmc-apps-settings packagegroup-obmc-apps-software packagegroup-obmc-apps-telemetry packagegroup-obmc-apps-user-mgmt packagegroup-obmc-apps-user-mgmt-ldap phosphor-ipmi-net run-postinsts shadow virtual-obmc-chassis-mgmt virtual-obmc-fan-mgmt virtual-obmc-flash-mgmt virtual-obmc-host-ipmi-hw virtual-obmc-system-mgmt' returned 1:
DNF version: 4.5.2
cachedir: /home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/daytonax-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/rootfs/var/cache/dnf
Added oe-repo repo from /home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/daytonax-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/oe-rootfs-repo
User-Agent: falling back to 'libdnf': could not detect OS or basearch
repo: using cache for: oe-repo
oe-repo: using metadata from Thu 06 May 2021 08:24:09 AM UTC.
Last metadata expiration check: 0:00:01 ago on Thu 06 May 2021 08:24:09 AM UTC.
Excludes in dnf.conf: shared-mime-info, udev-hwdb
--> Starting dependency resolution
--> Finished dependency resolution
Error:
 Problem: conflicting requests
  - nothing provides amd-power-control needed by packagegroup-amd-apps-chassis-1.0-r1.noarch
(try to add '--skip-broken' to skip uninstallable packages)

ERROR: Logfile of failure stored in: /home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/daytonax-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/temp/log.do_rootfs.23197
ERROR: Task (/home/user/dhanasekar/BMC/AMD/daytonax/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:do_rootfs) failed with exit code '1'

supven01 commented 3 years ago

[AMD Public Use]

In amd-power-control.bb service should be added

SUMMARY = "Chassis Power Control service for AMD platforms" DESCRIPTION = "Chassis Power Control service for AMD platforms"

SRC_URI = @.***/AMDESE/amd-power-control.git;protocol=ssh" SRCREV = "${AUTOREV}"

PV = "1.0+git${SRCPV}"

S = "${WORKDIR}/git"

LICENSE = "Apache-2.0" LIC_FILES_CHKSUM = file://LICENSE;md5=86d3f3a95c324c9479bd8986968f4327

inherit cmake systemd inherit obmc-phosphor-dbus-service

SYSTEMDSERVICE${PN} += "xyz.openbmc_project.Chassis.Control.Power.service \ chassis-system-reset.service \ chassis-system-reset.target"

DEPENDS += " \ boost \ libgpiod \ sdbusplus \ phosphor-logging \ "

In ethanol.conf, these lines should be added

VIRTUAL-RUNTIME_obmc-host-state-manager ?= "amd-power-control" VIRTUAL-RUNTIME_obmc-chassis-state-manager ?= "amd-power-control"

Also, remove the build directory completely, recompile it from scratch.

Thanks, Supreeth Venkatesh System Manageability Architect | AMD Server Software @.***D74254.A36AA3C0]

From: jdhanasekar @.> Sent: Thursday, May 6, 2021 3:09 AM To: AMDESE/amd-power-control @.> Cc: Venkatesh, Supreeth @.>; Comment @.> Subject: Re: [AMDESE/amd-power-control] Unable to integrate amd-power-control for Daytonax Server. (#2)

[CAUTION: External Email]

I have modified meta-amd/recipes-amd/packagegroups/packagegroups-amd-apps.bb, like this,

SUMMARY = "OpenBMC for AMD - Applications"

PR = "r1"

inherit packagegroup

PROVIDES = "${PACKAGES}"

PACKAGES = " \

    ${PN}-chassis \

    ${PN}-fans \

    ${PN}-flash \

    ${PN}-system \

    "

PROVIDES += "virtual/obmc-chassis-mgmt"

PROVIDES += "virtual/obmc-fan-mgmt"

PROVIDES += "virtual/obmc-flash-mgmt"

PROVIDES += "virtual/obmc-system-mgmt"

RPROVIDES_${PN}-chassis += "virtual-obmc-chassis-mgmt"

RPROVIDES_${PN}-fans += "virtual-obmc-fan-mgmt"

RPROVIDES_${PN}-flash += "virtual-obmc-flash-mgmt"

RPROVIDES_${PN}-system += "virtual-obmc-system-mgmt"

SUMMARY_${PN}-chassis = "AMD Chassis"

RDEPENDS_${PN}-chassis = " \

    amd-power-control \

    obmc-host-failure-reboots \

    "

SUMMARY_${PN}-fans = "AMD Fans"

RDEPENDS_${PN}-fans = ""

SUMMARY_${PN}-flash = "AMD Flash"

RDEPENDS_${PN}-flash = " \

    phosphor-software-manager \

    "

SUMMARY_${PN}-system = "AMD System"

RDEPENDS_${PN}-system = " \

    bmcweb \

    entity-manager \

    ipmitool \

    phosphor-hostlogger \

    phosphor-webui \

    phosphor-post-code-manager \

    phosphor-host-postd \

    phosphor-power \

    "

I am getting error like this,

@.***:~/dhanasekar/BMC/AMD/daytonax/build/daytonax$ bitbake obmc-phosphor-image

WARNING: Host distribution "ubuntu-18.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.

Loading cache: 100% |#########################################################################################################################################################################################################| Time: 0:00:00

Loaded 3817 entries from dependency cache.

Parsing recipes: 100% |#######################################################################################################################################################################################################| Time: 0:00:00

Parsing of 2502 .bb files complete (2495 cached, 7 parsed). 3823 targets, 366 skipped, 0 masked, 0 errors.

NOTE: Resolving any missing task queue dependencies

ERROR: Nothing RPROVIDES 'amd-power-control' (but /home/user/dhanasekar/BMC/AMD/daytonax/meta-amd/recipes-amd/packagegroups/packagegroup-amd-apps.bb RDEPENDS on or otherwise requires it)

NOTE: Runtime target 'amd-power-control' is unbuildable, removing...

Missing or unbuildable dependency chain was: ['amd-power-control']

NOTE: Runtime target 'virtual-obmc-chassis-mgmt' is unbuildable, removing...

Missing or unbuildable dependency chain was: ['virtual-obmc-chassis-mgmt', 'amd-power-control']

ERROR: Required build target 'obmc-phosphor-image' has no buildable providers.

Missing or unbuildable dependency chain was: ['obmc-phosphor-image', 'virtual-obmc-chassis-mgmt', 'amd-power-control']

Summary: There was 1 WARNING message shown.

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAMDESE%2Famd-power-control%2Fissues%2F2%23issuecomment-833323072&data=04%7C01%7Csupreeth.venkatesh%40amd.com%7C97d722b3c12146711fb208d910662d40%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637558853306258813%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vhF10HJQlHbqcuWitjoLF1xsDJy0%2BYSAynG6kGTHxqs%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADDXBQVW4FGJL4V74KPW6ATTMJFA7ANCNFSM44EH7LIA&data=04%7C01%7Csupreeth.venkatesh%40amd.com%7C97d722b3c12146711fb208d910662d40%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637558853306258813%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CmNuY0uRuNOEHUt8lfY%2Bs5WrsCJu1jS1drFUbVIC0%2FY%3D&reserved=0.

jdhanasekar commented 3 years ago

Thanks for the info. I should not changes anything in meta-amd/recipes-amd/packagegroups/packagegroups-amd-apps.bb. I have revert back RDEPENDS_${PN}-chassis = " \ amd-power-control \ to like this, RDEPENDS_${PN}-chassis = " \ x86-power-control \ Please correct me , If I am wrong.

jdhanasekar commented 3 years ago

With the suggested changes, I am getting below error.

ERROR: ExpansionError during parsing /home/user/dhanasekar/BMC/AMD/daytonax/meta-amd/meta-daytonax/recipes-x86/chassis/amd-power-control.bb
Traceback (most recent call last):
  File "/home/user/dhanasekar/BMC/AMD/daytonax/poky/bitbake/lib/bb/fetch2/__init__.py", line 1172, in srcrev_internal_helper(ud=<bb.fetch2.FetchData object at 0x7f6d263c17b8>, d=<bb.data_smart.DataSmart object at 0x7f6d2641c588>, name='default'):
         if srcrev == "AUTOINC":
    >        srcrev = ud.method.latest_revision(ud, d, name)

  File "/home/user/dhanasekar/BMC/AMD/daytonax/poky/bitbake/lib/bb/fetch2/__init__.py", line 1581, in Git.latest_revision(ud=<bb.fetch2.FetchData object at 0x7f6d263c17b8>, d=<bb.data_smart.DataSmart object at 0x7f6d2641c588>, name='default'):
             except KeyError:
    >            revs[key] = rev = self._latest_revision(ud, d, name)
                 return rev
  File "/home/user/dhanasekar/BMC/AMD/daytonax/poky/bitbake/lib/bb/fetch2/git.py", line 652, in Git._latest_revision(ud=<bb.fetch2.FetchData object at 0x7f6d263c17b8>, d=<bb.data_smart.DataSmart object at 0x7f6d2641c588>, name='default'):
             """
    >        output = self._lsremote(ud, d, "")
             # Tags of the form ^{} may not work, need to fallback to other form
  File "/home/user/dhanasekar/BMC/AMD/daytonax/poky/bitbake/lib/bb/fetch2/git.py", line 641, in Git._lsremote(ud=<bb.fetch2.FetchData object at 0x7f6d263c17b8>, d=<bb.data_smart.DataSmart object at 0x7f6d2641c588>, search=''):
                     bb.fetch2.check_network_access(d, cmd, repourl)
    >            output = runfetchcmd(cmd, d, True)
                 if not output:
  File "/home/user/dhanasekar/BMC/AMD/daytonax/poky/bitbake/lib/bb/fetch2/__init__.py", line 889, in runfetchcmd(cmd='export PSEUDO_DISABLED=1; export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export SSH_AGENT_PID="30923"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/user/dhanasekar/BMC/AMD/daytonax/scripts:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/arm1176jzs-openbmc-linux-gnueabi/amd-power-control/fetcheravoidrecurse-fetcheravoidrecurse/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/arm1176jzs-openbmc-linux-gnueabi/amd-power-control/fetcheravoidrecurse-fetcheravoidrecurse/recipe-sysroot/usr/bin/crossscripts:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/arm1176jzs-openbmc-linux-gnueabi/amd-power-control/fetcheravoidrecurse-fetcheravoidrecurse/recipe-sysroot-native/usr/sbin:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/arm1176jzs-openbmc-linux-gnueabi/amd-power-control/fetcheravoidrecurse-fetcheravoidrecurse/recipe-sysroot-native/usr/bin:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/arm1176jzs-openbmc-linux-gnueabi/amd-power-control/fetcheravoidrecurse-fetcheravoidrecurse/recipe-sysroot-native/sbin:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/arm1176jzs-openbmc-linux-gnueabi/amd-power-control/fetcheravoidrecurse-fetcheravoidrecurse/recipe-sysroot-native/bin:/home/user/dhanasekar/BMC/AMD/daytonax/poky/bitbake/bin:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/hosttools"; export HOME="/home/user"; git -c core.fsyncobjectfiles=0 ls-remote ssh://github.com/AMDESE/amd-power-control.git ', d=<bb.data_smart.DataSmart object at 0x7f6d263c15c0>, quiet=True, cleanup=[], log=None, workdir=None):

    >        raise FetchError(error_message)

supven01 commented 3 years ago

[AMD Public Use]

Try fetching the code amd-power-control using ssh method. You may have to add your rsa key (ssh_id.pub) of your build machine to your Github profile to fetch this.

Thanks, Supreeth Venkatesh System Manageability Architect | AMD Server Software @.***D74261.5DC17760]

From: jdhanasekar @.> Sent: Thursday, May 6, 2021 10:18 AM To: AMDESE/amd-power-control @.> Cc: Venkatesh, Supreeth @.>; Comment @.> Subject: Re: [AMDESE/amd-power-control] Unable to integrate amd-power-control for Daytonax Server. (#2)

[CAUTION: External Email]

With the suggested changes, I am getting below error.

ERROR: ExpansionError during parsing /home/user/dhanasekar/BMC/AMD/daytonax/meta-amd/meta-daytonax/recipes-x86/chassis/amd-power-control.bb

Traceback (most recent call last):

File "/home/user/dhanasekar/BMC/AMD/daytonax/poky/bitbake/lib/bb/fetch2/init.py", line 1172, in srcrev_internal_helper(ud=<bb.fetch2.FetchData object at 0x7f6d263c17b8>, d=<bb.data_smart.DataSmart object at 0x7f6d2641c588>, name='default'):

     if srcrev == "AUTOINC":

>        srcrev = ud.method.latest_revision(ud, d, name)

File "/home/user/dhanasekar/BMC/AMD/daytonax/poky/bitbake/lib/bb/fetch2/init.py", line 1581, in Git.latest_revision(ud=<bb.fetch2.FetchData object at 0x7f6d263c17b8>, d=<bb.data_smart.DataSmart object at 0x7f6d2641c588>, name='default'):

         except KeyError:

>            revs[key] = rev = self._latest_revision(ud, d, name)

             return rev

File "/home/user/dhanasekar/BMC/AMD/daytonax/poky/bitbake/lib/bb/fetch2/git.py", line 652, in Git._latest_revision(ud=<bb.fetch2.FetchData object at 0x7f6d263c17b8>, d=<bb.data_smart.DataSmart object at 0x7f6d2641c588>, name='default'):

         """

>        output = self._lsremote(ud, d, "")

         # Tags of the form ^{} may not work, need to fallback to other form

File "/home/user/dhanasekar/BMC/AMD/daytonax/poky/bitbake/lib/bb/fetch2/git.py", line 641, in Git._lsremote(ud=<bb.fetch2.FetchData object at 0x7f6d263c17b8>, d=<bb.data_smart.DataSmart object at 0x7f6d2641c588>, search=''):

                 bb.fetch2.check_network_access(d, cmd, repourl)

>            output = runfetchcmd(cmd, d, True)

             if not output:

File "/home/user/dhanasekar/BMC/AMD/daytonax/poky/bitbake/lib/bb/fetch2/init.py", line 889, in runfetchcmd(cmd='export PSEUDO_DISABLED=1; export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export SSH_AGENT_PID="30923"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/user/dhanasekar/BMC/AMD/daytonax/scripts:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/arm1176jzs-openbmc-linux-gnueabi/amd-power-control/fetcheravoidrecurse-fetcheravoidrecurse/recipe-sysroot-native/usr/bin/arm-openbmc-linux-gnueabi:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/arm1176jzs-openbmc-linux-gnueabi/amd-power-control/fetcheravoidrecurse-fetcheravoidrecurse/recipe-sysroot/usr/bin/crossscripts:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/arm1176jzs-openbmc-linux-gnueabi/amd-power-control/fetcheravoidrecurse-fetcheravoidrecurse/recipe-sysroot-native/usr/sbin:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/arm1176jzs-openbmc-linux-gnueabi/amd-power-control/fetcheravoidrecurse-fetcheravoidrecurse/recipe-sysroot-native/usr/bin:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/arm1176jzs-openbmc-linux-gnueabi/amd-power-control/fetcheravoidrecurse-fetcheravoidrecurse/recipe-sysroot-native/sbin:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/work/arm1176jzs-openbmc-linux-gnueabi/amd-power-control/fetcheravoidrecurse-fetcheravoidrecurse/recipe-sysroot-native/bin:/home/user/dhanasekar/BMC/AMD/daytonax/poky/bitbake/bin:/home/user/dhanasekar/BMC/AMD/daytonax/build/daytonax/tmp/hosttools"; export HOME="/home/user"; git -c core.fsyncobjectfiles=0 ls-remote ssh://github.com/AMDESE/amd-power-control.git ', d=<bb.data_smart.DataSmart object at 0x7f6d263c15c0>, quiet=True, cleanup=[], log=None, workdir=None):

>        raise FetchError(error_message)

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAMDESE%2Famd-power-control%2Fissues%2F2%23issuecomment-833606331&data=04%7C01%7Csupreeth.venkatesh%40amd.com%7Caf16f7a3d14c4d0c0f0f08d910a213b9%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637559110567696022%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qKqhjkkZTR6Fr1JI7v%2F5FZwzFUfVadKA26atYNR4IBs%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADDXBQT6E5E3YHWK7ZWU7IDTMKXI5ANCNFSM44EH7LIA&data=04%7C01%7Csupreeth.venkatesh%40amd.com%7Caf16f7a3d14c4d0c0f0f08d910a213b9%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637559110567696022%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=4Xe5w5sdqnXztC27rDPjBqflKIXcHDbbY%2BdCjjJtfFA%3D&reserved=0.

jdhanasekar commented 3 years ago

I have successfully fetched the amd-power-control source from Github, integrated with openBMC and built successfully. But I am not seeing video signal on the VGA monitor and it seems boards is not powered on because power control code requires board id.

I am unable to program board_id by fw_setenv. This command setenv boardid 6 is working but setenv board_id 6 is not working.

Below is the journal control log.,,,

root@daytonax:~# journalctl | grep -i power
Jan 01 00:00:18 daytonax kernel: at24 3-0050: page_size looks suspicious (no power of 2)!
Jan 01 00:00:36 daytonax systemd[1]: Starting Wait for /xyz/openbmc_project/control/host0/power_restore_policy...
Jan 01 00:00:39 daytonax systemd[1]: Starting Amd Power Control...
Jan 01 00:00:44 daytonax power-control[224]: Start Chassis power control service...
Jan 01 00:00:46 daytonax power-control[263]: ## Error: "board_id" not defined
Jan 01 00:00:46 daytonax power-control[224]: Board ID data is null, errno: 1message: Operation not permitted
Jan 01 00:00:46 daytonax power-control[224]: Unable to get Platform ID
Jan 01 00:00:46 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Main process exited, code=exited, status=255/EXCEPTION
Jan 01 00:00:46 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Failed with result 'exit-code'.
Jan 01 00:00:47 daytonax systemd[1]: Failed to start Amd Power Control.
Jan 01 00:00:58 daytonax systemd[1]: Finished Wait for /xyz/openbmc_project/control/host0/power_restore_policy.
Jan 01 00:00:59 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Scheduled restart job, restart counter is at 1.
Jan 01 00:01:01 daytonax systemd[1]: Stopped Amd Power Control.
May 07 08:56:26 daytonax systemd[1]: Starting Amd Power Control...
May 07 08:56:26 daytonax power-control[302]: Start Chassis power control service...
May 07 08:56:27 daytonax power-control[306]: ## Error: "board_id" not defined
May 07 08:56:27 daytonax power-control[302]: Board ID data is null, errno: 1message: Operation not permitted
May 07 08:56:27 daytonax power-control[302]: Unable to get Platform ID
May 07 08:56:27 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Main process exited, code=exited, status=255/EXCEPTION
May 07 08:56:27 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Failed with result 'exit-code'.
May 07 08:56:27 daytonax systemd[1]: Failed to start Amd Power Control.
May 07 08:56:30 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Scheduled restart job, restart counter is at 2.
May 07 08:56:30 daytonax systemd[1]: Stopped Amd Power Control.
May 07 08:56:30 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Start request repeated too quickly.
May 07 08:56:30 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Failed with result 'exit-code'.
May 07 08:56:30 daytonax systemd[1]: Failed to start Amd Power Control.
root@daytonax:~#

supven01 commented 3 years ago

[AMD Public Use]

Since your platform is Daytonax only, You may have to change amd-power-control to disable the board id check and make the code for daytonax by default. Our code is dependent on u-boot patch which will write board_id at u-boot phase.

Thanks, Supreeth Venkatesh System Manageability Architect | AMD Server Software @.***D74320.30FC6220]

From: jdhanasekar @.> Sent: Friday, May 7, 2021 7:07 AM To: AMDESE/amd-power-control @.> Cc: Venkatesh, Supreeth @.>; Comment @.> Subject: Re: [AMDESE/amd-power-control] Unable to integrate amd-power-control for Daytonax Server. (#2)

[CAUTION: External Email]

I have successfully fetched the amd-power-control source from Github, integrated with openBMC and built successfully. But I am not seeing video signal on the VGA monitor and it seems boards is not powered on because power control code requires board id.

I am unable to program board_id by fw_setenv. This command setenv boardid 6 is working but setenv board_id 6 is not working.

Below is the journal control log.,,,

@.***:~# journalctl | grep -i power

Jan 01 00:00:18 daytonax kernel: at24 3-0050: page_size looks suspicious (no power of 2)!

Jan 01 00:00:36 daytonax systemd[1]: Starting Wait for /xyz/openbmc_project/control/host0/power_restore_policy...

Jan 01 00:00:39 daytonax systemd[1]: Starting Amd Power Control...

Jan 01 00:00:44 daytonax power-control[224]: Start Chassis power control service...

Jan 01 00:00:46 daytonax power-control[263]: ## Error: "board_id" not defined

Jan 01 00:00:46 daytonax power-control[224]: Board ID data is null, errno: 1message: Operation not permitted

Jan 01 00:00:46 daytonax power-control[224]: Unable to get Platform ID

Jan 01 00:00:46 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Main process exited, code=exited, status=255/EXCEPTION

Jan 01 00:00:46 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Failed with result 'exit-code'.

Jan 01 00:00:47 daytonax systemd[1]: Failed to start Amd Power Control.

Jan 01 00:00:58 daytonax systemd[1]: Finished Wait for /xyz/openbmc_project/control/host0/power_restore_policy.

Jan 01 00:00:59 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Scheduled restart job, restart counter is at 1.

Jan 01 00:01:01 daytonax systemd[1]: Stopped Amd Power Control.

May 07 08:56:26 daytonax systemd[1]: Starting Amd Power Control...

May 07 08:56:26 daytonax power-control[302]: Start Chassis power control service...

May 07 08:56:27 daytonax power-control[306]: ## Error: "board_id" not defined

May 07 08:56:27 daytonax power-control[302]: Board ID data is null, errno: 1message: Operation not permitted

May 07 08:56:27 daytonax power-control[302]: Unable to get Platform ID

May 07 08:56:27 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Main process exited, code=exited, status=255/EXCEPTION

May 07 08:56:27 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Failed with result 'exit-code'.

May 07 08:56:27 daytonax systemd[1]: Failed to start Amd Power Control.

May 07 08:56:30 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Scheduled restart job, restart counter is at 2.

May 07 08:56:30 daytonax systemd[1]: Stopped Amd Power Control.

May 07 08:56:30 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Start request repeated too quickly.

May 07 08:56:30 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Failed with result 'exit-code'.

May 07 08:56:30 daytonax systemd[1]: Failed to start Amd Power Control.

@.***:~#

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAMDESE%2Famd-power-control%2Fissues%2F2%23issuecomment-834315049&data=04%7C01%7Csupreeth.venkatesh%40amd.com%7C2c640812e83a487cb09c08d911509636%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637559860079764205%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=OCwx87ZTpBUrNSdIgxr6piWlz7gvCFDIrWENb8BcEzs%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADDXBQWFPJCG6BTAIRKX5RDTMPJVNANCNFSM44EH7LIA&data=04%7C01%7Csupreeth.venkatesh%40amd.com%7C2c640812e83a487cb09c08d911509636%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637559860079764205%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=P3pdhzQ0TsvX8Zzr2ViLP0aOu99tGXUPnCM8%2FkKZ4iw%3D&reserved=0.

jdhanasekar commented 3 years ago

Then, I have to create a patch to remove the board ID check which is similar to x86-power-control patch to remove Intel specific code ??

jdhanasekar commented 3 years ago

I have added patches to remove board ID check and added colde like this, bool platformID = '6'; power_control::isDaytonax = true;

I am observing video signals (AMD EPYC logo) on a VGA monitor. After a few seconds, the board is stopped at BIOS (AMI) logo. But keyboard's capslock , numlocks keys are working. Seems board is not hanging and not booting further.

supven01 commented 3 years ago

[AMD Official Use Only - Internal Distribution Only]

"Failed to find the MON_P0_NMI_BTN line" Device tree does not look like it has the MON_P0_NMI_BTN definition.

Thanks, Supreeth Venkatesh System Manageability Architect | AMD Server Software @.***D74570.4F2F1BA0]

From: jdhanasekar @.> Sent: Monday, May 10, 2021 4:22 AM To: AMDESE/amd-power-control @.> Cc: Venkatesh, Supreeth @.>; Comment @.> Subject: Re: [AMDESE/amd-power-control] Unable to integrate amd-power-control for Daytonax Server. (#2)

[CAUTION: External Email]

I have added patches to removed board ID check and added colde like this, bool platformID = '6'; power_control::isDaytonax = true;

I am observing video signals (AMD EPYC logo) on a VGA monitor. But after a few seconds, the board is hanging and BIOS is not booting further. It has stopped before BIOS post screen. I am getting below messages in journalctl log,

@.***:~# journalctl | grep -i power

Jan 01 00:00:12 daytonax kernel: at24 3-0050: page_size looks suspicious (no power of 2)!

May 10 09:05:04 daytonax systemd[1]: Starting Wait for /xyz/openbmc_project/control/host0/power_restore_policy...

May 10 09:05:07 daytonax systemd[1]: Starting Amd Power Control...

May 10 09:05:11 daytonax power-control[214]: Start Chassis power control service...

May 10 09:05:11 daytonax power-control[214]: Failed to find the MON_P0_NMI_BTN line

May 10 09:05:12 daytonax power-control[214]: ASSERT_BMC_READY set to 0

May 10 09:05:12 daytonax power-control[214]: NMI Source Property Monitor

May 10 09:05:12 daytonax power-control[214]: Host0: Moving to "Off" state

May 10 09:05:12 daytonax power-control[214]: Initializing power state. resetButtonPressed: 0!

May 10 09:05:12 daytonax power-control[214]: terminate called after throwing an instance of 'std::logic_error'

May 10 09:05:12 daytonax power-control[214]: what(): object not holding a GPIO line handle

May 10 09:05:14 daytonax systemd[1]: Started Amd Power Control.

May 10 09:05:24 daytonax systemd[1]: Finished Wait for /xyz/openbmc_project/control/host0/power_restore_policy.

May 10 09:05:35 daytonax systemd-coredump[271]: Process 214 (power-control) of user 0 dumped core.

May 10 09:05:35 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Main process exited, code=dumped, status=6/ABRT

May 10 09:05:35 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Failed with result 'core-dump'.

May 10 09:05:38 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Scheduled restart job, restart counter is at 1.

May 10 09:05:38 daytonax systemd[1]: Stopped Amd Power Control.

May 10 09:05:38 daytonax systemd[1]: Starting Amd Power Control...

May 10 09:05:38 daytonax power-control[371]: Start Chassis power control service...

May 10 09:05:38 daytonax systemd[1]: Started Amd Power Control.

May 10 09:05:38 daytonax power-control[371]: Failed to find the MON_P0_NMI_BTN line

May 10 09:05:38 daytonax power-control[371]: ASSERT_BMC_READY set to 0

May 10 09:05:38 daytonax power-control[371]: NMI Source Property Monitor

May 10 09:05:38 daytonax power-control[371]: Host0: Moving to "On" state

May 10 09:05:39 daytonax power-control[371]: Initializing power state. resetButtonPressed: 0!

May 10 09:05:39 daytonax power-control[371]: terminate called after throwing an instance of 'std::logic_error'

May 10 09:05:39 daytonax power-control[371]: what(): object not holding a GPIO line handle

May 10 09:05:45 daytonax systemd-coredump[383]: Process 371 (power-control) of user 0 dumped core.

May 10 09:05:45 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Main process exited, code=dumped, status=6/ABRT

May 10 09:05:45 daytonax phosphor-dump-manager[384]: Failed to get property CurrentPowerState on interface xyz.openbmc_project.State.Chassis: Remote peer disconnected

May 10 09:05:45 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Failed with result 'core-dump'.

May 10 09:05:48 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Scheduled restart job, restart counter is at 2.

May 10 09:05:48 daytonax systemd[1]: Stopped Amd Power Control.

May 10 09:05:48 daytonax systemd[1]: Starting Amd Power Control...

May 10 09:05:48 daytonax power-control[448]: Start Chassis power control service...

May 10 09:05:48 daytonax systemd[1]: Started Amd Power Control.

May 10 09:05:49 daytonax power-control[448]: Failed to find the MON_P0_NMI_BTN line

May 10 09:05:49 daytonax power-control[448]: ASSERT_BMC_READY set to 0

May 10 09:05:49 daytonax power-control[448]: NMI Source Property Monitor

May 10 09:05:49 daytonax power-control[448]: Host0: Moving to "On" state

May 10 09:05:49 daytonax power-control[448]: Initializing power state. resetButtonPressed: 0!

May 10 09:05:49 daytonax power-control[448]: terminate called after throwing an instance of 'std::logic_error'

May 10 09:05:49 daytonax power-control[448]: what(): object not holding a GPIO line handle

May 10 09:05:56 daytonax systemd-coredump[464]: Process 448 (power-control) of user 0 dumped core.

May 10 09:05:56 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Main process exited, code=dumped, status=6/ABRT

May 10 09:05:56 daytonax phosphor-dump-manager[479]: Failed to get property CurrentPowerState on interface xyz.openbmc_project.State.Chassis: Remote peer disconnected

May 10 09:05:56 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Failed with result 'core-dump'.

May 10 09:05:59 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Scheduled restart job, restart counter is at 3.

May 10 09:05:59 daytonax systemd[1]: Stopped Amd Power Control.

May 10 09:05:59 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Start request repeated too quickly.

May 10 09:05:59 daytonax systemd[1]: xyz.openbmc_project.Chassis.Control.Power.service: Failed with result 'core-dump'.

May 10 09:05:59 daytonax systemd[1]: Failed to start Amd Power Control.

May 10 09:06:00 daytonax phosphor-dump-manager[570]: Failed to get property CurrentPowerState on interface xyz.openbmc_project.State.Chassis: The name is not activatable

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAMDESE%2Famd-power-control%2Fissues%2F2%23issuecomment-836454017&data=04%7C01%7Csupreeth.venkatesh%40amd.com%7C59b8e1bfedd54727256908d913950cb7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637562353156687006%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Cw5I6cA9b%2FkZqX0ErGws8zs7iNJ1hqaeqgoxcQwKUb0%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADDXBQSI3H27S26PHFUKDS3TM6QTBANCNFSM44EH7LIA&data=04%7C01%7Csupreeth.venkatesh%40amd.com%7C59b8e1bfedd54727256908d913950cb7%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637562353156687006%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=toT9fr6UUHIoKAbvJOttcI80ZGe96rNXIEa3RNlOs64%3D&reserved=0.

jdhanasekar commented 3 years ago

Actually, My Daytonax Server doesn't have an NMI Button. So I have not mentioned MON_P0_NMI_BTN. Please guide me for the next step.

supven01 commented 3 years ago

[AMD Public Use]

Even though there is no NMI button, there should be NMI gpio/signal. You will have to map that in DT.

Thanks, Supreeth Venkatesh System Manageability Architect | AMD Server Software @.***D74571.7180DAD0]

From: jdhanasekar @.> Sent: Monday, May 10, 2021 7:51 AM To: AMDESE/amd-power-control @.> Cc: Venkatesh, Supreeth @.>; Comment @.> Subject: Re: [AMDESE/amd-power-control] Unable to integrate amd-power-control for Daytonax Server. (#2)

[CAUTION: External Email]

Actually, My Daytonax Server doesn't have an NMI Button. So I have not mentioned MON_P0_NMI_BTN. Please guide me for the next step.

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAMDESE%2Famd-power-control%2Fissues%2F2%23issuecomment-836660682&data=04%7C01%7Csupreeth.venkatesh%40amd.com%7C2d66dbab54b64012497008d913b253bd%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637562478906803579%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2UOWysIkct3L9NcOBgrmBq3XW1VGSA4vtPW2O3%2BY68Q%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADDXBQUCG7SDX4ZP7FHWH3TTM7JE7ANCNFSM44EH7LIA&data=04%7C01%7Csupreeth.venkatesh%40amd.com%7C2d66dbab54b64012497008d913b253bd%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637562478906813571%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=75VAUlUQhktmbEnIkrYKGvxgnZb2MpUmUUBOOHZpS%2Fs%3D&reserved=0.

jdhanasekar commented 3 years ago

After adding MON_P0_NMI_BTN to DTS file, I am not seeing any negative statement.

But, system is staying at BIOS flash screen, not booting further. It seems it is not hanging , stuck.

Jan 01 00:00:19 daytonax kernel: at24 3-0050: page_size looks suspicious (no power of 2)!
Jan 01 00:00:36 daytonax systemd[1]: Starting Wait for /xyz/openbmc_project/control/host0/power_restore_policy...
Jan 01 00:00:39 daytonax systemd[1]: Starting Amd Power Control...
Jan 01 00:00:43 daytonax power-control[222]: Start Chassis power control service...
Jan 01 00:00:44 daytonax power-control[222]: ASSERT_BMC_READY set to 0
Jan 01 00:00:44 daytonax power-control[222]:  NMI Source Property Monitor
Jan 01 00:00:44 daytonax power-control[222]: Host0: Moving to "Off" state
Jan 01 00:00:44 daytonax power-control[222]: Initializing power state. resetButtonPressed: 0!
Jan 01 00:00:44 daytonax power-control[222]: RestartCause set to xyz.openbmc_project.State.Host.RestartCause.Unknown
Jan 01 00:00:45 daytonax power-control[222]: powerStateOff: power supply power OK assert event received
Jan 01 00:00:45 daytonax power-control[222]: Host0: Moving to "On" state
Jan 01 00:00:45 daytonax power-control[222]: POH timer started
Jan 01 00:00:45 daytonax power-control[222]: Host system DC power is on
Jan 01 00:00:47 daytonax systemd[1]: Started Amd Power Control.
Jan 01 00:01:02 daytonax systemd[1]: Finished Wait for /xyz/openbmc_project/control/host0/power_restore_policy.

jdhanasekar commented 3 years ago

I am not able to perform power cycle operation in web gui. Only one time, I can able to do reboot and then, reboot is greyed out.

jdhanasekar commented 3 years ago

Hi,

After powering up the Daytonax server by amd-power-control, I am observing ethernet is not working. I am not seeing the ip address for eth0. I have cross checked with my old image(without amd-power-control inclusion), Ethernet is working.

root@daytonax:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether a2:f2:bd:33:a6:b3 brd ff:ff:ff:ff:ff:ff
    inet 169.254.56.84/16 brd 169.254.255.255 scope link eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a0f2:bdff:fe33:a6b3/64 scope link
       valid_lft forever preferred_lft forever
3: sit0@NONE: <NOARP> mtu 1480 qdisc noop qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0

jdhanasekar commented 3 years ago

If I remove MON_P0_NMI_BTN declaration from GPIO E4 in dts file. Ethernet issue has gone. I am seeing ip address for ethernet port. I don't know why it is happening like this. But I am unable to do power off , power on via ipmitool now.

root@daytonax:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 8a:05:25:19:28:32 brd ff:ff:ff:ff:ff:ff
    inet 169.254.232.88/16 brd 169.254.255.255 scope link eth0
       valid_lft forever preferred_lft forever
    inet 10.1.60.97/16 brd 10.1.255.255 scope global dynamic eth0
       valid_lft 691189sec preferred_lft 691189sec
    inet6 fe80::8805:25ff:fe19:2832/64 scope link
       valid_lft forever preferred_lft forever
3: sit0@NONE: <NOARP> mtu 1480 qdisc noop qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0

supven01 commented 3 years ago

[AMD Public Use]

MAC should have this definition in your device tree.

&mac0 { status = "okay";

            pinctrl-names = "default";
            pinctrl-0 = <&pinctrl_rmii1_default>;
            clocks = <&syscon ASPEED_CLK_GATE_MAC1CLK>,
                            <&syscon ASPEED_CLK_MAC1RCLK>;
            clock-names = "MACCLK", "RCLK";

};

Thanks, Supreeth Venkatesh System Manageability Architect | AMD Server Software @.***D747D1.76FA6FA0]

From: jdhanasekar @.> Sent: Thursday, May 13, 2021 7:00 AM To: AMDESE/amd-power-control @.> Cc: Venkatesh, Supreeth @.>; Comment @.> Subject: Re: [AMDESE/amd-power-control] Unable to integrate amd-power-control for Daytonax Server. (#2)

[CAUTION: External Email]

If I remove MON_P0_NMI_BTN declaration from GPIO E4 in dts file. Ethernet issue has gone. I am seeing ip address for ethernet port. I don't know why it is happening like this. But I am unable to do power off , power on via ipmitool now.

@.***:~# ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

inet 127.0.0.1/8 scope host lo

   valid_lft forever preferred_lft forever

inet6 ::1/128 scope host

   valid_lft forever preferred_lft forever

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000

link/ether 8a:05:25:19:28:32 brd ff:ff:ff:ff:ff:ff

inet 169.254.232.88/16 brd 169.254.255.255 scope link eth0

   valid_lft forever preferred_lft forever

inet 10.1.60.97/16 brd 10.1.255.255 scope global dynamic eth0

   valid_lft 691189sec preferred_lft 691189sec

inet6 fe80::8805:25ff:fe19:2832/64 scope link

   valid_lft forever preferred_lft forever

3: sit0@NONE: mtu 1480 qdisc noop qlen 1000

link/sit 0.0.0.0 brd 0.0.0.0

- You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAMDESE%2Famd-power-control%2Fissues%2F2%23issuecomment-840509859&data=04%7C01%7Csupreeth.venkatesh%40amd.com%7C5b477bf7161f480cfaa408d91606b2a4%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637565040310076874%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=0c4cBAoAieFJAHBlHXsTQ5BCjjZ3uegQQxnl%2B8gCBiU%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADDXBQVP5LRGX43WUE4DYNTTNO5NRANCNFSM44EH7LIA&data=04%7C01%7Csupreeth.venkatesh%40amd.com%7C5b477bf7161f480cfaa408d91606b2a4%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637565040310076874%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5SRyhf11hDjJe2uoh4W7Cuq3UH786ca99rKytTLQg7o%3D&reserved=0.

jdhanasekar commented 3 years ago

Hi Supreeth,

My dts file has the same code like your code. After powering up the host, BIOS gets controls and it may write something in Aspeed registers. It may be the cause of for the ethernet issue. In the openBMC community, people are saying this. Please view this link, https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6260. Vendor BMC has a mechanism to protect ASPEED registers from BIOS writes.

Please forgive me, If I am wrong.

&fmc {
    status = "okay";
    flash@0 {
        status = "okay";
        m25p,fast-read;
        #include "openbmc-flash-layout.dtsi"
    };
};

&mac0 {
    status = "okay";

    pinctrl-names = "default";
    pinctrl-0 = <&pinctrl_rmii1_default>;
    clocks = <&syscon ASPEED_CLK_GATE_MAC1CLK>,
         <&syscon ASPEED_CLK_MAC1RCLK>;
    clock-names = "MACCLK", "RCLK";
};

&uart5 {
    //BMC Console
    status = "okay";
};

jdhanasekar commented 3 years ago

After including this patch https://github.com/openbmc/openbmc/blob/master/meta-phosphor/aspeed-layer/recipes-bsp/u-boot/files/0001-aspeed-Disable-unnecessary-features.patch.

I am not seeing BIOS standing at BIOS log screen issue. Now BIOS booted the AMD host completely to OS. Still , Ethernet is not working.

jdhanasekar commented 3 years ago

After enabling BMC LAN Configuration = Dynamic, BMC Ethernet is working. I have observed that once BIOS gets the control, It is disabling (indirectly)BMC Ethernet. I don't know Why it is like this. I have included a phosphor-ipmi-host recipe in my source code. BIOS may be disabling BMC ethernet via phosphor-ipmi-host.

jdhanasekar commented 3 years ago

After removing obmc-host-ipmi in machine/daytonax.conf, BIOS is not disabling BMC Ethernet. Able to do Host power cycle from openBMC webui successfully.