Thanks Dan, Kevin, [...] [suspend/resume] > [ 58.835223] wlan0: authenticate with 30:46:9a:68:a9:52 > [ 58.864519] wlan0: send auth to 30:46:9a:68:a9:52 (try 1/3) > [ 59.067596] wlan0: send auth to 30:46:9a:68:a9:52 (try 2/3) > [ 59.271484] wlan0: send auth to 30:46:9a:68:a9:52 (try 3/3) > [ 59.475356] wlan0: authentication with 30:46:9a:68:a9:52 timed out Yeah ... we saw this in the lab at some point, but somehow we couldn't reproduce it again later. The issue is that we stop the queues, and never restart them, and if it's the same issue then it's definitely the driver's fault. To confirm, when you get this, can you please do sudo cat /sys/kernel/debug/ieee80211/phy*/queues (assuming you have mac80211 debugfs compiled) If it's really the same bug, the first four queues (0-3) will show something like 00: 0x00000001/7 01: 0x00000001/0 02: 0x00000001/0 03: 0x00000001/0 [...] If this is the case, then I'd appreciate if you could do tracing. To do that, make sure CONFIG_IWLWIFI_DEVICE_TRACING is set in your kernel config (which requires CONFIG_EVENT_TRACING, you can use the / key in menuconfig to search for items). When you have that, grab the trace-cmd tool (ubuntu ships it now I believe) and start tracing *before* you suspend: sudo bash -c "echo global > /sys/kernel/debug/tracing/trace_clock" sudo trace-cmd record -e mac80211 -e iwlwifi -e iwlwifi_msg then suspend and resume while it's running, and ctrl-c later after it failed to connect after resuming. Then you get a file "trace.dat", compress it and send it to me privately (it's large, and may contain information you might consider private, like your AP name/BSSID/etc.) Thanks! If that's too much effort, let me know and I'll try to reproduce, but I'll probably need to have more info on your setup etc. as I haven't been able to reproduce this in mine yet, but I also have issues with suspend/resume anyway quite frequently :-( johannes -- 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
