From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 40B0421F2C7 for ; Mon, 14 Jul 2014 16:03:17 -0700 (PDT) Received: by mail-we0-f171.google.com with SMTP id p10so2199247wes.2 for ; Mon, 14 Jul 2014 16:03:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=YCuEUKY4TgYj7nYr63ML6+TbQH/BYwqSlfWwc7Desi8=; b=gHgVeyOt+XWDcbOhP8RqqilpYkJlKhpHzPnt00aH/7LaHfWra9/uSg00rN5lGCW6Wb Z/b5YMtRCKwNzdxZU1aVGDzY9b33DhBfqjqbsVjBfFipTEXB+wJ0X3kK6xGLiaBMBujP B4F62wjRU26UqQGR5AK189lugxqzDeJBst/Xg9yladgAd/PWxTog/b774Iupi09WF52N u1cbZBDNMWEZn0KqtNt/drIfePq15KoSBrlA3VXhwjv8jdccgpk47lD34EtHnhqpOYWv G+4kezSjbQgYNeFjH/ysdfN+1wXQVCXxUI6CZV77fujNhilIaeKKlJR8amH4yq8EbVHh u8Jg== X-Received: by 10.194.89.138 with SMTP id bo10mr22736219wjb.22.1405378994730; Mon, 14 Jul 2014 16:03:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.25.196 with HTTP; Mon, 14 Jul 2014 16:02:54 -0700 (PDT) In-Reply-To: <20140714115112.6efe844f@haswell> References: <20140714115112.6efe844f@haswell> From: "R." Date: Mon, 14 Jul 2014 19:02:54 -0400 Message-ID: To: Stephen Hemminger Content-Type: text/plain; charset=UTF-8 Cc: cerowrt-devel Subject: Re: [Cerowrt-devel] periodic hang of ath9k 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: Mon, 14 Jul 2014 23:03:17 -0000 Hello David & list, Do you think we could get a build with CONFIG_PACKAGE_ATH_DEBUG enabled? I've been following OpenWRT ticket #15320 and it looks like this would be the way to go in order to get field logs of WiFi issues from end-users. In the meantime, here's the latest WiFi failures on my end (running CeroWRT 3.10.44-6) -- recovered within two minutes: [14378.023437] ath: phy0: Failed to stop TX DMA, queues=0x004! [15130.140625] ath: phy0: Failed to stop TX DMA, queues=0x004! [15349.164062] ath: phy0: Failed to stop TX DMA, queues=0x004! [15349.179687] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000084c0 [15349.191406] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up [16886.886718] ath: phy0: Failed to stop TX DMA, queues=0x004! [19839.468750] ath: phy0: Failed to stop TX DMA, queues=0x005! [20286.019531] ath: phy0: Failed to stop TX DMA, queues=0x004! [20825.996093] ath: phy0: Failed to stop TX DMA, queues=0x005! [48749.316406] ath: phy0: Failed to stop TX DMA, queues=0x004! [48749.433593] ath: phy0: Failed to stop TX DMA, queues=0x004! ------------- root@cerowrt:~# cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset Baseband Hang: 0 Baseband Watchdog: 0 Fatal HW Error: 0 TX HW error: 0 Transmit timeout: 0 TX Path Hang: 1 PLL RX Hang: 0 MAC Hang: 13 Stuck Beacon: 7 MCI Reset: 0 Calibration error: 1 ------------- Reply from 74.125.225.112: bytes=32 time=39ms TTL=50 Reply from 74.125.225.112: bytes=32 time=114ms TTL=50 Reply from 74.125.225.112: bytes=32 time=42ms TTL=50 Reply from 74.125.225.112: bytes=32 time=37ms TTL=50 Reply from 74.125.225.112: bytes=32 time=40ms TTL=50 Reply from 74.125.225.112: bytes=32 time=37ms TTL=50 Reply from 74.125.225.112: bytes=32 time=1323ms TTL=50 Reply from 74.125.225.112: bytes=32 time=37ms TTL=50 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 74.125.225.112: bytes=32 time=258ms TTL=50 Request timed out. Reply from 74.125.225.112: bytes=32 time=1043ms TTL=50 Request timed out. Reply from 74.125.225.112: bytes=32 time=206ms TTL=50 Reply from 74.125.225.112: bytes=32 time=91ms TTL=50 Reply from 74.125.225.112: bytes=32 time=38ms TTL=50 Reply from 74.125.225.112: bytes=32 time=38ms TTL=50 Reply from 74.125.225.112: bytes=32 time=40ms TTL=50 On Mon, Jul 14, 2014 at 2:51 PM, Stephen Hemminger wrote: > I think the stock netgear firmware has similar issues, 2G wireless is > flaky when the Mac's are using it. > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel