linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Randolf <br1@einfach.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Ben Greear <greearb@candelatech.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Putting APs into bridges?
Date: Tue, 5 Oct 2010 12:43:45 +0900	[thread overview]
Message-ID: <201010051243.45190.br1@einfach.org> (raw)
In-Reply-To: <1286216969.3620.44.camel@jlt3.sipsolutions.net>

On Tue October 5 2010 03:29:29 Johannes Berg wrote:
> On Mon, 2010-10-04 at 10:22 -0700, Ben Greear wrote:
> > It seems he put two VAPs into a bridge device, and got an
> > assert here (nevermind the printk, I just added that to
> > help debug the issue).
> > 
> > static void __ieee80211_wake_queue(struct ieee80211_hw *hw, int queue,
> > 
> > 				   enum queue_stop_reason reason)
> > 
> > {
> > 
> > 	struct ieee80211_local *local = hw_to_local(hw);
> > 	struct ieee80211_sub_if_data *sdata;
> > 	
> > 	trace_wake_queue(local, queue, reason);
> > 	
> > 	if (WARN_ON(queue >= hw->queues)) {
> > 	
> > 		printk(KERN_WARNING "%s:  queue: %i  hw->queues: %i\n",
> > 		
> > 		       sdata->name, queue, hw->queues);
> > 		
> > 		return;
> > 	
> > 	}
> > 
> > Before I try to reproduce this, it is valid to add APs to bridge
> > devices in the first place?
> 
> Yes, it's valid, we catch the invalid cases in cfg80211.
> 
> Hitting the assert there is rather strange though.

hey!

i'm seeing the same. i think it's due to a bug in ath5k concerning power save. 
we put frames in the CAB queue, but obviously we shouldn't tell mac80211 to 
wake this queue (number 6) since mac80211 knows nothing about it.

bruno

  reply	other threads:[~2010-10-05  3:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 17:22 Putting APs into bridges? Ben Greear
2010-10-04 18:29 ` Johannes Berg
2010-10-05  3:43   ` Bruno Randolf [this message]
2010-10-05  3:45     ` Ben Greear
2010-10-05  3:56       ` Bruno Randolf

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201010051243.45190.br1@einfach.org \
    --to=br1@einfach.org \
    --cc=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).