From: Kalle Valo <kalle.valo@iki.fi>
To: reinette chatre <reinette.chatre@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: [PATCH v4] cfg80211: validate channel settings across interfaces
Date: Sat, 08 Aug 2009 11:49:25 +0300 [thread overview]
Message-ID: <874osin10q.fsf@litku.valot.fi> (raw)
In-Reply-To: <1249712383.30019.5561.camel@rc-desk> (reinette chatre's message of "Fri\, 07 Aug 2009 23\:19\:43 -0700")
reinette chatre <reinette.chatre@intel.com> writes:
> Hi Johannes,
Hi,
> This patch is now in wireless-testing and it is causing a problem for
> me. This was determined using bisect.
>
> I am able to bring the interface up and scan, but when I try to
> associate I get a hang.
>
> For example, when I run:
> $ iwconfig wlan0 channel <ch> essid <essid>
>
> then the command prompt never returns and system becomes progressively
> unresponsive. The logs do not contain any details of the problem.
I see the same problem with my iwl3945. I do 'sudo ifup wlan0' (which
starts wpa_supplicant), command prompt is printed once and then laptop
just hangs.
Reverting this commit fixes the issue:
commit e66cda2a15bede6fc3fa74482337a00ba768983a
Author: Johannes Berg <johannes@sipsolutions.net>
Date: Fri Aug 7 17:22:35 2009 +0200
cfg80211: validate channel settings across interfaces
--
Kalle Valo
next prev parent reply other threads:[~2009-08-08 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 12:47 [PATCH] cfg80211: validate channel settings across interfaces Johannes Berg
2009-08-07 12:50 ` [PATCH v2] " Johannes Berg
2009-08-07 13:49 ` [PATCH v3] " Johannes Berg
2009-08-07 15:22 ` [PATCH v4] " Johannes Berg
2009-08-08 6:19 ` reinette chatre
2009-08-08 8:43 ` Johannes Berg
2009-08-08 8:49 ` Kalle Valo [this message]
2009-08-08 19:33 ` Larry Finger
2009-08-08 20:10 ` Kalle Valo
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=874osin10q.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--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).