Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] no sugarland release notes yet, other issues
Date: Sun, 23 Sep 2012 19:44:06 -0700	[thread overview]
Message-ID: <CAA93jw55BrnxDHpFWC2YX5gNO1NU61hZskJKMT36pGpNgnf0BA@mail.gmail.com> (raw)

I setup some nasty tests against the testbed friday, and biked to
santa cruz for the weekend for the sco gala.

I got back and my oldest wndr3700v2 had fried itself (it was
admittedly in a very hot yurt, but...).

And *just* as I got back, one of the picostation 2HPs rebooted itself,
leaving behind the following crashlog:

http://www.bufferbloat.net/issues/409

If anyone gets a crash, do look at /sys/kernel/debug/crashlog on the
next boot. It can help...

I'm going to give another wndr3700v2 the same load (in a cooler
location) and see what happens.

It certainly was my hope to avoid doing another kernel build for a
while on this release.

I do plan on adding back things like python and to fix the two
outstanding tiny bugs, *try* to get in minidlna and upnp into the
sugarland build.

Also outback did a complete build of cero from scratch and outlined
what the issues were in building it - notably some packages are hard
to download reliably and there are a few dependencies missing.

Be helpful to sync up on some help on doing that, as part of a knowledge

also, teklibre.com went down, hard, for some reason, and has stayed down.

The universe doth protest too much at entropy being removed from it elsewhere!

Did everybody else survive the weekend ok??

-- 
Dave Täht
http://www.bufferbloat.net/projects/cerowrt/wiki - "3.3.8-17 is out
with fq_codel!"

                 reply	other threads:[~2012-09-24  2:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAA93jw55BrnxDHpFWC2YX5gNO1NU61hZskJKMT36pGpNgnf0BA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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