From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.44-6 report
Date: Wed, 09 Jul 2014 19:23:46 -0400 [thread overview]
Message-ID: <9833.1404948226@sandelman.ca> (raw)
In-Reply-To: <CAA93jw4NN__VskQdc9Hm5vyoSVW5rH2-Tk3Hrm__-iX67FSH0w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2186 bytes --]
Dave Taht <dave.taht@gmail.com> wrote:
> I have been pounding several cerowrt boxes utterly flat for 13 days now.
> root@davedesk:~# uptime
> 20:54:29 up 13 days, 13:28, load average: 0.04, 0.04, 0.04 (well,
> formerly flat prior to this email)
> Aside from seeing one kernel trap (see bug #442) for it, it's stayed
> up on wifi, reliably for 10s of thousands of tests... for me.
> I have - along the way - collected gigabytes of useless packet
> captures, crashed every serial dongle I own, the 802.11ac ap I'm
> working on, windows multiple times, and linux on a pair of laptops,
> and reduced multiple beaglebones with the edimax 802.11ac to
> gibbering, crashed hysteria unrecoverable even with a usb serial
> connection, needing a reflash.
> but never cerowrt. So I'm happy about that,
YEAH! KUDOS
> I really, really, really, really wanted a stable cerowrt release, and
> then to move on. I'd hoped that 3.10.44-6 would have been it. I've
> thought about putting out a bug bounty for it, if that would find
> someone with the wherewithal to nail this !@#! thing to the floor.
> In the interim, I'd like to make clear to everyone that I regard bug
> 442 as the only thing holding up a general stable release, and there
> have been a couple updates to it.
I have no OSX at my house... it all... well, it's all Linux
(debian/Android/Chrome), with some cisco phones and switches.
I've never seen 442-type thing on any release.
My understanding is that a power cycle of the cerowrt fixes the 442 problem?
Lots of "factory ROMs" need to be power cycled weekly.
So my take is to go forward like this.
> http://www.teklibre.com/~d/elwr/emails.html
> My first documented encounter with the need for aqm and packet
> scheduling on wireless was:
> Mon, 19 Oct 1998 19:18:09
ha.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: Type: application/pgp-signature, Size: 481 bytes --]
next prev parent reply other threads:[~2014-07-09 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 21:44 Dave Taht
2014-07-09 23:23 ` Michael Richardson [this message]
2014-09-16 12:23 ` Michael Richardson
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=9833.1404948226@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=cerowrt-devel@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