On Tue, Jan 04, 2011 at 02:29:53PM -0800, Paul Stewart wrote: > On Tue, Jan 4, 2011 at 10:19 AM, Paul Stewart <pstew@xxxxxxxxxx> wrote: > > 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. > > Whoops. I didn't apply that change correctly. Actually, I think this > change works. I think I may have spotted a couple of unrelated > anomalies I'll trace down and address separately. Great, I think this patch got sucked up already, I'll check. Luis -- 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
