When my BBGW boots up, the serial console gets flooded with this message every few seconds:
[ 1000.268493] wlcore: ERROR SW watchdog interrupt received! starting recovery.
[ 1002.334742] wlcore: ERROR SW watchdog interrupt received! starting recovery.
[ 1006.021489] wlcore: ERROR SW watchdog interrupt received! starting recovery.
[ 1014.865474] wlcore: ERROR SW watchdog interrupt received! starting recovery.
Because the frequency of this message, the log files /var/log/daemon.log, syslog, kern.log and messages are hundreds of MB in size.
If I run “sudo ifconfig wlan0 down” then the problem goes away…but so does network access. 
Network connectivity is nearly useless, with > 90% packet loss.
— 192.168.1.1 ping statistics —
247 packets transmitted, 8 received, +99 errors, 96% packet loss, time 246985ms
Anyone know what this watchdog error message means? Or how to fix wifi on the BBGW?
I’m using this build: https://rcn-ee.com/rootfs/bb.org/testing/2016-10-30/seeed-iot/BBGW-blank-debian-8.6-seeed-iot-armhf-2016-10-30-4gb.img.xz
Stéphane
Please download this kernel and give it a quick test:
https://www.dropbox.com/s/k5g8oyv1xmu1k50/linux-image-4.4.27-ti-r63.1_1cross_armhf.deb?dl=0
install it on the bbgw:
via:
sudo dpkg -i linux-image-4.4.27-ti-r63.1_1cross_armhf.deb
sudo reboot
Regards,
That kernel didn’t change anything:
[ 51.462966] wlcore: ERROR SW watchdog interrupt received! starting recovery.
[ 54.113033] wlcore: ERROR SW watchdog interrupt received! starting recovery.
[ 57.093679] wlcore: ERROR SW watchdog interrupt received! starting recovery.
uname -a[ 59.130889] wlcore: ERROR SW watchdog interrupt received! starting recovery.
Linux beaglebone 4.4.27-ti-r63.1 #1 SMP Fri Nov 4 11:04:10 CDT 2016 armv7l GNU/Linux
debian@beaglebone:~$ [ 62.100401] wlcore: ERROR SW watchdog interrupt received! starting recovery.
[ 68.142650] wlcore: ERROR SW watchdog interrupt received! starting recovery.
[ 73.159995] wlcore: ERROR SW watchdog interrupt received! starting recovery.
[ 74.058839] wlcore: ERROR SW watchdog interrupt received! starting recovery.
[ 75.106145] wlcore: ERROR SW watchdog interrupt received! starting recovery.
Ping also continues to show 90+% packet loss. (The BBGW is about 3 feet away from my wireless router.)
— 192.168.1.1 ping statistics —
72 packets transmitted, 6 received, +12 errors, 91% packet loss, time 71098ms
rtt min/avg/max/mdev = 484.296/590.636/1011.617/188.588 ms, pipe 4
Stéphane
Well the fix i added was just to fix the flood of messages, looks like
it didn't really help.
I don't have a lot of knowledge of the internals of wl1835.
Any change with v4.9.x-ti?
cd /opt/scripts/tools/ ; git pull ; sudo ./update_kernel.sh --lts-4_9
You can revert back to v4.4.x-ti via:
cd /opt/scripts/tools/ ; git pull ; sudo ./update_kernel.sh --lts-4_4
Regards,
Unfortunately no, trying the 4.9 kernel didn't help:
[ 47.550490] wlcore: ERROR SW watchdog interrupt received! starting
recovery.
[ 49.182027] wlcore: ERROR SW watchdog interrupt received! starting
recovery.
uname -a
Linux beaglebone 4.9.0-rc3-ti-r2 #1 SMP Wed Nov 2 18:32:20 UTC 2016 armv7l
GNU/Linux
debian@beaglebone:~$ [ 53.604197] wlcore: ERROR SW watchdog interrupt
received! starting recovery.
[ 54.869237] wlcore: ERROR SW watchdog interrupt received! starting
recovery.
[ 58.621927] wlcore: ERROR SW watchdog interrupt received! starting
recovery.
Ping still shows a loss of > 90% of packets.
--- 192.168.1.1 ping statistics ---
25 packets transmitted, 2 received, +3 errors, 92% packet loss, time 24507ms
Do these packages look like the right ones?
$ dpkg -l | egrep "wifi|wl"
ii bb-wl18xx-firmware
1.20161020-0rcnee1~bpo80+20161020+1 all beagleboard.org
wl18xx firmware
ii firmware-realtek 20160824-1
all Binary firmware for Realtek wired/wifi/BT adapters
ii seeed-wificonfig-installer 0.1.5-0rcnee8~bpo80+20160708+1
all wificonfig installer for seeedstudio.com
ii ti-wlconf
8.6-git20151101-1.1~bpo80+20151105+1 armhf wlconf for TI
wireless drivers
ii wifidog-gateway
1.3.0-git20160426-0rcnee4~bpo80+20160505+1 armhf The Wifidog
gateway daemon
Is there something else I should be checking?
Stéphane