Quoting Larry Finger <Larry.Finger@xxxxxxxxxxxx>:
On 03/11/2013 02:17 PM, Jussi Kivilinna wrote:
Quoting Jussi Kivilinna <jussi.kivilinna@xxxxxx>:
Hello,
I've made some more testing, and noticed that device does not go completely
silent...
I can now reproduce this hang without large transfers with
'ifconfig wlan0 up;
iw dev wlan0 scan & sleep 0.02; ifconfig wlan0 down'.
The large tranfers caused connection to fail sometimes, leading
wpa_supplicant
to issue scan that is aborted. Manually aborting scan causes
device/driver go
into this partial silence state too (with beacons/probe requests received).
So maybe driver does not do all the required clean-ups for aborted scans?
Have you tested 'ifconfig wlan0 up & sleep 0.02; ifconfig wlan0
down'? Is the scan part absolutely necessary?
Scan appearently is not necessary, 'ifconfig wlan0 up & sleep 0.02;
ifconfig wlan0 down' is enough. Just doing 'ifconfig wlan0 up;
ifconfig wlan0 down' is enough.
I also tested with monitor interface opened for tcpdump while doing
'ifconfig up&down' on wlan0 and still triggered the issue. Then
turning wlan0 up resulted monitor interface only receiving probe
requests from nearby devices.
-Jussi
--
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
