oxidecomputer / oxidecomputer/hubris
when the fan hotswaps don't show power good and we can't sequence, we should go ask them why
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
Our level one diagnostics work great, this is from a failure at a customer site:
Diagnosis { now: 0x763282, reason: MapoDetected, details: StuckInIdle { why: FanPowerNotOk, a0_en: true } }
So cool, we MAPO'd because one (or more) of the fan hotswaps lost PG. Each of the fan hotswaps has an i2c interface:
We should go ask the errant hotswap why it's off and provide that information as the next level of diagnosis.
Ideally we want to understand if this is a shorted fan, a broken motherboard etc so anything about the failure that we can get out of these would be good. We do also wire the alerts up to the FPGA irq collector for smbus fun and profit
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
Start by locating the level-one diagnostics handling for FanPowerNotOk and the fan hotswap I2C and FPGA IRQ paths. Determine how to query the errant hotswap and expose its failure details; done means the next diagnostic level reports whether the fan or motherboard failure information is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100