From: Johannes Stezenbach <js@sig21.net>
To: linux-wireless@vger.kernel.org
Subject: 2.6.36-rc7 warning in __cfg80211_auth_remove
Date: Thu, 7 Oct 2010 17:18:44 +0200 [thread overview]
Message-ID: <20101007151844.GB3183@sig21.net> (raw)
Hi,
just got the following while testing with rt73usb on
kernel 2.6.36-rc7 with wpa_supplicant v0.6.10:
wlan0: authentication with 00:22:b0:xx:xx:xx timed out
------------[ cut here ]------------
WARNING: at net/wireless/mlme.c:284 __cfg80211_auth_remove+0xc3/0xd0 [cfg80211]()
Hardware name: GA-MA78GM-S2H
Modules linked in: rt73usb rt2x00usb rt2x00lib mac80211 cfg80211 ppdev kvm_amd kvm ohci_hcd firewire_ohci firewire_core
Pid: 1167, comm: kworker/u:3 Not tainted 2.6.36-rc7 #1
Call Trace:
[<ffffffff81040979>] warn_slowpath_common+0x85/0x9d
[<ffffffff810409ab>] warn_slowpath_null+0x1a/0x1c
[<ffffffffa002d980>] __cfg80211_auth_remove+0xc3/0xd0 [cfg80211]
[<ffffffffa002e27c>] cfg80211_send_auth_timeout+0x93/0xaa [cfg80211]
[<ffffffffa00b12a7>] ? rt2x00mac_config+0x5e/0x68 [rt2x00lib]
[<ffffffffa004c3eb>] ieee80211_probe_auth_done+0x2a/0x97 [mac80211]
[<ffffffffa004e551>] ieee80211_work_work+0xecd/0xf3e [mac80211]
[<ffffffffa004d684>] ? ieee80211_work_work+0x0/0xf3e [mac80211]
[<ffffffff810595df>] process_one_work+0x29e/0x449
[<ffffffff81059b42>] worker_thread+0x1db/0x34d
[<ffffffff81059967>] ? worker_thread+0x0/0x34d
[<ffffffff8105cdbe>] kthread+0x82/0x8a
[<ffffffff810030a4>] kernel_thread_helper+0x4/0x10
[<ffffffff81044976>] ? do_exit+0x6c2/0x6d1
[<ffffffff814e5343>] ? _raw_spin_unlock_irq+0x21/0x3c
[<ffffffff814e5d41>] ? restore_args+0x0/0x30
[<ffffffff8105cd3c>] ? kthread+0x0/0x8a
[<ffffffff810030a0>] ? kernel_thread_helper+0x0/0x10
---[ end trace 1603934106686627 ]---
AP is also rt73usb in other machine, using WPA and hostapd 0.7.3.
Johannes
next reply other threads:[~2010-10-07 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 15:18 Johannes Stezenbach [this message]
2010-10-07 20:19 ` 2.6.36-rc7 warning in __cfg80211_auth_remove Johannes Berg
2010-10-07 21:59 ` Johannes Stezenbach
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=20101007151844.GB3183@sig21.net \
--to=js@sig21.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 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.