From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.5 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3DA6BC5517A for ; Wed, 11 Nov 2020 15:14:07 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 6919620791 for ; Wed, 11 Nov 2020 15:14:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=google.com header.i=@google.com header.b="KlihB3zu" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6919620791 Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 4CWStg2TsbzDqFt for ; Thu, 12 Nov 2020 02:14:03 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=google.com (client-ip=2607:f8b0:4864:20::f34; helo=mail-qv1-xf34.google.com; envelope-from=venture@google.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=google.com header.i=@google.com header.a=rsa-sha256 header.s=20161025 header.b=KlihB3zu; dkim-atps=neutral Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4CWSgr23W8zDqfZ for ; Thu, 12 Nov 2020 02:04:39 +1100 (AEDT) Received: by mail-qv1-xf34.google.com with SMTP id x13so1002665qvk.8 for ; Wed, 11 Nov 2020 07:04:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=09+d4E5wDypx2r5JDCcQj0M6Ib3U9YUkGCwp5paDvtw=; b=KlihB3zuLGdqRg8TvYBloXffftQm19wOHrQEBCdanbdOt1dwwbS3sBMMIM1sIVzN+a r4uv4eLvZIBADgeTIshL8sbzGSTKoU0NuSg9lO608XgQZ5ek6ZdxOOmj4WoAftltAzxt K1iMM7PUtCq/zHqM0y/syHEYaZK7Yi0XnCxjksydVcuVN8EUvOokWGI9hsJ0BXui4WV0 QwVfm9maDVQoNi70PYFwN1WYYgauRcs3m/2cJJvNkLUayaSmMdKjYUiPJz7/sJtzTnvM q/S1HP6kSYIaGgmvX+veFGRc1QKAaMChr9WHmJBHZ++Ph/Kd+XoolT1+NxqiGOkIQ+3g /gyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=09+d4E5wDypx2r5JDCcQj0M6Ib3U9YUkGCwp5paDvtw=; b=g3C0NumvxCdw3S/zGP+F3sh+JF3NvHi0U+hDGd9C841W0hsjrDsl7Aj/Dz+v7hRYXw JEZYJ09LmiRN9+JD9FpSAWOFJidOlyZ7avCtEDmDBF3JEmk8orhPEZwi8B3JtY/O3nBW KGSlMVTs5KA7vT6bf2mErRhJZMZcdfIyPYAT8UMObbNWukIc5s3/YfVUUBesKuwFKPNC hJE7fTgx/PpVICjYRFCr+bJ4igp4FDBoxc4MxEzFCuixiFKDttvK4vEj9JsUyyUgvN8J TTAovn2CJRaaym6H3S4oc3KBbVeFHfujf+OVTCMVtwLNE3bFT9jhd5OlhgX3/YDfp497 bFnQ== X-Gm-Message-State: AOAM530rZNht/M91iRy2miyR4FpOsXTqWWUXZD14HJQAKxAv2Jb80jPf htGfLLYoiFZ4u7XBrxYgZroiI4XovSSMskQuF7wKCA== X-Google-Smtp-Source: ABdhPJwSQYFKmezpBXo8zykcG9/K2nv9bsioIF0KprgmfuPkx4cyZx9ReEgxPPuldpoMqAHLy30yn3UnJ3RmV7I+7yg= X-Received: by 2002:a0c:fc52:: with SMTP id w18mr12283622qvp.48.1605107075054; Wed, 11 Nov 2020 07:04:35 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Patrick Venture Date: Wed, 11 Nov 2020 07:04:23 -0800 Message-ID: Subject: Re: Queries in phosphor-pid-control(swampd) To: Kumar Thangavel Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "openbmc@lists.ozlabs.org" , Patrick Williams , Josh Lehan , "Velumani T-ERS, HCLTech" , Vijay Khemka Errors-To: openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Sender: "openbmc" On Thu, Nov 5, 2020 at 4:22 AM Kumar Thangavel wrote: > > Classification: Internal > > Hi All, > > > > Does the current phosphor-pid-control handled the fan failures or i= f fan values is 0 ? Looks like, it ignores the fan values is 0 case. > > Could you please clarify me, how the fan(single/both) failures hand= led. if both fan failures, Do we need to power off the chassis or need to d= o power sled cycle ? The answers to the failure behaviors you wish are outside the scope of controlling the fans themselves. As I understand it, it's up to you or your use case what happens when fails start failing. The pid control daemon has default fail-safe values you can set, as well as minimum RPM set-points, so that if some things fail, it'll still move forward operating in a best effort to cool the system. But with fans failing, if there's something more one wishes to do with it, my recommendation would be to reach out with a broader email subject line -- there may be something already in openbmc (probably is) that'll track failures and trigger behaviors. However, currently pid control doesn't "manage the system." Which it sounds like you want. Or not? Your question sounds like you're not sure what the system _should_ do in a fan failure case, to which I cannot reply. Thanks! > > > > Thanks, > > Kumar. > > ::DISCLAIMER:: > ________________________________ > The contents of this e-mail and any attachment(s) are confidential and in= tended for the named recipient(s) only. E-mail transmission is not guarante= ed to be secure or error-free as information could be intercepted, corrupte= d, lost, destroyed, arrive late or incomplete, or may contain viruses in tr= ansmission. The e mail and its contents (with or without referred errors) s= hall therefore not attach any liability on the originator or HCL or its aff= iliates. Views or opinions, if any, presented in this email are solely thos= e of the author and may not necessarily reflect the views or opinions of HC= L or its affiliates. Any form of reproduction, dissemination, copying, disc= losure, modification, distribution and / or publication of this message wit= hout the prior written consent of authorized representative of HCL is stric= tly prohibited. If you have received this email in error please delete it a= nd notify the sender immediately. Before opening any email and/or attachmen= ts, please check them for viruses and other defects. > ________________________________