From: Vijay Khemka <vijaykhemka@fb.com>
To: Ed Tanous <ed.tanous@intel.com>, Patrick Venture <venture@google.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: pid control configuration
Date: Mon, 3 Jun 2019 18:18:38 +0000 [thread overview]
Message-ID: <C8C27C98-73BA-41C9-88C9-A99974210D22@fb.com> (raw)
In-Reply-To: <6b61ef37-4b8b-959a-5131-488d0560ce4c@intel.com>
Thanks Ed,
I will debug with some passthrough data.
Regards
-Vijay
On 6/3/19, 10:44 AM, "Ed Tanous" <ed.tanous@intel.com> wrote:
On 5/31/19 2:00 PM, Vijay Khemka wrote:
>
> This config is failing with below message.
> Apr 12 23:32:39 tiogapass swampd[1310]: terminate called after throwing an instance of 'std::out_of_range'
> Apr 12 23:32:39 tiogapass swampd[1310]: what(): _Map_base::at
>
If I had to guess, you're missing a property that's required.
> Is there any default data which I can be used for config but has no impact in its action?
Like I said before, I don't know of anyone running phosphor-pid like you
are hoping to. The "default" is to run in cascade loop mode, and all
the existing systems are examples of that configuration. It's likely
time for you to break out GDB and start debugging your configuration.
Alternatively, approximating your fans as linear, and using that as the
output targets would likely get you to a working thermal solution faster
than going down the path you're going.
prev parent reply other threads:[~2019-06-03 18:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 22:53 pid control configuration Vijay Khemka
2019-05-01 23:05 ` Ed Tanous
2019-05-01 23:10 ` Patrick Venture
2019-05-01 23:15 ` Patrick Venture
2019-05-02 23:24 ` Vijay Khemka
2019-05-06 16:20 ` Ed Tanous
2019-05-06 18:18 ` Vijay Khemka
2019-05-06 18:54 ` Ed Tanous
2019-05-10 21:20 ` Vijay Khemka
2019-05-13 16:32 ` Patrick Venture
2019-05-13 17:32 ` Ed Tanous
2019-05-15 19:21 ` Vijay Khemka
2019-05-15 21:50 ` Ed Tanous
2019-05-16 0:07 ` Vijay Khemka
2019-05-31 21:00 ` Vijay Khemka
2019-06-03 17:43 ` Ed Tanous
2019-06-03 18:18 ` Vijay Khemka [this message]
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=C8C27C98-73BA-41C9-88C9-A99974210D22@fb.com \
--to=vijaykhemka@fb.com \
--cc=ed.tanous@intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=venture@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.