From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: New cfg80211 warning on 2.6.32-rc<bleh>
Date: Tue, 29 Sep 2009 12:37:12 -0700 [thread overview]
Message-ID: <43e72e890909291237q23c40b91xc45245d44a4c10d6@mail.gmail.com> (raw)
I got this while running my tests by booting with mem=300M and CPU downscaled.
Luis
[ 2032.396393] phy4: Removed STA <ap-BSSID>
[ 2032.408522] phy4: Destroyed STA <ap-BSSID>
[ 2032.408542] wlan0: deauthenticating from <ap-BSSID> by local choice
(reason=3)
[ 2032.442906] phy4: device now idle
[ 2032.451837] ------------[ cut here ]------------
[ 2032.451876] WARNING: at net/wireless/core.c:613
wdev_cleanup_work+0xe9/0x110 [cfg80211]()
[ 2032.451883] Hardware name: 7660A14
[ 2032.451888] Modules linked in: ath5k(-) <bleh>
[ 2032.452072] Pid: 10, comm: events/1 Tainted: G W 2.6.32-rc2-wl #45
[ 2032.452080] Call Trace:
[ 2032.452098] [<ffffffff8105be78>] warn_slowpath_common+0x78/0xb0
[ 2032.452109] [<ffffffff8105bebf>] warn_slowpath_null+0xf/0x20
[ 2032.452127] [<ffffffffa00c25b9>] wdev_cleanup_work+0xe9/0x110 [cfg80211]
[ 2032.452144] [<ffffffffa00c24d0>] ? wdev_cleanup_work+0x0/0x110 [cfg80211]
[ 2032.452156] [<ffffffff81075c3e>] worker_thread+0x1fe/0x3b0
[ 2032.452165] [<ffffffff81075bed>] ? worker_thread+0x1ad/0x3b0
[ 2032.452176] [<ffffffff8107abf0>] ? autoremove_wake_function+0x0/0x40
[ 2032.452188] [<ffffffff81075a40>] ? worker_thread+0x0/0x3b0
[ 2032.452198] [<ffffffff8107a82e>] kthread+0x8e/0xa0
[ 2032.452209] [<ffffffff8101300a>] child_rip+0xa/0x20
[ 2032.452221] [<ffffffff81012990>] ? restore_args+0x0/0x30
[ 2032.452230] [<ffffffff8107a7a0>] ? kthread+0x0/0xa0
[ 2032.452239] [<ffffffff81013000>] ? child_rip+0x0/0x20
[ 2032.452245] ---[ end trace 7d678c5342bdcaab ]---
[ 2033.767265] ath5k 0000:03:00.0: PCI INT A disabled
reply other threads:[~2009-09-29 19:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43e72e890909291237q23c40b91xc45245d44a4c10d6@mail.gmail.com \
--to=mcgrof@gmail.com \
--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