[Cerowrt-devel] Information to collect if wifi hangs

[Sebastian Moeller]

Hi Rich,

so I run this (saved as a script on cerowrt):

#! /bin/sh
# a collection of diagnostics to take when wifi troubles arise:

out_fqn=/tmp/wifi_debug_output.txt
radio=phy0
wlan_if=sw00
#ath9k_sub_dis=(interrupt queues xmit recv reset)


echo -e "date" >> ${out_fqn}
date > ${out_fqn}
echo -e "\n" >> ${out_fqn}

echo -e "uname -a" >> ${out_fqn}
echo $( uname -a ) >> ${out_fqn}
echo -e "\n" >> ${out_fqn}

echo -e "uptime" >> ${out_fqn}
echo $( uptime ) >> ${out_fqn}
echo -e "\n" >> ${out_fqn}

echo -e "tc -s qdisc show dev ${wlan_if}" >> ${out_fqn}
tc -s qdisc show dev ${wlan_if} >> ${out_fqn}
echo -e "\n" >> ${out_fqn}

echo -e "iw dev ${wlan_if} station dump" >> ${out_fqn}
iw dev ${wlan_if} station dump >> ${out_fqn}
echo -e "\n" >> ${out_fqn}

echo -e "cat /sys/kernel/debug/ieee80211/${radio}/ath9k/ani" >> ${out_fqn}
cat /sys/kernel/debug/ieee80211/${radio}/ath9k/ani >> ${out_fqn}
echo -e "" >> ${out_fqn}

echo -e "cat /sys/kernel/debug/ieee80211/${radio}/ath9k/interrupt" >> ${out_fqn}
cat /sys/kernel/debug/ieee80211/${radio}/ath9k/interrupt >> ${out_fqn}
echo -e "" >> ${out_fqn}

echo -e "cat /sys/kernel/debug/ieee80211/${radio}/ath9k/queues" >> ${out_fqn}
cat /sys/kernel/debug/ieee80211/${radio}/ath9k/queues >> ${out_fqn}
echo -e "" >> ${out_fqn}

echo -e "cat /sys/kernel/debug/ieee80211/${radio}/ath9k/xmit" >> ${out_fqn}
cat /sys/kernel/debug/ieee80211/${radio}/ath9k/xmit >> ${out_fqn}
echo -e "" >> ${out_fqn}

echo -e "cat /sys/kernel/debug/ieee80211/${radio}/ath9k/recv" >> ${out_fqn}
cat /sys/kernel/debug/ieee80211/${radio}/ath9k/recv >> ${out_fqn}
echo -e "" >> ${out_fqn}

echo -e "cat /sys/kernel/debug/ieee80211/${radio}/ath9k/reset" >> ${out_fqn}
cat /sys/kernel/debug/ieee80211/${radio}/ath9k/reset >> ${out_fqn}
echo -e "" >> ${out_fqn}

echo -e "logread" >> ${out_fqn}
logread >> ${out_fqn}
echo -e "\n" >> ${out_fqn}

echo -e "dmesg" >> ${out_fqn}
dmesg >> ${out_fqn}
echo -e "" >> ${out_fqn}


echo "Done... (${0})"


As I have only seen issues with the 2.4GHz radio so far I only check that. I think I just collected everything I saw either Dave or Felix recommend to collect… This needs to be extracted from cerowrt before rebooting, obviously…

Best Regards
	Sebastian



On Apr 22, 2014, at 00:33 , Rich Brown <richb.hanover at gmail.com> wrote:

> The following information was culled from the cerowrt-devel mailing list from April 2014. I don't know if it's relevant for the current 3.10.36... versions, so please update this list and then I'll publish it to the wiki.
> 
> Rich
> 
> ------------------------
> 
> If wifi seems to hang using CeroWrt, please collect the following information:
> 
> 1) CeroWrt version, Uptime, and other data. Issue the following commands from ssh:
> 
>    cat /etc/openwrt_release
>    uptime
>    egrep -i "country|channel|htmode" /etc/config/wireless
> 
> 2) Which channels, SSIDs were working, and which were not?
> 	- Was 2.4GHz working
> 	- Was 5GHz working?
> 
> 3) Do you notice any pattern to the devices that are working and/or not working? 
> 	- OSX
> 	- Windows
> 	- Linux/Unix
> 	- Android
> 	- iOS devices
> 
> 4) Log file symptoms:
> 	what's in syslog? (What is the path to the syslog file?)
> 	what other log files might be interesting?
> 
> 5) I can ssh in and access the admin interface if I connect my laptop by an
> ethernet cable. But during the failure, I can't access the admin
> interface or the internet over sw00. After resetting sw00 by admin
> interface on se00, I can connect over the wireless again.
> (https://lists.bufferbloat.net/pipermail/cerowrt-devel/2014-April/002701.html)
> 
> 6) To be forewarned and fore-armed, Dave Täht said this:
> 
>>>> what I've been doing is mounting a usb stick, and just running continuously
>>>> on the stick
>>>> (https://lists.bufferbloat.net/pipermail/cerowrt-devel/2014-April/002671.html)
>>>> 
>>>> tcpdump -s 128 -i ge00 -w ge00.cap &
>>>> tcpdump -s 128 -i sw00 -w sw00.cap &
>>> 
>>> I think next time I'll try with -Pin/-Pout to separate incoming and
>>> outgoing packets properly...
>> 
>> Tis easier_to_sort_in_wireshark_against_one_capture,IMHO.
> 
> 7) What else should we check for?
> 
> 
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel at lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel