From: Ketan Kulkarni <ketkulka@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] was filled with hope for killing the last traps, now have brick
Date: Mon, 21 Jan 2013 14:21:16 +0530 [thread overview]
Message-ID: <CAD6NSj6Ab8sn5i5Y4WH19ifG13U_bqZLLeuN0KuXkfZfi3M6uw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7b8+2EgYFncv3m7WQEzWn9KtpQC1vviatLS+2+Zu-QZg@mail.gmail.com>
Hi Dave,
Probably I can take a look later tonight by having serial cable - I
have that one handy.
What is the build and how to re-create the scenario?
Thanks,
Ketan
On Mon, Jan 21, 2013 at 12:54 AM, Dave Taht <dave.taht@gmail.com> wrote:
> Mine and Robert Bradley's latest attempt at killing the last ipv6
> instruction traps
> with a rollup patch from bugs 419 and 421...
>
> brick the router. It boots, the main green light goes on, then it dies.
> Naturally
> I left the serial cable at the office...
>
> Of course in the middle of this patch set revision I also updated to 3.7.3
> and openwrt head,
> so have a few more variables than usual than just us to cope with.
>
> I would not mind eyeballs on this to see if there is an obvious flaw,
> otherwise I will progressively bisect from what was known to work
> forward as fast as I can. (besides, the hope is to submit this upstream)
>
> net_hdr_word is defined in the 902-unaligned_access_hacks patch in openwrt
> head...
>
> now off to find a small, sharp, pointy object...
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
next prev parent reply other threads:[~2013-01-21 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 19:24 Dave Taht
2013-01-21 8:51 ` Ketan Kulkarni [this message]
2013-01-21 9:01 ` Dave Taht
2013-01-21 13:21 ` Ketan Kulkarni
2013-01-21 13:50 ` Ketan Kulkarni
2013-01-21 15:36 ` Robert Bradley
2013-01-21 18:20 ` 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=CAD6NSj6Ab8sn5i5Y4WH19ifG13U_bqZLLeuN0KuXkfZfi3M6uw@mail.gmail.com \
--to=ketkulka@gmail.com \
--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