Comment 164 for bug 414560

What I've noticed after about a day's usage was that there were no more messages in dmesg, but there would still be periods of zero activity over wireless (about 10-15 seconds every few minutes).

So I wouldn't say a "real" fix has been released.

Edit: I just found that it correlates with "wpa_supplicant[1213]: CTRL-EVENT-SCAN-RESULTS" entries in the syslog.

I remember reading something about the driver/interface not being able to "multitask" and scan while being active at the same time - so a scan causes the activity to be paused/broken.