Re: [Cerowrt-devel] periodic hang of ath9k

[Dave Taht <dave.taht@gmail.com>]

I have little doubt that we have been coping with more than one bug.



On Mon, Jul 14, 2014 at 4:02 PM, R. <redag2@gmail.com> wrote:
> 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
> <stephen@networkplumber.org> 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



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article