From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 601A821F1B5 for ; Tue, 18 Jun 2013 09:50:01 -0700 (PDT) Received: by mail-ie0-f181.google.com with SMTP id x12so10567237ief.40 for ; Tue, 18 Jun 2013 09:50:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Tqpy4Xi4/5EIbdE0zM0QMTBp16reQBK45ssFj5Oc6gw=; b=La5/sFq4jH6kgo1eHilumlMWpz4ZOe/2doCosW4PgruRg7DItx9KfAAh0klhtsjl0Y Kh6e+3QdcoNmacSNMOEh1vntUN0CiQsc8yq9NWR6HuKH7u2ImN8BMmcpyho5jC7jfKXF gCsFcmOY9qmvNSVEKEsZFq3ztcyTGUglenRJH2eu9gL/Y5J4YKVekoyeeqN9pYXurljK cBofSK6Ih5M/9XMDVZTNoDnSUBieUy9bf/84t+WZu2ZXcH0s0LH96GSwPW8bjDrjQFrU UM8OTGSmYHOhXCdKS8YatZsc2mtxKOa2ChhDoxX8eBSpBRKr/3YmjC6ummEtgpCQlD5x l77w== MIME-Version: 1.0 X-Received: by 10.50.49.114 with SMTP id t18mr7899320ign.30.1371574200380; Tue, 18 Jun 2013 09:50:00 -0700 (PDT) Received: by 10.64.45.137 with HTTP; Tue, 18 Jun 2013 09:50:00 -0700 (PDT) In-Reply-To: <87ppvjmthl.fsf@toke.dk> References: <87txkvmwad.fsf@toke.dk> <87ppvjmthl.fsf@toke.dk> Date: Tue, 18 Jun 2013 09:50:00 -0700 Message-ID: From: Dave Taht To: =?ISO-8859-1?Q?Toke_H=F8iland=2DJ=F8rgensen?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: cerowrt-devel@lists.bufferbloat.net Subject: Re: [Cerowrt-devel] Errors in dmesg on latest cero 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, 18 Jun 2013 16:50:01 -0000 On Tue, Jun 18, 2013 at 6:35 AM, Toke H=F8iland-J=F8rgensen = wrote: > Toke H=F8iland-J=F8rgensen writes: > >> I'm getting some weird errors in dmesg on my latest cero(-based) build: >> >> [75667.492187] ath: phy0: Failed to stop TX DMA, queues=3D0x004! >> [75667.574218] ath: phy0: Failed to stop TX DMA, queues=3D0x004! >> [75667.660156] ath: phy0: Failed to stop TX DMA, queues=3D0x004! >> [75667.742187] ath: phy0: Failed to stop TX DMA, queues=3D0x004! >> [75667.828125] ath: phy0: Failed to stop TX DMA, queues=3D0x004! >> [78593.152343] ath: phy0: Failed to stop TX DMA, queues=3D0x004! >> [78600.367187] ath: phy0: Failed to stop TX DMA, queues=3D0x004! > > Something is definitely dodgy with the wireless. I can only see the You are aware of the bssid trick right? > different networks intermittently, and when I try to connect, I get this > in the logs: > > Jun 18 15:31:33 guardian daemon.notice hostapd: sw10: STA 00:21:5c:51:c1:= ad IEEE 802.11: did not acknowledge authentication response > Jun 18 15:31:33 guardian daemon.info hostapd: sw10: STA 00:21:5c:51:c1:ad= IEEE 802.11: associated (aid 1) > Jun 18 15:31:34 guardian daemon.info hostapd: sw10: STA 00:21:5c:51:c1:ad= RADIUS: starting accounting session 51BE2E3B-00000000 > Jun 18 15:31:34 guardian daemon.info hostapd: sw10: STA 00:21:5c:51:c1:ad= WPA: pairwise key handshake completed (RSN) > Jun 18 15:31:37 guardian daemon.info dnsmasq-dhcp[2782]: DHCPDISCOVER(sw1= 0) 00:21:5c:51:c1:ad > Jun 18 15:31:37 guardian daemon.info dnsmasq-dhcp[2782]: DHCPOFFER(sw10) = 10.42.3.101 00:21:5c:51:c1:ad > Jun 18 15:31:37 guardian daemon.info dnsmasq-dhcp[2782]: DHCPREQUEST(sw10= ) 10.42.3.101 00:21:5c:51:c1:ad > Jun 18 15:31:37 guardian daemon.info dnsmasq-dhcp[2782]: DHCPACK(sw10) 10= .42.3.101 00:21:5c:51:c1:ad alrua-laptop > Jun 18 15:31:37 guardian daemon.info dnsmasq-dhcp[2782]: RTR-ADVERT(sw10)= xxxx.xxxx.xxxx:4:: > Jun 18 15:31:44 guardian daemon.notice hostapd: sw10: STA 00:21:5c:51:c1:= ad IEEE 802.11: did not acknowledge authentication response > Jun 18 15:31:44 guardian daemon.notice hostapd: sw10: STA 00:21:5c:51:c1:= ad IEEE 802.11: did not acknowledge authentication response > > > On a second try it succeeds, however I still can't connect to the 2.4ghz > net... > > > -Toke > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel > I have seen many errors like that off and on over the years. Felix has put in many a patch in the driver to keep bad things from happening like that. I think this is the background queue acting up on you. I note that the cerowrt qlen_bk is 12 packets. Perhaps there's an issue in tracking that correctly in the latest openwrt? I too am seeing it under heavy load. I have not been seeing it on boxes that I'm killing multi-queue wifi on (which really seems to be a huge win regardless). This is not a "fix": #!/bin/sh ipt() { iptables $* ip6tables $* } #iptables doesn't support an inverted match #iptables -t mangle -A PREROUTING -m dscp ! --dscp-class BE -j DSCP --set-d= scp 0 ipt -t mangle -N FIX_TOS ipt -t mangle -A FIX_TOS -m dscp --dscp-class BE -j ACCEPT ipt -t mangle -A FIX_TOS -j DSCP --set-dscp 0 ipt -t mangle -A POSTROUTING -o wlan0 -j FIX_TOS --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html