oxidecomputer / oxidecomputer/omicron
Reservoir increase, a bridge too far?
@leftwo is already working on this.
Since Aug 26, 2026.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
I'm beginning to suspect the increase in reservoir size may have increased memory pressure a bit too far.
I'm opening this as a tracker issue to collect other issues and data to determine if we need to claw back some memory for the rest of the system.
Some issues that may be related:
https://github.com/oxidecomputer/stlouis/issues/1033
https://github.com/oxidecomputer/stlouis/issues/1034 This has been integrated from upstream as oxidecomputer/illumos-gate@8d9c1e6
https://github.com/oxidecomputer/omicron/issues/10871
There are some still to be triaged kernel cores from dogfood in /staff/core/dogfood-2026-07-29-misc-cores/ as well as several userland cores to be inspected (locating forthcoming)
More possibly related issues, though these are their own unique issues, I suspect the lower free memory may have increased the chance of us seeing them:
https://github.com/oxidecomputer/omicron/issues/10980
https://github.com/oxidecomputer/omicron/issues/10981
And older issue that I believe we stumbled across:
https://www.illumos.org/issues/14131
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.
Assessment
This issue has not been assessed yet.