From: Johannes Berg <johannes@sipsolutions.net>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.35-rc2-git1 - WARNING: at net/wireless/mlme.c:341 cfg80211_send_assoc_timeout+0x107/0x11e [cfg80211]()
Date: Mon, 07 Jun 2010 21:14:06 +0200 [thread overview]
Message-ID: <1275938046.29978.21.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTinmZh9GnrZLzOGi5Q_xHbky8cKdHAkOnsIA6_dZ@mail.gmail.com>
On Mon, 2010-06-07 at 15:06 -0400, Miles Lane wrote:
> [ 44.090157] WARNING: at net/wireless/mlme.c:341
> cfg80211_send_assoc_timeout+0x107/0x11e [cfg80211]()
> [ 44.090162] Hardware name: UL50VT
> [ 44.090165] Modules linked in: ipv6 snd_hda_codec_nvhdmi
> snd_seq_dummy snd_seq_oss snd_seq_midi snd_hda_codec_realtek
> snd_rawmidi snd_seq_midi_event snd_hda_intel iwlagn snd_hda_codec
> snd_hwdep snd_seq snd_pcm_oss snd_mixer_oss iwlcore snd_pcm mac80211
> snd_seq_device snd_timer uvcvideo rtc_cmos videodev rtc_core
> v4l1_compat v4l2_compat_ioctl32 snd psmouse cfg80211 rtc_lib atl1c
> snd_page_alloc asus_laptop battery sparse_keymap rfkill ac led_class
> sg sr_mod cdrom sd_mod ehci_hcd uhci_hcd
> [ 44.090239] Pid: 3915, comm: phy0 Not tainted 2.6.35-rc2-git1 #8
> [ 44.090242] Call Trace:
> [ 44.090254] [<ffffffff8103a482>] warn_slowpath_common+0x80/0x98
> [ 44.090261] [<ffffffff8103a4af>] warn_slowpath_null+0x15/0x17
> [ 44.090276] [<ffffffffa009b583>]
> cfg80211_send_assoc_timeout+0x107/0x11e [cfg80211]
> [ 44.090296] [<ffffffffa0115427>] ieee80211_assoc_done+0x71/0xa6 [mac80211]
Yeah, just had another report of this. I thought we'd fixed it, but I
guess not.
Do you happen to have more verbose kernel messages before this?
johannes
prev parent reply other threads:[~2010-06-07 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 19:06 Miles Lane
2010-06-07 19:14 ` Johannes Berg [this message]
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=1275938046.29978.21.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.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
all inboxes | Powered by JetHome®