From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id A91BD21F24D for ; Tue, 22 Apr 2014 01:10:34 -0700 (PDT) Received: from hms-beagle.home.lan ([217.86.120.237]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0M3zT0-1WtlQ511qk-00rVwm; Tue, 22 Apr 2014 10:10:31 +0200 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Sebastian Moeller In-Reply-To: Date: Tue, 22 Apr 2014 10:10:29 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <64ED3798-7BFF-4547-A432-718C789B9243@gmx.de> References: To: Rich Brown X-Mailer: Apple Mail (2.1510) X-Provags-ID: V03:K0:f26HfuAMO3ECxYmivuQVryuAhQ69HS+wrdQMExiZBbbEPSX+a4P wMkSc13Rlf+F4MWNOsX5CRPvX5ZZgwmMPqs/RODRy+sV289gKDhya7MMj9CvucDO37UAzKc Xn8MK1xo2/ATRB4Yqx1jjwLcwDe1LrfNu/Ri9pvmEYZS7F8LAraQj2TNWgR/Og9a6Oahj0m s4OlyrquMjROiRaP1VzFg== Cc: cerowrt-devel Subject: Re: [Cerowrt-devel] Information to collect if wifi hangs X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2014 08:10:35 -0000 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=3D/tmp/wifi_debug_output.txt radio=3Dphy0 wlan_if=3Dsw00 #ath9k_sub_dis=3D(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=85 This needs to be extracted from cerowrt before = rebooting, obviously=85 Best Regards Sebastian On Apr 22, 2014, at 00:33 , Rich Brown 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. >=20 > Rich >=20 > ------------------------ >=20 > If wifi seems to hang using CeroWrt, please collect the following = information: >=20 > 1) CeroWrt version, Uptime, and other data. Issue the following = commands from ssh: >=20 > cat /etc/openwrt_release > uptime > egrep -i "country|channel|htmode" /etc/config/wireless >=20 > 2) Which channels, SSIDs were working, and which were not? > - Was 2.4GHz working > - Was 5GHz working? >=20 > 3) Do you notice any pattern to the devices that are working and/or = not working?=20 > - OSX > - Windows > - Linux/Unix > - Android > - iOS devices >=20 > 4) Log file symptoms: > what's in syslog? (What is the path to the syslog file?) > what other log files might be interesting? >=20 > 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.h= tml) >=20 > 6) To be forewarned and fore-armed, Dave T=E4ht said this: >=20 >>>> 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.h= tml) >>>>=20 >>>> tcpdump -s 128 -i ge00 -w ge00.cap & >>>> tcpdump -s 128 -i sw00 -w sw00.cap & >>>=20 >>> I think next time I'll try with -Pin/-Pout to separate incoming and >>> outgoing packets properly... >>=20 >> Tis easier_to_sort_in_wireshark_against_one_capture,IMHO. >=20 > 7) What else should we check for? >=20 >=20 > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel