linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>
Subject: Re: Problem with IEEE80211_MONITORING_INTERVAL
Date: Wed, 22 Apr 2009 10:12:21 +0100	[thread overview]
Message-ID: <1240391541.10072.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1240391029.20308.1.camel@johannes.local>

Hi Johannes,

> > one other weird thing happens now (except wireless-testing tree and
> > suspend/resume is broken). The first connection attempt fails horribly:
> > 
> > CTRL-EVENT-SCAN-RESULTS 
> > Trying to authenticate with 00:23:ab:xx:xx:xx (SSID='Guest' freq=2412 MHz)
> > Trying to associate with 00:23:ab:xx:xx:xx (SSID='Guest' freq=2412 MHz)
> > Associated with 00:23:ab:xx:xx:xx
> > CTRL-EVENT-CONNECTED - Connection to 00:23:ab:xx:xx:xx completed (auth) [id=2 id_str=]
> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > l2_packet_receive - recvfrom: Network is down
> > Failed to initiate AP scan.
> > Failed to initiate AP scan.
> > ^CCTRL-EVENT-TERMINATING - signal 2 received
> > 
> > So starting wpa_supplicant does its job fine, then running dhclient I
> > end up in the disconnect and network down and after that scanning fails.
> 
> ???
> 
> And the below kernel message is all yo uget?

Yes, I am as puzzled as you are and can't make any sense out of it. It
seems that something is going horribly wrong here somewhere. I just
don't have any clue where.

> > Killing wpa_supplicant and dhclient and then trying again works fine. So
> > far I have seen that only after a fresh boot.
> > 
> > Found this one in dmesg:
> > 
> > ------------[ cut here ]------------
> > WARNING: at net/wireless/nl80211.c:205 nl80211_send_wiphy+0x4b/0x988
> > [cfg80211]()
> > Hardware name: 7454CTO
> > Modules linked in: fuse rfcomm sco bnep l2cap binfmt_misc
> > snd_hda_codec_conexant iwlagn iwlcore snd_hda_intel i2400m_usb
> > snd_hda_codec i2400m mac80211 uvcvideo snd_pcm btusb snd_timer snd wimax
> > cfg80211 soundcore bluetooth snd_page_alloc uhci_hcd ehci_hcd [last
> > unloaded: microcode]
> > Pid: 3274, comm: wpa_supplicant Tainted: G        W  2.6.30-rc2-wl #1
> > Call Trace:
> >  [<ffffffff80236604>] warn_slowpath+0xb1/0xe5
> >  [<ffffffff8039a44a>] ? extract_buf+0x84/0xe4
> >  [<ffffffffa0055e04>] nl80211_send_wiphy+0x4b/0x988 [cfg80211]
> 
> What tree are you using? This warning totally confuses me -- there's no
> code to produce it! It was a spurious warning Luis added some time ago,
> we removed right away again and now it's haunting us.

This is the iwlwifi tree based on wireless-testing. It should be
re-based, but maybe an old patch is still stuck in it. Remember that I
am using the nl80211 driver of wpa_supplicant.

Regards

Marcel



  reply	other threads:[~2009-04-22  9:12 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 23:21 Problem with IEEE80211_MONITORING_INTERVAL Marcel Holtmann
2009-04-16  0:21 ` Johannes Berg
2009-04-16  0:44   ` Johannes Berg
2009-04-16  1:12     ` Marcel Holtmann
2009-04-16  1:08   ` Marcel Holtmann
2009-04-16  1:16     ` Johannes Berg
2009-04-16  6:14   ` Kalle Valo
2009-04-16  9:12     ` Johannes Berg
2009-04-16  9:43       ` Johannes Berg
2009-04-16  9:49         ` Kalle Valo
2009-04-16  9:58           ` Johannes Berg
2009-04-16  9:59       ` Kalle Valo
2009-04-16 10:04         ` Johannes Berg
2009-04-16 10:08           ` Kalle Valo
2009-04-16 10:18             ` Johannes Berg
2009-04-16 10:23               ` Kalle Valo
2009-04-16  9:46 ` Johannes Berg
2009-04-20 17:13   ` Marcel Holtmann
2009-04-20 17:20     ` Johannes Berg
2009-04-20 17:26       ` Marcel Holtmann
2009-04-20 17:32         ` Johannes Berg
2009-04-21 19:56           ` Marcel Holtmann
2009-04-21 21:19             ` Johannes Berg
2009-04-22  7:32               ` Marcel Holtmann
2009-04-22  9:03                 ` Johannes Berg
2009-04-22  9:12                   ` Marcel Holtmann [this message]
2009-04-22  9:45                     ` Johannes Berg
2009-04-22 11:17                       ` Marcel Holtmann
2009-04-22 11:53                         ` Marcel Holtmann
2009-04-22 12:14                           ` Johannes Berg
2009-04-22 12:56                             ` Marcel Holtmann
2009-04-22 13:27                           ` John W. Linville
2009-04-22 17:35                       ` reinette chatre
2009-04-22  5:04             ` Kalle Valo
2009-04-22  7:27               ` Marcel Holtmann
2009-04-20 18:29     ` Jouni Malinen
2009-04-21 10:47       ` Marcel Holtmann

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=1240391541.10072.2.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.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 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).