<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    06.12.2019 5:43, Zheng Bao wrote:<br>
    <blockquote type="cite"
cite="mid:MN2PR04MB6669193B89BEFFF3252A1216CD5F0@MN2PR04MB6669.namprd04.prod.outlook.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
      <div style="font-family: Calibri, Helvetica, sans-serif;
        font-size: 12pt; color: rgb(0, 0, 0);">
        Is this problem solved?</div>
      <div style="font-family: Calibri, Helvetica, sans-serif;
        font-size: 12pt; color: rgb(0, 0, 0);">
        I met the same problem.</div>
      <div style="font-family: Calibri, Helvetica, sans-serif;
        font-size: 12pt; color: rgb(0, 0, 0);">
        <br>
      </div>
    </blockquote>
    <p>Well, AFAIU the meta-s2600wf layer in upstream openbmc is still
      non-functional.</p>
    <p>We're using the `wolfpass` machine from Intel-BMC/clean_builds
      now.</p>
    <p>We still see those network driver related backtraces, but the
      rest seems to work more or less fine.</p>
    <p>Host power can be controlled (even locally from openbmc shell)
      using ipmitool.<br>
    </p>
    <pre class="moz-signature" cols="80">With best regards,
Alexander Amelkin,
</pre>
    <br>
    <blockquote type="cite"
cite="mid:MN2PR04MB6669193B89BEFFF3252A1216CD5F0@MN2PR04MB6669.namprd04.prod.outlook.com">
      <div style="font-family: Calibri, Helvetica, sans-serif;
        font-size: 12pt; color: rgb(0, 0, 0);">
      </div>
      <div style="font-family: Calibri, Helvetica, sans-serif;
        font-size: 12pt; color: rgb(0, 0, 0);">
        Zheng<br>
      </div>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0);">
        <br>
        <hr tabindex="-1" style="display:inline-block; width:98%;">
        <b>From:</b> openbmc on behalf of Alexander Amelkin<br>
        <b>Sent:</b> Friday, November 15, 2019 10:53 AM<br>
        <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:openbmc@lists.ozlabs.org">openbmc@lists.ozlabs.org</a>;
        <a class="moz-txt-link-abbreviated" href="mailto:jason.m.bills@linux.intel.com">jason.m.bills@linux.intel.com</a><br>
        <b>Subject:</b> s2600wf problems (was: openbmc power-control
        can't work OK)
        <div><br>
        </div>
      </div>
      <div class="BodyFragment"><font size="2"><span
            style="font-size:11pt;">
            <div class="PlainText">Hi Bill!<br>
              <br>
              We're also having difficulties running a generic
              meta-s2600wf on Intel reference<br>
              s2600wf "Woflpass" board.<br>
              <br>
              We're using a newer openbmc commit
              (985dee9cb6bb29800a933e882913a44e6b9d4f420)<br>
              with a patch to phosphor-dbus-interfaces taken from commit<br>
              0bbcc8f0cc34236d6f8549c5f51410420dbc8f08 of that project.<br>
              The patch is applied in order to make openbmc build for
              s2600wf, without the<br>
              patch the build fails complaining about the missing
              NMISource interface.<br>
              <br>
              When we boot the image on s2600wf, we get a LOT of errors.
              The main problems we<br>
              have are:<br>
              <br>
              1. Host power can't be controlled<br>
              <br>
              2. Ethernet driver crashes<br>
              <br>
              Below are the logs. I've cut out all the non-error output
              here, except for the<br>
              log header.<br>
              <br>
              -- Logs begin at Thu 1970-01-01 00:00:10 UTC, end at Thu
              1970-01-01 01:02:06 UTC. --<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: Booting Linux on
              physical CPU 0x0<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: Linux version
              5.3.10-7b61b9e<br>
              (oe-user@oe-host) (gcc version 9.2.0 (GCC)) #1 Thu Nov 14
              14:13:03 UTC 2019<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: CPU:
              ARMv6-compatible processor<br>
              [410fb767] revision 7 (ARMv7), cr=00c5387d<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: CPU: PIPT / VIPT
              nonaliasing data cache,<br>
              VIPT nonaliasing instruction cache<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: OF: fdt: Machine
              model: S2600WF BMC<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: Memory policy: Data
              cache writeback<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: cma: Reserved 16
              MiB at 0x9d800000<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: Built 1 zonelists,
              mobility grouping on. <br>
              Total pages: 125984<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: Kernel command
              line:<br>
              console=ttyS4,115200n8 root=/dev/ram rw<br>
              ----- 8< ------<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: aspeed_gfx
              1e6e6000.display: failed to<br>
              initialize reserved mem: -19<br>
              ----- 8< ------<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: aspeed-smc
              1e630000.spi: Error applying<br>
              setting, reverse things back<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: aspeed-smc
              1e630000.spi: Using 50 MHz SPI<br>
              frequency<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: aspeed-smc
              1e630000.spi: unrecognized<br>
              JEDEC id bytes: 0a 0a 0a 0a 0a 0a<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: aspeed-smc
              1e630000.spi: Aspeed SMC probe<br>
              failed -2<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: aspeed-smc: probe
              of 1e630000.spi failed<br>
              with error -2<br>
              ----- 8< ------<br>
              Jan 01 00:00:10 vegman-s2600wf kernel: overlayfs: upper fs
              does not support tmpfile.<br>
              Jan 01 00:00:10 vegman-s2600wf systemd[1]: Failed to
              lookup module alias<br>
              'autofs4': Function not implemented<br>
              ----- 8< ------<br>
              Jan 01 00:00:10 vegman-s2600wf systemd[1]: Failed to put
              bus name to hashmap:<br>
              File exists<br>
              Jan 01 00:00:10 vegman-s2600wf systemd[1]:<br>
              xyz.openbmc_project.State.Host.service: Two services
              allocated for the same bus<br>
              name xyz.openbmc_project.State.Host, refusing operation.<br>
              Jan 01 00:00:10 vegman-s2600wf systemd[1]:
              unit_file_find_fragment:<br>
              <a class="moz-txt-link-abbreviated" href="mailto:obmc-host-reset-running@.target+0">obmc-host-reset-running@.target+0</a> →
              <a class="moz-txt-link-abbreviated" href="mailto:obmc-host-reset-running@0.target">obmc-host-reset-running@0.target</a><br>
              Jan 01 00:00:10 vegman-s2600wf systemd[1]:
              unit_file_find_fragment:<br>
              <a class="moz-txt-link-abbreviated" href="mailto:obmc-host-reset@.target+0">obmc-host-reset@.target+0</a> → <a class="moz-txt-link-abbreviated" href="mailto:obmc-host-reset@0.target">obmc-host-reset@0.target</a><br>
              Jan 01 00:00:10 vegman-s2600wf systemd[1]:<br>
              /lib/systemd/system/phosphor-ipmi-net@.socket:3: Invalid
              interface name,<br>
              ignoring: sys-subsystem-net-devices-%i.device<br>
              Jan 01 00:00:10 vegman-s2600wf systemd[1]:<br>
              xyz.openbmc_project.State.Host.service: Cannot add
              dependency job, ignoring:<br>
              Unit xyz.openbmc_project.State.Host.service failed to load
              properly: File exists.<br>
              ----- 8< ------<br>
              Jan 01 00:00:28 vegman-s2600wf power-control[172]: Failed
              to find the PS_PWROK line<br>
              Jan 01 00:00:28 vegman-s2600wf systemd[1]:<br>
              xyz.openbmc_project.Chassis.Control.Power.service: Main
              process exited,<br>
              code=exited, status=255/EXCEPTION<br>
              Jan 01 00:00:28 vegman-s2600wf systemd[1]:<br>
              xyz.openbmc_project.Chassis.Control.Power.service: Failed
              with result 'exit-code'.<br>
              Jan 01 00:00:29 vegman-s2600wf systemd[1]: Failed to start
              Intel Power Control.<br>
              ----- 8< ------<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: ------------[ cut
              here ]------------<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: WARNING: CPU: 0
              PID: 331 at<br>
              net/sched/sch_generic.c:447 dev_watchdog+0x268/0x288<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: NETDEV WATCHDOG:
              eth0 (ftgmac100):<br>
              transmit queue 0 timed out<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: CPU: 0 PID: 331
              Comm: python Not tainted<br>
              5.3.10-7b61b9e #1<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: Hardware name:
              Generic DT based system<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: Backtrace:<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<80107c84>]
              (dump_backtrace) from<br>
              [<80107eb8>] (show_stack+0x20/0x24)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r7:80a12d20
              r6:00000000 r5:9972378c<br>
              r4:00000009<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<80107e98>]
              (show_stack) from<br>
              [<806a84b0>] (dump_stack+0x20/0x28)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<806a8490>]
              (dump_stack) from<br>
              [<80116900>] (__warn.part.0+0xb4/0xdc)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<8011684c>]
              (__warn.part.0) from<br>
              [<80116998>] (warn_slowpath_fmt+0x70/0x98)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r6:805ad4bc
              r5:000001bf r4:80840b28<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<80116928>]
              (warn_slowpath_fmt) from<br>
              [<805ad4bc>] (dev_watchdog+0x268/0x288)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r3:99094000
              r2:80840aec<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r6:00000000
              r5:99071900 r4:9909422c<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<805ad254>]
              (dev_watchdog) from<br>
              [<8015ad94>] (call_timer_fn+0x40/0x124)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r9:00000122
              r8:ffffa6f8 r7:00000100<br>
              r6:805ad254 r5:9909422c r4:9909422c<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<8015ad54>]
              (call_timer_fn) from<br>
              [<8015af18>] (expire_timers+0xa0/0xdc)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r8:ffffa6f8
              r7:80a13a40 r6:99723854<br>
              r5:99723854 r4:9909422c<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<8015ae78>]
              (expire_timers) from<br>
              [<8015aff4>] (run_timer_softirq+0xa0/0x198)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:00000002
              r9:00000100 r8:80a12d20<br>
              r7:80a13a40 r6:80a13a40 r5:99723854<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:99723854
              r3:ffffa6f9<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<8015af54>]
              (run_timer_softirq) from<br>
              [<801022b4>] (__do_softirq+0xdc/0x314)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r8:00000000
              r7:99722000 r6:80a62334<br>
              r5:00000002 r4:00000001<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<801021d8>]
              (__do_softirq) from<br>
              [<8011a93c>] (irq_exit+0xac/0xe4)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:98e186dc
              r9:99722000 r8:00000000<br>
              r7:9d413600 r6:00000001 r5:80a4a5d8<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:00000000<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<8011a890>]
              (irq_exit) from [<8014d1f4>]<br>
              (__handle_domain_irq+0x60/0xb4)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<8014d194>]
              (__handle_domain_irq) from<br>
              [<801021cc>] (avic_handle_irq+0x68/0x70)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r9:99722000
              r8:98e18206 r7:9972396c<br>
              r6:ffffffff r5:99723938 r4:9d402e40<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<80102164>]
              (avic_handle_irq) from<br>
              [<80101a6c>] (__irq_svc+0x6c/0x90)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: Exception
              stack(0x99723938 to 0x99723980)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:<br>
3920:                                                       00000460
              0000054b<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: 3940: 00000008
              000002df 98e18000 de785a57<br>
              00000008 98e1800e 98e18206 000001cb<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: 3960: 98e186dc
              997239b4 0a4e3ec5 99723988<br>
              00000458 803b58e0 20000013 ffffffff<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r5:20000013
              r4:803b58e0<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<803b559c>]
              (lzma_main) from<br>
              [<803b64ec>] (xz_dec_lzma2_run+0x678/0x824)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:00000000
              r9:00000000 r8:98e1e000<br>
              r7:98e1eee8 r6:0000002a r5:98e09a84<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:98e18000
              r3:000003fd<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<803b5e74>]
              (xz_dec_lzma2_run) from<br>
              [<803b4ad4>] (xz_dec_run+0x2d8/0xa78)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:994b0c00
              r9:00000000 r8:98e09a84<br>
              r7:9d608800 r6:00000001 r5:00000001<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:98e09a80<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<803b47fc>]
              (xz_dec_run) from<br>
              [<802c6618>] (squashfs_xz_uncompress+0x8c/0x234)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:994b0c00
              r9:98e09a84 r8:98e09560<br>
              r7:0000001b r6:0000000d r5:00000001<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:98e09a80<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<802c658c>]
              (squashfs_xz_uncompress)<br>
              from [<802c6538>] (squashfs_decompress+0x68/0xa0)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:98e09560
              r9:98e09440 r8:98e09444<br>
              r7:0000001b r6:994b0c00 r5:802c658c<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:990f4200<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<802c64d0>]
              (squashfs_decompress) from<br>
              [<802c20ac>] (squashfs_read_data+0x404/0x734)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:00000000
              r9:994b0c68 r8:98e09560<br>
              r7:994b0bfc r6:0000001b r5:0000026c<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:0000001b<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<802c1ca8>]
              (squashfs_read_data) from<br>
              [<802c27b8>] (squashfs_cache_get+0x238/0x388)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:00000002
              r9:9d602fc0 r8:990ba7b8<br>
              r7:00000000 r6:0131366c r5:990ba780<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:00000001<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<802c2580>]
              (squashfs_cache_get) from<br>
              [<802c2d88>] (squashfs_get_fragment+0x2c/0x34)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:9ee5c5e0
              r9:00000004 r8:99723cd4<br>
              r7:ffffffff r6:9a05be18 r5:9a05be18<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:00000000<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<802c2d5c>]
              (squashfs_get_fragment) from<br>
              [<802c3b2c>] (squashfs_readpage+0xf4/0x920)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<802c3a38>]
              (squashfs_readpage) from<br>
              [<802000b8>] (read_pages+0x10c/0x160)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:00112cca
              r9:00000004 r8:99723cd4<br>
              r7:9a05bf00 r6:00000000 r5:9ee5c5e0<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:9ee5c5e4<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<801fffac>]
              (read_pages) from<br>
              [<80200494>] (__do_page_cache_readahead+0x1b8/0x1d8)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:9a05bf04
              r9:00112cca r8:99723cd4<br>
              r7:00000003 r6:00000004 r5:00000004<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:00000003<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<802002dc>]
              (__do_page_cache_readahead)<br>
              from [<802006cc>] (ondemand_readahead+0x218/0x288)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:00000000
              r9:99f785a0 r8:00000000<br>
              r7:9a05bf00 r6:00000000 r5:00000003<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:99f785f8<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<802004b4>]
              (ondemand_readahead) from<br>
              [<802008b0>] (page_cache_sync_readahead+0x5c/0x7c)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:99723ec0
              r9:99723dd8 r8:00000000<br>
              r7:00000000 r6:00000000 r5:99f785a0<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:9a05bf00<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<80200854>]
              (page_cache_sync_readahead)<br>
              from [<801f8138>]
              (generic_file_read_iter+0x680/0x970)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<801f7ab8>]
              (generic_file_read_iter)<br>
              from [<80242ef4>] (do_iter_readv_writev+0x150/0x1dc)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:00000000
              r9:99723ec0 r8:00000000<br>
              r7:99723ee0 r6:00000000 r5:00000000<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:99f785a0<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<80242da4>]
              (do_iter_readv_writev) from<br>
              [<80243940>] (do_iter_read+0xf4/0x1ac)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:00000000
              r9:00000000 r8:00000001<br>
              r7:99723ee0 r6:99723ec0 r5:99f785a0<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:00000000<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<8024384c>]
              (do_iter_read) from<br>
              [<80244d1c>] (vfs_iter_read+0x28/0x34)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r10:00000000
              r9:00000000 r8:00000400<br>
              r7:99495b40 r6:99723ec0 r5:99723ed8<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r4:9974d700<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<80244cf4>]
              (vfs_iter_read) from<br>
              [<8031e23c>] (ovl_read_iter+0xc0/0x114)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<8031e17c>]
              (ovl_read_iter) from<br>
              [<802442f4>] (__vfs_read+0x150/0x1d4)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r7:00000000
              r6:00000000 r5:99723f60<br>
              r4:99495b40<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<802441a4>]
              (__vfs_read) from<br>
              [<80244418>] (vfs_read+0xa0/0x120)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r9:00000000
              r8:00000001 r7:99723f60<br>
              r6:0175bec0 r5:99495b40 r4:00000400<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<80244378>]
              (vfs_read) from [<80244838>]<br>
              (ksys_read+0x70/0xf8)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r9:00000000
              r8:00000000 r7:00000400<br>
              r6:0175bec0 r5:99495b40 r4:99495b40<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<802447c8>]
              (ksys_read) from<br>
              [<802448d8>] (sys_read+0x18/0x1c)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:  r9:99722000
              r8:801011e4 r7:00000003<br>
              r6:76fe64d0 r5:430015bc r4:01695198<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: [<802448c0>]
              (sys_read) from [<80101000>]<br>
              (ret_fast_syscall+0x0/0x54)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: Exception
              stack(0x99723fa8 to 0x99723ff0)<br>
              Jan 01 00:01:12 vegman-s2600wf kernel:
              3fa0:                   01695198 430015bc<br>
              00000004 0175bec0 00000400 00000000<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: 3fc0: 01695198
              430015bc 76fe64d0 00000003<br>
              000005e8 432d4000 00001001 5dc2157e<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: 3fe0: fbad2488
              7ee24820 42f2d824 42f85f7c<br>
              Jan 01 00:01:12 vegman-s2600wf kernel: ---[ end trace
              0910e44f554793b0 ]---<br>
              ----- 8< ------<br>
              <br>
              There are more errors as well. Please see the attached
              full log.<br>
              <br>
              What do you suggest? How can we make it control the power
              of s2600wf host and<br>
              how do we make the network interface work?<br>
              <br>
              Thank you.<br>
              <br>
              With best regards,<br>
              Alexander Amelkin,<br>
              YADRO [<a href="https://yadro.com" target="_blank"
                rel="noopener noreferrer" data-auth="NotApplicable"
                moz-do-not-send="true">https://yadro.com</a>]<br>
              <br>
              25.10.2019 18:59, Bills, Jason M wrote:<br>
              > I'm copying the mailing list in case there are others
              who have similar questions.<br>
              ><br>
              > On 10/25/2019 2:57 AM, 阿桂 wrote:<br>
              >>     Hi, jason<br>
              >>           Could you help me, please ? My board is
              not a evb board, but it is<br>
              >> x86 platform. So i build openbmc
              *meta-s2600wf*(commit<br>
              >> ID c549f3a7f5496ec3b54ed65c8b4d8351db10995e)
              instead,which use<br>
              >> x86-power-control version
              f61ca6fdcc52beba485e014b5fad38a9e9a555ad<br>
              >> <<a
href="https://github.com/openbmc/x86-power-control/commit/f61ca6fdcc52beba485e014b5fad38a9e9a555ad"
                target="_blank" rel="noopener noreferrer"
                data-auth="NotApplicable" moz-do-not-send="true">https://github.com/openbmc/x86-power-control/commit/f61ca6fdcc52beba485e014b5fad38a9e9a555ad</a>>.<br>
              >> But when i use "ipmitools chassis power status"
              commond to get host status at<br>
              >> my board, it point out "Get Chassis Power Status
              failed: Unspecified error",<br>
              >> journalctl -f command refer to "ipmid[279]:
              Failed to fetch ACBoot property,<br>
              >> ipmid[279]: Failed to fetch RestartCause
              property". It seems there have no<br>
              >> property in dbus.  Where is the dbus
              property ACBoot and RestartCause<br>
              >> defined?I'm puzzled about this /situation. Could
              you///give me some suggestions?<br>
              ><br>
              > This is because the IPMI chassis power status command
              gets the power status by<br>
              > calling the IPMI chassis status command which
              requires a lot of other<br>
              > information such as the restart cause and AC fail
              status to return successfully.<br>
              ><br>
              > The ACBoot property is provided by a small script
              that we run to get the reset<br>
              > reason from uboot.  You can find it here:<br>
              > <a
href="https://github.com/Intel-BMC/openbmc/tree/intel/meta-openbmc-mods/meta-common/recipes-core/ac-boot-check"
                target="_blank" rel="noopener noreferrer"
                data-auth="NotApplicable" moz-do-not-send="true">
https://github.com/Intel-BMC/openbmc/tree/intel/meta-openbmc-mods/meta-common/recipes-core/ac-boot-check</a>.<br>
              ><br>
              > The RestartCause property recently moved to
              x86-power-control and is being<br>
              > synced up in this review:<br>
              > <a
href="https://gerrit.openbmc-project.xyz/c/openbmc/x86-power-control/+/26491"
                target="_blank" rel="noopener noreferrer"
                data-auth="NotApplicable" moz-do-not-send="true">
https://gerrit.openbmc-project.xyz/c/openbmc/x86-power-control/+/26491</a>.<br>
              ><br>
              > Thanks,<br>
              > -Jason<br>
              ><br>
              >> /         Thanks a lot./<br>
              >><br>
              >><br>
            </div>
          </span></font></div>
    </blockquote>
  </body>
</html>