From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
linux-wireless@vger.kernel.org, "Guy,
Wey-Yi W" <wey-yi.w.guy@intel.com>
Subject: Re: Warning when terminating wpa_supplicant (wext driver)
Date: Sat, 09 May 2009 13:00:02 +0200 [thread overview]
Message-ID: <1241866802.30488.3.camel@johannes.local> (raw)
In-Reply-To: <43e72e890905081823w2087e84aq3294ae1461e75b38@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On Fri, 2009-05-08 at 18:23 -0700, Luis R. Rodriguez wrote:
> From the looks of it the intel hardware doesn't want to stop the
> aggregation session which is API-breakage -- which is why you get the
> WARN_ON.
Yup.
> This is happening when you are disassociating.
Exactly. But not always, it seems.
> I have a
> feeling johill's other patch will fix your issue but regardless I
> believe this just highlights more we should flush our queues (both RX
> and TX) before scanning.
It might fix the disassoc, but I don't think it'll fix this issue. Might
make it disappear anyway though.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-05-09 11:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 6:18 Warning when terminating wpa_supplicant (wext driver) Marcel Holtmann
2009-05-07 11:35 ` Johannes Berg
2009-05-07 13:53 ` Marcel Holtmann
2009-05-07 14:19 ` Johannes Berg
2009-05-09 0:02 ` Marcel Holtmann
2009-05-09 1:13 ` Luis R. Rodriguez
2009-05-09 1:16 ` Luis R. Rodriguez
2009-05-09 1:18 ` Marcel Holtmann
2009-05-09 1:23 ` Luis R. Rodriguez
2009-05-09 11:00 ` Johannes Berg [this message]
2009-05-09 11:09 ` Johannes Berg
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=1241866802.30488.3.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mcgrof@gmail.com \
--cc=wey-yi.w.guy@intel.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.