Comment 9 for bug 1585863

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote : Re: WiFi malfunction after suspend & resume stress

That seems wrong. This change was done because you might otherwise get stray SCAN_DONE signals when the scan is in progress -- we should still be getting a SCAN_DONE signal later from the supplicant when we get the scan results. The issue here is that the scan may not be done correctly on return from suspend, but I doubt that forcing a SCAN_DONE to look at the scan results again is the right way to go about fixing this.

Since the issue can be resolved by asking the driver to scan again (via wpa or via iw dev wlan0 scan) and only seems to apply for iwlwifi (as far as I've heard), it would probably really point to either a driver or a wpasupplicant bug.

Tony, what are your thoughts on this? I know you recently spent a lot of time looking at the scanning/scan results logic?