Hi again, Jonathan Nieder wrote: > As discussed at [1], Camaleón has been experiencing unwanted random > wireless reconnects with various 3.2.y kernels up to and including > 3.2.19: This was first reproduced on a kernel closely based on 3.2.9. It would typically happen pretty reliably once a day or so. Four days of testing a kernel close to 3.2.2 haven't triggered it again[1]. The only brcm80211 change in that range is f96b08a7e6f6 brcmsmac: fix tx queue flush infinite loop So maybe the timeout is too short and this safety is tripping when it shouldn't. I've asked Camaleón to try a recent 3.2.y kernel with and without that commit reverted to test this guess. That leaves another mystery: which of the 22 changes listed at [2] was providing relief in earlier tests? E.g., does > c261bdf8acad brcm80211: smac: indicate severe problems to Mac80211 make it easier to recover from this kind of error? Are there commands we should run or diagnostics to try to get a better sense of what is going on? Grasping at straws, Jonathan [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=220;bug=664767 [2] http://thread.gmane.org/gmane.linux.kernel.wireless.general/92452 -- 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
