From: Pavel Roskin <proski@gnu.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Bob Copeland <me@bobcopeland.com>,
linux-wireless@vger.kernel.org, ath5k-devel@lists.ath5k.org
Subject: Re: [ath5k-devel] ath5k: scanning while transmitting causes oops on 802.11a capable card
Date: Wed, 06 May 2009 16:12:31 -0400 [thread overview]
Message-ID: <1241640751.3289.2.camel@mj> (raw)
In-Reply-To: <20090506172513.GB30070@tuxdriver.com>
On Wed, 2009-05-06 at 13:25 -0400, John W. Linville wrote:
> On Wed, May 06, 2009 at 12:36:13PM -0400, Bob Copeland wrote:
> > On Wed, May 6, 2009 at 12:14 PM, Pavel Roskin <proski@gnu.org> wrote:
> > > Hello!
> > >
> > > If I scan by "iw dev wlan0 scan" while sending data through the
> > > interface, I get a BUG in net/mac80211/tx.c:
> >
> > Agreed... Also I think the same thing happens for rx for ath5k,
> > explaining the 'unknown rate index' warnings (sc->curband changes
> > during scan but we process a beacon from 2ghz band, that one at
> > least just needs some synchronization in the driver).
>
> Ah, that could be -- I sure am tired of reading bug reports about
> that...
I've bisected it. The problem is introduced by the commit
2038ccfbb5f7fc7d8bca26bf53bdd6c7778136ff:
Author: Johannes Berg <johannes@sipsolutions.net>
AuthorDate: Wed Apr 29 12:26:17 2009 +0200
Commit: John W. Linville <linville@tuxdriver.com>
CommitDate: Thu Apr 30 15:06:34 2009 -0400
mac80211: tell driver when idle
When we aren't doing anything in mac80211, we can turn off
much of the hardware, depending on the driver/hw. Not doing
anything, aka being idle, means:
...
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-05-06 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 16:14 ath5k: scanning while transmitting causes oops on 802.11a capable card Pavel Roskin
2009-05-06 16:19 ` Johannes Berg
2009-05-06 16:36 ` [ath5k-devel] " Bob Copeland
2009-05-06 17:25 ` John W. Linville
2009-05-06 20:12 ` Pavel Roskin [this message]
2009-05-06 20:26 ` Johannes Berg
2009-05-06 21:29 ` Pavel Roskin
2009-05-07 6:01 ` Johannes Berg
2009-05-07 8:56 ` Bob Copeland
2009-05-07 14:04 ` Bob Copeland
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=1241640751.3289.2.camel@mj \
--to=proski@gnu.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=me@bobcopeland.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.