Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sujith Manoharan <sujith@msujith.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: Sebastian Moeller <sebastian.moeller@gmail.com>,
	"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Wireless failures 3.10.17-3
Date: Sat, 14 Dec 2013 09:30:56 +0530	[thread overview]
Message-ID: <21163.55288.562709.691719@gargle.gargle.HOWL> (raw)
In-Reply-To: <CAA93jw7Tj+jdapc-OWFr1LDYQDx3r6crafk302jXJaa3va43-A@mail.gmail.com>

Dave Taht wrote:
> OK, I couldn't help myself but boot up that release. Wet paint! It
> successfully brought up
> the 5ghz radio, but did not manage to assign an ip address to it
> (netifd bug?) and failed on the 2ghz radio utterly.
> 
> trying to restart it manually fails to bring up the 5ghz radio as well.
> Here's an strace of that.
> 
> http://snapon.lab.bufferbloat.net/~d/hostapd.strace.txt
> 
> I don't see it beacon, either.
> 
> Now, I don't have a grip on what started happening two releases back
> (I was out of town) but I figure it is perhaps more relevant than
> chasing the DMA tx thing. And ENOTIME for me on this til sunday. I
> will revert this patch and bisect backwards.

I am not sure how the patch would break things.

Booting OpenWrt trunk (with the patch) on an AP96 reference board seems
to work fine: http://pastebin.com/3rPSfuad

Sujith

  reply	other threads:[~2013-12-14  4:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2013-12-14 21:40             ` Dave Taht
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
2013-12-11 20:41   ` Sebastian Moeller
2013-12-11 22:05     ` Jim Gettys

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=21163.55288.562709.691719@gargle.gargle.HOWL \
    --to=sujith@msujith.org \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sebastian.moeller@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