New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fan Control / Hwmon(#2329): Handle OCC temp sensor failure #2222
Comments
Are we exposing these values via the sensor value attribute? I feel like this case should be translated into |
Pre-4.13 these 0x00 & 0xFF values were being presented in the sensor value attribute. A driver update was made (and included in post-4.13) to provied EAGAIN for 0x00 and EIO on 0xFF, however the user side support in hwmon was not complete, hence this issue. This problem is in discussion right now and scheduling the work is underway. |
https://gerrit.openbmc-project.xyz/10334 wspoon: Handle faulted OCC temp sensors |
When a temp sensor provided by the OCC is faulted, set the fans to full speed(10500 RPMs) Tested: Set Functional property of an OCC provided sensor to `true` and fans are set to 10500. Fan speeds drop when the same Functional property is set to `false` Resolves: openbmc/openbmc#2222 Change-Id: Iddd9049fc9677ca587422a5bf4104c0d3787af1a Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
When a temp sensor provided by the OCC is faulted, set the fans to full speed(10500 RPMs) Tested: Set Functional property of an OCC provided sensor to `true` and fans are set to 10500. Fan speeds drop when the same Functional property is set to `false` Resolves: openbmc/openbmc#2222 Change-Id: Iddd9049fc9677ca587422a5bf4104c0d3787af1a Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
When a temp sensor that is provided by the OCC times out having read failures, a 0xFF value is returned in the current temp reading byte. When a 0xFF is read by fan control, the fans for zone 0 should be set to full speed (10500rpms)
The text was updated successfully, but these errors were encountered: