Since a fatal trap can happen at aribtrary times, don't panic when the completions are not in a consistent state.

[jhb]

Just a few spelling nits: s/aribtrary/arbitrary/ in log, s/panicing/panicking/ (yes, it looks weird to me too, but adding the 'k' appears to be correct for adding -ing or -ed), s/sceduler/scheduler/, s/leading/leaving/. I still do double spaces at start of sentences in monospace fonts as well FWIW (and style(9) probably wants a blank line before the block comment).

I think your change probably makes sense though. We do similar hacks for lock assertions for similar reasons IIRC.

[markj]

sys/dev/nvme/nvme_qpair.c

573

While here the \n can be removed from the kassert string.

[imp]

sys/dev/nvme/nvme_qpair.c

573

gotcha

[imp]

Try a little harder, add comments.

[imp]

Plug more holes with tips from kib, jhb and markj.

[imp]

Remove now-obsolete comment.

[imp]

better comment.