On Mon, 2010-10-04 at 16:34 -0700, Ben Greear wrote: > I'm (also) trying to debug an issue with an ath5k system that deadlocks. > > We have sysrq output for the held locks, process backtraces, etc. > > One thing that has me confused is that the locks-held output shows > a large number of processes owning the rtnl_mutex. Any idea > how to tell what process *really* owns it? Can't really -- the mutex code acquires the lockdep dep_map before it even manages to lock, so that it can detect recursive locking. johannes -- 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
