On Thu, May 28, 2009 at 07:40:36AM -0700, Andrey Yurovsky wrote:

Thanks.  For what it's worth, substituting rt2x00 for ath9k works (ie:
one can bring up a mesh) on the same kernel, so it likely has
something to do with the driver.

OK, I traced it to the driver. It looks like mac80211 is asking the
driver to setup beaconing with beacon interval of zero (struct
ieee80211_bss_conf::beacon_int == 0) which does not sound correct to
me.. The adhoc mode beacon setup (which is also shared for mesh) in
ath9k does not exactly like this and ends up in an infinite loop trying
to figure out how many beacon frames have been transfered before the
current TSF..

We can obviously add a sanity check to the driver to avoid the busy
loop, but I would assume that something in the mac80211 mesh code could
also be changed to provide a more reason beacon interval to the driver.

-- 
Jouni Malinen                                            PGP id EFC895FA