Patrick McHardy wrote:
Larry Finger wrote:
Patrick McHardy wrote:
Larry Finger wrote:
=============================================
[ INFO: possible recursive locking detected ]
2.6.26-Linus-git-05752-g93ded9b #49
^^^^^^^^^^^^^^ dirty?
This kernel is not using the patches we sent.
No, but they didn't make any difference. I tried with all 3 applied,
then backed them out one by one. That was the state when I posted before.
Well, this is a completely different warning.
Here are the dumps with all 3 patches applied:
=============================================
[ INFO: possible recursive locking detected ]
2.6.26-Linus-05752-g93ded9b-dirty #53
---------------------------------------------
b43/1997 is trying to acquire lock:
(_xmit_IEEE80211#2){-...}, at: [<ffffffffa028f322>]
ieee80211_scan_completed+0x130/0x2e1 [mac80211]
but task is already holding lock:
(_xmit_IEEE80211#2){-...}, at: [<ffffffffa028f322>]
ieee80211_scan_completed+0x130/0x2e1 [mac80211]
Sorry. After all those kernel builds I got bleary-eyed and just looked for
recursive locking without any regard for the details.
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
