In message <v6wump3x4c.fsf@kechara.flame.org>, Michael Graff writes:
>It started perhaps a few months ago.  I think the problem is related
>to something that mycroft pointed out once on icb -- the wi driver
>processes N interrupts, then exits the processing loop.

>The value is 10 in the stock source.  I upped that to 100, and things
>for a lot better.  I'm considering removing the loop limit entirely to
>see what happens, or setting it really, really high.

Oh-hoh!  That might fit with my errors too.

I guess the idea is to avoid swamping the system if there's a lot of pending
stuff - but we should do something to say "go elsewhere in the system if you
must, but come back, we still have stuff to do".

-s