archive mirror
 help / color / mirror / Atom feed
From: Paul Fertser <>
To:, Yong Li <>
Cc: Zhikui Ren <>, Ed Tanous <>
Subject: xyz.openbmc_project.BeepCode and PSUSensors
Date: Tue, 20 Jul 2021 11:57:36 +0300	[thread overview]
Message-ID: <20210720085736.GD875@home.paul.comp> (raw)


Commit 3046a0242cfde0cbf871f632c2c143b48ac30c71 introduced support for
doing RPC to xyz.openbmc_project.BeepCode , but I do not see any
daemon claiming that bus mentioned anywhere.

As the result, the log gets these ugly messages:

beep error (ec = generic:113)

What am I missing? Is there a dependency someone has forgotten to add
for dbus-sensors? Or is this support runtime-optional and the error
should be handled appropriately to not spam the logs?

Where's the daemon handling xyz.openbmc_project.BeepCode anyway? Quick
search didn't let me find any sources for that.

Be free, use free ( software!

                 reply	other threads:[~2021-07-20  8:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210720085736.GD875@home.paul.comp \ \ \ \ \ \

* 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).