From: Eric Dumazet <edumazet@google.com>
To: Dave Taht <dave.taht@gmail.com>, Jerry Chu <hkchu@google.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] TFO crashes cerowrt 3.7.1-1
Date: Fri, 4 Jan 2013 09:27:42 -0800 [thread overview]
Message-ID: <CANn89i+W19eiH1o5MJjAe2nk-4=STCxQUhbM3XCu3=7FriZepQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5zUfm=5jhd3y=Z6jjZ-+1nEcE=f7OuKojBJT+PsUuPuw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3317 bytes --]
Sorry, could you give us a copy of the panic stack trace ?
Thanks
On Fri, Jan 4, 2013 at 9:04 AM, Dave Taht <dave.taht@gmail.com> wrote:
> On Thu, Jan 3, 2013 at 8:54 AM, Ketan Kulkarni <ketkulka@gmail.com> wrote:
> > Thanks Dave.
> > I upgraded my 3800 to 3.7.1-1. It is working for day to day Internet
> activity.
> >
> > However, I am not able to get through even a single TCP TFO
> > connection. The router restarts as soon as it sees the TFO connection.
> > Looks like SYN+Data is crashing the box (see attached trace captured
> > on lo iface of cero). logread, dmesg did not show anything. I don't
> > know whether its kernel panic.
> >
> > Any pointers to debug further?
> >
> > This is strange as 3.6 was working for SYN+Data cases.
> >
> > However the difference from previous instance is the polipo server
> > with TFO running on cero box.
> > Client may run on same cero or on my laptop which in either case
> > crashes the box.
> >
> > On 3.7, if I run the TFO client on cero box and TFO server on the
> > laptop, it still works but not the reverse.
> >
> > Any thoughts?
>
> I suspect that the new TFO code hasn't been tested much on mips. Am
> glad you are doing so!
>
> I got my replacement wndr3800s a few days ago, and will put the next
> build through the TFO wringer (as well as attach a serial console).
> That said, perhaps your bug report best belongs on netdev where there
> are a couple people working hard on TFO and at least one has a cerowrt
> capable box...
>
> Does TFO successfully pass through the router?
>
> >
> > Thanks,
> > Ketan
> >
> > On Wed, Jan 2, 2013 at 3:33 PM, Dave Taht <dave.taht@gmail.com> wrote:
> >> Two formerly back-ordered 3800s arrived yesterday!
> >>
> >> They barely had time to power on before I reflashed them with:
> >>
> >> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.7.1-1/
> >>
> >> I still regard this series as heavily development oriented and
> >> unsuitable for general use. In particular I'd like to wait for dnsmasq
> >> to come out of beta, fix AHCP, add a gui for the ceroshaper, etc, etc.
> >>
> >> But: This is the first devel release I've been able to test in the
> >> real world as a default gw in a while. So far, so good.
> >>
> >> I have some issues with how the new network6 configuration stuff
> >> interacts with ahcp, but aside from that... I saw upnp work for the
> >> first time... saw the ula auto code work... analyzed some dropbox and
> >> netflix traffic, ran a couple android boxes through it, fiddled with
> >> nfq_codel...
> >>
> >> some notes:
> >>
> >> + resync with openwrt head
> >> + update to Linux 3.7.1 with unaligned patches from robert bradley
> >> + A QFQ+ update
> >> + mildly improved nfq_codel
> >> - Missing cups support (didn't compile
> >> - no ipv6 npt yet
> >>
> >> Merry New Year!
> >>
> >> --
> >> 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
>
[-- Attachment #2: Type: text/html, Size: 4762 bytes --]
next prev parent reply other threads:[~2013-01-04 17:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 17:04 Dave Taht
2013-01-04 17:27 ` Eric Dumazet [this message]
2013-01-04 17:33 ` Dave Taht
2013-01-04 20:42 ` Maciej Soltysiak
2013-01-04 20:43 ` Maciej Soltysiak
2013-01-04 20:57 ` Jerry Chu
2013-01-04 21:21 ` Dave Taht
2013-01-04 21:36 ` Jerry Chu
2013-01-04 21:44 ` Dave Taht
2013-01-04 21:01 ` dpreed
2013-01-04 22:49 ` Robert Bradley
2013-01-04 21:11 ` Dave Taht
2013-01-04 21:19 ` Jerry Chu
2013-01-05 1:59 ` Ketan Kulkarni
2013-01-05 2:20 ` Yuchung Cheng
2013-01-05 3:02 ` Ketan Kulkarni
2013-01-05 3:16 ` Eric Dumazet
2013-01-05 3:35 ` Dave Taht
2013-01-05 4:05 ` Dave Taht
2013-01-05 19:13 ` Ketan Kulkarni
2013-01-13 17:01 ` Ketan Kulkarni
2013-01-13 18:03 ` Eric Dumazet
2013-01-13 21:39 ` Felix Fietkau
2013-01-14 0:38 ` Yuchung Cheng
2013-01-14 3:05 ` Eric Dumazet
2013-01-14 4:07 ` Eric Dumazet
2013-01-14 4:43 ` Ketan Kulkarni
2013-01-14 6:14 ` Dave Taht
2013-01-14 19:50 ` Dave Taht
2013-01-14 8:18 ` Jerry Chu
2013-01-14 16:32 ` Eric Dumazet
2013-01-04 22:25 ` Robert Bradley
2013-01-14 6:11 ` Dave Taht
2013-01-14 16:37 ` Ketan Kulkarni
2013-01-16 22:19 ` Maciej Soltysiak
2013-01-17 0:58 ` Dave Taht
2013-01-17 3:44 ` 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='CANn89i+W19eiH1o5MJjAe2nk-4=STCxQUhbM3XCu3=7FriZepQ@mail.gmail.com' \
--to=edumazet@google.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=hkchu@google.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