From: Zhenfei Tai <ztai@google.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Cc: Ed Tanous <ed@tanous.net>
Subject: [redfish/v1/Systems/system/Processors] How does it work on wolf pass?
Date: Fri, 9 Oct 2020 17:57:09 -0700 [thread overview]
Message-ID: <CAMXw96NCuqbeaOMQaO_BU2+_qQojOfLQdH-1=JS16vfanSZPdw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
Hi,
I've been testing bmcweb and noticed the response from the URI
`redfish/v1/Systems/system/Processors` contains an empty collection.
{
"@odata.context":
"/redfish/v1/$metadata#ProcessorCollection.ProcessorCollection",
"@odata.id": "/redfish/v1/Systems/system/Processors/",
"@odata.type": "#ProcessorCollection.ProcessorCollection",
"Members": [],
"Members@odata.count": 0,
"Name": "Processor Collection"
}
Looking at bmcweb code, it seems to look for dbus interfaces
`xyz.openbmc_project.Inventory.Item.Cpu` and
`xyz.openbmc_project.Inventory.Item.Accelerator`. However they can't be
seen in dbus.
# busctl tree --no-pager xyz.openbmc_project.Inventory.Item.Cpu
Failed to introspect object / of service
xyz.openbmc_project.Inventory.Item.Cpu: The name is not activatable
Entity-manager and cpu-sensor are running in addition to bmcweb. The
entity-manager config is below and I can see the config is picked up in
`xyz.openbmc_project.EntityManager`.
{
"Exposes": [
{
"Address": "0x30",
"Bus": 0,
"CpuID": 1,
"Name": "CPU 1",
"Type": "XeonCPU"
},
{
"Address": "0x31",
"Bus": 0,
"CpuID": 2,
"Name": "CPU 2",
"Type": "XeonCPU"
}
],
"Name": "internal_code_name",
"Probe": "xyz.openbmc_project.FruDevice({'BOARD_PRODUCT_NAME':
'internal_product_name'})",
"Type": "Board"
}
I'm not sure what else is required to have the URI work properly. Could
someone familiar with this issue help?
Thanks,
Zhenfei
[-- Attachment #2: Type: text/html, Size: 2526 bytes --]
next reply other threads:[~2020-10-10 0:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 0:57 Zhenfei Tai [this message]
2020-10-12 16:23 ` [redfish/v1/Systems/system/Processors] How does it work on wolf pass? Bills, Jason M
2020-10-14 9:06 ` Brad Chou
2020-10-14 9:57 ` Andrei Kartashev
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='CAMXw96NCuqbeaOMQaO_BU2+_qQojOfLQdH-1=JS16vfanSZPdw@mail.gmail.com' \
--to=ztai@google.com \
--cc=ed@tanous.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).