GSP transiently rejects NV0080 object allocation with status 0x1f when
busy — reliably on the first probe in a fresh server process and
intermittently right after RM operations (e.g. a power-limit write).
The probe surfaced that transient rejection as rm_power_supported=false,
making the Experimental Power Control block disappear in the UI until a
reload re-probed successfully.
- hal/rm_power: RmHandle.open() now retries the handle allocation
(3 attempts, 100 ms apart) before reporting the interface unavailable;
covers probe, set, and enable-check paths. Each attempt cleans up its
own fds, so retries are safe and idempotent.
- PerformancePanel: confirm a negative rm_power_supported reading with
one follow-up fetch before rendering it, so a single flaky probe can't
hide the block or flip it into "interface unavailable"; the confirm
has its own error boundary so a failed second request keeps the first
(valid) read. Also added a monotonic fetch-seq guard so a slow
response for a previously selected GPU cannot clobber fresher state.
- tests: cover transient-failure-retry and persistent-failure paths for
RmHandle.open.
Verified live: first probe after restart 5/5 (was 0/3), 150 rapid
set+get cycles with 0 probe flips and 0 set failures.