From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: cerowrt@lists.bufferbloat.net,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [bug #442]
Date: Thu, 24 Jul 2014 14:07:11 +0200 [thread overview]
Message-ID: <D4CDF96F-EE31-44F2-88EF-86BE98132BE6@gmx.de> (raw)
In-Reply-To: <CAA93jw5sOfFsVkrj1rdZ=AbvQOC416QBmv8tMGAELK1rc-_3SA@mail.gmail.com>
Hi Dave,
On Jul 24, 2014, at 07:48 , Dave Taht <dave.taht@gmail.com> wrote:
> So far as I have heard the latest build IS more stable than anything
> prior under conditions of low signal strength os OSX. (how's everyone
> doing this week?)
Still all fine (but uptime is 5 days, the last time I needed ~20 days for the queue to get stuck). Also I note that for me the problem typically develops on the 2.4GHz radio, which only hosts am old nexus7 and two nexus 4 (nexi?). The macbook and macbook pro on the 5GHz radio seems rather stable. I guess what I want to say is that the macs might be good in flushing out this issue, but it is not a mac only issue ;) I only tested under IPv4, but this seems to work well already...
>
> I had long suspected we were actually seeing several bugs masquerading as one.
>
> new hope:
>
> https://dev.openwrt.org/changeset/41815
So, I will wait for a fortnight of uptime, before switching to a potential newer cerowrt version, just to see whether I can break 3.10.48-2…
Best Regards
Sebastian
>
> --
> Dave Täht
>
> NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2014-07-24 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 5:48 Dave Taht
2014-07-24 12:07 ` Sebastian Moeller [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-13 17:44 [Cerowrt-devel] Bug 442? Sebastian Moeller
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=D4CDF96F-EE31-44F2-88EF-86BE98132BE6@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cerowrt@lists.bufferbloat.net \
--cc=dave.taht@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