On Sat, Aug 22, 2009 at 4:52 AM, Thiemo Nagel<thiemo.na...@ph.tum.de> wrote:
> Hi,
>
> just in case anybody is interested: I've recently had a lockdep warning
> about ath5k shortly after wakeup with 2.6.31-rc6 (see attachment).
Hmm, neither of these locks are taken directly by ath5k, so I would
suspect some problem further up the stack.
> [25341.376982] =======================================================
> [25341.376996] [ INFO: possible circular locking dependency detected ]
> [25341.377007] 2.6.31-rc6 #1
> [25341.377014] -------------------------------------------------------
> [25341.377019] events/0/9 is trying to acquire lock:
> [25341.377019] (cpu_add_remove_lock){+.+.+.}, at: [<c102fd8a>]
> cpu_maps_update_begin+0xf/0x11
> [25341.377019]
> [25341.377019] but task is already holding lock:
> [25341.377019] (&ehotk->hotplug_work){+.+.+.}, at: [<c103dadb>]
> worker_thread+0x1a8/0x2a2
> [25341.377019]
> [25341.377019] which lock already depends on the new lock.
--
Bob Copeland %% www.bobcopeland.com
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
