Re: ipw2100: race between isr_indicate_associated and rx path

On Thu, 2009-01-22 at 00:34 +0800, Helmut Schaa wrote:
> 1) The firmware receives the assoc response and moves internally to
> associated
> state, followed by an interrupt which informs the driver about that
> change.
> 2) The driver does _not_ update its internal state to ASSOCIATED in
> the
> interrupt handler. Instead it queues a work to be executed later.
> 3) The firmware receives the identity request from the AP and accepts
> the
> frame as it is in associated state. Followed by an interrupt to the
> driver.
> 4) The driver gets the rx interrupt but drops the frame due to not
> being in
> associated state.
> 5) The queued work is executed and state changes to associated but the
> AP will
> not resend the EAP frame as the firmware already acked it.
> 
> Afterwards wpa_supplicant times out because it did not receive
> anything from the AP.

Good audit. Can you try if scheduling the work immediately (instead of
delayed HZ/10) will fix the problem?

Thanks,
-yi


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword