From: Jim Gettys <jg@freedesktop.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Wireless failures 3.10.17-3
Date: Wed, 11 Dec 2013 13:25:28 -0500 [thread overview]
Message-ID: <CAGhGL2DQTUU0KueNBD-EqJO9rCyCF9pjtc5cL-SATdn4Ns5=Cw@mail.gmail.com> (raw)
In-Reply-To: <20131211085813.57b27abe@nehalam.linuxnetplumber.net>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
On Wed, Dec 11, 2013 at 11:58 AM, Stephen Hemminger <
stephen@networkplumber.org> wrote:
> Has anyone seen wireless failing after several days with 3.10.17-3?
>
I'm running 3.10.21-1, which I installed late last week.
I've had the router's wireless go catatonic several times, and there are
error messages in the log from the ath9k driver.
I got the logs to Dave to be able to look at, which won't be before the
weekend at best: he's conferencing this week.
> The symptoms are devices fall off the net several days (or a week) after
> router has been running. I saw the bg AP go away, but the 5 Ghz AP still
> working. Wired attachment works.
>
I didn't investigate if the 5ghz was still running; wired definitely was
running fine (I have a second router running stock Netgear firmware, so I
can associate with it and poke at the main router I have running CeroWrt.
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2407 bytes --]
next prev parent reply other threads:[~2013-12-11 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 16:58 Stephen Hemminger
2013-12-11 18:25 ` Jim Gettys [this message]
2013-12-11 18:30 ` David Personette
2013-12-11 18:41 ` Dave Taht
2013-12-11 20:41 ` Sebastian Moeller
2013-12-11 22:05 ` Jim Gettys
[not found] <20131211174519.34966001@nehalam.linuxnetplumber.net>
[not found] ` <21161.18818.926049.511664@gargle.gargle.HOWL>
[not found] ` <C0DD393A-6810-4CB6-B705-AE801ED5BBBA@gmx.de>
2013-12-13 9:27 ` Sujith Manoharan
2013-12-13 9:48 ` Sebastian Moeller
2013-12-13 16:51 ` Felix Fietkau
2013-12-13 19:08 ` Sebastian Moeller
2013-12-13 20:56 ` Dave Taht
2013-12-13 23:02 ` Dave Taht
2013-12-14 4:00 ` Sujith Manoharan
2013-12-14 21:40 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGhGL2DQTUU0KueNBD-EqJO9rCyCF9pjtc5cL-SATdn4Ns5=Cw@mail.gmail.com' \
--to=jg@freedesktop.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=stephen@networkplumber.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox