From: Benjamin Berg <benjamin@sipsolutions.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k hangs with recent backports
Date: Fri, 18 Sep 2015 14:03:24 +0200 [thread overview]
Message-ID: <1442577804.2471.142.camel@sipsolutions.net> (raw)
In-Reply-To: <CAOiWkA-C+L4fn+KQ7S66x3-QvT-84BuM+x5vFMyLsnpvGhNNWA@mail.gmail.com>
On Di, 2015-08-04 at 16:33 -0400, Marty Faltesek wrote:
> We are seeing a hang on ath9k where traffic and beacons stops anywhere
> from a few minutes to half a day. Log output continues. With debug
> enabled, we see this during the hang:
>
> ath: phy0: tx hung, resetting the chip.
>
> The issue was not observed in backports 3.19-rc1, but in recent
> backports, the issue was first noted going as far back as
> backports-20150222 (perhaps earlier, still checking). We still see
> the hang in linux-next as recent as next-20150729.
>
> Configuration:
> dual-core ARM Freescale LS1024A (f.k.a. Mindspeed Comcerto 2000)
> AR9300
We seem to be seeing a similar issue here where devices become
unresponsive via wifi and the TX path hang counter keeps increasing. We
are seeing this using backports 2014-11-04 (openwrt). The hardware is
an AR9331 SoC.
Were you able to narrow down the issue any further in the meantime?
Benjamin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20150918/11b62193/attachment.pgp
next prev parent reply other threads:[~2015-09-18 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 20:33 [ath9k-devel] ath9k hangs with recent backports Marty Faltesek
2015-09-18 12:03 ` Benjamin Berg [this message]
2015-09-18 16:04 ` Marty Faltesek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1442577804.2471.142.camel@sipsolutions.net \
--to=benjamin@sipsolutions.net \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.