From: Andi Kleen <andi@firstfloor.org>
To: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
rjw@sisk.pl
Subject: RTL8185 mlme.c:341 warning and failure still in 2.6.34rc7
Date: Fri, 14 May 2010 15:37:23 +0200 [thread overview]
Message-ID: <20100514133723.GA10351@basil.fritz.box> (raw)
[ccing Rafael because this seems to be a regression. Please add it to your list.]
When I boot my system with a RTL8185 the wireless doesn't come up at boot,
only when I manually restart it. Instead i get
I reported this a few rc*s back, but haven't heard anything back and the
problem is still there.
For me it's a serious problem when the wireless does not come up.
This didn't happen in .33.
-Andi
wlan0: authenticate with 00:1f:3f:1d:54:46 (try 1)
wlan0: authenticated
wlan0: associate with 00:1f:3f:1d:54:46 (try 1)
wlan0: associate with 00:1f:3f:1d:54:46 (try 2)
wlan0: associate with 00:1f:3f:1d:54:46 (try 3)
wlan0: association with 00:1f:3f:1d:54:46 timed out
------------[ cut here ]------------
WARNING: at /home/lsrc/linux-2.6.34-rc7/net/wireless/mlme.c:341 cfg80211_send_assoc_timeout+0xff/0x117 [cfg80211]()
Hardware name: ...
Modules linked in: ...
Pid: 3344, comm: phy0 Not tainted 2.6.34-rc7 #7
Call Trace:
[<ffffffffa0072124>] ? cfg80211_send_assoc_timeout+0xff/0x117 [cfg80211]
[<ffffffff8103a4f0>] warn_slowpath_common+0x7c/0xa9
[<ffffffff8103a531>] warn_slowpath_null+0x14/0x16
[<ffffffffa0072124>] cfg80211_send_assoc_timeout+0xff/0x117 [cfg80211]
[<ffffffffa00e6393>] ieee80211_assoc_done+0x74/0xa9 [mac80211]
[<ffffffffa00e85f0>] ieee80211_work_work+0xe4c/0xe8d [mac80211]
[<ffffffff81033cbe>] ? finish_task_switch+0x42/0xab
[<ffffffff810535d7>] ? prepare_to_wait+0x6e/0x7a
[<ffffffff8104f832>] worker_thread+0x192/0x227
[<ffffffffa00e77a4>] ? ieee80211_work_work+0x0/0xe8d [mac80211]
[<ffffffff81053342>] ? autoremove_wake_function+0x0/0x3d
[<ffffffff8104f6a0>] ? worker_thread+0x0/0x227
[<ffffffff81052efc>] kthread+0x82/0x8a
[<ffffffff81003954>] kernel_thread_helper+0x4/0x10
[<ffffffff81052e7a>] ? kthread+0x0/0x8a
[<ffffffff81003950>] ? kernel_thread_helper+0x0/0x10
---[ end trace 4e3067114aa2fd06 ]---
wlan0: deauthenticating from 00:1f:3f:1d:54:46 by local choice (reason=3)
--
ak@linux.intel.com -- Speaking for myself only.
next reply other threads:[~2010-05-14 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 13:37 Andi Kleen [this message]
2010-05-22 19:18 ` RTL8185 mlme.c:341 warning and failure still in 2.6.34rc7 Rogerio Luz Coelho
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=20100514133723.GA10351@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).