What wakes a deaf ring: three tries and the vendor's way, on the second XGS 3300, 2026-10-27
Issue 361: now and then a receive ring of the XGS 3300 raises its interrupt and the host never runs the handler. The look of 2026-10-21 finds such a ring within a tick or two and takes its packets, but the ring stays deaf: the block sends nothing for the next ones (lost-interrupt-2026-10-21.md). #793 put in three things to try on such a ring, and a way to leave the ring's status bit alone as the vendor's host does, all off by default. This is the soak that compares them. None of the three brings the ring back as a rule, and leaving the status bit alone does not stop rings going deaf.
The whole page, with how it was taken and what it does not show: What wakes a deaf ring: three tries and the vendor's way, on the second XGS 3300, 2026-10-27.
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.