From: "John W. Linville" <linville@tuxdriver.com>
To: seventh guardian <seventhguardian@gmail.com>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: d80211 deadlock with wpa_supplicant and rmmod
Date: Wed, 11 Jul 2007 19:41:53 -0400 [thread overview]
Message-ID: <20070711234153.GB5099@tuxdriver.com> (raw)
In-Reply-To: <1caff7430707111617o70a534a5x2cf6b611a91f301a@mail.gmail.com>
On Thu, Jul 12, 2007 at 12:17:35AM +0100, seventh guardian wrote:
> Hello,
> First of all I'm fairly new to this list (in all, this is my first
> message), so please be gentle.. I promise I will try not to waste your
> precious time.
>
> >I believe we have a deadlock in d80211.
>
> I have it too. But I'm using iwl3945 driver, in-kernel mac80211, and a
> gentoo kernel (basically a patched vanilla-2.6.22.1). My machine is a
> x86_64 core 2 duo.
>
> >The following triggers it on my 2way SMT machine with preempt.
> >
> >modprobe bcm43xx-d80211
> >add sta0
> >ifconfig sta0 up
> >start wpa_supplicant on the interface
> >rmmod bcm43xx-d80211
> >
> >After that rmmod hangs spinning and wpa_supplicant
> >stays in D state.
> >
> >If I first kill wpa_supplicant and then rmmod the module,
> >it does not deadlock.
>
> I can trigger this way:
>
> modprobe iwl3945
> ifconfig wlan0 up
> start wpa_supplicant
> do some wpa_supplicant work (for instance issue a scan)
> stop wpa_supplicant
>
> Then it will deadlock (that is, wpa_supplicant will refuse to be
> killed). The same thing happens if I try to modprobe the module out
> (modprobe will "hang spinning" as you said). I have to ultimately
> hard-shutdown my machine to bring it back to normal.
It seems you are replying to a very old original message. Since that
message was sent, linux-wireless@vger.kernel.org has become the
primary forum for wireless discussion.
Any chance you are savvy enough with git to try the wireless-dev kernel?
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git
Can you replicate the problem using those sources? If so, you may
want to attach your .config in your reply (just in case the exact
config makes a difference).
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next parent reply other threads:[~2007-07-12 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1caff7430707111617o70a534a5x2cf6b611a91f301a@mail.gmail.com>
2007-07-11 23:41 ` John W. Linville [this message]
2007-07-12 2:20 ` d80211 deadlock with wpa_supplicant and rmmod seventh guardian
2007-07-12 10:02 ` Johannes Berg
2007-07-13 12:05 ` seventh guardian
2007-07-13 21:45 ` Johannes Berg
2007-07-14 13:24 ` Jiri Benc
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=20070711234153.GB5099@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=seventhguardian@gmail.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