oxidecomputer / oxidecomputer/hubris
Gimlet switches to `A0PlusHP` suspiciously quickly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
Testing on gimlet-d (on niles), I hit 0 in humility dashboard to go to A0. Normally, the power in the lower-right corner changes to A0 for a while, then to A0PlusHP once the NIC is enabled. However, I'm seeing it go to A0PlusHP immediately. This is weird and suspicious.
Relevant Hubris code is here:
https://github.com/oxidecomputer/hubris/blob/fbd918a6ecbf19cf00cca2425443cc68bcce3889/drv/gimlet-seq-server/src/main.rs#L615-L621
https://github.com/oxidecomputer/hubris/issues/1187 may be related; we can debug further by looking at NicSMStatus when the weirdness occurs.
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
Reproduce the transition on gimlet-d on niles using humility dashboard, then inspect drv/gimlet-seq-server/src/main.rs around lines 615-621. Compare the behavior with issue #1187 and examine NicSMStatus when the unexpected transition occurs. Done means identifying why A0PlusHP appears immediately and restoring the expected staged transition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100