Where is this on the priority list? What can I do to help? ("Go away until the release is out." might be the right answer.)
There are (at least) 4 tickets on this: http://dev.laptop.org/ticket/10232 WiFi dies on suspended XO-1, os300 http://dev.laptop.org/ticket/10092 Networking broken over suspend/resume on os13 for XO-1 http://dev.laptop.org/ticket/9960 wake-on-WLAN doesn't always work (duplicate) http://dev.laptop.org/ticket/9967 ibertas suspend fails on XO-1 (fixed) I know about the ARP problem. I can avoid that by manually setting up the ARP table. I see two patterns. (Most of this should be in 10232.) The first case looks like a simple lost interrupt/wakeup. If so, it should be easy to get some more information. The symptoms are that the left WiFi LED is on. The right WiFi LED blinks when I ping that system but the CPU doesn't wakeup. Poking the touchpad wakes it up. Then it starts processing packets. I've got the back of a system off. Is there a handy place to get a scope/meter on the wakeup signal from the WiFi module to the EC? Is that signal edge triggered or level sensitive? The other case has the left WiFi LED off. The right LED doesn't blink if I ping it. I can wakeup the system with the touchpad but that doesn't fix the WiFi. If I shift to the neighborhood view and poke my AP, it disconnects, reconnects, the left LED goes on, and packets work again. There is code that occasionally checks the other channels, looking for APs and such. While that is going on, the left WiFi LED blinks. What happens if the system suspends when that code is in the middle of switching channels? Where is that code? Can I easily turn it off? -- These are my opinions, not necessarily my employer's. I hate spam. _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel