Johannes Berg <johannes@xxxxxxxxxxxxxxxx> writes: > Kalle and Lennert reported problems with the new work > code, and at least Kalle's problem I was able to trace > to a missing jiffies initialisation. > > I also ran into a problem where occasionally I couldn't > connect, which seems fixed with kicking the work items > after scanning. > > Finally, also add some sanity checking code to verify > that we're not adding work items while an interface is > down -- that case could lead to something similar to > what Lennert was seeing. > > There still seems to be a race condition that we're > trying to figure out separately. This seems to help with my problem, it associated quickly: Jan 6 18:05:36 tikku kernel: [ 153.527515] wlan0: direct probe responded Jan 6 18:05:36 tikku kernel: [ 153.536061] wlan0: authenticate with 00:1e:ab:10:e0:c2 (try 1) Jan 6 18:05:36 tikku kernel: [ 153.537910] wlan0: authenticated Jan 6 18:05:36 tikku kernel: [ 153.537924] phy0: device now idle Jan 6 18:05:36 tikku kernel: [ 153.538563] wlan0: associate with 00:1e:ab:10:e0:c2 (try 1) Jan 6 18:05:36 tikku kernel: [ 153.538578] phy0: device no longer idle - working Jan 6 18:05:36 tikku kernel: [ 153.578808] wlan0: RX AssocResp from 00:1e:ab:10:e0:c2 (capab=0x11 status=0 aid=1) Jan 6 18:05:36 tikku kernel: [ 153.578814] wlan0: associated Because I'm currently travelling, I have tested this only once. Will test more when I get back home. Thanks for the patch. > Signed-off-by: Johannes Berg <johannes@xxxxxxxxxxxxxxxx> Tested-by: Kalle Valo <kalle.valo@xxxxxx> -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
