On Thu, Dec 16, 2010 at 9:44 AM, Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> wrote: > Try this: Happy new year. I've tried this patch, and the system continues to suspend and resume successfully (i.e, the fix from the earlier patches continues to alleviate the original problem), however the system continues to be "deaf" to beacons at resume time if the system suspends and resumes while associated. You don't need a ChromeOS system to reproduce this issue. Just associate to the network and suspend/resume. On resume the system believes it should be associated, but then the beacon loss timer kicks in and we disassociate, since we are never successful in receiving a response. -- Paul -- 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
