oxidecomputer / oxidecomputer/hubris
losing CPU temperature induces a fan party
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
I'm un-convinced that this is good behavior, loss of the CPU temperature does potentially indicate a system wide problem and does make a thermal control loop hard, but I'd propose that a more correct behavior here would be to log the fact that this happened, optionally spins fans up (incrementally) to provide margin if the system was hot, put something in both an ereport and a ring buffer and desequence.
As it is, there's no up-stack reporting that something is wrong and we're left hoping someone notices the fans totally spun up and reports a problem, we should change this to provide automated failure reporting and make sure we can find out that something happened in a reasonable way.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Trace where loss of CPU temperature is handled and inspect the existing fan-control, ereport, and ring-buffer paths first. Done should include automated reporting of the failure, recorded ring-buffer and ereport entries, and a defined safe fan response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100