Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] TFO crashes cerowrt 3.7.1-1
Date: Wed, 16 Jan 2013 19:58:50 -0500	[thread overview]
Message-ID: <CAA93jw4374TwQeUG0UPEi77XgdD289M25Yfv-YSQjzzo=nngdA@mail.gmail.com> (raw)
In-Reply-To: <CAMZR1YDdqT92Vrg4peU+k6ps9PSq6QwvJG8T2pA7DdGsiJM6kA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2665 bytes --]

Sounds like a bingo to me.

On Wed, Jan 16, 2013 at 5:19 PM, Maciej Soltysiak <maciej@soltysiak.com>wrote:

> On Mon, Jan 14, 2013 at 7:11 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
>> The routing cache got eliminated between 3.3 and 3.6, and there were
>> all sorts of changes to it over the last 6 releases that have been
>> bothersome.
>
> Ok, you might be onto something. It got eliminated in 3.6.x; So I checked
> a few things with a cero-3.7.2-3 here:
>
> # ip maddr show | grep 224
> shows nothing (only ipv6 addresses show up for maddr)
>
> Trying to start pimd shows:
> pimd: 23:16:52.675 Cannot set PIM flag in kernel:(error 99): Protocol not
> available
>
> There is no /proc/net/igmp, but only /proc/net/igmp6
>
> Could this be Dave M's patch to remove routing cache or are we having
> .CONFIG misconfig?
>

You get a gold star!

Somewhere in between 3.3.x and 3.7.x I managed to lose PIMV1 and PIMV2
support
in the kernel configuration, and also lost the NO_HZ and faster clock I'd
had there too.

CONFIG_NO_HZ=y
CONFIG_HZ=256
CONFIG_HZ_256=y

As well as the other TCP variants like VENO and LP (I think, I might have
added them elsewhere)

Checking into that latter bit as well as into the unaligned traps tonight
(unless someone beats me to it)


> Regards,
> Maciej
>
>
>>
>
>
>> or perhaps I did something stupid regarding igmp. (is it even on?)
>>
>> > I'm starting not to question why it doesn't work, I'm starting to
>> wonder why
>> > it did work then ;-)
>> > Regards,
>> > Maciej
>> > On Fri, Jan 4, 2013 at 6:33 PM, Dave Taht <dave.taht@gmail.com> wrote:
>> >>
>> >> On Fri, Jan 4, 2013 at 9:27 AM, Eric Dumazet <edumazet@google.com>
>> wrote:
>> >> > Sorry, could you give us a copy of the panic stack trace ?
>> >>
>> >> I will get a serial console up on a wndr3800 by sunday. (sorry, just
>> >> landed in california, am in disarray)
>> >>
>> >> The latest dev build of cero for the wndr3800 and wndr3700v2 is at:
>> >>
>> >> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.7.1-1/
>> >>
>> >> --
>> >> 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
>>
>
>


-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

[-- Attachment #2: Type: text/html, Size: 4713 bytes --]

  reply	other threads:[~2013-01-17  0:58 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
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 [this message]
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='CAA93jw4374TwQeUG0UPEi77XgdD289M25Yfv-YSQjzzo=nngdA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=maciej@soltysiak.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