oxidecomputer / oxidecomputer/hubris

`monorail` should degrade gracefully when the tech ports are not available

Open
#2,625 5 comments 0 reactions 1 assignee View on GitHub

@hawkw is already working on this.

Since Aug 4, 2026.

Dominant language
Rust
Stars
3.6k
Forks
239
Avg merge
1d 12h
Merged PRs (30d)
23

Description

As discovered on https://github.com/oxidecomputer/hubris/issues/1410, the oscillator for the tech port PHY on the front IO board does not always work. We worked around this by power cycling the front IO board when monorail detects a problem (see https://github.com/oxidecomputer/hubris/blob/master/task/monorail-server/src/bsp/sidecar_bcd.rs#L270-L291). Something we've seen in the field a small number of times is this loop running infinitely. While we of course need to get to the bottom of that, a step in the right direction in the near term would be to let the rest of the management network operate while noting the tech ports are down. Ideally we'd have an ereport or some structured way of discovering the switch was in this state as well.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.