From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>,
Reinette Chatre <reinette.chatre@intel.com>
Subject: Re: Problem with IEEE80211_MONITORING_INTERVAL
Date: Wed, 22 Apr 2009 12:17:08 +0100 [thread overview]
Message-ID: <1240399028.10072.14.camel@localhost.localdomain> (raw)
In-Reply-To: <1240393523.21978.1.camel@johannes.local>
Hi Johannes,
> > > > 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.
>
> I just don't see anything in the kernel that would ever set the
> interface down, as indicated there.
I will try to install the latest wireless-testing from today and try
again since John merged all the patches. Maybe this is an issue with
wpa_supplicant and the nl80211 driver, but I am always running the
latest stuff here. As soon as Jouni pushes fixes, I run them.
> > > > WARNING: at net/wireless/nl80211.c:205 nl80211_send_wiphy+0x4b/0x988
>
> > > > [<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.
>
> Indeed:
>
> $ git diff iwlwifi-2.6/master..wireless-testing/master net/wireless
> diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
> index ebda7c5..97bb5c8 100644
> --- a/net/wireless/nl80211.c
> +++ b/net/wireless/nl80211.c
> @@ -202,8 +202,6 @@ static int nl80211_send_wiphy(struct sk_buff *msg, u32 pid, u32 seq, int flags,
> int i;
> u16 ifmodes = dev->wiphy.interface_modes;
>
> - assert_cfg80211_lock();
> -
> hdr = nl80211hdr_put(msg, pid, seq, flags, NL80211_CMD_NEW_WIPHY);
> if (!hdr)
> return -1;
I think that Reinette will fix that once she arrives at the office :)
Sorry about that confusion. I do still have an issue though.
Regards
Marcel
next prev parent reply other threads:[~2009-04-22 11:17 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
2009-04-22 9:45 ` Johannes Berg
2009-04-22 11:17 ` Marcel Holtmann [this message]
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=1240399028.10072.14.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.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;
as well as URLs for NNTP newsgroup(s).