From: Andrei Kartashev <a.kartashev@yadro.com>
To: "Chris Chen (TPI)" <Chris.Chen3@flex.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: [entity-manager] Question about temperature sensor stops update
Date: Fri, 29 Oct 2021 11:33:38 +0300 [thread overview]
Message-ID: <8c73fd80b5e4672e7dcac777cd5d46bc5d6bf0e1.camel@yadro.com> (raw)
In-Reply-To: <DM6PR08MB5514480BAD48B0B200646011DC879@DM6PR08MB5514.namprd08.prod.outlook.com>
Hello,
I didn't catch, what is your problem. As I see from the logs,
everything is fine: temp sensors instantiated, dbus objects created,
readings present. What's wrong?
As for FruDevice: yes, it's kind of weird behaviour: it exposes not
only actual FRU devices but also other I2C devices. You can introspect
that objects and see that they exposes
xyz.openbmc_project.Inventory.Item.I2CDevice interface instead of
xyz.openbmc_project.FruDevice
On Fri, 2021-10-29 at 08:02 +0000, Chris Chen (TPI) wrote:FruDevice
> Hi everyone,
>
> Actually, I have 2 questions as below:
> 1. I got understood from others on the mailing list, that I don't
> have to declare EEPROM or temp sensors on the I2C bus node in my dts,
> and it should be fine even I did it at the beginning. So I tried to
> remove this declaration in dts, then the sensor value I got is fixed,
> no update. Can someone help to take look at why it is?
> Here are some logs that appeared automatically after the
> system booted up. It looks like that entity-manager works fine. And
> the commands I used to check value.
> =======================================
> [ 23.713596] lm75 6-0049: hwmon1: sensor 'tmp75'
> [ 23.718894] i2c i2c-6: new_device: Instantiated
> device tmp75 at 0x49
> [ 23.728520] lm75 6-004c: hwmon2: sensor 'tmp75'
> [ 23.733779] i2c i2c-6: new_device: Instantiated
> device tmp75 at 0x4c
> [ 23.743707] lm75 6-004d: hwmon3: sensor 'tmp75'
> [ 23.749042] i2c i2c-6: new_device: Instantiated device
> tmp75 at 0x4d
>
> # busctl introspect xyz.openbmc_project.HwmonTempSensor
> /xyz/openbmc_project/sensors/temperature/DIMM_P1_EFGH
> xyz.openbmc_project.Sensor.Value
> interface - - -
> .MaxValue
> property d 127 emits-
> change
> .MinValue
> property d -128 emits-
> change
> .Unit
> property s "xyz.openbmc_project.Sensor.Value.Uni... emits-
> change
> .Value
> property d 40.187 emits-
> change writable
>
> # cat /sys/bus/i2c/devices/6-
> 004d/hwmon/hwmon3/temp1_input
> 40187
> =======================================
> 1. From my understanding, there is "detection daemon" which scans
> I2C bus looking for EEPROMs with IPMI FRU data. However, I found all
> devices on the I2C buses would be listed, not only Fru devices, when
> I used the command below. Is this correct?
> # busctl tree xyz.openbmc_project.FruDevice
> `-/xyz
> `-/xyz/openbmc_project
> `-/xyz/openbmc_project/FruDevice
> |-/xyz/openbmc_project/FruDevice/0_80
> |-/xyz/openbmc_project/FruDevice/0_88
> |-/xyz/openbmc_project/FruDevice/2_108
> |-/xyz/openbmc_project/FruDevice/2_112
> |-/xyz/openbmc_project/FruDevice/2_68
> |-/xyz/openbmc_project/FruDevice/2_72
> |-/xyz/openbmc_project/FruDevice/3_22
> |-/xyz/openbmc_project/FruDevice/3_50
> |-/xyz/openbmc_project/FruDevice/4_56
> |-/xyz/openbmc_project/FruDevice/5_48
> |-/xyz/openbmc_project/FruDevice/5_81
> |-/xyz/openbmc_project/FruDevice/6_73
> |-/xyz/openbmc_project/FruDevice/6_76
> |-/xyz/openbmc_project/FruDevice/6_77
> |-/xyz/openbmc_project/FruDevice/7_80
> |-/xyz/openbmc_project/FruDevice/7_88
> |-/xyz/openbmc_project/FruDevice/8_101
> `-/xyz/openbmc_project/FruDevice/hudsonbay ß
> this is the probe name we define in JSON configuration
>
> Thanks.
>
> Regards,
> Chris Chen
> Legal Disclaimer :
> The information contained in this message may be privileged and
> confidential.
> It is intended to be read only by the individual or entity to whom it
> is addressed
> or by their designee. If the reader of this message is not the
> intended recipient,
> is strictly prohibited. If you have received this message in error,
> please immediately notify the sender and delete or destroy any copy
> of this message!
--
Best regards,
Andrei Kartashev
next prev parent reply other threads:[~2021-10-29 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 8:02 [entity-manager] Question about temperature sensor stops update Chris Chen (TPI)
2021-10-29 8:33 ` Andrei Kartashev [this message]
2021-10-29 8:50 ` 回覆: " Chris Chen (TPI)
[not found] ` <a49158e3ebbc40465c73dae77a037643cdc2b7c3.camel@yadro.com>
2021-11-01 9:29 ` 回覆: " Chris Chen (TPI)
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=8c73fd80b5e4672e7dcac777cd5d46bc5d6bf0e1.camel@yadro.com \
--to=a.kartashev@yadro.com \
--cc=Chris.Chen3@flex.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).