On 07/21/2017 08:00 PM, Carl D. Blake wrote:
I don't see any further messages that indicate why the driver is
deauthorizing. I do notice that I get the message from wpa_supplicant
that it failed to initiate sched scan right before the disconnect
wpa_s is always good for some trouble. So one thing you could do is to
start wpa_s by hand and enable the debug options and see what wpa_s doing:
# wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -s -dd
Could this have something to do with it?
The DHCP code in ConnMan is not really driving anything directly. That
means we would see something from service.c which tells us it decided to
disconnect. But we don't see that either. So we should look at wpa_s.
I'm unconvinced that
this is a problem with the driver. The disconnect occurs reliably after
30 minutes of being connected. I can set my watch by it.
I agree, if you see can reproduce this with different wifi cards it is
probably not the drivers.