* Ricardo Salveti <rsalveti@xxxxxxxxxxxx> [181211 20:45]: > On Tue, Dec 11, 2018 at 6:23 PM Ricardo Salveti <rsalveti@xxxxxxxxxxxx> wrote: > > > > On Tue, Dec 11, 2018 at 6:12 PM Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > > > > > * John Stultz <john.stultz@xxxxxxxxxx> [181211 19:51]: > > > > On Tue, Dec 11, 2018 at 11:25 AM Ricardo Salveti <rsalveti@xxxxxxxxxxxx> wrote: > > > > > Then tried to reproduce with a simple 'while true; do ip link set dev > > > > > wlan0 down; ip link set dev wlan0 up; done;' and it was already enough > > > > > to cause the same hang. Adding a simple sleep 1 after down/up is > > > > > already enough to make it work, so something might be missing during > > > > > the down/up process that only happens when they get called right after > > > > > the other. > > > > > > With while true test above, I'm getting: > > > > > > wlcore: ERROR timeout waiting for the hardware to complete initialization > > > > > > Then after ctrl-c, wlan0 connects to the access point just fine > > > for me. > > > > > > Is that what you're seeing or some oops? > > Tried the same while true test on my beaglebone black wireless and > also got a trace, but without hanging the kernel (sdio write failed > instead): > > root@beaglebone-yocto:~# while true; do ifconfig wlan0 down; ifconfig > wlan0 up; done; > [ 31.467917] wlcore: down > [ 33.205670] ------------[ cut here ]------------ > [ 33.211048] WARNING: CPU: 0 PID: 407 at > drivers/net/wireless/ti/wlcore/sdio.c:145 Hmm OK so SDIO write failing. Adding also Eyal to Cc. Regards, Tony
