From: James Feist <james.feist@linux.intel.com>
To: Peter Lundgren <peterlundgren@google.com>,
openbmc@lists.ozlabs.org, vernon.mauery@linux.intel.com,
jae.hyun.yoo@linux.intel.com, Josh Lehan <krellan@google.com>,
Alex Qiu <xqiu@google.com>, Xiang Liu <xiangliu@google.com>,
Sui Chen <suichen@google.com>
Subject: Re: Performance issue with psusensor / dbus-sensors
Date: Fri, 14 Feb 2020 14:29:27 -0800 [thread overview]
Message-ID: <a47f684f-7007-1f55-190d-0edf79c0c0ba@linux.intel.com> (raw)
In-Reply-To: <CAK13xKNkmy5fTgi0xLK=F+fBJbA7EN3bRsinLbN2sTknfiCGwA@mail.gmail.com>
On 2/14/20 2:14 PM, Peter Lundgren wrote:
> We're running into some occasional and hard to reproduce performance
> issues with sensors on the entity-manager/dbus-sensors/intel-ipmi-oem
> software stack. I don't have much concrete to say on the subject, but I
> want to put a feeler out to see if anyone else has seen similar issues.
> Here's what we think so far:
>
> Complaints range from IPMI sensor reads being slower than normal to
> sensors "never" updating.
>
> Josh got access to one machine in a bad state and observed this:
>
> 1. All the I2C buses were working normally. i2cdetect ran successfully
> on each bus.
> 2. hwmon was working fine. He wrote a shell script to read all of the
> *_input sysfs files and could read every sensor in the system in 3
> seconds.
> 3. psusensor was running.
> 4. busctl --no-pager monitor | grep -i PropertiesChanged shows no
> traffic. On a healthy system, it shows many updates per second. No
> obvious error messages in journalctl --no-pager -f.
> 5. Restarting psusensor alleviates the problem.
Not sure if it's 100% related but Jae is looking into an issue with the
CPU sensor not reporting data after DC cycles. We haven't root caused it
completely yet but we'll let you know what we find.
-James
>
next prev parent reply other threads:[~2020-02-14 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 22:14 Performance issue with psusensor / dbus-sensors Peter Lundgren
2020-02-14 22:29 ` James Feist [this message]
2020-02-14 23:40 ` Vijay Khemka
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=a47f684f-7007-1f55-190d-0edf79c0c0ba@linux.intel.com \
--to=james.feist@linux.intel.com \
--cc=jae.hyun.yoo@linux.intel.com \
--cc=krellan@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=peterlundgren@google.com \
--cc=suichen@google.com \
--cc=vernon.mauery@linux.intel.com \
--cc=xiangliu@google.com \
--cc=xqiu@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.