[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1caff7430707111617o70a534a5x2cf6b611a91f301a@mail.gmail.com>
Date: Thu, 12 Jul 2007 00:17:35 +0100
From: "seventh guardian" <seventhguardian@...il.com>
To: netdev@...r.kernel.org
Subject: Re: d80211 deadlock with wpa_supplicant and rmmod
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.
> Below is sysrq-t output. It looks like it's related to rtnl_mutex.
>
> (...)
I'm sorry for my inexperience, but I have no idea on which more data
to provide you. I will gladly help running any tests you would find
appropriate.
> --
> Greetings Michael.
Cheers,
Renato Caldas
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists