This isn't a network-manager problem, so marking invalid there.
In this case I the microcode errors are a side effect of frequent
reassociations caused by invalid channel swtich announcements from the
AP. These errors _are_ a problem, but the issues with this specific
network can be fixed by ignoring these invalid IEs. I'll post a fix
shortly.
** Changed in: network-manager (Ubuntu Saucy)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Summary changed:
- 8086:0085 Intel wireless microcode driver failure in Saucy causes disconnects
+ Invalid ECSA IEs in probe response frames causes connection to drop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201470
Title:
Invalid ECSA IEs in probe response frames causes connection to drop
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201470/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
