From: Dirk Gouders <dirk@gouders.net>
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>,
Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>,
Johannes Berg <johannes.berg@intel.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG bisected] WARNING: CPU: 0 PID: 1550 at net/wireless/chan.c:373 cfg80211_chandef_usable+0x30/0x15f()
Date: Wed, 23 Oct 2013 07:41:54 +0200 [thread overview]
Message-ID: <ghvc0opmql.fsf@lena.gouders.net> (raw)
In-Reply-To: <201310222200.55773.sw@simonwunderlich.de> (Simon Wunderlich's message of "Tue, 22 Oct 2013 22:00:55 +0200")
Hi Simon,
Simon Wunderlich <sw@simonwunderlich.de> writes:
> Hey Dirk,
>
>> No need for censorship, I did some quick tests and stripped down my
>> wpa_supplicant.conf to a single entry. With this configuration I get a
>> lot of traces:
>>
>> ctrl_interface=/var/run/wpa_supplicant
>> eapol_version=1
>> ap_scan=1
>> fast_reauth=1
>>
>> network={
>> frequency=2412
>> group=TKIP
>> key_mgmt=NONE
>> mode=1
>> pairwise=NONE
>> ssid="Nokia_n9"
>> }
>>
>> I will also attach a dmesg output of my tests.
>>
>> > * your wpa_supplicant command line parameters when running
>>
>> It is running with a wpa_cli like this:
>>
>> /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf \
>> -W -B -i wlp4s0 -P /var/run/wpa_supplicant-wlp4s0.pid
>> /usr/bin/wpa_cli -a /etc/wpa_supplicant/wpa_cli.sh \
>> -p /var/run/wpa_supplicant -i wlp4s0 -P /var/run/wpa_cli-wlp4s0.pid -B
>>
>
> Thanks a lot for this, I could reproduce the issue and fix it, will send the fix
> in a minute - please try and report back.
thanks a lot, will send my test result immediately.
> Just two notes on your setup in case you are interested:
Yes, I am interested - I was just afraid to ask, because I didn't want
to cause too much noise with probably trivial problems ;-)
> * Your wpa-supplicant setup looks a little like an old WPA-NONE setup, but
> this is not supported anymore and will not encrypt your messages. Please have
> a look at IBSS/RSN if you want encryption.
Yes, I very rarely use that connection and always have in mind that it
is unencrypted. I will have a look at this but expect the mobile phone
side to be the hard one to get it to offer reliable encryption.
> * Your wpa_supplicant uses the old wext interface to the kernel. This is
> deprecated, it would better to use the (not so) new nl80211 interface instead.
> You will also get goodies such as 802.11n rates in ad-hoc mode if your
> hardware supports it. :)
Thats good to know, I will change my setup accordingly.
Thanks again for your help,
Dirk
> Thanks again for reporting,
> Simon
prev parent reply other threads:[~2013-10-23 5:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 12:09 [BUG bisected] WARNING: CPU: 0 PID: 1550 at net/wireless/chan.c:373 cfg80211_chandef_usable+0x30/0x15f() Dirk Gouders
2013-10-22 13:23 ` Simon Wunderlich
2013-10-22 15:14 ` Dirk Gouders
2013-10-22 20:00 ` Simon Wunderlich
2013-10-23 5:41 ` Dirk Gouders [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=ghvc0opmql.fsf@lena.gouders.net \
--to=dirk@gouders.net \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=siwu@hrz.tu-chemnitz.de \
--cc=sw@simonwunderlich.de \
/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