From: "Bills, Jason M" <jason.m.bills@linux.intel.com>
To: openbmc@lists.ozlabs.org
Subject: Re: [redfish/v1/Systems/system/Processors] How does it work on wolf pass?
Date: Mon, 12 Oct 2020 09:23:43 -0700 [thread overview]
Message-ID: <943f9c80-1f3c-b64d-1cb7-02b90d999be2@linux.intel.com> (raw)
In-Reply-To: <CAMXw96NCuqbeaOMQaO_BU2+_qQojOfLQdH-1=JS16vfanSZPdw@mail.gmail.com>
On 10/9/2020 5:57 PM, Zhenfei Tai wrote:
> 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 <http://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?
On Intel systems, we currently get most CPU information from the SMBIOS
tables which are provided to the BMC through something called the MDR.
That application is available here: https://github.com/Intel-BMC/mdrv2.
When we have seen empty CPU or memory resource collections in Redfish,
it has usually been caused by a failure to get the SMBIOS data from BIOS.
>
> Thanks,
> Zhenfei
next prev parent reply other threads:[~2020-10-12 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 0:57 [redfish/v1/Systems/system/Processors] How does it work on wolf pass? Zhenfei Tai
2020-10-12 16:23 ` Bills, Jason M [this message]
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=943f9c80-1f3c-b64d-1cb7-02b90d999be2@linux.intel.com \
--to=jason.m.bills@linux.intel.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 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).