The coprocessor taken up again in place, on both families, 2026-10-26
768: when the coprocessor's fast path
stops, the host stays up and takes it up again in place, and restarts the appliance only if that
fails - the default since 0.1.0-alpha.8.6 ("Take it up again, or restart", XGS: Settings). What is
measured here is 0.1.0-alpha.8.7 - and, with IPsec associations on an OCTEON TX coprocessor, the
octep.ko and recover.sh of the change after it - as an appliance meets it: the fast path stopped on
purpose on the coprocessor, and nothing done by hand after that - scripts/xgs/fastpath.py, from
cron, sees the driver take the coprocessor as gone and runs scripts/xgs/recover.sh. The PC asks the
appliance every 3 s how its driver stands and prints a line when the answer changes; after the
heartbeat answers again it prints what recover.sh logged, whether the host was restarted (its boot
time before and after), the management link, and a ping through the appliance.
The whole page, with how it was taken and what it does not show: The coprocessor taken up again in place, on both families, 2026-10-26.
The discussion of this page is held in the project's GitHub Discussions. Showing it here loads giscus from giscus.app and GitHub, and writing in it needs a GitHub account - what that means.