From: Simon Wunderlich <sw@simonwunderlich.de>
To: Dirk Gouders <dirk@gouders.net>
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: Tue, 22 Oct 2013 22:00:55 +0200 [thread overview]
Message-ID: <201310222200.55773.sw@simonwunderlich.de> (raw)
In-Reply-To: <ghzjq1pcc3.fsf@lena.gouders.net>
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.
Just two notes on your setup in case you are interested:
* 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.
* 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. :)
Thanks again for reporting,
Simon
next prev parent reply other threads:[~2013-10-22 20:11 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 [this message]
2013-10-23 5:41 ` Dirk Gouders
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=201310222200.55773.sw@simonwunderlich.de \
--to=sw@simonwunderlich.de \
--cc=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 \
/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