Implement a workaround for missing Tx completion interrupts in iwm(4).

iwm(4) releases resources whenever hardware signals Tx completion for a
frame at Tx queue index 'N'. It has been observed that we sometimes get
an interrupt for frame 'N - 2' followed by an interrupt for frame 'N',
with no interrupt being received for frame 'N - 1'.

Whenever this occurred a later decision to roam to another AP would fail
since AP node references for frames affected by missing interrupts were
never released. Another side-effect was an mbuf leak.

The problem was first observed at 36c3 and debugged there with bluhm@.

ok tobhe@

0 files changed, 0 insertions, 0 deletions