On Tue, Feb 05, 2013 at 12:26:47AM +0100, Mark Kettenis wrote: > > Date: Tue, 29 Jan 2013 21:04:30 -0500 > > From: Brad Smith <[email protected]> > > > > To a certain extent this seems to make rsu(3) work a little better, but > > now I am seeing ``rsu0: could not send join command'' messages which never > > happened before. > > Hmm, I wonder which of the two rsu_fw_cmd() calls in rsu_join_bss() is > failing. It seems to be the first call to rsu_fw_cmd() from the debug output.. the failure within rsu_join_bss() does not happen with every call of the rsu_join_bss() function though.
site survey pass 0 done, found 3 BSS newstate 1 -> 1 sending site survey command, pass=1 Tx cmd code=18 len=48 Rx event code=19 len=33 Rx event code=19 len=16 Rx event code=19 len=16 Rx event code=8 len=424 found BSS 84:1b:5e:4d:ef:36: len=424 chan=1 inframode=1 networktype=3 privacy=1 Rx event code=9 len=4 site survey pass 1 done, found 1 BSS newstate 1 -> 2 setting operating mode to 2 Tx cmd code=17 len=8 Rx event code=19 len=33 rsu0: could not send join command newstate 1 -> 1 sending site survey command, pass=0 Tx cmd code=18 len=48 rsu0: could not send site survey command $ dmesg | grep join sending join bss command to 84:1b:5e:4d:ef:36 chan 1 Rx join BSS event len=180 res=1 sending join bss command to 84:1b:5e:4d:ef:36 chan 1 Rx join BSS event len=180 res=1 sending join bss command to 84:1b:5e:4d:ef:36 chan 1 Rx join BSS event len=180 res=1 sending join bss command to 84:1b:5e:4d:ef:36 chan 1 Rx join BSS event len=180 res=1 sending join bss command to 84:1b:5e:4d:ef:36 chan 1 Rx join BSS event len=180 res=1 sending join bss command to 84:1b:5e:4d:ef:36 chan 1 Rx join BSS event len=180 res=1 rsu0: could not send join command sending join bss command to 84:1b:5e:4d:ef:36 chan 1 Rx join BSS event len=180 res=1 sending join bss command to 84:1b:5e:4d:ef:36 chan 1 Rx join BSS event len=180 res=1 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
