On Tue, 2009-07-21 at 17:50 -0700, Luis R. Rodriguez wrote:
> While running on wireless-testing + netns pending patches + wow patches:
>
> wpa_supplicant -D wext -i wlan1 -c mosca.conf
>
> [ 233.096916] phy0: device now idle
> [ 233.114625] ADDRCONF(NETDEV_UP): wlan1: link is not ready
> [ 234.116189] phy0: device no longer idle - scanning
> [ 234.233767]
> [ 234.233772] =======================================================
> [ 234.233797] [ INFO: possible circular locking dependency detected ]
> [ 234.233807] 2.6.31-rc3-wl #16
> [ 234.233814] -------------------------------------------------------
> [ 234.233824] wpa_supplicant/3089 is trying to acquire lock:
> [ 234.233835] (cfg80211_mutex){+.+.+.}, at: [<f83eb185>]
> cfg80211_get_dev_from_ifindex+0x15/0x80 [cfg80211]
> [ 234.233887]
> [ 234.233889] but task is already holding lock:
> [ 234.233901] (rtnl_mutex){+.+.+.}, at: [<c049de2f>] rtnl_lock+0xf/0x20
> [ 234.233932]
> [ 234.233934] which lock already depends on the new lock.
> [ 234.233936]
> [ 234.233957]
> [ 234.233958] the existing dependency chain (in reverse order) is:
> [ 234.233970]
> [ 234.233972] -> #1 (rtnl_mutex){+.+.+.}:
> [ 234.233996] [<c0169b35>] __lock_acquire+0xba5/0x1020
> [ 234.234014] [<c016a06b>] lock_acquire+0xbb/0xe0
> [ 234.234029] [<c05838f4>] mutex_lock_nested+0x54/0x300
> [ 234.234045] [<c049de2f>] rtnl_lock+0xf/0x20
> [ 234.234061] [<f83f734a>] nl80211_send_reg_change_event+0x1aa/0x250 [cfg80211]
I think you're using the wrong genetlink netns patch.
johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
