On Mar 15, 2009, at 13:45 , Ivo van Doorn wrote:
On Sunday 15 March 2009, Antonio Marques wrote:
Upon further investigation, beaconing does not work after configuring
an interface in mesh point mode but running 'iwlist mesh scan'
triggers something in the driver that enables beaconing.
After executing this command beacons are generated and correctly
received at other nodes.
Thats odd, but very interesting :)
Could you enable debugfs and CONFIG_RT2X00_LIB_DEBUGFS and
use the script from http://kernel.org/pub/linux/kernel/people/ivd/tools/rt2x00_regdump.sh
to create a register dump before running 'iwlist mesh scan' and
afterwards.
(So basically when beaconing is broken and when it is working).
Thanks,
Ivo
As requested, I have attached the output of the script run before and
after
running 'iwlist mesh scan'. Unfortunately there seems to be no change in
the output. I have also included the queue statistics as these do
change from
one state to the next. Any further pointers to help debug this? I'll
gladly test
any patches that try to address this issue.
Antonio Marques
Before running 'iwlist mesh scan':
kernel: 2.6.29-rc7-wl
driver: rt73usb
version: 2.3.0
compiled: Mar 16 2009 11:53:37
dev_flags: 0x0000625f
rt chip: 1300
rf chip: 0002
revision: 0002573a
register base words wordsize
csr 12288 300 4
eeprom 0 128 2
bbp 0 128 1
rf 4 4 4
Queues:
qid count limit length index done crypto
14 0 24 1 1 0 0
0 0 24 0 0 0 0
1 0 24 0 0 0 0
2 6 24 0 6 6 0
3 0 24 0 0 0 0
16 0 4 0 0 0 0
After running 'iwlist mesh scan':
kernel: 2.6.29-rc7-wl
driver: rt73usb
version: 2.3.0
compiled: Mar 16 2009 11:53:37
dev_flags: 0x0000625f
rt chip: 1300
rf chip: 0002
revision: 0002573a
register base words wordsize
csr 12288 300 4
eeprom 0 128 2
bbp 0 128 1
rf 4 4 4
Queues:
qid count limit length index done crypto
14 0 24 8 8 0 0
0 11 24 0 11 11 0
1 0 24 0 0 0 0
2 6 24 0 6 6 0
3 0 24 0 0 0 0
16 0 4 0 0 0 0
--
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
