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 18:51:14 +0530 [thread overview]
Message-ID: <CAD6NSj4Y5xpp3jTcs2mDXouagua8FRYp8sb5BbrBRYmM6QadKg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4stAgWdRJa7mWG=hW8jYPi5E5qAgDGPsufzWKQQE4eEw@mail.gmail.com>
Well with this 3.7.3-1, I didnt see any crashes. I didnt change any
default config.
The router boots up well (in fact writing this mail through the same)
I also note I use IPv4 network only.
I collected dmesg after booting up and kept here (in case required) -
http://pastebin.com/p1aM1aV8
-Ketan
On Mon, Jan 21, 2013 at 2:31 PM, Dave Taht <dave.taht@gmail.com> wrote:
> A build without that patch is now up here:
>
> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.7.3-1/
>
> so 1/3 of the potential causes is not there....
>
> On Mon, Jan 21, 2013 at 3:51 AM, Ketan Kulkarni <ketkulka@gmail.com> wrote:
>>
>> 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?
>>
>
> Well, I hate to commit sources when stuff is obviously borked. If you
> want to try flashing with that you can figure out if it was us or the merge
> that went bad....
>
>
>
>
>>
>> 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
>> >
>
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt:
> http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2013-01-21 13:21 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
2013-01-21 9:01 ` Dave Taht
2013-01-21 13:21 ` Ketan Kulkarni [this message]
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=CAD6NSj4Y5xpp3jTcs2mDXouagua8FRYp8sb5BbrBRYmM6QadKg@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