From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
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 17:29:55 -0400 [thread overview]
Message-ID: <1241645395.3293.3.camel@mj> (raw)
In-Reply-To: <1241641605.4029.10.camel@johannes.local>
On Wed, 2009-05-06 at 22:26 +0200, Johannes Berg wrote:
> Huh? That's confusing. Also, you say you get a BUG but point out a
> WARN_ON_ONCE, was that an oversight or does something crash there?
Sorry, I meant WARN_ON_ONCE.
> OTOH, I can see one thing happening -- it would access scan_channel.
> Patch should fix that, does it help?
Yes, that does the trick! Several scans with iw and iwlist while flood
pinging the AP don't cause any kernel messages. Thank you!
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-05-06 21:29 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
2009-05-06 20:26 ` Johannes Berg
2009-05-06 21:29 ` Pavel Roskin [this message]
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=1241645395.3293.3.camel@mj \
--to=proski@gnu.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=johannes@sipsolutions.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox