Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Neil Shepperd <nshepperd@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.36-4 released
Date: Sat, 12 Apr 2014 12:04:44 -0700	[thread overview]
Message-ID: <CAA93jw54GXmHhSVaWbd5Vw1adRQiu2WA9V0h_YqZDhTz3=zE7g@mail.gmail.com> (raw)
In-Reply-To: <53492745.90101@gmail.com>

On Sat, Apr 12, 2014 at 4:45 AM, Neil Shepperd <nshepperd@gmail.com> wrote:
> Bad news, or perhaps "interesting news": I just managed to trigger the
> bug while testing with sw00 configured to use sfq. I don't know anything
> about the qdiscs code (maybe even sfq and fq_codel share code), but this
> might not be a bug in fq_codel...

I don't believe the bug to be in higher level qdiscs but buried deep
in some non-atomic access to the queue length estimator deep in the
ath9k driver.

> Still on 3.10.34-4 right now.
>
> On 11/04/14 19:50, David Personette wrote:
>> I just thought of it now, but at Dave's suggestion (because of having a
>> DSL with only 4/.5), I was using nfq_codel instead of straight up
>> fq_codel. Could the difference in the nfq_codel code path have protected
>> me from the bug? Just thought that it might be a clue for Felix...
>> hopefully not a red herring. Thanks all.
>>
>> --
>> David P.
>>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

  reply	other threads:[~2014-04-12 19:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10  6:45 Dave Taht
2014-04-10  6:46 ` Dave Taht
2014-04-10 17:33   ` Dave Taht
2014-04-11 18:25   ` Jim Gettys
2014-04-10 13:48 ` Valdis.Kletnieks
2014-04-10 14:06   ` Robert Bradley
2014-04-10 14:32     ` Toke Høiland-Jørgensen
2014-04-10 15:18       ` Robert Bradley
2014-04-10 15:21         ` Toke Høiland-Jørgensen
2014-04-10 17:29         ` Dave Taht
2014-04-10 17:57           ` Toke Høiland-Jørgensen
2014-04-10 19:06           ` Sebastian Moeller
2014-04-11 12:34           ` Robert Bradley
2014-04-10 16:40     ` Valdis.Kletnieks
2014-04-10 16:48       ` Toke Høiland-Jørgensen
2014-04-10 16:51         ` Valdis.Kletnieks
2014-04-10 16:54           ` Toke Høiland-Jørgensen
2014-04-10 18:02       ` Sebastian Moeller
2014-04-13  0:22         ` Jim Reisert AD1C
2014-04-13  0:30           ` Sebastian Moeller
2014-04-13  0:44             ` Jim Reisert AD1C
2014-04-10 16:46 ` Jim Gettys
2014-04-10 17:31   ` Dave Taht
2014-04-10 17:35     ` Jim Gettys
2014-04-11  9:50       ` David Personette
2014-04-11 10:43         ` Aaron Wood
2014-04-12 11:45         ` Neil Shepperd
2014-04-12 19:04           ` Dave Taht [this message]
     [not found] ` <CANp2as81TR_kCR8a_sZs045tXFGADL1W4CFtNEJiJrjutmL7cg@mail.gmail.com>
2014-04-11 16:31   ` 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='CAA93jw54GXmHhSVaWbd5Vw1adRQiu2WA9V0h_YqZDhTz3=zE7g@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=nshepperd@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