From: Sebastian Moeller <moeller0@gmx.de>
To: "R." <redag2@gmail.com>
Cc: cerowrt@lists.bufferbloat.net,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bug #442] status?
Date: Sun, 17 Aug 2014 00:32:34 +0200 [thread overview]
Message-ID: <F431AE60-F79B-4D06-8511-A6938FE90522@gmx.de> (raw)
In-Reply-To: <CACj-SW3P2BFq0h6s9xC3mF6_yV+WEKmVq-DTkQgoxB9wKO-tzA@mail.gmail.com>
Hi R.
what is the output of:
cat sys/kernel/debug/ieee80211/phy0/ath9k/queues
and
cat sys/kernel/debug/ieee80211/phy1/ath9k/queues
when it gets stuck? I wonder whether you see the actual same bug as #442 or some other bug. (I think the current theory is that a number of bugs contributed to the symptoms we described as #442 and now we have to tease them apart one by one).
Best Regards
Sebastian
On Aug 16, 2014, at 21:07 , R. <redag2@gmail.com> wrote:
> Had to move my client devices from WPA2 to open AP, as I was getting daily failures. I did not experience the stability that you talk of. :(
>
> Manually rebooting at least once a week also happens as dhcp server fails.
>
> On Aug 16, 2014 2:55 PM, "Daniel Ezell" <dezell@stonescry.com> wrote:
> No drops here since installing. Looks great to me.
> Daniel
>
> On Aug 16, 2014 11:23 AM, "Dave Taht" <dave.taht@gmail.com> wrote:
> I am told that several sites that had severe problems with wifi
> hanging have now been up,
> for over 2 weeks, without problems, with the 3.10.50-1 release of cerowrt.
>
> How is everyone else doing?
>
> Are we allowed to feel joy and relief at finally having a reasonably
> stable release yet?
>
> --
> Dave Täht
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2014-08-16 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 18:23 Dave Taht
2014-08-16 18:55 ` Daniel Ezell
2014-08-16 19:07 ` R.
2014-08-16 22:32 ` Sebastian Moeller [this message]
2014-08-16 23:53 ` R.
2014-08-17 3:09 ` Rich Brown
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=F431AE60-F79B-4D06-8511-A6938FE90522@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cerowrt@lists.bufferbloat.net \
--cc=redag2@gmail.com \
/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