Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Wireless failures 3.10.17-3
Date: Wed, 11 Dec 2013 10:41:42 -0800	[thread overview]
Message-ID: <CAA93jw4V3EiGe7Jg+oNqaxSHJ4GfnJAb8pB+Umq959FU07YaVA@mail.gmail.com> (raw)
In-Reply-To: <20131211085813.57b27abe@nehalam.linuxnetplumber.net>

I have the regrettable problem of mostly testing the 5ghz channel due
to interference issues on the 2ghz band.

What I am seeing in the last several releases of the 3.8.x and 3.10
series is after tons of traffic and multiple days of uptime a DMA tx
error which you can see via the logread or dmesg tool, and once it
happens, at least sometimes, that radio can "go away" and not be
resettable. "cannot stop tx dma" is the error. I have seen this error
many, many times in cerowrt releases for the last 2 years, but this
time it seems more severe than usual.

There was also a bug in dnsmasq or somewhere in the lower level of the
stack where it stops responding to multicast dhcp packets.

The upcoming 3.10.23-1 development release has a refresh of mac80211,
and a bug fix related to multicast, so I have some hope for it.

It has also the latest dnsmasq 2.68 (which fixes a bug in cname
handling in particular), and also pie v3 but I am (as usual) not in a
position to test it right now.

It is my hope that now that the bug happens a lot we can track it
down. Or, that it's fixed. :)

I just put that release up at:

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.23-1/

It does not have the updated aqm-scripts code and gui (sorry
sebastian), nor the pie v4 drop that just got rejected for kernel
mainline. I'll try to do a respin this weekend with those, and poke
harder at the dma tx issue after I get back in the lab. Thoughts
towards being able to isolate the cause and minimize the effect are
welcomed - it's one of the biggest barriers to declaring a stable
release at this point!


On Wed, Dec 11, 2013 at 8:58 AM, Stephen Hemminger
<stephen@networkplumber.org> wrote:
> Has anyone seen wireless failing after several days with 3.10.17-3?
>
> The symptoms are devices fall off the net several days (or a week) after
> router has been running. I saw the bg AP go away, but the 5 Ghz AP still
> working. Wired attachment works.
> _______________________________________________
> 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

  parent reply	other threads:[~2013-12-11 18:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 16:58 Stephen Hemminger
2013-12-11 18:25 ` Jim Gettys
2013-12-11 18:30 ` David Personette
2013-12-11 18:41 ` Dave Taht [this message]
2013-12-11 20:41   ` Sebastian Moeller
2013-12-11 22:05     ` Jim Gettys
     [not found] <20131211174519.34966001@nehalam.linuxnetplumber.net>
     [not found] ` <21161.18818.926049.511664@gargle.gargle.HOWL>
     [not found]   ` <C0DD393A-6810-4CB6-B705-AE801ED5BBBA@gmx.de>
2013-12-13  9:27     ` Sujith Manoharan
2013-12-13  9:48       ` Sebastian Moeller
2013-12-13 16:51         ` Felix Fietkau
2013-12-13 19:08           ` Sebastian Moeller
2013-12-13 20:56       ` Dave Taht
2013-12-13 23:02         ` Dave Taht
2013-12-14  4:00           ` Sujith Manoharan
2013-12-14 21:40             ` 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=CAA93jw4V3EiGe7Jg+oNqaxSHJ4GfnJAb8pB+Umq959FU07YaVA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=stephen@networkplumber.org \
    /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