Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Aug 2012 23:15:09 -0700
From:      Adrian Chadd <adrian@freebsd.org>
To:        freebsd-wireless@freebsd.org
Subject:   Re: net80211/driver LORs: http://wiki.freebsd.org/WiFiDebugging
Message-ID:  <CAJ-VmokqTt84eawJXypJ9i_rM%2B9mCM0gtAj-ZzfVUK5-4krDdg@mail.gmail.com>
In-Reply-To: <CAJ-Vmok8wTVoy5UWh9QsKkLj8HWO0qfL=7UK-xtqezcK7OZgew@mail.gmail.com>
References:  <CAJ-Vmok8wTVoy5UWh9QsKkLj8HWO0qfL=7UK-xtqezcK7OZgew@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
.. so the first LOR is between node table lock and comlock - the
former in ieee80211_timeout_stations() and the latter in
ieee80211_set_tim().

So, something is holding the comlock when the node table lock is being
grabbed. Where is that happening? Would someone like to tackle that
particular issue?

Eg, what about printing out a witness backtrace if the comlock is held
when the node table lock is held? And vice versa? Just to try and
figure out who is holding things incorrectly?


Adrian



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokqTt84eawJXypJ9i_rM%2B9mCM0gtAj-ZzfVUK5-4krDdg>