Nicola: Thanks for the link. I see two patches there.
The first one fixes a memory corruption in the wireless device's SRAM that, according to the commit message, would result in the message "Queue 2 stuck for 10000ms" in dmesg. I'm not seeing that in anyone's logs, so I suspect the patch isn't going to help.
The second one sounds more like the association failures seen in some of the logs, but the commit that is identified as introducing the problem (cfg80211: use compare_ether_addr on MAC addresses instead of memcmp) wasn't merged to Linus's tree until 3.5-rc1. No released Ubuntu kernel is using 3.5 yet, so the patch there is not going to help either.
Nicola: Thanks for the link. I see two patches there.
The first one fixes a memory corruption in the wireless device's SRAM that, according to the commit message, would result in the message "Queue 2 stuck for 10000ms" in dmesg. I'm not seeing that in anyone's logs, so I suspect the patch isn't going to help.
The second one sounds more like the association failures seen in some of the logs, but the commit that is identified as introducing the problem (cfg80211: use compare_ether_addr on MAC addresses instead of memcmp) wasn't merged to Linus's tree until 3.5-rc1. No released Ubuntu kernel is using 3.5 yet, so the patch there is not going to help either.