https://bugzilla.novell.com/show_bug.cgi?id=441511
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=441511#c15
--- Comment #15 from Helmut Schaa 2009-01-21 06:40:45 MST ---
I was able to track the problem described in comment #14 down to a race in the
ipw2100-driver (luckily not the firmware). The circumstances are as follows:
1) The firmware receives assoc response and moved 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) Driver gets 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.
Now thinking about how to fix this issue.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.