<div dir="ltr"><span style="font-size:13px">> But the driver seems to be misbehaving.. Which WLAN hardware and driver</span><br style="font-size:13px"><span style="font-size:13px">are you using?</span><br style="font-size:13px"><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">I'm using the ath9k driver with </span>Atheros AR9285 chipset.<span style="font-size:13px"><br></span></div><div><span style="font-size:13px"><br></span></div><div><span class="im" style="font-size:13px">>> I'd rather not look into the kernel if I don't have to, but based on these<br>>> logs, would that be the next place to look?<br><br></span><span style="font-size:13px">> Yes</span><span style="font-size:13px"><br></span></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">Thanks, confirmed that the bug is in the kernel driver and I now have a fix and everything working well.</span></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">Thanks,</span></div><div><span style="font-size:13px">Aaron</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 22, 2014 at 4:19 AM, Jouni Malinen <span dir="ltr"><<a href="mailto:j@w1.fi" target="_blank">j@w1.fi</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, Dec 16, 2014 at 12:24:50PM -0500, Aaron Small wrote:<br>
> I use wpa_supplicant with NetworkManager on linux to connect to wifi. A few<br>
> months ago after a platform update (I'm not sure exactly what was updated,<br>
> whether it included wpa_supplicant and/or other things), wifi stopped<br>
> working after pm-suspend/resume.<br>
<br>
</span><span class="">> So I am wondering: should wpa_supplicant work after pm-suspend/resume, or<br>
> is it normal that it needs to be restarted? Because I was using it with<br>
> NetworkManager, I don't know, maybe NetworkManager was restarting it<br>
> before, and isn't now and that's what broke.<br>
<br>
</span>wpa_supplicant on its own was able to reconnect fine when I last tested<br>
this.<br>
<span class=""><br>
> and this in wpa_supplicant's log on resume:<br>
> wlan0: SME: Trying to authenticate with 00:24:01:6f:15:3f (SSID='oakmore'<br>
> freq=2437 MHz)<br>
<br>
</span>So wpa_supplicant is aware that connection was lost on suspend and is<br>
trying to recover here..<br>
<span class=""><br>
> nl80211: Authentication request send successfully<br>
> wlan0: SME: Authentication timeout<br>
<br>
</span>But the driver seems to be misbehaving.. Which WLAN hardware and driver<br>
are you using?<br>
<span class=""><br>
> which seems to me like wpa_supplicant is trying to connect and linux is not<br>
> allowing it? But if something is wrong in the kernel, then I'm not sure why<br>
> restarting wpa_supplicant would fix it.<br>
<br>
</span>Restarting wpa_supplicant will set the interface down and up which will<br>
likely reset driver state and can fix things there..<br>
<span class=""><br>
> I'd rather not look into the kernel if I don't have to, but based on these<br>
> logs, would that be the next place to look?<br>
<br>
</span>Yes<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Jouni Malinen PGP id EFC895FA<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
HostAP mailing list<br>
<a href="mailto:HostAP@lists.shmoo.com">HostAP@lists.shmoo.com</a><br>
<a href="http://lists.shmoo.com/mailman/listinfo/hostap" target="_blank">http://lists.shmoo.com/mailman/listinfo/hostap</a><br>
</div></div></blockquote></div><br></div>